[MTR] Minitaur Editor 3.2.0b4 and firmware 2.1.10 available

The Moog Forum Moog Beta Forum
1

Hello moog beta group !

After some time working on many critical issues, we are finally posting these new Minitaur Firmware and Editor beta versions, 2.1.10 and 3.2.0b4.

Please note that although we expect a noticeable improvement over last v3.1.0/v2.1.9, there are still a few critical items that we’re currently focusing at, hopefully they’ll all be sorted out in the next couple of weeks - after which we’ll be able to provide you with a new version. However, we do feel that it’s about time to start flooding us with all new issues ! Please install and use this version extensively, and post all bugs and feedback on the forum.

Firmware Changes:

  • LFO Shape and Hard Sync should now respond to changes on the Editor, and are operational from the hardware.
    IMPORTANT: You must reset all settings to defaults in order for this to work (this should be done on the Editor).
  • VCO2 Only is still not implemented, hopefully this will be added in the next version.
  • You may still get random SYSEX error messages on the Editor. It is known and we are working to solve this. Please inform us if you still see any of these.
  • There are Midi Sync issues we know about in Ableton, working on it.

Firmware New Features (use push combinations):
Glide + VCA Attack = Trigger Mode (3 positions). Used to be VCF Attack, changed on this version. Not implemented yet on the Editor.
Glide + VCF Attack = VCF EG Delay
Glide + VCA Decay = VCA EG Hold time
Glide + VCF Decay = VCF EG Hold time
Glide + VCO2 Freq = VCO2 Beat (linear detune)
Glide + VCO 1 Level = Ext Input Level
Glide + VCO 2 Level = VCO 2 Hard Sync on/off
Glide + VCA Sustain turned from min to max = Gate latched on
Glide + VCA Sustain turned from max to min = cancel Gate latch
Glide + LFO Rate = LFO Type (Triangle, Square, Saw, Ramp, S/H, Filter EG)

Main Editor Changes:

  • Added VST3 and VST3-VI components.
  • New and improved OSX installer. Installer now removes any older MTRE components.
  • Editor should suggest to perform GET, if no sync has ever been performed.
  • Second plug-in instance is now blocked.
  • Improved Midiporthandler behavior, no errors should load anymore.
  • Plug-in names should match older names as appear in DAWs.
  • Improved plug-in stability. We’re expecting noticeably fewer errors, freezing and crashes.
  • Faster GUI response and initiation time.
  • Fixed possible GUI corruption in FL Studio.
  • General bug fixes.

Editor Download:
http://www.moogconnect.net/downloads/minitaur/Minitaur-Editor-3.2.0b4-WINDOWS.zip
http://www.moogconnect.net/downloads/minitaur/Minitaur-Editor-3.2.0b4-OSX.zip
Note: OSX users should run the installer. Windows version is installed manually.

Firmware Download:
http://www.moogconnect.net/downloads/minitaur/Minitaur_Firmware_Beta_v2.1.10a1.zip

Drivers Download (Windows only):
Driver v3.30.0 (Windows 7 and up): http://www.moogconnect.net/downloads/minitaur/Moog_Minitaur_USB_DriverSetup_v3.30.0.zip
Driver v2.23.0 (Vista or XP): http://www.moogconnect.net/downloads/minitaur/Moog_Minitaur_USB_DriverSetup_v2.23.0.zip

  • The driver allows DAWs to use Minitaur’s Midi ports and an Editor plug-in at the same time.

NOTES:

  • Driver hasn’t been changed since the last beta. No need to reinstall the driver if already installed.
  • Users must first update the Minituar firmware, and only then install the driver.
  • With the new dedicated driver for the Sub Phatty, there is no need anymore for the generic moog USB driver and it should be removed. Uninstall any existing generic moog USB driver from “Programs and Features” (Control Panel) and manually delete the files “moogusbmidi_x64.sys” and “moogusbmidiks_x64.sys” in “Windows\system32\drivers”, before continuing.
  • No driver is needed on OSX.

Updating the Firmware:

  1. Enter bootloader mode: Press and hold VCO1 Wave and VCO2 Wave switches, and while keeping them both pushed plug the power cord into your Minitaur unit. Keep holding the two switches and press the Release switch, then release all switches. You should see the Glide switch LED blinking slowly, which indicates that your Minitaur is now in bootloader mode.
  2. Connect your Minituar to your computer using a USB cable. Please connect it directly and not using any hub. If Windows starts an automatic driver search, let it install the default drivers.
  3. Load the C6 sysex program and configure C6 midi ports so they point to Minitaur In/Out (“CONFIG”)
  4. Load the ‘Erase Firmware’ file provided in the firmware zip, into the C6 program (“LOAD”)
  5. Click SEND. VCO1 Wave switch LED should blink as the old firmware is being erased. Once completed, VCO1 Wave LED should go dark and Glide LED should keep on blinking slowly.
  6. Load the firmware sysex file into the C6 program and send it to the Minitaur (“SEND”). As the syx file is being transferred, you should be able to see the Midi LED blinking rapidly, and VCO2 Wave LED blinking slowly. Once the firmware update is completed, the Minitaur should reboot automatically. Your Minituar is now updated with the new firmware.
  7. Run the Minitaur Editor and check for the firmware version by clicking on “Settings”. It should say 2.1.10. If it says anything other than 2.1.10, it means that the beta firmware has not been updated successfully, and you should repeat the process again from the first step.

