-
Notifications
You must be signed in to change notification settings - Fork 10
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
ROUTE support using GPAC #18
base: development
Are you sure you want to change the base?
Conversation
Hi - just noticed your pull request, great to see that you already started with the integration! I've just commited the code for seamless switching (see #19). The location for the libflute calls has moved into ContentStream. I quite like your idea of using a lib-agnostic interface to handle file reception, I guess we could and should adapt the new classes accordingly as well. |
Hi Klaus, thanks for the feedback. I've just pushed a MVP. To test the implementation:
I have the following local patch:
Note that GPAC could have exposed the content directly using its HTTP embedded server. It allows to have low latency DASH(/HLS) ; otherwise if the HTTP server encounters the end of a served file it has no way to know if it is still being populated. But as per the discussion we had with the group I plugged on a lower level GPAC API. |
As just discussed with Romain, I will test this and rebase it into the seamless-switching branch |
I've just had a look at the GPAC files we need to add at link time for a minimal link (see here):
|
Work in progress. See #16. I put it here to get early feedback if any.
TODO: