PDA

View Full Version : Squeezebox 3 + Apple Time Capsule + Wireless = no love?



Paco II
2008-03-04, 08:51
I hope this is the appropriate forums for this. I've been using my SB3 for a long while now, and never had the need to post, as all worked great. Recently bought an Apple Time Capsule to use as my router. For the life of me cannot get the SB3 to connect to it wirelessly.

This is what I have tried: Time Capsule has been set up with no security enabled at all (for testing). It's default wireless mode of n with g & b compatibility is the only option I can try. There is no 'g&b only' option or anything like that.

The SB3 sees the router when I go through set up. But when I get to the part when it should connect to it, it fails every time. And strangely, when I look at the Time Capsule logs, there is no entry of any attempt by the SB3 to connect.

Anyone have any ideas? I really appreciate the help.

Just to add, no problem when connecting via ethernet. Also, all my other wireless products (3 laptops, 1 ethernet to wireless converter) connect fine.

Eric Seaberg
2008-03-04, 09:54
I'm not using Time Capsule but am using a 'N' type AirPort (B/G compatible) and it works great! It's connect to my SB3 via 'G' and to my MBPro via 'N'.

Do you see the SB3 grab an IP address? Are you using DHCP or static? Did the IP address of your server change with the addition of the Time Capsule and can you set your server to be static?

Paco II
2008-03-04, 10:00
No, there is no indication that the SB3 is grabbing an IP. The router is indeed using DHCP to server out local IPs. I did a factory reset on the SB3.

I am not clear about your last comment about setting the server to be static. Do you mean that the SB3 should grab a static IP? How do I set it to grab a specific local IP?

Thanks for the help!!



I'm not using Time Capsule but am using a 'N' type AirPort (B/G compatible) and it works great! It's connect to my SB3 via 'G' and to my MBPro via 'N'.

Do you see the SB3 grab an IP address? Are you using DHCP or static? Did the IP address of your server change with the addition of the Time Capsule and can you set your server to be static?

Jim77007
2008-03-05, 16:49
Just got my time capsule, and am having the exact same trouble. Per Eric's suggestions, I've looked in the time capsule logs, and see no indication that my SB3 has attempted anything.

I've tried the following time capsule wireless modes: no encryption, WPA/WPA2, and WPA2.

Ben Sandee
2008-03-05, 18:01
On Wed, Mar 5, 2008 at 5:49 PM, Jim77007 <
Jim77007.35tpxb1204761001 (AT) no-mx (DOT) forums.slimdevices.com> wrote:

>
> Just got my time capsule, and am having the exact same trouble. Per
> Eric's suggestions, I've looked in the time capsule logs, and see no
> indication that my SB3 has attempted anything.
>
> I've tried the following time capsule wireless modes: no encryption,
> WPA/WPA2, and WPA2.


You should probably add yourself to the cc list of this bug:

http://bugs.slimdevices.com/show_bug.cgi?id=7415

Ben

Jim77007
2008-03-05, 18:43
On Wed, Mar 5, 2008 at 5:49 PM, Jim77007 <
Jim77007.35tpxb1204761001 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
[color=blue]
You should probably add yourself to the cc list of this bug:

http://bugs.slimdevices.com/show_bug.cgi?id=7415

Ben

Thank you, Ben. Will do.

MrSinatra
2008-03-05, 20:41
i have had some trouble with some routers dhcp-wise, meaning trying to get SB to connect via dhcp was problematic.

so instead i set the SB to a static yet private IP outside the dhcp range and that seems to work fine.

have you guys tried that?

Eric Seaberg
2008-03-05, 21:38
My home system is much heavier, but I use the same concept. The router has a DHCP range, say 192.168.1.100 - .150. You could set your SB3 static using 192.168.1.10 and not have any conflicts.

To set your server as STATIC, go into the the NETWORK preference pane and click on the SHOW TAB and pull down to BUILT-IN ETHERNET. BTW, I think you said you were wired between your server and the Time Capsule, right?

