Following is a new dedicated Windows driver for the Minitaur, accompanied with new firmware v2.1.9. Upgrading to firmware v2.1.9 is required for the driver to work properly. This new driver should allow DAWs using MTR’s Midi ports and the Editor plug-in at the same time, meaning that you should be able to send and receive Midi to and from the unit while using the Editor.
NOTE: With the new dedicated driver for the Sub Phatty posted, 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” under “Windows\system32\drivers” before continuing.
Please note the driver should only be installed after upgrading to firmware v2.1.9, and not before.
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 MTR unit. Keep holding the two switches and press the Release switch, then release all switches. You should see the Glide switch LED blinking slowly, this indicates your MTR is now in bootloader mode.
Connect your MTR to your computer using a USB cable. 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. You should see the VCO1 Wave switch LED blinking while the old firmware is being erased. Once completed, VCO1 Wave LED should go dark and the Glide LED should keep on blinking slowly.
Load the firmware sysex file into the C6 program and send it to the MTR (“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 MTR should reboot automatically. Your MTR 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.9. If it says anything other than 2.1.9, it means that the beta firmware was not updated successfully, and you should repeat the entire procedure again.
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” 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 package.
Restart your computer
Power the MTR On, connect the USB cable and let Windows auto-detect and install the default MTR driver. This may take a few minutes so please be patient.
Once detected, install the new MTR driver. The installer should load two popup windows, asking to confirm the new driver components. 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 any of them are present is your system). The entries should appear under the root, with no exclamation mark in 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.
Testing:
Main thing to verify is that the new driver indeed works properly in all DAWs, and allows simultaneous use of the MTR’s USB Midi ports by both the DAW and the Editor plugin. General MTR stability and functionality is also important to verify. Please post all issue on the forum.
I think you’re one of a few here who have both MTR, SPH and S37. It will definitely help if you try to use all 3 editor plugins at once on the same DAW, and report if it works as expected.
I am constantly moving the three units from my home and to the office, so I’ll try my best to do the tests with all of them at the same time.
One thing is already uncomfortable for me is that only the S37 editor shows up in the DAWs as plugin but not as an instrument, both in mac and pc. This makes it a nightmare to set up inside Live.
As a side note, I want to ask you which OS should I keep. I updated the mac today to El Capitan and do not have Yosemite anymore (I still have an old Macbook running Snow Leopard) and I am able to update my computer running Windows 7 to 10 for free until July 29th. This will leave me without Win7, but still with a couple of ancient WinXP computers.
Should I discard the Windows 7 OS? I use it mainly for email, office and these tests…
Went smoothy and the Editor (v. 3.1.0) shows that my Minitaur is running FW 2.1.9.
However it seems like none of the new functions (Hard sync and new LFO functionality VCO 2 Only, LFO Shape, Clock Divider) are working.
When I change value for these I can see Midi is sent and MIDI LED on MTR is flashing, but there is no audible change to sound.
I have tried using both panel-settings and presets.
Other (old) functions seems to work fine when altered from the editor.
I have also tried the VST plug-in in Live but it’s the same issue there.
I have tried to re-install the FW but it didn’t help.
Edit: I upgraded from FW v. 2.1.1 and editor v. 3.0.4 and didn’t remove old editor before installing 3.1.0. Otherwise I followed the instructions.
Edit: Just tried the Windows editor on Win7 -same issue.
I tried again several times uploading 2.1.9 -but it didn’t fix my issue.
Then I tried to load 2.1.7 and that worked -eventough the MTR seemed to be transposed 2 octaves down.
Then I loaded v. 2.1.9 again and now the different LFO shapes works.
However VCO 2 Only doesen’t seem to have any effect (with or without hardsync enabled).
When only VCO1 turned up and “VCO 2 ONLY” enabled I would expect “VCO LFO AMT” to not have effect on VCO 1 -which it has.
loaded the New FW. (MAC) Everything seems to be working except the LFO Shapes. maybe hard sync too… not hearing much of a difference
Also when I change patches via a controller, the editor still does not follow along.
I havent really dug in, but otherwise… the rest appears good. Seems to have solved the velocity-related weirdness with some patches.
EDIT*just played around a little more: the VCO2 only LFO feature stops working after a little.
The only shape that doesn’t seem to work from the LFO is the EG, strangely enough as soon as I began playing the only waveforms that worked were Triangle and S+H. I tried turning it off and it worked fine aftwerwards.
The hard sync seems to work, however the Freq value seems to jump.
The VCO 2 ONLY button does not work, the LFO still modifies VCO 1 when it is ON
Working on win 64bit, 64 bit software(Live) updated firmware succesfully, installed driver, latest editor:
Everything installed fine,
VCO sync doesn’t seem to do anything, VCO2-only on the LFO neither.
The LFO waveshapes seem to have some kind of slew with sharp changes,
making the square rather blunt sounding (no sharp cuts) and the attack of the saw very indistinct.
The saw down actually sounds more like the ramp in a different phase starting point then an actual saw.
the clock-division display on the midi sync rates doesn’t follow the physical rate knob settings.
Also, when i set the lfo to midi sync, the triangle setting seems to sound more asymmetrical to me than when it’s in free mode (the descent is a lot faster than the ascent)
No luck even after upgrading the firmware from 2.1.8 to 2.1.9. When using the default windows driver I can get the standalone editor to recognize the Minitaur but once I remove the old driver and update to the one provided in this post the standalone editor no longer sees the Minitaur. Also, I have to do a hard note reset with all 4 buttons to open a new midi/audio track pair in Cubase which will work to send midi via usb and return audio but I have to do a hard note reset every time I add a track. Editor does not recognize the Minitaur as an instrument track or audio vst in Cubase. What else can be done? The best I can do right now is use the standalone to save patches which doesn’t do me any good while working in Cubase. Ugh..
There are a few critical issues which require fixes to be made on firmware side. We expect to have a new version as soon as Amos is back into MTRE/SPHE firmware development, which we hope to happen during next week. We appreciate your patience.