Minitaur firmware update soon - your requests here please

[Amos]

Hi all, and thanks for the quick feedback! I will work on all of these things today.

robml: well-spotted; I believe I changed the quantization routine (which maps a continuous value to a stepped parameter like Clock Divisions), such that it's getting off by one or two relative to the Editor. I'll make sure they are on the same routine and this should fix the problem.

Regarding Glide Type, when you divide MIDI range (128) by three items, the division actually falls at the value 85.3333... so it's 85 or 86 depending on what rule one uses for rounding up or down. The important thing again is that the editor and the Minitaur must use the same rule.

ricards: Beautiful work on the panel! Thank you very much for sharing it, and I will think about your suggestions for additional function mapping, too.

dshook: will check out the knob modes right away... it should indeed be a simple fix, if needed.

[Amos]

Should I be able to find the updates under -> Moogmusic.com / Support / Downloads...
or are they only available throughout this thread?

Also, I believe I will be updating from 2.0. Will I need to do the note calibration?

Lastly, are there official manual addendums for the updates outside of the descriptions in the posts by Amos?

I forgot to mention, you will NOT need to do a note calibration, if you are updating from v2.0 to the current beta (2.0.30) or the final 2.1 firmware once it's released. The note calibration was only necessary for some of the intermediate beta versions, while I was experimenting with some changes to the control voltage system. That's all sorted out now, and no re-calibration is needed.

[robml]

Regarding Glide Type, when you divide MIDI range (128) by three items, the division actually falls at the value 85.3333... so it's 85 or 86 depending on what rule one uses for rounding up or down. The important thing again is that the editor and the Minitaur must use the same rule.

i would suggest that if you are going to change it to 86, that you should also change the manual to reflect this for both LCT and EXT. otherwise people may try and program the synth via midi and have it land on LCT instead of EXT.

cheers

[Amos]

Hi Amos - any idea about changing the knob mode to "snap" ? It seems stuck on "relative" on my MT. I have tried the v.2 editor via USB as well as sending the sysex command directly via DIN MIDI and nothing seems to change the knobs' actual behavior. If this is in fact an issue I'm sure it's a simple fix for this upcoming release, and if it isn't, can someone please fill me in on what I am missing?!

Thanks

Dan

Dan-- I see what the deal is. I changed how global values like knob mode are edited, to make it more efficient for the new editor... however, I foolishly removed the old way to do it. That's why the v2 editor and sysex files are not changing the knob mode. I have put back the old way again... in the next firmware build, you will be able to edit the knob mode via the v2 editor or the sysex again. It's working already, if using the v3 editor. Next build will work with both. Thanks for reporting this!

[bafonso]

Is there a way to know on which preset we are reading/saving to from the front panel ? It would be nice if one oscillator button blinked for 10 20 30 and the other for 1, 2,3,4,... so you could easily know which one you are editing.

Sorry if this has been debated before but it's a long thread

cheers
b

[gab66]

Hi, i have stuck notes with 2.30 version too. Will it work with the V3 editor?
Will the release contain a VST how you told me by email?
When do you think to release it?

Thanks

[Karsten42]

Hi Amos,
i recently had a problem with my minitaur and sent it back to the dealer. When i got it back they said they had updated the software. Now the problem's gone but i'm very confused exactly which version of software it has. I would suggest to provide a simple continouus text file with a change documentation on the download server.

Maybe

Version 2
- FIX Now it works
- UPDATE changed color from black to white

Version 1
...

This would help much.

Kind Regards,
Karsten

[robml]

upgraded from version Minitaur_firmware_v2_0_30.syx to Minitaur_firmware_v2_0_32.syx

EDIT: updated this post to reflect problems still in v2.1 and an extra error i found.

here are my thoughts

-----------------------------------

MANUAL NEEDS TO BE UPDATED FOR GLIDE TYPE
0-42 LCR
43-85 LCT
86-127 EXP

-----------------------------------

LFO MIDI SYNC (PROBLEM 1) (Shows in MIDI Data as: Controller 87)
does something strange
if you send it a value of 64, it changes to 65
the manual shows 0-63 / 64-127 so shouldn’t it default the the first value of the parameter range (64)?

-----------------------------------

LFO MIDI SYNC (PROBLEM 2) (Shows in MIDI Data as: Controller 87)
when i set midi sync to ON (64 that becomes 65) the LFO speed DOES NOT change to the speed of the interval i have selected.
its as if the clock divider is having no effect on the LFO.

i cant get the LFO to sync to tempo in ableton or pro tools.

-----------------------------------

LFO CLOCK DIVIDER VALUES
FIXED!

-----------------------------------

LEGATO VALUE INCORRECT (Shows in MIDI Data as: General Purpose
does something strange
if you send it a value of 64, it changes to 2
the manual shows 0-63 / 64-127 so shouldn’t it default the the first value of the parameter range (64)?

-----------------------------------

KEY TRIGGER VALUE (Shows in MIDI Data as: General Purpose 7)
does something strange
if you send it a value of 64, it changes to 65
the manual shows 0-63 / 64-127 so shouldn’t it default the the first value of the parameter range (64)?

-----------------------------------

thats all I’ve got for now. out of time.

thx for your effort amos

cheers

[bozechicago]

hi Amos and all
thanks for your work in developing the minitaur, im particularly pleased by the shortcuts for having new parameters accessible on the front panel.
since im using my memory for so many other things, i started sticking some tape on the panel and writing the shortcuts.
then i thought i could go a little further and print some stickers with labels with similar design to the minitaur.
you can see what i did here http://makenoise.org/minitaur-update.html
in the first image is the panel with the stickers for the current available shortcuts.
for the second image, i started to imagine how it could be if is possible to use every knob for the other 'under the hood' parameters.
i think with good labelling we can say it all becomes 'front panel operation'
cheers

Dude, GREAT work, especially on the second overlay.
Amos, Id love to see all those shortcuts implemented!!!

[Casper]

http://makenoise.org/minitaur-update.html

The second image is all i want. )))

Amos, it is possible to implement this?

[LexTron6K]

Any news on the release of the new firmware and editor?

[andrzejmikosz]

Any news on the release of the new firmware and editor?

[ChrisO]

No word yet? I thought the editor was in beta months ago.

[gabrielakira]

Hello All,

I was wondering if anyone could offer some advice.

My Minitaur when run via CV to my Elektron A4 has all sorts of pitch and note issues.

For example:

C1 is at F#1. When playing up from C4 it starts going lower in pitch.

I am using firmware V2_0_28

I have tried:

Pitch calibration.

CV calibration (sending 1V to C1 then C4)

Factory Restore.

Checked cables.

Turned unit on and off.

Unfortunately the unit is virtually unusable in this state. Has anyone experienced similar problems or have any advice they might offer?

What is the latest firmware available?

Many thanks,

Gabriel

[till]

...
What is the latest firmware available?
...

2.1.0 released in March this year