Cubase 7.5 official announcement!

[LGK_Dude]

The thing that is worrying me though is the rack itself.
I think the warning (years ago) that the "rack" might be dropped eventually could turn into a reality real soon. Because the Instrument Track is now massively enhanced and actually more intuitive. Which is also similar to how instruments are loaded in Logic.

Just from the videos alone, I ask myself "do I really need the Rack Instance and MIDI channel combo anymore, if the Instrument Track can do the same and then some?"

By that I mean the Quick Controls. Obviously the main difference between the Instrument Track and the plain Rack Instance, will be the Quick Controls (currently). Else - both rack types can now have individual outputs (and unlimited at that as well - depending on the VSTi), and both the instrument track and instrument rack instance can be accessed with several MIDI tracks. So the plain rack instance might stay for a while for plain backwards compatibility issues - and then ultimately dropped. Which is now pretty much apparent.

Unless, and this is what wasn't shown so far, there is a reason to keep both other than compatibility. Something that only the rack can do and the "instrument track" instance can't? We don't know yet.

You make great points, and I really hope someone who knows might be able to answer them, or at least clarify a bit.

[SJ_Digriz]

The thing that is worrying me though is the rack itself.
I think the warning (years ago) that the "rack" might be dropped eventually could turn into a reality real soon. Because the Instrument Track is now massively enhanced and actually more intuitive. Which is also similar to how instruments are loaded in Logic.

Just from the videos alone, I ask myself "do I really need the Rack Instance and MIDI channel combo anymore, if the Instrument Track can do the same and then some?"

By that I mean the Quick Controls. Obviously the main difference between the Instrument Track and the plain Rack Instance, will be the Quick Controls (currently). Else - both rack types can now have individual outputs (and unlimited at that as well - depending on the VSTi), and both the instrument track and instrument rack instance can be accessed with several MIDI tracks. So the plain rack instance might stay for a while for plain backwards compatibility issues - and then ultimately dropped. Which is now pretty much apparent.

Unless, and this is what wasn't shown so far, there is a reason to keep both other than compatibility. Something that only the rack can do and the "instrument track" instance can't? We don't know yet.

I was wondering the same thing. But, notice that instrument tracks are now in the rack! This leads to a couple of thoughts. Rack Presets, which would rock. And, people have bitched about the lack of routing capabilities on the Instrument Tracks. This potentially allows that level of configuration.

So basically, the rack becomes an intermediary configuration window for VSTi. A little more control/config for routing and automation in a unified interface. Stuff that is neither the VSTi directly or a editing capability of the track.

I don't know how well it will work, but it does have some interesting possibilities.

[Guillermo Navarrete]

Hello all,

I am glad to see so many positive comments about the update.

I would like to clarify on somethings that have being coming up around the web:

1) Due to the new multi-output / multi-input instrument tracks, we also enhanced the Instrument Track preset feature by the capability to store and recall all of the VSTi audio returns (incl. Volume, Pan, EQ, insert FX, etc settings) belonging to the Instrument Track as well as all connected MIDI tracks. Here is a practical example: you could save and load a HALion Sonic SE Instrument Track making use of each of the 16 slots, each with its own audio return channel and each connected to its own MIDI track in one Instrument Track Preset. Be aware however, that group channels that are connected to a VSTi audio return channel are not saved in the Track Preset (yet).

2) The 7.5 update will be available from December 4, 2013, from Steinberg dealers worldwide as a boxed version and in the Steinberg Online Shop as a download version. While the boxed update includes 3.5 GB content and requires a 500 MB application installer download, the download update version available through the Steinberg Online Shop requires the download of the content as well as the application installer (4 GB download).

EDITED: Minor Typo.

Best regards,
GN

[fmr]

Hello all,
...
2) The 7.5 update will be available from December 4, 2013, from Steinberg dealers worldwide as a boxed version and in the Steinberg Online Shop as a download version. While the boxed update includes 3.5 GB content and requires a 500 MB application installer download, the download update version available through the Steinberg Online Shop requires the download of the content as well as the application installer (4 GB download).

Best regards,
GN

Hello Guillermo. You didn't answer my question. Will the upgrade price for version 6.5 users raise from the current 199,00 euros, or will it remain the same?

[Guillermo Navarrete]

Hello,

Hello all,
...
2) The 7.5 update will be available from December 4, 2013, from Steinberg dealers worldwide as a boxed version and in the Steinberg Online Shop as a download version. While the boxed update includes 3.5 GB content and requires a 500 MB application installer download, the download update version available through the Steinberg Online Shop requires the download of the content as well as the application installer (4 GB download).

Best regards,
GN

Hello Guillermo. You didn't answer my question. Will the upgrade price for version 6.5 users raise from the current 199,00 euros, or will it remain the same?

I am sorry but I cannot discuss the pricing policy.
EDITED: The price changed on the 15 of october from 149 to 199.
So now the upgrade from Cubase 6.5 to Cubase 7 should stay in 199.00.
May I ask why do you want to know? Maybe I can explain it better.

Best regards,
GN

[SJ_Digriz]

Be aware however, that group channels that are connected to a VSTi audio return channel are not saved in the Track Preset (yet).

ok ... grumble ... that's what it looked like.

I can assume this is on the todo list? We really need to be able to just select a group of tracks, regardless of type, and save those as a preset, folders and all.

Question: Can we save the entire (t)rack as a preset?

[Guillermo Navarrete]

Hello,

