EDIT: GUI not updated when loading a preset from the top menu (thanks Hjulskov!). Will load a fix asap.
Minitaur Editor v3.2.0b6 and Firmware v2.1.13 are ready for testing !
New in this version: Windows installer ! We are still working to improve it, however current version should run and install in all Windows versions,
so please let us know if you encounter any problems installing this beta. You may need to relocate some of the DLLs once installed, to the relevant folders on your specific system/s.
Firmware Changes:
Improved LFO section:
Erratic LFO Sync rate when turning MIDI SYNC on/off
Clock Divider values should be accurate
LFO Waveshapes should be symmetrical
Fixed: No audio from minitaur upon powering on; MTR should always play sound when powered on - please report if it doesn’t.
Fixed: Erratic value transmission of VCF EG Delay (reported by kendallhalbert)
Fixed: Possible noise when switching to EXP Glide mode
Fixed: Velocity settings not recalled with presets
Main Editor Changes:
Improved: Faster GUI ! Let us know if you can feel any improvement.
Fixed: Category list doesn’t get updated according to the presets added in user area
Fixed: Preset and Category lists doesn’t get populated until selecting a preset
Fixed: Preset drop-down list structure should now match S37E menu style
Fixed: Preset drop-down doesn’t get updated with list of hardware presets
Fixed: State of the RELEASE button in hardware is not recalled correctly
Fixed: Cubase may crash when loading MTRE VST3. Let us know of any crashes !
Fixed: Minor graphical issues
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.13. If it says anything other than 2.1.13, 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:
DAW integration
LFO Midi Sync functionality
Automation
Preset saving and recalling
General stability and connectivity.
No crashes !
We are still lacking important feedback on how AU performs in Logic.
LFO sync not working for me. Whatever i do i cannot get LFO to sync with clock. VCO2 not working when hard sync is on. UI response on editor is much faster than before.
I think my minitaur broke down today. It sounds very weird. Like out of tune but worse. every patch i made sounds awful. I Downgrade to previous build but it sounds same. I have tried to calibrate it but calibrration failed with every editor (like it starts to calibrate but then stays on one note forever with only vco1 running). I am very frustrated.
Have you followed the firmware installation procedure step by step ? Lets give it one more try. Meanwhile I reported your issue to tech support who will be able to contact you directly and hopefully solve your issue. Lets keep this discussion going on email.
Update went fine. From the first start it had weird notes but everything has been fixed by calibration. Now testing the Editor and the firmware in production. Everything’s fine so far.
Still need a dedicated midi input or smth for the Editor to connect an external midi keyboard and/or virtual midi keyboard (with ‘drone/latch’ option). At least for the Standalone mode.
Standalone Editor: two bugs with presets management page.
‘Rename’ button appears in the left lower corner of the editor. (I think It has to be right over the current preset name)
The Editor doesn’t save presets to default folder after install.
Mac OS X 10.10.5 (14F2009) Yosemite
Editor version: 3.2.0b6
MT Filmware 2.1.13
Actions:
Modify any given preset
Right click the Preset Name field - you will see the rename button in the lower left corner
Rename the preset
Press Save As…
It will attempt to save the preset to user’s home directory instead of default directory (which is ~/Library/Application Support/Moog Music Inc./Minitaur/Presets Library/User).
If you press Save As and navigate the Editor to its ‘default’ folder (~/Library/Application Support/Moog Music Inc./Minitaur/Presets Library/User) it will save a preset and then ‘remembers’ this folder for subsequent saving.
Save As: The Editor “remembers” the last used location when saving presets.
If you delete MTRE preferences, the default SAVE AS location becomes ~/Library/Application Support/Moog Music Inc/Minitaur/Presets Library.
Can you try that and see if it makes any change ? these are the .prefs files under the Minitaur folder.
It probably should go to:
~/Library/Application Support/Moog Music Inc/Minitaur/Presets Library/User
With the Editor installer, if WIndows’ Display scaling (text, etc) is set to anything other than “Smaller - 100% (default)”, the Installer’s License Agreement page doesn’t show the option to “accept” or “decline” the license terms, therefore, you can’t complete the Editor installation.
I installed the Editor on 2 different PC’s, both running Windows 7. On one PC, the installer created a “Moog Music” folder on the Start Menu programs, but didn’t show the Editor, only the Uninstaller. On the other PC, the “Moog Music” folder wasn’t created at all. With both PC’s I had to manually look for the Editor and create a desktop shortcut, etc.
During installation of the firmware, after I had erased the previous firmware, the C6 program couldn’t find the Minitaur while the Minitaur was in bootloader mode. Windows did not recognize the Minitaur as a valid USB device. After exiting bootloader mode and restarting the Minitaur, Windows USB drivers found it. However, a few minutes later, the Minitaur let out a LOUD blood curdling squeal that scared the hell out of me! I had to unplug the Minitaur to get it to stop.
To finish the firmware installation, I had to go to the other PC, where I was able to complete the firmware install as normal. However, after a little while, and for no apparent reason, the Minitaur let out the same LOUD blood curdling squeal again. This time is scared my 7 year old daughter to death !
Thanks Gil. Now my Minitaur is possesed ! And too late for Halloween at that, LOL.
I have a similar problem, but I don’t even see the Moog Music folder in the Start Menu programs, only a Minitaur Editor folder which has only the uninstaller as well.
I have a similar problem, but I don’t even see the Moog Music folder in the Start Menu programs, only a Minitaur Editor folder which has only the uninstaller as well.
Mine could have been a “Minitaur Editor” folder as well. I wasn’t on that particular PC when I posted and was going off of my flaky memory
Hi Gil.
Today I tried more tests on ‘Save As issue’. Here are the results:
I deleted the prefs file and started Minitaur Editor
while attempting to ‘Save as’ my preset it opens a ‘save as’ dialog in the default folder (~/Library/Application Support/Moog Music Inc/Minitaur/Presets Library) and then IMMEDIATELY jumps to my home directory root. I cancelled the dialog and proceeded to the next step.
As we know, the ~/Library folder is hidden by default in Mac OS X, so I opened Terminal and run a command ‘chflags nohidden ~/Library/’.
After this command I got back to MT Editor and tried again to ‘Save As’ my preset. Now it navigates to the default dir, and no jumps to my home root dir, and no problem: I saved the preset do my desired location in ~/Library/Application Support/Moog Music Inc/Minitaur/Presets Library/User
For additional testing, I switched to the Terminal and run a command ‘chflags hidden ~/Library/’.
Further Save As dialogs AGAIN jump to my home root dir. No way to navigate to ~/Library with default Finder settings.
So, this behavior of the editor is somehow related to the ‘hidden’ flag of the user library directory.
Temporary solution: run ‘chflags nohidden ~/Library/’ in Terminal
!
! And too late for Halloween at that, LOL.