[MTRE] Minitaur Editor 3.2.0RC13 is available!

We realized that some errors may happen in Windows when using early Cubase versions, which seems to be performance related. Therefore we had to change the way the files are written and GET is performed. We also improved and fixed the way the Editor handles long lists of presets.

If you are a Windows user, please use VST heavily, do GET again and again, and use the Librarian all over. Let us know if anything goes wrong.
There were almost no changes made to the OSX version, but it still important to assure that nothing has been broken.

Firmware version 2.2.0RC11 is final at the moment and we do not plan to make any newer one unless a real blocker is found.

Editor changes:

  • Cubase 5 may raise an error message once GET completes
  • Clicking Up/Down top arrows a few times may cause an endless loop of preset switching in Librarian
  • Switching to a different folder, scrolling from top arrows may navigate to “invisible” presets
  • It’s possible to trigger a function/click button using Enter during GET
  • Rotating LFO Shape doesn’t change shapes
  • Empty lines may appear on hardware presets list
  • Once doing SAVE AS the currently active preset is not marked/yellow anymore

NOTE: While Firmware is unchanged, Editor is now 3.2.0RC13. However, we removed the “RC” suffix from the Editor executables, so it appears as 3.2.0. Do not link or publish this version to anyone outside this beta group, as it may cause different versions of the product carrying the final version number to co-exist on-line.

Download full package:
http://www.moogconnect.net/downloads/minitaur/Minitaur-Release-Candidate-3.2.0RC13-2.2.0RC11.zip

Separate installers
Editor:
http://www.moogconnect.net/downloads/minitaur/Minitaur-Editor-3.2.0RC13-WINDOWS.zip
http://www.moogconnect.net/downloads/minitaur/Minitaur-Editor-3.2.0RC13-OSX.zip
http://www.moogconnect.net/downloads/minitaur/Minitaur-Editor-3.2.0RC13-OSX-10.6-10.7.zip

  • It is important that you first uninstall/delete all older app and plugin components, prior to installing this version!

Firmware (unchanged):
http://www.moogconnect.net/downloads/minitaur/Minitaur-Firmware-Updater-OSX-2.2.0rc11.zip
http://www.moogconnect.net/downloads/minitaur/Minitaur-Firmware-Updater-Windows-2.2.0rc11.zip

  • Version number will read 2.2.0, with no RC suffix.

Windows Drivers:
Driver v3.30.0 (Windows 7 and up): http://www.moogconnect.net/downloads/minitaur/Moog_Minitaur_USB_DriverSetup_v3.30.0.zip
Driver v2.23.0 (Vista or XP): http://www.moogconnect.net/downloads/minitaur/Moog_Minitaur_USB_DriverSetup_v2.23.0.zip

  • The driver allows DAWs to use Minitaur’s Midi ports and an Editor plug-in at the same time.

NOTES:

  • Drivers haven’t been changed since the last version, so no need to reinstall if already present.
  • 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.

Installation

Updating the Firmware:

  1. 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.
  2. 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.
  3. Run the updater and follow the instructions
  4. Once completed, run the Editor and check for the firmware version by clicking on “Settings”. Verify is says “2.2.0”.

Installing the driver (Windows only):

  1. Power off your Minitaur and disconnect its USB cable.
  2. 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.
  3. 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.
  4. Restart your computer.
  5. 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.
  6. 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.
  7. Restart your computer.
  8. 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.
  9. 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.

Can’t wait to test it with Live tomorrow!!!

Thanks, waiting to hear how it performs for you!

Working great at the moment!!
One thing that would be really nice is when changing presets from clips in Live, the presets in the editor also change… Hope you understand my poor english…!
I mean when making pgm change in Live, presets in the VST editor of the Minitaur is not changing too… So you don’t have the name of the preset you are using and same for the knobs… They don’t move when you change preset from Live… So you don’t know where you are…
Hope you understand!!

Does the actual preset on hardware (sound) change when you play the clip, if it was set to another preset ?

Yes the pgm change works perfectly with clips from Live. Really impressive reactivity.
And also great reactivity when tweaking hardware knobs, the knobs of the vst editor are perfectly synced to the hard knobs.
But yeah, it would be really more easy that the knobs position and preset name also change when using pgm change in Live…

This would be a nice feature, but unfortunately we’re running out of time. At the moment only critical blockers are handled. There will be (yet) one more version to test this week, which we consider as our final one.

As long as the actual sound changes with the program change commands, and as long as the settings of the Editor are saved and recalled with projects (and set the correct sound when loaded), I think we’re set.

I have not tried this at the moment but I will.