Issue with Turing Machine - solved!

Plugins & Modules
1

I’m suddenly having a strange issue with Turing Machine. I have TM set up with a VCA before the clock input to constrain the notes. But suddenly, TM stopped progressing steps as you lower the VCA. I was previously able to get it to constrain the note values all the way down the VCA level, but it just stopped doing that after a crash.

I’ve reinstalled Rack2, and all my modules. Deleted my user folder. And tried a bunch of module combinations to see if it was a clock or VCA issue. Turing Machine seems to be the offender. I am going to open a support ticket with VCV but was wondering if anyone had seen this kind of behavior before.

EDIT: I had the VCA in the wrong place. After the clock, before the TM. Putting it after the TM before the v/Oct fixed the issue. Being new can be frustrating sometimes.

2

I think this is the correct behaviour, by closing the VCA you lower the pulse VC until there is no more clock pulse. Are you sure this used to work ? Can you load a patch (made by you) that used to work and now does not ?

3

Constraining note values sounds like you had the VCA after the cv output, then it never stops, just lowers possible notes values to whatever Ov is centered on. Check out sickozell randloops sequencers for some cool variations on the theme, with offset and scale on the cv output, here the VCA is built into the module.

4

Yeah, I figured it out. VCA was in the wrong place in the patch.

1 Like