Cubase 7 & DP8

Their list editor is far superior. No piano roll down the side (why would anyone need that when there is another editor all about that?) and you can step sequentially through each value without touching the mouse - very fast. There are some superior functions, 'split notes" is like CB’s disolve part but way more flexible. Transpose functions that would make Mr. M happy! Their “Step Time” (as they call it) sequencing is much more intuitive and easier… plus, my most missed feature, start transport/record on midi event. :sunglasses: . (been begging for that in all those FR topics here since 2008)… I’ve not seen DP8 in the flesh yet, but if a wad of cash fell in my lap, I’d be tempted, for sure. I love cubase as it formed my re-entry into music production a while back (took a long hiatus), but the old days I lived in Performer (pre DAW), and it was and is still excellent. Steiny should study these things I mention! :sunglasses:

Hope that’s an answer for you Steve… cheers - R

Check out the free Voxengo plugin called “MSED”

It can split stereo into mid/side and vice versa. Once split to M/S, you can process those components separately using your standard stereo plugins. Then another instance of MSED will combine the M/S back to stereo again.

Yes! Thanks for taking the time to write that, Robin. I’m actually having a look at DP8 now. Like everything no tool does it all.

There are two stand-out things about DP that I like. All the tools use music terminology, and the interface is very unified and easy on the eyes. When it comes to pure functional prowess though, Cubase is totally on steroids in comparison.

And DP has so many of the features that have been requested here for a long time, it does appear though that Cubase is getting some of those.

I like change, it helps shake up the creative sandbox to look at things in a different way…

It depends on what you consider supporting. NE can be applied to all VST as well as external synthesizers. The restrictions are imposed by the limitations of MIDI, meaning that MIDI has no way of understanding or process messages per note, with the exception of a specific message which most synthesizers don’t support anyways.

So messages are per note, which makes it much easier to cut and paste note segments together without having to worry about the Track MIDI Controllers. E.g. if you wanted to have a second set of chords played exactly like a previously recorded chord, you can easily copy just the notes, and all associated MIDI modifiers are copied along.

As it used to be, you either had to cut and copy track parts (in order for the Track MIDI Controllers to copy along) or copy them separately. After copying one can easily alter the notes of the new chord(s) and voila, you have the same expression.

Another neat thing, which might be to what your question was referring to, is supporting NE parameters natively inside of an instrument, like HALion 4, Padshop and Retrologue (the ones I know of and use, unfortunately). This enables NE custom parameters, which as an example in HALion 4 can be mapped by me the sound creator. To record them you could use a MIDI device capable of sending MIDI controllers that in turn map to NE parameters, or as mozizo pointed out, you can edit them inside an editor, e.g. the Key Editor.

From a long time user of MIDI, what I have expressed above is a natural evolution of MIDI into VST3 (NE) instruments, which is probably why I like it. However, there is much more to VST Expression that if you are building sounds and composing, it IS worth a look. Here’s another older article from Sound On Sound about VST Expression.

Here are a few demo’s for anyone who wants to understand more:
VST Expression
VST Expression 2
Retrologue
Eigenharp
Cubase5 VST Expression Demo
Cubase 6 tutorials

This:

This:

There are other instruments (and hosts) in development or in planning (at least if you believe the forums), though like I pointed out, a lot of vendors seem to continue on the stubborn side. There are people that want VST3.5 NE support in other hosts and instruments, but the nay-sayers strongly argue against it.

Some that want NE, like myself, do not buy unless they are at least considering VST3.5. I mean, to me it’s like buying an old hardware synth without MIDI, which makes it a pain to work with, in comparison to one with MIDI.

Some arguments for and against:

Kontakt thread 2011 (check out Miloslavs (valsolim) point on page 2)
Kontakt thread 2013 (the opposing argument is a real gem here)
Logic thread 2011

There are several threads in the host forums, Reaper, FL Studio, Sonar, ProTools, etc.

There is no relevant “debate” going on. There is a deficit of information and people misunderstand what VST 3.5 does.

The NI thread you pointed to is 2 years old, and that company has not shown the least indication that they might be adding VST 3.5.

Why does Kontakt have so many people making instruments for it and Halion has so few?

I think SB should actively promote Halion and design ways for virtual instrument makers to translate their product from Kontakt to Halion. They should proselytize and make it attractive to to them, and find ways the develpoers can make money using VST 3.5 in their product.

Monophonic note expression is very nice, but at this point, for my own intents and purposes, there is not much real-world use for the other parts of VST 3.5 since I don’t use synth sounds. My taste runs in other directions from the kind of sounds that come with SB products.

+1