Yay. 3am here so will try in the morning.
OK just tried it and was able to crash the MIDI within five minutes. It seems if you step through the program changes (possibly too quickly for the T3?) it will give you a constant high note. For some reason if you go to an Arp preset you can clear this, changing to a normal preset leaves you with the high note.
ok, interesting. Thanks for the additional clues, that should help.
any other misbehavior you see, please do your best to document exactly what you did to cause, or what you were doing when you encountered, the problem..
thanks!
Well just tried it again. If I’m ‘gentle’ with it all is fine, i.e. play note, let it finish, change program, play next note. But if I am playing a note, switch to another patch midway that’s when I sometimes get the stuck note. Switching to an arp patch fixes it.
Also I notice that if I edit from the X-Station’s front panel (mapped to the T3’s CCs) that if I am holding a note and hit the Octave button (that corresponds to the foot pedal, not the oscillators) then I can consistently get it to freeze on that note (it’s always the note you play that’s frozen, not like original way I described above where I get a high note).
Currently I am going like this:
X-Station>Cubase>Midex3>Taurus 3 MIDI In and use the X-Station’s program change buttons.
Later today or tomorrow I will try X-Station MIDI Out directly into the Taurus 3 to see if that’s any different.
OK I just tried it direct, X-Station MIDI Out into T3 MIDI In and I can reproduce the exact same behaviour, so that is:
-
Hanging notes when scrolling through sounds via MIDI and a note is still playing.
-
Changing the octave (pedal) via MIDI whilst playing a note.
Both result in hanging notes. Both are fixed by going to an Arpeggio patch, but note still hangs if changing to any other patch.
I think the Octave (pedal) may be broken in software as I also notice that via MIDI the Octave button has no effect. I can get it to light up via MIDI, but the octave remains the same pitch. The Glide and Decay work fine. The Octave works fine from the actual pedal switch.
great, this all sounds eminently fixable! should have it sorted next week.
Great to hear, Amos! Am looking forward to the bug fixes! 
so happy someone is interested and putting his good time and attention into the t3.
really looking forward to all that might be fixed, upgraded , implemented and whatsoeverbig or small. thanks amos !
(maybe in future velocity to the internalsounds might be possible??? 
)
It’s taken over 18 months to get to the point the widely-known main MIDI bugs still aren’t fixed?
Frankly, I think Moog support is giving short shrift to the folks that believed in the T3 and bought it and made it happen.
The new products are great but can someone explain the difference between this buggy firmware patch and the crappy updates MSFT is constantly putting out to fix all their security flaws?
Looks the same from here and I’m not gonna hold my breath waiting for an actual fix that works later this week.
I needed, and received thanks to mr Arkadin, more info to fix the bugs.
Try this version if you like:
http://seamslikereality.com/moog/TaurusFWUpdate_v1_14x_20Dec11.zip
cheers,
Amos
thanks, i’m going to try that one.
How about:
- Amos is the only staff member performing embedded development
- Amos is acquiring direct feedback from their customers on bug fixes, with no corporate layers to wade through
- You haven’t seen his work station in person to witness the heavy workload he is under (they JUST finished the Cluster Flux)
- Moog isn’t a big enough company to employ an army of developers
- Moog has not been convicted as a monopolist in anti-trust court
- Moog doesn’t engage in anti-trust tactics like strong-arming their resellers to exclude competitors
- Moog products don’t run on a junk Windows platform that attracts viruses and rootkits which their “security updates” fail to prevent
Please find another nit to pick
It’s far from nitpicking when people have been begging for a fix for 18 months. Lockups from various causes are noted in this forum as early as March of 2010. v1.13 was released in June of 2010. The hanging MIDI note problem was first reported soon after.
It’s nothing personal against Amos.
The facts speak for themselves. Moog dropped the ball on this fix bigtime in favor of other projects and left T3 owners literally on a hanging note FOR 18 MONTHS.
I’ve bought over $7,000 of Moog gear since 2005 so I believe I have paid the price of admission to comment about their customer service, regardless of what you and your little laundry list might think.
I think Moog releases products to the market too quickly.
They really need to chill out, skip a few NAMM shows, and develop something that leaves the gate with no bugs.
I think Amos has been wanting to clone himself for years.
if anybody ever thinks a product is in dire need of firmware help, I invite them to email me directly. Even if I am tied up on another project at the time, I can take the issue to our weekly engineering meetings, we can figure out a priority and schedule time for a fix.
That’s ultimately what happened this time around; I am truly sorry that it took as long as it did to get to that point. I try to be more responsive.
And that’s why I love Moog. Try getting that kind of response from RolanKorgaha. 
Here’s an update with some new features.
http://seamslikereality.com/moog/TaurusFWUpdate_v1.14x2_22Dec11.zip
Added in this version:
new per-preset parameters (found on ADVANCED PRESET menu) -
• Volume Velocity Sensitivity (0-127)
• Filter Velocity Sensitivity (-64 to +63)
• LFO Key Trigger (off, on) – this resets the LFO phase to zero on noteOn regardless of the LFO Sync Source
also, LFO Sync Source is reduced to two options, Internal or MIDI. Older presets will be converted to the new settings automagically.
• per-preset MIDI OUT transpose (XPOS OUT on advanced preset menu; -64 to +64 semitones); there is also a global setting.
new global parameters:
MIDI IN tranpose (-64 to +64 semitones); found on the MIDI SETUP menu.
MIDI OUT transpose (-64 to +64 semitones); MIDI SETUP menu. This is a global setting; if a preset has a nonzero XPOS OUT setting, then the preset’s transposition value will be used for MIDI out instead of the global setting.
I think that’s it for now… tomorrow I’ll add MIDI CC output filtering like on the Phatty series (send all, all - volume, just pedals, none).
Please try this and see what you think. If you need a Windows version of the firmware loader, let me know.
Thanks!
-Amos
Amos,
Can you do Midi IN Filtering? (To keep the Voyager’s filter pot from affecting the Taurus filter but still allow Keyboard and Mod Wheel Control and similar)
Will the Midi In Transposition solve the problem you get when you connect the Voyager’s Keyboard to the Taurus and the lowest Voyager key transmits an undesirable high pitch from the Taurus?
Eric
-
maybe, yeah. will need to work up a spec for it.
-
yes, it should. Although you can already transpose the Voyager MIDI out, I’m pretty sure…