FFAStrans forum

It seems that the P2 detection is broken with the latest 0.9.0.4 version.
I tried to copy the "CONTENTS" folder and nothing happens.
It seems that the program detects the folder, as it says that it's opened in the program if I try to move it, but the transcode doesn't start.
Nothing useful in the logs.
I also tried to update ffmpeg builds with the very latest ones (x86 and x64) but nothing changed.
Could you look into it?
Do you use special ffmpeg builds or can I compile them myself enabling avisynth?
Thank you in advance.

Thanks for reporting, I'll take a look at it. The ffmpeg-build shiped with FFAStrans are the "official" Zeranoe builds. Nothing special. https://ffmpeg.zeranoe.com/builds.
You can of course build your own versions if you have special requirements, but if something breaks, it's not FFAStrans fault

-steinar

Just as a quick reminder: we do have the same problem. Occurs in 0.9.0.2 and above.

The issue has been fixed in the upcoming 0.9.1 version. Stay tuned

-steinar

Perfect! I look forward for it to be released!

so, P2 now works a again - except in combination with the h264-node. Then we get "encoding failed - no moov atom found. File might be corrupt!" With other nodes f.ex. the custom ffmpeg node it works flawlessly.

Do you get this message prior to or after 264-encoding? I.e., does encoding start at all?

-steinar

it seems to start working and abort in the middle of the way

novalis wrote: ↑Wed May 30, 2018 9:16 am it seems to start working and abort in the middle of the way

That's weird. It's probably ffmpeg.
I think that adding an AV Media node between the P2 monitor and the encoder node might temporary solve the issue (as workaround).

Have you chosen MOV as P2-wrapper or MOV in the 264 encoder?

-steinar