Steinberg Cubase Pro 8

[Guillermo Navarrete]

Hello,

Update prices are out:
Update from Cubase 7.5 to Cubase Pro 8 = €99.99
Update from Cubase 7 to Cubase Pro 8 = €149.00

Maybe my brain is fuzzy on the details, but it seems this has been the exact pricing for an upgrade for at least the last 4 versions, yes? If anything, they are predictable.

Devon

Not correct, the update from Cubase 6.5 to Cubase 7 was €149.00 and from Cubase 6 €199.00

The prices have been reduce for this update.

Best regards,
GN

[lfm]

Would there be a detailed comparison pdf - like for 7.x?

Often there is a slide in features and things only available in Cubase, is now in Artist as well etc.

Thinking of track lanes and track archives in Artist 8?

Thanks.

[SJ_Digriz]

Would there be a detailed comparison pdf - like for 7.x?

Often there is a slide in features and things only available in Cubase, is now in Artist as well etc.

Thinking of track lanes and track archives in Artist 8?

Thanks.

on the steinberg site on the comparisons tab

[lfm]

Would there be a detailed comparison pdf - like for 7.x?

Often there is a slide in features and things only available in Cubase, is now in Artist as well etc.

Thinking of track lanes and track archives in Artist 8?

Thanks.

on the steinberg site on the comparisons tab

Thanks, but wasn't that the more rough comparison. Then a link a to more info about plugins - which is of no interest for me.

There used to be something called detailed comparison. There you could see what was only in full Cubase and not in Artist etc.

I could also add if List Editor(Midi) is there in Artist.

List editor, track archives and track lanes were the things I missed the most in Elements 7.

EDIT: Downloading manual it says that track lanes and list editor are in Artist - but track archives(track templates) only Cubase Pro.

[Mushy Mushy]

I have a question re bounce in place...

Presumably this causes the MIDI channel to be converted into audio, and the VSTi to then be deleted.
Can one retrospectively change their mind and go the other way? (ie, audio back to MIDI and VST).

That would be

[SJ_Digriz]

I have a question re bounce in place...

Presumably this causes the MIDI channel to be converted into audio, and the VSTi to then be deleted.
Can one retrospectively change their mind and go the other way? (ie, audio back to MIDI and VST).

That would be

It only mutes the source .. the channel does not go away. So you can go back anytime you want. You can also use track versions on the source, render/disable, then go back enable/new version/fix something/render, and go back to either of the previous setups.

[Mushy Mushy]

It only mutes the source .. the channel does not go away. So you can go back anytime you want. You can also use track versions on the source, render/disable, then go back enable/new version/fix something/render, and go back to either of the previous setups.

Ah ok, thanks.

I do like my idea better though. Although, it's probably impossible.

[lfm]

I have a question re bounce in place...

Presumably this causes the MIDI channel to be converted into audio, and the VSTi to then be deleted.
Can one retrospectively change their mind and go the other way? (ie, audio back to MIDI and VST).

That would be

It only mutes the source .. the channel does not go away. So you can go back anytime you want. You can also use track versions on the source, render/disable, then go back enable/new version/fix something/render, and go back to either of the previous setups.

Manual call it Render in place.

Seems you have many options what to do with both source and destination tracks.

Specify what happens to the source tracks after rendering.
•Keep Source Tracks Unchanged
•Mute Source Tracks
•Disable Source Tracks
•Remove Source Tracks

Desination can keep automation if you want that, to continue working.

Seems quite cool.

[billcarroll]

I have a question re bounce in place...

Presumably this causes the MIDI channel to be converted into audio, and the VSTi to then be deleted.
Can one retrospectively change their mind and go the other way? (ie, audio back to MIDI and VST).

That would be

It only mutes the source .. the channel does not go away. So you can go back anytime you want. You can also use track versions on the source, render/disable, then go back enable/new version/fix something/render, and go back to either of the previous setups.

Manual call it Render in place.

Seems you have many options what to do with both source and destination tracks.

Specify what happens to the source tracks after rendering.
•Keep Source Tracks Unchanged
•Mute Source Tracks
•Disable Source Tracks
•Remove Source Tracks

Desination can keep automation if you want that, to continue working.

Seems quite cool.

Not as good as good as track transform or bounce in place in Studio One. It's a start though.

[lfm]

Not as good as good as track transform or bounce in place in Studio One. It's a start though.

Maybe, I don't remember - it was two years ago I ran a project in S1.

Remember I always liked how Sonar do freezing. Really easy to do back and forth - and also ability to work on frozen tracks.

[budweiser]

I have a question re bounce in place...

Presumably this causes the MIDI channel to be converted into audio, and the VSTi to then be deleted.
Can one retrospectively change their mind and go the other way? (ie, audio back to MIDI and VST).

That would be

+1, ala studio one. The best way to freeze, imo. By the way, i'm not sure the freeze has been updated in cpro8, as this new feature is called render in place. Sounds more like a new thing, but it's a good start !
Anyway i will update.

[Overflow]

Hi,

Just installed my 8 Pro update. Quick question - can not find "group vst plugins by vendor" in VST plugin preferences. Did Steinberg remove this option?

cheers,
o.

[gravehill]

Regarding Render in place, I noticed an oddity that might be due to VST2 but anyway. If you use a multi-timbral synth with several output channels, Cubase doesn't know in which output the midi part will sound. As result it renders ALL outputs and you get a bunch of silent renders and redundant audio channels in addition to the part you actually wanted.

Maybe it is possible to make a macro that detects if the rendered part is silent and if it is, removes the part and channel automatically...

[LawrenceF]

Not as good as good as track transform or bounce in place in Studio One. It's a start though.

Track Transform is a different thing but the direct bounce in Cubase 8 actually looks better than S1's direct bounce, when compared directly, in isolation, only because of the additional bounce options.

Re: Transform... If you think about it, Cubase 8's new bounce is a mini substitute for Transform, because you can bounce the midi to a new track and disable the instrument track.

There should be no reason for anyone to use "freeze" in Cubase now unless disabling a track actually doesn't free up ram and/or disabled tracks clips don't react to edits like insert or delete time. Although, it's likely the case that disabled tracks clips won't follow the edits like with Transform, so not quite the same thing for editing and round trips.

But still, many miles better than what they had.

[Guillermo Navarrete]

Hello,

Regarding Render in place, I noticed an oddity that might be due to VST2 but anyway. If you use a multi-timbral synth with several output channels, Cubase doesn't know in which output the midi part will sound. As result it renders ALL outputs and you get a bunch of silent renders and redundant audio channels in addition to the part you actually wanted.

Maybe it is possible to make a macro that detects if the rendered part is silent and if it is, removes the part and channel automatically...

This is a known issue we are working on it.

Best regards,
GN