Closed GrzeWier closed 2 years ago
Fixed by be590646
Yes it is fixed, thanks
Sent from mobile
On Thu, 20 Jan 2022, 21:51 jcdr428, @.***> wrote:
@GrzeWier https://github.com/GrzeWier please try this fix https://github.com/jcdr428/tsMuxer/suites/5006139587/artifacts/146949189 and confirm it works as expected.
— Reply to this email directly, view it on GitHub https://github.com/justdan96/tsMuxer/issues/540#issuecomment-1017917124, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXD5PJ5GXYQNAHMWH4532W3UXBYWFANCNFSM5LTWSKPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
Hi When opening in the GUI some files with Dolby TrueHD audio report "track unknown" error. Any such file is fine (it plays in all common media players) and can be processed in other AV tools (like eac3to, MKVToolnix, ffmpeg) without issues. One thing in common for all such cases seems to be: there is no core AC3 track inside the TrueHD track.
Sample of such file: https://www.demolandia.net/downloads.html?id=48882118