Files are using their localised file names as their output names in the WebInterface

[SheldonABS]

Hi Team,

I've noticed a bug within the latest version of the WebInterface where once a file has finished transcoding, it uses its localised file name as its name in the File column. I have attached screenshots.

We have recently updated the instance of both FFAStrans and the WebInterface on three of our machines and we have noticed this on two of our machines. The weird thing about it is that it seems to be targeting different extension types depending on the machine. Screenshots 1 & 2 are the problematic ones and screenshot 3 is the unaffected one.

Screenshot 1 shows that the majority of files that complete transcode come out with the localised file name in the file column, however we noticed that on this machine it is only for the .mp4 files that are inputted. When we input a .mxf file, this outputs as its original file name without any issues.

Screenshot 2 shows that only few files are affected but it only seemed to affect .mov files that are inputted. Inputting a .mp4 or .mxf files into this machine has a result of its original file name as its output.

Screenshot 3 for reference only has .mxf files as inputs.

It doesn't seem to matter which workflow the files go through but if they are their "targeted" file type it outputs as its localised file name. Currently we have a workaround in place of adding an additional column for its filename which is done using a populate variables node to assign the original file name to "s_filename" and display that on the WebInterface but we'd prefer it to be like the previous versions where this wasn't present if possible?

Please could we have any suggestions on how to resolve?

Do let me know if you need any more details and thanks in advance for the help!