We have an HLS playback system for some media, but recently we've started to see player item's logging an error: Player item error: -15419 CoreMediaErrorDomain The operation couldn’t be completed. (CoreMediaErrorDomain error -15419.) (null) We're using 3 tracks; Media, Audio, and IFrame. It appears to happen when we're seeking. However, it appears the seek succeeds, we just don't know what is causing the error. I've looked at our Seekable and Loaded ranges and the seek times appear valid. Our initial streaming playback seems to be starting a bit slower than normal, and we're afraid we have something inconsistent within our HLS playlists. Perhaps this error can indicate something? Is it possible to find out what this error refers to? Thanks

It's been 3+ years since this thread: https://developer.apple.com/forums/thread/92119 Has there been any update to NSURLCache caching the partial data for requests? i.e. a cache sharing a non-byte range response for a data chunk that doesn't match the newer desired range? Does NSURLCache still ignore byte ranges on storage/fetching? Thanks

We're using AVPlayer to stream HLS over http/2, and noticed that while different playlists (media, audio, iframe) are downloaded in parallel to each other, all of the segment fetches within a track are performed sequentially. i.e. If we wanted to start playback part way through an HLS playlist we'd end up making 3-4 segment fetches first (MAP/init, plus initial segments, plus segment I want to play), and these were all done sequentially, blocking on each other. Is there any way to make the AVPlayer fetch all of these segments at the same time? I'm assuming if we added an offline HLS data fetcher we could come up with something, but that's a lot more involved than telling the player it can use up more data, etc. Thanks