USB controllers

r.erorr · Unread post by **r.erorr** » 26 Feb 2016, 15:45

I'm going to buy one of AKAI usb controllers, but I want know if there is possible to send feedback messages to controller, so I can see highlighted buttons of actually playing samples, blinking light or what ever. And if it is possible then how - patching scripting?

sephult · Unread post by **sephult** » 26 Feb 2016, 15:53

I have an Akai APC20 controller, they are generally mapped specifically for Ableton...but can be reverse engineered. I had created a APC20 sequencer in another thread with someone else using.

Typically the pads are note on/off messages, and there is also a sysex mode that needs to be set prior to set the latch on/off mode. It seems like it would be do able for what you are thinking. Possibly taking a sampler "playing status", then using this with a script to send the note on/off commands.

-s

r.erorr · Unread post by **r.erorr** » 26 Feb 2016, 19:26

So, the answer is scripting only? Sounds extremely sophisticated. Can you please share some visualizations of patching(if?) or script?

sephult · Unread post by **sephult** » 26 Feb 2016, 21:47

APC20 Sequencer Thread

Also do a search for akai, drakh also did an apc sequencer. I can help you along if this is the path you intend to use.
Yes there will be scripting necessary too, there is not much leniency in the way akai does their controllers as most the APC are made for ableton...but either way it's a useable controller. Regardless I use mine for all kinds of things even without the feedback. It's a quick and easy way to MIDI learn with whatever I need.

grego mondo · Unread post by **grego mondo** » 15 Mar 2016, 18:46

hello I've done this kind of feedback on a mpk mini (lighting the pads) ... just take your "is playing" from the sampler, then a "0to1" sends a "note on" and a "1to0" send a "note off" ... no scripting needed.

nay-seven · Unread post by **nay-seven** » 15 Mar 2016, 18:56

and generally (works with lanchpads) a simple midi learn on a switch (you need to set the switch and the device Midi out to motorized) works too !

r.erorr · Unread post by **r.erorr** » 22 Mar 2016, 23:49

grego mondo wrote:hello I've done this kind of feedback on a mpk mini (lighting the pads) ... just take your "is playing" from the sampler, then a "0to1" sends a "note on" and a "1to0" send a "note off" ... no scripting needed.

Finally got my APCmini . . .
Ok, I understand that MIDI messages can be triggered with 0to1 or 1to0 but how do you make that feedback? Do you mean lighting(something) on Usine or real physical pads? Could you please explain me more details?

drakh · Unread post by **drakh** » 04 Apr 2016, 10:20

nay-seven wrote:and generally (works with lanchpads) a simple midi learn on a switch (you need to set the switch and the device Midi out to motorized) works too !

yeh motorized works but...
..but only when you change the value from GUI for example if you click by mouse to button or something similar.
"problem" is when you press the button on your controller which is mapped to some switch. then the "motorized" option in automation does not work for the feedback. i am using one special patch for this purpose

Sal · Unread post by **Sal** » 04 Apr 2016, 17:19

