Look-ahead to MuseScore 4.2

• Aug 31, 2023 - 11:44

Hi everyone!

Here's a quick update about some of the things we are working on as we prepare for the release of MuseScore 4.2 later this year

Alternate string tunings for guitar

We’re working on a new ‘string tuning’ element, which will be accessible via the Guitar palette. This will provide an easy way to specify new tunings for multiple strings and (optionally) have those tunings displayed in the score. You’ll be able to choose from a list of preset tunings or enter an entirely custom tuning. Tunings can be added to any measure in the score, and will take effect from that point onwards in terms of tablature fingerings and pitch range warnings (red notes).

guitar_alternate_string_tuning.png

Parts

We’re working on a much smarter system for handling the synchronisation of elements between parts and the main score. By default, elements and their properties will be synchronised between the score and all parts. However, you will be able to turn off synchronisation for specific properties on individual elements where you would like those properties to be different between the main score and the parts. Improving this functionality is going to make a huge difference to ensemble and orchestral scores made with MuseScore, and we’ll be really keen for testing and feedback on this feature in particular, when it’s ready.

Dynamics

We're adding the ability to apply dynamics to specific voices, so you could have Voice 1 mezzo-forte while Voice 2 is piano, for example, and you'll hear that effect during playback. We're also working on an option to vertically centre dynamics between the two staves of a grand staff.

dynamics_voices_grand_stave.png

Performance

4.2 will also bring some welcome improvements to performance, particularly in the area of audio generation. Our current tests show MP3 rendering is at worst unchanged, and at best up to 10 times faster than before, depending on the score. These speed improvements also benefit cloud saving and publishing to MuseScore.com and Audio.com.

Share on Audio.com

MuseScore 4.1 introduced the ability to upload score audio to the free streaming site Audio.com, a new platform under the Muse umbrella that's closely associated with Audacity, MuseScore's sister application. In MuseScore 4.2 we plan to improve Audio.com sharing by providing an option to update existing audio in-place rather than uploading as a new file each time.

share_audiocom.png

Team

We're delighted to welcome Zac Jansheski to the MuseScore desktop team. Zac has worked at Muse for several years now, but he recently joined the MuseScore team as a Quality Assurance Engineer. If you’ve taken a peek at our GitHub repo lately you’ve probably noticed an increasing raft of concise and carefully crafted issues with his name on them! Luckily for us, Zac is also an expert percussionist, and he’ll be helping with the major percussion overhaul we have planned for later in the 4.x series.

Get involved!

Please see our previous announcement for ways you can help out, including documentation and translations. If you're a developer, don't forget to take a look at the Community Projects board.

Also, today (August 31st 2023) is your last chance to Vote for MuseScore in the UX Design Awards! If you haven't voted yet, please consider doing so now.


Comments

It sounds very promising. Thanks for your hard work.

I am wondering when the pianoroll will be reintroduced, and when the "DAW arrangement view" will come (the game-changer feature of MS4), along automation and MIDI mapping. Maybe it has been abandoned?

In reply to by creal

According to the developers, MuseScore 4.2 takes at least five months to develop. Therefore, if alpha comes out first as early as the end of October and beta tests are released in late November or early December, and there is no problem, the official release at the end of December is most likely. So I've made a rough road map with this. 4.3 will be released in 2024, but no specific release schedule has been released yet.

In reply to by chaejunsu0902

Thank you. But at the end, that does not answer my question. We don't know if the pianoroll will be reintroduced in 4.3 or if the arrangement view/automation will be in 4.3, 4.4, or even MS5. Maybe it's not even in the pipes anymore.

Maybe we cannot have more info, and that will answer my question

> ... a new ‘string tuning’ element ... will provide an easy way to specify new tunings for multiple strings and (optionally) have those tunings displayed in the score. You’ll be able to choose from a list of preset tunings or enter an entirely custom tuning.

Really nice that MS4.2 will simplify the matter of designating altered tunings for stringed instrument.

A couple of questions:

• Once a user has defined a custom tuning can they save that as a "preset" that's easily accessed in other scores? And will it be possible to export and share a list of such custom presets?

• I'm curious, what's the purpose of the show/hide icons?

scorster

In reply to by Jm6stringer

If I follow the logic then, by showing the 6th string (of Drop D tuning) the reader sees the the string that has been altered from standard tuning. Alternately, the user could show the full tuning by Showing each string.

I'd also like a parallel option where MuseScore displays string pitches (in a mono spaced font) to the left of the initial tablature staff, or optionally at the left of every tablature staff. See the attached images.

Scorster

In reply to by yonah_ag

For me the note letter would be sufficient without the octave number.

I agree.
Most guitarists who employ alternate tunings develop a "feel" for the "correct" octave number. If they get it wrong, they learn quickly. (Try cranking a string up a whole octave by mistake. See what happens... :-)

On the other hand...
For the "Edit String Data" dialog, octave numbers are needed because the same dialog is used for different stringed instruments. Also, it makes it easy to discern re-entrant tunings: e.g., for 5-string banjo.

In reply to by yonah_ag

yonah_ag write > For me the note letter would be sufficient without the octave number.

Yes, simple class letters would suffice. Even as I made the graphic I found the octave number unattractive and I felt it divert my attention from the pitch class.

And the octave numbering is knowable in the capo element dialog.

scorster

Hope you will improve the channel mixer with the ability to chose and play instruments in other sound fonts for the main instruments and for the chords … thx

In reply to by Marc Sabatella

Thanks Marc for your feedback
In fact I had done that already but found that it is not working for the chords on top of the score which are now shown differently in the new mixer.
Hope 4.2 will also cover the sound selection for these chords. I ma using them quite a lot !

In reply to by philippe888

They are shown different indeed but it absolutely works to select a new sound the way I described. If you have a score you are having trouble getting to sound the way you want, just ask for help in the Support forum and attach the score, and we’re happy to help!

for film work, I DESPERATELY need , and I'm sure a lot of other film composers also need, the possibility to MIDI SYNC Muse Score with a DAW .
This could be via another program or utility like the IAC bus in Mac OS for example, or Jack Audio , midi pipe etc.
For that there needs to be a Midi Sync page within Muse Score that can send and receive sync and midi transport control information.
After that, a routable midi out and in for each instrument would be amazing- then one could transfer instantly midi tracks between Muse Score and the DAW.

I would like to try the smarter system for handling the synchronisation of elements between parts and the main score. But where can I find it? And how does it work?
As for dynamics per voice, it's very welcome. However we also need the ability of creating custom dynamics with custom volume changes. Sometimes we need more subtle dynamics, something between and mf and f, or f and ff, like a real musician can do.

Do you still have an unanswered question? Please log in first to post your question.