Minitaur firmware update soon - your requests here please

[bichuelo]

in v2.0.18, the envelope clicks should be gone, and the Release button LED should be working correctly in all modes.

These seem to behave better, however, in my unit OSC 1 is now 7 semitones below OSC 2...

[greenborder]

I do however experience something strange where the modulation / mod wheel state is sometimes reset when changing parameters. For instance when I set the VCF mod value to a positive value and then turn down the mod wheel it disables (correctly) the modulation. However when changing any parameter like the VCA release or sometimes the filter cutoff, the mod value is 'applied' and I have to turn the mod wheel up and down again to reset it correctly.

any time the VCO LFO AMT or VCF LFO AMT pots are jostled, it resets the "mod wheel" parameter to maximum.
This was the best compromise for people who are using controllers with no mod wheel, versus controllers with mod wheel... the idea being if you are turning up the LFO Amount pots you want to know what the maximum amount of modulation will be... if you want dynamic mod-wheel control, you set the Amount once and then use the actual mod wheel thereafter.

See if this is what's actually happening... if not, we can investigate further.

Yeah I understand and appreciate the concept, but with .16 it would reset when I touched other parameters such as filter cutoff. I'm currently migrating to a new computer so I'll test again in a week or so.

[ALB]

in v2.0.18, the envelope clicks should be gone, and the Release button LED should be working correctly in all modes.

These seem to behave better, however, in my unit OSC 1 is now 7 semitones below OSC 2...

SAME AS ME

coming back to 2.16 right now... hope it will not keep this mess

But, Amos... where is gone 2.0.17 ?

[Amos]

OK I will figure out why the detuning of Oscillator 2... I noticed this also but it went away (in v2.0.18) when I did a Note Calibration. So, if you want to use the newest firmware, load it and then send the note calibration sysex and it should be fine.

http://www.moogconnect.net/downloads/mi ... 72_Cmd.syx

[ALB]

i tried the note calibration before your message and it didn't worked on 2.0.18.... ( it worked before )

it made just the begining, very deep, then a sweep to highest in 1 sec and stayed like this ("biiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii") until i finaly reboot the minitaur.
made it again, "biiiiiiiiiiiiiiiiiiiiiiiii".... revert to 2.0.16

maybe i'll try again later

[Amos]

hmm. OK, I am having the same problem now. I've broken something; my apologies. It worked yesterday. Stand by, I'll get it sorted in the next version...

[Amos]

OK, tuning is back to normal.
Envelopes aren't perfect yet but they are better; should be no popping. Please try it.

http://www.moogconnect.net/downloads/mi ... 2_0_19.syx

have a good weekend,

Amos

[robml]

hey amos
i just tried to install 2_0_19.syx
i was updating from 2_0_16.syx

when the syx had finished sending, the midi light went solid and the glide button kept flashing.

the buttons were non responsive so i pulled the power.

seems to be working, but i don't know if the firmware took ok. is there a way i can check the firmware version?

the release button seems to work ok, and the oscillators dont seem out of tune.

the 2.0 editor crashed the minitaur when i pressed "Capture bank" on the "Presets Window". the sound halted and i had to restart the minitaur. then the preset names changed to what looked like the header of a file edited with a hex editor haha

the release light in the 2.0 editor doesnt ever turn off now.

i guessing the 2.0 editor is now redundant

cheers

[Amos]

the 2.0 editor should in fact display the current firmware version on the "under the hood" page.

What you described is not how the firmware update process is supposed to go.
My recommendation is to send the "erase firmware" sysex, followed by the v2.0.19 firmware sysex again,
if it updates successfully it should reboot to normal operating mode.

The 2.0 editor should behave the same with v2.0.19 as it did with v2.0.16; to the best of my knowledge I changed nothing in that regard.

thanks for checking it out

[greenborder]

Hi Amos,

The migration to my new computer went faster than expected and got to do some testing. I cannot reproduce the issue with the LFO value reset to max value when touching 'random' parameters, I must have accidentally touched while touching the VCA attack, sorry. However there are still some issues with the LFO in .16, when I turn the mod wheel fully down there is still some modulation applied to the VCF. This is easily noticeable with high resonance values (great for spooky halloween sounds ). Is this fixed in .20 or shall I wait with upgrading? Let me know if you want me to upload a audio sample.

Additionally the Minitaur editor and the minitaur are quite out of sync, for instance the LFO rate is backwards and simultaneously updates the resonance (oohhh wait maybe this is related to what I describe above?), and some button states such as legato are not shown correctly in the editor. I know you guys are working on an update but maybe this helps there too.

[robml]

hey amos,

i did the erase and then the 2_0_19 firmware. the minitaur appeared to take the firmware properly, going into normal operation after updating.

a couple of things I noticed:

after the installation of the firmware the first time you press the release button, the light didnt come on, the second press it came on and then operated normally.

every time you plug the power in the release button comes on by default. i would expect the normal behaviour to be unlit as release is the secondary function of the decay/release knob.

i dont see anywhere on the under the hood page where it shows the firmware version.

my presets are still all jumbled. i tried to attach a screenshot but got the following error message "Sorry, the board attachment quota has been reached."

cheers, rob.

[bgirl]

You can see the firmware version on the top left of the under the hood screen.

[robml]

You can see the firmware version on the top left of the under the hood screen.

must be not working for me

https://www.dropbox.com/s/9zzkqle86s6dn ... 3%20AM.png

cheers

[greenborder]

You can see the firmware version on the top left of the under the hood screen.

must be not working for me

https://www.dropbox.com/s/9zzkqle86s6dn ... 3%20AM.png

cheers

It will display on the Under the Hood screen, as shown here (if your connection is correct you'll see your firmware version there): http://www.captainbob.de/publicuse/mini ... hehood.jpg

[robml]

maybe it only does it on the windows version?