Next, select MANUALLY where is says Using DHCP and enter the same address as what showed using DHCP. Confirm that Subnet Mask and Router are also the same. Click APPLY NOW in the bottom right and close.

Your server will always have this address and the SB3 should always be able to see it without issue.

Paco II
2008-03-16, 14:39
How do I have the SB3 use a static IP? In the initial setup (as I have done a factory reset), there does not appear to be a way to switch to using a static IP.


i have had some trouble with some routers dhcp-wise, meaning trying to get SB to connect via dhcp was problematic.

so instead i set the SB to a static yet private IP outside the dhcp range and that seems to work fine.

have you guys tried that?

Claudius
2008-03-21, 08:35
Correct. I have the same problem SB3 will not pick up an IP address. I has nothing to do with making the server a static. My server is already a static IP, but until the SB3 gets an IP address, it won't see it. I even tried it hard wired it still won't be recognized by Time Capsule.

Claudius
2008-03-21, 08:53
Only way I could get it to work was to use a hardwired ethernet connection for the SB3, wireless won't work. Then set an IP in the SB3 menu outside the IP range of the wireless IPs assigned on the Time Capsule. My Slimserver is set up the same. But it works again thank goodness. It really should work with APPLEs DHCP assignment, that is a problem.

blblack
2008-03-21, 11:32
Only way I could get it to work was to use a hardwired ethernet connection for the SB3, wireless won't work. Then set an IP in the SB3 menu outside the IP range of the wireless IPs assigned on the Time Capsule. My Slimserver is set up the same. But it works again thank goodness. It really should work with APPLEs DHCP assignment, that is a problem.

