Serious problems with Minitaur and editor

I just upgraded to Rev2 firmware and editor but I was also having some of these issues in the previous release (LFO, editor).

  1. Often the LFO does not work. Changing the VCO or VCF amount has no effect. Reboot fixes the problem.
  2. Sometimes reboot (like fixing the above) loses all stored presets.
  3. Editor does not get all knob positions from minitaur. For example storing my preset does not capture all settings.
  4. Loading a preset can sound different each time (all settings not transmitted to minitaur).

Is my minitaur defective?

OSX 10.7.4
Minitaur USB connection to editor

-Justin

  1. Often the LFO does not work. Changing the VCO or VCF amount has no effect. Reboot fixes the problem.
  • Do you have a controller with a Mod Wheel connected? maybe you just sent a mod wheel zero message… next time try turning up mod wheel on your controller instead of rebooting Minitaur, see if that’s all it is
  1. Sometimes reboot (like fixing the above) loses all stored presets.
  • really? like, you reboot, then in the Editor you go to the Presets page and Get Bank from the Minitaur, and there are literally no presets in the Minitaur’s memory, where previously you had definitely loaded presets into the Minitaur’s internal memory? I’ve never seen this. Maybe we should walk through the details of exactly what you’re doing.
  1. Editor does not get all knob positions from minitaur. For example storing my preset does not capture all settings.
  2. Loading a preset can sound different each time (all settings not transmitted to minitaur).

Is my minitaur defective?

– probably not defective but there may be some issues there… I’d make sure that the internal ribbon cable from the panel to the main board is fully seated, for a start… I suggest you email techsupport at moogmusic dot com for additional assistance.

Same here. Also when you have a patch where it works. when you use the modwheel the setting is gone.

Also the When usb is active on the Minitaur it makes strange noises !!!

i have a normal m key Keyboard from CME and when i try this with the modewheel no change. just swithing of the MT helps.

Also when you jumt in the editor to an empty patch, than it works fine till you use modwheel again.
I think this can not be the reason that a ribbon cabel is of etc… must be a bug somewhere.

Is this easy to fix? if not i just have 14 days money back but i wan´t to hold my minitaur…will be nice if you can fix this soon.

Hey Amos,

great ideas are put in the REV 2.

But, same here.

In the 1.0.7. I didn’t have any problems with the MOD part of the MOOG. Right now with the REV 2 the LFO’s sometimes doesn’t react and needs an restart. Didn’t change anything in my hardware setup (Octatrack sending MIDI to MT). Right now I went back to 1.0.7. and problems disappeared.
But can’t use the new functions implemented in REV 2

I don’t know also whether it is a problem of transmitting all data or what, but all of my presets done earlier sounds a little bit different or much different after the upgrade.

If you would be able to fix this that would be awesome.

Should I also contact the Moog Tech Support. From my perspective it rather looks like bugs in the software, but maybe i’m wrong.

Oh boy…Every preset that I send with my Minitaur Editor works if it uses the oscillators. If it uses filter tracking, it defaults at 50% or so. I put it to 100% in the editor, all works fine. I put it to 200%, it all works fine. All is connected via USB. All presets track over as I expect.

So…

The filter tracking is lost. I love the fact that I can “play” the filter. I can’t play it at 100% or 200% tracking once I disconnect the USB and power down/power up. Why? It’s a HUGE deal to me to play like that. I really don’t feel like working in half-steps with the filter.

BUMMER!!!

no awnser from moog ? not nice…

Well, it’s been a few days. I’m wondering if they’re working on the coding a bit more. I was able to find the presets stored within the editor software on my mac and change them, it doesn’t work that way. I really wish I had access to the storage within the Minitaur itself, that way, I could mess with the presets outside of the Minitaur by editing the .syx files, and simply “drag 'n drop” the .syx files into the Minitaur. Wouldn’t that be something neat?

The preset .syx files are wonderfully easy to understand and it would be really fun to be super-precise with the .syx coding. It works against manually tweaking the knobs, but it’s another way to adjust things.

