I installed the 3/18 nightly build and get the same exact problems on
both Shoutcast and Live365. Shoutcast gives this error: There was an
error parsing the stream information. Try reducing the number of
streams if you've set a great number. (2).
I really don't understand. I just checked the
I am running into the same problem. I moved to 6.5b1 and the firmware
on the SB3 is 35. It seems to totally freeze up at least once
everyday.
In my case it is a hard freeze. The SServer doesn't see it, I can't
soft power down and power back on either. The only fix is to reboot
the SB3 and
govardha,
As you can't ping the player (which I assume you can when it is
working) and there is no control connection, I think this means the
problem is to do with the network/player rather than slimserver.
This does not seem to be the same problem as the one seen by others as
you can restart
Physically unplugging the power connection to the SB3 device and
restarting it seems to work. There are no network problems in my home,
as a laptop, 2 tivo's and my Macintosh all of which are connected
wirelessly perform flawlessly.
I will try to ping when the SB3 freezes up once more and let
I suggest you raise a bug against the firmware to ensure this is
investigated.
As for loading the old firmware. As long as the old file exists in the
Firmware directory, you can edit the squeezebox2.version file to replace
35 with 28.
--
Triode
Have spent a few days trying to figure out why slimserver was hanging
when i added my last few CDs (Eac to Flac). Finally discovered that it
was self inflicted I'd managed to tag several cd's with DISCC twice.
This crashes the server on a rescan.
Got it sorted then thought I'd upgrade to
I replaced the Plugin with the one you linked and it fixed the problem.
I updated the bug report with my system info.
--
NWP
NWP's Profile: http://forums.slimdevices.com/member.php?userid=3730
View this thread:
NWP Wrote:
I replaced the Plugin with the one you linked and it fixed the problem.
Just to be sure... Could you please swap back and forth between these
two version and always reproduce the bahaviour even with only eg. 300
streams?
If yes, could you please give this version a try?
Thanks!
Max - I don't think it is causing your problem, but you may want to try
removing the: $client-killAnimation() from
Slim::Buttons::Playlist::jump.
I don't think this is needed by the current scolling code and was added
a long time ago to kill scrolling when tracks changed with the old
scrolling
That attachment doesn't seem to be downloading correctly for me. I will
remove and reinstall Slimserver so I have the old version of plugin.pm,
then I will switch them back and forth to see what happens.
--
NWP
NWP's
I think I didn't understand AndyG's instructions on enabling the the
d_plugin flag before. I enabled it from the web interface. I saw in
the other thread where you told someone to run slim from the command
line with the flag, so I tried that.
This is what I get. Hope it helps:
2006-03-19
Unfortunately if things like Shoutcast spit out bad XML there isn't much
we can do. However, Shoutcast is working fine for me today, so maybe
they've fixed the problem.
I did have the problem mentioned today with the number of streams set to
2000. Reducing to 200 fixed it.
BUT there
This is what I get. Hope it helps:
It's the usual suspects... BTW: what language setting are you using (OS
and Slimserver)?
--
Michael
---
Help translate SlimServer by using the
StringEditor Plugin (http://www.herger.net/slim/)
OK, I think I've diagnosed out the ogg issue. Nothing to do with the
beta version - just the sox version on Ubuntu 5.10...
See here: http://forums.slimdevices.com/showthread.php?t=17627
--
doundounba
doundounba's
You say the power button doesn't help. Do you mean it doesn't
eventually reboot (you have to be patient) or do you mean that after
the reboot it still can't connect?
There is a firmware subdirectory of the server directory that contains
the firmware and firmware control files.
--
Millwood
15 matches
Mail list logo
