-
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
Feature request: master display & max-cll and valer auto pick and transfer #185
Comments
+1 :) |
(--master-display copy, --max-cll copy)
NVEnc 4.60 should have feature you have requested, you can specify "--master-display copy --max-cll copy" and the master display string and max-cll value will be transfered from the input file (if exists). |
Thx for the respondence,I tested the 4.60 with "--master-display copy --max-cll copy "and it's fully working! And after check with Mdiainfo,in video both have master disply luminance and max-cll it adds somthing like "maxcll_original/maxFall_oringinal" values in number(copied),in video only has master disply luminance it adds MaxCLL and Max FAL values in 10 digit numbers. Is it an original inten design? |
Ah, I see, some weird "MaxCLL/MaxFALL" seems to be added when the output format is mkv, when the video has only master display metadata (I had been testing with mp4). |
thank you |
I found a HDR video file encoded error with these option.But the file is too big i can't upload it. Error only occurs in meta-data copy encode mode and everything runs well in “hand-operated” .hevc encode mode. The error show in line "Assertion in_ts != ((int64_t)0x8000000000000000ULL) failed at libavutil/mathematics.c:171" This is the detail in video stream hope it helps: Video |
@hydra3333 Thank you for pointing out the problem, unexpected value for maxCLL/maxFALL should be fixed in NVEnc 4.61. @devil40xxx Unfortunately, I tried with several samples I have, but I'm unsuccessful in reproducing your error. Checking the source code, "Assertion in_ts..." error seems to be related with audio processing, so I'm little confused why copying master-dsiaply or light content metadata causes this error. |
cough, any time, cough (I did nothing except thank you for your great work!) |
@rigaya And I think the auido encoding is a little bit complex even for pro users. It seem like if you don't use the exact correct symbols in above 5.1 situation you may get some weird mapping result .In ffmpeg we can use something like " -map 0:1 -acodec libopus -af aformat=channel_layouts="7.1|6.1|5.1|2.0|mono" -b:a xxxk" to handle almost everything ease and safe,similar to --max-cll copy,i think if we can get an Thx for the good job, again :") |
@devil40xxx I think this is a problem caused by the insufficient handling of muxing, I have improved the handling of muxing in NVEnc 4.63, which might fix this issue. |
Use --master-display /--max-cll , options ,we can define the value when encoding HDR videos,
it 's powerful enough to finish the job.
But the fact is ,we open mediainfo or other videotools check the vale,and fill it in nvenc command line options —— and seldom change the value (we just encoding ,not adjusting) ,and have to copy the values one by one by hand (and sometime we have to double check and waste a little time).
So can it be a little easy (lazy ) way in nvenc that we could have an option something like "--transfer HDR-MD-CLL ",it can auto transfer master display string and max-cll value (in case it doesn't need change).
Thanks for the great job in this great software!!
The text was updated successfully, but these errors were encountered: