--- kdf <slim-mail (AT) deane-freeman (DOT) com> wrote:
> Quoting Felix Mueller <fcm4711 (AT) yahoo (DOT) com>:
>
> > Hi there
> >
> > Is anyone successfully using the rm2mp3proxy.pl
> script
> > with the current CVS? I had it working with an
> older
> > SlimServer release, but with the current one,
> > SlimServer just gets completely unresponsive and
> > needs to be restarted. (Or if I kill the script
> > SlimServer comes back after about a minute.)
> >
> > I see that the script gets triggered and is
> reading
> > the
> > stream from the internet, but SlimServer seems to
> > have a problem using the output of the script.
> >
> > I tried on two different Linux installations and
> got
> > the same result.
> >
> > Any ideas?
>
> I wondered about this. Some filenames were
> accidentally getting detected as
> urls, so the isURL routine was tightened.
>
> sub isURL {
> my $url = shift;
> return (defined($url) && ($url =~
> /^(http|icy|itunesplaylist|file):/i));
> }
>
> Try changing this to:
> sub isURL {
> my $url = shift;
> return (defined($url) && ($url =~
> /^(http|icy|itunesplaylist|rtsp|file):/i));
> }
>
> see if that helps.
Thanks for the tip. However this was not the problem.
I did a try and error with older releases until I
found the change around April 1st that causes
the problem.
Apparently it's a timing issue. The change in
RemoteStream.pm line 108 from a fixed timeout of 2s
to the global timeout setting (in my case 30s) causes
the problem.
In my opinion the timeout on line 108 needs to be
smaller than the timeout SLIMP3 or Squeezebox is
waiting until reporting a loss of connection with
SlimServer.
Going back to a fixed 2s timeout resolves the problem.
Felix
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
> Quoting Felix Mueller <fcm4711 (AT) yahoo (DOT) com>:
>
> > Hi there
> >
> > Is anyone successfully using the rm2mp3proxy.pl
> script
> > with the current CVS? I had it working with an
> older
> > SlimServer release, but with the current one,
> > SlimServer just gets completely unresponsive and
> > needs to be restarted. (Or if I kill the script
> > SlimServer comes back after about a minute.)
> >
> > I see that the script gets triggered and is
> reading
> > the
> > stream from the internet, but SlimServer seems to
> > have a problem using the output of the script.
> >
> > I tried on two different Linux installations and
> got
> > the same result.
> >
> > Any ideas?
>
> I wondered about this. Some filenames were
> accidentally getting detected as
> urls, so the isURL routine was tightened.
>
> sub isURL {
> my $url = shift;
> return (defined($url) && ($url =~
> /^(http|icy|itunesplaylist|file):/i));
> }
>
> Try changing this to:
> sub isURL {
> my $url = shift;
> return (defined($url) && ($url =~
> /^(http|icy|itunesplaylist|rtsp|file):/i));
> }
>
> see if that helps.
Thanks for the tip. However this was not the problem.
I did a try and error with older releases until I
found the change around April 1st that causes
the problem.
Apparently it's a timing issue. The change in
RemoteStream.pm line 108 from a fixed timeout of 2s
to the global timeout setting (in my case 30s) causes
the problem.
In my opinion the timeout on line 108 needs to be
smaller than the timeout SLIMP3 or Squeezebox is
waiting until reporting a loss of connection with
SlimServer.
Going back to a fixed 2s timeout resolves the problem.
Felix
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway