And a well-written manual it is! I only wish they had included a list of the factory preset names & locations - it would save users time scrolling through banks to find their favorite presets, at least until we memorize them. Thanks Moog, now I have something to keep my mind busy for the next few days until my Taurus arrive!
Did a Brit slip in halfway through the manual write? “Analogue” appears a couple of times. Not that i’m complaining, that’s the real way of spelling it of course .
I love the footnote on the last page (and there’s truth to it!)
CAUTION: Be careful.. Speaker damage, structural damage to buildings, or personal injury are
all possible using the Taurus 3 Bass Synthesizer at high volumes. With some amplification
systems, Taurus 3 sounds may cause loose objects to rattle, move across the floor or fall down.
Moog Music Inc. is not responsible for any consequential damage or injury associated with using
the Taurus 3 Bass Synthesizer.
The reason that the factory presets aren’t listed in the manual is that they were still being compiled when the deadline arrived to send the manual off to the printers. The original plan was to include the factory presets on the last page, but time limits dictated otherwise.
The control range is 12-bit (0-4095), which is like the Voyager, but all bits are displayed.
While the pass-thru and snap modes make sense for finite controllers like the footwheels, the endless encoder will always be in track mode. I might be wrong on this one.
The pitch CV accepts 0-5V at 1 V/oct., so there’s an expo converter on this input (the oscillators being exponentially scaled).
MIDI note range is limited to 0-60, to prevent excessive voltage damaging the oscillator circuitry.
The wheel lights can flash in time with the LFO!
Polyphonic playing with another Moog is possible (p40)
Although the pedals transmit velocity (which can be conveniently quantized), there is no way to utilise this controller on the pedals themselves
I didn’t actually get billed for the pedals until late January last year, so I’m probably going to be down the queue a little bit (despite ordering the day they came out!). But I look forward to you guys having a good play/demo and moreso to getting a hold of my own set!
Greg, you are welcome. I think a lot of folks take user manuals for granted. A well-written one, like the Taurus & Phatty manuals that you wrote, add to the enjoyment and usability of an instrument, while a poorly -written manual can lead to cursing & pulling your hair out. Good job, & thank you Greg, your efforts and hard work are much appreciated.
Just thought of it for new code (2.3?) . Listening Amos? I know you have plenty of time for countless user requests.
Here’s one:
Have a ‘split’ mode in the Phatty that allows a split such that keys from ‘middle C’ on the Phatty on down get sent out Midi to Taurus and the other keys (C# up) play internal OSCs.
Regardless of what Octave the Phatty is in, the lower key register should map to an assigned Taurs octave. (or something like that)
That would be killer. Sure it can be done with Mapping software in my Mac, but I’d love to have this be a straight wire solution.