This is my first use of the latest FW and VST this is what I found to not be working as I would expect. Overall compared to what I had installed, FW 2.1.1 and VST 3.1, the VST isn’t crashing Ableton. Before it would crash pretty often and I would simply not use it. The previous standalone was fine but I didn’t work with it in that way. I used my simple m4l patch for basic automation but I didn’t have patch control. It would be nice if the full sysex implementation was avaliable. The stability seems much better with my time using it, I didn’t have a single crash. Keep up the good work.
After the FW upgrade and installation of the VST I did reboot my Mac and restore the VST to default settings.
\
Volume Knob not tracking in the VST when changed on the Minituar. But, When changing the knob in the VST it does change the volume output
Pitch Bend Up range jittery visual response. Can’t change past 2.
Noticed on Push 1 that the controls labeled BndUpAmn and BndDwnAm are reversed. The up control on Push, Bank 5 knob 3 is controlling the down amount and visa versa.The Dwn Amn knob is NOT controlling a parameter but nothing is being changed in the VST.
Using my m4l patch for the Minitaur I can change the pitch bend up amount. So it appears to be in the VST.
Glide Type same visual results but can’t change past LCT.
Same thing with my m4l patch I can change the value and it is working.
The glide rate control on Push is a 0-1.0 value and is changing the glide type parameter not the glide rate.
The Glide type on Push is changing the volume control parameter
Optlevel is controlling the external input volume
External Input level controls nothing
-VC02Only is controlling VCF LFO Amount
It looks like everything in Back 5 of Push is off by one control.
PtchLFOA is control in pitch bend up amount
The mod wheel on Push is controlling VCO2 Only parameter on and Off
VCAEdgel and VCAEDGEDel control nothing.
\
LFO Rate LED doesn’t indicate anything in the VST not really a issue just a visual item.
Why is the release button no on the extended page? That seems to be the only control not on the page?
The good part is I never had any stuck notes while using this FW and VST. before I used to get the occasional stuck note and would have to power cycle the Minitaur. So that is a big plus for me.
Thanks for the extensive testing and detailed report !
I reordered your comments so it’s easier to relate to them:
Thanks, let us know if this changes at any point in the future.
This is by design. The volume knob on the Minitaur is analog-only; it doesn’t send MIDI, so MTRE can’t know about it. MTRE volume knob relates to “MIDI Volume” CC 7 which the Minitaur listens to (and it’s in addition to / in series before the hardware volume) but doesn’t send.
Thanks, came up on 3.2b8 and reported.
Thanks, will report that on. I can’t tell for sure however if Push compatibility is going to be treated for this release.
I would be interested to hear from someone that is using Novation AutoMap. Are the parameters above also off? I used to but don not use it anymore since I purchased a Push. My guess is it would have the same problems as the Push control mapping.
If I remember correctly when I was using my Novation Remote 37 it worked liked the Push. The code knew what you were actively using and mapped the parameters to the knobs. I am guessing that the Push works in much the same way. They might have used much of the same code I have no idea. So, my guess is that Automap will have the same problem with this VST controls at the same points listed above. If that is the case, in my opinion it would be time well spent fixing. I don’t think it would be that hard to fix in the code. Since everything is off by one there is an array or place at the point indicated where the code is off.
I have not used a Komplete Kontrol. I know that behind the scenes of Ableton there are the MIDI remote scripts for hardware controllers. I played with them briefly when I had my Remote SL. I am willing to bet, Novation, Native Instruments, Livid Instruments etc. use most of the same code to make this functionality work. Just tweaked for their controllers. So yes. if you experience the same problems on the Komplete Kontrol I would think it is a safe bet that it would be wrong on all of these controllers.
You may then just ask why not just used the knobs on the Minitaur? What if it is tucked in a rack far from reach? I have a bunch of hardware synths and I use a Push as the central unit to everything. I only go over to the hardware synth when I am programming sounds locally. When I am working on a track I live in front of the Push and control each hardware synth from their. It would be nice for this to work correctly in my opinion.
Just tested. Everything seems fixed but noticed one new item. I probably over looked this the first time testing the beta version.
LFO Sync Display on Push is not aligned with the VST display. For example, the Push will say it is at 1/16T but in the VST it is 1/8T. When expanding the VST in Ableton the value on the horizontal slider does match what is being displayed on the Push. But, the VST is saying something different. The Minitaur is playing what is displayed in the VST window. So for example, the display on push says 1/4 but the VST says 1/2T. The Minitaur is syncing the LFO to 1/2T.
I tried the same test on my m4l patch and it is working correctly. The Push Display is aligned with the operation of the Minitaur.
So maybe it is a display threshold issue? Looking in the manual there is a range of values per time value.
Either way most everything is fixed. If the LFO rate display value can be fixed I would say the controls and display of those controls is 100%.
Good work! Thank you for fixing the items so quickly.
If you simply play a chromatic scale on the highest octave, you will notice the next C# gives you an unexpected detuning on the two oscillators which dissapears on the next D. Then it rolls back to the previous octave.
