rustyhodge
commented
2 years ago Have you done a raw packet capture to see what the triggering metadata is? Look for "StreamTitle" in the raw captured data.
You can use this script to do that (change the URL of course). Tweak max filesize to your preferences, it will depend on the stream bitrate.
#!/bin/bash
source="http://ice.somafm.com/illstreet-128-mp3"
maxseconds=60
target="streamrip-$$.mp3"
echo "statrting rip or $source to $target"
curl -s --user-agent MozillaPro --header 'Icy-MetaData:1' -m $maxseconds -i $source > $targetRun hd on that file, scroll through and you'll see something like this:
00000060 af 12 15 70 6f 07 53 74 72 65 61 6d 54 69 74 6c |...po.StreamTitl|
00000070 65 3d 27 48 75 67 6f 20 4d 6f 6e 74 65 6e 65 67 |e='Hugo Monteneg|
00000080 72 6f 20 2d 20 54 68 65 6d 65 20 46 6f 72 20 54 |ro - Theme For T|
00000090 68 72 65 65 27 3b 53 74 72 65 61 6d 55 72 6c 3d |hree';StreamUrl=|
000000a0 27 68 74 74 70 3a 2f 2f 73 6f 6d 61 66 6d 2e 63 |'http://somafm.c|
000000b0 6f 6d 2f 6c 6f 67 6f 73 2f 35 31 32 2f 69 6c 6c |om/logos/512/ill|
000000c0 73 74 72 65 65 74 35 31 32 2e 6a 70 67 27 3b 00 |street512.jpg';.|
000000d0 00 00 00 00 00 00 c7 57 a5 b1 7d 63 7f 1b d6 a3 |.......W..}c....|That way you can see if something strange is being sent to the Icecast server that's causing it trouble.
Here's a good resource on the ICY Metadata protocol: https://web.archive.org/web/20070117080413/http://www.smackfu.com/stuff/programming/shoutcast.html
doug-hoffman
karlheyes
Sending inline metadata from a client appears to be broken beginning with 2.4.0-kh11. A few instances are processed, but then it goes completely wrong:
Packet captures confirm that valid metadata is being sent at the time it breaks. The client is SDRTrunk, which works fine with icecast-2.4.4 and 2.3.2kh32.
If streaming is allowed to continue after metadata processing breaks, the daemon eventually becomes unresponsive.