Annual Request: Do NOT Activate Project When Closing Project

[suntower]

If you have multiple CPRs open and you close one, the next one automatically activates.

MADDENING!

When I have several CPRs open at once and I close one I OFTEN may want to choose to open ANOTHER CPR that is NOT from among the ones I currently have open.

So I have to wait for Cubase to load up the next underlying CPR.... which in my case may take several minutes. I say again...

MADDENING!

This is the kind of teeny, tiny change that -should- be attended to in a .0x release.

[dmbaer]

What, you don't trust Cubase to know *exactly* which CPR you want to work on next?

Seriously, there's no justification in any sane world for this design decision. If one uses heavy-duty Kontakt instrumentation, load times can be excruciating. Please fix this immediately, Steinberg,

[suntower]

Sadly, I was fired right before the mind-reading beta cycle back in 2005.

---JC

What, you don't trust Cubase to know *exactly* which CPR you want to work on next?

Seriously, there's no justification in any sane world for this design decision. If one uses heavy-duty Kontakt instrumentation, load times can be excruciating. Please fix this immediately, Steinberg,

[Prock]

My annual +1 for this

Regards

[suntower]

And what REALLY makes me APOPLECTIC? I'm about 100% sure it would take the dev 5 minutes to implement this feature. I mean what's to do.

if ( pref )
load_project() // current code behaviour
else
// do_nothing

... I mean... WHAT'S TO DO?

[Stephen57]

+1

It would be more helpful to have a preference option to 1) do nothing and let me select which project to make active, 2) activate the last opened project. I agree. Not activating the previously active project would be a better default.

[Svengali]

+1

[Evertone]

+1
This would be nice!

[profezeus]

Absolutely +1

Such an option would be really convenient.
I lost a lot of time because of this.

[RichardTownsend]

+1

[alexis]

+1

I think the workaround is to never close a project, just keep opening new ones? I can't imagine that ends well during long sessions, however ...

[djw]

+1

[mozizo]

+1

[In_Stereo]

+1

[DTS Recording Studio]

+1

[peakae]

+1

[Outspan]

+1

[dbh]

+1 drives me nuts too..

[john charles]

+1

[grossecoulisse]

+1 2019

[mitchiemasha]

This is the single most annoying thing that makes me want to die every time it happens. People complain about accidentally clicking the loop on and off but it's nothing compared to closing a project and forgetting you had another one loaded or even worse, it reverts to the 1 you didn't want. The sense of dread, the NOOO! as you await the load bar you had no desire to finish.

PLEASE STEINBERG REMOVE THE AUTO ACTIVATION OF UNDERLYING PROJECT.

Make it do nothing... we can then simply click the activation or x, of what ever we require.

[suntower]

The -really- frustrating thing?

There is a backlog of about 50 requests like this... requests that a decent developer could knock out in a couple of days... that go untouched for TEN YEARS.

[profezeus]

Just want to quote a post I've written in another thread (hope it helps somehow):

"Yes, this is annoying but I use a workaround for this.
I always start Cubase/Nuendo with a blank project than open all other loaded projects that I’m actually working on. Whenever I close any project, I don't need to think about which will be activated next, the blank project gets activated automatically in a second, then I can choose which other loaded project I want to activate.
It always defaults to the first blank project.
This can save you a lot of time."

[mitchiemasha]

What about if multiple have been opened? Does it always revert to the first empty project? I can't see me doing it but that's genius.

[profezeus]

Yes, it always reverts to the first empty project. It does not matter how many projects are open at the same time.