I’ve recently bought a Minitaur rev 2.0 and I am having these issues when trying to connect it to my laptop using editor software and USB cable (on windows 7 ultimate x64):
First of all, almost all of cases the firmware is displayed as ? instead of 2.0.28 in “Under the Hood” panel. I need to do many-many clicks on MIDI inputs and outputs in order to have the correct firmware displayed.
Second, I saved almost 50 presets on Minitaur using Mac OS X 10.9 and Editor for Mac, but when I try to capture bank in Windows, the software is trying to read almost 15 seconds from minitaur (the MIDI led is blinking) and then it simply displays “Capturing…” and nothing happens (MIDI led is not blinking anymore)
Third, I am not able to use get any MIDI USB input device working with Minitaur and Editor. I can change the MIDI inputs, the led blinks on change but I cannot use any MIDI USB device…
Can you let me know what to do to have Minitaur working OK with Windows 7 x64 and its software ?
Thanks
I think you’re best off with the release version of the firmware unless you’re in the beta. I’m in the beta and it’s a rocky road. Have you tried using the firmware and editor published on the web site?
Sorry to get all Yoda on you.
There are interface changes between 2.0.0 and 2.0.28 that are pretty frustrating if you don’t know about them. Also, the occasional coding mistake here and there in the new pre-release firmwares.
I don’t know if the editors are cross compatible to firmwares.
I think 2.0.0 is on the web site. http://www.moogmusic.com/sites/default/files/Minitaur_REV_2_WIN.zip
There will be a VST and VST-i in addition to the new stand-alone editor which if I understand your question, is part of what you’re looking for. I don’t know if you can expect to route MIDI through the 2.0 editor yet.
My experience with the 2.0 editor and the similar editor for the Sub Phatty is that they’re not super responsive to customized input and output settings. Basically, if your preference is for MIDI CH#2, then you’re best off setting it to 1 to use the editor. If you filter MIDI messages as a configuration election, again, can’t do that to use the editor. (Which I suppose makes sense, but you know.) To set the input chan on the Minitaur, press all four buttons at the same time and they will all blink in unison. Then whatever the next channel that sends a signal is will become the root channel for the Minitaur. Pretty slick, I think.
Anyway, I’m Win7/32 and the Minitaur 2.0 editor has been reliable except in my experience, some of the settings don’t stick, like knob mode. Hard to say if it’s just the editor not reflecting the settings or what. If you download the Sysex commands, you can just send some elections from your sequencer or use Elektron’s C6 program to send them. http://www.moogmusic.com/sites/default/files/handy_Minitaur_sysex_commands.zip
This has been super reliable for me. Same head’s up applies re firmware version though. If it’s not showing the firmware version, I think you can assume it’s not connected.
I don’t know if it’s in the new editor or the old one but under c \users \user \appdata \roaming \moog there might be prefs files you can delete.
FWIW, I think the production release of the new editor, features, firmware and hopefully documentation is right around the corner.
Thank you for your input, I’ve used firmware 2.0.0 at the moment I achieved Minitaur and I can say I had almost the same issues… it may be probably one of the linked libraries (vc x64 runtime libraries) by which editor depends at the runtime. You’re right, it’s hard to say the editor may reflect all this strange behavior… I will investigate a bit this case. Anyways, until a stable editor version for win 64, I will use Mac OS X editor because I can import my presets from Minitaur and of I can save my own custom presets into it (that is still my main issue with Windows 7 x64 and Minitaur). By the other hand a VST editor should be very good but until then I will use the customized patches with my DAW (Cubase 6). I don’t expect to route MIDI between my DAW and editor if this was your question, I understood from the first time it was designed to be a standalone editor (code written and module dependency on windows sdk and not on VST sdk), I just wanted to use it as standalone editor for my patches and of course to simply link a USB keyboard controller to this editor and not to use a MIDI cable between Minitaur and the controller.