Be aware however, that group channels that are connected to a VSTi audio return channel are not saved in the Track Preset (yet).

ok ... grumble ... that's what it looked like.

I can assume this is on the todo list? We really need to be able to just select a group of tracks, regardless of type, and save those as a preset, folders and all.

Question: Can we save the entire (t)rack as a preset?

Do you mean the VST Instrument rack?

Best regards,
GN

[SJ_Digriz]

Do you mean the VST Instrument rack?

Yes, if I load 20 instruments into the rack with all the QC and routings the way I want, can I save that entire instrument chain as a single preset?

[Guillermo Navarrete]

Hello,

Do you mean the VST Instrument rack?

Yes, if I load 20 instruments into the rack with all the QC and routings the way I want, can I save that entire instrument chain as a single preset?

For the VST instruments that have a special integration with Cubase it will recall the Quick Control that you have setup in that particular instrument E.g. HALion 5 or HALion Sonic 2. But for the rest, the next time you load the instrument it will recall exactly the Quick Controls parameter assignments that you have previously set up on the VST Instrument Rack. So these are stored globally.

Best regards,
GN

[Compyfox]

So the new Instrument Track does make the Instrument Rack instance pretty much obsolete, especially if it's further developed with C8 paid public beta (read: C7.5) and C8 itself.

So I assume, the rack instance load capability will be(!) eventually dropped.


Just one thing that is troubling me (aside from my still remaining Q's)...

hile the boxed update includes 3.5 GB content and requires a 500 MB application installer download, the download update version available through the Steinberg Online Shop requires the download of the content as well as the application installer (4 GB download).

There was a load of critism towards the core installer process, which was actually dropped with more recent ISO's of Cubase.

Why continue insisting(!) on the core installer for either version (Download or Boxed)? Especially for those rigs that are not online.

This is an unnecessary additional step of copy protection - especially since all USB Elicenser bound software wasn't cracked for years now. It's just jumping yet another hoop.

I just want to pop in my DVD, install and work. Just like old days. So why remove that step in more current ISO versions to ultimately remove it again with a paid update? I really don't get it why Steinberg is constantly funking things over.

[SJ_Digriz]

Hello,

Do you mean the VST Instrument rack?

Yes, if I load 20 instruments into the rack with all the QC and routings the way I want, can I save that entire instrument chain as a single preset?

For the VST instruments that have a special integration with Cubase it will recall the Quick Control that you have setup in that particular instrument E.g. HALion 5 or HALion Sonic 2. But for the rest, the next time you load the instrument it will recall exactly the Quick Controls parameter assignments that you have previously set up on the VST Instrument Rack. So these are stored globally.

Best regards,
GN

So I can't load 10 instruments and have the 10 instruments load back all at once from a preset? It's still 1 instrument at a time?

[Guillermo Navarrete]

Hello,

Hello,

Do you mean the VST Instrument rack?

Yes, if I load 20 instruments into the rack with all the QC and routings the way I want, can I save that entire instrument chain as a single preset?

For the VST instruments that have a special integration with Cubase it will recall the Quick Control that you have setup in that particular instrument E.g. HALion 5 or HALion Sonic 2. But for the rest, the next time you load the instrument it will recall exactly the Quick Controls parameter assignments that you have previously set up on the VST Instrument Rack. So these are stored globally.

Best regards,
GN

So I can't load 10 instruments and have the 10 instruments load back all at once from a preset? It's still 1 instrument at a time?

No, but, wouldn't it be the same as saving it as a template... I simply do not see a realistic situation when you are in the middle of a project and all of the sudden you want to load 10 new instruments to replace the existing ones.
Please do not get me wrong, but for that, why don't you simply save the project as a template?

Best regards,
GN

[Compyfox]

A situation would be, if you use like 3 different drum modules to create one drum sound, or you have a clean slate or other project and suddenly want to add a 80 seat orchestra (spread over 4-6 VSTi).

I do understand where SJ is coming from, and what he is aiming at. It's just that the details regarding Instrument Track vs Instrument Rack+MIDI is just not well documented so far.

And the question still remains, if the "rack instances" will be obsolete at a later state.

[LawrenceF]

Guillermo: Can you talk more about the rack in general?

Rearrange instances vertically? Rename? Directly replace instruments?

Thanks.

[SJ_Digriz]

I simply do not see a realistic situation when you are in the middle of a project and all of the sudden you want to load 10 new instruments to replace the existing ones.

No, that isn't what I meant ... add 10 more not replace the ones that are there. I constantly swap out orchestration sets. Project Templates don't work well for that, as I have to create a MASSIVE template and delete a bunch of crap out to get it manageable, only to figure out I want some of it back in later.

But, here is an example of how a more useful preset would work ..

I have a Moog Voyager, with the Voyager plugin (either instrument track or rack). I have to monitor the audio for moog on a separate track. I use 2, a stereo and a mono. So, as an instrument track, I'm up to 3 tracks now. I also do a lot of control of that synth with Cthulhu. Which is another rack instrument, midi and midi track that I point at the Voyager plugin instance. Up to 5 tracks. I put the Voyager in a folder, then Cthulhu tracks in a folder inside that folder. Nice and clean. I want to click on that folder and save the entire contents as a preset.

I have a modular synth. I use Silent Way to control it. That folder structure takes 15 tracks. I want to click the folder and save a preset.

And, as I've stated before, the drum setups and orchestra setups are extensive as well, but simply saving an instance of the outs config, doesn't do me much good.

The current method of presets addresses the issue from the wrong direction.