Roadblock in implementing Adaptive Streaming

[n-ce]

So, in dealing with #158 & fully supporting streaming through the Piped API, I learned a few things.
In my experience, The Piped API always returns HLS data, while dash would always be null.

This means I pivot naturally towards bringing support for HLS streams.
This gives me two options :

• The hls.js library
• The ShakaPlayer library

On Testing the hls.js demo using a hls manifest from a piped stream I found out that the library does not detect opus streams, which is also documented in this issue.

For reference, here's ytify playing the same id through the invidious api on static streaming with opus support

This is a major issue since our project is Opus first which makes me worried if I have to drop support for opus streams in order to support adaptive streaming.

Therefore I'm opening up to community suggestions.

[n-ce]

After having learned more,
I realized piped never did provide a dash manifest, it creates one using dashUtils.js

For reference however I will use dash.js from the Hyperpipe project which suits our use case.

It is also to be noted that invidious does provide a dash manifest in their videos endpoint or directly accessible through /api/manifest/dash/id/:id but that would mean I have to keep support for the invidious api just for this.
There are some things the piped api does better, such as audio languages & ttml availability so it's a worthy tradeoff.

This means now I have to support dash streaming for which I can use

• the dash.js library
• the shakaPlayer library

Thankfully dash embraces opus so there's no such conflicts we previously encountered.