FINAL 1.0.0/1.2.0: PUBLIC DOWNLOAD FOR INSPECTION

The Moog Forum Moog Beta Forum
1

Hooray ! We have a final 1.0.0/1.2.0.

The release version is 1.0.0rc3, packed as one zip file with the final documentation:

http://www.moogmusic.com/firmware/Sub_37_Editor_v1_0_0.zip

Please:

  • Remove any previous installation, keeping your preferences folder and library presets
  • Download and install
  • Run the firmware updater
  • Load every instance of the plugin and standalone (x86/x64 of VST, AU, AAX, RTAS). Make sure they all load, and that they keep the last used folder location when clicking Save As. This assures the components are indeed the latest ones compiled (1.0.0rc3)
  • Open every doc and make sure it can be read

Please report anything unusual, we’d like to publish asap.

Thanks all for your cooperation.

2

Gil,

On starting editor with Sub 37 on, and then switching Sub 37 off the editor and librarian give no indication of the Sub 37 being off. If I then restart the editor with the Sub 37 off, I get the connect hardware message. Is this the expected behaviour?

Iain

3

HI,

Very great news. This makes my day. Prost

Just a little minor flaw in the “Sub_37_Editor_Users_Manual.pdf” on page 7

The librarian:

The picture there is very old or not really confirm with the Editor.
There you see that there are presets without a category.
Not a big deal, but easy to change this.

Thanks to you all, for the great update..
All went “SM :sunglasses: :sunglasses: TH”
Have a nice day

Regards Luloop.
Screenshot.jpg

4

Hi,
I see that there is a indication when Sub 37 is switch off.
Screenshotu.jpg
regards Luloop

5

Well, ideally it should work like this:

Sub 37 off → Editor On → Couldn’t Connect to the Hardware message → Sub 37 on → connected and controlled both ways
Sub 37 on → Editor On → connected and controlled both ways
Sub 37 on → Editor On → Sub 37 off → Hardware Disconnected notification → Sub 37 on → connected and controlled both ways

We know about an edge case on which the editor won’t reconnect when turning the Sub 37 off and back on, and are investigation it. It doesn’t work perfectly in all cases, but we will check into this again on 1.0.1.

6

Thanks Luloop !

I believe Amos will be able to fine tune the docs on the next update. For now it’s probably be released in its current state.

7

Gil, Amos and team,

thank you for producing a marvellous editor

Iain

8
  1. Manual
  • new manual - whoo-hoo!
  • very nice!

Setup section

  • image - shows editor 0.9.37, fw 1.1.0
  • add a section to talk about local control and DAW ?
    (Ah. I see it later in the Plug-In section.)
    (important point, so repetition is good?)

Preset Library section

  • image shows a preset selected from the Hardware List, not the Preset List
  • image does not show the extra preset folders
  • Share Presets - “opens an email client” Hmm, sort of … not really.
  • can add description of keyboard commands for both folder navigation and HW List up/down

Plug-In

  • p.10, 3rd line from bottom. Some extra spaces.

    \
  1. FW update went fine.

    \
  2. Editor - a few issues for 1.X.Y
  • Sequence Randomize: never affects Skip; all other R/T/RT can get changed
  • would still like the Save Seq to pick up the preset name as a default .seq file name
  • Trash Audio/Alessandro Cortini/Peace.syx is still a “current preset” instead of “edit buffer”
  • Share Preset - controls are chopped off when bottom panel is folded up
  • Share Preset - has “Enjoy !” in the email text; that pesky space-punctuation motif that I hate. :slight_smile:

Looks great!
Thank you!

9

Thanks Amos and Gil for this beautiful work.

10

Installation and first connection seems fine.

But it seems that the editor has problems with some of the new presets in the lib or just spit something out when the mod wheel is raised significantly (not sure if this is wanted):

Orbit Terrarum:

  • Trombone
  • Trumpet

and the problem / “effect” seems to persist with the next choosen presets sometimes until clicking two or three further entries (depending from the presets - so i assume it depends on any parameter which is not reset cleanly when switching to another preset in that runtime case).

hth a bit…

11

There are a few presets in this library in which the mod wheel acts like as volume control. It has been questioned and found to be by design,

Is that what you mean ?

12

Reported the relevant issues. Thanks !

13

Orbit Terrarum:

  • Trombone
  • Trumpet

At first, I thought it was just how those presets were made, but I think there is something else going on.

Drag SH1 and Trombone together to some unused bank slots.
Play Trombone - you need to raise the MW.
Play SH1, it’s OK.

Now leave the MW fully up.
Select Trombone again; nothing plays.
Select SH1; it plays.
Select Trombone; it does not play.
Hold a Trombone note, nudge the MW back down a little bit, and there it is.

So, maybe there is something with the initial state of the MW?

14

Either I don’t understand how things should work (duh!), or maybe there’s a problem.

What I though would happen was that the Global KB Priority setting would take precedence over the Preset’s setting, and that we would have a global control over high-note or low-note playing.

I use the standalone editor, latest 1.0.0 and 1.2.0 releases as of Thursday.

In the Editor, do an Init Preset.
Make sure its Note Priority is set to LAST.
In the Setup Page, set KB Priority to PER PRESET.

Now, play and hold a note, then play some other notes above and below it.
They should all sound.

Now, on the Setup Page, set KB Priority to LOW NOTE.

Repeat the note playing.

When holding a note and playing others above it, the low note sustains, because it’s held down. Good.

When holding a note and playing others below it, nothing new is played; the held note continues. Bad?

A further test:
Hold a note, then add two other notes below it, to make a triad.
The first note is sustained; the pitch doesn’t jump to any of the lower notes.
Release one of the lower two notes that were added.
The pitch jumps down to the other note that was added.

It behaves similarly when the global KB Priority is set to HIGH NOTE on the Setup page, except “things happen” on the high side.

If the global setting is Last Note, then we get Last Note. That’s good!

Here’s a summary table:
(urk = goofy on the low end, eek = goofy on the high end)

KB Priority Settings
Global / Preset / Result

Last / any / Last
Per-Preset / Last / Last
Per-Preset / Low / urk
Per-Preset / High / eek
Low / any / urk
High / any / eek

Playing with the Sub 37 only, disconnected from the computer, powered off then on, a fresh Init Preset from the panel, things work the same way as above.

So… my concept of what should be happening doesn’t match what actually does happen. Where did I go wrong?
Thanks!

15

I tested some older firmware with only the Sub 37, no editor.

1.1.0 is from the zip file from the web site, dated 2015-05-18.
1.1.13 is a fresh download of the old file, contents dated 2015-11-24.
1.1.25 is the latest version that I saved, dated 2016-02-29.
1.2.0 is from the latest Sub_37_Editor_v1_0_0.zip file, 2016-04-13.

KB Priority Settings               Results
Global      Preset     1.1.0   1.1.13   1.1.25   1.2.0
------------------------------------------------------
Low         any        Low      x       x        x
High        any        High     x       x        x
Last        any        Last     Last    Last     Last
Per-Preset  Low        Low      x       x        x
Per-Preset  High       High     x       x        x
Per-Preset  Last       Last     Last    Last     Last

The “x” means a goofy response, as explained in the previous post.

Old FW 1.1.0 works the way I expected it to; FW 1.1.13, 1.1.25 and 1.2.0 do not.

(Edited to add 1.1.13 results.)

16

Strange behavior confirmed for Firmware 1.2.0.
It’s indeed not what I would expect either.

17

Installation of Firmware and Editor worked fine (Mac OS X 10.11.4). Editor and Synth seem to work without major problems. As always I completely delete all Sub 37 Software (Plugins, Editor App) and Settings (~/Library/Application Support/Moog Music Inc./) files.

However, I noted the following after the Firmware update, Hardware power cycle and start of Editor (and allowing download of all HW patches):

  • there was an odd patch in the edit buffer: Slightly altered version of the patch that was selected (before update) with a rather weird duophonic 25 note sequence, I can’t remember to have programmed
  • the Sub 37 still had the same Midi In/Out Channel (Ch 7) settings as before the FW update

Manual reads well, but still would benefit from a PDF Table of Contents.

The Firmware still shows weird behavior if duophonic sequences are played via incoming MIDI instead of by LOCAL.
Please see separate thread: http://forum.moogmusic.com/viewtopic.php?f=20&t=25189

18

Strange behavior confirmed for Firmware 1.2.0.

Thanks for confirming Oli! I thought I was going crazy!

19

First of all: CONGRATULATIONS TO THE RELEASE!

Short question: Is the published version announced yesterday identical to this one, or should we download and install again from the link in tge mail to get the latest and greatest?

20

A checksum of the two zip files shows that they are the same, comparing the release candidate from April 15 with the release from Apr 18. So, I don’t think a reload is required. I was going to reinstall blindly, but now I won’t. Thanks for the reminder to check first!