-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skipping NAL unit 63 #514
Comments
I see these same warnings with NVEncc to, I just use log level fatal on ffmpeg, and --log-level error on nvencc, for both of them I send the log to a file to prevent my screen filling with these errors. |
Hi, I am encountering this issue as well. I can make the log pretty, but my problem is, that it takes for ages to finish the ffmpeg command. I am unsure why. with the high log level I see the Skipping NAL for a very long time and then it finishes. The actual transcode is done. So if I press q for stopping ffmpeg it finishes and all is good. But for my use case pressing q is not practical. Any Idea, what I could do? (I am grasping straws, as I find nothing helpfull anywhere about this.) |
I'm not sure how I should handle this NAL unit 63, at this time just tried to avoid showing too much log messages. NVEnc 7.37 might suppress too many "Skipping NAL" messages, might help speeding up the encoding. |
The problem does not seem to be the log. It takes very long even without log messages. Not sure why. Irritating is also, that if I use dovi-tool (https://github.com/quietvoid/dovi_tool) to get the baselayer and the enhancment layer with ffmpeg filter hevc - | dovi-tool demux (well, not the exact command, but you get the point) I do not have this issue, even though it practially is doing the same thing in ffmpeg, right? |
I am trying to re-encode a 4k HDR10/Dolby Vision show.
This is the info from mediainfo:
This is the info from ffprobe:
I ran dovi_tool with -m 2 against the HEVC source. When I ran the ffmpeg encode with:
ffmpeg -i
It started screaming constantly with
Have discussed DolbyVision in general here before however any thoughts on this? Would nvenc be able to handle this with my RTX 4090 or do I need to encode without it and inject it in with dovi_tool after? Never ran into this before with ffmpeg and cpu encoding until now so apparently this source has "more" DolbyVision data then any other I've dealt with.
The text was updated successfully, but these errors were encountered: