Requesting features for Musescore 2.1
Congratulations to the Musescore team! A lot of work and many improvements in this new version since 2.0.3. For such a small group of developers this is really an achievement! Musescore, as a notation software has already reached professional standards and is in par with Sibelius or Finale. Actually with some playback improvements, Musescore will be a replacement for its expensive counterparts. I really, really love Musescore.
Now I have a small request :) Is it possible the playback features described in the video of this post: https://musescore.org/en/user/527826/blog/2016/08/02/screencast-soundba… to be implemented in let's say, version 2.1.1 (even as experimental features), or I will have to wait for version 3.0. I'm interested in single note crescendo/decrescendo (which is obviously a very difficult task) and the port/midi_channel number assignment in the Mixer window (very useful if I want to connect Musescore with external samplers through Jack).
Thank you in advance!
Comments
No, unfortunately that's not possible. It would break the compatibility with 2.X.
In reply to No, unfortunately that's not by [DELETED] 5
Ah I see! Thank you Nicolas for your immediate reply...
There are some playback issues (besides the above) which in my opinion, could be solved with a more general approach to the design of the Mixer (and Musescore in general) if compatibility with 2.x were not a concern (*) e.g
a. There is no need to always allocate multiple midi channels for piz, arco, muted e.t.c for strings and trumpets, but only when this is necessary.
b. The piano staff could allocate 2 midi channels if needed, so we could have simultaneously different Dynamics for treble/bass e.g. mf on the treble and pp on the bass.
c. What is happening now, (unless I'm doing something wrong) each time I make an instrument change on the same staff a new midi channel is created even if I want to select one of the previous instruments already present.
I'm not a developer, and I haven't a clue about the difficulty of implementing the above features, just throwing in some practical ideas... hopefully implemented at the next version 3.0 I strongly believe that version 3.0 must be redesigned from scratch, no mater how time it will take for this
Thank you again
(*) PS: For compatibility with 2.x one could for example, export his current work in musicXML format and subsequently import it to the new Musescore (version 3.0) without loss of information (?)
In reply to Ah I see! Thank you Nicolas by vasmakk
3.0, once ready, will import 2.x scores directly, without the need to go via MusixXML.
Same like 2.x does import 1.x scores.
Just on the way down you need to go via MusicXML.
In reply to 3.0, once ready, will import by Jojo-Schmitz
This is even better !!
Thanks
In reply to Ah I see! Thank you Nicolas by vasmakk
As for (b). You can already do this.
Add a dynamic marking to a note of the relevant staff; then use the inspector to alter the range it applies to (staff/part)
In reply to As for (b). You can already by jeetee
Cool. I'll give it a try when I find some time.
Thanks!
On the other hand (a) and (c) might be related you know. arco pizz tremolo muted etc could be implemented as Instrument Changes on the same staff...