my remote cannot control neither my computer nor the internet thru wireless. It all happened right after today's update. Can we say Squeezebox is dead? mine never was able to connect directly to my wireless router, always created problems. I don't understand why it has to be this hard, to play music. I'm really regretting all the money I paid for this....
Can Anyone help me?
Results 1 to 7 of 7
Thread: end of duet after the updates
2010-06-22, 18:20 #1
- Join Date
- Oct 2009
end of duet after the updates
2010-06-22, 19:03 #2
Did you do a factory reset? Did you try having the latest update reinstalled again? Did you try falling back to the firmware before the update?
As to saying it has never played music right, have you checked your wireless network? I would say a good 90% of problems I find with the Duet end up being the users WiFi setup, not the Duet.iPhone
ModWright Platinum Signature Transporter, VTL TL-6.5 Signature Pre-Amp, Ayre MX-R Mono's, VeraStarr 6.4SE 6-channel Amp, Vandersteen Speakers: Quatro Wood Mains, VCC-5 Reference Center, four VSM-1 Signatures, Video: Runco RS 900 CineWide AutoScope 2.35:1, Vandersteen V2W Subwoofer
Transporter, ADCOM GTP-870HD, Cinepro 3K6SE III Gold, Vandersteen Model 3A Signature, Two 2Wq subs, VCC-2, Two VSM-1
Office: Touch with Vandersteen VSM-1s
Kitchen: Touch in-wall mount w/ Thiel Powerpoint 1.2s
Bedroom: Squeezebox BOOM
Bathroom: Squeezebox Radio
Around the House: SliMP3, SB1, SB2, SB3
Ford Thunderbird: Duet, Mac Mini
Ford Expedition: SB Touch, USB drive
2010-06-22, 23:03 #3
whats the color of the led on the reciever ? red blue or something else ?
More specific info would help anybody trying to understand your problem .
Try also to describe your hardware n more detail and how it's conected etc .
Btw the controller also have an diagnostic menu.
settings > advanced > Diagnostics .
What does it says there ?--------------------------------------------------------------------
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3 sub.
Kitchen: Touch + powered Fostex PM0.4
Misc use: Radio (with battery)
iPad1 with iPengHD & SqueezePad
(in storage SB3, reciever ,controller )
server HP proliant micro server N36L with ClearOS Linux
2010-06-23, 00:49 #4
- Join Date
- May 2009
- Denmark (Struer)
Is your Receiver running as cabled?
There was a problem introduced in 7.5.1/7.6.0(beta) with the remote/controller not working to well with cabled Receivers. I think that the correction was checked in Monday and rollout of the controller software will take place as soon as it has been verified.
Edit: Actually the new controller software is out; which build are your controller running at the moment?Main: Receiver (Audiocom) -> Beresford Caiman+ (Gatorized) -> Carver A-500x -> B&W 704
Office: Receiver -> Luxman L-210 -> Stax SR84 Pro
-> Beresford Caiman (Gatorized) -> Superlux HD668B
Server: A8-5500, 4 GB, SSD+ 2*1 TB, Win8 w. SBS 7.8 (SQLite w. High Mem)
Tied together by D-Link DIR-655 + DGS-1008D
2010-06-23, 21:09 #5
- Join Date
- May 2010
I have the same problem: after the update to 7.5.1 r8885 my controller appears to be playing but gives no output. I've checked the receiver channels, not the problem. Reloaded the firmware, no help. It is not the wireless connection, which shows at 38%, same as it always has when working perfectly.
2010-06-24, 17:53 #6
- Join Date
- Jun 2008
- Northern Va, US
2010-06-29, 00:20 #7
- Join Date
- May 2010
solution to the "no output" issue
I've sent this very issue to Squeezebox tech support and they've solved my particular problem. Here's the very helpful response that solved my issue, with a three possible solutions:
FROM: "Logitech Customer Support" <firstname.lastname@example.org> DATE: Sat, 26 Jun 2010 14:13:26 -0700 (PDT)TO: <email@example.com>; <firstname.lastname@example.org>REPLYTO: "Logitech Customer Support" <email@example.com> SUBJECT: No sound output after 7.5.1 (r88885) update. The controller connects to Squeezebox.com and to the computer library. It appears to be playing but no ... [Incident: 100624-002897]
Response (Trevor) 06/26/2010 02:13 PM
It sounds like one of three things has occurred here.
1) The Xilinx audio chip in the Receiver is malfunctioning. We can try to reset it by doing a factory reset, holding in the button on the front until it turns red and flashes fast.
2) Port 9000 (The audio traffic port) is being blocked. Unlikely as it appears to be playing but there is no audio. Usually manifests as the inability to play the file at all with an error message.
3) The outputs are malfunctioning. Can you confirm this by trying to connect it to a different input on your stereo?
We can also try taking the software aspect out of the equation and trying just a hardware based test tone. To do so, unplug the Receiver, hold in the front button, and plug it back in. The LEDS should flash different colours and an extremely irritating sound should come out of the speakers it's attached to. If this fails, we're looking at a hardware failure.
re: anything to do to prevent a recurrence?
Just did the factory reset on the receiver (your #1 solution), and bingo! Thanks so much. I did have to sign off and restart the controller to get this to work. Would that be normal?
Any suggestions to prevent a repeat of the problem?
It's not really something that can be prevented, as it's not really something that should happen. We find it occurs most frequently if there is any sort of static build up between the inputs on your stereo and the outputs on the Duet.
Squeezebox Technical Support Manager