-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
update of live manifest with large timeShiftBufferDepth is slow #288
Comments
Update, v.1.6.2 doesn't have this issue. |
@peyoh, can you please clarify what you mean when you say that the video "squeezes"? I'm not familiar with that term in this context. |
Sorry for this "term" :), |
@joeyparrish. With larger timeshifts it seems .MPD parsing speed is greatly affected by SegmentTemplate startNumber="17650" parameter:
As the time goes on, this number increments and the interface starts to be insensitive But with 1.6.3 even with small timeshift, I'm unable to play video. Seems like manifest ubdate REALLY gets too much time. |
To address one issue: your |
@joeyparrish With timeshiftbufferdepth of 3600 sec, both versions works well.
Thank you. BRS/ |
Could be a regression, then. We'll look into it for v1.6.4. |
Adding assertion messages when missing was slowing down the code because of the repeated throwing at catching of exceptions. Now only add a stack trace if the assertion will fail. Issue #288 Change-Id: Ic4ec3180df0178f1e3e0b25534d9e5bb018707a4
@peyoh This should be fixed now. Please try again with the latest from |
Hello, BRS |
Great! We'll roll this out in v1.6.4. |
Hello,
today I clone the latest player.
( Fri Feb 12, 2016)
With attached mpd (502_24h.mpd
501_24h.zip
)
Chrome gets 100% CPU and the tab with player becomes heavly unresponseable. The video "squeezes" also. Debug log shows:
mediakeys.js:48 Using native EME as-is.
2player.js:191 + video/mp4; codecs="avc1.4d001f" is supported
2player.js:191 + video/mp4; codecs="avc1.4d001e" is supported
player.js:191 + audio/mp4; codecs="mp4a.40.2" is supported
player.js:191 + video/mp4; codecs="avc1.4d001e" is supported
player.js:191 + audio/mp4; codecs="mp4a.40.2" is supported
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 6759155760, duration: 900480, repeat: 298}
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 7028410800, duration: 900480, repeat: 909}
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 7847978160, duration: 900480, repeat: 857}
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 8620605360, duration: 900480, repeat: 2149}
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 10556641200, duration: 900480, repeat: 2494}
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 12803446320, duration: 900480, repeat: 289}
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 13064598960, duration: 900480, repeat: 466}
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 13485138480, duration: 900480, repeat: 200}
mpd_utils.js:275 SegmentTimeline contains a large gap/overlap. The content may have errors in it. s…a.d…h.mpd.SegmentTimePoint {startTime: 13666150320, duration: 900480, repeat: 446}
live_segment_index.js:240 @availabilityStartTime seems to be inaccurate; some segments
But with shaka-player version from Nov 18 2015,
the same MPD works fine, even the same warnings occurs.
I'm using edash-packager as packetizer.
Please tell me what environment to arrange for debugging.
BRS
The text was updated successfully, but these errors were encountered: