Problems with old TV - Can I decode a new file and re-encode to an older version of a codec?
Five years ago, I've bought an inexpensive Samsung TV (ue55nu7099) and I'm using it to watch from minidlna server. I'm not very happy with the firmware player, but it's bearable and I don't want to use an external player. The TV can access the local network but is blocked from internet access. From the beginning, the TV was very picky about the encoding of media files but I found out, that I can make just any file playable when I re-encode it with this command:
ffmpeg -i INPUT.mkv -c:v h264 -pix_fmt yuv420p -c:a ac3 OUTPUT.mkv
This stopped working a few weeks back. The TV started to skip frames and sometimes even froze without being able to recover. I was able to solve that by installing an older static version of ffmpeg.
/usr/local/bin/ffmpeg-6.0-amd64-static/ffmpeg -i INPUT.mkv -c:v h264 -pix_fmt yuv420p -c:a ac3 OUTPUT.mkv
Again, it's working perfect when I'm re-encoding any file that isn't too new. I am still having some (less severe) problems with some very new files. I am not sure, but I suspect that this older version of ffmpeg can't decode those new files perfectly. Is it possible to use an updated and new version of ffmpeg for decoding a media file and then re-encoding it with an older version of the codecs, so that my TV can handle it?
Am 31.05.24 um 14:42 schrieb bbb:
Five years ago, I've bought an inexpensive Samsung TV (ue55nu7099) and I'm using it to watch from minidlna server. I'm not very happy with the firmware player, but it's bearable and I don't want to use an external player. The TV can access the local network but is blocked from internet access.
From the beginning, the TV was very picky about the encoding of media files but I found out, that I can make just any file playable when I re-encode it with this command:
ffmpeg -i INPUT.mkv -c:v h264 -pix_fmt yuv420p -c:a ac3 OUTPUT.mkv
This stopped working a few weeks back. The TV started to skip frames and sometimes even froze without being able to recover. I was able to solve that by installing an older static version of ffmpeg.
your command is very unspecific to begin with even profile is missing https://trac.ffmpeg.org/wiki/Encode/H.264
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@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@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). 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)
Compare encoder settings between files encoded with different versions.
On 5/31/24 16:39, Paul B Mahol wrote:
Compare encoder settings between files encoded with different versions. _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
It seems of all the files I've checked so far, The files that are causing problems have settings like this:
Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
While the file that are running just fine, all seem to have the setting this:
Stream #0:0: Video: h264 (High), yuv420p(progressive), 1912x1032 [SAR 1:1 DAR 239:129], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
Is there a way to ensure "yuv420p(progressive)" without "tv" and "bt709"?
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@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@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
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@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@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@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@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.
On Fri, May 31, 2024 at 5:18 PM bbb <ffmpeg-user@bugblatterbeast.de> wrote:
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@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@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@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@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.
That have nothing to do with encoder settings.
_______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
participants (3)
-
bbb -
Paul B Mahol -
Reindl Harald