[MTR]2.1.20[MTRE]3.2.0rc1 Testing Result

Here is what I found in my testing.

All of this testing is done via USB MIDI if that makes difference.

In Ableton with the Editor Closed playing a sequence or holding a note, when you open the editor the Minituar stops playing until you hit the next note. Looks like the VST is making a connection to the Minitaur and this bogs it down for a second and then once the VST makes a connection you can continue playing a note. I don’t remember this being a problem in the previous FW.

The LFO set to midi synced when changed from the LFO Rate knob on the Minituar won’t allow you to control it from the VST editor anymore. This happens after you use the LFO RATE knob once. So when you first power up the Minitaur, then open the VST, you can change the Sync rate. Once you use the LFO rate knob you can no longer use the VST to change the rate. I don’t know if this is feature or not. But if I select 1/4 in the VST editor it won’t go to that sync unless you change it will the LFO Rate knob. I tried power cycling, reseting the VST to defaults etc. Always happens to me.

The LFO shape is not working at all after you use the LFO rate knob to change the sync rate. When you first power up and use the editor without touching the Minitaur physical panels controls it is fine. So it seems that everything is fine editing in the VST until you use the LFO Rate knob to change anything.

Thanks for reporting, checking into it.

First and third issues I can’t reproduce.

The second I could reproduce once but the next times it worked as expected, so I’m not sure.

The third one (LFO Shape) is -critical- , please let us know the exact steps we should follow to make this happen.

Can you try the same with the following firmware/editor versions 2.1.21/3.2RC3 and see if it happens?

http://www.moogconnect.net/downloads/minitaur/Moog%20Minitaur%20Editor-3.2.0rc3-OSX.zip
http://www.moogconnect.net/downloads/minitaur/Minitaur%20Firmware%20Updater-with2.1.21.zip

There are some issues with this version, therefore it hasn’t been officially posted for testing, but it would be interesting to know.

Thanks!

Here is a video of what I am experiencing.
https://www.dropbox.com/s/pzmnt030fn9tvwy/MInituar%20Beata%20FW%20Video1.mov?dl=0

Will download the latest FW and test.

Here is my testing with the latest 2.1.21 and the latest editor. The LFO shape is fixed and the rate is fixed. Opening the VST while the miniature is playing still stops the minitaur from playing. I have this normally plugged into my Thunderbolt display USB port. I tried plugging it directly to my laptop USB port and it still does the same thing.

Here is a video again.
https://www.dropbox.com/s/fjwpa18tuhc15yw/Minitaur%20Beta%20FW%20Video%202.mov?dl=0

Thanks for the videos!

So the only issue now is that minitaur stops playing while instantiating the plugin ?

I’m not sure it’s not a limitation but I will check. We logged this item on 2.1.9, which seemed to not to happen later on 2.1.14, anyway doesn’t seem like a high-level issue, as you usually wouldn’t instantiate a plugin during live performance, and save projects already have it pre-loaded.

Correct. The only issue I see is initializing the VST while playing stops the Minitaur until the next note.