-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add DASH support back in #1
Comments
Thanks David! So I should compile this (your) branch, right? Already started compiling and it seems to be going all good! Just typed "make"! |
Arrived to the first error: |
Are you compiling with separate emsdk? https://emscripten.org/docs/getting_started/downloads.html Another way would be to use the Docker image - see https://emscripten.org/docs/getting_started/downloads.html but use |
@rafael2k by the way, the example is now up: https://github.com/davedoesdev/streamana |
@davedoesdev, I'm compiling with stock versions from Debian 11 repository. |
Cool, thanks! I'll try with the binaries for now. |
OK cool. The stock version from Debian is probably behind quite a bit. emsdk comes with it's own version of Node, for instance. |
I'll think about how best to put dash in |
Yay! I'll update just my node and see if compilation finishes (or try to patch the source). |
@rafael2k how are you testing DASH ingestion? Is there an open source server I can test against? |
In my current DASH workflow I contribute (upload) the live stream to icecast2, then I make ffmpeg connect to it and create the DASH manifest and files on the fly. |
Hmm, at the moment I've only tested streaming the generated DASH files to an ingestion URL (like YouTube). |
I suppose if you had a local web server which accepted POST (or PUT) of the generated DASH files then that might work? |
I'll have a look at setting one up locally when I get time. |
Btw, I merged DASH support into master and streamana I'll need to test it by ingesting it into a local http server and then playing out the files in a browser |
Great! Indeed, icecast2 works this way [1] - a PUT to the server. In case of DASH, I think the ingest will be similar, but instead of just one PUT, it will be one PUT per chunk, I think. |
@rafael2k in your workflow, where is the desired destination of the DASH files? |
The desired destination would be a server which can later serve the encoded DASH formatted media through a webserver. But I'm not totally sure yet. The "push" protocol can be REST based, or not. A simple network socket pushing the media to the server would be enough already. |
@rafael2k this is now in the UI. You can select DASH or HLS, POST or PUT and the CORS mode. I tested it PUTting to a local Apache server which I enabled WebDAV on and it worked fine - I could stream the DASH files into a |
This is wonderful David. I'll test soon. Cheers! |
@rafael2k how did you get on? |
See early commits on Kagami#166
The text was updated successfully, but these errors were encountered: