AlienBBC and Live365 problems

[Slim]

I am having trouble accessing Internet Radio using AlienBBC (v0.11) and
Live365. I use a proxy to connect to the Internet, and have the following
two scenarios;

1) Proxy set in Slimserver
No playback from either AlienBBC or Live365. Both of these connect and
present the list of program choices. But I am not able to actually listen
to anything

2) No proxy set in Slimserver
AlienBBC playback works but Live365 will not connect, I get a 'Website
error' message.

All the other Internet Radio options seem to work (Shoutcast, Radioio, etc)

I have installed the SlimServer_v2004-12-03 nightly to see if this helps,
but still no joy. Any ideas of what I am doing wrong?

Thanks,

-- Stuart


Random Thought:
---------------
Yeah. Wait a minute. It's the guy from TV. My kid's
hero...Cruddy...Crummy...Krusty the Clown!

-- Homer Simpson
Krusty Gets Busted

[Jim]

Slim wrote:
> I am having trouble accessing Internet Radio using AlienBBC (v0.11) and
> Live365. I use a proxy to connect to the Internet, and have the following
> two scenarios;
>
> 1) Proxy set in Slimserver
> No playback from either AlienBBC or Live365. Both of these connect and
> present the list of program choices. But I am not able to actually listen
> to anything

If you run the server with --d_plugins, I'd wager you'll see the
message: "Live365.protocolHandler failed to connect to live365.com" and
some additional detail.

It looks like some code gnomes (gotta' love open source) made the common
Live365 site calls aware of the proxy setting, but hadn't noticed that
the protocol handler does its own socket work. It would also fail to get
the playlist for the current station.

I was always a little uncomfortable with the protocol handler doing its
own socket work, but that discomfort was offset by me not wanting to
tweak the API code to manage the kind of data the protocol handler gets.
Live365 doesn't send HTTP headers when one requests a playlist, which is
"wrong" and won't work with the API code, which only returns content.

Doing it right so that it's globally proxy aware will take some
redesign, but I'll work that up and get it to Vidur. Could take a week
or two, I'm a little swamped with the holidays.

Jim

[Jim]

Jim wrote:
> Slim wrote:
>> I am having trouble accessing Internet Radio using AlienBBC (v0.11) and
>> Live365.

> Doing it right so that it's globally proxy aware will take some
> redesign, but I'll work that up and get it to Vidur. Could take a week
> or two, I'm a little swamped with the holidays.

....or, I could pull a Scotty and have "a week or two" mean "an hour or two."

I just sent the patch to Vidur that should solve your problems. I don't
have a proxy myself, so if you could please keep an eye on the nightlies
and let me know if it starts working once the patch gets checked in.

Cheers,
Jim

[Jules Taplin]

Jim... you're going to show me up, matey.

I haven't even begun to work out what's not right with AlienBBC in the
same circumstances. My guess is that it's something to do with the
transcoder_proxy


-- Jules

Jim wrote:

> Jim wrote:
>
>> Slim wrote:
>>
>>> I am having trouble accessing Internet Radio using AlienBBC (v0.11) and
>>> Live365.
>>
>
>> Doing it right so that it's globally proxy aware will take some
>> redesign, but I'll work that up and get it to Vidur. Could take a
>> week or two, I'm a little swamped with the holidays.
>
>
> ...or, I could pull a Scotty and have "a week or two" mean "an hour or
> two."
>
> I just sent the patch to Vidur that should solve your problems. I
> don't have a proxy myself, so if you could please keep an eye on the
> nightlies and let me know if it starts working once the patch gets
> checked in.
>
> Cheers,
> Jim
>
>

[Jim]

Jules Taplin wrote:
> Jim... you're going to show me up, matey.
>
> I haven't even begun to work out what's not right with AlienBBC in the
> same circumstances. My guess is that it's something to do with the
> transcoder_proxy

You've got a considerably more complex plugin than I do. I make some API
calls of an XML web service, the heavy lifting is done by stock
libraries. ;-)

Jim

[Slim]

> Jim wrote:
>> Slim wrote:
>>> I am having trouble accessing Internet Radio using AlienBBC (v0.11) and
>>> Live365.
>
>> Doing it right so that it's globally proxy aware will take some
>> redesign, but I'll work that up and get it to Vidur. Could take a week
>> or two, I'm a little swamped with the holidays.
>
> ...or, I could pull a Scotty and have "a week or two" mean "an hour or
> two."
>
> I just sent the patch to Vidur that should solve your problems. I don't
> have a proxy myself, so if you could please keep an eye on the nightlies
> and let me know if it starts working once the patch gets checked in.
>
> Cheers,
> Jim
>
>

[Jim]

Slim wrote:
>>Jim wrote:
>>
>>>Slim wrote:
>>>
>>>>I am having trouble accessing Internet Radio using AlienBBC (v0.11) and
>>>>Live365.
>>
>>>Doing it right so that it's globally proxy aware will take some
>>>redesign, but I'll work that up and get it to Vidur. Could take a week
>>>or two, I'm a little swamped with the holidays.
>>
>>...or, I could pull a Scotty and have "a week or two" mean "an hour or
>>two."
>>
>>I just sent the patch to Vidur that should solve your problems. I don't
>>have a proxy myself, so if you could please keep an eye on the nightlies
>>and let me know if it starts working once the patch gets checked in.
>>
>>Cheers,
>> Jim
>>
>>

[Daniel Cohen]

Happy New Year, all.

It's time for another try to solve my AlienBBC problem. I've asked
before but no useful replies. I'm hoping for some generic things to
try that might reveal the issue, rather than specific answers which I
know I won't get.

AlienBBC works fine when SlimServer is run from the command-line. But
it doesn't load properly when SlimServer is run normally.

So Qurstion 1 is: why should there be any difference at all in the
two procedures?

I've tried turning on the plugins debugging option, but that doesn't
help. With command-line use it tells me (as it should) all the
details of the plugin loafing ok, with normal use it just says that
the plugin was not recognised.

So Question 2 is: whether there's any other useful debugging option
that I should switch on?

The specific problem with normal use of the SlimServer is that the
Web interface reveals a plugin called Alien. The Squeezebox menu
shows an entry that is completely blank.

"Alien" is the name of the folder containing all the AlienBBC stuff,
and this folder is inside the Plugins folder. There seems to be
nothing else in the actual plugin text that could give that word.

This suggests to me that there is a path issue somewhere, presumably
with the plugin.pm script. I've compared the script with that for
DateTime (the only other one that has the plugin inside a folder)
which works ok, but couldn't spot any differences that were obvious.

Question 3: can anyone spot such an issue?

All this is running on a Mac. I have set SlimServer to run for one
user only, but someone else has the same problem with it set for all
users. Unfortunately, Jules is unfamiliar with Macs, and I have no
real familiarity with perl, though I can disentangle the meaning of
the script to some extent.

AlienBBC 0.11, SlimServer 5.4.
--
Daniel Cohen

[Neil Sleightholm]

I think I can help with question 1. When working to get AlienBBC
working on Windows I found something similar and the problem was that
the HTML libraries for perl are not complete when running from the exe.
To fix this copy "C:\Perl\site\lib\auto\HTML" to ".\server\CPAN\auto"
(you need to create the directory 'auto'). Copy "C:\Perl\site\lib\HTML"
to ".\server\CPAN" (the HTML directory already exists and I overwrote 2
older files with the newer ones from my Perl install). I'm not a MAC
expert so this might not apply!

Neil

Daniel Cohen wrote:

