Controlling both devices does not seem a problem, when you are streaming you’re not playing a disc and when you are playing a disc you’re not streaming. So one of the two is in stop mode.
Maybe I overlook something, I don’t own the transport.
sorry if I keep nagging on about this ( I promise it will be the last time) but pushing a real button is so much more convenient then picking up an ipad.
Is it correct to assume that the IR code set for a given transport is defined by the OEM who manufactures the mechanism? If so, wouldn’t the same remote work for the Rossini Transport and the Vivaldi Transport II (since these use the same Denon/Marantz M3 mechanism IIUC)?
If that’s true then it would seem strange that they use different RS-232 code sets but ho hum!
Hi @struts001
No … that’s not the case.
The same IR remote codes work for all dCS disc transports (whether CD only or SACD capable) going all the way back to the Verdi.
The RS232 commands are consistent and are documented in the Remote Commands document downloadable from the support area but the way that the Rossini DAC and Rossini Transport talk to each other by RS232 (two devices on an RS232 connection) is different to the way that the Vivaldi Transport(s) / Upsampler & DAC talk to each other (three devices on an RS232 connection) because of the split between Upsampler and DAC (hence the way that the commands are issued and replied to is different) … so Mosaic has to handle the two differently and a Vivaldi Upsampler being used with a Rossini Transport or a Rossini DAC being used with a Vivaldi Transport are simply not supported combinations by the Mosaic app.
I hope that helps.
Phil
I see. Thanks!
Phil, understood. Which is why, if possible, it should be up to the DAC to decide how best to handle the received IR transport control button presses;
When @ AES 1+2 → control Transport
When @ AES 3+4 → control Streaming
That said, I can’t think of any other button presses that get translate into a REST call. So, there’d need to some significant development associated with that, which would be tricky I guess.
Probably easier to do this with one of those new generation of Remotes that supports IR, IP and Bluetooth, all in one, like the Remote 3
As an aside from the original discussion I’ve been looking at that remote for myself too and it looks lovely but I’m really wary of plonking down what is significant money on something that can end up a brick after a few months … I have an original Neeo Remote and that is a superbly built, fantastic looking and feeling bit of kit that - very soon after its release after a Kickstarter campaign - was bought out by Control 4 and left all the original owners and backers that had sunk significant money into making the original unit exist totally hanging.
Logitech couldn’t make the Harmony remote “pay” long term (if it had done then they wouldn’t have discontinued it) - I have several of those now not doing anything.
Even the oddball entity that is Philips had to call time on their Pronto lineup, again I have several of those now sat gathering dust.
As far as the Neeo is concerned the last remaining hope that I have for it is this…
sigh
Too true. Likewise, it was a pity when Senic couldn’t make the business case fly and discontinued the Nuimo remote, even though at the time it was pretty revolutionary in simplicity and user-experience and demand far outstripped supply.
Here’s the issue:
Remotes simply don’t work that way unless the capability specifically was designed in from the start.
Without a communications bus, each component with an IR receiver is programmed to only recognize commands for that component. “Pause” means something to a transport, not to a DAC (What would it mean, stop playback?) Worse, if multiple components interpreted the same code, without a communication bus whose interpretation would win?
Remote programming in an audio component is generally burned into read-only firmware - not updatable firmware but good old ROM. Even if it’s flash, there’s likely no mechanism to update it. This is like the way programmable remotes generally can control a certain variety of components - and no others.
So sure, you can say in hindsight that “these keys should mean these things in these modes,” but unless the entire system was designed to communicate way the start, it can’t be changed now without an APEX-like hardware upgrade program.
The controls are all on one remote as a matter of convenience - “If you buy this other component, these keys will operate these functions on those components.” This is true for system remotes for most brands. The remote for my Ayre preamp has keys that mean nothing to the system because I don’t have an Ayre CD player.
It’s not reasonable for remote keys never meant to be recognized by the upscaler, even if it has an IR sensor, to control streaming.
There’s simply no way to get there from here.