]]>
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,,
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,,
Statistics: Posted by drakh — 12 Apr 2016, 17:27
]]>
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,,
Statistics: Posted by Sal — 11 Apr 2016, 18:58
]]>
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 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
Statistics: Posted by drakh — 08 Apr 2016, 13:10
]]>
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
Statistics: Posted by cmodica — 08 Apr 2016, 10:25
]]>
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.
Statistics: Posted by cmodica — 07 Apr 2016, 19:22
]]>
]]>
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 repositoryStatistics: Posted by drakh — 07 Apr 2016, 17:37
]]>
]]>
]]>
Statistics: Posted by cmodica — 07 Apr 2016, 12:19
]]>
Statistics: Posted by nay-seven — 06 Apr 2016, 18:42
]]>
]]>
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
Statistics: Posted by Sal — 04 Apr 2016, 17:19
]]>
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
Statistics: Posted by drakh — 04 Apr 2016, 10:20
]]>
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?
Statistics: Posted by r.erorr — 22 Mar 2016, 23:49
]]>
]]>
]]>
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.
Statistics: Posted by sephult — 26 Feb 2016, 21:47
]]>
]]>
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
Statistics: Posted by sephult — 26 Feb 2016, 15:53
]]>
]]>