Author Topic: Un-playable stream address  (Read 1350 times)

sveakul

  • Posts: 55
Un-playable stream address
« on: 24 Jul '18 - 03:38 »
This radio stream address (Prog Palace Radio) will not play in XMPlay 3.8.3.8, but plays fine as-is in Foobar, MusicBee and AIMP:

http://69.162.103.66/stream/gstaffor.pls?mp=/stream

Stream is 256k MP3 with the following icy headers; any ideas?? :

HTTP/1.1 200 OK
Server: cc-web/1.6.3
Date: Tue, 24 Jul 2018 02:34:08 GMT
Content-Type: audio/mpeg
Transfer-Encoding: chunked
Connection: close
icy-notice1: <BR>This stream requires <a href="http://www.winamp.com">Winamp</a><BR>
icy-notice2: SHOUTcast DNAS/posix(linux x64) v2.5.5.733<BR>
Accept-Ranges: none
Access-Control-Allow-Origin: *
Cache-Control: no-cache,no-store,must-revalidate,max-age=0
icy-name: Prog Palace Radio
icy-genre: Progressive Metal, Prog Rock
icy-br: 256
icy-sr: 44100
icy-url: http://progpalaceradio.com
icy-pub: 1
icy-metaint: 8192
X-Clacks-Overhead: GNU Terry Pratchett
« Last Edit: 24 Jul '18 - 03:42 by sveakul »

Ian @ un4seen

  • Administrator
  • Posts: 21370
Re: Un-playable stream address
« Reply #1 on: 24 Jul '18 - 13:59 »
It is playing fine here, so strange that it isn't there. If you check the playlist entry's "Track info" after opening the URL in XMPlay, what URL do you see there? I'm see this: http://69.162.103.66/proxy/gstaffor?mp=/stream

sveakul

  • Posts: 55
Re: Un-playable stream address
« Reply #2 on: 24 Jul '18 - 18:16 »
Hi Ian:  If I replace the original address with the one you indicated (http://69.162.103.66/proxy/gstaffor?mp=/stream), the stream connects and plays fine.  With the original address, it won't even make a connection at all, just drops to the next playable station on my list.

Using the published address of http://69.162.103.66/stream/gstaffor.pls?mp=/stream, which you can see by checking out the website (http://www.progpalaceradio.com/) and going to the "Port 80 Streaming" link under 256k MP3, AIMP and MusicBee (both BASS) connect as-is and keep that URL in the File Info.  However, I just noticed that with Foobar, after connecting via the published address, it does change the URL path to the one you supplied.  Why my XMPlay didn't also follow that behavior, which yours DID, I guess remains a mystery--possibly something in my Internet config it takes issue with??

The main thing is I now can play the stream in XMPlay with that new "proxy" address and I thank you!  As nature abhors a vacuum, I abhor an unsolved mystery, but hey that's life  :)

Ian @ un4seen

  • Administrator
  • Posts: 21370
Re: Un-playable stream address
« Reply #3 on: 25 Jul '18 - 17:49 »
Yeah, XMPlay should load the PLS playlist and add the contents to XMPlay's playlist, so you should see the "proxy" URL (rather than the original URL) in XMPlay's list. I'm not sure why that wouldn't be happening. Are you only having the problem with this particular playlist URL, or others too? If you happen to have Wireshark installed, you could use that to check if the PLS file is being downloaded by XMPlay.

Does it make any difference how you open the URL, eg. using "Open file(s)" window or drag'n'dropping it from a browser? How about if you download the PLS file and then open it?

sveakul

  • Posts: 55
Re: Un-playable stream address
« Reply #4 on: 25 Jul '18 - 22:15 »
Hi Ian:  Interesting!  What I found is that by letting my web browser (Firefox) choose XMPlay to open the link by default, it WILL open and play normally and change the link to the proxy.  The failure only happens if I copy the original link as-is, then paste it into XMPlay's "Add/URL" dialog and attempt to open it.

Never had a problem with any other link doing the copy/paste method, so I would think it's that particular site handling requests differently and/or that odd "mp=stream" suffix.

At least it shows me it's about time I change the browser's default handler for pls to XMPlay :)

Ian @ un4seen

  • Administrator
  • Posts: 21370
Re: Un-playable stream address
« Reply #5 on: 27 Jul '18 - 15:34 »
I've retried the URL a bunch more times and I have been able to reproduce the reported problem sometimes, generally the 1st time after I haven't tried it for a while. It happens when the connection timeouts, so XMPlay can't read the PLS file and instead just adds the original URL to the list. Perhaps the server is going into a sleep state after a while and it takes some time to wake up again. Anyway, you could try increasing the "Timeout" setting in the "Miscellaneous" options page and see if that helps.

sveakul

  • Posts: 55
Re: Un-playable stream address
« Reply #6 on: 27 Jul '18 - 19:21 »
Roger that, will bump up my timeout value from now on.  Thanks for all your help with this!