I have Nuage working fine with Nuendo but I can’t get Cubase Pro going at all. This hasn’t been an issue before but I now find myself needing to use Cubase occasionally.
Cubase is registered in the Workgroup Manager as DAW B and is successfully detected in the workgroup when opened.
However, the Nuage controllers don’t pick it up. The only Nuage menu item in Cubase is the Nuage HA option - nothing for the I/O, fader or master as there is in Nuendo. Pressing the DAW B button on the master/fader does nothing. I’ve double checked the firewall entries and they’re identical to the Nuendo entries.
Anyone shed any light on what might be the problem?
On an unrelated note, if anyone is running the Nuage Nio500 I/O’s I have a few workflow questions if anyone would be kind enough to engage in a few PM’s. Thx.
What if you remove Nuendo from the Workgroup manager, (Arrow down, but Nuendo in de lower section), and then move Cubase “up” as only DAW.
Fire up Cubase and see what happens.
Thanks for the pointers. It didn’t work quite as you described but going with similar theory I finally got it figured out.
Cubase won’t operate as DAW B (as it’s described in the courseware). Basically, if I remove Nuendo and Cubase from the Workgroup and just promote whichever one I want to use in there once it’s open (which automatically goes in as DAW A) the controllers pick it up & I get my full Nuage menu & saved settings.
Well one of them would have to be Pro Tools I guess and that Mac would also have to run Nuendo as the bridge. You would have DAW B available for another computer though. Pretty sure that’s how it works.
I thought I’d be able to run Nuendo or Cubase on the same machine once they were in the workgroup (not at the same time) but you can only have one of them in there.
Yes, that is correct.
Nuendo, Cubase and/or ProTools.
Very handy in a typical Post-setup, where you are mixing one one machine (or multiple) and recording the mixes/stems to another machine.
That other machine is often ProTools.
You can get other DAW’s in there, I have successfully used both Audition and Reaper on the Nuage. Implementation is, of course, limited but you can ride faders which is nice. john
Hi,
I see that you get Reaper working on the Nuage system.
Is it posible to tell how you did this?
And can you tell me about how to configure it, maybe send me the configuration?
I won’t be going in to the studio today but I’ll look next week, I don’t remember the specifics of setting up Reaper as it took some work to make that happen, Reaper is not controller friendly in my experience. Audition was simple but it has been awhile, I’ll double check that one next week also and report back. john
Hey folks! So to get Reaper working on Nuage I added two HUI (partial) setups from Reaper>Preferences>Control/OSC/web. One is set to “HUI(partial) (dev 0,0)”, the other is “HUI(partial) (dev 1,1)”. The quotes are from me, the rest of the syntax is how it appears in the Reaper Pref’s window. It then shows up as a Protools selection under DAW B in the Nuage Workgroup Manager window.
For Adobe Audition, I haven’t used it in quite some time and am not having any luck getting it to work.
This is clearly a bug which will never be resolved properly since Yamaha’s brilliant management decided to screw the Nuage community and drop the product. Wait, you say support will continue for 5 years. Well if that is the case, fix this so that DAW A is Nuendo and DAW B is Cubase. This is how it should work without having to do work arounds!