macbook m1 big sur node unpredictability
Beantwortet
My 2 nodes are totally fine (very high internet speed, etc) when casting music to them via iOs devices (iPhone, iPad) but I got a new MacBook with an m1 chip and running Big Sur and it's not good. (Old MacBook was fine.) Basically it sometimes works for a little while and then just stops. Or it plays the first ten seconds of a song and then no sound. If I shift over to computer audio, it's fine. It just can't cast to the nodes consistently. I've been through every single potential wireless and apple problem so I'm asking if others are aware of this. For now, I just have to play music through an iOs device, not my laptop.
-
Thank you. Yes to all; been through many paths. Am assuming eventually it'll get sorted but will submit a ticket if I can figure out how.
0 -
Airplay...now there's a thing. I have been struggling to connect a large iTunes library to the Node 2i using SMB networking, a fiddlesome and so far unsuccessful task. Now I look at Airplay and there is the Node 2i, clear as you like. I wonder if this will work?
Update: no
1 -
When a BluOS Player is selected directly from the list of Airplay compatible devices in the Apple Music app, lossless audio is converted to AAC at 256 kbps. As a workaround, when the system-wide audio output on a Mac is set to a BluOS Player, the AirPlay Content is sent up to 16 bit 44.KHz using ALAC or Apple Lossless.
To change the system-wide audio output in Mac, perform the following steps on your Mac:
- Select Control Center in the menu bar.
- Select the Airplay icon under Sound.
- Select the required BluOS speaker.
- Open the Apple Music app, select the Airplay icon in the upper-right corner.
- Select Computer ––> (BluOS Speaker).
Alternatively, to change the audio output on the Mac – click here.
The Apple Music app will now stream bit-perfect lossless audio to the BluOS Player.
0 -
Gosh that is a quick intervention, Tony W! This appears to be one way of getting at it. (This older Mac with the Library still on iTunes, though the main machine is an M1 chip macMini like OP's case.) But as Seppi Evans suggests, even before you came in, I would rather use the Android controller if I possibly can get the SMB config right — that's what I've been fiddling around with all morning, oh and quite a bit of the afternoon now too, it seems.
Thank you for stepping in here — I wd say I like the way the Node 2i sounds into the mighty Naim system, it is far from disgraced, tho I was not expecting to have to work the configuration so hard. It's a constant battle between ease of use and security isn't it?
0 -
I figured that workaround, too, Tony W. The problem with it, using a MacBook, is that you then can only select one node. Again, I can use multiple speakers if using airplay from iPhone or iPad.
0 -
Unf this workaround doesn't. AirPlay sees the Node device but won't address it. According to the Apple crashlog, the audio device control (thread 30) has fallen over with a kernel invalid address. (This is in the older Mac, V10.11.6.)
Back to mono?
0 -
If you do prefer a Local Library - we have been doing that for some time - if the following KB does not help; https://support.bluos.net/hc/en-us/articles/360000197008 - please select Help, Send Support Request in the BluOS App.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
7 Kommentare