-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Q: Text feedback for virtual target #832
Comments
Sorry for the late reply. You need two virtual control elements for this. Otherwise I don't see how it can work. It's two separate labels, so there should be two virtual IDs. However, in my opinion, using the the controller compartment / virtual control elements with OSC is too much indirection. I would probably just use the main compartment. Well, depends on the use case. Any specific reason you going the "virtual" detour? |
Hi @helgoboss! Thanks for your attention. My goal in using the controller compartment is to reduce the number of mappings in the main compartment.
I have already achieved this result using only the main compartment, the problem is this solution demands 64 mappings (16 MIDI controls and 48 OSC feedbacks) for each VST plugin I want to map, which makes the process of mapping a new plugin very time consuming. So, the feature I think could make it possible is having the target in the main compartment send BOTH text feedback to the OSC labels and numerical feedback to the OSC knob. Does it make sense? Thanks again for your support for creating the awesome tool that is Realearn! |
I think I understand. I guess that would need a new type "Both" in addition to "Numerical feedback" and "Textual feedback". Or rather, it would need to be possible to use both at the same time with the same mapping. Then, on the controller compartment side, there would be 2 mappings with the same virtual target, one which takes care of displaying the numerical feedback (to OSC address A) and the other one for displaying the textual one (to OSC address B). Just thinking out loud. Not sure if I want to add this because it makes things more complex. Have you tried ReaLearn Script = creating the mappings via Lua? This is what I usually do if it gets annoying to add multiple similar mappings. |
Just adding the input field for text feedback on the virtual target wouldn't work? Or the feedback options is only set in the actual mapping, within the main comportment? I will take a look at ReaLearn Script, haven't tried it yet. Thanks for the advice! |
Hi!
I'm trying to create a Controller mapping for a custom Touch OSC layout I made to function as a screen for my Arturia Minilab MK II, with 16 encoders and 2 labels each. Each knob has a label for a parameter name and a label for the current parameter value. I created three mappings for the first knob: one for the knob itself (with control and feedback enabled) and two for the labels (only with feedback enabled), and assigned all of them to the same Virtual Multi number. Then, I added a mapping on the main compartment, selected the corresponding virtual source.
The problem is: I can't find a way to send different types of feedback to the same multi. My goal is to send numeric feedback to the knob and text feedback (with placeholders for the parameter name and textual parameter value) to the labels. I was expecting I could select "text feedback" on the labels mapping on the controller compartment, but that field is missing. Is there a way around this or it's actually a limitation?
Mapping window for virtual targets without the text expression field

Expected feedback (text and numerical feedback from the same target)

Actual feedback (same feedback type for both sources)

The text was updated successfully, but these errors were encountered: