Just curious here,
The dialog asking you if you want to activate the project when loading it. Do you ever answer No to the question? If so, what is your workflow in which you don’t active on load?
Thanks
Bernard
Just curious here,
The dialog asking you if you want to activate the project when loading it. Do you ever answer No to the question? If so, what is your workflow in which you don’t active on load?
Thanks
Bernard
I asked an AI and it says: If you don’t activate the project in question its tonality will be changed from major to minor and vice versa.
That, of course, was just made up nonsense .
Actually, this is a valid question:
If I didn’t activate the project I could see what’s going on in there but not hear or work with it because only one project can be active at a time. In other words, if I merely needed a quick visual overview to get the infos I was looking for I would go with this option.
Hope that helps
Just to add to this, you can actually work in and even save your “un-activated” projects’ “project window,” the transport controls will only apply to the active project, and none of the plugins or audio connections will be activated. Mix Consoles, etc will launch for the active project. I use it to copy events/parts/tracks etc from other projects and it works great. On a Mac, you can actually have Cubase and Nuendo both open and active at the same time, and can copy and paste between them
You are right and this is a very important point- thanks for chiming in
!
I never changed anything in the non-active project because on Windows you can’t hear what you are doing - it’s like flying blindfolded. From what I read it is the same on a Mac, right?
Yeah, I use it the same way: Getting the infos I need and if I want something from that project I just copy and paste it to the active project right there and then.
Haha, I am not sure if we define “active” the same way. For me, an active project has to be not only accessible on all levels but it must also provide an audible feedback. I do not claim that this is the universal definition of “active” - it’s just my personal definition of an active project
Your definition is as good as mine or better!
Yes sir, plugins and audio connections are detached in all but the “active” project. So indeed, it’s in the blind, but it’s nice when you’ve got a “work” folder with a bunch of tool-belt items, tracks, etc that you may like to use a lot but don’t want to build out a template for it. That way you’ve got a deactivated project to copy stuff TO as well for safekeeping if you want
I meant the explicit Cubase/Nuendo meaning of “The One With The Lighting Bolt Activated.” And in your sense, yes, it’s the ONLY project where you can do that (AFAIK).
P.S. My presumption is that this use-case is why you can’t get the MixConsole view of an inactive project - so that you’re “safe” to muck about and not mess up your production, active project.
Okay, I was under the misconception that you defined active as both projects having the lightning bolt activated at the same time. As I am not on a Mac my knowledge in that area is limited…
Is this the one where Joey believes that whenever he touches the lightning bolt on his new sneakers he can run at the speed of light until Phoebe overtakes him in the park?
OH sorry, I misunderstood to which you referred: So BOTH are true - my previous statement that within Cubase OR Nuendo, only one project can be “active” (lightning bolt) at a time. If running Cubase AND Nuendo apps at the same time, each app has an active project, and yes, on a Mac you can play them literally at the same time. As in, I could have Cubase playing 3 tracks and Nuendo playing 3 tracks and if you synced them properly, you could mix them both simultaneously - at least with my UAD hardware (but that’s how Core Audio works, even though it’s labeled as ASIO). I wouldn’t do that, but I could. That I don’t normally do. But I almost constantly have Live and Nuendo open at the same time and feed my Live signal out via UAD virtual channels (64bit) into Nuendo. It’s awesome.
Ah, I see… yes, now I understand what you meant! Thanks for the explanation
@enigmus First of all, sorry for polluting this thread with all these hickups. @Thor.HOG pointed out an important use case that might not have gotten the attention it deserves: You can also use “ghost projects” to store your favourite tracks, presets etc and open the project passively as a toolbox >
Since each Cubase installation is independent you can launch both Cubase 13 & 14 at the same time and each can have their own Project active. And if your audio interface allows even hear both simultaneously.
A few versions back I copied the Cubase.exe in the same folder and gave it a slightly different name. That worked too and let me have 2 copies of the same version open and functioning.
This was all on a PC.
Thanks @raino , that’s good to know!
But whenever deadlines are involved I would not dare to tempt fate…