minitaur bug

[jeepo]

I thought that the minitaur was supposed to ingore midi notes higher than one octave above middle c. In reality it responds to higher midi notes, but only plays the highest note of it's range. This is annoying and should be changed such that notes which are too high are either completely ignored, or the oscs are muted so that the filter can be played. The current droney c is an annoyance, not a feature.

[EMwhite]

I wouldn't call it a bug.

But I would say that you have a good idea for a new feature !! : )

Actually I requested (somewhere) that they implement a mode which detaches either or both of the OSCs from the keyboard and allowed it to drone on a preset note. Your request could be part of the same feature; a limit CC which sets the highest note that will sound; accompanied by another new setting (obviously) the lowest note that can sound.

[jeepo]

I called it a bug because in the manual it says "note values of 73 and higher are ignored"

[jeepo]

Another way to handle midi notes which are out of range would be to transpose them down a couple octaves (or even better, for each octave out of range, drop it another octave, such that each succsesive octave is one lower than the last). I think this would be a cool solution, as it avoids notes dropping out, as well as pedal points, while adding more bass.

The adjustable drone point is a cool idea too, but I'm not sure whether the drone point is even programmable, or simply a result of cv clipping within the circuit.

[EricK]

I believe the Taurus III does this as well if Im not mistaken.