-
Notifications
You must be signed in to change notification settings - Fork 18
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
replay stops after last segment created #5
Comments
I think I know what is causing that... give me a minute. |
This should fix it.
|
This fix solved issue above (replay stops after last segment created). THX! However there must be another thing, since the play on segments with EXT-X-DISCONTINUITY does not continue smooth. Same source file as above. Same config, just updated x9k3 version to new. Problem detected with ~seg32.ts, ...seg134.ts, seg187.ts ... When testing in browser using VideoJS 7 in Chrome on windows 10, I see some report in console of browser around segment with EXT-X_DISCONTINUITY (this is I believe where stream is restarted from beggining): and video player stops and browser is re-fetching same segments a few time (in should normally just move on) then stops. |
Is that with the longb.ts video? |
yes, longb.ts |
Dude, that's just some random on my server, I would not use that for any kind of testing. When I get some time I will look at the discontinuity issue. |
I double reset the stream when I fixed the loop, wait 10 mins and run pip again. If you are using something with a big GOP like that , you can adjust the seconds with the -t switch and target duration is hard to predict, longb is a kick ass video though, I ride longboards. |
When running x9k3 with "replay" x9k3 stops on last segment and does not anymore update index file, or write new segment .ts files.
If I fully understand --replay it should keep "faking" continous live stream with updated index.m3u8 and (?maybe) new created .ts files. Everything seems OK until last segment.
x9k3 started with:
x9k3 -i longb.ts --replay
No sidecar / scte35 injection or anything similar was used.
Used version:
After some time (approxy 150 seconds) last index.m3u8 was created:
This fill remained static after that - no further changes occured to index.m3u8.
This are last moments of x9k3 (I waited until index.m3u8 stopped changing, then after a few seconds I pressed CTRL-C)
input stream file used was taken from slo.me....
The text was updated successfully, but these errors were encountered: