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.14. If it says anything other than 2.1.14, 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.
On this version, the up and down preset selection buttons (arrows) next to “Preset Manager” are still randomly changing current preset.
Edit: This may be because, a previous editor version had given me some presets with the same name, including a second “panel settings”. I’ve just changed them to make sure all the names are different, and things are looking better.
Has the storing of extended settings such as velocity modulation of filter and amp been improved? I’m trying to work out if it’s fixed or not.
Edit: It’s looking better, in that I think I can store and recall patches with velocity modulation. It’s possible that some older, previously stored patches might not be loading correctly. I’ll reserve a proper report until and unless I can reproduce a real issue.
I should add that no muting should randomly occur anymore, so playing a keyboard should always trigger sound (based on the setting of the used preset of course).
But, it still jumps, something which was clear for many in the last version. This time, it only seems to jump once, between 2.30 and 4 o’clock depending on the waveform configuration
“This is the characteristic sound of the analog circuit, the stepping is caused by the harmonics of the oscillators themselves. It’s not firmware and cannot be changed; it’s just how it sounds.”
So apparently this is not something that can be changed.
Trust me, I know what I am speaking about.
I did this test while using the same feature on the Sub Phatty. I also own a Sub 37, a Voyager and two FreqBox units since this is one of my favourite features in synths. Even a customer once thought his FreqBox was broken since he didn’t understand this zipping sound at the beggining.
What I am speaking about is a jump it does once while you are turning the knob. I remember it worked properly in one of the first beta firmware versions. I could look for that specific version and/or record a video showing the problem
Please send me the preset (or presets) which demonstrates the issue along with reproduction steps, results and expected results, and we’ll have a look into it.
Move the VCO2 Freq knob slowly between 2 and 4 o’clock, please do it from the hardware so you can do it real slow Hard Sync jump at 3 o’clock.zip (318 Bytes)
We had Amos looking into your report and this is his response:
Just checked this and all is normal. If you play any MIDI note C1 or below, there is no “jump” in the sync sound. The jump is caused by the “top octave wrapping” feature, when the frequency of VCO2 is pushed above its physical limit of C5.
I am testing it and, frankly, I am not sure. It seems to work fine around C1 but it sometimes jumps again one or two octaves below it. What you say about the top octave wrapping feature makes a lot of sense…
Besides this issue, I have found that when the LFO MIDI Sync button is on, the LFO rate gets stuck in the last value, if it is not receiving MIDI Clock. I wouldn’t call this an expected behavior, but a bug.
I found something unusual:If I turn the VCO2 FREQ all way down and I press C#6 (MIDI note 86) each oscillator plays a different note, a semitone apart.
Are you able to reproduce it?
Furthermore, I feel the oscillators are off. Their pitch slightly drift across the keyboard, even after proper calibration…