Hello everybody, and warm welcome for all new 50+ members added this week !
We are heading a release, and have made some major changes and improvements over the last couple of weeks. This comes up as a new firmware and Editor package: v1.1.19 and v0.9.39. Please note that firmware must be updated for the Editor to function properly.
Firmware updater should basically not fail (please verify)
Synth-to-Editor connection should be stable. You should ideally not see any spontaneous invalid sysex/hardware disconnected message, and controlling synth from Editor and vice versa should be solid.
Major automation issue in Cubase, fixed
Compare option support added
Fruity Loops crash when switching to plug-in settings, fixed
Automation not recorded in Ableton when done from the synth panel, fixed
Button clicks not recorded by automation in Logic X, fixed
Mapping page vanishing GUI, fixed
Many other minor level bugs fixed
Main feedback required:
Does the firmware updater fail ?
Do you encounter any connection or stability issues ?
Are you able to use the plugins in your DAW sessions ?
Are settings saved and reloaded in projects correctly ?
Can you record and save automation ?
AAX and RTAS, we would still like to know how it works for you
Hi Gil,
I installed it and had no problems under OSX 10.10.5 with Live 9.6
I tried the setup with the external instrument, which works fine. It is astonishing that Lives external instrument seems to get the latency compensation quite right. When I turn the compensation off, the audio signal is 9 ms late if the midi signal from the daw, but when I turn the compensation on, the audio is just 1 ms late. How can lives external instrument get the latency from the sub 37. Is it sendung out some special signals? I catch the audio of the moog with an uad apollo twin, running @ 48 KHz with an 128 samples buffer.
I had the firmware installation fail during the second phase. I did happen to turn off another, non-Moog, USB audio device that was attached to the same PC as the Sub37 during the second phase of the firmware installation. Donāt know if thatās related or not.
The installer prompted me to try to install the firmware again, which I did, and it began installing the second phase again. This time it completed without any problems.
Iām using 10.10.5 with Ableton 9.5 and notice that the knobs/buttons on the Editor software donāt respond to the hardware movements at all ā not the VST, AU or stand alone. The software, though, does affect the hardware (at least the on/off buttons reflect current state).
Also ran into a crazy bug in stand alone when moving the LFO rate knob simultaneously moved a whole bunch of parameters at onceā¦ as if they were all linked to that one knob.
I havenāt had much of anytime to play with it, but will post more.
Found another bug (tested in standalone osx version): When I rightclick in Preset Name field at the top and type in a new name, it doesnt get updated, the old name remains. It works only when I save a preset in the user list and rename it there.
Actually, this only started happening in 1.1.19/0.9.39 ā 1.1.16/0.9.37 was fine in this regard. Iāll try doing the āresetā button ā that helped last time.
Iām going directly into USB 2.0 port in Mac Pro 2008. Iāll try a different cable, and DIN too.
Firmware update 1.1.20 (thatās what it says when I download from the 1.1.19 link) failed at the end of phase 1 in the first attempt. But it worked at the second attempt. The second phase took pretty long to finish (more than 10 minutes).
One thing which was not clear to me from the instructions: It says to hold the pitch wheel in the 100% position and power cycle the synth. It doesnāt tell when to release the pitch wheel.
No problems with install, works like a charm, but I am missing one of my favorite functions nowā¦
Prior to this installation, I could assign the MOD 1 and MOD 2 destination by holding down the āMOD DESTā button and turning a knob, which is great. But now, this function seems to be missing.
A quick note regarding āeditor controls the hardware, but hardware changes donāt appear in the editorā ā
I have noticed that this can happen if you update firmware and donāt cycle the Sub 37 power off /on, after the firmware update and prior to testing the editor.
That is to say, Iāve noticed MIDI output from the hardware not working properly right after a firmware update; and turning the Sub 37 off and back on again fixes this. Seems to be unique to the just-after-firmware-update condition.
Possibly there needs to be some further work so that MIDI output always works right after a firmware updateā¦ but for now, just keep this in mind and cycle the power once firmware update is complete, and before testing how it works with the editor.
I updated to the latest firmware 1.1.20 and editor last night.
When I got to the end of install phase 2 it sat at installing this phase. I heard my usb connection turn off and it just sat on that screen until I decided to close it. My Sub 37 was playing presets even though to me it seemed like it didnāt finish.
So just to make sure ot installed correctly I decided to run the updater again. The firmware screen did show I was on 1.1.20, but I did install it anways. This time around it went all the way through and told me it completed.
That was the only thing that happened with the firmware update. Iāll report my Pro Tools experience in the Pro Tools thread.
Hi Gil,
I seem to have lost connection between the plugin and editor and the sub 37, probably something silly I am guessing but has me stumped right now. I have attached the error message, midi in and out under editor setting have the sub 37 marked in red text. 1.1.19 / 0.9.39 was installed successfully.
Cheers,
Bill.
Did you turn the power off/on on the Sub 37, since updating the firmware?
Did you try clicking the red selections under MIDI In/Out to see if a valid Sub 37 selection exists on the drop-down selector?
Also, are you on OSX or Windows, and (if Windows) did you install a new Moog USB Driver? That might change the names of the Sub 37 MIDI ports which might require re-selecting it on the editor Setup page.
first, many thanks to Gil and Amos be part of the beta forum.
Iām on Mac Book Pro (current 10.11.3).
Firmware installer was working as expected. With 1.1.16 i had to flash twice after the first run ended in a white / empty LCD display on the sub37.
Editor was installing as expected.
I got crashes while trying to import a sysex with multiple patches at once. I had to remove the preference files of the editor to get it working again.
i used sysexlibrarian the to play in the patches into the sub37 and āreadā them from the editor.
It seems the editor doesnāt like any other files then patches within the patch folders (instead of just ignoring them) - crashes
it seems the knobs react only if i click ācapture hardwareā before in some circumstances (even with abs) - if this is the usual behavior, it may make sense to signal the state anywhere (if not yetā¦)
when going through the list of presets over the preset selector (over āpreset nameā) by cursor keys the shown preset changes, but the sound stays the same (no midi send to sub37) - if i use the mouse it works correctly instead - so this might be a small bug.
feature requests:
for me it would be helpful if the current ADRS envelopes are shown graphically (which is a nice feature of plug out editors to me) - but this is just a personal tasteā¦
hope this helps a bit in any way.
Will check AAX64 (Mac PT12.3) on weekendā¦
But far from this - this editor is still one of the best iāve seen (even in this beta state Ć) !
