Newbie Question about exceeding 127 Parameters

[drdelasquish]

Hey Everyone,

Newbie here with a dumb question. To my limited understanding there are 8 available midi targets within Lemur, each capable of sending 16 channels of 127 CC's. So in my mind I'm thinking even if I only used one midi target, I could still create a lemur controller that is theoretically capable of sending and controlling at least up to 2,032 parameters on a virtual synth, sequencer, etc. However, using lemur with Pro Tools 11 HD, I'm struggling to figure out how to access all of them. Right now, I'm only able to use 127 parameters in a single instance of Lemur. When I make my way up to Channel 1, Control 127, and I circle around to Channel 2, Control 1, the parameter simply controls the same parameter assigned to Channel 1, Control 1.

Is it possible to build a template with more parameters than that? Right now I'm building an interface for Izotope's Iris 2, and I'm not even half way done, and I'm not even using any of the z parameters or functions, only x.

Thanks for the help! I'll take any advice I can get!
Cheers

[Macciza]

Hi
Sounds like a PT issue , or similar . .
Yes Lemur will send MIDI on different channels, check with a MIDI monitor to make sure if you want . . .
If it is sending them properly then it is PT not interpreting them properly - maybe like Live they aggregate all incoming MIDI to a single channel.

I would suggest checking PT docs or help to see if PT actually will allow multiple channels to be mapped . . .
It should I think, because the MackieControl stuff sends on multi channels - It may be an issue particular to the plugins . . .

Also be aware that some CCs are pre assigned to particular purposes, particularly above 120,(All notes off, Reset etc) and probably should not be used for general purposes

Cheers

[drdelasquish]

@ Macciza

Great feedback. I thought it might be pro tools so I tried with the standalone version of Iris 2 and it still didn't work. However, I started to notice a ton of glitches in Iris 2's midi mapping as soon as I started assigning what I had so far. Reading your note on it possibly being an issue with the sampler instrument is something I didn't think of. I'll try with a different instrument.

Thanks!

[Phil999]

often there is an "omni" mode how a device or DAW receives MIDI data - mostly for receiving MIDI notes from a keyboard that often changes the MIDI channel. In Lemur (and any MIDI controller) this should be avoided in many situations and for different reasons.

[drdelasquish]

[img]Midi%20Channel%20Test[/img]

Ok so I just performed a test using a 3rd party software. I had two faders (CC5 Chn1 and CC5 Chn2) and they read independently of eachother. However whether I'm testing it in Pro Tools, or stand alone versions of Iris 2, Absynth 5, or Reaktor 5, the result is the same; Anything mapped to channel 2 controls the corresponding CC of channel 1. Which means I'm still currently unable to add more than 127 objects for parameter control.

Since it's happening in stand alone plugins as well as within pro tools, I don't think it's a pro tools issue. Is it possible that its my os? (OXS 10.9.3) Anyone else using Mac?
Or maybe I should try a hardware connections through an IO dock or something instead of using AdHawk?

[Phil999]

no, it's only a MIDI issue. Your instrument/DAW receives in omni mode and therefore receives all channels, regardless on what channel you send data. Standalone synths usually receive all 16 channels, that's what you're observing.

In most DAWs/hosts you can receive/send MIDI data for every MIDI port and MIDI channel, giving you thousands of accessible parameters (continuous controller, note on/off, aftertouch, etc.). Unfortunately I don't know how to do this with ProTools. My advice is to ask about this in a ProTools forum or PT support. Do not mention Lemur because it is only a MIDI thing.