If problems are serious, e-mail amos or rosser [at] moogmUsic.com. They are awesome at answering any concerns via e-mail. Understandably, Amos is very busy, and is not always on the forum. Best to get in touch with him directly if there are issues. :slight_smile:

Hi everyone, I am looking at these issues now. Thanks very much for the feedback, and thanks for your patience – I will definitely fix these issues. V2 is not the final Minitaur update; it will continue to get new features, and of course I want to fix any bugs that may occur, as well.

All the best,

Amos

Thanks! Looking forward to the new updates!

VERY cool -
Looks like you guys are doing a great job addressing issues with Rev 2.
Looking for ward to the next round of updates! :sunglasses:

Thanks!

Randy

I am not currently seeing the “LFO stops working” problem, and I think I am following the same steps to reproduce it. If you are having any Minitaur v2 problems, please try sending this “Factory Reset” SysEx command to your Minitaur, using your favorite sysex-sending utility:

http://seamslikereality.com/moog/Minitaur_Factory_Restore_SysEx.zip

This will not affect any presets saved in your Minitaur; it only resets all the global settings to default. I wonder if some of the trouble is caused by some global settings having wrong values after updating from v1 to v2. Please test and let me know; thanks!

Hi Amos,

no change after send the syx to the minitaur. try to update it again.
hope you will find the bug.

i also found out after sending the sys ex . now when i use the editor and jump to the 0-Panel Setings the lfo funktion comes not back.
Before sending it i can jump back to the 0 patch and it still woked again, from now on i have to switch the mt off.

when i switched it of and jump again thru the patches the lfo works , till i play the modwheel again.
this is a small affort , so long you do not use the wheel it works !!!

i don´t know if this helps… and sorry for my bad spelling

ok …it seems to be a sporadic thing . after using the mood whee again its gone.

I am having serious issues as well. First off, I have tried registering my Minitaur several times with both the MT involved and without, and I have yet to get a download link or even have the Minitaur show up in my gear list (the slim phatty appears, but all my new moog gear does not). Thankfully somebody else hooked me up with the editor which is pretty ridiculous in the first place. What sense is there in “hiding” the download. You need a piece of moog gear to use it right???
Anyway, the big issue I am having with the editor is it is not saving my custom presets. I build something on the panel and LOVE IT!!! But, when I go to save it to the editor, it first changed the name (no matter what I type) into this “E7%D7%E8%…” Now it still behaves the same way but saves them as “DEFGHIJKLMNOPQRS”. Either way, the Minitaur makes no sound when I try to reload said patch. Frankly, I could give a shit about an editor when I have all these knobs to play with EXCEPT without the editor, there is no way to save presets. DAMMIT!!! I’m now taking pictures of my Minitaur with my iphone inorder to “Preserve” presets. Is this the new Standard?? Maybe someone will answer this post unlike my Slim Phatty posts.
I love moog sound, but there software programing needs serious attention.
I hope that Moog gets is stuff together and fixes the vast amount of issues I am seeing on all the forums because this is a fantastic piece of Hardware. It is such ashame it depends on the very poor software to function fully.

same here (macbook pro 2010, os x 10.6.:sunglasses: and with the latest editor/minitaur firmware.
reboot issues and when recalled, the presets on the minitaur itself are often slightly different or completely different.

looking forward to rev2 fixes, hope you can solve the issues soon & keep up the good work.

also the lfo problem is still open and no more coment from moog about this.

For those of you with the LFO problem (the one where it stops running/light turns solid); I’m on that list, btw.

4 quick/simple questions:

  1. Do you see the problem while using a) USB, b) DIN Midi or c) both
  2. Do you have any gear in your Midi chain sending SysEx as far as you know?
  3. Is a DAW or any software running on your attached device (if USB), or are you more or less either directly connected (if DIN) or a somewhat simple USB topology where you have a Midi Keyboard connected to your PC via USB and then Minitaur connected via USB.
  4. Finally, if 1a or 1c, are you also running the Minitaur editor when the problem occurs?

Hoping to contribute to the community of owners by helping to troublshoot this. I have a pile of equipment and am very VERY good at experiencing every problem that exists : )

Thanks.