Fixed Ableton crash which was a side effect of the new workaround we did on 3.2.0RC16 for having the panel following program change commands from the DAWs.
As usual, we’d like to consider this our final release. Please remove any older components, download and reinstall the full package. Let us know how it works for you.
NOTE:Please do not link or publish this version to anyone outside this beta group, as it may cause different versions of the product carrying the final version numbers to co-exist on-line.
The driver allows DAWs to use Minitaur’s Midi ports and an Editor plug-in at the same time.
NOTES:
Drivers haven’t been changed since the last version, so no need to reinstall if already present.
Users must first update the Minitaur 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.
Installation Updating the Firmware:
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.
Connect your Minitaur 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.
Run the updater and follow the instructions
Once completed, run the Editor and check for the firmware version by clicking on “Settings”. Verify it says “2.2.0”.
Installing Windows drivers:
Power off your Minitaur and disconnect its USB cable.
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.
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.
Restart your computer.
Power the Minitaur On, connect the USB cable and let Windows auto-detect and install the default Minitaur driver. This may take a few minutes so please be patient.
Once detected, install the new Minitaur 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.
Restart your computer.
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.
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.
I’m hitting some manner of firmware gremlins, VCO2 ONLY is not working for 2.2.0 RC11, but everything is fine with 2.1.13
Test steps are:
Load editor and choose an init preset
Set LFO RATE and VCO LFO AMT to 12 o’clock
Set VCO2 ONLY state to active
Verify only VCO1 is present in the mix and listen for any pitch modulation
Editor version doesn’t seem to impact behavior. I’ve installed 2.2.0RC11 both with c6 and the official tool, also fiddled with cabling.
The official updater tool crashes on exit, but that doesn’t seem to be interfering with the success of installing it to the hardware in my setup.
It’s working perfectly here with both standalone and the plugins. Something is really very strange about your report. Are yoו confident you really are using the latest RC17 version ? Have you manually deleted all older components from your computer prior to installing it ?
I’ve just tried that RC17 version and VCO2 ONLY function is definitely not working as expected.
It does work for presets which already have it set. Here is a partial work around: after making a new preset from init, if I save it with the VCO2 ONLY state active, and re-load it VCO2 only can be heard working again.
The problem with that work around is most of the time VCO2 ONLY is being de-activated during the save process. I don’t think this is an editor problem though, I think the hardware (at least in my setup ) is not acting on the event properly.
What is the key press short cut to toggle the feature on/off with the hardware panel?
ok, I don’t remember if I asked already, but FYI the filter modulation (VCF LFO AMT) is NOT supposed to be affected by VCO2ONLY,
which means only VCO should be affected. If you take VCF LFO AMT down, can you hear the change when toggling VCO2ONLY on/off?
Are you back to firmware 2.2.0RC11 when testing that 3.2.0RC17 ?
If it still doesn’t work for you, please allow us to teamview your machine to try to figure out why… we are supposed to hand this version over today for release.
Much appreciated.
PS - it seems there’s no panel shortcut for VCO2ONLY. Here’s a list of the new combinations:
Glide + VCA Attack = Trigger Mode (3 positions). Used to be VCF Attack, changed on this version.
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)
Changing “Wrap Up” mode by holding GLIDE and turning GLIDE knob. GLIDE knob below mid-position = octave wrap OFF; GLIDE knob above mid-position = octave wrap ON. When top octave wrap is on, then notes above C5 will repeat the highest octave; when octave wrap is off, then all notes above C5 will play C5.
Right, no VCF fiddling with these issues. Basically I’m just working from an Init preset and only setting LFO RATE, VCO LFO AMT and VCO2 ONLY. The setting of VCO2 ONLY isn’t removing the modulation of VCO1 pitch. However, initializing the VCO2 ONLY state from some other pre-existing preset does work.
I’ve been back to testing 3.2.0RC17 with FW 2.2.0RC11 after verifying that behavior I’m hearing did change with FW 2.1.13.
Hello,
I don’t know if my problem is an issue or a normal bahaviour.
For info, my MTR is mainly controlled over CC message from Max/msp and only over the USB connection.
The DIN is only used to receive a SYNC from an other musician. So, in this configuration “MIDI SYNC” is always ON but the other musician doen’t always send a sync signal.
In this configuration, when there is no SYNC signal but with “MIDI SYNC” still activated, the “KEY TRIG LFO” doesn’t work until I switch off the MIDI SYNC…
It is normal ?
Thx
ps: I know you are only looking for importants problems, but as Rene “MR79” mentionned, the preset names didn’t change with program change in the VST editor, you fixed it ! Cool…
…is it so impossible to do the same with the standalone editor ? =))) In my personal setup, it’s really really really annoying… =))))… I ask…we never know =))
Here when I send a Program Change to the MTR (I mention that I only control the MTR over the USB)
→ the MTR recognize the Program change, the sound change etc…
→ the MTRE doen’t recognize it, but
→ If after each programChange sent, I send a sysex to make the MTR output all the CC, the MTRE shows the knobs positions of the good preset but the preset name in the MTRE never change…
I’m not sure to be clear.
We already talked about that few times ago…
I’m confused, as for the last few versions we posted as RC we had no reports about this. We will really release it as is at the moment, as this phase cannot take forever.
However, I’d really suggest that you do the following:
Then install 2.2.0RC11 again, and verify on the Editor that it’s 2.2.0
This may fix some issues that you might have.
P.S
Key Trigger works normally here as VST in Ableton (Windows), both when MIDI Sync is On or Off.
However, I did notice it does not work correctly when used as VSTi on a single Midi track. But this could also be an Ableton limitation (as you do not really assign any midi output in that track, thus no “sync” is actually activated).
I this this should be mandatory, my unit had a problem in one of the latest releases and was solved after doing this. Maybe there is some clutter code left on the unit, and this procedure seems to clean it completely
Yeah you’re right. This was asked a few versions ago, but probably should ideally be done whenever installing any new beta version. The normal “production” user has never used any 2.2.0 beta before, so it won’t be necessary.
I just did this update, coming from version 2.1.1 and the installer crashed upon exit, after a successful installation. Indeed, the unit reports firmware 2.2.0 after this and seems to work fine
There could be a relation between the crash and the version the unit has when you do the update…
Thanks. It’s not likely to affect the firmware itself, as it really rarely crashes and when it does it happens only once the full version is already installed. However, it seems like the version mismatch is really only a beta related use-case and shouldn’t happen in production.
It’s sure that it’s strange that I’m the only one to report this issue.
Here is my procédure
-I downgraded to Fw2.1.1 (verified in editor)
-I reupgraded to Fw2.2.0RC11 (verified in editor)
-I opened the editor and click “MIDI SYNC”
-I clicked LFO TRIG (then the lfo is not trigged)
-I switched off MIDI SYNC
Then the LFO is well trigged.
I tried with the editor and with CC message send via max/msp and its the same here :
impossible to use the LFO KEY TRIG if MIDI SYNC is on…
And my other problem is still the same about ProgramChanges.
The MTR recognize them but not the MTRE…