dear fellow T3 owners
i sent a message to tech support yesterday telling them of the votes accumulating on the petition, and they have responded with some great news : )
in response to our requests, they are scheduling a firmware revision next week, and this should result in an update being with us as soon as beta testing is done. i'm not sure of the extent of that update, but we should at least be free of bugs in the near future.
they are aware of the call for an editor (i hope none of us have incurred back problems in the meantime ; ) and they are considering how to move that forward as well.
they have asked for our understanding in view of their intensive development schedule and relatively small team. as far as i'm concerned, once my T3 is reliably useable, all will be forgiven. the editor is more important for us than they possibly realise, and there is reason to believe that the wait for it won't be anything near the delay we've had to date.
watch this space.
thumbs up for the moog guys, and for your good selves for adding your voices to the petition...
rumble on!
adam : )
Here it is, guys!
Here is a long-awaited firmware update for the T3.
I still need folks to test this; it definitely fixes the random freezes/lockups that could occur, and prevents stuck notes from happening if you are holding a pedal down while transposing the pedalboard. I re-tooled the Note Stack to try to prevent stuck MIDI notes, but I'll need folks who were experiencing stuck MIDI notes to test this and tell me if the problem is resolved.
Mac users go for this file:
http://seamslikereality.com/moog/TaurusFWUpdate_v1_14_MAC.zip
Windows users grab this one:
http://seamslikereality.com/moog/TaurusFWUpdate_v1_14_WIN.zip
Full instructions are included in the zip file.
Please report back and let me know how it works for you!
Thanks,
Amos
T3 Firmware Update
This is great news, many thanks Amos & Co.
still sticking...
hi amos
many thanks for the update here and in firmware!
the firmware update was accepted fine - i'm showing vers: 1.14. i'm still getting stuck notes however. if i use the T3 for midi input into logic, triggering a mono softsynth, i can reliably get a hung/stuck note by hitting the octave transpose button (both up and down) while keeping a note depressed. the only way of killing the stuck note is at the sequencer end.
normally this wouldn't be a problem if the pedals are being operated with one foot only, but if the patch uses hold on the note (sustained drone), then transposing will leave the external source hanging and the filter envelope will not be retriggered when subsequent notes are played.
UPDATE
i was just about to save this message, then wondered whether my mother midi keyboard causes the same thing to happen. guess what - it does. i hold a note down while transposing the whole keyboard, and the note sticks again, even if i return the transposition to the same value and press the note again. on my controller keyboard, it's never been an issue, since it has 88 keys, and i never need to transpose the keyboard while performing. the T3 is a different matter, so needs to respond differently.
____________________________________________
here are the notes from firmware update 1.11 :
"Feature Enhancements:
The OCTAVE footswitch now works precisely the same as on the Taurus 1:
If a note is held down while you toggle the OCTAVE footswitch, the octave of the note jumps immediately.
If the note has been released but is still sounding (long decay), you can press the Octave footswitch and the decaying note will not change, but the next played note will sound at the new Octave setting.
A similar behavior has now been implemented for Preset Change in v1.11. If no notes are being held down but a long decaying note is still sounding, you can change to a new preset and it will not affect the sound of the decaying note. The sound will change to the new preset on the next played note. If you are actively holding down a note while changing presets, you'll hear the sound change immediately."
___________________________________________
is there an operational conflict between desired transpose/preset change behaviour with the T3 in standalone mode, and note trigger/release behaviour when using the T3 as a midi controller?
if so, is it possible to either have the internal and external triggering treated differently, or to have a menu option to alter the trigger/retrigger behaviour of the midi output independently of the internal soundsource?
best
adam