ekohn00

Do you actually stream 4 separate streams? ie have 4 logins? Nothing wrong with that, just wondering as I believe sirius is one stream per login.

go digital coax from the control4 controller to the anthem. it will use Anthem's DAC. or just bypass C4 altogether with something like a bluesound Node (my latest toy and it's worth it).

Great info to know. And as LED lighting keeps getting more advanced it might be worth getting the regular line.

Based on the number of switches in this house, 15 years can bairly pay for them.

With an Anthem Reciever, why are you even relying on the C4 Controller's DAC?

Sadly I've been living with the model from 15 years ago and cursing any time a builb humms...... Not that i know its only $100, time to consider some updates...

My wife noticed the bluesound was amazingly better than just using C4, she thought i got new speakers. now i have to get another one for house.........

you're using the Anthem's DAC and as such it may be designed for better audio performance on the COAX vs HDMI. This is more of an Anthem question then C4...

Turn off HDMI/ARC and let Control4 turn off the receiver

This is half right. The driver is bound to the core. That allows you to only select music, and the core to know to stream to a device. However, the driver also needs to be bound to an audio end point. If i was doing this as roon only, that would be input-1 on my amp. This is exactly how i did my main connection. you don't bind it to the dac but the dac's endpoint. The twist is I wanted to also use the bluesound node to stream other sources using the bluesound drivers. And i could bind both the bluesound and the roon to the amp. I did find 2 work arounds, as I could actually find away with all the suggestion on universal adapters. 1. Looks like I can use the roon driver and just bind it to any unused device. This way the roon driver goes to the node and lets me select the music i want, but won't interfere with the blusound drivers bindings. I can then use the bluesound driver to select my streaming sources. 2. I guess i can use a Y cable from the bluesound and have the one bluesound port connect to both input 1 & 2 of my amp. then bind bluesound to 1 and roon to 2. (still need to test this as I amenot sure what sending streams to an unused port will do overall.

The zone driver controls the core but becomes the binding for the dac. In my case that’s the Bluesound, but I also bind the Bluesound drivers. however, you just gave me a great idea. I can use the Roon zone driver to control roon for my Bluesound and just bind it to any unused input, but never physically connect it. so my Bluesound works as planned, and I can now change my Roon music with Roon driver

I used to do the nice cheap free server methods. Used Plex for all my music. then I looked at Roon. In short it brings 2 things: 1. A fantastic visual library experience through the Roon app. By far! The metadata is just amazing. Basic albums, live albums and classical was best handled in Roon. not a big deal if your just storing files and folders - though the search and organization is pretty amazing to have with Roon 2. audiophile sound - so Roon really focuses on getting the best sound performance. There’s a lot about getting data to a dac over the network - they also added an app for CarPlay. So if your using the Node, I can tell the difference between Roon direct and Roon via airplay they have a Roon demo for 2 weeks, check it out and let me know what you think

Mine as well. As a nice surprise they updated the firmware yesterday for the Node 130 and it now works with Roon Ready.

i don't think that would work. it's still a 1:1 in to out. it allows me to mix differnt connections (hdmi to rca). I would basically need a way to select between 2 drivers, but only have 1 physical connection (bluesouind to C4 Amp).

I had a chance to play... So basically on the phone it's easy. I just wish there was a mini-driver for airplay. In order to get C4 to be aware that your phone is using airplay you need to select either one of the mini drivers (before airplaying) or the main driver. this could be a bit cleaner had there been a airplay mini driver.

there's a binding problem... the bluesound has only one audio out.... in my scenario I can't even bind both as far as i can tell.

The bluesound is roon-ready, but when using the Blusoud drivers, you must control Roon with the Roon APP. I'd like to also control roon from my T3 screen, as if I was just using the roon driver. I'm wondering if there's a way to "trick" the system to allow a 2nd driver. Roon drivers control Roon core so no app is needed. However, the driver can't bind the same connections as the bluesound driver so they can't work together, at least not that i can tell..... The kicker is I also want to use the bluesound driver to work with other streaming services. Looking for any tricks...if they exist. thanks.

No sir. Topic is bluesound. I'm using the bluesound to keep life and connections simple. It's capable of airplay, so the question is how do you select the bluesound off the menu when using Airplay.

Dumb question, how is everyone making a selection when using Airplay - need to make this wife proof when she streams music from her iphone. thanks.

Will check that out. Thanks.

I said I blame the drivers. At least I can work it through the main driver for now. after a couple of upgrades we can try again.

From what I can tell, The mini-driver in the pool music room aren’t working. I can go to node - and then select the music service. That seems to work. strangely if I go to the pool bar and select a mini driver, I get that error I showed you and then it plays the mini driver.

Mitch did some great work, but the Bluesound is very quirky. I hate to tell him it’s not working as planned - I blame blue sound’s drivers. oh and if anyone is using Roon, definitely don’t update your Bluesound firmware now.

check again, latest is 3.2 online. but don't install, who knows maybe that's why mine isn't working. I also found out the latest firmware kills roon ready.

All good. I am thinking there's a driver version problem (maybe), when i click on the driver it shows 3.0.1, but strangely it shows 3.2.0 in the properties. I did a hard reset this morning, no joy. Also backed down the Firmware on the Node, since there is a Roon problem, still No Joy.