Open alecgorge opened 9 years ago
This seems to work really well. I presume the only noticable downside to this is OrigamiEngine uses more memory?
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.
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?