However, note that it hasn’t been announced yet, hence it is still confidential. Once we have all documentation ready, it will be delivered to Marketing for official publishing.
Also note that we have just started a new phase for Sub Phatty Editor. Expect a new beta version soon.
We want to thank you all for your time and great support during this beta phase!
I understand that the problems I had on Snow Leopard are limitations that come from the OS and/or the old Live version? Hopefully they can be added as known issues section?
I’s be more than happy to check the documentation when it’s ready.
Regarding the official release date, are we able to know when it will come beforehand? We want to record a video showing the new features, and put it online the same date of the release
I will be shooting a couple of videos showing the new features in the next days, so I made a list of changes since the last public version of the Firmware and Editor:
• Hard sync, either from the Editor or with Glide + VCO2 Level
• LFO to OSC 2 Only, either from the Editor or pressing Glide+VCO LFO AMT
• Various waveforms for LFO, can be set from the Editor or with Glide + LFO RATE
• Hardware shorcut for Wrap to Octave function. Hold Glide + turn Glide
• Editor has now an installer and creates a start menu on Windows
• New utility to update the firmware
• Glide + VCF Attack = VCF EG Delay
• New driver for Windows that allows multiple instances
• Optimized Decay & Release modes
Changes:
• Glide + VCA Attack = Trigger Mode (3 positions). Used to be VCF Attack, changed on this version
• CC mapping (don’t know exactly which ones)
I will have to look into this carefully in order to be able to list every possible change,
but from the top of my head, also:
Switching presets by clicking the Up/Down arrows on keyboard, once selecting a preset from the top menu
VSTi can be used to have the GUI panel changing when sending program changes to hardware from a Midi track, in DAWs (set “Echo Midi” to On)
Librarian functionality improved in many ways
Enhanced graphics
Save As remembers last location
DAW Midi Sync, very much improved. The waveform should start with the first beat of each bar, Divider/Rate functionality much better now (i.e Switching Midi Sync On/Off)
Real-time syncing between the list of librarian and hardware presets
Hello everyone ! I had the same issue and it was impossible to install the driver until I sat my computer in Secure Boot mode Off, which solved the issue.
I would like to be able to use the Minitaur in Secure Boot mode, though…
I just noticed an important bug with the Glide switch.
Anytime I am pressing the Glide switch while moving a knob :
If the Glide mode was OFF prior to doing this, the Glide light flashes extremely shortly without activating the Glide option.
If the Glide mode was ON prior to doing this, the Glide light flashes off extremely shortly without deactivating the Glide option.
This is also causing an issue when automations or CV signals are sent to the Minitaur while the user attempts to toggle the Glide mode.
(Thanks to CV mapping, I am experimenting a faux-duophonic technique by modulating the VCO2 Frequency while a main sequence is played.)
Knobs provoking the issue are :
VCO2 Freq
VCO1 Lvl
VCO2 Lvl
LFO Rate
Env Attack
Env Decay/Release
Amp Attack
Amp Decay/Release
Amp Sustain
LFO Rate
VCO LFO Amt
Glide Rate
Thanks a lot in advance !
MINITAUR FIRMWARE VERSION : 2.2.0 (Latest build)
MINITAUR SOFTWARE EDITOR VERSION : 3.2.0 (Latest build)
I’ve found something that looks like a bug regarding the LFO Key Sync. It doesn’t work as long as LFO MIDI Sync is ON.
Furthermore, these values do not reflect exactly their positions on the Editor as well as the unit. They might turn OFF or ON before the value actually changes on the unit
I think I didn’t express myself well on the last line. The values change before the actual parameter changes when I use Push. I would expect other controllers to do so as well
I tested this today and it works as expected for me.
Sending midi from an Ableton midi clip to MTR.
Having the Editor VST loaded on an audio track.
In Preferences, MTR ports SYNC are checked.
While playing the clip, having Midi Sync on, and then turning KEY TRIGGER, it’s engaging and you can hear the LFO cycle restarts with every new note. Also works when first turning KEY TRIGGER on, and then turning MID Sync on or off…
What’s the exact scenario you are using? and what results are you getting?
I tried yesterday and I got the same results as described earlier. Before I did, I reverted back to the last public firmware 2.1.1 (which is no longer available at Moog’s site) and I found that the different waveforms on the LFO worked, and the LFO Key Reset worked whether the LFO MIDI Sync was on or off.
I upgraded then to the current official firmware and the problem was there again. LFO Key Reset doesn’t work as long as LFO MIDI Sync is on, though I have to try yet using the same method you explain here. I am able to do so on Friday. I am simply using Push and the latest version of Live 64-bit on a macOS Sierra
One thing I didn’t compare if it failed using the old firmware was the values, which do not update simultaneously on Push and the Editor. They change on Push before the actual value changes on the unit
I made the test again Gil, and indeed, if I do it with a sequence, it works.
But, if the DAW is not running and you are simply playing ad libitum, the LFO KB trigger does not work while the LFO MIDI Sync is on, it does while the latter is OFF
SYNC ports are checked here as well
Regarding the display of the values, now I see that Push is more precise than the editor. In the latter, the values change before there are audible changes, in many parameters.
