slim:noscan doesn't work at all. Is there way to prevent verification of streams?

[Kramer]

Hi,

My provider, Internode provide hosted radio stations. http://www.internode.on.net/resident...oadband_radio/
Access to these radio channels is only available when you are on the provider's network.
The problem is - it's impossible to play them with SquezeNetwork (it works only if you have PC with SquezeCenter turned on.)

There has been one message about this problem: http://forums.slimdevices.com/showthread.php?t=37596
http://forums.slimdevices.com/showthread.php?t=49083
And it's not resolved. slim:noscan doesn't change anything.

- URL http://radio.internode.on.net:8082/#slim:noscan=1 results in "Checking stream..." for a few seconds, then Squeezebox says "Stopped"
- URL http://media.on.net/radio/42.pls#slim:noscan=1 results in message "Error: No items found in playlist"
- URL http://media.on.net/radio/42.m3us#slim:noscan=1 results in message "Error: No items found in playlist"

Is there a way to get this working? To prevent Squeezenetwork from verifying streams? Why does it do that anyway?

[bpa]

I think noscan has to be added to the real URL and not the playlist URLs (i.e. not the URLs ending with m3u or pls).

[Kramer]

I am trying with real URL, http://radio.internode.on.net:8082/
Adding #slim:noscan=1 on different way. it doesn't work.
http://radio.internode.on.net:8082/#slim:noscan=1
http://radio.internode.on.net:8082#slim:noscan=1
or whatever.

[bpa]

When you play the station on PC can you confirm what URL is actually playing (e.g. properties on WMP) - sometimes these stations have handshake which alter port number between initial request and actual playing.

[Kramer]

When you play the station on PC can you confirm what URL is actually playing (e.g. properties on WMP) - sometimes these stations have handshake which alter port number between initial request and actual playing.

Yes, I checked with netstat, when you play the stream the connection is established to the exact address specified in URL.

So it's definitely a SqueezeNetwork bug.

[bpa]

So it's definitely a SqueezeNetwork bug.

This is only a user forum - if you want the problem investigated by the development team you must log it as a new bug report or add it to an existing bugs report in the bugs database
http://www.slimdevices.com/redir.htm...imdevices.com/

[andyg]

On Nov 26, 2008, at 4:08 AM, bpa wrote:

>
>>
>> So it's definitely a SqueezeNetwork bug.
>>
>
> This is only a user forum - if you want the problem investigated by
> the
> development team you must log it as a new bug report or add it to an
> existing bugs report in the bugs database
> http://www.slimdevices.com/redir.htm...imdevices.com/

I'm going to look at this today, sorry this keeps breaking.