> Happy New Year, all.
>
> It's time for another try to solve my AlienBBC problem. I've asked
> before but no useful replies. I'm hoping for some generic things to
> try that might reveal the issue, rather than specific answers which I
> know I won't get.
>
> AlienBBC works fine when SlimServer is run from the command-line. But
> it doesn't load properly when SlimServer is run normally.
>
> So Qurstion 1 is: why should there be any difference at all in the
> two procedures?
>
> I've tried turning on the plugins debugging option, but that doesn't
> help. With command-line use it tells me (as it should) all the
> details of the plugin loafing ok, with normal use it just says that
> the plugin was not recognised.
>
> So Question 2 is: whether there's any other useful debugging option
> that I should switch on?
>
> The specific problem with normal use of the SlimServer is that the
> Web interface reveals a plugin called Alien. The Squeezebox menu
> shows an entry that is completely blank.
>
> "Alien" is the name of the folder containing all the AlienBBC stuff,
> and this folder is inside the Plugins folder. There seems to be
> nothing else in the actual plugin text that could give that word.
>
> This suggests to me that there is a path issue somewhere, presumably
> with the plugin.pm script. I've compared the script with that for
> DateTime (the only other one that has the plugin inside a folder)
> which works ok, but couldn't spot any differences that were obvious.
>
> Question 3: can anyone spot such an issue?
>
> All this is running on a Mac. I have set SlimServer to run for one
> user only, but someone else has the same problem with it set for all
> users. Unfortunately, Jules is unfamiliar with Macs, and I have no
> real familiarity with perl, though I can disentangle the meaning of
> the script to some extent.
>
> AlienBBC 0.11, SlimServer 5.4.

[Jules Taplin]

Ah. Interesting, Neil. That might also explain why Triode's most recent
AlienBBC-on-windows builds need proper perl, too.

Triode - does that make sense to you, or are we barking up the wrong tree?


-- Jules

Neil Sleightholm wrote:

>I think I can help with question 1. When working to get AlienBBC
>working on Windows I found something similar and the problem was that
>the HTML libraries for perl are not complete when running from the exe.
>To fix this copy "C:\Perl\site\lib\auto\HTML" to ".\server\CPAN\auto"
>(you need to create the directory 'auto'). Copy "C:\Perl\site\lib\HTML"
>to ".\server\CPAN" (the HTML directory already exists and I overwrote 2
>older files with the newer ones from my Perl install). I'm not a MAC
>expert so this might not apply!
>
>Neil
>
>Daniel Cohen wrote:
>
>
>
>>Happy New Year, all.
>>
>>It's time for another try to solve my AlienBBC problem. I've asked
>>before but no useful replies. I'm hoping for some generic things to
>>try that might reveal the issue, rather than specific answers which I
>>know I won't get.
>>
>>AlienBBC works fine when SlimServer is run from the command-line. But
>>it doesn't load properly when SlimServer is run normally.
>>
>>So Qurstion 1 is: why should there be any difference at all in the
>>two procedures?
>>
>>I've tried turning on the plugins debugging option, but that doesn't
>>help. With command-line use it tells me (as it should) all the
>>details of the plugin loafing ok, with normal use it just says that
>>the plugin was not recognised.
>>
>>So Question 2 is: whether there's any other useful debugging option
>>that I should switch on?
>>
>>The specific problem with normal use of the SlimServer is that the
>>Web interface reveals a plugin called Alien. The Squeezebox menu
>>shows an entry that is completely blank.
>>
>>"Alien" is the name of the folder containing all the AlienBBC stuff,
>>and this folder is inside the Plugins folder. There seems to be
>>nothing else in the actual plugin text that could give that word.
>>
>>This suggests to me that there is a path issue somewhere, presumably
>>with the plugin.pm script. I've compared the script with that for
>>DateTime (the only other one that has the plugin inside a folder)
>>which works ok, but couldn't spot any differences that were obvious.
>>
>>Question 3: can anyone spot such an issue?
>>
>>All this is running on a Mac. I have set SlimServer to run for one
>>user only, but someone else has the same problem with it set for all
>>users. Unfortunately, Jules is unfamiliar with Macs, and I have no
>>real familiarity with perl, though I can disentangle the meaning of
>>the script to some extent.
>>
>>AlienBBC 0.11, SlimServer 5.4.
>>
>>
>
>