-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider supporting MPEG-TS streams that start/end with an incomplete TS packet #1332
Comments
The sample isn't supported because it doesn't start at a TS packet boundary, which we currently require. Note that even if we were to support starting at an arbitrary point in a TS packet, this stream wouldn't play on most Android devices, since decoder support is not required for either mp2 audio or h262 video, as are contained in this stream. See here. It's an open question whether we should support starting (and ending) at an arbitrary point in a TS packet. |
Updated the issue title to reflect the possible enhancement. |
Talking about decoders I think that this isn't a big problem, since this kind of streams (mpeg-ts/mpeg2/mp2) are mostly used in live TV streaming. And the main target devices (shield, sony, nexus) usually have decoders. Please correct me, if I'm wrong but to handle this situation It's possible to use pro-active "filter" which will try to sniff data forward to find the bound and drop all trailing bytes? |
@erdemguven - Maybe I imagined it, but I seem to remember we talked about this (or something similar) a while back. In any case, perhaps we should add support at this point (I guess it's just a relatively simple change in TsExtractor?). |
I'm also interested in this fix. mpeg2 video plays from mkv container but not from mpeg-ts. It's not really clear to me what you mean with 'TS boundary' and 'incomplete TS packet'. |
…r lost sync. Issue: #1332 Issue: #1101 Issue: #1083 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=125659191
I'd like to confirm that adc7ece (applied to dev-v1) fixes the issue. Thank You |
Stream info
The text was updated successfully, but these errors were encountered: