42Noir

A new way to control midi-controllers in Max (only Mac OS). If you are tired of mapping your controller over and over again, or you think even for one second which parameter controls what?...I suggest you to download this standalone patch. As an artist programmer and a performer in 42Noir, I have learned that you must make the midi mapping generic, robust, and reliable. It will help you stay focused on the creative part of max programming, and on stage will give you more confident in playing your interface.

Highlight features: Automatic mapping, Easy max control, Presets, Controller Labels.

We developed few external objects to interact in a very simple way with the app, and the standalone app can run on the background of your performance (won't take any computer resource from the max process, and also no collisions with your patch!). For download and more information please visit our website.

We use it in our performance and now you can use it too, for free.

A new way to control midi-controllers in Max (only Mac OS). If you are tired of mapping your controller over and over again, or you think even for one second which parameter controls what?...I suggest you to download this standalone patch. As an artist programmer and a performer in 42Noir, I have learned  that you must make the midi mapping generic, robust, and reliable.  It will help you stay focused on  the creative part of max programming, and on stage will give you more confident in playing your interface.

Highlight features: Automatic mapping, Easy max control, Presets, Controller Labels.

We developed few external objects to interact in a very simple way with the app, and the standalone app can run on the background of your performance (won't take any computer resource from the max process, and also no collisions with your patch!). For download and more information please visit our website. 

We use it in our performance and now you can use it too, for free.

easycontroller

So cool!! I'm having some trouble getting the presets to save. I moved the application file to a separate folder right away and yet it still won't save. The preset button doesn't even change color when clicked. Connects well within Max though. Do you know what the issue could be?

Hi Wes, glad to hear from you. Is it only the presets? Do you see 2 files created in the current app folder when you opened the app? (map.txt and preset.jascon)

Just to make sure, you need to move only the app to a different folder without any other files.

Hi Wes, glad to hear from you. Is it only the presets? Do you see 2 files created in the current app folder when you opened the app? (map.txt and preset.jascon)
Just to make sure, you need to move only the app to a different folder without any other files.


Limitations like that should be mentioned up front.

yes, I forgot to mention it here.
Thanks.


recently I tried to setup my Faderfox LV3 with EasyController. But it is not working as I expected. The sliders on the LV3 sends

I only can map the first slider, and the s1...s8 move always together, nevertheless I assigned Slider 2 ( cc7, ch 2) to s2 etc.

Is there a mode to clear all assignments?

And is there a implementation of incremental knobs?

Hi,
recently I tried to setup my Faderfox LV3 with EasyController. But it is not working as I expected. The sliders on the LV3 sends
1. Slider cc7 ch1
2. Slider cc7 ch2
...
(as I can see in Max or MIDI-Monitor).
I only can map the first slider,  and the s1...s8 move always together, nevertheless I assigned Slider 2 ( cc7, ch 2) to s2 etc.

Is there a mode to clear all assignments?
And is there a implementation of incremental knobs?

Just to make sure, when you monitor your sliders in midi, does it show the standard number:

if its bigger than 176 but below 192 you probably on different midi channel, and maybe you can try to switch to channel 1. If your Faderfox has a unique midi message format, ie not the standard format 176 nn nn , I can help you fix it and designate it to your Faderfox, then send it over to you, by letting me know the numeric output of the midi when you move sliders. If you however have the standard format 176 nn nn, just go to the map text file that is created in the folder, and see what went wrong there. you can correct it manually by changing the cc to everything and save it. You can also delete everything and re-assign all the sliders.

Let me know if you have a problem with it, it seems like an easy fix for the application, sometimes controllers doesn't follow standard protocol...

Hi Klangschmied,
Just to make sure, when you monitor your sliders in midi, does it show the standard number:
ie 176 nn nn?
if its bigger than 176 but below 192 you probably on different midi channel, and maybe you can try to switch to channel 1.  If your Faderfox has a unique midi message format, ie not the standard format 176 nn nn , I can help you fix it and designate it to your Faderfox, then send it over to you, by letting me know the numeric output of the midi when you move sliders. If you however have the standard format 176 nn nn, just go to the map text file that is created in the folder, and see what went wrong there. you can correct it manually by changing the cc to everything and save it.  You can also delete everything and re-assign all the sliders.
Let me know if you have a problem with it, it seems like an easy fix for the application, sometimes controllers doesn't follow standard protocol...
cheers,
Shalti (contact@42noir.com)


Hi 42noir,
thanks for your fast answer.
In Max 6 I can see:

Fader 1 (LV3):  176 7 nn (nn = 1 to 127)
Fader 2 (LV3):  177 7 nn
.....to....
Fader 8 (LV3):  183 7 nn.

The map-file is:
1, 7;
2, 7;
3, 7;
40, "LV3-1 Faderfox LV3";
4, 7;
5, 7;
6, 7;
7, 7;
8, 7;
21, -1;
22, -1;
23, -1;
24, -1;
25, -1;
26, -1;
27, -1;
28, -1;
29, -1;
30, -1;
31, -1;
32, -1;
33, -1;
34, -1;
35, -1;
36, -1;
11, 7;
12, 1;
13, 1;
14, 7;
15, 7;
16, 7;
17, -1;
18, -1;
0, 7;
20, -1;

Ok, thanks for the info, I see the problem. The standard format is that 176 is constant and the second arg is changing. I will add a quick change for your faderfox this week, and hopefully it will workout straightaway. I will send you a link here, or you can send me an email and I'll send you.

Ok, thanks for the info, I see the problem. The standard format is that 176 is constant and the second arg is changing. I will add a quick change for your faderfox this week, and hopefully it will workout straightaway. I will send you  a link here, or you can send me an email and I'll send you.


hi in the new version you can change on the midi format tab to " by channel". It should solve the problem, let me know if that works.

hi in the new version you can change on the midi format tab to " by channel". It should solve the problem, let me know  if that works.

thanks for implementing MIDI format, now it works!

One question: How can I clear an assignement?

The MIDI Format always jumps back to the "Standard" when starting EasyController. Could "By Channel" stored as a deafult?

The MIDI Format always jumps back to the "Standard" when starting EasyController. Could "By Channel"  stored as a deafult?

hi great! you can clear an assigment by deleting the txt file or overiting. I will do the option for default and let you know. Let me know if you have other suggestions/improments cheers.

hi great! you can clear an assigment by deleting the txt file or overiting.  I will do the option for default and let you know. Let me know if you have other suggestions/improments cheers.

EasyController

2017-01

UK/Israel