Ugh, been having headaches about this for almost 2 years.
I've got the Akai APC mini to work with parameter feedback with some ugly hacking.
But when hacking takes more time then music production, I get depressed, which made me dump Usine for a while.
(The hack only partially does it's job, and does not work on my other controllers)
Since I like Usine anyway, I decided to buy Bome's midi translator and see if that gives me less headaches with midi communication.
(To be continued)
Now the solutions in Usine are (or should be) very simple, but,,,,
without help from specialists here it's hopeless for most..

Getting more attention to midi controller edit possibilities, or some basic example presets to dissect, would be a huge help.
(And a pretty female psychoanalyst to hold my hand and pat my back while experimenting,
and a special usine D/A converter so it can pour me fresh coffee,,,)

Interesting thread btw

cmodica · Unread post by **cmodica** » 06 Apr 2016, 18:20

i have the same problem with my LaunchControl. the pad of the controller is lighting when i clic on the switch in Usine. But if i use the controller to active the swith, the pad doesn't light back ...

nay-seven · Unread post by **nay-seven** » 06 Apr 2016, 18:42

Yes, because this family of controller wait for a specific velocity value to choose colors , ON/OFF states and so.
You need to create a patch ( with MIDI out) and use a create midi module with the good value .

cmodica · Unread post by **cmodica** » 07 Apr 2016, 12:19

Thank you.
It works with a midi out module. Not realy usefull because it needed to add somme modules and a midi out device on each rack. But it works. The LaunchControl PAD are lighting on and off when i push on it

La Tenaille · Unread post by **La Tenaille** » 07 Apr 2016, 13:05

For my controllers I've added a data delay module before the create pin, because if you send the message whith pressing your button, your finger cancels the message. Even so you need to release your finger before the delayed message is sent.

cmodica · Unread post by **cmodica** » 07 Apr 2016, 16:11

Yes. that's why i put a "Wait 1 block" module before the create pin. Like that, i am sure that it didn't create midi message before set the Val2.

drakh · Unread post by **drakh** » 07 Apr 2016, 17:37

Here is my solution ( https://github.com/drakh/hollyhock-libr ... mapper.pat )
this is how the feedback works from inside

and this is how it is patched with the switch

so basicaly, you use standard midi mapping function in Hollyhock you map your switch to button which should have feedback, and connect to it the subpatch which is doing al the work.
The subpatch is sending the data to midibus, so you need to ad into midi out device patch "get from midibus" element and select correct midi bus ( i am using for that this one helper https://github.com/drakh/hollyhock-libr ... SELECT.pat )

this solution should react to your actions from GUI, and as reflects the changes from maped MIDI automation. And it should as well initialize state of the LED on controller when you press play.

just grab my hollyhock library from git

https://github.com/drakh/hollyhock-library (using some GIT client, or clicking to "download as zip" on the homepage of the repository

drakh · Unread post by **drakh** » 07 Apr 2016, 17:41

and yeah i think, the whole midi learning function is littlebit hms how to say....."funny/outdated" and it would be nice when it will work in a little bit different way. for me example of good midi mapping (with feedback etc) is native instruments Traktor

cmodica · Unread post by **cmodica** » 07 Apr 2016, 19:22

Yes, it would be nice when it will work in a little bit different way.

No time to test your patch before take my train an going to work on my new project for two weeks. I will work with Hollyhock without your patch, but i hope to test it as soon as possible.

it seems to be a realy intertesting solution to patch the feedback faster and more usefull.

Thank you, very much.

cmodica · Unread post by **cmodica** » 08 Apr 2016, 10:25

I take time to test and it works. Great !

i just had to delete the "const" module link to the Chan Pin of "Create Midi" and link the "Data In Chan" module to the Chan Pin of "Create Midi" module.

I think i will add something link to the B of the " * " Math Module to select the color of the swith. And it will perfect.

Thank you

drakh · Unread post by **drakh** » 08 Apr 2016, 13:10

cmodica wrote:I take time to test and it works. Great !

i just had to delete the "const" module link to the Chan Pin of "Create Midi" and link the "Data In Chan" module to the Chan Pin of "Create Midi" module.

I think i will add something link to the B of the " * " Math Module to select the color of the swith. And it will perfect.

Thank you

heh yes i am generating the midi event on channel 1, as all my HW controllers are configured to send/recieve on channel 1

Sal · Unread post by **Sal** » 11 Apr 2016, 18:58

Hi drakh, thanks for the saving hand.

I´d like to bother you for a few more questions,,
(Gets into tutorial mode)

You said,,
so basicaly, you use standard midi mapping function in Hollyhock you map your switch to button which should have feedback,

Check,, I use the shortcut ´Ctrl m´, click (in my case) the ´bypass´ button on my vst plugin, and hit a key on my Akai APC mini, and hit ´Ctrl m´ again to shut of the process..
(After I switched on motorized on the APC mini midi output, which I put in the rack output section)

And then you said,,
, and connect to it the subpatch

How ???
Do I need to put it in the vst patch in the patch-editor as a subpatch ?
And how do I connect ?

And,,
The subpatch is sending the data to midibus, so you need to ad into midi out device patch "get from midibus" element and select correct midi bus

Uhm,, could you elaborate ?
Are you talking about the MIDI BUS SELECT patch you made ?
Where/how should this be connected ?

I hope I dont bother you to much, but I would really like to get this working,,

drakh · Unread post by **drakh** » 12 Apr 2016, 17:27

Sal wrote:Hi drakh, thanks for the saving hand.

I´d like to bother you for a few more questions,,
(Gets into tutorial mode)

You said,,
so basicaly, you use standard midi mapping function in Hollyhock you map your switch to button which should have feedback,

Check,, I use the shortcut ´Ctrl m´, click (in my case) the ´bypass´ button on my vst plugin, and hit a key on my Akai APC mini, and hit ´Ctrl m´ again to shut of the process..
(After I switched on motorized on the APC mini midi output, which I put in the rack output section)

- "midi control led mapper" works as "motorized" so you don't need to turn on the motorized option in mapping but i think better motorized send data just hwen you click to GUI element. my patch reads the state of the switch and sends data whenever it changes - when you click to the switch from GUI, or you press the button on your controller which causes switch state change

And then you said,,
, and connect to it the subpatch

How ???
Do I need to put it in the vst patch in the patch-editor as a subpatch ?
And how do I connect ?
- the second picture is exact with the switch and "midi control led mapper" is exact example what you need to do. if you need to control your VST you have to connect the switch to the VST parameter which you want to control.

And,,
The subpatch is sending the data to midibus, so you need to ad into midi out device patch "get from midibus" element and select correct midi bus

Uhm,, could you elaborate ?
Are you talking about the MIDI BUS SELECT patch you made ?
Where/how should this be connected ?

1. click on the devices icon to open the devices panel
2. doubleclick on your midi out device (i don't have midi controller connected now, so i opened the midi lan device, in your case it would be APC MINI or so)
3. add "midi bus select" to your output device patch and in the properties panel of the "midi bys select" subtach select "control panel" for the "where" property, so the selectbox will be visible in your midi out device when you click the open/close icon of the device

I hope I dont bother you to much, but I would really like to get this working,,

manu · Unread post by **manu** » 02 May 2016, 11:47

Welcome to %s forums

USB controllers

Who is online

Login • Register