|
Avid Pro Audio CommunityHow to Join & Post Community Terms of Use Help Us Help YouKnowledge Base Search Community Search Learn & Support |
#11
|
|||
|
|||
Re: Pro Tools Complete Midi CC# Chart
Hey guys and girls,
I haver a question about this. I have built a portable setup and want the smallest controller thinkable, I have the Griffin bluetooth now to control my protools for clip gain (just a s short-cut) but now I would like to have it control my selected fader up and down. I managed to get the fader jump in a position with an apple script controlling MIDI Pipeline to the protools M-Audio MIDI controller settings in Pheripherals. Problem is, I can just set the fader in a certain fixed position depending on the value in the apple script. It will not move up and down from its previous position (like you want a controller to behave This is the command for down: tell application "MidiPipe" MIDISend toPort "MidiPipe AppleScript Input" withData {176, 34, 1} end tell and the one for up: tell application "MidiPipe" MIDISend toPort "MidiPipe AppleScript Input" withData {176, 33, 1} end tell Thanks so much team!! Ciao, Arjen Quote:
|
#12
|
||||
|
||||
Re: Pro Tools Complete Midi CC# Chart
Hi,
So iv been losing my mind here. I cant get any plugin in my PT 2018 unlimited to "learn" CC messages that aren't from 33-40. So from 127 CC messages, AVID is limiting us to 8 of them to control a plugin? Lets say it is limited, I cant even find a proper list of all the PT12's CC commands. I got a few midi keyboards and I want to populate their damn knobs. I mean my novation launch control has 16, whats the point in that Am I missing something here?
__________________
Mac Pro (Early 2009) El Capitan (10.11.6) Protools HD 12.8.3 |
#13
|
|||
|
|||
Re: Pro Tools Complete Midi CC# Chart
That won't work.
Some plug-ins (instruments) will have a MIDI learn function, allowing you to assign physical controls to virtual knobs - but otherwise it's a proprietary language, for which you need a control surface that speaks said language (Eucon / HUI / certain older Digidesign surfaces). Some people have had a degree of luck emulating Hypercontrol, by using a Novation controller, with it's accompanying Novation MIDI remapping software. Sent from my iPhone using Tapatalk |
#14
|
|||
|
|||
Re: Pro Tools Complete Midi CC# Chart
Additionally there's the Slate Raven, which uses a layer of intermediate software (it might be possible to get hold of that intermediate software, but it could be a nightmare mapping it all).
Of course, with the above mentioned control surfaces, in addition to the default plug-in mapping, you can create your own custom maps. Sent from my iPhone using Tapatalk |
#15
|
||||
|
||||
Re: Pro Tools Complete Midi CC# Chart
Quote:
Ronnie Pollock has just posted "I've discovered a solution to achieve Hypercotrol functionality with Protools beyond version 10" - see the last 2 Posts: http://community.m-audio.com/m-audio...y_button&reply Partial quote: "However I also discovered that if you open the application IGNITE before loading Protools then basic Hyperontrol functions become ACTIVE within Protools 12 and Ignite no longer has access the Axiom 32 Mini, freeing it up for Protools. This method appears to trick the Axiom Mini into keeping the Hypercontrol functions active for Protools 11 / 12. "
__________________
Pro Tools Studio 2024.3 * SSL UC-1 * Digidesign Command 8 * M-Audio Axiom Pro 49 * PreSonus Speakers & Monitor Station V2 * Lenovo W520 laptop Type 4276 (32 GB RAM) with extra-Ports Dock + SSDs: 2 @ Samsung T5 + 1 @ Samsung T7 * 3 Screens: 15.6 Laptop + 24 BENQ GL2450-B + Samsung 27 CT550 curved Monitor |
#16
|
|||
|
|||
Re: Pro Tools Complete Midi CC# Chart
Quote:
Interesting, I will check that out (though it sounds like it doesn't work with plug-ins, or panorama - just volume). When I noticed I'm quoted several times in that thread, I figured it was going to be a dead end - but this at least sounds promising, in terms of adjusting multiple volume faders simultaneously, when not using a control surface. Cheers! Sent from my iPhone using Tapatalk |
#17
|
|||
|
|||
Re: Pro Tools Complete Midi CC# Chart
Unfortunately, the Griffin knob is not the best choice because there's no way to get it to connect without using the Griffin software.
There's a workaround which is to open a floating fader, click in the number window at the bottom of the fader and if you have the Griffin set to scroll up/down, it will then control the fader. My suggestion is that you get an app that allows you to program window position data and mouse clicks like Controller Mate for $25. Then use it to set up a few things. First a button that gives you an on off mode for the set up. I like the caps lock key because you can disable it in the Mac preferences. Plus they usually have a light. Then when it's on, use the keyboard's driver in controller mate to disable the keypad keys. From there map button 1 to use window location data to hover the cursor to over the floating fader button, then click with the left mouse button. Add a short delay of 0.02 seconds and then in the floating fader window, use that window's location data to hover the cursor over the numbers at the bottom and click with the left mouse. If you set it so that releasing the key sends the ctrl-opt-cmd-w keystroke, you can duplicate this set up across all of the buttons and as you hold a button the corresponding track's floating fader will pop up and position the cursor in the number window so that scrolling the Griffin will move the fader and this will continue as long as you continue to hold the button. Then the fader will disappear the moment you let go. You can also toggle it if you prefer. I'll go a little further and suggestion you use memory locations to open groups of tracks in 8-10. That way if you're looking at 10 drum faders, the keypad will map to them. When you select your guitar and key group of 8-10 faders, they'll pop up as the only 8-10 and the keypad will work for them now. It will eliminate scrolling in the mix window. I'm also saying groups of "faders" rather than "tracks" because I prefer to mix on aux tracks. It's an analogy for a console. When mixing on a console, your session set up is routing the tracks in protools to the converter outputs that correspond with the console channels and most people come up with a consistent layout so that instruments are always in the same place. By using aux tracks, you can build your own "console' within ProTools. Then you can make a session to use as a template. I think there are advantages to using stereo auxes in all cases, but for simplicity I'll describe it using mono auxes. Choose a "console" size. Let's say 48 channels. Now make 48 auxes and label them like you would label a console with tape - use names and color coding and even name the inputs in the routing set up. Use memory location points to recall groups of auxes, but assign them to a high number, like start a 101 so that auto created points don't end up changing the numbers. That will enable you to map the recall memory location keystrokes to a single key - or a pair of keys, like a modifier key + a keypad key, (and have the modifier disable the keypad while holding the modifier - this will make sense once you've set everything else up). Now, add you default plugin chains to each aux. You can also add effects sends and returns. What this means is that you've pre-built an entire "console" with identical or custom-to-the-instrument channel strips that's mapped to memory location points recallable with a single keystroke and then holding down a keypad key enables the Griffin knob to control the corresponding fader. To set up a session someone has sent you for mixing, you open their session, route all of the tracks to the correct aux inputs that are already labeled in your I/O set up and then go to Import Session Data and import your console with everything preloaded and mapped. It will take about a minute to add your entire template which is way faster than building it adding plugins as you go or using track presets. It the extra memory it uses is 48 mono axes worth, which is nothing. Then you have the source tracks with no plugins feeding your mix "channels". You also have the option of leaving everything they sent you inserted and starting with whatever parts work. Getting this set up the first time will take a while. But as you develop different approaches or get new plugins, you can duplicate that session, and make the changes in a new one. Use a session rather than a template since you have to open a template. It's far easier to work in their session and import your data. Once this all makes sense, you can start doing things like mapping the mutes and solos to the keyboard keys (as opposed to the keypad keys) 1-8. You can even use an auto repeated and use 1 to raise fader 1 and q to lower it. You keep track of whether your keyboard is in normal operation or your modified set up by toggling back and forth with the caps lock key and the LED cues you which mode you're in. Here's what that looks like: https://www.instagram.com/p/B3ggx1YATqY/ Quote:
|
#18
|
|||
|
|||
Re: Pro Tools Complete Midi CC# Chart
I have a question about "plugin select" which I think is CC 57.
I've been using the plugin cycling at 75 and the bank up and down and they all work fine. I'm pretty sure that at one point I had it working where after I navigated to the right plugin, I hit the button that sends CC 57 and it opened the plugin, but for some reason that doesn't work any more. The only things I can think of is that CC 57 is the wrong one, or the mode or flip settings are somehow changing/disabling CC 57. Any suggestions would be much appreciated. Also, plugin cycle only scrolls down through the plugins. Is there an option to cycle up? |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
ERXP::Scrolling past the last page of MIDI CC Chart will crash | TieDyedDevil | Eleven Rack | 2 | 03-25-2011 08:22 PM |
Pro Tools 9 Compatibilty Chart | tg4878 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 9 | 11-29-2010 08:44 AM |
Pro Tools LE and HD Comparison Chart? | Dizzi45Z | Tips & Tricks | 3 | 05-26-2008 12:13 PM |
HUI midi implementation chart | Hogie | MIDI | 3 | 10-03-2005 09:11 AM |
Mackie HUI MIDI Specifications - Midi implementation chart | yamyyy | Pro Tools TDM Systems (Mac) | 2 | 05-31-2001 07:16 AM |