-
Notifications
You must be signed in to change notification settings - Fork 60
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
Error: Invalid profile for mode 2 conversion! #112
Comments
Sure, sounds reasonable. |
I appreciate it! I made a wrapper for your cli program, which basically sends mode 2 to every input, as the RPU I want out of it, to encode to x265 with and for maximum combability, errors out if the input is already mode 2. Side note, not really related. How are you able to detect which hdr format a hevc file upon input? Mediainfo/ffprobe will not show the proper hdr format of a dolby vision input in hevc format. Only once it's wrapped into a container. |
Mode 2 now overrides back to mode 0 behaviour when used on a profile 8 RPU.
In ffmpeg 5.0, ffprobe can detect the RPUs for every frame. |
I appreciate the quick work! Thank you for the information on ffprobe. |
Input media info format: Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
If I just choose -m 2 every time, which for combability purposes, I'd want every time, I will get this error if the input is already profile 8: Error: Invalid profile for mode 2 conversion!
Is there anyway to bypass this without having to check the profile before hand?
The text was updated successfully, but these errors were encountered: