CraigStevenson;232177 Wrote:
> I can't get over the improvement. Wow! (Again...)
No offense to you or any of the hardworking chaps that are busy trying
to improve the can of worms that is now called "Squeezecenter"
It still stinks to high heaven.
.
--
haunyack
Transporter -> B&K R200.2
I just got done installing the October 2 build of SqueezeCenter 7.0 for
testing. Although it is still early, after about 10-15 minutes, I could
not reproduce the issues that I reported earlier, when using 6.5.4.
There were a couple of times when I noticed a brief hesitation, but
nothing approac
CraigStevenson;232162 Wrote:
> I just logged a report through the "proper" channels. I did reference
> this thread. Hopefully, somebody will contact us here, and see what
> the common factors are.
Excellent !
--
Greg Erskine
--
Greg Erskine;232159 Wrote:
> Hi Craig,
>
> Unless the issue has been reported though the "proper" channels then it
> will not be assigned to anyone to fix, that is why I asked earlier if
> anyone has logged the problem.
>
> I the past when I logged problems I was told not to do so until I
> loa
CraigStevenson;232153 Wrote:
> Hopefully, this thread will be brought to the attention of somebody
> at Slim/Logitech, and this will be investigated further
Hi Craig,
Unless the issue has been reported though the "proper" channels then it
will not be assigned to anyone to fix, that is w
The latest nightly builds (for the last 3 or 4 weeks) uses FW32 for the
Transporter. This has only been modified for better sync'ing (I think)
from FW31 which has been used since about 6.5.4.
Just to reitterate, SS7 was using FW31 until a few weeks ago, but is
now on FW32.
--
MikeFish
-
MikeFish;232147 Wrote:
> i noticed mine was happening everytime I turned it on and tried to
> access the Music Folder. Guessing it was a network issue regarding
> access to my ever growing collection I thought there was nothing
> anybody could do. However, the latest version of SS (or should i sa
i noticed mine was happening everytime I turned it on and tried to
access the Music Folder. Guessing it was a network issue regarding
access to my ever growing collection I thought there was nothing
anybody could do. However, the latest version of SS (or should i say SC
now) has stopped this compl
I have not reported this, since it doesn't seem to be easily
reproducible. However, I do not know for sure if it has been or has
not been reported. It will be interesting to see if going back to an
earlier firmware version fixes it for anybody. Unfortunately, I
haven't had a chance to do this,
I change back to 6.5.1. with firmware 27 on the 27 September 2007 and so
far no problem, but... my lockups only ever occurred every other week,
so the jury is still out.
Does anyone know if this problem has been logged officially? It
wouldn't get looked at otherwise.
regards
--
Greg Erskine
-
cliveb;230217 Wrote:
> And after what I've read recently, I have no desire to tempt fate by
> doing so! 6.5.1 is working very nicely, feeding a TP and an SB2. It
> ain't broke, so it's not going to get "fixed".
I understand completely. That probably means I'll have to fix mine by
going back to
CraigStevenson;230101 Wrote:
> It would be interesting to see if you notice the same problem(s) after
> upgrading from 6.5.1. (Although I'm not recommending that.)
And after what I've read recently, I have no desire to tempt fate by
doing so! 6.5.1 is working very nicely, feeding a TP and an SB2
cliveb;230059 Wrote:
> I have never experienced this problem. And my Slimserver is running on a
> lowly 533MHz mini-ITX machine, which I'd guess is a lot less powerful
> than what many others run around here.
>
> There are two possible differences between my setup and others' that
> might be sig
cliveb;230059 Wrote:
>
>
> 1. I'm running firmware 24, .
Might you have a link for FW 24 handy...I'd like to give it a try as my
TP exhibits these symptoms from time to time.
Cheers!
.
--
haunyack
Transporter -> B&K R200.2 -> Vandersteen 3A Signature. (Listening room)
SB3 (RWA analog) ->
I have never experienced this problem. And my Slimserver is running on a
lowly 533MHz mini-ITX machine, which I'd guess is a lot less powerful
than what many others run around here.
There are two possible differences between my setup and others' that
might be significant:
1. I'm running firmware
Greg Erskine;229992 Wrote:
> I hate to do a "me too" post, but this happens on my Transporter as
> well.
>
> I have also noticed it seems to occur after extensive use the
> navigation buttons on the remote. It requires me pulling the plug to
> get it going again.
I too have to say that I've exp
Greg Erskine;229992 Wrote:
> I hate to do a "me too" post, but this happens on my Transporter as
> well.
>
> I have also noticed it seems to occur after extensive use the
> navigation buttons on the remote. It requires me pulling the plug to
> get it going again.
Thank you for this post. There
I hate to do a "me too" post, but this happens on my Transporter as
well.
I have also noticed it seems to occur after extensive use the
navigation buttons on the remote. It requires me pulling the plug to
get it going again.
--
Greg Erskine
-
SuperQ;229889 Wrote:
> I really have a feeling that there is a packet loss problem, or the
> slimserver is being starved for resources.
>
> All remote commands are sent to the server and processed. The
> Transporter does not support gige, so it could be a duplex negotiation
> problem between th
CraigStevenson;229883 Wrote:
> Yes, that's EXACTLY what I experienced. I was doing a lot of browsing
> through my music, both in genres and music folder, while the music was
> playing, and then all of a sudden, the transporter stopped responding
> to the remote. The knob on the front resisted t
MikeFish;229875 Wrote:
> I occassionally get freezing, but if you leave it a couple of minutes it
> catches up with any button presses you have made during the freeze. The
> knob on the front resists against any turing like you described.
> Using SS7 with FW32.
> Also as my library has grown i no
I occassionally get freezing, but if you leave it a couple of minutes it
catches up with any button presses you have made during the freeze. The
knob on the front resists against any turing like you described.
Using SS7 with FW32.
Also as my library has grown i notice it a lot more as I select Mus
Wombat;229743 Wrote:
> My Transporter sometimes hangs completely after feeding it with my
> CD-Transport.
> When switching back from S/Pdif to Slimserver i sometimes need to pull
> the plug.
> Did you play around with external sources?
No, I don't use the external sources at all.
--
CraigSte
I have also experienced freezing of my transporter a couple of times.
Needed to unplug the power cable to reset it,.
I am using fw 31 with ss 6.5.5.
--
Veggen
Veggen's Profile: http://forums.slimdevices.com/member.php?use
My Transporter sometimes hangs completely after feeding it with my
CD-Transport.
When switching back from S/Pdif to Slimserver i sometimes need to pull
the plug.
Did you play around with external sources?
--
Wombat
Transporter -> monoblocks -> self-made speakers
--
haunyack;229631 Wrote:
> Anything else on the switch?
>
> .
Yes, but nothing new since the 6.5.4 upgrade. That's really the only
thing that changed
--
CraigStevenson
CraigStevenson's Profile: http://forums.slimdevi
CraigStevenson;229628 Wrote:
> My system is running wired directly to a gigabit ethernet switch, so it
> isn't a wireless issue.
Anything else on the switch?
.
--
haunyack
Transporter -> B&K R200.2 -> Vandersteen 3A Signature. (Listening room)
SB3 (RWA analog) -> Rotel RB1070 -> B&W Matrix
My system is running wired directly to a gigabit ethernet switch, so it
isn't a wireless issue.
--
CraigStevenson
CraigStevenson's Profile: http://forums.slimdevices.com/member.php?userid=8219
View this thread: http://foru
I've had no firmware or lockup problems on my Transporter. I started
with 6.5.0 and upgraded every minor release, and am running 7.0 testing
now. Sometimes I have had what I thought was Transporter trouble, but
it turned out to be my access point being locked up.
It could be a new firmware inte
Sounds just like the issues I had when my system was unplugged.
http://forums.slimdevices.com/showthread.php?t=30856
I changed to 6.5.4 and the latest firmware and have had less problems,
although I never unplug my unit (which for whatever reason seems to be
related to my problem).
Post back if
To answer one question, my music is in FLAC format, and the tags are
properly done. I did some limited testing today, and didn't have any
problems. I'll keep testing, and see if it happens again. I also have
an upgrade to do on another server, so I'll see if anything strange
happens with the SB
CraigStevenson;228929 Wrote:
> I added some new music, but I had already re-scanned it prior to the
> upgrade.
What format is the new music?
Tags in proper order?
.
--
haunyack
Transporter -> B&K Reference 200.2 -> Vandersteen 3A Signature.
(Listening room)
SB3 (RWA analog) -> Rotel RB 1070
haunyack;228928 Wrote:
> Sounds like a re-scan was initiated.
> Have you new music in your collection?
> I've noticed that even though scanner.exe has it's own process, it
> occasionally interferes with U.I. functionality.
> .
I added some new music, but I had already re-scanned it prior to the
Sounds like a re-scan was initiated.
Have you new music in your collection?
I've noticed that even though scanner.exe has it's own process, it
still interferes with U.I. functionality.
.
--
haunyack
Transporter -> B&K Reference 200.2 -> Vandersteen 3A Signature.
(Listening room)
SB3 (RWA anal
I just upgraded my SlimServer from v6.5.1 to v6.5.4. My transporter
requested a firmware upgrade, which I performed. However, during my
listening test, after about 10 minutes, the remote control stopped
working. The lights would light, but the transporter wouldn't respond.
(I was doing a lot of
35 matches
Mail list logo
