If you have a problem or need to report a bug please email : support@dsprobotics.com
There are 3 sections to this support area:
DOWNLOADS: access to product manuals, support files and drivers
HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects
USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here
NEW REGISTRATIONS - please contact us if you wish to register on the forum
Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright
Simultaneous control of knob/xy pad
Simultaneous control of knob/xy pad
Hi there,
Attached is a control scheme I've been working on. I'm having some issues with it and was wondering if anyone had any suggestions?
It's part of a VST in which 2 methods are provided to control some parameter - an xy pad and a knob.
This means that, in order to work realistically, the two control methods also need to control one another.
So far, the knob can be controlled using the pad and it's working very well. However, I'm struggling with the knob controlling the pad. I am able to move the xy pad cursor using the knob, but when I stop dragging, the knob snaps back to its initial position. I've been at this for a few hours now, but still no luck. Does anyone have any suggestions? I'll explain what I've done so far:
The method I've used might not be the most efficient way. The pad outputs a value of 0 - 1. This output enters the knob control module and into a select primitive. The select is controlled by the "interact" boolean on the DragY primitive. If the knob is not being dragged, the output from the module is the pads value, else it is the knobs value, hence the pad can control the knob.
Inside the pad, there are other selects. One is controlled by the boolean variable of the DrgXY primitive. It determines what value is sent to the F2A primitive. If the pad is being used, the pad's own X value is sent to the F2A. If it is not being used, the knobs output value (scaled to match the pads grid size) is sent to the F2A. This should allow the knob to control the pad.
Finally, the boolean variable "interact" from the knob is sent into the pad. This is used to determine what the output value of the pad is. If the knob is being used, the knobs output also becomes the pad output (you can see this more clearly in the schematic). I'm not even sure if this is required - it may even be causing part of the issue? My thought process what that if moving the knob did not actively change the pad output value (which in turn is going back into the knob), the knob would snap back to the value whenever it wasn't being used.
Apologies for the long-winded post. I'd appreciate any suggestions, as I'm pretty stuck with this.
Attached is a control scheme I've been working on. I'm having some issues with it and was wondering if anyone had any suggestions?
It's part of a VST in which 2 methods are provided to control some parameter - an xy pad and a knob.
This means that, in order to work realistically, the two control methods also need to control one another.
So far, the knob can be controlled using the pad and it's working very well. However, I'm struggling with the knob controlling the pad. I am able to move the xy pad cursor using the knob, but when I stop dragging, the knob snaps back to its initial position. I've been at this for a few hours now, but still no luck. Does anyone have any suggestions? I'll explain what I've done so far:
The method I've used might not be the most efficient way. The pad outputs a value of 0 - 1. This output enters the knob control module and into a select primitive. The select is controlled by the "interact" boolean on the DragY primitive. If the knob is not being dragged, the output from the module is the pads value, else it is the knobs value, hence the pad can control the knob.
Inside the pad, there are other selects. One is controlled by the boolean variable of the DrgXY primitive. It determines what value is sent to the F2A primitive. If the pad is being used, the pad's own X value is sent to the F2A. If it is not being used, the knobs output value (scaled to match the pads grid size) is sent to the F2A. This should allow the knob to control the pad.
Finally, the boolean variable "interact" from the knob is sent into the pad. This is used to determine what the output value of the pad is. If the knob is being used, the knobs output also becomes the pad output (you can see this more clearly in the schematic). I'm not even sure if this is required - it may even be causing part of the issue? My thought process what that if moving the knob did not actively change the pad output value (which in turn is going back into the knob), the knob would snap back to the value whenever it wasn't being used.
Apologies for the long-winded post. I'd appreciate any suggestions, as I'm pretty stuck with this.
Re: Simultaneous control of knob/xy pad
That's fantastic Tronic - Much better than what I was attempting to do.
It certainly seems using Flowstone's animated knob instead of Synthmaker's might have helped.
It certainly seems using Flowstone's animated knob instead of Synthmaker's might have helped.