Hello,
i would like to know how to use those Vst Expressions in Cubase 5 with zebra..
Does it work at all? Or is it just for sample based vsti like East West stuff etc..?
Are there any predefined keyswitches in Zebra? Don't get the whole idea behind it actualy..would be nice if anyone could bring some light on it..
thanks
here is a video that explains the basic thing..
http://www.the-composers-approach.com/f ... t_002.html
VST Expressions in Cubase 5 for Zebra?
-
- KVRAF
- 4805 posts since 21 Jan, 2008 from oO
-
rectus_dominus rectus_dominus https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=189415
- KVRian
- 735 posts since 16 Sep, 2008
Whoa, cool feature!
I don't think that Zebra has to do anything with keyswitches though (?)
I don't think that Zebra has to do anything with keyswitches though (?)
Just let its Sound do the talking: http://www.synthmaster.com/
-
- KVRAF
- Topic Starter
- 4805 posts since 21 Jan, 2008 from oO
I just heard that the Vsti itself has to support this feature..
All the NI stuff is supposed to work like that..but since its a pretty new feature not all the Instrument are able to do that..
How about you Ursß Do u see a way for Zebra in future??
cheers
All the NI stuff is supposed to work like that..but since its a pretty new feature not all the Instrument are able to do that..
How about you Ursß Do u see a way for Zebra in future??
cheers
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
I have no clue what it is. It's not defined in any plugin standard I'm currently supporting... is it some esoteric VST3 stuff?Zork wrote:How about you Ursß Do u see a way for Zebra in future??
-
- KVRAF
- Topic Starter
- 4805 posts since 21 Jan, 2008 from oO
No, its not esoteric..
did you watch the video? its about keyswitches just way smarter..but the plugin itself has to support this in a way..
did you watch the video? its about keyswitches just way smarter..but the plugin itself has to support this in a way..
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Ah... I get it. It's a feature that makes working with sample libraries easier. Some of these libraries use keys to switch between different samples (actually, some Ohmforce plugins do that too). Cubase lets you put in a name for these and locks these keys from transposition. It keeps the score cleaner and allows for a more compact view.
It's IMHO nothing that currently makes sense in or for Zebra. Instead of *switching* you can seamlessly *crossfade* between variations of a sound by automating the XY Controls.
Urs
It's IMHO nothing that currently makes sense in or for Zebra. Instead of *switching* you can seamlessly *crossfade* between variations of a sound by automating the XY Controls.
Urs-
- KVRAF
- 4141 posts since 11 Aug, 2006 from Texas
As of today Zebra can't change the sound of a preset via note-on/note-off events.
I don't see why you can't just create automation lanes, assign them to XY controllers and rename them to do what you want. That's what I do in Reaper. You can see the event changes just like this:
You could just as easily use the square wave envelope and directly automate a re-named X_1.
I don't really see what keyswitching has over this method. Can you explain why you want this feature?
I don't see why you can't just create automation lanes, assign them to XY controllers and rename them to do what you want. That's what I do in Reaper. You can see the event changes just like this:
You could just as easily use the square wave envelope and directly automate a re-named X_1.
I don't really see what keyswitching has over this method. Can you explain why you want this feature?
-
- KVRAF
- Topic Starter
- 4805 posts since 21 Jan, 2008 from oO
well..i just saw the video and thought it would be nice to edit those stuff via the expressions..
it just a very compfortable way of editing controller information..
as soon as one has set up a good expression map to work with it could make things a lot faster i think..
it just a very compfortable way of editing controller information..
as soon as one has set up a good expression map to work with it could make things a lot faster i think..
-
rectus_dominus rectus_dominus https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=189415
- KVRian
- 735 posts since 16 Sep, 2008
Yes, when using sample libraries it is much easier.
I hope that by that time I'll have a PC capable of handling these samplers, Live will have some alternative to this method too
I hope that by that time I'll have a PC capable of handling these samplers, Live will have some alternative to this method too
Just let its Sound do the talking: http://www.synthmaster.com/
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Yes. Synths have to specifically programmed to sound different, samplers just play different samples. I think it's too complicated with complex synths. It may work well with Minimonsta, but it's too much asked for when creating a Zebra patch (which can have a hell of a lot of expressive things going on all by itself, without need to switch anything)rectus_dominus wrote:Yes, when using sample libraries it is much easier.
-
- KVRAF
- Topic Starter
- 4805 posts since 21 Jan, 2008 from oO
well yea..just thought i asked and see what you think..since i dont work with samples or samplers a lot i thought there might be an easy way..but for sure..
not really neccesary..
have a good n8!
not really neccesary..
have a good n8!
-
- KVRAF
- 1617 posts since 11 Dec, 2008 from Minneapolis
An Ableton Live trick somewhat towards the same ends:
Create a 2 MIDI tracks "track-I" and "track-M"
For track-I, set input on and input to track-M
Put the MIDI notation on track-M (or set to monitor some external source)
Put an instrument rack with Zebra on track-I; map XYs you want to use to the rack (I actually just drag a saved rack preset which has the first XY mapped, as well as octave, semitone, and volume controls, or a variant of this rack for some specialized purpose)
Create a few clips on track-I, use clip automation to set XY or sequence XY rack knobs. Make sure to turn the knobs to full as automating rack knobs via clip automations is relative based on percent, rather than absolute. Also start with a default clip that has 1 automation point at 100% per XY control, and duplicate this clip, and tweak the duplicates - then _only_ the XYs will show up in envelope view when "Show All Modulations" is set (might also be worth setting some MIDI CCs like this, e.g. modwheel), avoiding overwhelming menus to find a rack element.
When played these clips will pass automation to the instrument rack even though MIDI is coming from track-M. If a specific clip has a quality (e.g. loud, quick or whatever) naming that clip can help.
Further toward the video example, one could map those clips to a particular MIDI channel/note value from a keyboard. If those were e.g. (c/-1 to b/-1) on a keyboard, those would not then also pass to track-M even if it were set to monitor that keyboard.
Finally, selecting the two tracks and dragging them into Live's browser saves these two channels as a set. The very generic set can then be dropped into another Ableton set retaining the routing. The mappings of key->instrument "dummy" clips won't be retained. (this avoids potential conflicts down the line).
This is not the only way or always the best way to do something like this, it can be easier just to duplicate a track and tweak XYs - this way each track remains freezable. To freeze per-'dummy'-clip this way isn't impossible but requires some more trickery (MIDI overdub recording). This can be fun, it also can become difficult to manage. Labeling things and doing things the same way consistently across Live's elements and objects helps.
Create a 2 MIDI tracks "track-I" and "track-M"
For track-I, set input on and input to track-M
Put the MIDI notation on track-M (or set to monitor some external source)
Put an instrument rack with Zebra on track-I; map XYs you want to use to the rack (I actually just drag a saved rack preset which has the first XY mapped, as well as octave, semitone, and volume controls, or a variant of this rack for some specialized purpose)
Create a few clips on track-I, use clip automation to set XY or sequence XY rack knobs. Make sure to turn the knobs to full as automating rack knobs via clip automations is relative based on percent, rather than absolute. Also start with a default clip that has 1 automation point at 100% per XY control, and duplicate this clip, and tweak the duplicates - then _only_ the XYs will show up in envelope view when "Show All Modulations" is set (might also be worth setting some MIDI CCs like this, e.g. modwheel), avoiding overwhelming menus to find a rack element.
When played these clips will pass automation to the instrument rack even though MIDI is coming from track-M. If a specific clip has a quality (e.g. loud, quick or whatever) naming that clip can help.
Further toward the video example, one could map those clips to a particular MIDI channel/note value from a keyboard. If those were e.g. (c/-1 to b/-1) on a keyboard, those would not then also pass to track-M even if it were set to monitor that keyboard.
Finally, selecting the two tracks and dragging them into Live's browser saves these two channels as a set. The very generic set can then be dropped into another Ableton set retaining the routing. The mappings of key->instrument "dummy" clips won't be retained. (this avoids potential conflicts down the line).
This is not the only way or always the best way to do something like this, it can be easier just to duplicate a track and tweak XYs - this way each track remains freezable. To freeze per-'dummy'-clip this way isn't impossible but requires some more trickery (MIDI overdub recording). This can be fun, it also can become difficult to manage. Labeling things and doing things the same way consistently across Live's elements and objects helps.