The forum won’t let me post this in the related thread, since the last two posts were from me. Possibly this is a question more general than to that specific plug-in.
I tried to instal this plug-in on my Mod Duo X. The location listed in the instructions were for a dwarf, so I assume the destination is “root@modduox.local:/root/.lv2/”
But I got an illegal operation error.
Is there a specific way the hardware must be mounted? Should the web-gui be connected or disconnected?
I figured this out - the instal instructions listed the scp command with a -O, I removed that and the plug-in was installed. Unfortunately the “dry through” feature I was testing, did not work.
Actually I should revise my statement that the dry through does not work. It isn’t a dry/wet type option - it seems to allow for the dry signal to pass through when not stuttering (I believe the original behaviour), or to have silence when not stuttering. This option is really useful, and I totally appreciate it since it’s an interesting option. But it isn’t a dry/wet type thing where the entire dry signal will pass through along with the (wet) stuttering.
this plugin is available in beta, so why not install from there?
EDIT: I am wrong! Dave has been working a lot on doing plugins, I thought this one was included in the pack but it is not, is it a new one?
@DaveM next time try to use the online builder at MOD Cloud Builder which takes a buildroot mk file just like in mod-plugin-builder. and the resulting page for shareable builds allows anyone to install with 1 click, making this whole procedure much easier for users.
The plug-in is in beta - but I had recommended a mix or dry passthrough option and Dave was awesome enough to take that advice and add the feature. This is a newer build with my feature request!
It took me weeks to have an empty saturday to test this, so that’s on me.
It’s in beta indeed. Once I have some updates ready I’ll make a new pull request with this plugin included too.
I tried to use the cloud builder. But unfortunately I got an error. I didn’t have the time to investigate yet. I’ll send the error message your way once I get to my device.
@S_Righteous I will update the readme. My bad, the -O flag is only needed on some macOS machines
@falkTX I’ve looked into the build error I got: lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?. Could you update Cargo (rustup update) on the cloud perhaps?
Hi Dave - I think this new feature provides the best options, but it may confuse some users, as it is unlike a traditional dry/wet balance type option. The unaffected dry signal is not passed through the plug-in in no matter which way this setting is set. But that is fine since you can always patch the dry signal to go around the plug-in.
What it does do, is allow you to have glitches with dead space between them (which sounds better to me) when the dry is off. When the dry is on, those dead air spaces between glitches have the original signal.
Thanks for adding this, it has better flexibility now, and I will be testing it out more this week. I was using my Mod Duo X in a performance last week, and your plug-in sounded awesome live! Thanks again for your hard work.
I need to add some support for mac builds on my side. I’m getting that ready.
And after that the Mod team still need to add dedicated build scripts for the desktop app.
No, you can build for Linux x86_64 with bootstrapping ./bootstrap.sh generic-x86_64
After finishing the bootstrapping, you can build each plugins with ./build generic-x86_64 PLUGINNAME under the mod-plugin-builder folder.
But mod-plugin-builder can’t build for Windows and Mac plugins.
To build a plugin, run: ./build <platform> <plugin-package>
Where platform is either modduo, modduox, moddwarf or x86_64 and plugin-package is a folder inside the plugins/package directory.
from github README
However, the rust build environment is needed for DaveM’s plugins.