FINAL VERSION: Editor 0.9.47 / 1.1.25

Hi all !

Please download and install Editor and Firmware latest version, hopefully it’s out last version before release !

Performance in Windows should be improved in this version, let us know how it works for you :wink:

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

If it looks stable enough, we will start general regression on the entire product to confirm it for publishing.

Our goal right now is to make sure this version is totally stable and doesn’t introduce any new major issues, so please report anything unusual.

Thank you all for your amazing job and support during this beta phase !

Gil.

Hi,

Clicking in the middle window from the librarian and sorting the presets. is not really ok.
When a preset name starts with a number followed by a letter, (5TH IN LINE) and the next preset is starting with a number (1970s SciFi Computer), The sorting is not ok in the editor.
Numbers has higher priority as letters…Or?
So when I have a preset with the name: 5TH IN LINE and a preset with the name: 1970s SciFi Computer, the preset with 1970s SciFi Computer should be first in the sorting, course of numbers has higher priority.
funny is that when you click in the Preset name (editor), (where you see all the presets).. There is every thing OK.
OMG…OK my English is to bad…I know…So here two pics of it.

First pictures is how it should be.
Second picture is the one How it is.
ok sort.jpg
wrong sort.jpg
One other post what I post today with the new editor software, version 0.9.46. …got no answer on this one…
What do you think?

Hi,
Very nice presets but not all of them are ok for me.
When I delete them in the editor or move them to an other folder, is working fine.
Closing the editor and then starting editor again, All the presets are all back again.
It would be much better to have the custom Library presets as a separate package.

Regards Luloop

Thanks Luloop,

I will check this out. Anyway for now it won’t block the release.

As for the custom bank behavior, this is the product design, so Amos may be able to answer.

Something odd with my user presets…

It might be due to having previous versions installed, but using this as standalone I’ve a couple of new presets that I’ve not used/sync’d yet with the editor which are showing as Init Preset, although the patch info is there. i.e. the sounds are correct but the name on the hardware Preset panel is ‘Init Preset’.

Capturing the Hardware from changes the name in the top browser panel, but not in the hardware presets panel, which is still ‘Init Preset’

On the attached screen grab you can see the name in the preset browser is LFO FUN, but in the hardware panel patch 13-07 is still ‘Init Patch’. 13-07 is the loaded patch btw.

The synth shows the correct names, and loads the correct sounds from either the editor or the synth itself..

Renaming the patch from the hardware panel has now initialised my patch… duh! shouldn’t have tried that!!

Changing and renaming the patch on the synth then updates the editor.

Thought it was worth mentioning in case the first install of the editor doesn’t capture properly and folks lose patches - but more likely its to do with having previous installed versions. I remember having to clear the folders a while back for similar reasons, but maybe worth a mention in the set-up docs if so.
Screen Shot 2016-03-02 at 21.26.31.png

Thank you so much Gil… I found a way to Customize this “custom bank”
Just make them hidden..but is not the normal way
No need to change this product design…It should be like this. Every software designer put his custom presets in the software…

Dear Amos..

But when the possibility is there in the editor..Moving presets…copying presets…deleting presets..Making new folders for the new custom presets…and so on…
Then it has to work fine..and not when you start the editor again…and all is up site down.

Just want to thank you for this awesome product and We hope it gonna be a splendid success.
I am from Belgium and think a bit different…

Lovely greetings from Luloop

After installing the latest firmware, when I turn the Fine Tune back on the middle position, the C is pitched as a B flat + almost 50cent.
I´ve had this issue in another firmware edition as well, but not sure if I´ve had it every time I´ve upgraded..

I´ve tried turning it off and on again with the Fine Tune set to a minimum when shutting it off or on, but haven´t been able to recreate the issue once more, so maybe it´s just like this the first time booting after firmware upgrade now. Last time I had this experience was on stage, so I had switched the power off once (or more) after firmware updating.

These problems below still exist on my build plus this release added when ableton “flashes” through the automation lanes or automation line stops moving issue ( the issues listed below) then usually the second automation lane changes from what ever parameter i have it set to the default “device on” lane. That didn’t happen on the previous builds.


Ndoe wrote:
I guess i have something I’ve noticed and i might be late to the game but when I use the AU version on my build below the automation works as you would think like other plugins in Live. I touch the knob with the mouse or on the sub 37 and ableton automatically detects what I am adjusting and brings up the current automation lane displayed. When I use the VST version the behavior doesn’t work the same. Live does record the movements if i use the hardware or the mouse but i have to go into the I/O section and find the automation manually. If i use the mouse to select the parameter/ knob on the plugin it will then bring it forward. I am just curious if this is normal behavior or not.

All of the other AU and VST i have operate the same with the mouse or a hardware knob midi synced. Ableton will bring the parameter I am adjusting to the front. It works on my rob papen, NI and others. So the VST sub 37 Editor doesn’t function the same as AU plugin in that manner.

