fully clockwise (1.0) should be stepped, counter clockwise (0.0) is continuous.
however, on MM its the opposite 1.0 is continuous, 0.0 = stepped.
easy to test,
use X1 as v/oct , and you’ll hear its gliding when 1.0 - it should not be.
note: works correctly in vcv desktop.
Huh, that’s very strange. StepCV is also backwards.
The weird thing is that part of the code is not changed at all from the VCV Rack plugin.
Ah, I see. It’s actually the same as on VCV. Click the X Mode button on VCV until the light above it turns red. That makes the Steps knob and CV act “backwards”.
I think the only difference is that the MetaModule version starts off with the switch at red, but the VCV version starts it off with it green.
1 Like
ah, could be… I never use on anything other than green, in vcv or hardware
@danngreen this appears to be a more general problem w/ modules not using the defaults they should do (i.e. what you will get in vcv)
I do not know if this is specific to each module or if its the meta module, generally, not using the modules defaults.
this is turning into quite a big problem for me when patching directly on the MM, as often the ‘defaults’ being used are not sensible…
e.g. in a recent patch, I found the rebel tech sequencer, was defaulting switches incorrectly… and I was stumped for 10 minutes, because my patch was doing nothing at all…
I was then even more confused, when I re-created on vcv and it worked fine first time.
so the issue here is, when patching on the module.
you really have to go and check every parameter of the module before you can use it…
again, not sure if its an issue with particular modules/parameters or a meta module issue…
that said, Im a bit confused…
as I know when writing my own vcv modules, I use configParam and explicitly set a default - which I expect to be used. so Id assume other modules do similarly!?
Hmm… Ok I’ll look at the RebelTech sequencer.
For the Marbles, we re-did portions of that (notice the buttons have become 3-position toggle switches), so all that happened in our version we had set a different default value.
In general, though, the VCV-ported plugin modules are constructed the same way they are, so if they call “configParam” and specify a default, then that gets called on MM and gets used. I’ll have to look at the RebelTech code to see what’s going on.
1 Like
cool… thanks
so generally, if defaults are not as ‘expected’, we report as a module specific issue.
no worries, Ive just been unlucky then
rebel tech was Stoicheia (sp?) - mode a / b - in vcv it defaults to trigger, on MM to mute (iirc)
As refered to the original manual of marbles.
Thanks! That clarifies things.