Metadata in FLAC streams

[philippe_44]

Interesting
On mp3 stream I’m seeing updates in all iOS apps I have tried, all PC apps and when played by any SB Player hardware or software. I have not tried with any Linux tools.
Pretty sure I can add an icy-metaint to the headers if it’s missing and really required but how are all of the apps / software / SB players consuming it if it’s not there?

The server should only insert icy-metaint when the client added a header request "icy-metadata" (from top of my memory). AFAIK, LMS adds that and when player is doing direct streaming, it tells the player to look for it. Squeezelite handles icy-interval and then sends back the string it receives every "icy-metaint" to LMS. In proxied, LMS does that on his own.

In summary :

- a client that can handle icy, sends a header "icy-metadata" in its GET request
- a server than can send icy adds a "icy-metaint" with the byte interval
- in the stream, every "icy-metaint", a few bytes are inserted with the updated (if any) "StreamTitle= and StreamUrl=" string.

[bpa]

Interesting
On mp3 stream I’m seeing updates in all iOS apps I have tried, all PC apps and when played by any SB Player hardware or software. I have not tried with any Linux tools.
Pretty sure I can add an icy-metaint to the headers if it’s missing and really required but how are all of the apps / software / SB players consuming it if it’s not there?

I see the change on LMS. Need to enable some logging to find out how this happens.

[d6jg]

The server should only insert icy-metaint when the client added a header request "icy-metadata" (from top of my memory). AFAIK, LMS adds that and when player is doing direct streaming, it tells the player to look for it. Squeezelite handles icy-interval and then sends back the string it receives every "icy-metaint" to LMS. In proxied, LMS does that on his own.

In summary :

- a client that can handle icy, sends a header "icy-metadata" in its GET request
- a server than can send icy adds a "icy-metaint" with the byte interval
- in the stream, every "icy-metaint", a few bytes are inserted with the updated (if any) "StreamTitle= and StreamUrl=" string.

That’s useful info. So it’s the client that says “I can consume metadata if you send it” and the server then supplies the icy-metaint if that’s the case?

What is expected in StreamURL ?

[bpa]

That’s useful info. So it’s the client that says “I can consume metadata if you send it” and the server then supplies the icy-metaint if that’s the case?

What is expected in StreamURL ?

URL for cover/track image or whatever image you like.

[d6jg]

URL for cover/track image or whatever image you like.

That’s exactly what info I was looking for. Thanks.

[bpa]

Couldn't see it I'll look more in the morning but VLC doesn't update title either, so I'm pretty sure the metadata mechanism in use now is not "normal" icy.

[bpa]

Final go - enabled player.streeaming.remote - and LMS logs all the iCY data your server is sending.

[d6jg]

Final go - enabled player.streeaming.remote - and LMS logs all the iCY data your server is sending.

Thanks
I will do that in the morning

[bpa]

Thanks
I will do that in the morning

The only I idea I have at this late hour is the metadata interval has a default value. The "StreamTitle" data seems to be very frequent in the stream - far more frequent than "normal" mp3 stream with icy data.

edit:

Adding logging into LMS and not sure why I didn't see it before but icy-metaint header is there and is set for 16384.

[20-08-26 23:43:39.4878] Slim::Player::Protocols::HTTP::parseDirectHeaders (557) Headers  [
  "Date: Wed, 26 Aug 2020 22:43:39 GMT\r\n",
  "Server: rocketstreamingserver\r\n",
  "Content-Type: audio/mpeg\r\n",
  "icy-metaint: 16384\r\n",
  "icy-br: 128\r\n",
  "ice-audio-info: ice-samplerate=44100;ice-bitrate=128;ice-channels=2\r\n",
  "icy-description: \r\n",
  "icy-genre: Mainly Rock\r\n",
  "icy-name: Juke Radio 128kbps mp3\r\n",
  "icy-pub: 1\r\n",
  "icy-samplerate: 44100\r\n",
  "icy-url: https://jukeradio.double6.net/\r\n",
  "Cache-Control: max-age=0, no-cache, no-store\r\n",
  "Pragma: no-cache\r\n",
  "Expires: Wed, 26 Aug 2020 22:43:39 GMT\r\n",
  "Access-Control-Allow-Origin: *\r\n",
  "Connection: close\r\n",
]

[d6jg]

@michael
Going back to the original point that song info from my FLAC(Ogg) stream was not being displayed in some instances I have managed to find the time to update a couple of Pi's and do some analysis.

In the attached "X" means that meta data is not updated

The problem players are

SB Touch (doh!)
iPeng
piCorePlayer but ONLY when it also the server

Unfortunately I do not have a Transporter or a Duet so can't confirm the status.

Just to restate in ALL cases mp3 metadata is fine.