Hans Mittendorf

I want to control a plug in via fader. I have a motormix conected and have put midiin midiparse unpack ctlin numer box inside a patch.

When I push the fader, only one number is shown. When I add print MIDI, I have some numbers running up tp 127 in relation to the fader.

Why do I not get the control output right?

Hello,
I want to control a plug in via fader. I have a motormix conected and have put midiin midiparse unpack ctlin numer box inside a patch.
When I push the fader, only one number is shown. When I add print MIDI, I have some numbers running up tp 127 in relation to the fader.
Why do I not get the control output right?


midi-control-via-motormix

Quote: hans.mittendorf@free.fr wrote on Tue, 22 May 2007 15:55

----------------------------------------------------

> I want to control a plug in via fader. I have a motormix conected and have put midiin midiparse unpack ctlin numer box inside a patch.

> When I push the fader, only one number is shown. When I add print MIDI, I have some numbers running up tp 127 in relation to the fader.

> Why do I not get the control output right?

Could you post the patch that you're using?

Quote: hans.mittendorf@free.fr wrote on Tue, 22 May 2007 15:55
----------------------------------------------------
> Hello,
> I want to control a plug in via fader. I have a motormix conected and have put midiin midiparse unpack ctlin numer box inside a patch.
> When I push the fader, only one number is shown. When I add print MIDI, I have some numbers running up tp 127 in relation to the fader.
> Why do I not get the control output right?
----------------------------------------------------

> I want to control a plug in via fader. I have a motormix conected and have

> put midiin midiparse unpack ctlin numer box inside a patch.

> When I push the fader, only one number is shown. When I add print MIDI, I

> have some numbers running up tp 127 in relation to the fader.

Darwin Grosse developed externals and patches for motormix i/o which work

great for total integration. That should get you started on whatever you

https://cycling74.com/twiki/bin/view/Share/DarwinGrosse

On 5/22/07, Hans Mittendorf  wrote:
>
>
> Hello,
> I want to control a plug in via fader. I have a motormix conected and have
> put midiin midiparse unpack ctlin numer box inside a patch.
> When I push the fader, only one number is shown. When I add print MIDI, I
> have some numbers running up tp 127 in relation to the fader.
> Why do I not get the control output right?
> _

Darwin Grosse developed externals and patches for motormix i/o which work
great for total integration. That should get you started on whatever you
want to control with it.

You have seriously misunderstood the idea of ctlin and midiparse. One look at the ctlin helpfile should solve your problem.

I had two looks at the helpfile took out ctlin but midiparse is still not clearer. should the patch be midiin midiparse unpack pack

Mattijs,
I had two looks at the helpfile took out ctlin but midiparse is still not clearer. should the patch be midiin midiparse unpack pack


Since the midiparse object outputs a list of two values

(the controller number and its value), you'll need to

unpack the list to get the values you need. You may find

the route object useful for being able to output a

Since the midiparse object outputs a list of two values
(the controller number and its value), you'll need to
unpack the list to get the values you need. You may find
the route object useful for being able to output a
specific controller.


Also note that the Motormix faders are high resolution, they send TWO CC messages for each value, one MSB, one LSB. Refer to the Motormix developer documentation.

So ctlin is not the way to handle this, you'll need to use midiin and match or perhaps midiin and midiparse.

Also note that the Motormix faders are high resolution, they send TWO CC messages for each value, one MSB, one LSB. Refer to the Motormix developer documentation. 

So ctlin is not the way to handle this, you'll need to use midiin and match or perhaps midiin and midiparse.


Quote: johnpitcairn wrote on Tue, 22 May 2007 23:46

> So ctlin is not the way to handle this, you'll need to use midiin and match or perhaps midiin and midiparse.

That's exactly what he was trying. Maybe have a look at the patch he posted ;)

Quote: johnpitcairn wrote on Tue, 22 May 2007 23:46
----------------------------------------------------
> So ctlin is not the way to handle this, you'll need to use midiin and match or perhaps midiin and midiparse.
>

Hello everyone who has contributed to this subject.

As it stands at this point, I guess that midiparse is not reading the incoming raw midi from the motormix prperly. When I connect it to unpack and a number box, only 32 is shown and it does not move.

On the other hand, I have installed Darwin's motormix objects and it is a cheerful moment when you see the faders moving up one after each other! I guess that Darwin should know how to plug the patch for incoming midi from the mm.

