-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MU4 Task] Automation UI implementation #19490
Comments
Wow this is a great concept. Perhaps eventually, things that can capitalize on this UI design and grant full control over playback:
While a piano roll wouldn't be ready for implementation now, these would grant similar capabilities before that is ready without having to worry about the UI and editor complications. This could really eliminate the need for a piano roll while it may still be handy later on as a bonus. Edit: I've been alerted that one of the main reasons the PRE is not currently in development is because of the desire to avoid having to use these which are deemed not sufficiently flexible enough to implement and subsequently not worth adding to the codebase / maintaining. Understood. If any similar temporary measures can be instated sooner to affect finer note position/ where the attack starts and note duration separate from the notation conveniently that would be amazing. Otherwise looking forward to the playback engine improvements in MU5 or later.
Seeing that this is now marked ready for development I just wanted to bring these to attention before development was fully underway, in case these could be taken into account before possible road-blocks may come up in implementation once it's partially built. |
When can we expect this to be released. In 4.6? I'd like to be able to used other VSTs I bought outside of the paid muse sounds I got. |
Task description
This is the first implementation task to introduce Automation in MuseScore 4. Users should be able to:
A later task will handle drawing the default Dynamics (for MuseSounds) and Velocity (VSTs, Soundfounts) curves based on the dynamics in the score.
The text was updated successfully, but these errors were encountered: