Hi Folks,
is there an Editor/VST for the Moog Muse?
I do miss the ability to control the Muse remotely like I can do with other synths and I’m hopeful that we will get a proper patch editor with full MIDI control functionality eventually.
Best!
In Cubase I created a Midi Device. Now I can assign my Muse as an instrument.
Waiting patiently over here too. Really, I almost want a librarian as much as I want an editor. The manual labor of arranging patches at the moment is kind of a drag, but not that big of a deal.
Hello Pouvez-vous avoir la gentillesse de me dire comment vous faites pour créer in instrument midi dans Cubase?
Je viens de recevoir mon nouveau Muse et je n’arrive pas à le connecter en midi à Cubase!.. : 
Merci à tous!
Hello Can you please tell me how to create a midi instrument in Cubase? I just received my new Muse and I can’t connect it in midi to Cubase!.. ::?: Thank you all!
the Moog community forums and user groups are valuable resources for sharing experiences and potential third-party solutions.
+1 on an Editor/Librarian.
Not only for managing the patch library,
but also, an editor is a nice way to be able to easily look at how
patches designed by others are put together.
The flagship synth really deserves an editor.
The Subsequent 37 editor is great.
any news about and editor/librarian for the MUSE? thanks
A fellow Moog Muse user has been working on one. Unofficial.
Hi
I write librarians for different keyboards, and I am thinking of doing one for the Muse as it’s patch management is pretty arcane.
I will probably end up doing one anyway, but if there is interest in it by others, then it might bump it up on the priority list.
I do not write editors, as of course the reason why I have gone for a “knobby synth” is that front panel experience.
3 Likes
It lets you visually Geometry Dash Lite document and recall your patches without needing paper templates or taking photos.
Hi there, I’m waiting for a preset manager & librarian also for some time now.
At least a preset manager that could operate without having to be in disc mode, so you could drag & drop from the computer batch of presets, listen to them and create on a mirror bank on the computer a kind of best of of existing presets / user one … and then replace the memory with your own selection. I have this experience with the ASM Hydrasynth preset manager and it’s really a nice way of doing this. It could be also a bigger preset memory (512 /1024 slots) that could help. You’ll only need a way to organise the 16 banks of 16 presets (maybe a A/B/C/D menu to choose the different 256 slots).
Hope they’ll do something about this as for now I feel like it’s really a waste of time and energy to dive in the presets and organise them as it is.
1 Like
I ma seriously thinking of it as a Christmas project, but I do not think that the Muse has a SYSEX implementation unless somebody knows otherwise? At least I have been hunting the internet for info and I have not found any info
So it may be starting off with an editor that can read the disk mode folder structure into the editor, so disk mode would still need to be used.
1 Like
UPDATE: I have raised a support ticket with Muse to ask if they support SYSEX.
If they do not, it will needed to be file based only
Thanks for your answer Derek.
I get the point even of I’m not a technical person. The Sysex question is a good point to ask Moog. Thanks
SYSEX = SYSTEM EXCLUSIVE. This is a class of MIDI messages for synthesizer specific data such as patch transfer
Most if not all synths support SYSEX as a means of transferring patch data, but the MIDI Section of the Moog Muse Manual makes no mention of it, and I can find no reference to it at all on the internet.
Well, my support ticket was replied to today, and it has confirmed that there is no SYSEX mode in the Muse MIDI implementation, which I suspected given it was not documented in the manual.
I have asked for it to be considered, but I will start with reading/writing the disk mode folder structure.
Hi Derek, thanks for your feedback.
So now at least we know that SYSEX is out of the equation for the moment. Thanks for sharing your points & progress on this thread.
1 Like
No worries.
I must say that the Muse is the first MIDI equipped synth I have owned that does not support SYSEX, which is very surprising and especially so at its flagship synth price point. I do hope that Moog come to realise how limiting that omission is in terms of patch management, especially on such a fantastic synth, and add it.
E.g. my librarians for other synths can of course operate on files (either native synth disk formats or captured SYSEX) or direct with the synth via MIDI SYSEX. I can build a single database of patches, tag, sort and filter that database and fire a selected patch over the synth edit buffer to audition without saving.
This is the first librarian that will need to operate on a file tree as opposed to a file, and just looking at Moog and the commercial libraries I have brought, they do not follow a consistent file tree structure in where the folder the tree starts
E.g.
Factory Patches/library/bank01/patch01/vox humana.mmp
Launch Expansion/library/bank01/patch01/stargazing.mmp
Is nice and consistent, but the following are different in tree structure, albeit you always end up at an MPP file as the “leaf” node at the end.
Limbic_Bits_MOOG_Muse_LUNA/Presets/bank13/patch01/titan pad.mmp
Luftrum32-MoogMuse/Patches/bank13/patch01/brume.mmp
So I will need to account for that, but all doable. I think it might be based on creating my own .muse file format and having an Import/Export Muse Disk Mode file tree option, which will be designed to parse packages with slightly different tree start points, recursively looking for mmp and mmseq files and noting the file structure it needs to recreate on export (including number/name of banks if they are not all there) to be compatible with the original file (easier for my testing).
My hope is that once I support the disk mode structure, Moog will see the value of what is being done and add SYSEX so I can expand further. I may also see if we can start a vote on it over here as a separate topic.
BTW, my librarians are Java based, so support by default: Windows, Mac OS and Linux as packaged applications, or as an unpackaged application any OS capable of supporting the minimum Java run time (currently J17).
If you want a nose about my current suite librarians, take a look at
I will be parking the work I am doing on montage.factory updates for Montage M to do this Muse work as a side project over Christmas (when I have a few weeks off to have a good run at getting something going), and I also have plans to do one for the Hydrasynth next year as I am not a fan of their librarian and I have accumulated so many Hydrasynth patches I want them in a database!