You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2019. It is now read-only.
I would like to eliminate the small blip between two MP3's streamed over HTTP.
My guess was that there isn't enough time for the HTTP request to load enough data between the EOF of the first source and end of playback for the first source for the second source to load data over HTTP.
Based on this hunch, I multiplied CHUNK_SIZE and BUFFER_SIZE by 4:
This gives gapless playback from cache and over HTTP. However, seek didn't seem to behave properly until I used [_player seekToTime:seekSlider.value withDataFlush:YES].
Are there any downsides to this approach?
The text was updated successfully, but these errors were encountered:
A little more, yeah. The other thing I noticed is initial playback and starting playback after seeking takes a little longer due to the increased sizes, but that is acceptable for what I need to do.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to eliminate the small blip between two MP3's streamed over HTTP.
My guess was that there isn't enough time for the HTTP request to load enough data between the EOF of the first source and end of playback for the first source for the second source to load data over HTTP.
Based on this hunch, I multiplied
CHUNK_SIZE
andBUFFER_SIZE
by4
:This gives gapless playback from cache and over HTTP. However, seek didn't seem to behave properly until I used
[_player seekToTime:seekSlider.value withDataFlush:YES]
.Are there any downsides to this approach?
The text was updated successfully, but these errors were encountered: