Just a few remarks from a Mulab newbie...

[fluffy_little_something]

I have played around with that software for about a week now. I really like it, it is so much nicer to work with than my previous, more expensive DAW

Still, one of the things that strike me is the terrible volume to which some patches and samples are set, for instance in the drum patch selection window. Since I work mainly using headphones, it really hurts my ears sometimes. I am sure it is not my computer as I never change the system volume and listen to music on the same phones. I noticed the same issue with some other DAWs as well.

What does Choose Color in the drum module refer to? I don't see any color change...

Maybe I have just not discovered how it works (the docs are like Swiss cheese), but is there no way to easily delete, rename or move patches to another folder? So far I do it in Windows Explorer, where I also have to delete the cache file for every folder in which I change any files. Else there are errors the next time I try to open patches.

A mouse-over explanation of all non self-explanatory items would be fine as well, especially for abbreviations. Some just don't ring a bell with me and I am wondering what they stand for.

Quite a number of presets are pretty useless, but I guess that goes for all DAWs

[fluffy_little_something]

Improvements with regard to undo and redo would be great. I often experiment by adding new modules to patches and when I change something for the worse or accidentally delete the wrong module, undo would come in handy.
Undo and redo would also make sense for comparing a new sound to the previous sound after a parameter change in order to switch back and forth. Alternatively a direct way to compare would be even better, like keeping the o key pressed to play the original patch and releasing the o key to play the modified new sound. Something like that

[janamdo]

. Alternatively a direct way to compare would be even better, like keeping the o key pressed to play the original patch and releasing the o key to play the modified new sound. Something like that

Yes that is good idea..start with the source sound and chance this and compare.
You can make the two sounds in de session MUX if you go deeper in the audio path ( osc-filter-amp-modulations etc )
Toggle between the two sounds in de session MUX

[robenestobenz]

Improvements with regard to undo and redo would be great. I often experiment by adding new modules to patches and when I change something for the worse or accidentally delete the wrong module, undo would come in handy.
Undo and redo would also make sense for comparing a new sound to the previous sound after a parameter change in order to switch back and forth. Alternatively a direct way to compare would be even better, like keeping the o key pressed to play the original patch and releasing the o key to play the modified new sound. Something like that

Agree on this point. Undo/redo is patchy, and also means your workflow gets broken up with dialogs - although I do think having dialogs is the right thing in this case, even if for the wrong reason.

Also agree about the abbreviations. I think most of us can guess ATT, DCY or VOL. FTN though? XPS? Tooltips would be nice, I mean, if we get them for the play button, might as well It's of course all covered in the docs, but the further a user can get without resorting to that, the better IMO.

Also: welcome to the board!

[fluffy_little_something]

Thanks, yes, I am new here

It's not important, but it seems one cannot minimize a window after maximizing it. One has to close it and then open it again.

[> DiGiT <]

its nice to get your initial impressions without bias or at least from a fresh perspective. weve been trying to give suggestions for semantic improvements for a while.

[sl23]

Glad its not just me having trouble with the docs I'm also glad someone else thinks some abbreviations are puzzling.

[MuTools]

Still, one of the things that strike me is the terrible volume to which some patches and samples are set, for instance in the drum patch selection window. Since I work mainly using headphones, it really hurts my ears sometimes. I am sure it is not my computer as I never change the system volume and listen to music on the same phones. I noticed the same issue with some other DAWs as well.

You mean when browsing for a new (drum) sample?

Maybe I have just not discovered how it works (the docs are like Swiss cheese), but is there no way to easily delete, rename or move patches to another folder? So far I do it in Windows Explorer, where I also have to delete the cache file for every folder in which I change any files. Else there are errors the next time I try to open patches.

Indeed that's the way, currently.
May be improved in the future.

Quite a number of presets are pretty useless, but I guess that goes for all DAWs

Feel free to be more specific.
If a majority finds a certain preset useless, it will be removed from the factory lib.

[MuTools]

I'm also glad someone else thinks some abbreviations are puzzling.

Which abbreviations?

Do you also mean the same ones robenestobenz listed i.e. the ones in the MuSampla editor? (FYI: MuSampla is also a part of MuPad and MuDrum)

[sl23]

Yes I mean those ones. But as was mentioned above, a tooltip would solve the problem.

[fluffy_little_something]

Still, one of the things that strike me is the terrible volume to which some patches and samples are set, for instance in the drum patch selection window. Since I work mainly using headphones, it really hurts my ears sometimes. I am sure it is not my computer as I never change the system volume and listen to music on the same phones. I noticed the same issue with some other DAWs as well.

You mean when browsing for a new (drum) sample?

Maybe I have just not discovered how it works (the docs are like Swiss cheese), but is there no way to easily delete, rename or move patches to another folder? So far I do it in Windows Explorer, where I also have to delete the cache file for every folder in which I change any files. Else there are errors the next time I try to open patches.

Indeed that's the way, currently.
May be improved in the future.

Quite a number of presets are pretty useless, but I guess that goes for all DAWs

Feel free to be more specific.
If a majority finds a certain preset useless, it will be removed from the factory lib.

Yes, especially in the new drum sample selection window. Seems they are played at max volume there, as if hitting the center spot of the drum.

I guess it would be way faster for me to list the presets that I can use than those I can't I mean, there are the weirdest patches while standard instruments that have been used in almost any genre for decades, such as the original Rhodes pianos (not the DX7 clones), are not represented. There are no good horn sections, no good strings, etc. One has to create all that from scratch.

Presets is one area where a DAW supplier could distinguish itself from the rest, but most suppliers still seem to think their software is used for electronic music such as House only. I had the same problem with FL, so does my brother who still uses FL. In our view 8X% of presets are only irritating sound gimmicks.

[fluffy_little_something]

I found a great-sounding free synth yesterday, my first external synth I want to use in Mulab. Where am I supposed to save the VST patches I program? Upon clicking on Save, Mulab opens the Mulab folder. Does it matter where I save them as long as I find them again?
I did save a patch in Mulab yesterday, but when I load it the name of the patch does not show up, despite playing the new sound, it just shows the wrong name. Maybe it is a VST issue?

[MuTools]

Where am I supposed to save the VST patches I program? Upon clicking on Save, Mulab opens the Mulab folder. Does it matter where I save them as long as I find them again?

Indeed it doesn't matter as long as you can find them again.

I did save a patch in Mulab yesterday, but when I load it the name of the patch does not show up, despite playing the new sound, it just shows the wrong name. Maybe it is a VST issue?

I guess so. The VST is a black box to MuLab. Which VST are you talking about?

[fluffy_little_something]

OK, good go know.

The VST is called Tal-Elek7ro. I only use it because I can get edgier brass pads out of it, probably because of its 18- and 24-db filter models. It sounds very good for a free VST, nice old-skool skin as well.

[fluffy_little_something]

Is my computer too weak or why can't I put two different instrument patches (for instance piano and pad, used to be quite a common combination) into one rack? As soon as I do, I hear nothing anymore Or do I have to dublicate the entire track associated with the first rack/sound for the second rack/sound?