November 12, 2017 at 12:29 am #73483
Today I played with the XY-Pad in Ctrlr and I realized that although I can control modulators assigned ti X and Y with it there is no visual feedback when I change the values of modulators that are X and Y.
I was under the impression that a modulator in Ctrlr is always bidirectional so whatever it sends it always reacts to. This is the case with Knobs and Sliders but somehow is not with XY-Pad. Can you guys confirm this on your systems. Maybe there is a setting that I am not aware of that enables the visual feedback on XY-Pads?
On my panel there is an option to show big XY-Pad instead of two small sliders for better and more accurate control but it seems kinda useless to me if the pad is not reacting to the changing values of both sliders. And to be clear I mean the visual feedback when the sliders values are changing (form DAW automation for example) and the XY-Pad is not touched with the mouse at the moment. To my understanding the “ball/circle” should move following the XY coordinates of changing values. Any ideas or known issues?
Thanks!November 12, 2017 at 6:19 am #73486
should it not have a method associated with it?
eg: x with a mapped value, y with a mapped value, so it
can interpret both incoming events.
the one in my panel (which i must’ve copied over from a
panel i opened) have ‘onValueCange’ method set to ‘metXYpad’
-can’t remember where that comes from, but if you can find it,
it might have a useful method.November 12, 2017 at 1:05 pm #73493
I can’t think of any method that will be resposible for the feedback on my XY pad. When I use the pad the associated Knobs are moving only the other way around it is not working. When I move knobs I should see XY pad mirroring the changes but nothing seems to happen.
If your XYpad works properly I would of course appreciate the Lua method that is associated.
Cheers!November 12, 2017 at 3:02 pm #73495
Same thing happens here, XYpad cotrols the assigned knobs and can write automation but as soon as automation is in Read mode Knobs are moving to the changing values but the XY does nothing.
November 13, 2017 at 12:13 am #73505
- This reply was modified 1 week, 5 days ago by proton.
bump!November 13, 2017 at 3:08 am #73508
You’ll probably have to write an onValueChange method for the knobs that update the value of the pad. You’ll need some sort of check to make sure to don’t generate a feedback loop (ie when you change the value on the xy-pad it updates the knobs, but when the knob updates, it will try to update the xy-pad, which will then trigger ctrlr to update the knob, etc.
http://godlike.com.auNovember 13, 2017 at 3:11 am #73509
The other thing you may be able to do in Ableton is automate the x-y pad rather than the knob. The X-Y pad will need VST parameters that can be assigned from Ableton to do this. I haven’t used the X-Y pad, so not sure if this is possible, but if you can Ableton would actually play bay the X-Y pad, rather than the knobs. The X-Y pad then moves the knobs.
http://godlike.com.auNovember 13, 2017 at 1:11 pm #73513
yes in theory this is what I thought but it looks like XYpad is not even changing its own “Current Modulator Value”. This is why I think it is able to control the assigned Modulators for X and Y axis but it is not able to receive any feedback and that makes it kinda useless really if you ask me and creates even more confusion when user “think” the values are represented by the position of the “ball” on the XY canvas but they are not.
Any ideas on the ev. Lua method that could somehow make it respond to changing values? This will be my last try or I will have to give up on XYpads completely.
You must be logged in to reply to this topic.