I will post a video to show an example of the two below to help understand what i mean:

I also noticed in both the VST and AU version if i enter in 5 automation lanes in Live i.e ( cutoff, res, mod 2 filter amt) the main channel lanes will flash between the different automation lanes. In the video I have 5 lane of automation and it always seems to rest on resonance automation lane in the past 3 builds.

https://youtu.be/Tmb38Ww_P9A

While doing this test i noticed it i edit the automation while it is playing ableton stops picking up the movements on the synth. It will still record midi cc in the individual clips but it stops picking up automation. Looks like if i draw in 3-5 separate lanes is when it loses “connection” almost every time. I can still use the mouse to draw in envelopes and the sub reacts to it so it is receiving the automation. Mid way through on this video when the automation line jumps i am moving other knobs so it is reading that i am moving other knobs, but the automation line stops moving.

https://youtu.be/bhzV7Uq5o0c

Thanks Ndoe for the detailed report.

I will check into this asap. However I’m not sure we will be able to handle it to version 1.0, it may have to wait for the next update.

Reported.

Request for final version: Ability to resize editor even bigger to fill Apple Cinema display!

Request: In LIbrarian > ‘Hardware Presets’ (in the Right hand section of Librarian): It would be useful to have option to sort presets alphabetically via triangle curser like the curser in the ‘Preset library’ (in the left hand section of the Librarian page).

And this

WOW! 0.9.47 is looking nice!

  • nothing installed in user’s Library/Application Support/Moog Music Inc. at installation = good!
  • but populated when first run = fantastic!!!
  • Devine Presets dump - gone = good
  • Salmagundi/ComputaGames - fixed = good
  • three Factory Presets - still fixed = good
  • CV mapping - still fixed = good
  • hover over setup button - nothing = good
  • seq mod dest lfo phase/duty - not there = good
  • deadly name, no crash = great
  • on and on
  • plus, trimmed leading spaces in Preset Name menu = very good!!
    (or did I miss it from earlier releases?)

  • The Manual = very spiffy looking!

  • some little glitches:
  • the image for the Setup panel shows 0.9.39 and “Disconnected”
  • maybe show a Librarian page with more contents? (which also shows “Hardware Disconnected”)
  • feel free to take words and re-organization from my html version
    (which is why I made it) http://forum.moogmusic.com/viewtopic.php?f=20&t=24837#p152505
  • a better review coming tomorrow (Fri)
  • the README_FIRST.RTF file mentions 0.9.46 (I know, it will get changed…)

The bad:

  • Share Presets - I’ve sent a few, and never received them
  • Librarian … you know.

Seems like your DAW is scanning an older version of the plugin (0.9.39).

The DLL names have changed between versions, so you may have a few Sub 37 files in the VST folder.

How do I use the Editor in Studio One on Mac? I have added an external instrument and assigned it to the S37, as well as added a keyboard device and assigned it to the S37 but no GUI.

I have a Moog folder in my Instruments list but my Minitaur Editor is the only thing in there, no S37. Is the BETA a manual process or something to get it to show up in S1 perhaps?

The standalone works great. Love the presets.

Thanks,
Steve

Hi Gil,
I installed it and had no problems under Win7pro 64bit :smiley:

Greetings,
Marius

Eveything seems to work very well, congratz to you all.

Only thing, i had to enable the wheels and panels in the midi out section to get the editor to respond in live, and enable the keys, panel and wheels on the sub to get it to respond to the physical buttons. makes sense to me, i don’t want the physical unit responding with the latency of the software.
However, your manual seems to suggest almost the opposite method (disabling local control). but that doesn’t work for me.

i amusing Win8 64bit, Live 32bit version, and sending midi note/clock/ editor in and out all via the usb


But the way it’s setup everything is working perfectly, so no complaints there

Two crashes this morning after adding S37 VST in Studio One 3.2 on Mac 10.11.3

Both crashes occurred while only having Minitaur and Sub 37 VST2 instrument tracks loaded. I was able to record a few notes on each lane and the app just closed without warning.

Crash logs attached
S1 Crash 2016-03-05a.zip (25 KB)
S1 Crash 2016-03-05b.zip (22.8 KB)

Thanks for the report.

  1. Does the crash happen all the time and is there a reproducible scenario we can use ?
  2. Can you attach the crashing Studio One session please ?
  3. Does it crash on a different though using a similar scenario ?
  4. Are you using latest 1.1.25 firmware ?

I decided to give the S37 Editor a fair shake and NOT include the Minitaur in this test. The Minitaur as it seems, is the issue with the crashing, but I’ll have to put that in as a possible bug for Minitaur.

As for Sub 37, the VST seems to be solid, but I have noticed an issue with automation.

Please review link to video to demonstrate

https://youtu.be/GE70nz59UsQ