MIDI learn #50
MIDI learn #50
Comments
|
Andrew Belt say "MIDI learn might land in v1.0 in November/December." :-) |
|
A MIDI CC in with 32 output jacks for all the 14 bit controllers looks most
general. Has any one ever had a controller which needed learn which was not
one of those? Maybe it would need a flashing light so that the control
could be seen.
…On 13 September 2017 at 07:58, nay-seven ***@***.***> wrote:
Andrew Belt say "MIDI learn *might* land in v1.0 in November/December."
:-)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#50 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAkQlUu8ZMTjM1EnUOeKmaed9cOR_LyRks5sh30TgaJpZM4PVc_2>
.
|
|
I'll make a MIDICC2CV module with 16 changable CC outputs in Core later, which is closer to what you're talking about. But this issue's request is about MIDI-to-knob mapping in Rack itself. |
|
@AndrewBelt Are you working on this? I might try to implement it, need this asap. Already mapped 2 of knobs by modifying current midi module (my novation launch key mini has no pitch or mod wheels) |
|
It might be ~3 weeks before I can get around to the MIDI Interface revamp, and MIDI learn will likely be even after v1.0 releases. It's still on the TODO list though. If you need it urgently because of a live show or something, you can hack MidiInterface.cpp near the lines
by changing the |
|
Yeah, already figured it out :)
…On 22 Sep 2017 20:48, "Andrew Belt" ***@***.***> wrote:
It might be ~3 weeks before I can get around to the MIDI revamp, but I'll
do this before the Audio revamp.
If you need it urgently because of a live show or something, you can hack
MidiInterface.cpp near the lines
case 0xb: // cc
switch (data1) {
case 0x01: // mod
by changing the data1 hex number to whatever your controller emits. Then,
the Mod output will respond to that controller knob.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#50 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA7nFZO5Aob8AA8t7G7jhoAsKdurMENAks5sk_L0gaJpZM4PVc_2>
.
|
|
Sorry for the other duplicate request post. +1 on OP here. Would LOVE to see Midi Learn added at some point if coding time etc allow. |
|
Can't wait to this feature! I would defenitely abandon Reaktor for VCVRack when Midi learning is supported. Thanks for all of your effort! |
|
What would be the proper way to implement this? Is there a preferred way to send messages from one module to another (except via Wire::step())? |
|
The way I'll do it is have a special MIDI-learn core module and a special GUI for hooking up knobs to MIDI channels. No MIDI wires. |
|
@AndrewBelt That's exactly how I had imagined it. Thanks for putting this on board! We love you and VCVRack :D |
|
Need this to control filters, functions with midi fighter twister if I figure out a template I’ll share it! |
|
Would be great to have an "Instant Mapping" mode for MIDI Learn - to address the problem of 1 physical controller meeting a high number of virtual controls and dynamic modules placements. E.g. always map all knobs of active module. Use case would be right hand mouse-navigation to activate modules, left hand could stay on controller moving knobs of that active module. |
|
any progress on this feature? |
|
@amp3rsand Won't start until Rack 1.0 development is active, which will be 4-6 months from now. |
|
Thanks for your great work on Rack @AndrewBelt! When it's time for this feature, might be cool to consider bidirectional mapping -- so ppl with controllers that programmatically show current position (lighted encoders, touchscreen apps) can get proper feedback if they turn mapped knobs from within Rack. This would also open up the possibility of using another program with a more timeline-based UI paradigm to snapshot and sequence parameter changes. |
|
+1 for a Midi-learn feature, that would be brilliant. |
|
Is this still on track for the 1.0 release ? |
|
It was in my suggestions list, i would really support this feature.. how can we help this one to come up ? |
|
Not sure how we can get them to implement thus feature but it sure would
make it much more tactile.
…On Thu, 24 Jan 2019, 17:38 Uriel Deveaud, ***@***.***> wrote:
It was in my suggestions list, i would really support this feature.. how
can we help this one to come up ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#50 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEsYkpNN32ay6WhVvPZyOMzzxXFRB_Weks5vGe-xgaJpZM4PVc_2>
.
|
|
+1 for this feature. Its the one big thing I'm missing! |
|
It's working on rack v1-gpl (branch) for those who can't wait, I absolutely love this feature! |
|
@0mars If you have a Mac release to share, i'm interested ;-) |
|
@nay-seven unfortunately, I don't have a mac. |
|
ok, no problem, thanks anyway ;-) |
|
Has this feature been implemented in the recently released version 1.0? |
|
Yes, I believe this can be closed |
It would be awesome if modules' knobs could be mapped to MIDI controllers.
The text was updated successfully, but these errors were encountered: