Hi, I’ve updated the Minitaur firmware using the MIDI In port (with my trusty M-Audio Uno which only serves me for that kind of tasks). I can run the standalone but you must communicate with the Minitaur selecting the Minitaur USB IN & OUT in the setup menu, and the DIN MIDI IN for keyboard or DAW input. That way it works very well both ways and the Standalone editor displays the correct V2.1 firrmware.
On the minus sides, the MINITAUR plugin does not work in VST (Sonar 8.3, Cubase 7.5) and in AAX64 ProTools 11
ok guys do the following ( instructions using only PC + Ableton Live 9.1.2 !! ) .
The problem is that the vst plugin editor needs to use usb ONLY and NOT together with ABLETON . Ableton needs to use ONLY the midi port of the Minitaur !!!
( if you select any midi port on Ableton then it stays open even if you are not running for example Minitaur !! Ports can be controlled only from Ableton , noone else !! )
( vst runs connected with firmware of Minitaur only when moog minitaur through USB is selected !!! When on midi NO CONNECTION !! ASK MOOG WHY . . . . )
So open Ableton and disable USB connection of Moog ( preferences - moog minitaur input - output — off. . . )
Then select external instrument — select MIDI OUTPUT you are using ---- AUDIO FROM … , DRAG vst editor ---- select moog minitaur input output and
the firmware connection is WORKING !!! ( at least to me … )
So only on usb to be connected with firmware 2.1 and of course NO STAND ALONE and VST EDITOR running together !!!
thats all , hope i have helped
greetings from Athens ,
bye
noob here, but i’m relatively confident i’m following the update process correctly. i’m having the same issue - I tried updating via usb, as well as midi in (via scarlett 18i8), and editor still cannot see the hardware, so i can’t load any presets.
narapo - i’m not sure what you mean by “you must communicate with the Minitaur selecting the Minitaur USB IN & OUT in the setup menu, and the DIN MIDI IN for keyboard or DAW input”? is that selection somewhere in the editor settings somewhere?
login - if the host needs a separate midi cable, does that i mean i can’t control the minitaur with my midi keyboard, AND work in ableton at the same time? or are you just talking specifically about the plug-in?
Hi
Thanks I have mine set up like that, the problem is when I go to select midi input & outputs on the VST there are none available. Even with the minitaur USB midi I/O de-selected in ableton.
Ok so I already have this set up as you describe, however when trying to assign the midi I/O on the vst there are no options at all. The standalone works fine
Guys regarding Ableton in order the input output of the vst editor to be avalaible you must first deactivate the usb Minitaur driver of Ableton on options (Preferences - Midi Sync - unclick Moog Minitaur input output - select midi output for Minitaur ) . If you dont do that OR do that when editor is running then input and output on editor are not avalaible . After that if you run the vst editor the input output options will be avalaible to chose !!! Select Moog Minitaur in the editor for input output ( usb connection of Minitaur ) and the connection is done .
Follow the procedure closely and it will work .
First deactivate usb Minitaur driver in Ableton — then chose midi output in Ableton ----- external instrument , Minitaur , midi output , input channel ---- open vst Minitaur editor , chose Moog Minitaur — done
( stand alone must be off be aware !! only one of them can be used !! )
Im running win 8.1 pro 64bit , Ableton Live Suite 9.1.2 and editor is working without any problems .
From moog support: " our programmers are working on a solution".
Amos have you any news on this? After almost 2 years of waiting i really would like to use minitaur in my studio production..
i’m using MainStage and when i put the editor in an external instrument track MainStage crashes.
Could be the same problem? Does anyone had the same problem in MainStage?
Thanks
Alessandro
meanwhile, about the “hardware disconnected” problem.
Users who are familiar with Minitaur firmware-update process, who would like to try a beta firmware version, please try this:
OK, thanks for checking! That rules out one possibility.
As soon as sub37 is released, we will proceed with developing a custom USB MIDI driver; which I still think is the probable solution for most users who are still having this problem. Thanks for your patience, and stay tuned.
Running mac osx 10.8.5, also getting the “hardware disconnected” problem with the editor. Using the USB port.
I have a USB 49 key midi controller hooked up to the mac. The editor is receiving MIDI from the controller but I can’t get note on messages to the MT via USB.
BTW this thing is a beast. For a bass synthesizer it projects that “oomph” as well as my T3 and T1. Nice work.
Tried the 2.1.1 firmware update. Still getting the hardware disconnected problem.
I’m on a recent mac mini running mavericks. Got only usb 3 ports, tried also through a powered usb 2 hub, but no success.
The thing is, I love that thing.
Love it more than my sub phatty, but not being able to use the editor ( mostly for presets ) makes it useless.
Guess i am taking it back to the store.
I will buy instantly again when the problem is fixed !
Are you using the editor when you see the hardware disconnected error? Are you running the Plugin or in Standalone?
The reason why I ask is because the plugin uses an application called Minitaur MidiPortHandler. When you open the plugin, it also launches this handler; it appears this handler communicates with the plugin and hardware. When you close your DAW, the handler does not release the process in windows, so when you open the plugin or standalone again the ports are in use and you get the “hardware disconnected” error.
I don’t remember seeing this error in previous versions, so it’s either the DAW, software or the firmware causing it. Ableton just updated to 9.1.3, and have not used the editor much in Ableton because of the bugs. IIRC FL Studio worked fine, but I have not used that in a few weeks. Cubase was working, but buggy.
I’m at a point where I don’t use the editor until they get the bugs fixed. Which is unfortunate because I work so much in the box that editors like this make is easier for me to integrate hardware. So now I’m at a point where I don’t use the minitaur at all.
If you are using Ableon there is a Max for Live editor that I know works well. I may go back to that for Ableton Projects. It does not save presets on the minitaur, but it does save the presets in Ableton. That may make the experience easier. Here is the link for it:
You can also run the standalone version side by side with Ableton. In Windows you have to make sure they do not share midi ports. It’s not integrated, which is why I don’t do this, but it does work. The standalone version for some reason does not use the MidiPortHandler.
In the meanwhile, I need to confirm if this issue occurs in Cubase as well.
The 2.1.1 firmware breaks the USB composite device on Windows 7. After you run the update, the driver crashes and will not start. Then you can not connect to the Minotaur at all . . . .
So I went back to the 2.0.0.32 firmware. That was the last most stable firmware for me. It works fine with the latest editor both in standalone and plugin.
I’ll wait until Moog sorts out their software/firmware issues and I get a solid confirmation before I upgrade again.
