We have a new update ready for both minitaur Editor and Firmware. These are v3.2.0b5 and v2.1.11.
Firmware Changes:
Added VCO 2 ONLY support. Use Editor, or push Glide+VCO LFO AMT on hardware to switch On and Off
Fixed VEL SENS. Should no longer allow any silent notes. Please verify if possible.
Fixed CC input/output for VCF EG HOLD, VCA EG HOLD, TRIGGER MODE, LFO SHAPE, VCO2 ONLY
Switched orientation of In/Out ports. You should now see Moog Minitaur In on the Midi In menus, and Moog Minitaur Out on the Out menus (Windows). You may need to reselect the midi ports on your Editor for it to connect.
The driver allows DAWs to use Minitaur’s Midi ports and an Editor plug-in at the same time.
NOTES:
Driver hasn’t been changed since the last version. No need to reinstall the driver if already installed.
Users must first update the Minitaur firmware, and only then install the driver.
With the new dedicated driver for the Sub Phatty, there is no need anymore for the generic moog USB driver and it should be removed. Uninstall any existing generic moog USB driver from “Programs and Features” (Control Panel) and manually delete the files “moogusbmidi_x64.sys” and “moogusbmidiks_x64.sys” in “Windows\system32\drivers”, before continuing.
No driver is needed on OSX.
Updating the Firmware:
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.1.11. If it says anything other than 2.1.11, 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.
Installing the driver (Windows only):
Power off your Minitaur and disconnect its USB cable.
If you haven’t done so already, uninstall any existing generic moog USB driver from “Programs and Features” (Control Panel), and manually delete the files “moogusbmidi_x64.sys” and “moogusbmidiks_x64.sys” from Windows\system32\drivers.
If case you are also using a Sub Phatty, install its new dedicated driver, posted here: http://forum.moogmusic.com/viewtopic.php?f=20&t=25828
Same goes for Sub 37. Use the production driver provided with the Editor 1.0.0 / Firmware 1.2.0 release package.
Restart your computer.
Power the Minitaur On, connect the USB cable and let Windows auto-detect and install the default Minitaur driver. This may take a few minutes so please be patient.
Once detected, install the new Minitaur driver. The installer should load two popup messages, asking to confirm the new driver. Mark the checkboxes and let it complete. If asked by the installer to disconnect and reconnect the cable, please do so.
Restart your computer.
Check your Device Manager settings. There should be a separate entry for MTR, SPH and S37 (in case they are present is your system). The entries should appear under the root, with no exclamation mark placed on them.
Open the Editor, click the Setting button and select “moog Minitaur In/Out” from the Midi Input and Output menus. To sync all preset, click the GET button.
What to test:
Use both Standalone and Plugin extensively and report any issues. Mainly:
Automation
Preset saving and recalling
DAW integration
General stability and connectivity. We expect the connection not to be spontaneously lost.
Crashes. We know about Cubase crash on OSX which happens if you turn the MTR down while open. Please let us know if you come across any others.
Logic. We are still lacking important feedback on how it performs there.
What do you mean by “scratchy” ? Did you get the same kind of noise in all patches ? did you hear the actual sound of each preset but there was some kind of distortion on the master output ?
No, it’s not distortion. It sounds similar to a notch filter. You can discern that the patch is different in subtle ways, but everything sounds basically the same. May I send you some clips?
Please note that I haven’t tried using the editor yet, just trying to play the synth after upgrading the firmware. Is there some post-upgrade procedure that I must follow via the editor (some kind of “reset”) that I should perform?
If you upgraded from 2.1.7 then please try to restore all global settings to defaults via the Editor once upgraded to 2.1.11, and let me know if it still happens. I’d be interested in the sound clips as well if possible, email me directly.
I just downgraded to 2.1.0 and then went up to 2.1.11 and couldn’t hear anything unusual, so I wonder what exactly is that you’re experiencing…
When i save my manel settings as new preset via “save as”, VCO2 ONLY and HARD SYNC are set to off in the preset even though they are activated when i hit “save as”.
The problem doesn’t occur when just using “save”.
Using Live 9.7, MacOS Sierra and the VST Plugin.
That was the only problem for me in a 1 hour jam session
Can’t seem to make it work inside Live, hopefully I am doing something wrong? It does work on the standalone versions, both 32 and 64-bit with these instructions.
I have tried loading the editor as an instrument and as a plugin, changing the ports after the error message, closing the editor and loading it again, closing Live and opening it again. But I haven’t been able to make it work.
Should I delete de Minitaur device from the Device Manager? Delete specific entries inside the Windows registry?
I did a few (very short) compatibilty tests this evening:
OSX 10.11: the editor works with Maschine 2.5 (loaded as vst instruments) and Mainstage 3 (as au instrument, 64 bit) and Logic Express 9.1.8 (validation passed both at 32/64 bit; used only at 64 bit). I tried loading it and moving a few parameters from the editor while playing with an external keyboard, so far it seems to work.
It also works with Cubase 8.5 (my main daw). Ot recalls correctly the setting with the song (although I’m not sure about sync settings, I’ll test it again and report about it) and automation seems to work fine (at least on the surface, I didn’t test it deeply yet), but I didn’t see the vst automation parameters for the new parameters (if this is not expected in the current beta, then I can report the parameter list I see).
OSX 10.7: the editor passes validation in Logic Express 9.1.8 (32/64 bit); I have yet to connect my Minitaur to that mac so I can’t comment on the actual functionality yet.
I noticed that VCF EG Delay (Glide + VCF Attack) seems to be transmitting values erratically, compared to VCF EG Hold time (Glide + VCF Decay). Please refer to attached screen shotz. Is this an issue?
