FFAStrans forum

Well, I don't have access to the NLE and QC you're using so it's a bit difficult to recreate and investigate. Does the issue occur if you submit a file directly to the "XDCAM-HD" encoder?

-steinar

Hi Jakida, I'm not able to reproduce. Using your workflow and mp4-file, the output mxf file is pretty much identical to the original, apart from the properties. No missing frames as far as I can tell. I loaded both files into Premiere and both look nice and dandy. Where and/or how do you see the mis...

Oh well, yes I seen similar things happening to the monitor. It's very basic and dare I say poorly written. But I will take a look at how it can be fixed without too much effort but I'm not going to spend too much time on the current web monitor.

-steinar

Well, I'm sorry but the last option in the "Audio extractor" shows I've been experimenting with the true peak implementation. However, it's not completed and the option should have been removed prior to release. It was sloppy and I'm sorry for the inconvienience. :oops: The problem is also present i...

Hi taner, This is as expected in a farm setup. It does not matter what cache metod you're using. Also, the way the farming implementation in FFAStrans work, your files might be picked up by a semi busy host, but it's less likely as it will not look for jobs that often. If the job is picked up by a h...

I have looked into it and it's a bit more challengig than it might seem: Modifying one thing (max peak or loudness) affects the other, which in turn affects the one you modified in the first place. So it's a contiunous adjustment of the two parameters until you reach something which is true to specs...

Thanks for the report, Taner. I'll take a look at it.

-steinar

Hi BitScroll,

I really don't care how you use FFAStrans

-steinar

Hei Benjamin

Keeping your "old" node that deletes the cache record should not be a problem.

-steinar

Important notice: In the latest 0.9.2 release, the users of the QT reference approach might need to add "color = 0" (RGB24) or "color = 1" (RGB32) to their QTInput string. The latest AviSynth+ release(s) does not deal well with the default YUY2 output coming from the QTSource plugin. From the examp...