Moog Taurus II controller CV doesn't seem to be working?

[brother firefingers]

Ok, I connected the CV out of my Taurus II controller to the ring position (CV in) on my Rogue, but the controller would not activate the Rogue.

That being said, I did notice an odd occurance; when connected as above, depressing a key on the Rogue resulted in the correct note, but with an aftertone that was different than the note struck. I found that by turning the Range knob on the Taurus II controller, this after note could be made higher or lower than the keyboard. So, there is something going on, but not what should be going on.

I was using standard mono 1/4" plugs. Am I doing something wrong, or do you think there is a problem with either the Rogue (works fine in all other respects) or the Taurus II (which I have never tried to use until I got the Rogue, as I purchased it as a seperate controller, not part of a Taurus II bass pedal set)?

All help appreciated.

[MC]

You need to connect a trigger. Use V-trig output of the pedals.

[brother firefingers]

Ok, I connected the V-trig out to the trigger in on the Rogue; the Taurus will trigger a note now, but only the last note played on the Rogue. Do I need to connect CV and V-trigger simultaneously?

[brother firefingers]

Ok, a further report... connecting the CV out of the Taurus II controller to the keyboard in of the Rogue, and further connecting the V-trigger out of the Taurus II to the V-trigger in of the Rogue allows the foot controller to control the synth!

Success!

THAT having been said, with the above-mentioned connections, if I use the keyboard section of the Rogue, I get the afternote of the last note depressed on the Taurus II... any way to get around this so that I can choose to use either on stage?

Finally, I don't know what S-trigger is but I suspect the S stands for "sequence", since depressing any note on the controller with the S-trig connected just starts the Rogue going in whatever setting you have. It doesn't seem to integrate into the system as I have described it.

[ebg31]

Finally, I don't know what S-trigger is but I suspect the S stands for "sequence", since depressing any note on the controller with the S-trig connected just starts the Rogue going in whatever setting you have. It doesn't seem to integrate into the system as I have described it.

"S-Trigger" means Shortening Trigger. It's a techuique first implamented in the custom modular systems. It's relating to power distribution among the modules, and it caused some hassles for Will Alexander and Gene Stopp when they were repairing Keith Emerson's Moog.

I guess, the R&D section of Moog continued to use those trigs well into the 70's.

[Kevin Lightner]

Sorry to correct you, but S-trig means "Switch Trigger."
Same thing as a switch closure to ground.
Some people call it a shorting trigger, which is ok too.
However, shortening is what you bake with

Switch trigs are a drag because they're not a standard connector or signal in today's music world. Very common for me to be asked to convert S-trigs to V-trigs (voltage triggers) because S-trigs are extremely difficult to mult and interface with.

Fwiw, Emerson's Moog still uses switch triggers I think, though I could be wrong.
Zimmer's and Norlanders Moogs are far larger and all of the envs were converted to V-trigs.
Many larger Moog modulars and Minimoogs have had this mod done.
Pretty common to see.

[brother firefingers]

Thanks to both of you for the information.

In regards to the keyboard on The Rogue having an after-tone equivalent to the last note played on the Taurus II controller (when connected), is there a way to correct this, or is it simply an audible electronic artifact that results from the design and configuration?

[MC]

That's normal operation for the Taurus II to override the Rogue keyboard.

It can be corrected with circuit modifications. I don't know if this has ever been done with a Rogue, but it has been done with the model D minimoog.