13.11.2023, 23:49
(13.11.2023, 21:48)Selur Wrote:Quote:have you looked at the 3rd debug i have postedno, since it wasn't there when I looked at the post.
it uses:
At the time of me adding the 3rd debug soon after, the DL counter wos still at 0
So, this ducks logic dictates, 0 DL Equals= 0 Post read throughs ..
Hence, my question..
(13.11.2023, 21:48)Selur Wrote:for the muxing, so the same as the tsMuxeR->tsMuxeR call from before.MUXOPT --no-pcr-on-video-pid --new-audio-pes --vbr --vbv-len=500
V_MPEG4/ISO/AVC, "F:\Temp-\00246.track_4113_2023-11-13@19_29_44_4210_06.264", fps=23.976, insertSEI, contSPS, ar=1:1 (Square)
A_MLP, "F:\Temp-\iId_2_lang_en_aid_4352._2023-11-13@19_29_44_4210_04.thd", lang=eng
We will see, if the meta data tsMuxeR GUI uses differs from what Hybrid uses for the files, I might be able to adjust Hybrid to it.
Quote:And, you have to change / uncheck a few settings to get only TSmux to work through the process from A to Z you know..yes, if you don't like the defaults adjust them,...
Cu Selur
You don't say .. 0^0
Anyway, are you ready for this Sir.Selur.? Becaue this might confuse you!
but at the same time not.. and i guess your suspicions are correct. i.e: → The wrong Calls !
So i did created the raw files as suggested and compared the meta files creatted through hybrid, and afterwards the meta info created by tsmux gui..
And here's the confusing part..
the ffmpeg process through hybrid uses : A_MLP ... but get this... when i load the raw track in Tsmuxgui: it reports as A_AC 3 !!
Now as for tsmuxer .. the meta file created through hybrid reports A_AC3 and in Tsmuxgui A_AC3 aswell .. BUTTT....
Creating the Raw files using tsmux in hybrid resulted in CRASH !..
So yes, to me this looks more like an extraction issue than anything else !
And most important .. A_MLP seems to be the way .. ^_^ After all MLP is what media info reads from the source aswell in the first place selur..
cheers,