SHOUTcast problems.

[Killzone_Kid]

Please stop breaking the service. Every time I switch it on (and I don't even use it this often) something always fails. Today everything fails, the search the playback the genres. Many stations have 1-3 listeners max!

[dotme]

You ever tried working on your car while someone's driving it down the street?

Doesn't usually end well. The YP is in a state of disrepair, and fixing issues sometimes involves temporarily taking functions offline.

http://forums.winamp.com/forumdisplay.php?f=86

[DrO]

Killzone_Kid: no one is intentionally trying to break the service, especially those of us who've been up since silly o'clock trying to rectify the issues with the system.

like dotme's comment, a lot of systems have kept trying to connect to the system when it's not in a valid state but killing everything causes more issues so it's trying to disable parts with as little impact as possible to get things fixed to then re-enable them.

we can only apologise but no one has purposefully tried to do this - no one wants it going wrong.

-daz

[Killzone_Kid]

Originally Posted by dotme

You ever tried working on your car while someone's driving it down the street?

[ramani]

thanks dotme and DrO for the latest updates.
eagerly awaiting full resumption of service.
SHOUTcast service was really fantastic,can't be without it.
thanks.

[DrO]

it should pretty much be working ok now (famous last words).

if that is not the case then is there something explicitly that isn't working which you can point us to have a look at to also see if it fails or not?

-daz

[ramani]

Thank u very much for the reply and just now checked and it's not ok as of now.
by the way i am accessing the shoutcast service via playon hd2 HDD media player.
Till the interruption of service it was ok.
as pointed out by many others,the search functions and genres are void of data.
this is just for information only
thanks and regards

[DrO]

as long as the main site is working then that's the key aim at the moment. if your using SHOUTcast via in-app stuff, then it is likely that things will be behind / providing stale or missing results though by now most of the backend should have caught up and be providing things nicely.

i can only view a few things overall and from what i've seen, they all are reporting things are ok.

-daz

[ramani]

thanks DrO,
As you have pointed out, the in-app shoutcast services are yet to be ok. also i have checked up with the iphone app, "VU RADIO" and it's only a shoutcast supported application too.
so i'll wait and see how it's going to be.
thanks and best regards.

[Nick_G]

Hmmm.

Still stalling on the 'Search by Type' starting with AAC+ streams. So it looks like this bug hasn't been totally squashed yet, although it has been better than recently.

[DrO]

i updated the status thread a few minutes ago - basically anything to do with api.shoutcast.com (as most in-app stuff uses) isn't working correctly at the moment (basically no data is available to it), so things are running, just firing blanks. otherwise yp.shoutcast.com and shoutcast.com are working correctly to my knowledge.

-daz

[ramani]

thanks DrO,just now the service is back again,with the search functions and genres updates
functioning as it should be and the stream playback as normal.
checked this in two or three different in-app programmes embedded in different platforms.
thanking for the great support,
best wishes and regards.

[DrO]

a fix was deployed a few hours back which seems to have resolved the app issue i.e. anything using api.shoutcast.com for things.

-daz

[radiorack]

SHOUTcast is a JOKE! Is there some other service?

[radiorack]

Originally Posted by DrO

a fix was deployed a few hours back which seems to have resolved the app issue i.e. anything using api.shoutcast.com for things.

-daz

Shoutcast had it soooo cool before

[Killzone_Kid]

Originally Posted by radiorack

SHOUTcast is a JOKE! Is there some other service?

Not that provides slick API and is as popular.

[Killzone_Kid]

Guess who is back? Yes me, because the damn search API doesnt work again! Well it kinda works, because you can retreive genres, but if you try to search by KEYWORD it returns 0 result no matter what the keyword is.

Is there a problem or someone just changed specification?

[Killzone_Kid]

Does anyone have any idea why keyword search is not working?

[Killzone_Kid]

Anyone?

[Killzone_Kid]

Thank you very much for non existing support while someone happily keeps breaking the API.

I went and examined what you've done to it this time, and apparently as I expacted you changed specification. As per own still existing documentation wiki...

URL (JSON Request):

Stations based on bitrate

http://api.shoutcast.com/station/adv...it=3&f=json&k=[Your Dev ID]

Stations based on media type

http://api.shoutcast.com/station/advancedsearch?mt=mpeg&limit=3&f=json&k=[Your Dev ID]

Stations based on genre id

http://api.shoutcast.com/station/adv...it=3&f=json&k=[Your Dev ID]

...you should be able to filter results by just indicating the type mpeg or aacp instead of audio/mpeg or audio/aacp, which is not the case anymore.

Well now you must specify the whole 9 yards. Before I could say mt = audio and get both mpeg and aacp results. Now I have to drop mt all together to do that, but, apparently I cannot even consistently do that because some calls REQUIRE some form of mt parameter and it cannot be empty either.

The whole thing becomes a mess very rapidly.

[DrO]

it's hard to give support when support is not around aka i'm not a robot and needed a week off.

to my knowledge the handling of the api's shouldn't have changed with the other changes which have been made though i'm not 100% on that area. will raise the issue though if you can confirm exactly what you were using beforehand then that will make it easier to compare against.

-daz

[Killzone_Kid]

Originally Posted by DrO

it's hard to give support when support is not around aka i'm not a robot and needed a week off.

to my knowledge the handling of the api's shouldn't have changed with the other changes which have been made though i'm not 100% on that area. will raise the issue though if you can confirm exactly what you were using beforehand then that will make it easier to compare against.

-daz

Thanks for replying daz, but I thought you had a dedicated dev team reading the forums. I can only guess but before it was regex matching mt parameter, therefore &mt=audio would match both 'audio/mpeg' and 'audio/aacp' and &mt=mpeg would only match 'audio/mpeg'. Now you need to specify the whole thing &mt=audio/mpeg if you want to match 'audio/mpeg' but the wiki specification still says &mt=mpeg is enough, which is false as this is what broke.

I can guarantee you that API changed as the result of the changes.

[DrO]

Originally Posted by Killzone_Kid

Thanks for replying daz, but I thought you had a dedicated dev team reading the forums.

that would be me predominantly.

Originally Posted by Killzone_Kid

I can guarantee you that API changed as the result of the changes.

i'm not disagreeing that it's likely that the api has changed as there have been quite a few changes / additions made to it, hence looking for confirmation on things before i relay it on to be checked out, etc.

-daz

[DrO]

i believe an update has been deployed which re-enables the old behaviour along with the new style handling.

-daz

[Killzone_Kid]

Thanks Daz. I have already updated my players to adapt to the new specification, but tried the old version and it is now working again too. Also before if I would search for "thrash" as keyword it would produce 0 results, now it gives me at least 9, so something else got improved obviously with this fix.

[DrO]

i'm not sure what else was changed but thanks for reporting and confirming all is ok now.

-daz