Page 1 of 1

Error with DNxHD encoder atom

Posted: Fri Mar 30, 2018 12:45 pm
by momocampo
Hello,

I had an error with a workflow quiet simple:
Ftp > Encoder DHxHD (120 with "create avid project structure" check) > delivery
I want just download a file (mxf XDCAM HD) from ftp (growing files check and sleeper time =60), encode it in dnxhd and delivery in a avid folder. I add I tried with little files and it works well.
But, I enable this workflow last night to catch a file but this morning this message :

Image

I saw in the ffastrans work folder the original downloaded file and the encoded DNxHD file. That's means the download and the encoding were ok. Problem in delivery : file too big?? (24 Go).
If someone could help me, it will be very kind.
Thanks
;)

Benjamin

Re: Error with DNxHD encoder atom

Posted: Fri Mar 30, 2018 8:32 pm
by admin
Can you please check which version of processors.exe you are running? It's in the "About FFAStrans" under "Help" in the main GUI.

Thanks!

-steinar

Re: Error with DNxHD encoder atom

Posted: Fri Mar 30, 2018 8:52 pm
by momocampo
Hello Steinar,
Ok I will check but it will be not before Tuesday. But I checked I had use 0.9.0.3 patch.
Cheers.
B.

Re: Error with DNxHD encoder atom

Posted: Fri Mar 30, 2018 9:18 pm
by admin
Ok that's fine. I think I know what might be the problem, but I need to know what your Avid section configuration looks like. So just let me know on Tuesday. Happy weekend and thanks for reporting bugs! :-)

-steinar

Re: Error with DNxHD encoder atom

Posted: Sat Mar 31, 2018 10:27 am
by momocampo
Hi Steinar,
Here is the avid DnxHD node . I must say in my first idea I choose XDcam node but you know a bug is present for xdcam+avid structure so I used DNXHD.

Image

I repeat I tried with small mxf XDCAM files and it was ok.

Thanks.

B.

Re: Error with DNxHD encoder atom

Posted: Mon Apr 02, 2018 9:13 am
by admin
Is this consistant? Small files are good and large files are bad? The error code is not related to the size in any way but rather how FFAStrans enumerates the %s_original-path~n% variable. So the size issue is a bit puzzeling. Anyway, I have taken measures to fix the error. I will send you a private patch so that you can test.

-steinar