I'm not sure about the DHCP part, apparently there are at least some people having issues with TC giving Squeezebox DHCP IPs over wired ethernet like you describe. The more troubling problem is that the Squeezebox and TC don't like to talk to each other over wifi at all. This part has nothing to do with DHCP settings (it doesn't work even when the TC is in bridge mode and the DHCP server is elsewhere on your network), it's a basic wifi interop problem. That problem is being tracked in the bug mentioned earlier in this thread: http://bugs.slimdevices.com/show_bug.cgi?id=7415

MrSinatra
2008-03-23, 19:51
i made the SB static IP, not the server.

i don't know if i still need to do that, but at the time, (some time ago), it fixed my issue.

tday01
2008-03-23, 21:03
I tried fixed IP for SB (fixed IP to SB MAC address from capsule). Still no love :(

wyzard
2008-03-24, 08:21
I'm having the same issue. I was able to connect wired, but would love to be able to do the wireless set up. I even assigned the Squeezebox a static IP address in the TC. Nothing.

I'm going to try to reset it up using wired mode and see what happens.

Hopefully the wireless will work soon.

Eric Seaberg
2008-03-24, 08:33
I'm wondering if the TC defaults to 802.11N at 5GHz where the SB3 will use 802.11G at 2.4GHz? I've got the AirPort N but run it 802.11N B/G compatible @ 2.4. This allows my SB3 and other Macs to see it as well as my MacBook Pro running N.

Just a thought...

wyzard
2008-03-24, 09:44
I'll check that out. Right now I've got it hard wired and it's working great. Listening to some Beatles right now. Now, I've got to clean up my album art and I should be good to go.....

Just want the wireless functionality to work for when I add more receivers in other sections of my home.

dweeks
2008-03-25, 08:27
I'm in the same boat with my SB3 and Time Capsule. I have the SBE wired up, but I have a setup problem that is preventing me from listening to Internet radio.

My SB3 is in a location that makes it impossible to wire it to my router. However, I can easily wire it to my Mac Pro. Mac Pros have -two- internal NICs, so one is wired to the router, and the second is wired to the SB3.

The first NIC is set for 192.168.0.x. This allows the Mac Pro to connect to the DSL modem and router.

The second NIC setting, for the SB3, is 192.168.1.x

The problem is that, since the SB3 is wired directly to NIC 2 on the Mac, but is not connected to the Internet-hooked NIC 1, I get "connection timed out errors" when I try to connect to any Internet radio station. I know this is because the 2nd NIC is providing just a hard wired network connection from SB3 to Mac, and there is no DNS ability.

Adding DNS server IP numbers to the network pref pane for NIC 2 makes no difference.

Does anyone who is more Mac network-savvy than I (that's almost anyone) have any suggestions?

Phil Leigh
2008-03-25, 08:58
can you bridge the NICS on the Mac?

Phil Leigh
2008-03-25, 09:04
Sorry I just re-read your post...
you can wire the Mac to the SB AND you can wire the Mac to the DSL Modem/Router...
get a switch ($10?) and wire the sb+router to the switch and then wire the switch to one of your Nic's!

dweeks
2008-03-25, 09:08
"can you bridge the NICS on the Mac?"

That's the question,and I don't know how to do that. I'm still searching Google...

Phil Leigh
2008-03-25, 10:35
"can you bridge the NICS on the Mac?"

That's the question,and I don't know how to do that. I'm still searching Google...

I've searched and it seems the answer is either no...or maybe but it's not obvious how to do it!
I'd get a switch and use a single NIC - much simpler :o)

sgard9
2008-03-25, 10:56
I like Phil's idea of getting an inexpensive switch and simplifying
your network. Put the switch at the MacPro and plug the cable from the
router into the switch. Connect one of the NIC's to the switch and
connect the SB3 to the switch. Unless you want to do some
sophisticated routing or bridging with the MacPro I would just leave
the second NIC unused. Let the router do NAT and be the DHCP server.
The MacPro and SB3 will be the DHCP clients. Of course if you don't
want to use DHCP then you can still hook things up this way and
configure the network manually.

That being said, I have not owned a Mac with two NIC's. However, I
would assume that you could go to "System Preferences" > "Sharing" and
select "Internet Sharing". This should give you the option to "Share
your connection from" Ethernet 0 "To computers using" Ethernet 1, or
something like that. Then maybe it would work OK the way you currently
have it wired. Might be worth a try if you don't want to buy the switch.

-- Scott --

On Mar 25, 2008, at 9:08 AM, dweeks wrote:

>
> "can you bridge the NICS on the Mac?"
>
> That's the question,and I don't know how to do that. I'm still
> searching Google...
>
>
> --
> dweeks
> ------------------------------------------------------------------------
> dweeks's Profile: http://forums.slimdevices.com/member.php?userid=1387
> View this thread: http://forums.slimdevices.com/showthread.php?t=44165
>
>

sgard9
2008-03-25, 11:27
If you want to do ethernet bridging between separate ethernet networks
on the two (or more) NIC cards of the MacPro and share selected
services between them then that should not be a big problem. If I were
going to get involved in this area of more sophisticated multiple
interface networking I would buy a third party solution with a more
user friendly interface such as "IPNetRouterX" from Sustainable
Softworks. I personally have no connection with this company and it
has been many years since I have used any of their products.

-- Scott --


On Mar 25, 2008, at 10:35 AM, Phil Leigh wrote:

>
> dweeks;283455 Wrote:
>> "can you bridge the NICS on the Mac?"
>>
>> That's the question,and I don't know how to do that. I'm still
>> searching Google...
>
> I've searched and it seems the answer is either no...or maybe but it's
> not obvious how to do it!
> I'd get a switch and use a single NIC - much simpler :o)
>
>
> --
> Phil Leigh
>

ebranda
2008-03-27, 12:30
Had the same problem but found a simple workaround using my AirPort Express. Configure the AP Express to *extend* the existing TC wireless network (using the AirPort Utility app to create a WDS -- just follow the config wizard instructions for extending your existing network). Then physically locate the AP Express close to the SB3 and re-connect to the wireless network. From the SB3 everything will appear as it was before the changes, but you should now be able to connect. Worked fine for me the first time.

Cintra
2008-03-27, 22:38
Had the same problem but found a simple workaround using my AirPort Express. Configure the AP Express to *extend* the existing TC wireless network (using the AirPort Utility app to create a WDS -- just follow the config wizard instructions for extending your existing network). Then physically locate the AP Express close to the SB3 and re-connect to the wireless network. From the SB3 everything will appear as it was before the changes, but you should now be able to connect. Worked fine for me the first time.Yes, I started off that way, but went for Time Capsule alone in order to obtain the full 'n' speed.. are you sure you have that!?

MrSinatra
2008-03-27, 22:45
only if he has he new airport express that does n.

but couldn't it work in mix mode too?

time capsule = n and g and the old airport express expands the g range?

Cintra
2008-03-28, 06:07
According to the bug page this would appear to have been resolved today - "Fixed in SB fw 88, TR fw 37, SBR fw 23

The big question now is how to upgrade SB firmware to 88 when the SB is not talking to the Time Capsule network?

I have the latest 7.01 Slimserver software on my iMac.. and fw 86 on the SB.

radish
2008-03-28, 06:13
The big question now is how to upgrade SB firmware to 88 when the SB is not talking to the Time Capsule network?


Ethernet cable?

Cintra
2008-03-28, 06:39
Ethernet cable?
Yes I have one connected now - unfortunately SB is not connecting correctly to Squeezecenter even via ethernet.

It does connect to the Squeezenetwork ok though.

If I press brightness on the remote for long enough, I get a message update_begin:bad state

Perhaps the firmware 88 isn't yet available, or perhaps it doesn't like 7.01..

Has anyone upgraded ok yet?


Edit: I went back to the standard 7.0 Slimserver, with no improvement

Edit2: I installed Slimserver on an XP machine sitting on the same network, and was able to see the Squeezebox ok, and update the firmware. However it still shows fw 86 after the update :-( and I am still unable to access the Squeezebox from the iMac server.

tday01
2008-03-28, 07:59
If so, how do i force an update on these two.


Thanks

Tony

mfitzhugh
2008-03-29, 15:02
I had the same experience as Cintra, finding that after I upgaded to Squeezcenter 7.01 and forced a firmware update (by pressing and holding "Brightness") my player is still at firmware v. 86.

Is firmware v. 88 coming in a future nightly build of Squeezcenter or is the answer more complicated than that?

I'm running a SB3 and my wife made honest-to-goodness faux sobbing noises today when I told her it'd take a bit to get out Squeezebox up and running with the Time Capsule. :-)

radish
2008-03-29, 15:16
fw86 is in builds of 7.1, not 7.0.1. You can download it here:

http://www.slimdevices.com/downloads/nightly/

Note however, that 7.1 is pre-beta and so could be a complete mess :) This includes the fw86 itself, it hasn't been through full testing yet so isn't supported. If you really don't want to wait, you could download 7.1, take out the fw file and put it in the right place in your 7.0.1 installation, then edit the .version file to make 7.0.1 use fw86.

Cintra
2008-03-29, 21:21
fw 86 is the firmware which appears to download with the standard Windows XP version of Slimserver. I certainly have it on my SB3.

What I am hoping to be able to do is update the SB3 to fw 88, which according to the bug report has resolved the Time Capsule issue.

I am able to connect with/use/and update ok on XP which is connected directly to the Timecapsule.

Unfortunately, if I connect the iMac directly to the Time capsule in place of the XP system, I can setup the ethernet network, but SB isn't available according to the browser interface :(


Edit: Well I have come a stage further by running the iMac on my Tiger partition. Squeezebox works fine toward the Time capsule both over wireless and direct ethernet connection, no doubt because Tiger isn't set up to use the 'n' speed.. I updated to v 7.0.1 while I was at it, and re-updated the firmware which still brings down fw86! At least I can run SB over wireless again now if I want.. by booting into Tiger :)

Can anyone say when fw88 may be available? <<<<<<<<<<<

Oops, a bit too fast off the mark there. It worked when the iMac connection was wireless AND SB3 was directly connected to Time capsule, but not when I moved SB3 remotely and tried to connect wirelessly to it :(

radish
2008-03-30, 08:30
You're right, I got the versions confused..sorry! I don't see 88 in any of the available builds yet.

forddonald
2008-03-30, 09:07
Add me to the list of users anxiously awaiting the release of fw supporting Time Capsule. I have to keep a second wireless bridge up just to service the needs of Squeezeing until this is ready.

Like the others, I can connect my Controller to the TC 'n'/compatible network, but the Receiver & Transporter both do not connect (can't get past joining network stage).

r3w2000
2008-03-30, 09:12
How do you find the FW version in the nightly build info for 7.01? I get a 403 when I click the build notes. Thanks.

radish
2008-03-30, 09:37
I downloaded the zip and took a look inside :)

ronnie136
2008-04-03, 08:54
I see from the bug list that the Time Capsule issue has been fixed in Squeezebox Firmware 88, but does anyone have any idea when firmware 88 will be available? What is the usual leadtime between build, I see the nightly build isn't always updated with the latest build.

I currently can't use mine due to the TimeCapsule compatability issue.

Cintra
2008-04-03, 09:41
I see from the bug list that the Time Capsule issue has been fixed in Squeezebox Firmware 88, but does anyone have any idea when firmware 88 will be available? What is the usual leadtime between build, I see the nightly build isn't always updated with the latest build.

I currently can't use mine due to the TimeCapsule compatability issue.

The answer I received a few days ago was:

"The fix I provided works with SB, TR and SBR, but needs
to be verified by our QA team first and if they approve it,
it is planned to include new firmware into the next bug fix
release which would be 7.0.1.

And to answer your next question, no, I have no
information about when 7.0.1 will be released. Sorry."

So, we just have to wait

Mvh

Cintra
2008-04-05, 05:57
I downloaded the latest version of 7.0.1 from the above link and was very surprised when it automatically updated firmware and YES it was fw 88!

So far I have checked it out remotely using Tiger.. am on my way back to Leopard in a very few seconds..

forddonald
2008-04-05, 06:23
Confirmed - nightly build of SqueezeCenter has new firmwares for Transporter (37, up one), Receiver (23, up one) and Controller.

Confirmed - Transporter fw 37 connects to Time Capsule correctly and works as normal. Yea!

Cintra
2008-04-05, 06:30
Confirmed - nightly build of SqueezeCenter has new firmwares for Transporter (37, up one), Receiver (23, up one) and Controller.

Confirmed - Transporter fw 37 connects to Time Capsule correctly and works as normal. Yea!

Are you running Leopard 10.5.2 by any chance?

I am still having difficulty with Leopard. Communication is getting further than before, it gets an IP from Time Capsule but the final 'Connecting to SqueezeCenter' doesn't make it :(

forddonald
2008-04-05, 07:20
No, I use SqueezeCenter on Debian in a VM.

http://www.vmware.com/appliances/directory/1207

Cintra
2008-04-05, 07:25
No, I use SqueezeCenter on Debian in a VM.

http://www.vmware.com/appliances/directory/1207

Ah well, thanks for letting me know..

Anyone else having trouble with Leopard 10.5.2?


Edit I am able to select Squeezenetwork ok with the remote, then I see both Squeezenetwork and Squeezebox in the 'Choose Player' drop down of the localhost:9000 web page, but when I select Squeezebox, I get the "Do you want to leave Squeezenetwork.. Yes/No" window, but saying Yes doesn't connect me with SB, it leaves me in Squeezenetwork.

However, it is a step closer ;) This occurs both on my iMac and MB Air, both on 10.5.2

lagosirio
2008-04-05, 15:34
I came back today from two weeks vacation and made the SC update and the SB3 Firmware update. It was a full success. Seems that all problems have been solved - the WLAN connection is stable and all works fine. Shortly after I even installed the new Time Capsule Firmware Update from Apple.

I am working with iMac 24", Leopard 10.5.2, Time Capsule and SB3 - all wireless.

mfitzhugh
2008-04-05, 20:48
Another success: I just upgraded my SB3 to use firmware version 88, which arrived with a recent nightly release of Squeezecenter 7.0.1. My Squeezebox is now back in action, connecting without trouble to my Time Capsule using WPA2.

Thanks to all the developers. As usual, you folks rule.

- Michael

Cintra
2008-04-05, 23:06
Another success: I just upgraded my SB3 to use firmware version 88, which arrived with a recent nightly release of Squeezecenter 7.0.1. My Squeezebox is now back in action, connecting without trouble to my Time Capsule using WPA2.

Thanks to all the developers. As usual, you folks rule.

- Michael
@lagosirio and @mfitzhugh

Lucky guys! I'm stuck with SqueezeNetwork only :(

May I ask if you have other Apple network devices than the TC in your network?

mvh

lagosirio
2008-04-06, 00:10
I have just the TC and SB3 - no further devices. TC is connected to DSL via a Zyxel 660HW. The Zyxels's WLAN is de-activated.

Cintra
2008-04-06, 00:24
I have just the TC and SB3 - no further devices. TC is connected to DSL via a Zyxel 660HW. The Zyxels's WLAN is de-activated.

Thanks :)

I'm going bananas here.. I currently have just the TC too.

Edit: Breathe again :)
At some time in the recent past I had changed the firewall settings on both of my Apple machines to 'Allow only essential services'.
Changing back to 'Allow all incoming connections' fixed the Sqeezecenter problem!

