FFAStrans forum

Hi udosauer, thank you for using FFAStrans and welcome to the forum! :-) I'm sorry but the project is closed source and there is no SDK to create own nodes. This might change in the future but currently this is the state of the project. It's also undergoing a major revision so the current release wi...

Hi knuelle, thank you for using FFAStrans and for your interest in taking a part of the development :-) Right now, the code is undergoing a major change so giving broad access to the code at this point is not a viable option. So currently both the old and new source code is closed. This might change...

Hi seePyou,

I know about this shortcoming with the youtube-dl applications getting outdated. This will be addressed in the next major version of FFAStrans.

-steinar

I can think of several reasons why the variable is not populated but they all must be due to a programming error or logical flaw, or system deviation. So as Harry writes, the answer is probably in the user variable file that is passed from node to node. In the ideal world it really should not matter...

Gotta hand it to you, Harry; it seems you have a valid point after all regarding the "too fast for the ffastrans code"! When I tried yesterday with a batch-script containing only "exit 1" it worked flawless but with your "cmd /C "dir y:" " example it does not. So now I have changed the code to wait ...

Why do you believe that is the case, Harry? Windows will store information like the exit code for that PID's handle for...I guess until the PID is reused. So long after the process has closed you can actually ask for the exit code if you know the PID, which FFAStrans definately does. Alexander, mayb...

Hi Ricardo, The reason you had trouble is because you have 3 monitors picking up the same files and at the end you have a node that tries to move the original file. This will cause the conflict you are seeing. TThe three monitor nodes have been lying on top of each other causing you to only see one....

Hi Ricardo, thank you for using FFAStrand and welcome to the forum!

I would like to take a look at your workflow and your ffastrans.ini file. Can you export your workflow and send the files?

-steinar

Hi Alexander, thanx for reporting! I will take a look at it.

-steinar

@Benjamin, this warning is for the ProRes encoder, not when you use prores in a custom node like pntaylor is doing.
@pntaylor, we need to know it this allways happen or just occationally.

-steinar