arcodange/mediabunny
1
0
Fork 0
mirror of https://github.com/arcodange-org/mediabunny.git synced 2026-09-27 19:03:46 +02:00
Code Issues Packages Projects Releases Wiki Activity

Remove createInputFrom, changed meaning of PathedSource, add CustomPathedSource

Browse Source
This commit is contained in:
Vanilagy
2026-04-21 13:22:10 +02:00
parent d12c48562c
commit 2b3e5f45c6
16 changed files with 349 additions and 428 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guide/reading-hls.md
+4 -17
View File
@@ -8,30 +8,17 @@ Mediabunny exposes HLS playlists as if they were a single giant input file. Like
## HLS inputs
HLS playlists (master & media) are read through the same `Input` interface as all other media files in Mediabunny. The difference is that HLS uses multiple files, meaning a `PathedSource` is required:
HLS playlists (master & media) are read through the same `Input` interface as all other media files in Mediabunny. HLS must read multiple files, meaning any [`PathedSource`](../api/PathedSource) is required:
```ts
import { Input, PathedSource, HLS_FORMATS } from 'mediabunny';
import { Input, UrlSource, HLS_FORMATS } from 'mediabunny';
const input = new Input({
source: new PathedSource(
'https://example.com/master.m3u8', // The path to the entry file
({ path }) => new UrlSource(path),
),
source: new UrlSource('https://example.com/master.m3u8'),
formats: HLS_FORMATS, // HLS_FORMATS includes HLS as well as the commonly-used segment formats
});
```
The `PathedSource` requires that you return a [`Source`](../api/Source) for every file (identified by a [path](../api/FilePath)) that Mediabunny wants to read.
Since this pattern is common and kind of cumbersome to write, there exists a shortcut:
```ts
// From a URL:
const input = createInputFrom('https://example.com/master.m3u8', HLS_FORMATS);
// From a file (server-side environment):
const input = createInputFrom('/path/to/master.m3u8', HLS_FORMATS);
```
However, the `PathedSource` variant is still useful for custom sources; maybe your HLS files don't reside behind a URL but you have them in memory, or in IndexedDB. In this case, there's no way around `PathedSource`, since you'll need to supply your own "path to data" function.
You can supply any custom "path to data" resolution logic by using [`CustomPathedSource`](../api/CustomPathedSource).
## Reading tracks