Minitaur Want to roll back OS's. Help Bugs!

[Grinder]

Does anybody have an OS prior to 2.0 that they would share with me? Im having major LFO problems with 2.0, basically any preset beyond #2 it cuts off and wont come back unless i call up panel mode 4 or 5 times in rapid succession (glide plus osc 1/2). I would rather a stable LFO then be able to save at this point. wanting to try and roll back to see if some of my issues go away.

Other weirdness that really bothers me is Im getting a high pitched squeal when i turn glide on from time to time that is horrible, i can get rid of it if i hit panel mode a bunch of times as well. Also decay/release on the amp env. stops working randomly if i scroll around on presets for a while. this only comes back with a reboot Can any one confirm these?

[whomdoyouworkfor]

I'm having many of the same issues...LFO won't work and the preset system is buggy and unusable. Really starting to wonder if moog is going to address this (seems that many others are experiencing the same problems).

I went back to my old system of running 1.2 and gigging w/ an ipad to send individual cc messages to the minitaur so i can work w/ presets.

You can email techsupport@moogmusic.com for a download of 1.2.

[till]

To use the Mintaur with CV ins, the Mintaur uses the LFO with the given modulation depth when changing a patch. But once the mod wheel controller data is received, it changes its behavior to controll the modulation depth my the mod wheel's setting. The max depth is now controlled by the modulation depth knobs. This was done for all non MIDI usage of the Mintiaur. And this is a clever design. So you may only have to use your mod wheel a bit.

[Grinder]

Im sequencing it with an octatrack so there is no mod wheel involved. Im not sending it anything but note data and it drops out. I can make it it drop out everytime i switch to patch 3 or 4 from the front panel. Ive tried with a MIDI controller and had the same result and i know i did NOT touch the mod wheel.

[EMwhite]

You should consider blasting the settings with _Minitaur_Factory_Restore_Cmd.syx and then put in a fresh copy of 2.x. I don't think any of the issues you are seeing are anywhere near normal so I'll think you will be ok after you do this.

I do have some v1.x versions but there is a very good chance that there are some bugs in there... try the above then best to reach out to Amos@MoogMusic.com directly and I'm sure he'll be happy to give you the latest v1.x build if that's what you want.

[till]

Keep in mind, that the patch memory was introduced with the version 2 firmware. So you might loose this feature. And the editor in version 2 might not work well with an older Minitaur firmware version. And downgrading is not officially tested by most manufactures. And I know examples of problems caused by this due to missing initializing of certain hidden parameters on some non Moog synths. So better ask for some Moog support.

Remember, that some other gear sends out modwheel data value 0 when switching presets. And most sequencers do send a few MIDI CCs when starting or stopping playing a song.

I would recommend to check you MIDI data by using a MIDI monitor. Most so called hardware problems and firmware bugs are just a MIDI problem.

[Grinder]

@till.
I get the same result in symptoms using using either the sequencer OR a Midi controller so i dont think this is the issue. Thats a good idea about the midi monitor though just to make sure, Ive never used one though, do you have any suggestions on where i could get one? I use a Mac.

Are you guys saying that you can scroll through all you presets and the LFO responds past preset #2?

[till]

...
Thats a good idea about the midi monitor though just to make sure, Ive never used one though, do you have any suggestions on where i could get one? I use a Mac.
...

I am using this one on my Mac: http://www.snoize.com/MIDIMonitor

[Grinder]

Hey till, Havent had a chance to get on here in a while. Thanks alot for the monitor, hopefully it reveals something useful

[whomdoyouworkfor]

Grinder,

FYI I found a way to retain LFO usage w/ 2.0 and presets. If i'm sending a midi note (holding it down), and then do the glide + osc commands to move through presets, the LFO still works! Otherwise, I lose functionality exactly the way you detailed in your post. I've tried it over the midi and usb inputs.

I'm not experiencing the glide squeal or amp envelope knob issue you mentioned in your initial post, so I can't speak to that.

The only other issue I'm experiencing is related to the "capture bank" command in the Editor software. When I use it, the Minitaur mislabels all the presets (preset 1 is now preset 2, preset 2 is now preset 3, etc) in the Editor window, but I've found this issue to only be related to naming. So if you already know how your presets are sequenced in the Minitaur, you can just ignore this misleading information/not use this button.

Hope this helps!

[Amos]

I think I may modify how the LFO AMT knobs interact with MIDI Mod Wheel, to fix this.

The idea is, if you turn either of the LFO AMT knobs, the "MIDI Mod Wheel" value inside the Minitaur will be set to maximum (as though the mod wheel on your controller was all the way up). This way, if you're adjusting LFO Amount from the panel, you always hear 100% of the amount indicated by the panel knob. If you are using a MIDI mod wheel to control the Minitaur, this will continue to work as it does now... the only difference will be that if you're NOT using a MIDI mod wheel, you won't get stuck in a state where there is an imaginary mod wheel that is set to zero. I believe that in essence is what's happening here.

Minitaur firmware updates and bugfixes scheduled for the near future; stay tuned for more info. Cheers!

Amos

[Grinder]

Thats fantastic news! Thanks Amos, looking forward to the update

[aen]

Urgh. Just had a real rig nightmare. Practiced with the minitaur and my behringer FCB1010, everything was fine. Set up for a gig, no midi into the Minitaur. Today I updated the minitaur to version 2, and the behringer controller was working, except everytime I hit a note, the Minitaur jumped to a preset. As it turns out, I can't seem to edit my FCB anymore. Something is certainly screwed up there. I would like to go back to version 1 on the minitaur, because it usually worked.

[aen]

*UPDATE*

Of course. Reset the computer. Got the "program change" messages out of my FCB. NOt sure about the "midi quit" issue. I guess I'll bring extra midi cables and whatnot in the future.