I still need to figure out how to route the individual faders, since they are meant to control different plug ins. If someone has done this already, I would be happy to learn from him. 

Hello everyone who has contributed to this subject.
As it stands at this point, I guess that midiparse is not reading the incoming raw midi from the motormix prperly. When I connect it to unpack and a number box, only 32 is shown and it does not move.
On the other hand, I have installed Darwin's motormix objects and it is a cheerful moment when you see the faders moving up one after each other!  I guess that Darwin should know how to plug the patch for incoming midi from the mm.
I still need to figure out how to route the individual faders, since they are meant to control different plug ins. If someone has done this already, I would be happy to learn from him. 
cheers


> Hello everyone who has contributed to this subject. As it stands at

> this point, I guess that midiparse is not reading the incoming raw

> midi from the motormix prperly. When I connect it to unpack and a

> number box, only 32 is shown and it does not move.

10 or 14-bit Midi is composed of two controller messages, 32 appart. You 

just see the last, which is the LSB. You need to use both and compose 

It should work with ctlin only (have no motormix here, can't test it...):

Hans Mittendorf schrieb:
> Hello everyone who has contributed to this subject. As it stands at
> this point, I guess that midiparse is not reading the incoming raw
> midi from the motormix prperly. When I connect it to unpack and a
> number box, only 32 is shown and it does not move. 

10 or 14-bit Midi is composed of two controller messages, 32 appart. You 
just see the last, which is the LSB. You need to use both and compose 
the value you want out of it...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


cool job done!! It works, I can send from three different faders. But, the numbers I want are 0 to 127 and I am not sure on how to make up the calculation for that in your patch.

cool job done!! It works, I can send from three different faders. But, the numbers I want are 0 to 127 and I am not sure on how to make up the calculation for that in your patch.
Thanks for your help!


O.K thanks to Stefan, I have this solution to use a motormix fader input

#P number 157 289 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

O.K thanks to Stefan, I have this solution to use a motormix fader input
max v2;
#N vpatcher 38 59 638 459;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 159 240 27 196617 / 2;
#P newex 158 141 37 196617 midiin;
#P number 157 289 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 157 265 27 196617 +;
#P newex 156 215 29 196617 << 1;
#P newex 156 188 50 196617 ctlin 0 1;
#P connect 4 0 0 0;
#P connect 0 0 1 0;
#P connect 5 0 2 0;
#P connect 2 0 3 0;
#P connect 1 0 5 0;
#P pop;
Thanks Stefan!


> cool job done!! It works, I can send from three different faders.

> But, the numbers I want are 0 to 127 and I am not sure on how to make

> up the calculation for that in your patch. Thanks for your help!

just use ctlin 0, 1, 2, 3, 4, 5, 6, 7 and ignore the LSB part...

Hans Mittendorf schrieb:
> cool job done!! It works, I can send from three different faders.
> But, the numbers I want are 0 to 127 and I am not sure on how to make
> up the calculation for that in your patch. Thanks for your help! 

On 23 mai 07, at 20:35, Stefan Tiedje wrote:

> 10 or 14-bit Midi is composed of two controller messages, 32 appart. 

> You just see the last, which is the LSB. You need to use both and 

> compose the value you want out of it...

> It should work with ctlin only (have no motormix here, can't test 

For my behringer bcf2000, it doesn't if it's connected thru USB but 

does if I plug it on my Midi interface...

But it works with [midiin] in both cases!

Centre de Recherches et de Formation Musicales de Wallonie asbl

> Hans Mittendorf schrieb:
>
> 10 or 14-bit Midi is composed of two controller messages, 32 appart. 
> You just see the last, which is the LSB. You need to use both and 
> compose the value you want out of it...
>
> It should work with ctlin only (have no motormix here, can't test 
> it...):

Nice to read it works for a motormix.
For my behringer bcf2000, it doesn't if it's connected thru USB but 
does if I plug it on my Midi interface...
But it works with [midiin] in both cases!

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl
http://users.skynet.be/crfmw/max


Note that ctlin will not receive the LSB of an MSB/LSB pair anyway, so nothing is coming in on CC32 for the posted example. If you want the full resolution of the MotorMix faders, you MUST either use midiparse, or roll your own MSB/LSB recognition system connected directly from midiin.

See my reply to the other MotorMix (output) thread for an example.

midi control via motormix