ryanheise

Since it hasn't already been mentioned above, another solution aside from writing the audio to a file is to define your own subclass of `StreamAudioSource` that returns the audio data...

It is the native level player that actually makes the requests, and its first request is also going to be a normal request assuming the server doesn't support range requests....

> If I understand correctly, you are basically saying to return a `Stream` that currently contains No, a stream doesn't "currently contain" anything, a stream supplies data at the rate...

I don't have windows and can't test it, but regarding the source/content length I can just say that `StreamAudioResponse` follows the HTTP standard for range requests. Are you familiar with...

Just to check again, are you familiar with how range requests work? You'll need to share all parts of the range request header and all parts of the response header...

`StreamAudioResponse` implements the HTTP range request protocol. It feeds through just_audio's HTTP proxy. `StreamAudioSource` feeds through just_audio's HTTP proxy. Since this feature works through the HTTP proxy, it's all based...

> From what I found, a client can check if a server supports range requests using a HEAD request. Is such a HEAD request being sent and processed behind the...

You can print out the parameters to see the values that correspond to the request header, and you can print out the parameters in the response object to see the...

> Note that if I set `rangeRequestsSupported: true` in the response, the exact same output is logged and the same behavior is observed. No failed assertion is reported. `rangeRequestsSupported` is...

Actually, this discussion is probably a bit off-topic for this issue. The purpose of this issue is to be able to play an audio asset that CAN fit in memory,...