Please see final RC minitaur firmware version 2.2.0RC2b. Please install, use it extensively and let us know how it works for you.
If no critical issues are found, this is going to be the official release.
IMPORTANT: Please DO NOT link this version to anyone outside this forum and beta group. It is still confidential, and may cause different versions carrying the same number of 2.2.0 to be present. We will release it officially the regular way.
Enter bootloader mode: Press and hold VCO1 Wave and VCO2 Wave switches, and while keeping them both pushed plug the power cord into your Minitaur unit. Keep holding the two switches and press the Release switch, then release all switches. You should see the Glide switch LED blinking slowly, which indicates that your Minitaur is now in bootloader mode.
Connect your Minitaur to your computer using a USB cable. Please connect it directly and not using any hub. If Windows starts an automatic driver search, let it install the default drivers.
Load the C6 sysex program and configure C6 midi ports so they point to Minitaur In/Out (“CONFIG”)
Load the ‘Erase Firmware’ file provided in the firmware zip, into the C6 program (“LOAD”)
Click SEND. VCO1 Wave switch LED should blink as the old firmware is being erased. Once completed, VCO1 Wave LED should go dark and Glide LED should keep on blinking slowly.
Load the firmware sysex file into the C6 program and send it to the Minitaur (“SEND”). As the syx file is being transferred, you should be able to see the Midi LED blinking rapidly, and VCO2 Wave LED blinking slowly. Once the firmware update is completed, the Minitaur should reboot automatically. Your Minitaur is now updated with the new firmware.
Run the Minitaur Editor and check for the firmware version by clicking on “Settings”. It should say 2.2.0. If it says anything other than 2.2.0, it means that the beta firmware has not been updated successfully, and you should repeat the process again from the first step.
Restore settings to defaults by clicking on “Restore Default Global Settings” on the Editor’s Settings page.
So far so good, update went smooth and I see now simply 2.20 on the editor with no RC2b, correct?
I was able to reproduce the LFO MIDI sync bug I reported earlier today briefly, but now I am unable. Hopefully it was something I did wrong on my side, or the bug is now gone
I’m also hitting an LFO issue, the issue I reported in 2.1.18 has come back: Preset LFO depth amount is not heard until after touching the control in the editor.
Yes, you will see 2.2.0 from now on. The “RC” suffix is for internal use only and won’t appear on the Editor anymore.
Are you referring to this ?
If the LFO is set to MIDI clock sync, it doesn’t work until it receives a MIDI Clock Start message. This only happens when you use the unit outside a standard DAW, for example MIDI-OX or MIDI Pathcbay, and you are using an external sequencer.
Amos put much resources on the entire LFO/Sync/Mod Wheel functionality lately to make it work correctly, and we expect no issues now,
so it’d be interesting to know.
I just found something else, which I couldn’t reproduce a second time, not even after turning the unit off and back on. I understand this, as well as the problem with the LFO mentioned above, is happening when the firmware has just been installed. Once you start using it, it simply works.
The bug seems to be the following:
The CV inputs are shown in the Editor as Default. But, they don’t work until I make an assignment first. If I change the CV back to default, then they work, and remember the setting after power off.
I tried mapping a few parameters and they all work fine
The only way I think these issues can be reproduced is by rolling back to another firmware and coming back to this one. Something I will try to check later today, hopefully with the latest public release at Moog’s site
I just installed it and the previous mapping I had on the CVs was kept and works, as well as the LFO rate, which was synced to MIDI. Should I try rolling back to the last official release and the come back to this one again?