-
-
Notifications
You must be signed in to change notification settings - Fork 335
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
HLS (HTTP Live Streaming) and DASH support #166
base: master
Are you sure you want to change the base?
Conversation
(exit is fired after async call so is no good)
Docker image for buliding is available as |
That's a good idea, it should be possible to postMessage it back to the
main app.
…On Wed, 10 Nov 2021 at 16:25, Banou ***@***.***> wrote:
@davedoesdev <https://github.com/davedoesdev> Is it possible to get back
the result without having it POSTed ?
e.g getting it back from the memory via some emscripten mem calls ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#166 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARYYU5N7ZFK6GKVKHJNVYLULKMHJANCNFSM5FLCSLCQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I opened an issue for this:
davedoesdev#2
…On Wed, 10 Nov 2021 at 18:48, David Halls ***@***.***> wrote:
That's a good idea, it should be possible to postMessage it back to the
main app.
On Wed, 10 Nov 2021 at 16:25, Banou ***@***.***> wrote:
> @davedoesdev <https://github.com/davedoesdev> Is it possible to get back
> the result without having it POSTed ?
> e.g getting it back from the memory via some emscripten mem calls ?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#166 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AARYYU5N7ZFK6GKVKHJNVYLULKMHJANCNFSM5FLCSLCQ>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
|
@davedoesdev Yeah i was just asking if there was a way to not POST the result buffers, but i just looked at the files you have and quickly found https://github.com/Kagami/ffmpeg.js/pull/166/files#diff-422ddc10e000c1fc59beea711ad0f2643abd420405c383c377b11227c0e58776 which i can modify to get back the array buffers without POSTing anything, so i deleted the message |
@Banou26 yes that's the file that needs modifying. If I get time I'll see about adding an option to do this. |
Upper layer can always terminate worker if it needs to exit without waiting
Also update other submodules that have newer versions available
Is this fork able to use async/await for input IO, would i be able to make similar changes in libav to get async/await working ? I've tried to use avformat demuxer/muxer with asyncify but it resulted in errors like
When used in coordination with stuff like If i had async/await working for pulling data that'd make my life and code way easier Basically any async/await in the main program(my own c++ code calling libav) loop worked fine, but if it was called from a libav callback(libav calling back my functions), async/await completly broke |
Add support for streaming (POST) via HLS and DASH.
Uses asyncify and wasm.
Also updates FFmpeg to n4.4