Notifications
Clear all

Using CC Rider to control MIDI CC of Baby Audio Transit VST

5 Posts
2 Users
0 Likes
66 Views
(@jason_za)
Estimable Member
Joined: 4 years ago
Posts: 65
Topic starter  

Good day. I placed CC Rider before Baby Audio Transit (both in the MIDI section of Unify) and set the CC to 113, which is what it shows when using the ear to control the Transition Control button in Transit but it isn't making the Transition Control button move. I'm not sure if this is the intended purpose of CC Rider but am hoping so. I'm not sure what I'm doing wrong... Any help will be much appreciated.


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@jason_za

Excellent question. There are many things to unpack here, so I'll take them one by one.

I placed CC Rider before Baby Audio Transit (both in the MIDI section of Unify)

If you want CC Rider to send MIDI to any audio-effects on an INST layer, you must put the CC Rider instance onto a MIDI layer, and set your INST layer to listen to it. If you put CC Rider into the MIDI-effects chain of the INST layer itself, its output will only go to the instrument plug-in on that layer, not to the audio-effects. The description in the manual is not very clear on this; I will rewrite it. 

...set the CC to 113, which is what it shows when using the ear to control the Transition Control button in Transit...

I don't understand. Where do you see CC#113 appearing when using the ear?

...but it isn't making the Transition Control button move.

Transit doesn't listen to MIDI (except optionally to trigger its randomize function). From page 9 of the Transit manual:

Assigning Hardware Controllers to Transit
Transit was designed with live performance in mind. Therefore, MIDI mapping is expected to be
handled via a DAW like Ableton Live or Bitwig Studio to ensure utmost stability. Most modern
DAWs have a built-in MIDI learn/MIDI link functionality that will allow you to assign hardware
controllers to Transit's parameters. For specific setup instructions, please refer to your DAW’s
manual.

This is the core of your issue. You're trying to use MIDI to modulate one of Transit's parameters directly, but most newer plug-ins don't work that way. What you need to do is use CC Rider to spin a Unify macro-knob, and link that knob to the parameter you want to modulate. The best way to do this is to put your CC Rider instance into the MIDI-effects chain of an embedded Unify layer, then assign the appropriate CC# to one of the embedded Unify's macro knobs, and link that knob to the plug-in parameter(s) you want to control.

I have attached a zipped Unify patch which illustrates this, using Transit. Unzip the .unify file, drag/drop it into Unify to load the patch, then save wherever you wish. (By default, it will save to the User Library, because that's where I saved it on my system.)


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

It's critical to understand that MIDI CC's and parameter-automation are not the same thing. CC's are MIDI messages. Parameter automation operations are "function calls" made by a host into a plug-in instance, requesting that a given parameter is to be assigned a new value. CC messages have very poor value-resolution (only 7 bits) but excellent time-resolution (MIDI message-times are sample-accurate). Automation calls have excellent value-resolution (32 bits, floating point) but poor time-resolution (at least in most implementations, Unify's included).

In some future version of Unify, we hope to provide true LFOs to drive macro controls. CC Rider is a stopgap solution until we can do this. It's arguably the worst of all worlds, combining the poor value-resolution of MIDI with the poor time-resolution of automation, but for sufficiently slow modulations it works reasonably well. Note some DAWs (notably Bitwig and Ableton Live) provide better parameter-modulation LFO solutions.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@jason_za

You might find Transit's built-in "motion sequencer" simpler, smoother, and more powerful than trying to use CC Rider for modulation.


   
ReplyQuote
(@jason_za)
Estimable Member
Joined: 4 years ago
Posts: 65
Topic starter  

Thanks a lot, @getdunne. I only recently started using Maschine and its automation is terrible, so that was the reason I was looking for a workaround to normal automation and it is new to me. Thanks for the explanations - I was not aware of many of these things and it will help me going forward.


   
ReplyQuote
Share: