For some reason, the Control to CV plug-in no longer works on my Mod Duo X. If I make a simple pedalboard with just that plug-in, I can use the CV monitor to see that the output of the plug-in is erratic. Also, if I assign the output of the Control to CV plug-in to any parameter of any other plug-in, it simply does not control that parameter.
I also loaded up older pedalboards which use the Control to CV plug-in, these were not edited in any way, yet now they no longer work.
My system says it is entirely up to date, and all my plug-ins are up to date.
hey @S_Righteous I did a quick test and couldnāt replicate your issue. I tried it on the MOD Duo X with MOD OS and the plugin running the latest versions.
Do you have some more info? Can you share a little screen recording demonstrating the behavior?
Hello @S_Righteous sorry for the late reply. I see that you already managed.
What you are showing was definitely not my experience when I tried to replicate it.
The behavior that shows on the screen (or the lack of it) is also replicated on the sound?
What Iām trying to discover here if itās something not updating in your browser because of some cache issue.
Yup, it sounds how it looks. When you can see that the Gain plug-in is unaffected by CV, so is the actual audio signal. You can also see that the signal into the CV monitor is erratic - it used to reliably show a real time indication of the CV signal, now it looks severely late, or just wrong.
When all this happened, I was working on a complex pedalboard which used a lot of CV signals. I half wonder if something in that pedalboard caused something to break, which needs to be reset. I can send a version of that pedalboard to you.
In my dashboard, it does list an update for the Mod Pedal, which I donāt own, so I havenāt applied that update. Actually I think I canāt apply that without having the pedal.
The version of Chrome I was using was: Version 111.0.5563.146 (Official Build) (x86_64) although today it literally just updated to Version 112.0.5615.49 (Official Build) (x86_64) So I retested to see if the update was causing an issue, but the Mod issue is still the same on the updated Chrome.
i just updated my Duo X to 1.13.1.3123 and updated all my plugins. i recreated your board and added the Invada Test Tones signal generator in front of the Stereo Gain plugin - so i can hear whatās going on. hereās what iām seeing and hearingā¦
the GUI knob on āControl to CVā does respond immediately to turning the Duo X knob. the audio output confirms that āControl to CVā is actually changing smoothly, corresponding to the Duo X knob, and is controlling the āStereo Gainā level in the same way. so, in terms of control and audio function, everything is working.
however, in the browser GUI neither the āCV Meterā nor the āStereo Gainā update properly. specifically, they donāt update at all as long as the Duo X knob is in motion, and when motion stops they take about 1 second to update to whatever is the final value of the knob after it finishes moving.
@S_Righteous and @jon can you check carefully whether this might be the same as whatās happening for you?
@mj_prod perhaps you could check as well? for me, the discrepancy between actual function and what shows on the GUI is happening in both knob modes.
@S_Righteous if we all confirm this behaviour, perhaps you could write it up as a Bug Report?
I just rechecked with a simple set up, and it seems that the audio IS being affected by CV, but that the GUI is not updating at all, in either the CV monitor, or the destination plug-in. However I initially noticed this issue with a more complex pedalboard where the audio was not updating, I āheardā the issue before I could zoom in to see it in the GUI. I will go back to that to see (hear. . ) if this is still the case.
I also tested with the most recent version of Firefox, and the behaviour of the GUI is the same. This also was the case with Safari, but I donāt have the most up to date version, and mine crashes, which is why I always use Chrome.
Plutek - since you are experiencing the same issues as I am, would you be kind enough to test out a pedalboard for me and see if you have the same CV overload issues I have also experienced? Iām not sure how to privately share a pedalboard though.
I was working on a complex CV set up which had issues, when I found the separate issue with the Control to CV plug-in. So I focussed on that in this thread. I wonder if both issues are related.
I believe there is a checkbox on the pedal sharing board that allows you to hide the board from the main feed on upload, but provides a link to the board you can privately share.
excellentā¦ throw me that link, and iāll be happy to test it out! iāll just say that weāve got family visiting with us now and through the easter weekend, so i may not get to it until tuesday.
Itās all good - I really appreciate you looking into this.
So there is a looper, you can throw in anything, radio, vocals etc. Then a sequencer sends CV on and off signals to two mixers so that the looper gets chopped up into 8 parts. My final goal is that an octapad will trigger those.
There is a pitch shifter added. You can just listen and hear that the loop has each 8th note muted/unmuted. If you adjust the pitch shifter rapidly, like from 0 to -12, then the sequencer will overload, and then you hear that the CV did not mute the loop where it should have, but a few of those parts stay open - the sequencer visually stalls as well. The sound of this may not be obvious depending on what you chose to loop.
The pitch shifter is just an example to send a signal which overloads the CV. I was using some other processors and noticed that the CV would get interrupted as well.
