Hi,
First of all, thank you for maintaining AudioStreaming.
I'm evaluating AudioStreaming for an iOS internet radio application and I have a question regarding authenticated streams.
Does AudioStreaming currently support setting custom HTTP headers when opening a remote audio stream?
For example, I need to send headers such as:
- Authorization: Bearer
- X-API-Key:
- X-Device-Id:
Ideally something along the lines of:
player.play(url: streamURL, headers: [
"Authorization": "Bearer ...",
"X-Device-Id": "..."
])
If this is not currently supported:
- Is there an existing workaround?
- Would you consider adding support for custom request headers?
- Which part of the codebase would need to be extended to implement this feature?
My use case is authenticated internet radio streams where the backend requires custom headers on every request.
And one last question if possible. Does AudioStreaming expose decoded PCM samples or AVAudioPCMBuffer frames that can be used to build a real-time visualizer/FFT spectrum analyzer?
Thank you.
Hi,
First of all, thank you for maintaining AudioStreaming.
I'm evaluating AudioStreaming for an iOS internet radio application and I have a question regarding authenticated streams.
Does AudioStreaming currently support setting custom HTTP headers when opening a remote audio stream?
For example, I need to send headers such as:
Ideally something along the lines of:
If this is not currently supported:
My use case is authenticated internet radio streams where the backend requires custom headers on every request.
And one last question if possible. Does AudioStreaming expose decoded PCM samples or AVAudioPCMBuffer frames that can be used to build a real-time visualizer/FFT spectrum analyzer?
Thank you.