RELEASE CANDIDATE: 0.9.40 / 1.1.20

The Moog Forum Moog Beta Forum
1

Hi all !

We have a release candidate ready as 0.9.40 and 1.1.20.

Download from here -

Windows: http://www.moogconnect.net/downloads/sub37/Moog_Sub_37_Editor-0.9.40-WINDOWS.zip
OSX: http://www.moogconnect.net/downloads/sub37/Moog_Sub_37_Editor-0.9.40-OSX.zip

Firmware is still 1.1.20:
http://www.moogconnect.net/downloads/sub37/Sub_37_Firmware_v1_1_20.zip

Fixed in 0.9.40:

  • Fix for recalling mapping and map per preset
  • Fix #321 Certain preset cannot be copied to a custom folder although its name is valid
  • Fix #512 Renaming preset from the top menu doesn’t work
  • Fix #508 VST plugin’s window in cubase cannot be resized
  • add support to sysex notification for Program change by 3rd party
  • Fix #507 Window inside a window appears in Cubase when loading a saved project
  • Workaround for VST setParameter loop in Ableton
  • Fix #503: Empty pop up + app hangs on OSX
  • Fix weird sending of set CC mapping when boot

The intention is being able to release the Editor by the end of next week, which means it’s very much important for us to have your feedback regarding this version.

Please install, check and report stability, automation, DAW compatibility, connection performance, preset system issues and anything else that you find important enough.

Whatever is not critical level will be delayed to the updates made after first version is released.

Thank you all for your great job and contribution !

2

Thanks!

No issues so far. Every FW update has worked perfectly for me Macbook 5,1 (late 2008) OS X 10.9.5.

Hoping to spend some more time with the editor this weekend!

3

Hi Gil,

installed and so far everything is OK.
Cheers Glyn.

4

For convenience I have re-packed all the latest files with documentation in one download:

http://www.moogconnect.net/downloads/sub37/Sub_37_Editor_Pre-Release_v0_9_40.zip

This is mostly for the convenience of new testers, so they can get all the documentation… editor and firmware files are same as in the individual links above.

Cheers,

Amos

5

Hi,

I would like to know if this is the normal behavior in Reaper.

After making some automation the MIDI button stays red all the time and the Sub 37 front panel doesn’t work. Even if I disarm all the tracks. If I want to use the Sub 37 panel again I have to bypass the Editor, then the MIDI button turns off. Is this OK?

Thanks in advance.

6

I was getting the same behavior last night but i am in ableton on the build listed in my signature. I thought is was a midi loop on my end but I couldn’t find it in the settings

7

Thanks for the answer but the weird thing is that if it were a MIDI loop when I disarm all tracks it should stop but it is not the case.

8

not true, if it’s a MIDI loop between Editor and Sub 37 directly. The DAW wouldn’t have anything to do with that.
Looking into this ASAP. Can one of you run MIDI Monitor to see what messages are flying back and forth?

thanks!

9

That was something that I did too. I put two instances of a MIDI Monitor VST before and after the Editor and none MIDI messages were detected.

10

Nope, totally not normal or expected. I’m testing this now; thanks for the report!

11

Hi Amos,

I forgot to mention that even with the Editor bypassed (MIDI led off) if I move some knobs in the Sub 37 the Editor GUI responses to these movements.

Thanks in advance.

12

Hi Gil and Amos,
installation went fine under OS X 10.11.3. Standalone and vst Plugin are working (tested with ableton live 9.6). Also the patch renaming works. No probs with automation.

I just played around with the “Rhythmic 5th filtration”. there I noticed that the editor doesnt show the changing lights of the filter slope correctly. It just stands still.

Greetings,
Goat

13

Thanks.

I have just checked here and it does change as should. Are you using firmware 1.1.20 ?

Is it possible that you changed the preset at some point ? Can you set everything to default and check again ?

14

Hi,

This should be fixed in 0.9.42. Will you be able to confirm please ?

Thanks !

15

I got another problem in Reaper with the latest version. I sent a PM to Amos about it.

Thanks Gil.

16

Thanks. What is the other issue you’re having ?

I am refering to the following report:

“After making some automation the MIDI button stays red all the time and the Sub 37 front panel doesn’t work. Even if I disarm all the tracks. If I want to use the Sub 37 panel again I have to bypass the Editor, then the MIDI button turns off.”
Thanks for checking.

17

Hi Gil,

The other is the jumping values explained here:

http://forum.moogmusic.com/viewtopic.php?f=20&t=24822&start=15#p152607

Thanks in advance

18

Sure,

But is the Midi RED light issue fixed for you ?

19

Yes. The MIDI let issue is solved. Thanks

20

Thank you !