A bunch of feature requests

[Hanz Meyzer]

Here a little collection of feature requests. Using macOS version.

- Saving reg info in the normal user library dir, instead in the app dir. So the reg info won't be deleted on every update. At least for MUX.

- Shortcut to the user dir on the very top of the file selector. Maybe an additional user's desktop shortcut, too.

- Support for OS' directory/filename translations, which are stored in meta files in macOS. So the "users" dir would appear as "Benutzer" dir in german localisation. ( AND also correctly sorted )

- A real multi band split module, which provides multiple crossover filter curves, one linear phase one, and some zero latency ones.

- Saving MUX and Mulab presets into one user library / documents dir instead, not within the VST dir structure. Changing the updater system.

- Basic support for macOS color file tags: Displaying it in the file browser, preserving it on overwrite, maybe support for context menu to set the color tag.

[MuTools]

- Saving reg info in the normal user library dir, instead in the app dir. So the reg info won't be deleted on every update. At least for MUX.

With reg info i assume you mean your user key, right?
Well the user key is stored in MUX folder/User/Settings/MainSetup.txt
So if you simply update the .Vst files the user key is preserved.
And if you do a full update and copy over your User folder (cfr this doc page), the user key is preserved too.

Shortcut to the user dir on the very top of the file selector.

It's there: Favorites button -> User Library.

Saving MUX and Mulab presets into one user library / documents dir instead, not within the VST dir structure. Changing the updater system.

If you follow the above update steps, there is no issue as your user lib will be preserved too.
That said you also have the option to indicate another user lib folder location:
main menu -> Preferences -> User Library Folder

[Hanz Meyzer]

Thanks.

[zippybungle]

chord generator like codefn42 cales and chordz

[MuTools]

Already in MUX: The Note Mapper module.



Docs: http://www.mutools.com/info/docs/mux/mu ... dules.html

[antoniaz]

Let me propose some additional ideas:

1) option to automatically take the current system device in the Audio Setup dialog (I find this very helpful on Mac when using GarageBand); I quite frequently switch between different audio setups...

2) project-level tempo variation (BPM) also by graphical curve in addition to the tabular format

3) non destructive MIDI quantization

4) visual feedback during active recording

5) public format for an entire instrument importing into MultiSampla (whatever, but openly specified); even better, an import function from common formats like SF2 or SFZ

6) notepad to keep some custom text for each project

[zippybungle]

thanks very much

[Hanz Meyzer]

Hi,

I would like to add another request:


- Make the mulab sequencer modular itself, so it is a midi/audio input module and can be used within MUX VST! So you could use it e.g. as sampler track in your DAW, syncing to the host DAW. Or as MIDI track...

[bibz1st]

Have you tried the Sequence player/ Step Sequencer

[Hanz Meyzer]

Have you tried the Sequence player/ Step Sequencer

No no I mean a full audio track, just like in Mulab, available as audio in module, syncable to host song position. And same with a midi track.

Ok, but this is maybe way too much effort.

[heks]

Are you meaning something like Fl studio vsti?

[pljones]

In the modular area, you have Audio, MIDI and Modulation In and Out points both in MuLab and in MUX VST. In MuLab, in "other" you also have "Audio File Recorder". That's not present in MUX. MuLab also (not modular yet...) has an event Sequence recorder. Both of these create content that appears in a MuLab Part (concept does not exist in MUX), which gets arranged onto Tracks (concept does not exist in MUX) in the Composer (concept does not exist in MUX).

Given that MUX doesn't have a composer (because it's not a DAW - that's what MuLab is), I'm not sure what creating Sequence or Audio Parts would get you? You wouldn't be able to use them in the host you had MUX hosted in, as they're MuTools-specific concepts, not part of the VST world. What are you trying to do in broader terms?