[FFmpeg-user] Problems with old TV - Can I decode a new file and re-encode to an older version of a codec?
bbb
ffmpeg-user at bugblatterbeast.de
Fri May 31 18:18:36 EEST 2024
On 5/31/24 17:10, Reindl Harald wrote:
>
>
> Am 31.05.24 um 15:50 schrieb bbb:
>> On 5/31/24 15:16, Reindl Harald wrote:
>>> your command is very unspecific to begin with
>>> even profile is missing
>>>
>>> https://trac.ffmpeg.org/wiki/Encode/H.264
>>> _______________________________________________
>>> ffmpeg-user mailing list
>>> ffmpeg-user at ffmpeg.org
>>> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>>
>>> To unsubscribe, visit link above, or email
>>> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
>>
>> Thank you for the info and the link!
>>
>> It has been working fine so far with just that command (I can't
>> remember where I got it from)
>
> well, so it's completly random what is falling out - no codec options
> specified, no quailty options - basicaly you are telling ffmpeg "do
> whatever you want"
>
>> Seems like profile is defaulting to "high".
>>> Stream #0:0(eng): Video: h264 (High), yuv420p(tv, bt709,
>>> progressive), 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k
>>> tbn (default)
>
> which is maybe a problem - at least some years ago anything but
> baseline was a problem on many devices including iPhone
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
Yes, thanks. I didn't realise that.
My players say it's exactly the same codec and doesn't show a
difference. But when inspecting the files with ffprobe, it seems that
yuv420p(progressive) is working fine and either one or both of the
options "tv" and "bt709" seem to be causing the problems.
More information about the ffmpeg-user
mailing list