Use Shaka CEA parser for TS

[avelad]

Have you read the FAQ and checked for duplicate open issues? YES

Is your feature request related to a problem? Please describe.

Right now there is the forceTransmuxTS setting to parse CEA-608 on devices that natively support TS, but this involves using mux.js and transmuxing TS to MP4.

Describe the solution you'd like

Since we have a CEA-608 parser for MP4, the idea would be to extend it to support TS.

Describe alternatives you've considered

Leave current behavior

[avelad]

Note: there is native TS on Edge, Xbox, and Chromecast.

[avelad]

With 8a3bed7 I think it would be good to remove this dependency. @theodab what do you think?

[theodab]

It sounds reasonable as a feature. I'm not sure if we could justify getting rid of mux.js support altogether, but extending the CEA-608 parser to not require the intermediary step of turning TS into MP4 would be nice performance-wise.

I don't think this is something the Google Cast team is interested in, though, so I wouldn't expect us to get around to it anytime soon. I'll mark this as seeking PRs for now.

[avelad]

@theodab Do you know if the Cast team wants only DASH or is also interested in migrating and using ShakaPlayer for HLS as well?

[joeyparrish]

We would like to use Shaka for HLS, and TS in HLS isn't going away any time soon. (Though it saddens me to admit it.) So yes, we should extend the CEA parser to support TS and drop this flag.

[joeyparrish]

Looking at this again, forceTransmuxTS isn't only useful for CEA. It's also useful for working around broken platforms.

So long as we have transmuxing with mux.js, I think we should give apps the option to force us to transmux TS, even when the platform claims to support it.

But I'm still in favor of using our native CEA parser for TS as soon as we can.