FFAStrans forum

Hi all

I have an issue with the DNxHR encoder when trying to use the "create Avid project structure" option. If I try to use this in a workflow, then only audio is encoded. I don't think I'm doing anything wrong as if I switch the DNxHR encoder out for a standard DNxHD, then all is good.

As an aside, I'm also getting an error when trying to read log files - I use Notepad ++ to read .json files, but I can't get FFASTtrans to use it as mt .json viewer.

Any help appreciated.

Thanks

Hi encodermonkey,

Besides your very cool alias, you're right about the DNxHR issues regarding Avid project structure. And it's a bit embarrassing because this node should have gotten more attention prior to release. As it is now creating Avid project simply don't work and it might be an option to temporarily disable it in the next update until we get it sorted out. However, the solution is not that simple i'm afraid and it might take a while before we get the Avid function working in this node.

Anyway, thanks for notifying and sorry about the "mess"!

-steinar

Thanks for confirming Steinar. It's rather unfortunate as my entire workflow is based on the DNxHR encoder. Any idea how long this may take to address? Will creating a custom FFmpeg node do the job? If so, could you point me in the direction of what the command syntax is for making an Avid project structure output would look like?

Thanks

I'm sorry, but I have to dig a bit deeper into the issue. FFAStrans use the BBC BMX to create the Avid files and there was work going on to implement DNxHR support. When creating the node (a year ago) I was hoping they would be finished in time but that never happened.
Afaik, creating Avid-compatible files directly in ffmpeg was not possible last time I checked. But that might also have changed for all I know. But the amount of work and time spent rewriting most of FFAStrans left little time to polish and quality-prove the DNxHR node. Avid-support GUI should have been disabled/removed in the final 1.0.0 release but I wanted to get the node out for the release. In the mean time, creating straight DNxHR in MXF still works though.

-steinar