> Just checked at least for RP: the protocol handler of RP (the part of
> the plugin that tells LMS how to stream data for a given source and
> collect metadata) tells LMS that interactive streams cannot be paused,
> so LMS stops them. I vaguely remember a simialr thing for Qobuz where
> (for no good reasons AFAIR) it refuses to pause.
I think for Qobuz there was a limitation with seeking within https
streams or something, wasn't there? Something you improved at some point?
RP is different: The interactive stream is a series of blocks of tracks.
Handling these blocks is a bit complicated as a block can have many
tracks. Thus the file length has little to do with the individual track
length. And RP (at least at the time I implemented it) didn't support
seeking on their end. Therefore I didn't invest time into making it work.
> the plugin that tells LMS how to stream data for a given source and
> collect metadata) tells LMS that interactive streams cannot be paused,
> so LMS stops them. I vaguely remember a simialr thing for Qobuz where
> (for no good reasons AFAIR) it refuses to pause.
I think for Qobuz there was a limitation with seeking within https
streams or something, wasn't there? Something you improved at some point?
RP is different: The interactive stream is a series of blocks of tracks.
Handling these blocks is a bit complicated as a block can have many
tracks. Thus the file length has little to do with the individual track
length. And RP (at least at the time I implemented it) didn't support
seeking on their end. Therefore I didn't invest time into making it work.
Comment