Taurus 3 firmware update - v2.0.3

Hey Amos, you have just popped into the forum to post a couple of replies about Minitaur. How about some news about updates for the Taurus 3?

Hi Amos,

As there is a major update on Minitaur (brilliant !!), are there some of the new features which could be transposed to our beloved T3 ?

Thanks !

Isn’t the editor usable for the t3 yet?
When using midi to steer the voyager , the voyager sometimes has hanging notes after stopping the sequencer from the t3
? Known bug ?

by Amos » Thu Apr 04, 2013 7:51 pm

Hi Pete, I did not remember to look at the arpeggiator this go-round… but our friend Alfredo BiCho has reported a symptom as well, so I’ll have another go at it. Look for a fix for arpeg transpose in v2.1, coming soon… (next week or so?)



by Amos » Sat Apr 05, 2014 6:04 am

thanks for the report; I will fix this as soon as possible.
There is an outstanding note latch bug on my list as well.



by Amos » Thu Sep 25, 2014 4:16 pm

OK, check this action out.

No editor yet (sorry!) but I do have a firmware update v2.0.4 for you to try.

In this version:

  • arp midi output includes transpose value
  • midi cc input/output values scaled correctly
  • Note Latch should no longer get stuck
  • MIDI Echo/Merge preserves original MIDI channel

mac files:
http://www.moogconnect.net/downloads/ta > … 14-Mac.zip

windows files:
http://www.moogconnect.net/downloads/ta > … 14-Win.zip

I have been away from Taurus 3 firmware for a while, so I might have accidentally broken things with these new changes due to my unfamiliarity with the code. I hope not, of course! > :slight_smile: > But I do recommend testing this version thoroughly before any mission-critical applications.

Let me know how it works for you.



by Amos » Fri Oct 03, 2014 9:47 pm

^^ I’m not sure Pete; although I didn’t test the arp MIDI output very much before putting out this build… I can confirm that I am getting transposed arp notes (if I have the arp latched and then transpose the foot pedals) but I am also getting the occasional stuck MIDI note when I do a transpose while the arp is running, so I have a little more work to do there. Not sure how many people are using this feature. > :slight_smile: > I will get it dialed in though.



by Amos » Wed Feb 01, 2017 4:08 pm

I wouldn’t say it’s the last-ever Taurus 3 Firmware. There’s a Taurus 3 under my desk right now, just waiting for a chance for further update work… however, it’s been waiting there a year or more as my time is in such short supply.

As the company continues to grow, we will have opportunities for sustaining engineering work that we haven’t had while we were in “small start-up” mode… which is a mode we’ve been in for about a decade… > :slight_smile: > but it’s working and we are getting there. I predict there will be eventual follow-up on this product but I can’t assign it to any timetable.

Kind regards,

Amos

I would not hold your breath over any further updates going by the above list of promises. Amazing lack of interest for such a pricey product. My two cheap Minitaur’s get much more love and support from Moog. :slight_smile:

That IS an exhaustive summary of the situation :laughing:

As in many companies, people are just on too many topics at the same time, trying to focus on commercial priorities and new products development. I can understand this.

However, I would love to have Amos asking his boss “I need 2 days development for the loyal T3 users so they can benefit a little of the Minitaur features, so they can still be happy and buy some new upcoming expensive piece of Moog gear”. And when his boss says “this is a 5-years old topic, we have other priorities”, he can answer “I know, they have been waiting THAT long, so they simply deserve it. Right ?”
(and I am not talking about spending weeks to find out why my very T3 still freezes notes sometimes…)

Agree
+1

And the T3 customers are some of the most loyal and dedicated (and it’s not like they’re asking that the old T3 microsite be updated).

How did this end?

Reorganized my home studio and am getting good use out of my T3. Believe it or not, I have 1.13 installed.

Considering the thread/soap opera above, what is the most stable release to jump up to.

I do not envision needing to SEND midi arp or transposing incoming midi sequencing but do want the built-in ARP to be stable. I also want the incoming and outgoing midi-clock to be dead on.

It’s been soooo many years, I wonder who is even still around to answer but am hopeful!

Thank you very much.

It’s amazing that for the price of these, they have just completely forgotten about all the people that bought them. I have to say, I feel a little let down by all the empty promises.
I have the T3, two Minitaur’s and a Sub37. I doubt I would buy another Moog product though. Through owning these 3 models, it’s been a common sight seeing the same promises being posted into the respective products sub forums. Same excuses, different forum, same result. New product comes out, all the rest are pretty much left as they were with only promises that things will be fixed.
Not a great business practice really.

The brand had the same behavior for discontinued products: they simply dropped them without further support. I absolutely love my Taurus 3 set, but I was hoping in a definitive firmware and a Mac editor…

The editor is what really baffles me : you have made and upgraded an editor for the minitaur, so how much work would it be to adapt that one for the t3 ???
(Not nice)

Moog Music is hardly the first.

Unlike the Minitaur, the T3 does not have features “under the hood” that can only be accessed by an editor. And the front panel IS the editor.

true,
but it’s very unhandy to program a sound when i have to bend over all the time, as the t3 lays on the floor, under my other keyboards…
everything is connected by midi ,and steered / editable by midi/ cubase, so it’s unhandy to have one that for some strange reason doesn’t allow distant control
( i know the voyager can be used to control, but that is chaotic and interferes with normal use of the voyager).
the solution would be very simple: small adaptation of the minitaur editor so that it can recognize the t3 . don’t think many people will be bothered by some functions that don’t work on the t3, they will be glad to be able to control the t3 straight away without having to crawl on the floor as only alternative.

this besides a long awaited firmware update to unbug this magnificent machine completely…
it’s good if the firm ( moog) would finish/ complete the thing , good for the name of moog, and creating even more good feelings in the group of hardtime moog users ( and sponsors of the whole t3/ minitaur en further derivates of this model)

another one ( therafter) could be a small editor for the mp201 pedal

thanks beforehand for all the work to be done , a constructive thinking long term moog fan

My T3 is at waist level not on the floor. I don’t play it with my feet - that’s what MIDI is for.

I agree that tweaking the T3 on the floor is not always convenient. For lack of an editor, I found other solutions.

To me, an editor for the MP201 is more important.

For sound design, I put my Taurus 3 on the couch table.

But indeed, they first treaded us Taurus 3 buyers as premium customers, but now Moog forgot about us :frowning:

If only they would publish the sysex documentation.
This would enable someone to write an editor with patch handling.

I am not asking to get it for free.
I would pay for a working editor.

I’m an organ player from "origin ", so 2 manuals andromeda-a6 and voyager ( with midi connected hammond module) and t3 for the footwork :slight_smile:

Regarding the fact that the t3 reacts to knob movements of the voyagers makes me think the editing is done by msb- lsb controller data , not sysex
Problem is hardly any daw supports making your own editor with these
Therefore taking the minitaureditor as startingpoint and simply changing the number of msb/lsb , would probably be sufficient …

Right, edits are done via MIDI CC.

But there is no way to store or load the presets settings into an editor without sysex.

Oke, understood
Regarding the fact that they probably don’t use checksum ( like roland) that won’t be such a big deal either : change the id, parameters probably will be mostly the same
Anybody knows if the presets of the t3 and minitaur are mostly the same / interchangable ?
I don’t think it’s rocketscience, just a question of some attention and a little time
Especially for footwork equipment an editor is a must !
After all , we all come on age, and creeping on the floor isn’t getting easier :slight_smile:

Good to see some new posts in the T3 forum :slight_smile:
Hopefully someone from Moog might join in.

Just quoting myself… I still think this is a valid scenario ! :mrgreen: