Hi,
my minitaur editor doesnt let me to load presets (everything like tweaking other functions in Panel Tab etc works fine btw). In preset manager tab it says: hardware disconnected. I am connected via USB (setting: midi input: mood minitaur, midi output: mood minitaur).
please advise…
Thanks
T.
try to run only the editor.
I have the same issue when running the editor and a virtual key or a midi/sysex manager
I am having a similar issue - I am sometimes able to get the software to connect but the communication is only 1-way (the knob settings on the minitaur are reflected on my screen but changes I make in the software do not translate back to the machine). Also, this is inconsistent at best and requires power cycling the unit. The status always shows as “hardware disconnected” in the editor.
I’m also having this problem!
I’m having the same issue, always “Disconnected” or “Hardware Disconnected” in the firmware. I’m not even sure if my firmware update worked, as I can’t tell. I hope this gets looked at.
Hey once again,
I contacted support - hopefully they will answer. I will let you know as soon as I know something more.
re:TLA - I don’t really get it what you mean under “try to run only the editor”. I am actually running only the editor (no DAW or so…).
best, T.
Having the exact same problem, and tried it on both mac osx 10.8.5 and pc windows 7 64bit. Seriously a major problem. Already returned one Minitaur thinking I had a defective unit, now seeing that it’s a full on issue. This really makes it unusable…please fix!!!
Hooked up my new minitaur last night and ran into this problem exactly. It’s a no go in Logic & Standalone.
Appreciate a fix as well.
A little birdie told me that there’s a bug fix update to the new editor being released any day now.
Same problem here.
I updated the firmware (I think so, anyway, the lights blinked as they were supposed to throughout the process)
Still same problem. Both in stand alone x64, and as a VST in Ableton Live 9 Standard.
Same problem here! Thank god I found this thread as I was really struggling to get info on this online. Does anyone know if the update is ready yet? THANKS!
I have the the problem here. Hello moog, any news about a bug fix?
Same problem here 
i almost went to return my minitaur… as I thought it was faulty
very annoying as I can’t save my presets
same problem here, I already contacted support team and I am waiting for their response.
I have just bought a new Minitaur and I am also having the “hardware disconnected” situation. I seem to have related issues - the firmware version in the editor’s settings never gets out of the “discovery phase” and really the worst problem for me is that although the minitaur hardware has the Rev2 decay/release control working, there appears to be no presets whatsoever even after reinstalling the Rev2 firmware (multiple times!) Is this the same situation for everyone else here or do you have the factory presets installed but cannot do anything with them because of the preset section of the editor not connecting with hardware?
I would appreciate any information before I have to run the gauntlet of returning the minitaur. I have to say that I am bit disappointed that Moog would leave people hanging with this situation.
Same problem for me with both the VST and the standalone.
Updating the firmware didn’t help
Firmware update 2.1.0 just fixed it!
http://www.moogconnect.net/downloads/minitaur/Minitaur_firmware_v2_1_0.zip
Changes:
http://www.moogconnect.net/downloads/minitaur/Minitaur_firmware_v2_1_new_features.rtf
Today,i update to firmware 2.1 and editor 3.0,but my minitaur is still disconnected of the editor.
Any suggestion?
Hi,
I’ve bought my miniature last december, I upgraded it with 2.0.21 and I could do almost what I wanted to
Today with the 2.1, I have the same issue “hardware disconnected” and sending presets to the Minitaur is not possible anymore.
What’s the problem ??
I’ve just upgraded to firmware 2.1.0 and I’ve got the same problem.
Still - on the plus side at least my minitaur accepts a firmware update now Anyway I’ll be rolling back to version 2.0 till this is fixed.