True, but it’s not important for me....and Core has no WISA capability. :/ That's what's a showstopper for me.
Location: Sweden
My B&O Icons:
True, but it’s not important for me....and Core has no WISA capability. :/ That's what's a showstopper for me.
Location: Sweden
My B&O Icons:
Just add a transmitter 1....and Core has no WISA capability. :/ That's what's a showstopper for me.
Yes - but in an integrated setup it is disabled!I think it’s because the integration uses the nl protocol so it’s similar to nl multiroom.For Airplay 2 to work in the integrated setup, multiroom for Airplay has to be selected on the Core, but there is no possibility to enable Chromecast for multiroom in the Core setup.Specification says “Chromecast built in” and I have seen videos where the core is added to Google Home.
Location: Copenhagen
Hmm.... that was one of the main reasons for planning a swap to Core.Yes - but in an integrated setup it is disabled!I think it’s because the integration uses the nl protocol so it’s similar to nl multiroom.
Location: Sweden
My B&O Icons:
Just add a transmitter 1.
Well, thats an extra box to hide, more cables, extra power socket to find and 400EUR to add.
I always wondered what made B&O adopt WISA, and then drop it on its one single available music system? While all speakers - both standalone and integrated ones have it.
I have integrated the BV14 with essence Mk2 so i would say you can do it
On the app it doesn't show the essence since they are integrated. It shows the BV14
In a week I will pickup a Core (IR-capable) including IR eye.
The IR-eye are the classic B&O, but with new internals.
I´m not sure in what usecases you actually have reason to sent IR commands to Core (when integrated to my BV-11).
Volume control I assume goes through the BV-11.
Choosing e.g "MUSIC" on the BR1 remote from standby maybe trigger Core first and then wakeup BV11.
Anyone knows?
/C
Location: Sweden
My B&O Icons:
I have a Core integrated with my BV11.If you have assigned a key or command correctly on the BV11 (either Beo4 or BR1) to point to “MUSIC” on the Core it will wake up the BV11 when activated. I don’t see a need for the IR-eye as all the relevant commands for the Core is routed through the BV11 including volume control.In a week I will pickup a Core (IR-capable) including IR eye. The IR-eye are the classic B&O, but with new internals. I´m not sure in what usecases you actually have reason to sent IR commands to Core (when integrated to my BV-11). Volume control I assume goes through the BV-11. Choosing e.g "MUSIC" on the BR1 remote from standby maybe trigger Core first and then wakeup BV11. Anyone knows? /C
Location: Copenhagen
In a week I will pickup a Core (IR-capable) including IR eye.
The IR-eye are the classic B&O, but with new internals.
I´m not sure in what usecases you actually have reason to sent IR commands to Core (when integrated to my BV-11).
Volume control I assume goes through the BV-11.
Choosing e.g "MUSIC" on the BR1 remote from standby maybe trigger Core first and then wakeup BV11.
Anyone knows?
/C
I have a Core integrated with my BV11.
If you have assigned a key or command correctly on the BV11 (either Beo4 or BR1) to point to “MUSIC” on the Core it will wake up the BV11 when activated.
I don’t see a need for the IR-eye as all the relevant commands for the Core is routed through the BV11 including volume control.
Yes, that is my thought.
I will give it a try and potentially return the IR eye if not needed.
Location: Sweden
My B&O Icons:
I have one BV11 integrated with a Moment, and another BV11 (different location) integrated with a Core ... and like you ... I'm weighing up the pro's and cons of both approaches.
You can setup speaker groups on the 11 and integrate the Core, so it is mapped to a BEO4 button or a BR1 button. The big difference is that when integrated, the CORE is removed from the App product view - so you can't get back to it's setup/config screens - eg. to change the line-in sensitivity. The moment - when integrated - stays in the list, and you can still control it / choose a input (bluetooth / line-in).
I love the design of the Moment, but rarely use the jukebox/tablet aspect of it, but it does allow casual users to play music without the need for an App - which I'm guessing is why they have this different approach?
I may switch my Core and Moment deployments between locations, because one is more likely to have 'casual' users than the other where an App is fine.
Best of luck with your tinkering ...
You must be logged in as a BeoWorld member to post replies to forum threads.
Register to access the forums, reference material, and exclusive member benefits — including our monthly prize draw.
Become a Member