Comments on: Reading SHOUTcast metadata from a stream

By: mike

mike — Fri, 09 Dec 2011 14:08:50 +0000

@kamalpreet - There was an old defect in the code that caused the blip for some streams. I thought this version in Google Code was updated to fix that. Does this happen with all streams? Try a shoutcast and icecast stream and see if there is a difference. My metadata code has since been integrated into some of the forks of the official AudioStreamer github.

By: kamalpreet

kamalpreet — Mon, 05 Dec 2011 00:44:40 +0000

My bad english, It is not a blip (just read the definition of blip) but a very short distortion noise (or sometimes a tiny gap) in the music.

Sorry admin for posting 3 comments for one problem. Please forgive me

By: kamalpreet

kamalpreet — Mon, 05 Dec 2011 00:01:54 +0000

Also to confirm I notice this on the indie 103.1 and audiostreamer-meta app as well.

By: kamalpreet

kamalpreet — Sun, 04 Dec 2011 23:58:23 +0000

Hi guys,

Is it just me or is there an blip in the audio after every 20-30 seconds? I guess this happens when the metaDataUpdated method is called in the view.

Or does it just do it in the simulator? Would be great if someone could confirm. Thanks

By: zerano

zerano — Sun, 07 Nov 2010 11:45:09 +0000

Anyone managed to extract the Metadata with AS3 ?

By: mike

mike — Sat, 06 Feb 2010 21:23:41 +0000

What’s the URL of the stream you are using?

By: sj

sj — Sat, 06 Feb 2010 20:47:36 +0000

also, when it does go through and all, no skips/repeats it stops after about 10 seconds

By: sj

sj — Sat, 06 Feb 2010 20:19:36 +0000

so I am trying to use this with a shoutcast stream, and I keep getting really different/really strange results (I have been able to stream just fine with the old matt gallagher example). Some of the times this does work, I get the metadata from the stream etc, but then the audio loops through the same segment twice and ends. Other times I just get an EXC_BAD_ACCESS error in MyPacketsProc() when it tries to copy to the audio queue buffer, when this happens the metadata (if any is retrieved) is just garbled nonsense. This can take a few seconds of streaming for it to happen but it always seems to terminate with EXC_BAD_ACCESS and produced a lot of nonsense. I am using the latest release right now. Any help would be much appreciated and thank you for all of your work!!!

By: mike

mike — Mon, 31 Aug 2009 15:34:26 +0000

@Bogdan For some streams the only way I’ve gotten the bitrate is to look for “icy-br” in the response headers the same way you look for “icy-metaint”.

That would be great if you publish the code, thanks!

By: Bogdan

Bogdan — Mon, 31 Aug 2009 10:48:22 +0000

I noticed that in the latest code form Matt, he obtains the bitrate just as I was trying to. The thing is that I was trying to get the bitrate when using an AAC stream, and it seems it works only with MP3 streams.

Because I wanted to use this latest version of Matt’s, I added myself the metainfo code of yours and it works ok. I also commented the fail_with_error code when trying to read the bitrate, because when using AAC streams, the play failed.

In a week or so I will publish this code on the internet (I still need to polish it a bit – for instance, error handling), if you agree, and I will add the link here also.