I'm a longtime Logic Pro & Cubase user, and trying to find if there is a way that I can modify the midi data from my various controllers prior to entering the sequencer, as I can do in Logic's environment, but with Cubase instead. I'm thinking some kind of standalone scripting tool which could separately modify various midi input ports and then send them to Cubase via a multi-port midi loopback. Is there anything out there which would work in this way?
Some examples of the simple things I need to do:
- Precisely and arbitrarily change velocity curves
- Filter notes / PB
- Filter, add, or reassign CC's and change their curves
- Change the velocity curve of black keys compared to white keys, for one of my keyboards where they are not well matched
I can do all of these easily in Logic's environment, but not all of them in Cubase's input transformer. It's important for my workflow to do these mods before recording in the sequencer, not after the fact with midi plugins.
Replicate aspects of Logic environment with Cubase on Windows
-
- KVRAF
- 7114 posts since 22 Jan, 2005 from Sweden
Have a look at Plug'n Script for BlueCatAudio that allows scripting for both midi and audio.
Then from normal midi track use midi send to make the full solution, since PnS is VST synth or effect.
But total solutions with VST instruments can also be done with Patchwork from BlueCatAudio as well.
If using that kind of host within daw - you can also look at Piz VST midi plugins(look at Insert Piz Here on KVR). Whole bunch of useful tricks including what you describe there.
Then from normal midi track use midi send to make the full solution, since PnS is VST synth or effect.
But total solutions with VST instruments can also be done with Patchwork from BlueCatAudio as well.
If using that kind of host within daw - you can also look at Piz VST midi plugins(look at Insert Piz Here on KVR). Whole bunch of useful tricks including what you describe there.
-
- KVRer
- Topic Starter
- 23 posts since 13 May, 2007
Ifm, thanks for the info. Using midi plugins and extra tracks & midi sends is something I wanted to avoid, to keep my workflow efficient. But it sounds like Plug'n Script could still do what I need at least. Can it generate a VST-MA plugin which can be used in the midi inserts of a midi track? The documentation is ambiguous. If that were the case then I can think of a way to make this work pretty much the way I want...
~~~~~~~~~~~~~~~~
-
- KVRAF
- 6097 posts since 5 Jul, 2001 from Just about .... there
Are you aware of the MIDI track input transformer in Cubase? It has some, but not all of those capabilities.
If you have to ask, you can't afford the answer
-
- KVRer
- Topic Starter
- 23 posts since 13 May, 2007
Yes, I'm aware of the input transformer, but it only does part of what I need to do and even then not so easily (for example, scaling velocity is possible but an arbitrary curve is not).
~~~~~~~~~~~~~~~~
-
- KVRAF
- 6097 posts since 5 Jul, 2001 from Just about .... there
I'm pretty sure the logical editor has random function. Again, not trying to argue .. but I think there is stuff there that can be track templated to get most of those functions. I realize it isn't all of them.
If you have to ask, you can't afford the answer
-
- KVRAF
- 7114 posts since 22 Jan, 2005 from Sweden
I talked to them about making also a VST-MA version to be fitted directly as midi fx in Cubase, but showed no interest - so no. They claimed format is deprecated by Steinberg and possibly replaced by VST3-something.bsalter wrote:Can it generate a VST-MA plugin which can be used in the midi inserts of a midi track? The documentation is ambiguous. If that were the case then I can think of a way to make this work pretty much the way I want...
In Patchwork you can load multiple of anything VST and save as preset - how is that for workflow?
Piz stuff is a vast variety of functionality already, not going into programming level. You have the scaling stuff and much more.
https://code.google.com/archive/p/pizmidi/downloads
The pdf describe all the enclosed plugins and what they do.
I extensively use track archives to restore loads of tracks in a simple way, if to do it right in Cubase. I haven't used midi sends in particular, but assume as other routings are kept it may work. If to assume setup is reused in constuction many synths with routings in many situations.
-
- KVRer
- Topic Starter
- 23 posts since 13 May, 2007
I tried the Patchwork demo but found it unstable when using certain instruments.
However, I've found a way in general to do the kind of routing that I need, that I didn't realize before:
midi controller input -> Instrument track with midi capable vst (activate monitor)
Instrument track midi output -> midi track (activate monitor)
midi track output -> loopback midi bus
loopback midi bus -> Instrument tracks
Btw, I did a quick test and found that midi routing seems to be preserved in track archives.
So, I might be able to do this just with Kontakt scripting, and load the whole setup into any project as a track archive. Thanks for getting me thinking on this!
However, I've found a way in general to do the kind of routing that I need, that I didn't realize before:
midi controller input -> Instrument track with midi capable vst (activate monitor)
Instrument track midi output -> midi track (activate monitor)
midi track output -> loopback midi bus
loopback midi bus -> Instrument tracks
Btw, I did a quick test and found that midi routing seems to be preserved in track archives.
So, I might be able to do this just with Kontakt scripting, and load the whole setup into any project as a track archive. Thanks for getting me thinking on this!
~~~~~~~~~~~~~~~~
-
- KVRAF
- 7114 posts since 22 Jan, 2005 from Sweden
Interesting to hear track archives work for midi routing as well, I wasn't sure - thank you.bsalter wrote: Btw, I did a quick test and found that midi routing seems to be preserved in track archives.
So, I might be able to do this just with Kontakt scripting, and load the whole setup into any project as a track archive. Thanks for getting me thinking on this!
About PatchworkSynth, I had some trouble understanding to route midi at first.
But every instrument loaded get midi from input from track as default - in parallell, kind of.
And you have to reduce through internal midi patch busses which are getting midi from what.
I have v1.73 and this was a bit cumbersome and a lot of click all over - maybe v2.x are better regarding this.
When using a lot of midi plugins together with VST instruments it become a lot of work. Thinking if instability is due to midi from input is hitting all over.