lagosirio
2008-04-06, 04:21
Thanks :)
Changing back to 'Allow all incoming connections' fixed the Sqeezecenter problem!

Very good - enjoy it :-)

wyzard
2008-04-06, 04:59
Doesn't look like my SqueezeCenter updated overnight. Anyway to force an update? Want to get this running wirelessly.

Thanks.

Cintra
2008-04-06, 05:26
Doesn't look like my SqueezeCenter updated overnight. Anyway to force an update? Want to get this running wirelessly.

Thanks.

you need to download 7.0.1 from http://tinyurl.com/432tm4 and probably need to connect your SB via ethernet to the TC for the firmware update to take place

mvh

milesbeverley
2008-04-07, 02:43
I also downloaded the update and now my receiver connects to the Time Capsule!! So well done to Logitech on solving the issuing. However now I have a second problem. When I connect to my music library on my PC the sound either stutters constantly or on the last attempt it played for 3 seconds then stuttered.

Has anybody had this experience? Any suggestions?

MrSinatra
2008-04-07, 02:47
have u tried unplugging the unit and then plugging it back in after a minute or so?

i have to do that after nearly any firmware update.

milesbeverley
2008-04-08, 23:52
i also have the same problem with the sound stuttering. i have updated to the latest firmware which connects to the time capsule. i have also moved the computer near the time capsule. the receiver is in another room. i am playing itunes ripped AAC files. so everything was working well last night. playing music from my itunes library sounded perfect. however when i tried it this morning (without changing any configurations) the sound either stuttered immediately or played for 10 seconds before stuttering. when i play internet radio or my song files which are stored over the internet (mp3files) these all play well. the stuttering sound doesnt sound like a muting of the sound...it sounds like the computer is struggling to play the file. meaning that the song plays very slowly.

