We worked intensively this week to try to reach a point in which we feel comfortable with releasing this version. We would like to ask everyone to delete/uninstall all older components, reinstall the firmware, drivers and editor, and report how it acts for you. We’re only one step from approving this version for release, and your feedback is highly valuable.
NOTE: While Firmware is unchanged, Editor is now 3.2.0RC11. However, we removed the “RC” suffix from the Editor executables, so it appears as 3.2.0. 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 number to co-exist on-line.
Changes in this versions:
GET will be asked only once, in case the user saves a preset to a new location
Fixed: GUI might freeze when processing the list of presets after GET
Fixed: Save As working again
Fixed: Crash once completing GET in Windows (please verify)
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.
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 is says “2.2.0”.
Installing the driver (Windows only):
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 understand the next step is to update the manual, which I understand should be included in the installer? The current release has one, but it is available only at the site, not in the program’s folder
The docs will be updated by Amos and added later. We have no ETA for the official release, and it’s mainly based on markeating-level decisions. However once RC11 is found to be stable enough, we will deliver it and go on to the next beta.
I have found a problem while running the Editor on Snow Leopard
The CV Mappings don’t populate, they appear empty although they keep the last parameter set and work correctly. You are able to map them afterwards and it works as expected.
After you change the view to another tab (I.e. from Settings to Preset Manager and back), or you close and open the Editor, the same issue persists; the mapping still has the last set parameters, but they are shown as blank spaces again
Still lots of weird behavior, panel setting is silent, save for some clicking sounds, only some presets make any sound and it’s usually abruptly cut off - pretty terrifying stuff. Took my unit apart and re-seated the ribbon cable which did not help.
For whatever reason, perhaps my unit does not take well to the new installer app. Everything is working as normal after reverting back to Minitaur_Firmware_Beta_v2.2.0RC4
I’m running El Capitan and CV setting are persistent. I haven’t tried the CV functionality on the hardware though, but settings are persistent in the editor. Eg. the settings are as I set them after closing and opening the editor.
Also the hardware works well -all presets works as before.
However I don’t think I uninstalled the previous editor before installing this latest.
Edit: I have now tested CV functionality by connecting my Korg SQ-1 and it works as expected -also tried to restart hardware and editor. Settings are persistent.
Installed FW 2.1.1
Started editor (3.2.0) -could not find hardware (maybe because the FW was too old?)
Ran FW updater for 2.2.0 (version 2.1.1 confirmed)
Updated FW to 2.2.0
Uninstalled Editor
Installed Editor ver. 3.2.0 RC11
Had a quick test including of presets (stored in hardare) and the CV mappings (both editor-settings and hardware using SQ-1) -everything seems ok.
Edit: found a minor thing : when having one of the CV inputs mapped to a filter destination some other pots are moving a tiny bit in editor also.
Edit2: disregard Edit1 -this was because my SQ1 was set to 8V, setting to 5V everything seems good.
When having Pitch or Volume CV mapping set to Filter Cutoff -turning the cutoff pot on the hardware causes heavy distortion.
However when using Filter CV in this does not happen.
Just realizing that I only voltages up to 5V are allowed -have I harmed my Minitaur?
-I was running the SQ-1 at 8V for the first minutes…
I didn’t mention that the CV mappings are correctly saved and this function works fine on the Editor when I plug the unit to the Windows 7. The issue only shows up on the Editor and it is only on Snow Leopard.
There are no issues in this regard on the hardware.
I saved some specific CV Mappings on each computer, changed the unit to the second one and the mappings were correctly saved on the unit. The problem seems to be only on the display in the Editor on 10.6.8
I haven’t tried any of this on El Capitan since I have to move the Minitaur to our workshop, but I am doing this at home. Shall I do it? I plan to do the full reinstallation you describe during the weekend anyway…
I also wonder if I am the only one who is doing these tests on Snow Leopard…
Yes, it would be great to know if the same issue appears on El Capitan as well for you.
So to sum it up -
In Snow Leopard, whenever you go to the Settings page, the 3 CV mappings fields show as empty
If you make a selection on any of these fields, it will be stored in the MTR, so if you connect your MTR to a different OS, the Editor shows the stored selection?
It’d be great if you can reinstall everything inc. firmware (manually) and also check this on El Capitan,
I have my Korg SQ-1 connected to Pitch/Volume CV and have mapped the Cutoff to the connected input.
Eg. I have mapped Pitch CV to Cutoff which then modifies the cutoff as expected -but if I then turn the cutoff pot while cutoff is being modified via. CV the sound gets distorted whilst moving the pot.
I also noticed that when booting op the hardware the panelsettings are not scanned -meaning that the actual sound does not refect the panelsettings. I can prove this by turning off the hardware, turn cutoff all up, turn on the unit and no sound is outputted until i slightly move the cutoff knob.
It’s the hardware -when booting up the sound should reflect the panel settings -it doesen’t. Eventhough the cutoff is fully open and VCO2 FREQ is centered the filter is closed and VCO2 is way off.
What you’re describing is very critical. Still I can’t reproduce it… Setting the panel, playing. Switching off and on, playing. Same sound (also for VCO2). No Editor involved.
Did you manually re-installed firmware 2.2.0rc11 ?
Are you having anything connected to any of the CV Ins ?
Can you video that ? or list the steps for reproduction ?
I used the updater to install firmware 2.2.0rc11.
Nothing other than my midikeyboard on MINI IN and audio out was connected.
I’ll mail you a video showing the issue and steps for reproducing.
Should I manually delete and install the FW ?
Edit: Got an answer from Amos -the distortion I experienced is expected:
“So, the distortion comes because the parameter is getting two streams of updates for the same parameter value, and if the values don’t match it jitters between them as each new message comes in.”