Installing the driver (Windows only):

  1. Power off your Minitaur and disconnect its USB cable.
  2. If you haven’t done so already, uninstall any existing generic moog USB driver from “Programs and Features” (Control Panel), and manually delete the files “moogusbmidi_x64.sys” and “moogusbmidiks_x64.sys” from Windows\system32\drivers.
  3. If case you are also using a Sub Phatty, install its new dedicated driver, posted here:
    http://forum.moogmusic.com/viewtopic.php?f=20&t=25828
    Same goes for Sub 37. Use the production driver provided with the Editor 1.0.0 / Firmware 1.2.0 release package.
  4. Restart your computer.
  5. Power the Minituar On, connect the USB cable and let Windows auto-detect and install the default Minituar driver. This may take a few minutes so please be patient.
  6. Once detected, install the new Minituar driver. The installer should load two popup messages, asking to confirm the new driver. Mark the checkboxes and let it complete. If asked by the installer to disconnect and reconnect the cable, please do so.
  7. Restart your computer.
  8. Check your Device Manager settings. There should be a separate entry for MTR, SPH and S37 (in case they are present is your system). The entries should appear under the root, with no exclamation mark placed on them.
  9. Open the Editor, click the Setting button and select “moog Minitaur In/Out” from the Midi Input and Output menus. To sync all preset, click the GET button.

What to test:
As usual, please use and test this version in all possible ways, using both Standalone and the Plug-in components. Please also check the new VST3 and VI components. Note that some DAWs ignore VST components if they find a matching VST3 component in their folders, so if you wish to use VST over VST3, either remove or rename the VST3 files and then let your DAW rescan the Plug-in folder.

On the OSX installer the VST3 and VST3-VI components are deselected by default, so you want to mark them if you’d like them to be installed.

Further tests:

  • OSX installer stability. As some of you have reported installation issues, please report if they still happen.
  • Settings should be saved and recalled with any DAW project.
  • Please watch for stability and connection issues (“Hardware Disconnected”). We expect the connection to be very solid.
  • VI components should perform just the same way as the other, non-VI components.
  • Anything else you may think of !

Thanks for your cooperation !

2

Installed on Mac OS Sierra, no issues with installer or firmware update.

The Hard Sync switch works for me now. However, “VCO2 Only” does not engage while in standalone. Jammed a solid hour without crash (or that weird thing where the Minitaur gets hung on a note). Jammed all in standalone tonight, I’ll try VST editor tomorrow.

Besides the “VCO2 Only” parameter there are no other issues. Sooooo glad you all are still developing this thing. I loved Minitaur before and you all just made her even better.

I can’t wait to modulate VCO2 independently with both hands free for more knob turning!

3

Accidentally Jammed on the Minitaur for another hour using it as VST without additional issues. I still can’t get the “VCO 2 Only” feature to work though.

What is the difference between Editor and Editor VI?

4

@ChrisO

5

Thanks Chris.

As noted VCO Only is still not implemented, we hope to place that in on the next beta.

VI is added to retain backward compatibility with the current (production) version, basically it’s just “another” component which some prefer using over the FX plug-in.

Are you running VST or VST3 ?

6

Just tested the new 'wares, everything seems to work quite well,

sync sounds lovely and will definitely be an asset :slight_smile:
there are some strange bumps in the spectrum when you do freq sweeps though, this could be normal behaviour, it sounds quite musical, however my sub 37 doesn’t have this when i do sync freq sweeps.

lfo types, settings rates all work flawlessly, and sound perfectly as they should, kudos
decay/release and button combo commands are also on the nose

no vco2 only as said,
i tried to use a cp 251 as an external modulator of the osc 2 frequency, didn’t work, it sounds crackling distorted, and the sound level pops in and out, this could just be to do with the value scaling being off (like when you go to low with the relative frequency of the synced osc)
sometimes no sound comes out any more untill you manually re-tweak the freq knob.

i did a quick test modulating beat frequency instead while in sync, and this sounded and worked as per expected.
Please try to adress this as well, as it would be lovely to use my cp 251 and still retain the internal lfo for other purposes

one more thing, i noticed that as soon as i plug a cable into the minitaur cv inputs this generates a negative offset value, even when the cable is not connected to the other end. Not sure if this normal behaviour?

