RELEASE CANDIDATE: 0.9.42 / 1.1.23

Problems again in Reaper.

After recording some automation (Filter Cutoff and Filer Resonance) and play the synth again for 2 or 3 seconds the MIDI button lights for a moment and the Filter Cutoff jumps to 0. If I move the knob and play again the same thing happens again and again. Even with the DAW stopped, I mean, without playing any automation previously recorded.

Thanks in advance.

Editor 0.9.42
FW 1.1.23
OSX 10.11.3

I cleaned the system of the old editor and its preferences and miscellaneous files throughout the system.

Installation was clean, w/o errors.

Before I got the this release, I had already updated the firmware separately, from its own download, so I didn’t completely test the combined fw/sw install. But, the firmware updater in the combined package ran ok, and detected the FW on the Sub 37.

The best part: owners and permissions on the installed files are good! Woo-Hoo! Thank you, thank you, thank you, thank you! I haven’t been this excited since I brought the Sub 37 home last November! (that’s kinda sad, isn’t it?)

Something different: When first run, the Editor used to say that it needed to sync itself with the Sub37. It didn’t do that this time; it did not ask to automatically “get”. A manual “GET” worked ok.

Something fixed: I tried sending a preset without an internet connection – it correctly and quickly sees that there’s no network, and gives a good error message. A most excellent result!!!

Something lingering: However, changing the per-preset mapping can still be missed by 'Save’s.
My tests:

  • turn on Map Per Preset
  • init preset, save as ‘init’, and again as ‘init2’
  • double click ‘init2’
  • set some CV Mapping for it
  • click Save
  • move back to ‘init’ (up arrow in Preset Name), and return to ‘init2’
  • the mapping is gone
  • set it again
  • save it again
  • move back to ‘init’ and return again, and now the mapping shows up

But looking very, very good!

I´m not sure if it has to do with the last firmware update, but I cannot remember to have experienced this before;

When changing fast from a spooky lead preset (Preset vol: 100%) to a fuzz bass preset (Preset vol: 84%, but loader), the fuzz bass volume starts out too soft and takes a few seconds before the first long note builds up to full volume. The spooky lead has about 1 sec Attack on F and A, while the fuzz bass has 0 on both, and multi trig.

EDIT: It might be worth mentioning that I haven´t tried this particular fast (it´s not incredible fast) preset change since firmware 1.1.14.

I´ve tried inserting the Sub 37 as an External instrument (Mono) in Logic Pro X 10.2.1 on a new channel strip where I´ve made a small sequence in piano roll, and then choosing the Sub 37 (Mono) as an Audio FX plugin on the same channel strip, both following the instructions in the Sub37_Plugin_Setup_LPX.pdf. When I choose the Sub37 as an Audio FX, the Editor show up with this message in front; “The Editor cannot connect to the hardware. Please connect your Sub 37 and set MIDI In and Out on Setup page.” (“Continue”)
I´m using USB for MIDI.

When I press Continue, the Editor shows up without Preset choosen.
I choose a preset, but no sound.
I´ve tried changing the Global - Local Control On and Off.

EDIT: I cleared my settings, and made it a new, and got sound, but I still get the same error message both when setting up the Editor first time, and when I close and then Open then same project in Logic.

Firmware updater works perfectly here (none since 1.1.16 have ran correctly on my system).

I am getting an odd thing with knobs moving on their own using the standalone editor

I have Midi Sub37 in/out
and as keyboard controller m-audio keystaation 88

after moving a a know, ie; osc1 octave the knob then moves again.

any ideas ?

Mac 10.9.5

Matt :slight_smile:

I’m not sure what you mean exactly. How is the M-Audio connected ? Does it control the Sub 37 ? What are the steps you are following ? Can you make a video ?

Thank you.

Even with the external controller not connected and only sub37 in out
When setting ie: pitch OSC knob using the mouse it will then jump to another setting.

Basically changing a knob setting in the editor via mouse the setting will change on its own.

Is that clear ?

I got a similar problem with the jumping values in Reaper.

This is part of my answer to Amos:
_In my case is very easy to reproduce the issue:
\

  • Create a track with the Editor
  • Arm the track and set Automation Mode to White, then start recording moving some knobs i.e. Filter Cutoff
  • Stop recording and set Automation Mode to Read/Trim, then play the track from the beginning. You can see how the envelopes move the knobs in the Editor. No problem at all.
  • Stop Reaper. You can play the Sub 37 flawlessly until you move the knob that has been automated before. 2 seconds after moving the knob it jump to a certain value. Sometimes 0, sometimes another value.

    If I remove the Editor the envelopes disappear and I can play the synth without problems._