Is it feasible to add support for a custom audio codec that isn't supported by the browser?

[inkychris]

I have a custom audio codec that I've got working with a modified version of shaka-packager and custom gstreamer plugin to facilitate adaptive streaming, but I'd like to be able to get it working in browser too. I was wondering if it was feasible to extend dash.js to facilitate transcoding the audio to wav before sending the audio downstream? This could be either in memory or even just transcoding segments to disk. I'm imagining using Web Assembly for the actual decoder but want to make sure I can process the data between downloading segments and presenting it to the browser in some capacity before attempting a WASM decoder implementation.

I don't know if having some kind of plugin mechanism in dash.js would be a useful feature to make it easier to support/test new DASH codecs in a browser?

[dsilhavy]

I think this goes in a similar direction as #4374. You will need to transcode the audio to a supported audio codec and put it into an ISOBMFF container. Then it can be appended to the MSE.

There is no such mechanism in dash.js yet. However there is a conversion from MSS to DASH. That is operating on a container level. From what I remember it is .piff to .mp4.

[inkychris]

Cool, sounds like I'm on the right track then. Useful to know that I need to use an ISOBMFF container. I was attempting to switch it to a raw audio/wav mime type but didn't get very far and the way I was doing that seemed more applicable to an ISOBMFF container with the mime-type;codecs= format that seemed to be required.