Closed Randrianasulu closed 2 years ago
@Randrianasulu the lpcm frame size in the first m2ts lpcm header is incorrect: it is 2008 bytes, whereas it shoud be 960. Only the following values are permitted:
fixed in ffmpeg git... sorry, really not your bug
@Randrianasulu so no more issue in tsMuxer with the commit in ffmpeg.git ?
yeah, it works - tsmuxer recognizes stream and xine can play (renamed) iso...
On Sunday, April 24, 2022, jcdr428 @.***> wrote:
@Randrianasulu https://github.com/Randrianasulu so no more issue in tsMuxer with the commit in ffmpeg.git ?
— Reply to this email directly, view it on GitHub https://github.com/justdan96/tsMuxer/issues/580#issuecomment-1107863683, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJSS7TOV4FMCJAYNN5INIYLVGVLCBANCNFSM5UF6NKTQ . You are receiving this because you were mentioned.Message ID: @.***>
interesting enough encoding sample with ffmpeg git result in same overflow....
sample:
wget -c http://streams.videolan.org/issues/8526/00064.m2ts
ffmpeg command
/home/guest/ffmpeg/ffmpeg -i 00064.m2ts -c:v copy -c:a pcm_bluray -mpegts_m2ts_mode 1 00064-1.m2ts
On Friday, April 29, 2022, Valerii Zapodovnikov @.***> wrote:
See @.*** https://github.com/FFmpeg/FFmpeg/commit/058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4
— Reply to this email directly, view it on GitHub https://github.com/justdan96/tsMuxer/issues/580#issuecomment-1112747654, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJSS7TMMFO4HEGPORGJTIE3VHMOB5ANCNFSM5UF6NKTQ . You are receiving this because you were mentioned.Message ID: @.***>
https://cloud.mail.ru/public/jjGj/orJY9VFwM
~18 mb sample I made with (hacked) ffmpeg 4.4 with backported bluray-pcm encoder from ffmpeg git.
May be I did it wrong, but at least mplayer plays it...