Custom FFmpeg Encoding Error - Unsupported input (Error number -129 occurred)

[SheldonABS]

Hi Team,

Happy new year!

I currently have workflow setup that uses a Custom FFmpeg Encoder to convert video files into an MP4 format with the options in the screenshot attached. When using MP4 files as the input for this workflow, I noticed that random files are getting hit with the following error once it goes through the Custom FFmpeg:

Encoding: Unsupported input (Error number -129 occurred): fmt:yuv420p csp:bt709 prim:reserved trc:reserved -> fmt:yuv420p csp:bt709 prim:reserved trc:reserved.

I've attached a screenshot of the workflow; For reference, the Populate variables node just grabs the duration of the input file and assigns it to a variable then the conditional just checks the variable matches the source file duration. Everything else is just moving the encoded file and source file to different folders. I'm also on version 1.4.1.

Currently also troubleshooting to figure out the issue but I thought to also post it up here in case anyone can help find the solution quicker.

Thanks!

[FranceBB]

Could very well be an issue with the frame properties of the input. Have you tried putting an A/V Decoder node in front to the have Avisynth indexing and passing the uncompressed A/V Stream living in RAM to NVEnc?

[SheldonABS]

I have not tried this no. I'll give it a try shortly and get back to you. Thanks for the quick suggestion!

[emcodem]

Wait a moment, that error msg does not look like an ffmpeg error msg but more like something from ffastrans internally. i'd suggest using commandline executor instead of custom ffmpeg.

[SheldonABS]

Hi Team,

Apologies for the late reply.

For an update, adding the A/V decoder did seem to resolve the issue I was having and everything has been working fine since. If the issue does come up again I'll try using commandline executor as an alternative solution but for now, all is good!

Thanks for the help!

[FranceBB]

I'm glad to hear that.
Avisynth saves the day once again

[baev12]

Hi, all!
Got the same issue with Custom FFmpeg Encoding with all parametrs in FFmpeg option field and empty videocodec field etc.
Solution was the same - put the A/V decoder before Custom FFmpeg Encoding. I think NVEnc does not understand something without...

Thanks for the software, Team!

[FranceBB]

Yeah, in general it's always nice to have the indexing in front as it means that the encoder downstream gets an uncompressed A/V stream directly from the frameserver (Avisynth) which takes care of several things including tackling problems within the container of the source or dynamically changing frame properties and other things.

Avisynth to the rescue once again.

[emcodem]

Just guessing but the nvenc encoders or better all the pipeline stuff around it is often not able to auto insert the needed pix_fmt conversion.
Usually i do insert the corresponding conversion filters in ffmpeg before the encoding happens, e.g. -vf format=yuv422p for studio codecs on 50xx cards or -vf format=nv12 for distribution encoding 4:2:0

[FranceBB]

sure, but it would still not protect you from dynamically changing frame properties without specifying -reinit_filter 0 which is what is likely at stake here. The reason why I say this is that even when adding an A/V decoder, it will still index the source and deliver the same pixel format as the source. What it will however do is stabilize the frame properties.