has anyone else experienced this or does someone know a fix?

milesbeverley
2008-04-08, 23:54
and just to answer the previous suggestion, yes i have unplugged the receiver after the firmware update.

milesbeverley
2008-04-09, 11:44
Well it seems that it waa a distance problem. I placed the receiver near to the router and computer. Now everything wors without stuttering. However it isn'tt so useful as the receiver was purchased in orrder to play in another room. So the only thing that works is using MP3tunes to upload my music and stream it down to my receiver. oh, well....

Siduhe
2008-04-09, 11:51
I have a receiver that works over three floors away from my router. Are you in an area of very high wireless interference? How many other wireless networks can you see? Can you change the channel on your router to a less congested one?

Some good tips to improve your wireless connection here:

http://wiki.slimdevices.com/index.cgi?NetworkProblemsSecondGuide

milesbeverley
2008-04-09, 13:33
I tried moving the channel and looked at all the wifi networks near me. I am the only one on that channel. I also installed interference robutness on the time capsule. Tested it and the sound still stutters...

milesbeverley
2008-04-10, 00:13
Maybe the signal needs a boost. However I don't know if it the connection between the PC and receiver or the Time capsule and receiver which needs the boost. Anyone have any suggestions??

milesbeverley
2008-04-10, 13:18
I managed to solve the problem myself. I bought an airport express to extend my network signal and that did the job. Seems that the network signal wasn't strong enough to play from my PC but ok to play from MP3tunes!! Weird.

