Is the icy-metaint always found in the http headers, or could it be in the response data?
I´m asking due to some old code of mine which searches both the headers and the data, but I cannot find any stream with the icy-metaint not in the header.
icy-metaint should only ever be received in the header since it needs to be known from the start of the stream playback in order to be able then calculate when the metadata details will arrive.
-daz
I found this code on the stackoverflow also checking for the metaint in the stream itself... so it must be possible, but I cannot find such shoutcast example!
http://stackoverflow.com/questions/8621353...-in-android-2-2 (http://stackoverflow.com/questions/8621353/textview-not-updating-shoutcast-stream-metadata-in-android-2-2)
the v1 and v2 SHOUTcast DNAS only ever send it at the start of the client connection in the header information - and the source code for both versions which is open in front of my matches with that what i'd previously said.
with what you've referred to, i don't see why it attempts to look in the body of the stream unless they've come across a 3rd party DNAS which does it that way. but as i say, the official SHOUTcast DNAS do not send it in-stream.
-daz