OLD PRESETS - Beta Team ??

Hi
new firmware 1.2.0 and editor Beta 1.0.0
in the librarian section, I noticed a folder called BETA TEAM with 9 sub folders with 2 letters (AG / DS / … / TT)
When I look into them on their Windows folder location, there’s a lot of presets (sysex)
but I can’t see and load it in the editor.

Is there old versions of presets that cannot work on the new firmware ?
Is it possible to fix that ??

It is possible that -some- presets made with older versions of the Editor and/or Firmware won’t load. But it’s less likely that -all- of them won’t load… Where are these folders located ? They should all be under the Preset Library folder for the Librarian to see them:

C:\Users<username>\AppData\Roaming\Moog Music Inc\Sub 37\Presets Library

If they still do not load, will you try using the older version used to make them and see if they load ?

Or you can attached the entire folder structure as one zip file and I’ll check it here locally.

P.S

Are they all your custom made presets ? I don’t recall us providing this list of presets.

Thanks.

Where are these folders located ? They should all be under the Preset Library folder for the Librarian to see them:
C:\Users<username>\AppData\Roaming\Moog Music Inc\Sub 37\Presets Library

yes, they are located in the presets library folder.
These folders appeared when I did an old update of the firmware 1.1.16 or 19

If they still doesn’t load, will you try using the older Editor used to make them and see if they load ?

I tried all the editor versions that I have (0.29 to 1.0) and no preset loaded…
you can download them here https://dl.dropboxusercontent.com/u/983402/Beta%20Team.zip

P.S
Are they all your custom made presets ? I don’t recall us providing this list of presets.

nop, not mine.

Well, I can’t import them into the Sub 37 Editor, but I -can- import them into the Sub Phatty Editor, which I believe is the one to which they belong :wink:

haha, sorry for disturbance… I don’t know how I get those presets… never had a sub-phatty

at least, I can inform you that all is working good for me with new release
used a lot with ableton live 9 and it works perfectly.

good job

Thanks, keep reporting anything unusual !

:wink:

(sorry to bother with that but I have a big trouble with driver for MP201 :
http://forum.moogmusic.com/viewtopic.php?f=10&t=25266
would you send me the last working MP201 drivers for win7 if you have that ?? )

Hi,

I have read your MP201 thread.

On you PC - are there any moog drivers installed ? which and of what version ?

Are any of the beta 2.23.0/3.30.0 version preset on your system ?

yes
the installed driver is 3.30.0.0
firmware of MP201 is 2.1
here are the details

ok lets do a small experiment:

  1. Unplug the Sub 37 and MP201
  2. In Add/Remove programs, unintall 3.30.0 completely
  3. Under Windows\System 32\drivers, please delete any files which carry the name “moog” in them
  4. Restart
  5. Plug only your MP201, and run the latest firmware updater:
    http://www.moogmusic.com/downloads?category=All&product=117
  6. Follow the insructions provided

My assumption is that it will now work for you.

Now please:

  1. Unplug the MP201
  2. Install 2.23.0 (provided with the 1.0.0rc3 zip file):
    http://www.moogconnect.net/downloads/sub37/Sub_37_Editor_Pre-Release_v1_0_0_-_30Mar2016.zip
  3. Restart
  4. Plug and try to update your MP201 again (even if already updated).

Do you see the same problem you had in the first place ?

Please let me know.

Thanks.

ok
it took time to experiment but it works great now !!! :smiley:
I can pilot all my gear (sub37, slim and mp201) by USB.

You’re a master !! thank you very much.

(I put your recipy in the controller forum, it could be useful for others)

Wait a minute. Did you also try the second scenario ?

i.e

2.23.0 installed -and- you are able to run and install the MP201 update ?

We must verify it work also when the new driver is preset in the system.

Yes , I made the 10 steps
Install the moog sub37 Usb driver
And then made the update of mp201 again

Great news.

Glad it works for you now. Thanks!

Thanks to you

This can be a little sensitive actually, as some components (such as drivers) are still confidential. To remind, we also test integration between various components, some of them are in production and other are being developed, so issues you may encounter may not happen to non-beta users. But you can surely note that cleaning out older drivers and reinstalling them has solved your issue :wink:

Thanks !