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

[Mr Arkadin]

Just tried it.

Probably related to fixing the LEDS, but now the decay and glide now not only show off on the LEDs but actually are disabled, so in a way the display is now correct, but all the decays and glides have been switched off every preset.

[Amos]

Just tried it.
... but all the decays and glides have been switched off every preset.

This was actually a result of the code I used to "convert" old (pre-v1.2x) preset parameters to the new format.. problem is, as a beta-tester of the previous version you'd already converted your presets automatically... the same routine, run a second time on the same presets, caused those parameters to be switched off. I changed the logic to only run this conversion on genuinely-old presets (prior to any of the recent beta versions). Seems to work OK now.
Fixed the Glide/Decay/Octave LEDs, as well as the Velocity->Filter Cutoff mapping.

Latest greatest files:

Mac-
http://seamslikereality.com/moog/Taurus ... 12_OSX.zip

Windows -
http://seamslikereality.com/moog/Taurus ... 12_WIN.zip

[francesco]

Hi Amos,

after the installation of v1.25 all the presets sounding dull - kind off closed cutoff. I had no luck with factory reset to get the presets sounding right. After two tries, I switched back to v1.13 for rehearsal tomorrow. No time at the moment to try the new features, maybe I find some time at the weekend.
Frank

[Amos]

Hmm, OK. Since I just "fixed" the velocity to filter cutoff, I am guessing this is the cause of the change you noticed. All presets should have zero velocity-to-cutoff modulation by default, though... this is probably not the case. I'll check it. Thanks!

I was out of town at a festival from friday-monday, sorry I was not able to look at this sooner...

[Amos]

New one - fixes filter issue reported by francesco in v1.25... check it out! Thanks

http://seamslikereality.com/moog/Taurus ... 12_MAC.zip (mac)
http://seamslikereality.com/moog/Taurus ... 12_WIN.zip (windows)

[till]

Hi Amos,

this one is better with the cut-off.
I haven't tested the velocity yet, because I use the pedal-board all the time and no external midi notes.

Q: why does my Taurus III always erease the flash with the 10 and 5 sec. countdown twice when updating? Is the description in the read-me wrong? Or is this a machine specific behavior?

[francesco]

Hi Amos,

this one is a keeper so far. Thank you!
Checked:
- Presets
- Velocity to filter, volume and resonance
- Global midi out transpose
- Midi sync dead stop and local clock
- Midi sync any clock and start msg
- i'm not sure about the usefulness of the setting 'start msg': At the moment the arpeggiator start with receiving the start msg from the sequencer but stops with the next note off and do not start with the next played note, if there is no overlap between the played notes.
I will go on and explore the new firmware further.
Frank

[Amos]

Hi Amos,
...I haven't tested the velocity yet, because I use the pedal-board all the time and no external midi notes.

velocity works from the pedal-board also!

Q: why does my Taurus III always erease the flash with the 10 and 5 sec. countdown twice when updating? Is the description in the read-me wrong? Or is this a machine specific behavior?

I think this is to do with the underlying firmware-version; there is always a "safe mode" system which is programmed at the factory... this version will run if the regular firmware is missing or corrupted, and it is running during the flash-erase process. I believe an early safe-mode firmware did this flash erase twice, as you are describing. The earliest version does not display any message at all, as I describe in the instructions... I'll amend the instructions to include a description of your scenario also.

Thanks!

Amos

[Amos]

- i'm not sure about the usefulness of the setting 'start msg': At the moment the arpeggiator start with receiving the start msg from the sequencer but stops with the next note off and do not start with the next played note, if there is no overlap between the played notes.

That's a mistake. If a start msg has been received, the arp should respond to next played note as usual, unless/until it gets a stop msg. I'll fix it.

Please continue testing and let me know if you find anything else of which you're not sure about the usefulness... thanx!

[David Bulog]

Amos
How about ARP being able to be triggered by Gate In--that way you can program rests in a step sequencer and come up with more flexible rhythms
Failing that a least a programable rest function for ARP

thanks David

[Amos]

David: I can't implement any new feature requests just now; my focus is on getting the current code finalized for release. I would like to add a Rest function for the step sequencer; I promise I'll add something to this effect before all is said and done.

I will make a new build tomorrow that fixes the "sync start message" bug identified by Francesco. If there are no other problems, then we'll call it Taurus firmware v2.0.

Does anyone have any other issues to report in the current v1.26 version?

Thanks!

Amos

[Mr Arkadin]

I would like to add a Rest function for the step sequencer

Hang on, you can't just try and slip that by us casually. Is the step sequencer finally going to make it into the T3? If so, now would be a good time to get an editor with a step seq section.

Does anyone have any other issues to report in the current v1.26 version?

Haven't done extensive tests but it seems to be in a better state than before (once the sync start has been fixed).

[bichuelo]

Functions like the Arpeggiator, Note Off Velocity and Step Sequencer and the MIDI functions are big advantages for this instrument.

If any of these are left without practical functionality, most users would not be able to take advantage of them, and the original work that has been put into them would be lost, at least until a whole new version is developed.

That would be a shame, to say the least

[Amos]

I would like to add a Rest function for the step sequencer

Hang on, you can't just try and slip that by us casually. Is the step sequencer finally going to make it into the T3?

What I'm calling "the step sequencer" is already in there. If the arpeggiator is running with both Arp Latch and Note Latch turned on, then the arpeggiator will play a looping sequence of all the notes you enter into it, in order, including duplicate notes. The sequence can be up to 128 notes long. Maybe "step sequencer" is too loaded of a term to use for this function... but if it had the ability to program rests or ties, then perhaps the term would be a better fit.

Again, my apologies, but I have to release a new version and I can't delay it now to begin implementing new features. If the features already included in this round are solid, then it's time to rejoice and call it v2.0. I have every intention of continuing to support and improve the T3 into the future.

Cheers,

Amos

PS) sync start is fixed; preparing new update files now.

[Amos]

v1.27 - fixes arpeggiator sync start (Sync start = start msg + sync stop = dead stop)

http://seamslikereality.com/moog/Taurus ... 12_MAC.zip (mac)
http://seamslikereality.com/moog/Taurus ... 12_WIN.zip (win)