Hi all! I fixed some Taurus 3 bugs this week, and added a couple of features.
This should probably be called version 2.1.0, but I’m tagging it 2.0.3 since it’s not been officially tested yet and this isn’t an official release. It seems to work though; maybe you’d like to check it out as well.
Fixed: MIDI OUT filtering works now (can choose not to send Volume CC7 from volume wheel, or no CCs at all from either of the footwheels, only notes). Also, MIDI CC output should be better.
New: Can save footwheel volume per preset, can save pedal transpose per preset.
Nothing seems to happen at my end. I get a brief message saying “Updating…” (it is too brief to see the rest of the message) and then nothing seems to happen. Is it supposed to do the full count up and reset like previous updates?
yes, it should follow the same routine as all the previous updates.
I know it works for me and at least one other fellow… make sure FW UPDATE is enabled (Master menu, System utilities page), this defaults to Off every time so you need to set it manually before sending the update. If you’ve done that already, try changing something about your MIDI-sending situation (switch to USB, switch from USB to a 3rd-party interface, update the drivers for said interface…)
Only just read this - this will be great for quick changes even within one song - a bit like hitting the Octave switch but with any transpose avaialble. Nice one.
I think I’ve been one of the most vocally downbeat about T3 continuing development so a big thumbs up and a pint if you get to London. Here’s looking to v2.5 and ultimately v3.0.
Are you wearing a Santa hat and going on UHF TV touting that it’s Christmas in April? : )
I was perfectly happy with the code in my Taurus (which is old by any measure) because when I stomp on dem pedals, the house shakes, but kudos and thank you for not leaving the faithful in the dust.
You might need to recalibrate the control wheel? After the first firmware update I did I noticed I couldn’t easily zero whatever parameter I was controlling. Recalibrating worked perfectly.
Well I did the calibration procedure, without success. The number on the display reads out correctly, but the parameters are really at 1/4th of their usual value.
I tried using external controllers (7 or 14-bit) too, and even though the display on the T3 doesn’t update in realtime, the same thing happens.
Everything works as expected when I roll back to 2.0.2
hmmm, interesting! evidently, this is not the same for everyone.
I’ll compare the two versions carefully, to see what could be the difference.
Thanks for your tests!
FYI The FW 2.0.3 updated successfully (via USB) without a hitch — following instructions from the last T3 update using the supplied SYsEx app
Unfortunately, as far as I can tell either this FW update still hasn’t addressed the ARP/TRANSPOSE problem I bugged you about ~ or perhaps I have just not set something right in the T3 menus?
Problem remains — Sending notes out from Arpeggiator works properly only until I hit the transpose button after which the T3 plays the transposed notes but the MIDI notes going out do not change from the original pattern… is there something else I need to do within T3 menus or has this just not been addressed yet?
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?)
That is SO cool! I wonder if it should have it’s own page like the Slim Phatty ARP though I realize the layout is completely different and we have dedicated on/off switches controlling the ARP already… Thinking perhaps that would be a way to give us a choice to set SEND TRANSPOSED MIDI NOTES on/off
While you are at it, I am remembering there was another issue discussed here previously in the forum about the high C?(top note if bass synth scale) ringing out when a note above the recognized pitch scale is sent to either Minitaur or Taurus - was that already addressed? While I have used it to good effect in a ‘happy accident’ kind of way it would be very nice to be able to filter THAT out
Lastly, to the other user in the thread - au contraire about the Mintaur it is certainly no toy and works amazingly well either WITH Taurus or independently. Personally I can’t see parting with either of them! In fact even with this glitch in the transpose I just laid down a beautiful track with Taurus sending out notes to the Minitaur while playing the XL on top. Then I added a track of hammond going through an MF 104 and left the power on out there, so better get back to it …just came in to check these messages
As long as you’re working on it, one other small item I’ve noticed is that latched notes will end the first time the control wheel is moved. If you change the wheel’s position first, and then latch a note, there’s no issue. The note remains on through subsequent changes to the wheel’s position.
The control wheel is almost always set to Cutoff on my rig so I can’t say for sure that the note would end if you were adjusting, say, resonance for the first time. But the latch stays on if I modulate Cutoff via CV and leave the wheel alone.
Further thoughts on the ARP and specifically the NOTE LATCH in relation to arpeggiator feature — Being able to use the buttons is brilliant … — Meanwhile, the NOTE LATCH feature is implemented for the MINIBRUTE in software only – I am not sure if T3 Software similar to Minitaur REV2 is coming - but if so it would be nice if we had that option too ~ or even something like the MIDI MuRF Pattern Editor built-in
This is what I was hoping would be in the editor. Imagine being able to edit patterns on your computer visually, then store them in place of arps for live work. Would be brilliant.
