You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a while and at the moment (Shutter Encoder 16.8), I get the wrong video levels resulting in a low contrast picture when converting from MXF OP1a / AVC-Intra 100 to MP4 / H.264. (Tested on macOS and Windows.)
As a workaround, I can use "Colorimetry / Covert levels: 16-235 > 0-255" to force the correct levels, but it used to work automatically.
I could narrow down the issue to the version change from 16.0 to 16.1 (16.0 still produces the desired result). It seems like with this version change, a different build of the ffmpeg suite has been introduced (version details below).
When I drop the ffmpeg files and associated dylib from 16.0 into the 16.8 application bundle on macOS (/Applications/Shutter Encoder.app/Contents/Resources/Library), I get the desired result again. So I suspect the specific ffmpeg version.
This issue is still present with the new ffmpeg version shipped with 17.0.
ischeriad
changed the title
Wrong video levels when converting AVC-Intra to H.264
[bug] Wrong video levels when converting AVC-Intra to H.264
Jul 21, 2023
For a while and at the moment (Shutter Encoder 16.8), I get the wrong video levels resulting in a low contrast picture when converting from MXF OP1a / AVC-Intra 100 to MP4 / H.264. (Tested on macOS and Windows.)
As a workaround, I can use "Colorimetry / Covert levels: 16-235 > 0-255" to force the correct levels, but it used to work automatically.
I could narrow down the issue to the version change from 16.0 to 16.1 (16.0 still produces the desired result). It seems like with this version change, a different build of the ffmpeg suite has been introduced (version details below).
When I drop the ffmpeg files and associated dylib from 16.0 into the 16.8 application bundle on macOS (/Applications/Shutter Encoder.app/Contents/Resources/Library), I get the desired result again. So I suspect the specific ffmpeg version.
ffmpeg in version 16.0:
ffmpeg in versions 16.1 and up:
The text was updated successfully, but these errors were encountered: