Hi, i thought i’ll start a new topic where we can reunite all the ideas for the new OS while Amos is working on the new fooger. This way we can gather the information and get things moving. I think it’s time to report all the bugs you ever found too.
In a previous tread i post some of my ideas, here they are again just to start this, every idea is welcome!!
Midi filter per preset so you can choose what midi information the T3 is sending. Particulary i’ll like to filter master volume, control wheel, arp notes with options for every arpeggiated note, base notes, and only the played (pressed) notes, some CC’s, etc.
Transpose midi notes per preset, and include the option of no midi notes so the T3 doesn’t send any midi notes in that preset.
Add velocity fixed values, so you can choose per preset the velocity of the note independent of the way you press the pedals.
Fix all the bugs found on the latest OS (stuck midi notes and arp notes)
Some or all of the features added to the LP in the new OS (retriggered LFO, new clock divisions, midi clock out, star / stop messages, etc.)
Transpose incoming MIDI note values by octave function, so when controlling the T3 with a Voyager or other MIDI controller one can play doubled lines an octave or two apart.
If the incoming MIDI note transpose function worked in half-step increments that could be handy too.
Hmm, most of what I’d want has been covered so I’ll simply echo the few I most desire:
Fix the old OS bugs (MIDI-note sticking – regardless of Arp in-use or not. Even worse, note-sticking when MIDI is not even in use.)
^ THIS IS A HUGE DEAL ^
Add KB LFO triggering (as seen in Slim Phatty’s new OS)
Changeable MIDI CC output (as seen in Slim Phatty’s new OS)
Full ADSRs
Before I saw Amos’ presence in this forum, I was actually considering letting my Taurus 3 go and buying two Slim Phattys to replace it. Now that there is a glimpse of hope though, I don’t think I can let such potential slip through my fingers.
Please don’t forget about us Taurus 3 owners, Amos. We love you and have seriously missed you.
You’re probably right, i was thinking the same thing, but i think at this level we should let the ideas come. Eventualy Amos will tell us if that thing can or cannot be done.
I specially like c7sus’s idea of adding incoming notes transpose… nice one!! (if it’s possible)
I had this idea a while back and another poster had the same idea. It could be described as wrap-around split or wrap-around transpose. The idea is that if you had a piece that required say a low E, well obviously you only have a low C on the footpedal. Rather than transpose the whole pedal board so that the C is now an E (confusing at the best of times, more so after a few JDs), I have a different solution.
So my idea is this: have a split function like on many keyboards, except not for sounds (as there’s only one engine) but for pitch. E.g. Pick your split point as E. The E pedal now becomes your lowest pitched note, the low C to D pedals then become the upper range that you’ve shifted along.
So pitch wise from lowest (physical) pedal to highest you would have say C1, C#1, D1, D#1, E0, F0, F#0 through to B0, then C1 again.
It sounds more complicated than it is and of course you get the high C twice, but once implemented I think it would be easier on the brain than transposing.
Perhaps the physical high C note pedal could become the higher octave note (ie. +1oct E in this example) rather than just doubling the high C note.
Did I miss the step sequencer? It was mentioned in a post by Amos a while ago:
"The T3 arpeggiator is shipping with Random mode.
And a 128-note step sequencer.
You can enter a step sequence and then transpose it on the fly using the Transpose function and the bass pedals. It’s really fun.
i don’t know if this idea has any future but i’m going for it anyway:
I really like the T3 to be able to send midi chords for the polyphonic instruments you can control with it… lets say you can program each patch witn the chords for every note: C (major), D (minor), etc. that would be awesome!!! with triads i would be happy, please!!
The wrap-around idea is interesting, but I like the idea of changing octaves by pedal velocity.
If you press the pedals below a preset velocity threshold, you get the lower octave. If you press above the preset velocity you get the higher octave. That way you have two octaves always available.
To get more extreme, you could have three velocity levels to cover all three octaves at once. This would require a lot more control, but would be very interesting to me.
Not sure if this is possible, I just noticed it whilst scrolling through some presets. When you hit a note and release then change patch you don’t get the new sound until you hit a new note: all good and as most want it.
However, if the first patch has LFO and you play a note, release it, then change patch, although the sound doesn’t change, the LFO doesn’t carry on into the decay - it immediately goes to the new patch’s setting, which makes sense but doesn’t allow any spillover if the first patch has a long decay. Any chance of an “LFO Spillover ON/OFF” parameter whereby the rate doesn’t change to the new value until you hit a note?
PS. I really like the veloity idea. Because the Taurus isn’t velocity sensitive I forget that the actual pedals themselves are capable of sending velocity. I like the idea of setting a velocity split point of, say, 64 and then anything above that is one octave, anything below is another. I think just two values is most realistic though.
This may appear to be an odd-ball request, but I think it may prove most useful:
If it is at all possible, perhaps allow for mapping the (9) footswitches on the front panel of the T3 to send MIDI CC and parameter changes. This, of course, in addition to allowing the first bank (A) of presets to be overwritten – allowing for quick recall during live performance with the click of a footswitch.
I would also like to reiterate that I think LFO retriggering should, without question, be a part of the next OS update for the T3. Oh, and triplets too please.
(The above are merely requests – regardless of the oftentimes ‘absolute’ means of speaking.)
Better Duophonics via Midi. (All Moog products should play together like the Slims. This is one of the main reasons I bought the T3)
I want to drone a note on the Voyager while I play a lead on the Taurus. Having to transpose the Voyager’s keyboard down renders the Voyager’s engine unusable.
I would also like to be able to disable all of the Midi control from the Voyager except the keyboard. I want to tweak the params of the Voyager without changing the sound of the Taurus.
You could add a “polyphonics” menu. That menu would reject Midi CC’s and allow others. This would allow just external keyboard or keyboard and modwheel control over the Taurus.
Id also like to see a customized rubber cap that fits in the recess where the input/output/power jacks are to protect from dust.
Hi guys, the initial propouse of this tread was to recolect in one place all the features or improvements that we, T3 users, woul like to see in the new firmware… since there´s no answer from Moog on the topic, i just want to express my dissapointment on the way Moog has deal with the T3 problems… i’m pissed!!!
They aren’t necessarily obligated to reply to every (or even any) wish list or feature request thread someone starts up. You can always contact them directly if you actually expect a response.
I sent an email regarding the MIDI bug. I have given up on future OS features and an editor for now, I just want the MIDI fixed. And Amos already knows about this bug as he replied in an old thread.
