Benches Uncategorized

14

track automation & modulation wheel ?

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hi,

I have several sample libraries and software instruments where the modulation wheel (CC01) controls the volume of the instruments. Other CC's control things like vibrato and flutter. I have set up an external midi controller with the appropriate CC's. This works fine.

I can record this midi information, but I'd rather use track automation. However, I don't know how. I tried the learn function, but without succes.

Can anybody help me out?

Thanks, Wouter.

14 replies

Sign in or join Beachball Help to reply.

  1. 0

    Bee Jay

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    CC data
    is MIDI data. It should be recorded to regions, like any other MIDI data.

    You can edit this MIDI CC data in a similar way to automation using the Hyper Draw feature.

    If you don't want to record MIDI CC data, and instead want to use automation to automate instrument parameters directly, you can do so, you'd just need to use Automation Quick Access (learn the mod wheel) and select the instrument parameter automation lane to draw.

  2. 0

    composer123

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Automation Quick Access works fine for volume, but not for the modulation wheel. What I do:

    * I have a GM device connected to a software instrument.

    * When I select this GM device in the arrange window I hear my software instrument.

    * When I move the mod wheel the volume (not the volume fader) of the software instrument changes.

    * When I enter Automation Quick Access mode with volume the visible automation parameter, the volume slider moves up and down with the mod wheel.

    * When modulation or another CC is the visible automation parameter, nothing happens.

    Any ideas?

  3. 0

    Bee Jay

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    If I'm understanding you correctly, it seems you are confusing automation with MIDI controller messages, and the two are very different.

    The mod wheel is a MIDI CC message, and what it will do on a given instrument depends on how that instrument is programmed. This has nothing to do with automation.

    What CC is your mod wheel sending? if your volume fader is changing, it sounds like it's sending CC #7, not CC#1 - check in the transport what CC number it's sending.

  4. 0

    composer123

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I understand the difference between automation and MIDI controller messages.

    The mod wheel is sending CC01. The volume fader is only moving in Automation Quick Access, in which case the mod wheel is used in another way.

  5. 0

    Bee Jay

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Then you presumably have already learned the mod wheel to automation quick access. Try turning automation quick access off, or deassign the control.

    I'm still not quite clear on what your problem is, though...?

  6. 0

    composer123

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    My problem is that automation quick access and normal automation only seems to work for volume and pan. And not for other Midi CC's like modulation, breath control, portamento and expression.

  7. 0

    CCTM

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi

    You are correct in your assertion that Track Based Automation cannot be created for MIDI CC1 and the like using the normal Touch, Latch or Automation Quick Access methods.

    It is possible to record the CC messages as Region -Based events and then convert them to Track based:

    Step 1 Record the CC1 data into a MIDI region

    Step 2 Enable HyperDraw for that region (View:HyperDraw.. choose the CC no).

    Step 3 Use "convert Visible RBA to TBA function (Track:Track Automation:Move visible Region data to Track Automation).

    You can then edit (and draw manually) the CC automation.

    Not as nice as being able to play it in directly as TBA, but....

    Maybe this will help?

    CCT

  8. 0

    Vacheto

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    composer123 wrote:

    but I'd rather use track automation.

    First of all you have to provide which Software Instrument you use to provide you true information. Some third party Software Instruments support both "Host Automation" & "Midi Automation" maps like Kontakt for example. In this scenario if you use Midi Automation and had set for a certain control i.e CC#1 and if you try to use Logic Quick Access like Bee Jay suggested, then Logic Physical Input will block CC#1 and you can not control your Software Insr. as you do before.

    If your Software Intrs. supports "Host Automation" custom map, then you can assign/learn CC#1 to control a given parameter inside the Software Instr.

    After that you can use the Logic CA dialog to learn and use Track Automation but I do not RECOMMEND ! CC#1 will be BLOCKED from the Physical Input you can not use any more which is quite essential as a Modulation Controller for many other synths etc. It is recommended to use CA ( Controller Assignments Dialog ) with CC# like CC12,13,14 - General use...

    Finally it will be O.K to record your CC#1 as you always do and use the Hyper Draw ( you can try Autodefine keycommand ) and switch the view using it directly in the Arrange using enough zoom of the region in question. You can use Modifiers to make curves etc as you do with the Track Automation (See the pic below - I'm on my PC laptop right now and it's Logic 5).

    Or you can use Host Automation map inside your Soft.Istr and learn some CC# of General Use like CC12,13,14 after that use the Logic CA learn feature.

    !http://img203.imageshack.us/img203/4757/hypdraw.gif!

    !http://img59.imageshack.us/img59/4967/aglogo45.gif!

  9. 0

    Bee Jay

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    My problem is that automation quick access and normal automation only seems to work for volume and pan. And not for other Midi CC's like modulation, breath control, portamento and expression.

    Automation has
    nothing to do with MIDI. Two fundamentally different things. You can automate Logic's channel volume and pan, because automation is directly controlling Logic's channel strip - this goes nowhere near MIDI..

    If you are trying to use automation to control things via MIDI, or to send MIDI, then you are not getting the concepts of what these things are, from what I can see. Or maybe I'm not understanding you correctly, perhaps.

    Automation quick access is designed to assign
    one MIDI controller, an accessible one like your mod wheel, to let it control any automatable parameter in Logic - in essence, it's a quick way to control automation from one MIDI control that you define.

    Automation is
    not for sending MIDI to a plugin or virtual instrument. Automation does not send MIDI, it talks to specific parameters in the instruments directly inside Logic. No MIDI involved.

  10. 0

    composer123

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks everybody for your replies.

    I guess I stick with recording the CC, merge it with the region containing the notes and edit it in hyper draw.

    The disadvantage of this approach is that there is no such thing as touch or latch. It would be nice to be able to change just a bit of the hyper draw curve with an external midi controller. I think this is not possible. When I want to change the hyper draw data I have to edit it with the mouse, or delete the existing data and record new data. Correct?

    BTW, is there a quick way to delete all visible hyperdraw data with a key command? I searched for it but couldn't find it.

  11. 0

    Vacheto

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    composer123 wrote:

    It would be nice to be able to change just a bit of the hyper draw curve with an >external midi controller. I think this is not possible.

    You can use midi take folders to do that. Have a look at the picture below. Just enable this setting. Keep in mind that the midi Take Folders Autodefine view can not be changed so if like to edit the control nodes you must open the Piano Roll Hyper Draw as shown.

    is there a quick way to delete all visible hyperdraw data with a key command?

    All visible sounds too global... You can SHIFT select to rubber hand a region of events in the Hyper Draw and hit the computer Delete or Backspace keys to delete the events.

    !http://img705.imageshack.us/img705/729/takefolders.gif!

    !http://img59.imageshack.us/img59/4967/aglogo45.gif!

  12. 0

    composer123

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for your quick reply.

    Interesting suggestion about the take folders. The disadvantage is that I need 2 tracks for every instrument: one for the notes and one for the CC data. And my template is already over 200 tracks...

    I know about shift-select and delete, but was hoping for a solution without touching my mouse.

  13. 0

    Vacheto

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    composer123 wrote:

    The disadvantage is that I need 2 tracks for every instrument: one for the notes >and one for the CC data. And my template is already over 200 tracks...

    Right it is nice to have a good track order, so when use Sub "duplicated" tracks to record take folders for the Midi Automation you can activate the main "H" arrange button and switch on the green "H" buttons of each "Sub" control data track. This way you can hide all "Sub" midi automation tracks.

    Actually you will do some emulation of the Track Automation order. When you hit "Show Track Automation" then the sub track automation panes are shown. It is equivalent of operation the main arrange "H" button to show the midi/region automation tracks etc.

    I know about shift-select and delete, but was hoping for a solution without touching my mouse.

    Use a voice command "Get out" for example ! 😀

    !http://img59.imageshack.us/img59/4967/aglogo45.gif!

  14. 0

    crimsonnoise

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    composer123, I have been trying to find out the same for years. I too am keen to control expression / velocity crossfade with modwheel and have it recorded as automation rather than midi. I really hope one day Logic will allow other controllers than just volume and pan recorded this way, and I don't understand why it's not possible now. Automation quick access should simply allow this.

    My workaround is as follows:

    I record all the expression as PAN. The modwheel data (control #1) gets converted to PAN via automation quick access, and is recorded onto the track as PAN automation. The all the track instruments are cabled, for each midi port, to a transform object, that transforms PAN back into MOD.

    All my instruments are pre-panned in VE Pro, so I normally have no need to adjust the pan anyway.

    I am using a Mackie Control (=Logic Control) surface and it's quite neat as one can flip the faders, then the main faders become PAN and I can re-ride the expression if necessary.