Skipping NAL Unit 63

[jriker1]

I am encoding videos and when I do my dolby vision files I get the message in the subject over and over again thru the entire encode process. Basic encode commands are:

ffmpeg -i <source>.mkv -sn -an -f yuv4mpegpipe -strict -1 -pix_fmt yuv420p10le - | x265-10b - --input-depth 10 --output-depth 10 --y4m --preset slow --hdr10 --hdr10-opt --high-tier --repeat-headers --crf 19 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "1000,629" --chromaloc 2 --no-sao --range limited --keyint 24 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --dolby-vision-rpu rpu.bin --dolby-vision-profile 8.1 --vbv-bufsize 160000 --vbv-maxrate 160000 <output>.hevc

Should I just be ignoring these constant messages scrolling on the screen or is there a fix/alternative?

[microchip8]

It's harmless. ffmpeg doesn't have all DV profiles implemented in decoding, so you get that message.

[jriker1]

Thanks. I'll ignore it but since it's so pervasive on the console window scrolling thru what looks like millions of these messages, guessing it's effecting thruput.

[microchip8]

Here is the ticket to that. Might want to comment on it so it hopefully finally gets resolved.

https://trac.ffmpeg.org/ticket/5688

[rwill]

Originally Posted by jriker1

Thanks. I'll ignore it but since it's so pervasive on the console window scrolling thru what looks like millions of these messages, guessing it's effecting thruput.

It is not 'millions', it is one line per frame. A movie has what? 150k to 200k pictures if its 24 Hz?

If you are concerned about speed: pipe the stderr output from ffmpeg to a file instead of console with "2> garbage.txt" after the ffmpeg command. This should prevent a redraw of the console.

For your example this should be

ffmpeg -i <source>.mkv -sn -an -f yuv4mpegpipe -strict -1 -pix_fmt yuv420p10le - 2> garbage.txt | x265...

[benwaggoner]

Originally Posted by jriker1

Thanks. I'll ignore it but since it's so pervasive on the console window scrolling thru what looks like millions of these messages, guessing it's effecting thruput.

You're likely right on the throughput. I remember a version of PageMaker back in 90's was determined to spend 4x more time reporting on the progress of an import than it did on the import itself, as it updated the number of characters processed after every character.

[quietvoid]

Originally Posted by rwill

It is not 'millions', it is one line per frame. A movie has what? 150k to 200k pictures if its 24 Hz?

It's not one per frame, it's one per UNSPEC63 NALU.
It's a whole bitstream, so it could easily go into the millions (parameter sets, SEIs, slices) are all under that type.

That said, I doubt it has any impact on transcoding.
Even for decoding it would be negligible.

[excellentswordfight]

If you dont want it to clutter up the console just hide it with setting a less verbose loglevel (e.g -loglevel quiet)

[Balling]

Originally Posted by microchip8

It's harmless. ffmpeg doesn't have all DV profiles implemented in decoding, so you get that message.

Technically it does. Just apply the patches: https://patchwork.ffmpeg.org/project...t/?series=7164

[microchip8]

Originally Posted by Balling

Technically it does. Just apply the patches: https://patchwork.ffmpeg.org/project...t/?series=7164

They don't fix NAL 63.

[caphp]

Hi jriker1,

you can use the following parameter:

ffmpeg.exe -loglevel error -stats -i <source>.mkv <followed by your parameters...>

This suppresses the NAL Unit messages and still shows you all errors (if any occur), including ones which can be recovered.

Hope this can help you.

Bye