Taurus 3 firmware update v1.2 - now with new features!

Hi there!

So after I installed 1.2, recording and playback of MIDI data in Logic abruptly came to a screeching halt. MIDI messages were being sent with the proper rhythm and with velocity differences, but they were all for the same note (CO? can’t remember) and when I went to play back, nada. Went back to 1.13 and everything’s working again. Did I miss something perhaps? Wouldn’t be the first time! For details and the solution I found (almost perfect!) to the saga of me, Logic, and the T3, check out my other posts. And thanks for being you, Moog people.

If you read page 1 of this thread you’ll see seveal references to the arp being broken in v1.2. Amos has yet to post the fix for it. I suppose he’s been a bit busy with NAMM.

yes, the new products need attention too.
good one this year , has to be said.

hi all, I am working a lot on Minitaur right now, but I’ve had some time for Taurus too. Once I got back into that code, there was more to be done than I had anticipated. That’s why some things broke in the 1.2 beta… although I’d have caught more of those things if I’d had more time for testing right before NAMM…

Update is, I’m working hard to get Minitaur ready for beta testing this week. That effort will continue over the next couple of weeks, but I should start to have time to get back to Taurus during this span as well. I’ll try to get the Taurus update complete and bug-free this month, if possible. No more new features for now; I need to focus on testing and stability only from this point.

All the best,

Amos

I know how you feel, Amos.

My day job is to support production systems around the world such as South Africa or Germany. My software gets installed remotely, we don’t always have the option to do it onsite. Under that condition we don’t HAVE the luxury of beta testing - my software has to work from the get go. I do as much offline testing as I possibly can, because they can’t afford to miss shipments. A wee bit more pressure than a NAMM show… :open_mouth:

Now I see how Dave Luce felt while developing the Polymoog…I really feel for you engineers what with deadlines and bugs and all. :open_mouth:

keep the good work going, as long as there is progression, none of us will complain.
thanks !

Hi Amos,

Thanks for the MIDI transpose feature, that has made things so much easier for me.

Regards,


Graham.

I have a great idea for the T3.

Can the key gate time modulate the VCA release time? So when I play staccoto notes the VCA release is short, and the release gets longer as I hold the key down longer.

This would be a handy feature to those of us who play with their feet and saves having to toggle the DECAY footswitch.

Or maybe a time threshold that toggles the decay footswitch. If a key gate is under the threshold, decay is OFF for short release. If key gate exceeds the threshold decay is ON.

how is the state of the update ?
or is time consumed completely by completing the minitaurusthing ?
still lot’s of good mooglovingpeople hoping and waiting for The upgrade.
amos , please…


fr.gr. sunny

Hello! Minitaur is OK since last week. This week I resume work on Taurus. Thanks!

-Amos

Thank the lord. I was worried our ‘old’ Taurus was going to get forgotten.

OK as well as the fixes (particularly the broken arp), something on the Minitaur struck me. It has keyboard tracking, but only available via MIDI. And I seem to remember you hadn’t decided whether to make it 100% or 200% (seems you’ve settled on 200% judging by the manual).

This suggests to me that the keyboard tracking on the Minitaur is software driven, so any chance it could added to the Taurus 3 firmware too?

50/100/200 % ?

Taurus 3 gets its filter tracking via a fixed resistor from the pitch-CV, just like the Taurus 1.
I might be able to add more pitch-CV to filter in software, but I can’t take it to zero.

Could you negate the pitch CV and sum it to get zero tracking?

Unless there was some kind of “null calibration” to dial in just the amount of negation required for each unit, then it would be impossible to guarantee zero tracking this way, due to small variations in the analog circuitry from unit to unit. So, not impossible, but it quickly becomes pretty involved…

Zero keyboard tracking wouldn’t be a terrible loss. The Taurus I was 50% tracking, as should be the Taurus 3. I would be happy if it could track 50/67/100, “67” mimicing the original model D 2/3 behavior.

At the moment, it is very difficult to tap the tempo for a 16th arppegio or lfo speed with the foot in a live situation.
Would it be possible to modify the tap-tempo function in a future update to tap in the desired BPM directly?
This would be a great help for me.

I may have discovered something odd. Not sure if it’s a bug yet, but I can’t figure out what’s going on. I haven’t used MIDI in a while (been using the pedals), but decided to play some stuff from a keyboard.

The problem is if a play an F I’m actually hearing the C below that. I have no transpose on the Taurus 3 and none on th MIDI channel in Cubase. I cannot for the life of me find any transpose setting that could be doing this.

Is there another place I could be transposing it without realising? If not can anyone confirm if this happens on their T3?