Cubase / Cub.Artist / Cub.Elements 6.0.3 update pre-announce

UPDATED on 2011 07 15

Dear Cubase 6, Cubase Artist 6 and Cubase Elements 6 users,

Great things are happening here at Steinberg! Based on the invaluable feedback we received for the initial 6.0 as well as the 6.0.1 and 6.0.2 versions, we have used the last months to further improve Cubase. All these enhancements will emerge in the next 6.0.3 maintenance update. After already announcing the first improvements in June, here is a complete insight on what is to be expected in 6.0.3:

Please note that depending on your Cubase version, not all improvements and resolved issues are part of the update

Improvements in 6.0.3

1) Event handling opacity while slip-editing
When slip-editing an event, the event will now turn semi-transparent just like when dragging and moving it in 6.0.2.

2) Gridlines in front of parts/events
To further simplify editing and positioning of Audio Events and MIDI Parts, Cubase 6.0.3 introduces the ability to draw the Grid Lines of the Project window and the Audio Part Editor in front of them. The strength of the gridlines in front of parts and events can be seamlessly controlled.

3) Zoom handling and part names: show Event Data/Name options
A new event display preference lets you customize how part names and data on smallest track height are displayed.

4) Support for Euphonix/Avid MC Pro remote control surfaces
An update for the Steinberg EuCon Adapter will be released together with Cubase 6.0.3, adding full support for MC Pro remote control surfaces in Cubase 6.

5) Video improvements
Cubase 6.0.3 features improved playback performance of HD video formats in general. Single-threaded codecs (like Motion-JPEG, Photo-JPEG, and QuickTime DV) will benefit from the also new “Boost Video” option: if enabled, one CPU core is excluded from audio processing and reserved for video decoding and playback tasks, resulting in smoother video performance.

6) Audio import: Split File Name Format
To higher the level of compatibility when exchanging audio files with other products and to give more flexibility in general, creating split files from multi-channel files can now be named. For example, it’s now possible to add suffixes like “_L” or “_R” to the corresponding channel.

7) MultibandCompressor: Live mode
The MultibandCompressor plug-in now features a new efficient Live mode which reduces plug-in latency as well as load on the CPU.

8) New Patchname Script for Yamaha MOX synthesizer
A Patchname Script for the Yamaha MOX synthesizer is now available in the MIDI Device Manager.

Issues resolved in 6.0.3

1) Folder track
When expanding a folder track, the track list now doesn’t scroll to keep the focus on the track folder.
The original issue is described in more detail at:

2) Audiowarp
a) When playing back warped material in a loop for an extended time, the audio quality remains intact (PC Windows only). The original issue is described in more detail at:

b) A warped audio event now stays in sync, also when placed in a part with multiple splits and the project includes tempo changes. The original issue is described in more detail at:

c) A potential AudioWarp issue with shifted audio events, when changing the tempo in the Sample Editor toolbar, has been resolved.

3) VariAudio
After flattening VariAudio modifications, the solo state in the Sample Editor will behave correctly.
The original issue is described in more detail at:
Also an issue has been resolved, where the VariAudio analysis could render the application unresponsive.

4) Key Commands and Macros
Deleting a macro won’t render the application unreliable. Applying user-created key command presets won’t result in opening the Preset Browser.
The original issue is described in more detail at:

5) Quantize
Some quantizing errata corrected. Iterative quantizing for audio events behaves correctly and approximates the chosen quantize preset and grid value now.
The original issue is described in more detail at:

6) VST Expression
Chasing MIDI CCs for VST Dynamics works correctly now. If a project used Note Expression data, the Tempo Detection doesn’t lead to potential instability of the application.

7) Freeze
Opening a project with frozen channels now allows proper editing of plug-ins loaded in Insert slots 7 & 8.

8) Input Transformer
The “Off Velocity” parameter has been added to the Input Transformer.

9) Metronome
Distortion at certain sample rates when using user-samples for the Metronome has been eliminated.

10) ReWire
Improved playback/transport synchronicity using Reason, respectively for ReWire connected applications.

11) MonoDelay plug-in
Producing additional ASIO load when enabling the improved silence detection in the MonoDelay plug-in has been resolved.

12) AutoPan plug-in
The LFO waveform state is now displayed correctly in the AutoPan plug-in.

13) Spector plug-in
An issue has been resolved, where Spector doesn’t display the current spectrum correctly.

14) Score Editor
a) Erratic track arming issue resolved in conjunction with open Score Editor and changing layouts.

b) Under certain conditions Crescendi symbols on page 1 could appear on the following Score pages. This issue has been resolved.

c) The Zoom Tool in the Score Editor behaves correctly now.

d) An issue has been resolved, where the Delete Overlaps function deleted preceding events under certain conditions.

e) Bottom staffs are no longer selected when scrolling pages.

f) Potential issues with MusicXML files exported from Finale and imported to Cubase have been resolved.

Thank you all for your extended feedback once again!

We aim to release the 6.0.3 update for Cubase 6 and Cubase Artist 6 by the end of July.

Apart from a small issue with VST Connections (one time reconnecting of connections required for some USB interfaces) if updating from OS X 10.6 to 10.7, Cubase 6.0.3 is OS X 10.7 Lion compatible.

Thanks for choosing Cubase!

Helge Vogt
Product Marketing Manager Cubase
Steinberg Media Technologies GmbH

Very good news, thanks and continue with the communications and improvements. CS.

lovely job keep them coming ! :smiley: :smiley: :smiley:

Finally a proper fix to TE - Now if you guys could only work on admitting errors and not pushing them into the Music Lounge, we’d be on the right track!

Excellent work, Steinberg Team! Keep it up! :sunglasses:

I’m waiting for this update…

Did you read my feature request?

(to make it possible to adjust the number of 1/16 notes per count)

Here’s to hoping Quantize is actually fixed. You reference my thread but you speak of Iterative quantize which has nothing to do with it. Are you going to fix my quantize glitch as well? the one described in the thread/video?

Looking quite forward to this release, keep up the great work Steinberg. If the official release is slated for the end of July, I hope a beta or pre-release can come about before then for those eager to test and try beforehand.

Yes, this should be fixed as well. I 'll update the list to reflect this soon.


Aloha and +1

Go Cubase!

Great news Helge!

On the one hand I am very happy with the rate of patches. Also, as a LooooooonG time Cubase user, 6 is by FAR the most stable initial release and is enjoyable to use for most editing.

EDIT: some seem to think grid lines will solve the TE problem. I’ll reserve my annoying complaints until after giving it a whirl.


How about the sluggishness with Variaudio?



Great News!!! :smiley:

Nice, when’s this due? Will be installing Artist 6 in a few weeks time, it’d be nice to get started on this version :sunglasses:


Love the new patch release rate and the Steinberg online communication!

Thanks guys!

Yep, good news !
This is new in Steinberg land and definitely an improvement.
Still would have love to see a ‘quicker than 6 month’ fix for T.E. …
BUT not so long ago, this could have taken one+ year … :wink:

Also good to see the other urgent issues, fixed.


thanks for the update Helge - welcome news; and to you for keeping the comms going.

Then there’s this:-

+1 - I’d also be interested in any info/progress you can give…?
probably related to this post/topic, where Christian Fremerey was saying a fix was being readied, but as we know didn’t make into 6.0.2

Good news !