milesbeverley
2008-04-10, 22:13
Actually the problem came back last night and again this morning. Buying the network extender didn't work. Any more suggestions or tests I can run?

MrSinatra
2008-04-10, 22:19
can you plug the SBR into the airport express's ethernet jack?

milesbeverley
2008-04-11, 01:47
I will try it over the weekend. Another thought occurred to me. The reciever sits next to a cordless digital phone. Maybe that is interferring. I will switch that off too.

milesbeverley
2008-04-12, 10:52
I have now moved the Apple Airport Express to sit beside the receiver. Still stutters. I have also turned off the cordless phone next to the receiver. Finally I have tried connecting the receiver to the Airport using an ethernet cable but all of this doesn't stop the stuttering. i am still confused as to why the internet radio works but the music library doesn't..

milesbeverley
2008-04-12, 10:59
I also moved the receiver downstairs again next to the computer and the music stops stuttering. So there is some interference somewhere but even putting an airport next to the receiver doesn't help.

MrSinatra
2008-04-13, 17:26
what bitrate is the music stored at?

milesbeverley
2008-04-14, 00:28
It is 128kb AAC recorded through iTunes. it shouldn't be a problem to stream. I have now tried streaming the music library from two different PC's running Vista and still the stuttering continues. It is a mystery...