7

Notice:

Please post any feedback on separate/new threads, it makes it easier to discuss the individual reports that way.

Thanks.

8

Sorry, I missed the detail about the “VCO 2 Only” not yet in play. My apologies.

I also experienced the stepping(bumps) while manually modulating the VCO2 frequency. I do not have much experience manually modulating Hard Sync frequencies so I figured it was normal as it passes certain intervals? I will examine later if this is an unexpected phenomenon.

I tested Standalone, VST, VI VST. I can test VST3 and AU tonight. However, is there an advantage to using VST3 with an editor? My understanding is that the main feature addition of VST 3 is to route to internal audio busses. But the editor doesn’t route audio unless I am missing something.

Edit
Gil, I also wanted to clarify. I am NOT having the issues I was on past versions of editor and firmware where the Minitaur would get stuck on a single note mid performance. The issue use to happen while recording automation or just turning a bunch of knobs. Previously I would not have been able to run it for 2hrs with out having to power cycle, the new wares seem to have fixed the issue.

Additionally, it may just be me, but it seem the filter tracks better than it did when I first got the synth. Not sure if the new wares had anything to do with that.

9

Thanks!

Chris and Matthias, is it possible that you both are referring to the same issue ?

I’ll tell what I’m experiencing here:

When using high octaves, if VCO2 pitch goes up to a certain point, it’s octave will be pulled down.

This can happen in all different situations where VCO2 pitch is involved.

My general thought was that this is not a desirable behavior, but Amos is the one who should be able to tell what is involved with changing this. Since he’s a bit busy with other tasks it may take a few days until he’s able to tell :wink:

Matthias -

Regarding you CV issues, can you try to perform a full calibration to your minitaur and check this once again ?
Also try restoring all settings to default.

Thanks again.

10

Thanks for the update :smiley:

Here are my finding so far:

Hardware:
I also hear some stepping when hardsync enabled and FREQ is turned -even though note is 2 octaves below the highest.
With Hard sync enabled the FREQ pot only effects frequency when above 0.

Editor (OSX):
Tried to install without uninstalling the old editor which resulted in Installer crashing first time.
Then I uninstalled the old editor and tried again with success.
@Gil : I can mail you the crash report if you want it?

VCA VOLUME : Not synched from hardware and if turned all down on editor -you cannot turn it up on hardware.

I have fingers crossed on VCO 2 ONLY will be implemented as it will be killer combined with Hard sync :slight_smile:

/Peter

11

I would bet we are referring to the same behavior, but like I said, I wasn’t sure if it was a common behavior or an issue.

However, if it is avoidable, I think widening the smooth sweep range would be more desirable once “VCO 2 Only” pitch modulation is implemented. I was still able to find some delicious sweet spots modulating VCO2 Pitch while in Hard Sync so I personally am happy as is.

12

Thanks Peter !

Would you send me the preset that shows the “stepping” problem ?

Crash log for the installer would be great too !

Will check the Volume issue.

13

This has been a bug for a long time now, don’t know exactly when it began. For some reason I never reported this.

I also find this bug is still there: http://forum.moogmusic.com/viewtopic.php?f=20&t=25703#p156533

The new features are now working fine though in this new version, great job!!

@GilW As we are all able to see, the different issues are mostly been reported in this thread, and I know it is difficult to track each one individually. Why not assign a code for each bug? Like a number, or a combination of letters and numbers for each bug that is confirmed and you are looking into?

14

Thanks for the note,

The issue is documented and is given high priority.

New items should really be given new threads. We should basically only reply here with general beta impression reports.

15

Maybe you could add a section at the beggining of this thread; Known issues/bugs?

This would stop people like me sending in unnecessary reports :wink:

16

There are way too many documented items in our records, so it would be a bit complicated to list them all.

It’s ok to repeat others’ reports. Always better to be over-informed than under-informed.

I think in a short time we all will be able to have a clearer picture of the beta state.

17

2 of the bugs I reported a long time ago (maybe 2 years ago) are still therein this release.

Velocity to VCA doesn’t get stored via the editor.

Using the cursor up/down arrow on preset selection pull up random patches and sometimes stops navigating at all.

This is disappointing.

18

It’s still a beta, and the two issues are logged (as well as many others).

Let us know what else you may find.

Thanks!

19

Yes, I realise it’s a beta.

However, these issues have been around since the device was released (pretty-much when I bought one) in 2012 I think?

So, despite Moog knowing about the issues, 4+ years later, they’re still there.

You can’t, in all honesty, say that this is a good state of affairs.

20

Hi Purusha,

You are testing a version in beta. We took you comment seriously and logged them as high priority.

There is no point complaining about something which is not yet released, hope you understand.

Any feedback about new issues please open as separate threads.

Thanks.