Mapping MIDI CC # To Softsynth Parameter

Author
Post
Essentials Only Full Version
AdamGrossmanLG
Max Output Level: -62 dBFS
  • Total Posts : 1436
  • Joined: 2014/07/13 03:40:34
  • Status: offline
2015/04/27 21:26:11 (permalink)

Mapping MIDI CC # To Softsynth Parameter

Hello All,
 
How do you go about figuring out what MIDI CC # controls what parameter in a soft synth?  I have an external MIDI CC Sequencer that I can send MIDI CC information to a track.  I can only choose a MIDI CC#, so I cannot know what it is mapped to in a softsynth.  Is there a section where I can see the MIDI CC# of each softsynth parameter?
 
If not, how can i say assign MIDI CC#78 to say an attack envelope parameter?
 
I know about ACT, thats good for external midi controllers, but I have to know what CC# these map to.

Much appreciated,

Adam
#1

4 Replies Related Threads
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Mapping MIDI CC # To Softsynth Parameter 2015/04/27 21:35:13 (permalink)
    Depends on the synth. Some support MIDI learn or have some way to assign a CC to parameters. SONAR provides a way to remote control automation parameters see  http://www.cakewalk.com/D...age=3&help=0x20183
    post edited by scook - 2015/04/27 21:42:26
    #2
    azslow3
    Max Output Level: -42.5 dBFS
    • Total Posts : 3297
    • Joined: 2012/06/22 19:27:51
    • Location: Germany
    • Status: offline
    Re: Mapping MIDI CC # To Softsynth Parameter 2015/04/28 03:59:28 (permalink)
    What the synth is doing with incoming MIDI is not standardized. Some plug-ins follow proposed MIDI names http://www.midi.org/techspecs/midimessages.php , some not.
    Mentioned by scook automations are part of VSTi specification, so they are common for all synth. ACT is using the same schema. But ACT and Remote Control are not working throw normal MIDI track/route.
     
    In case you record CC MIDI, the result appears in the MIDI clip. When recording Automation, the result is saved as Track automation. But you convert between these 2 types of recording. I mean in case you record Automation and then find out the synth has MIDI CC for that and you want use it you do not have to re-record.
     
    Some information about what goes where you can find on my site (link in signature).
     

    Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
    GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
    RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
    www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
    #3
    AdamGrossmanLG
    Max Output Level: -62 dBFS
    • Total Posts : 1436
    • Joined: 2014/07/13 03:40:34
    • Status: offline
    Re: Mapping MIDI CC # To Softsynth Parameter 2016/08/21 12:32:34 (permalink)
    edit
    #4
    Blades
    Max Output Level: -43 dBFS
    • Total Posts : 3246
    • Joined: 2003/11/06 08:22:52
    • Location: Georgia
    • Status: offline
    Re: Mapping MIDI CC # To Softsynth Parameter 2016/08/21 12:54:42 (permalink)
    I just got around to opening a ticket about this last night even though I've known of the issue for quite some time.  I use the Remote Control for a thing or two, but not much because it doesn't seem to "stick" when saving the project.
     
    If you have the option to do it with ACT instead (i.e. that parameter on that synth is able to be mapped), I believe this will actually save with the project.
     
    If anyone has ideas about the saving of Remote Control mappings, that would be great to know, as I don't know how long it will take to get a response back from Cakewalk on this question.  It's been asked before in many threads, so I feel like they must know that it is a problem and it is far on the back burner of development.
     
    edit: didn't realize that this thread is as old as it is.

    Blades
    www.blades.technology  - Technology Info and Tutorials for Music and Web
    #5
    Jump to:
    © 2025 APG vNext Commercial Version 5.1