bpa
2008-04-14, 01:12
AAC/M4a file will stutter on PC's running Vista with SATA disks using a NVIDIA adaptor/chips.

There are a number of threads on the subject (usually under the header Stutter / m4a and not this thread title !) - the problem is associated with Quicktime.

Try the faad2 solution described in post 13 of this thread.

http://forums.slimdevices.com/showthread.php?t=41673

If your PC matches the above criteria, essentially install faad2 and edit convert.conf (use Wordpad) to match the lines in the post.

Ignore the comments about mplayer as that was offered as an alternative to faad2.

milesbeverley
2008-04-14, 14:01
Well I tried following the instructions (see attached file) however the sound still stutters... Is the file format correct??

bpa
2008-04-14, 14:13
The format looks correct. If it wasn't correct you'd probably get static noise or no sound.

Did you restart SC ? The updated conf files is only read at SC startup.

Check Settings/Advanced/Filetypes - under the Apple settings - the faad program should be indicated and no Apple type should be disabled.

MrSinatra
2008-04-14, 14:41
bpa is the genius, so i'm sure he'll figure this out...

but i'm curious about something else.

you said net radio is fine. most net radio is mp3. its your local music that is the issue. it sounds like your local stuff is all aac.

is that right so far?

is it possible your aac is drm?

