Musescore 4 feature requests
So, after having done some testing with the musescore 4 builds here are a list of features that I would like if possible added in the future. This would encourage me to perhaps even skip out on using a DAW entirely.
-VST/VSTi support if at all possible for non VST3 type plugins. (or if someone can point me in a direction to a VST3 player for vst2 plugins)
-GUI options for Muse Sounds, I'd like to be able to finely control playback for every note. For instance on strings, I'd like to be able to control vibrato, expression, etc like you would in a regular vst.
-Instrument selection for Muse Basic
-Automation (I know this is coming eventually but I would really want to highlight that being able to use the CC from VSTs will be super important)
-A separate 'midi' view which functions like an actual DAW and makes things like working with automation and mixing easier to work with.
-Support for adding tracks on the midi view which can include .wav files so that I can include effects. The ability to add tracks that do not show in the notation editor section
-An option to specify which folders to look for for vsts in the preferences section.
-Options to include standalone vsts which operate via .dlls.
-support for other audio drivers like ASIO. Additional options for playback sample format, sample rate, etc.
-Ability to make sends, and buss tracks
-A button to hear the mix in mono
-Lots more Audio settings for buffering, here's some examples with what I can change in REAPER:
-Lots more render settings when rendering as an audio file:
Overall though musescore 4 is great and I'm super excited!
Attachment | Size |
---|---|
image_2022-11-19_162809450.png | 94.11 KB |
image_2022-11-19_163109875.png | 75.94 KB |
Comments
Sure, but these need to bet entered in the GitHub issue tracker.
In reply to Sure, but these need to bet… by bobjp
would these count as issues? if so I can add them, I had thought they were more of a 'want to have' kind of thing but when I have time I can.
In reply to would these count as issues?… by mnmwert
In general, requests can be added to GitHub once they are fleshed out here. I'd wait until MuseScore 4 actually releases, and until there is some consensus reached here of how the features should look. Then it could make sense to open issues on GitHub - we'll see what process is announced at that time (still unclear). I do know it will only make sense to do one request per issue, and really, it's better to do that here as well. But we'll see what kind of discussion this post generates. Might make sense to separate something out later if it gets too hard to follow.
In reply to IN general, requests can be… by Marc Sabatella
Yes, my mistake.
I know that aspects of a DAW will be incorporated into MU4. Which is fine as long as they don't get in the way of the fact that this is notation software first and foremost. Just my opinion, of course. Composing is a hobby for me, so I don't need too much stuff getting in my way. Of course there are many who take it more seriously. That's fine. And not that playback isn't important to me. It is. I write for videos and live stage productions. Small scale, to be sure. I go back and forth on liking MU4 or not. Some parts of playback are great, and some are not. We'll have to wait ant see.