and have u tried just downloading a mp3, or ripping a cd to mp3, and seeing if that has an issue? drm-free of course. (i don't trust "converting" from one format to another)

the idea would be to determine if its the filetype, or maybe something specific about your setup. how is your computer connected to the router btw? wireless or ethernet?

milesbeverley
2008-04-15, 01:36
MrSinatra you have a couple of valid points. I don't have DRM on the tracks I am playing however they are aac encoded. I will try it with an MP3 file and see how it goes. I will also try a direct ethernet cable with the PC (currently it is wireless). Ths should eliminate some of the variables. If I was a betting man I would think that the ethernet cable will solve the problem. For the only reason that the receiver plays the music perfectly when I place it next to the PC.

I will try both and let you know how it goes. thanks for the advice.

milesbeverley
2008-04-15, 01:38
BPA, I did restart the reeceiver but I will check under the settings to make sure the faad was recognised.

bpa
2008-04-15, 01:41
I did restart the reeceiver


Not the receiver - restart SqueezeCenter.

milesbeverley
2008-04-15, 01:44
Sorry, you're right. Will try again tonight. thanks.

milesbeverley
2008-04-15, 14:42
BPA, you identified the problem!!! I bought an ethernet cable and wired the PC to the router. Didn't work. Then I tried ripping a song to MP3...that did work! However my whole library is in AAC format. So i tried the faad option. stopped and restarted the SC server and now it works!!! Thank you all for your help.

Will Logitech bring out a fix in one of it's beta releases??

If I install another beta SC release do I need to again replace the convert.conf file?

bpa
2008-04-15, 15:05
Will Logitech bring out a fix in one of it's beta releases??


It's not a Logitech or SC problem - it's a QuickTime/Nvidia/Vista problem. If you try to play some file with Quicktime you may experience delays or stutters.



If I install another beta SC release do I need to again replace the convert.conf file?


Create a file called custom-convert.conf same format as comvert.conf but just with the new "faad" lines. Put the custom-convert.conf file in the same directory as convert.conf. The custom files are left alone between upgrades and the custom setting override the convert.conf settings - so SC will then keep using faad with each upgrade.

milesbeverley
2008-04-15, 15:24
I think I spoke too soon. The stuttering is back. Not as bad as before but it is still there. Hmmm. This isn't goinn to be easy. I will have to try the MP3 file again to ssee if that stutters now.

milesbeverley
2008-04-15, 15:38
well it seems the songs are playing again without skipping. Maybe it was a glitch. I need to do some more testing over the next days.

bpa
2008-04-15, 15:51
Stuttering is a common symptom with a variety of causes. You may have had two issues. Does the stuttering affect all AAC files or just a few ?. When it occurs in a specific file - does it occur in the same place ?

You could do a bulk convert AAC to MP3 using a command line something like in a bat file
faad -w inputfile.aac | lame - outputfile.mp3

However there will be a loss in quality - it would be better to solve the underlying problem - otherwise it may reappear in another context.

milesbeverley
2008-04-15, 22:57
to limit the variables when testing i have only tried a few songs. the stuttering can occur within 10 seconds however when i use the faad app it normally takes longer to stutter and the stuttering isnt so bad as it was originally.

this morning i tried again abd the stuttering was back. i stopped the tune and moved the airport express near to the logitech receiver. the song seemed to play without stuttering. while playing the song i turned off the airport express and no stuttering occurred. it could be coincendence or it could be the buffer playing out. i will probably need to test it more. the faad solution definitely helped but it may need a combination of fixes for it to work.

milesbeverley
2008-04-16, 22:44
i tested again with the faad configuration and also the airport express near the receiver, and using the aac files. no stuttering so far. so it might be the combination of noth that works.

stranfe thing is that the controller showed full signal near the airport express however after the nightly software update the signal is low. do i need to reconnect the controller or receiver to the network?

pgrashof
2008-04-28, 10:59
Hi folks,
also just bought a time capsule to get the 'n' wireless standard. I own a squeezebox version 1 and also have problems connecting to the time capsule. It only seems to work without encryption. For the SB3 there apparently is a firmware update to fix the issue, but I haven't seen firmware updates for SB1 for quite a while. Are they still being developed? Any other suggestions to fix the problem?

Eric Seaberg
2008-04-28, 12:36
I've been running an SB3 on an Extreme Base Station w/Gigabit for many months! It's certainly been 802.11g at it's BEST, since it won't see 'N'. Regardless, I've made it work and NOT had issues with sync to a Transporter (unlimited wired bandwidth) running Squeezecenter 7.0.

Can I help with anything else?