MuseScore Studio 4.4.2 is now available!

• Sep 12, 2024 - 14:49

Hi everyone,

We're pleased to announce that MuseScore Studio 4.4.2 is now available. This update addresses stability issues, fixes a problem with MuseScore Studio's online functionality, improves playback quality especially on less powerful computers, and includes several other enhancements and fixes in various areas.

Online functionality & MuseScore.com

  • Some users reported that MuseScore Studio 4.4 was unable to connect to the internet and that they could not log in to their MuseScore.com and Audio.com accounts. This has been resolved.
  • This update includes changes that facilitate a fix for the "Send to YouTube" feature on MuseScore.com.

Stability improvements

  • A crash has been fixed that occurred when opening a score containing a rest beamed together with the next two notes
  • A crash and a corruption that occurred when changing the actual length of a measure have been fixed
  • A crash when hiding staves with lyrics has been fixed
  • A crash when closing a score under specific circumstances has been solved
  • A problem that caused all parts of the UI to be detached from the main window, sometimes resulting in crashes upon further interaction, is now prevented

Engraving and score interaction fixes

  • You can now drag multiple hairpins at the same time to move them around
  • Dynamics can now smoothly be dragged across barlines again
  • Dragging dynamics or expression text no longer affects adjoining hairpins when snapping has been turned off
  • Vertical centering of dynamics no longer interferes with harp pedal diagrams
  • Layout issues related to the 'Combine with voices that share the same stem direction' property have been fixed
  • Repositioning images by dragging them with the mouse works again
  • Joining measures no longer causes certain elements to be shifted or lost
  • Undoing after joining measures no longer results in unexpected behaviour
  • Beams no longer (dis)appear unexpectedly under specific circumstances in continuous view
  • No unexpectedly large brackets/braces appear anymore when deleting staves under certain circumstances

Playback fixes & improvements

  • The audio engine has been further tweaked, improving performance on all devices but especially on less powerful hardware (note: to get the most out of this, you need the latest version of MuseSampler, which is the engine behind Muse Sounds. To receive the latest version, close MuseScore Studio and then open Muse Hub, which will install the update in the background.)
  • Pedal playback for VST has been fixed
  • An issue involving tempo markings and measures with a reduced duration has been fixed
  • Metronome markings containing 'c.' (in the meaning of 'circa') after the '=' sign are now also accepted; thanks @pacebes for your contribution!
  • Preview playback of chord symbols just after entering them is back again
  • You'll hear no more unexpected portamento effects when clicking on notes to preview their sound
  • In MuseScore Studio 4.4, the 'Solo' button for the metronome track was intentionally removed. However, for existing scores where the metronome track was already solo'ed, this meant that it couldn't be unsolo'ed again, leaving all other channels stuck in silence. In MuseScore Studio 4.4.2, such scores are now automatically fixed.

Miscellaneous fixes

  • Chord symbols are now exported to MIDI again
  • The state of the Loop button in the playback panel correctly updates again when opening a different score
  • When running the AppImage on Linux, the app name and icon are correctly recognised again
  • In the Properties panel for fretboard diagrams, hovering the preview diagram no longer results in the fingerings disappearing
  • MuseScore Studio 4.4 contained a fix that prevented chord symbols to be rendered wrongly in scores with custom chords XML files after saving and reopening such scores. Version 4.4.2 goes a step further, by also automatically fixing scores from older versions when opening them.

For even more detail, see the MuseScore Studio 4.4.2 project on GitHub. 

With thanks to everyone who constructively helped us identifying and resolving these issues!

A look into the future

We are planning to release one more version in the 4.4 series, namely 4.4.3, which will available in a couple of weeks. This update will mainly bring more bug fixes, but we might include some small new features as well. After that, we will focus on the development of MuseScore Studio 4.5, which will bring a long-awaited overhaul to the percussion input flow, among other things. Stay tuned!

Comments

• Oct 20, 2024 - 18:29

I have struggled with Dorico after the Finale announcement - not to mention wasting $150 on the upgrade. I have now discovered MuseScore. Wow! I love it. I was able to write a new piece immediately without any tutorial. I was able to figure out what I needed to do. With Dorico it would take me DAYS with multiple posting of questions to the Dorico forum. Wish I had never paid for the upgrade.

Reply

• Sep 16, 2024 - 16:02

Congratulations on the new release!

While there seems to be much anticipation of the changes coming to percussion input flow, I can't find any description of them other than that they are being "improved". Is there more information on these planned changes available somewhere?

For example, I'm trying to understand if the mapping of percussion instruments (such as drumkit) to different VSTs is being addressed. Today, moving to a different VST for drums can require edits to the drum part (since the MIDI notes used by drumkits isn't always the same). Will the new percussion system include "look-up" functionality, so when I enter a note for "hi-hat" it will always play that way as I move to different drumkit VSTs?

Reply

• Sep 16, 2024 - 17:26

A VST drum kit that uses a mapping other than general MIDI is outside our control

Sound libraries in the Muse Hub are in our control and can be mapped to "play nice" with eachother for easy switching.

There are long-term potential improvements to this (possibly via a database of known VSTs and their sounds/instrument/technique mapping) but that is in the more distant future.

Reply

• Sep 16, 2024 - 17:49

Understand. So I assume this means that 4.5 will reconcile open / closed hi-hat between Musesounds and MS Basic. (Today, Musesounds uses an articulation to show open, but MS Basic uses a different note). Does this also mean that the MIDI mapping for open hi-hat in the Musesounds drumkit will be fixed in 4.5? Today, you get this by entering "hi-hat" and adding the "open" articulation. But when exporting MIDI, open and closed both export as MIDI note 42, so there is no distinction between them.

And to my original question, is there a place where these plans are documented?

Reply

• Sep 16, 2024 - 19:09

No, the plans are are still a bit generalized.

The advantage of MuseSounds is that it doesn't need a different midi-pitch to change the open-ness of a hi-hat. This could be good or bad depending on what you want to do, but the midi pitch that gets written is what gets sent out.

A legacy MIDI open hi-hat might be a good idea for import-export purposes

Reply

• Sep 16, 2024 - 19:22

@mdeluca wrote

> Does this also means that the MIDI mapping for open hi-hat in the Musesounds drumkit will be fixed in 4.5? Today, you get this by entering "hi-hat" and adding the "open" articulation. But when exporting MIDI, open and closed both export as MIDI note 42, so there is no distinction between them.

@Zac wrote

> A legacy MIDI open hi-hat might be a good idea for import-export purposes

Ya think?

Just seems odd that MuseScore has its relatively deep predilection to sidestep MIDI.

People have grown accustomed to MIDI since it started working with instruments about 40 years ago.

"Legacy" hi-hat?

Reply

• Sep 16, 2024 - 19:49

Thanks @zac for this information. If I understand your note correctly, this means that means composers need to choose between two competing options when writing for hi-hat - the "standard" way that historically has been supported (with different MIDI notes for open and closed), vs the "new MuseSounds" way that is not currently backward compatible.

If I write a part for any other instrument (violin, trumpet, etc.) I have assurance that I can easily switch between MuseSounds and any other VST and retain the notes I put in. But when writing for hi-hat in a drum kit, it seems I now need to choose whether to keep the part compatible with all other VSTs, or write exclusively for MuseSounds. If this is correct, I have trouble seeing how I would use the MuseSounds drum kit with any regularity.

For reference, this is entered as a bug in GitHub at https://github.com/musescore/MuseScore/issues/24669

Is there something I'm misunderstanding here?

Reply

• Sep 16, 2024 - 20:49

@mdeluca wrote

> when writing for hi-hat in a drum kit, it seems I now need to choose whether to keep the part compatible with all other VSTs, or write exclusively for MuseSounds. If this is correct, I have trouble seeing how I would use the MuseSounds drum kit with any regularity.

That's my question precisely ...

@mdeluca wrote in a Github post

> What is not clear is whether this is an artifact of the move to a new percussion system (started in v4.4, expected to be completed in v4.5), with the new code being added in 4.5 providing an interface to address this issue. But as currently configured, drum export for open / closed hi-hat is broken when using the Muse Sounds drumkit.

Well said. And thanks for posting to Github.

Perhaps in 4.4.2 we currently have another example of "un oeuf insuffisamment cuits."

Reply

• Sep 16, 2024 - 21:09

To be clear, this is problem is solvable, but there is some nuance and room for improvement. MuseSounds can recognize the MIDI pitch for open hi-hat, that can be done in a simple library update independent of MuseScore Studio.

"Standard" is a funny word in non-pitched percussion. In a way, as things stand, we are being forced to choose between MIDI standards and notation standards (and even notation standards for drum kits is a hotly debated topic). MuseScore's philosophy has been to prioritize notation standards. Also, many VST's have some departure from General MIDI (VST drum kits can vary greatly, some have several Hi-Hats)

The legacy way was to use x on a different line: a human drumset player would not recognize that as an open hi-hat (assuming you know what I am referring to, that notation would be considered a different cymbal by a human). It was actually more difficult to write the notation for a standard open hi-hat then and it was often a
point of ridicule for MuseScore. Perhaps in the not-so-distant future can also add some logic that changes the pitches of hi-hats with open articulations on MIDI export.

In MuseSounds, the sampler recognizes that the user put an "open" articulation on a hi-hat and that makes playback happen. This is a good user experience for many people. However, as you know, this only changes what the sampler plays, not the midi pitch itself and it is not backwards compatible as you stated. The advantage of some departure from general midi is:
1. Smoother writing experience for drummers and people who don't even think about general midi
2. Composer will be able to get even more detailed playback options. In some of our MuseHub Libraries, you can control how open/loose/tight the hi-hat is, what hand you play the hi-hat with, strike with the shaft or the tip...etc. MIDI General cannot do that.

TL;DR I hear your complaint and understand the issue, in the very near future, we can add open hi-hat MIDI to MuseSounds drum kits but it will not be "standard" notation. We have a long and ambitious list of improvements for the percussion writing experience but the timeline is not locked-in at the present moment but I am sure more details will be shared soon.

Reply

• Sep 16, 2024 - 22:22

Why not translate the hi-hat note with an “open” articulation into the correct MIDI pitch when emitting MIDI data? (VST drum kits that deviate from the standard would need the ability to customize the mapping, but this can be implemented later down the line.)

Reply

• Sep 17, 2024 - 00:32

Thanks very much for your detailed reply. And my apologies if this discussion of 4.5 features is hijacking the 4.4.2 thread - I'm happy to move this discussion to a different location if that makes more sense.

Here's my understanding of the situation:

(1) It's hard to point to a single "standard" for non-pitched percussion (I am in full agreement here).
(2) General MIDI (GM) defines open and closed hi-hat with two separate notes (specifically, 42 and 46 respectively).
(3) Historically, open and closed hi-hat were represented in MS Studio using different notes on the drumset staff. In v4.2, for example, closed was a cross notehead above the top line (staff line -1), and open in the top space of the staff (staff line 1). This system allowed export using the appropriate GM note, but did not adhere to more "standard" notation, where open is shown as a note in the same location as closed but with the "open" articulation symbol.
(4) MuseSounds is moving to this more "standard" notation system, where Muse Sampler can read the articulation symbol and render the "open" sound. This allows for the more standard notation to play back appropriately when using MuseSounds, and provides access to other options available in MuseSounds libraries (variation of how far open, etc.)
(5) Because the underlying note for "open" and "closed" are the same (staff line -1), however, MuseScore Studio does not (currently) have a way to differentiate between open and closed notes when exporting, even though "open" has an articulation symbol. This also presents a problem when switching between MuseScore libraries and VSTs, as the VSTs can not "read" the open articulation symbol.

You outline a few potential options to address this:

(A) Logic could be added to the MIDI export process in Studio to intercept "hi-hat with open articulation" and map this to MIDI note 42. You suggest above that this might be possible in the "not too-distant future".

This option would definitely clean up MIDI export and support the ability to transfer parts to a DAW, as the export would follow GM conventions (with whatever modifications would be needed for the VST being used). But it sounds like this would still retain an incompatibility within the program when changing from MuseSounds to a VST. In other words, if I wrote a note using an articulation for "open", it would still be played as "closed" when switching from MuseSounds to a VST inside MuseScore Studio. Is that right?

(B) MuseScore Studio could add a second way to trigger "open" hi-hat, and MuseSounds could be updated to play "open" either when using the "open" articulation symbol or a separate note location. As a composer, I would have a choice to make: the articulation symbol (which would look "right" but would not export properly), or a separate note location (which would export properly for VSTs in a DAW, but would not look "right").

There are a few things that are not clear from your description. Both of these notes should play properly (as "open") when using MuseSounds. But what about MS Basic, or a VST? And what would happen if I start writing using "MuseSounds" notation (with the articulation notation) but then switch to a VST for a different sound?

(C) Leave things as they are. (You don't call this out specifically, but it is an obvious potential option). While I don't recommend this, it would need to be accompanied by good documentation, describing some of the points and restrictions above. In fact, careful documentation would be needed for any of these options to make sure users know how to work in the new system.

++++++++++++

The other option, of course, is to change "hi-hat with open articulation" to a separate MIDI note within the core code for MuseScore Studio. You don't mention this above, suggesting that this may be difficult (or more) to implement. If it is possible, however, this would seem to address all issues - MuseSounds would see a note with an articulation symbol, allowing control of the hi-hat as you outline (partially open, etc.), and VSTs and export would see this "MIDI note 42", allowing for proper playback and notation.

++++++++++++

Again, I appreciate your time to help describe what's going on and planned here. I've added a pointer in the GitHub issue to this thread as additional background, and hope that a good solution that cleans up notation, interfaces well with MuseSounds and other VSTs, and is implementable in code can be found.

Reply

• Sep 17, 2024 - 03:25

Any new development on Muse Drumline coming to Linux? In the original 4.4 post, They said that they would make a post on the forum about it, but I haven't seen anything about it. Also the play back on linux is SO much better. Thank you for fixing that on lower end computers, to hear my scores I would have to export a .wav file but now I can just listen and I hear everything. Amazing work.

Reply

• Sep 17, 2024 - 10:06

A new version of Muse Sounds Manager is being worked on at the moment, which will unblock the release of drumline for Linux users. This is actively being worked on, and we've been told to expect a release in the coming 3-4 weeks. We'll post a forum update on this when it's ready.
And very good news about the playback improvements! Very glad to hear this :-)

Reply

• Sep 17, 2024 - 08:00

That's a fantastic news! Is there any chance to have the performance issues with kind of big project fixed? I posted an issue on github, but got no answer at all. Thank you again for the great work!
EDIT: They answered.

Reply

• Sep 17, 2024 - 16:21

Hi, any chance that ara plugin full support will be added in the future? for programs like synth 5? currently, it's available to put in but doesn't work.
Thanks

Reply

• Sep 17, 2024 - 18:07

Does this mean
1. Playback for MuseScore Studio 4.4.2 for Linux will be disabled? Or that
2. Only enhancement introduced by the upgrade to MuseSampler by MuseHub for Windows and Mac will be missing from 4.4.2 for Linux, that otherwise playback will be as it has been for 4.4.1 (excluding any bug fixes included in 4.4.2)?

Hope this is clear.

Reply

• Sep 17, 2024 - 16:42

I struggle with the accessibility of the new Muse Hub. In general, dark themes are very difficult to read for me. Is there a setting somewhere that I overlook that allows to switch to a light theme?

Reply

• Sep 19, 2024 - 20:43

My laptop speakers stopped working last night and only output a bunch of noise. After eliminating many options, I'm sure it's due to Musescore. After I updated to 4.4.2 yesterday, whenever I open Musescore, the speakers stop working, and then work again when I close it. Please take a look at this issue, I can only try to use a lower version now.
I'm using a Dell Inspiron 15 3520 and Intel® SST OED.

Reply

• Sep 19, 2024 - 21:14

I submitted a comment earlier fretting over certain Muse Sounds not downloading, only for them to work perfectly twenty seconds after submitting the comment… the universe loves pranking me 🤣

Reply

• Sep 20, 2024 - 04:18

Since updating(meaning before, this glitch was not happening) my score randomly crashes and does not save, it closes the app entirely. As I said this has not happened before updating it.

Reply

• Sep 20, 2024 - 18:39

Greetings

I noticed a long time ago that the new versions of Musescore Studio have made a function that existed in the mixer disappear, so to speak. Let me explain, in older versions, for example, when you added a pizzicato to the strings, another MIDI channel was automatically added to the mixer as if it were an instrument change and it sounded like the pizzicato. However, with the new updates, that has disappeared, now, when you add a pizzicato, you can clearly hear the sound change, but it remains on the same MIDI Channel as the strings. This resulted in the fact that when it is exported in MIDI format to open in another software, it does not recognize the pizzicato, but instead it appears next to the same MIDI channel as the strings, causing confusion when assigning the sounds.

My point is, I don't know if they did it this way to reduce space in the mixer, or if it was something they overlooked. And if there is a solution in musescore itself, or how can I take this question to the developers so they can give me a clear answer or if they can fix it.

Lampiran Ukuran
Mezclador 3.png 82.94 KB

Reply

• Sep 21, 2024 - 16:57

Hey MuseScore!

I'm a new user and loving this software! Having used Finale for nearly 20 years and having just recently purchased my first Mac in years, the two together are great, so thank you all!

Quick question, is MuseScore 4.4.2 compatible with Mac OS 15 (Sequoia)?

Reply

• Sep 22, 2024 - 00:28

Based on the technical release notes of macOS 15, I expected no issues for MuseScore Studio, and in practice, in five days, I have indeed not seen any issues. So it looks like it's fully compatible! We might post an 'official' statement about this next week, if we decide that that's necessary.

Reply

• Sep 26, 2024 - 18:55

It is certainly considered, and will certainly be done. There is no concrete timeline for this yet though. In the past year(s), some volunteers have attempted to contribute Jian pu support, but unfortunately none of them have been able to finish this work, because of the size and complexity of the task.

Reply

• Oct 13, 2024 - 07:04

Hi, great progress! The drumline update seems awesome.

Unfortunately, there are still many "missing" features and weird bugs that force me to stay on MS3 (this list based on Musescore 4.4.2 tested earlier today):
◄► MS4 has no image capture.
◄► MS4 cannot pitch bend. (MS2 & MS3 could pitch bend)
◄► MS4 has no actual Full Screen mode.
◄► MS4 cannot get a clean interface (cannot hide Home|Score|Publish, Parts|Mixer or Undo/Redo buttons).
◄► MS4 cannot scroll by note playback, only smooth scroll. (I teach, and rhythmic scrolling is great for accessibility as it makes the rhythm visual, plus cuts the file size way down, great for sending videos to parents when their kid misses a recorder class lol)
◄► MS4 auto-adds reverb to each track and all older projects, and I can't remove or adjust reverb globally.
◄► MS4 use the scroll wheel to make changes in the mixing window rather than scroll the window. And there's no way to undo these unintentional mixing changes, since the Mixer is not connected to the undo history.
◄► MS4 when I press a key on my midi keyboard, MS4 ignores the velocity, duration, & polyphony, forces all instruments into mono, and plays the note for one second. This is bewildering!
◄► MS4 Mixer combines all playing techniques and instrument changes into a single channel, whereas MS3 would expand the mixer track to include all instruments and techniques on unique midi channels (for example, in MS3, if I have arco, pizz, & tremolo on a violin staff, there are separate channels in the mixer for each, and I can even assign different sounds, panning, volume, etc; but in MS4, there's just "Violin" and I cannot independently voice or mix them in any way -- see images).
◄► MS4 Mixer does not allow selecting or renaming tracks.
◄► MS4 Does not allow creating custom instruments, and does not read custom instruments from earlier versions.
◄► MS4 During new score creation, when inputting score info, Tab skips most input fields (Composer, Subtitle, Lyricist, Copyright).
◄► MS4 The New Score creation process was quite unintuitive and frustrating. I couldn't even adjust templates (tweaking the instruments in Jazz Combo is impossible). I have suggestions for this.

Regarding image capture, I teach music and create all sorts of visuals. I also frequently present around the country for other music educators, and creating workshop materials is a huge part of what I do. Exporting graphics in MS3 is a game changer. I can't imagine why this feature was eliminated.

Literally just today, I was helping a student get started with Musescore, and I'm constantly having to tell students (and the occasional youtube fan) "Ohhh, well, MS4 cant't do that thing that I did back in 2018, or that thing I did in 2022, or that cool thing we did in class today, so let me show you how to uninstall it and find the old versions..." At least the old versions are still available, and I'm grateful for that.

As an example, this video I made with MS2 is literally impossible in MS4: https://youtu.be/eKC2ykkYWDY

And if you have both MS3 and MS4, try loading the attached file (Super Bomberman). Is there any way to accomplish what I've done in MS3 with MS4?

I congratulate you on the recent updates, but its been very frustrating that so many useful features have been eliminated & neglected for nearly 4 years now. Can we get feature parody with 4.5?

MS4 really seems like a lost cause at this point. A completely different program capitalizing on the musescore name. At least, for users like me who used it massively and sent thousands of users your way over the past 15 years. It feels like you've completely abandoned us and our workflow. Feature parody matters.

Lampiran Ukuran
2024-10-12 22_06_14-Greenshot.png 205.88 KB
2024-10-12 22_06_55-Greenshot.png 356.18 KB
Super_Bomberman_2_ms3_v5_(not gen midi).mscz 53.32 KB

Reply

• Oct 13, 2024 - 12:45

Thanks for this list; it's always useful to see which things are important for people. I'll go through these points one by one:

  • Image capture: it is not clear how this feature was superior to the screenshot functionality that is built into every operating system nowadays.
  • Pitch bend: it should work as far as I know, so we'll need more details here. Probably easiest if you share a score where it's broken.
  • No full screen mode: could you describe what you mean? In what way does "View > Full screen" not meet your needs?
  • "clean" interface: if you can describe a convincing use case for this, you could consider creating a feature request at https://github.com/musescore/MuseScore/issues/new/choose. There is some exploratory design work going on about a "minimal mode", and I'm not sure if that will immediately include what you're asking for, but if you log a feature request it can be kept in mind.
  • non-smooth playback cursor: this has been requested exactly once before at https://github.com/musescore/MuseScore/issues/18809; it is not certain when exactly this will be implemented, because it's just one of the almost 1000 open feature request, and other things get requested more often, but eventually it will happen (and of course, any contributor is free to implement it right now).
  • Reverb: is this the button you're looking for? Scherm­afbeelding 2024-10-13 om 11.53.30.png
  • Mixer / scroll / undo: these are known issues (https://github.com/musescore/MuseScore/issues/21054, https://github.com/musescore/MuseScore/issues/11128)
  • (Improved) MIDI (keyboard) support will come in a future update (maybe 4.6, or maybe some things even in 4.5 already) (https://github.com/musescore/MuseScore/issues/13381)
  • Playing techniques (pizz, arco, etc.) are now implemented in a more sophisticated way, removing the need for separate mixer channels for each of them. If you can describe a convincing use case that still requires multiple channels, feel free to create a feature request using aforementioned link. (tip: don't forget the "why" aspect)
  • Renaming mixer tracks will come in 4.5 or 4.6
  • Custom instruments: you can try creating another feature request for this; it looks like there is currently no open issue for it. Alternatively, request the specific instruments that you need to be added. The thing with this feature is that MS3 implemented it in a very unfinished way (requiring the user to submit an XML file in an undocumented format that changes with every few updates is not in line with our standards). In MS4, we obviously want to avoid such unfinished features, and if we implement a replacement, we'd do it properly, with a proper UI etc.. But that is of course more work.
  • Tab navigation: this one is a bit complicated. There are multiple issues about this on GitHub. The current behaviour is technically consistent with MS4's new keyboard navigation model (where Tab jumps between sections and the arrow keys between individual controls), but it is clear that it isn't very intuitive/usable in practice. A refined (more conventional) model is planned for either 4.5 or 4.6.

It must be noted that not every MS3 feature can immediately be ported over to MS4. Reasons include:

  • for some features, there is no clear use case, so we can't afford spending time on them, unless new information is provided to us about why the feature could be useful; that doesn't always mean that the MS3 feature will be brought back in its original form: sometimes a better solution for the same problem is implemented
  • some MS3 features were implemented using older technologies or bad technical design, which makes it impossible to port them, requiring a complete rewrite; this is not always feasible, especially for less popular features
  • for some things, there are just better ways nowadays
  • there has to be a balance between re-implementing MS3 features (i.e. moving backwards) and implementing useful new functionality (i.e. moving forwards).
  • it is natural that software evolves. macOS updates constantly remove features that I rely on. Sometimes, this leads to an adjustment in my workflow, that turns out to be an improvement in the end. And sometimes, it doesn't. In the case of macOS, the only option in such case is to be sad and live with it. In the case of MuseScore, you can explain your situation to us, and we'll take it into consideration.

When logging feature request, I would recommend: don't focus on which MS3 features are missing "on paper". Instead, focus on what problem you need to be solved, and why. If MS3 happened to do a better job at solving that problem, you can reference how MS3 did it as a possible solution. But "I want to achieve X because Y" is a much more convincing motivation than "MS3 had it".

By the way, it's "feature parity", not parody. Feature parody must be something like this: https://www.youtube.com/watch?v=AXeUeILI8IM 🙂

Reply

• Oct 13, 2024 - 12:53

Image capture of Mu3 is superior to the OS one by far because it

  1. supports setting DPI
  2. supports transparency
  3. supports SVG export
  4. supports to differentiate between screen- and print-view
  5. is implemented in an OS independant way
  6. had a resizeable rectangle, with coordinates that would persist within a session. And that rectangle was moveable—even to various pages of the score—allowing for consistent sized images.
    (citing @scorster, see further down))

Reply

• Oct 13, 2024 - 16:38

As noted above, a number of things on this list are simply misunderstandings - like, there is pitch bend (and far more sophisticated at that), and the new accessibility model simply means that Tab is now combined with F6 and cursor keys for faster navigation of complex windows Ike the score wizard). so most of things you are thinking of as impossible in Mu4 are not at all - there is just in some case a somewhat different method to achieve the same - or better - results. So Id encourage you to start new threads for specific individual problems you are having trouble figuring out how to solve. That way we can show you how to accomplish your goals in a more focused way (one thread per problem you are trying to solve).

Regarding image capture, I would agree this would be nice to have back. But to be clear, all OS’s provide native ways of doing this for quick and dirty screen shots, and publish mode gives you the print preview. For those cases where you need the higher DPI quality for print, or transparency for some special effect, or fine control over sizing for consistency in publication, the export function in the file menu works great as well. So while it the built-in image capture tool was useful indeed and Indo would love to see it return someday, there are perfectly good ways to get the job done. As a professional educator myself I haven’t encountered a case I can’t solve very well in MU4. Again, if you need help with a specific problem for which you ahre having trouble seeing how to use MU4, just start a new thread.

But more generally, I’d observe that by focusing on the handful of specific things about MU3 that are missing or don’t work the same in MU4, you are missing the enormous list of things that MU4 does better than MU3, and all the new possibilities this opens up.

Reply

• Oct 13, 2024 - 22:03

@Mac Sabatella wrote:

> Regarding image capture, I would agree this would be nice to have back.

Good to hear your stance on that!

I think a sufficient users agree, so the return of Image Capture would be widely welcomed.

> But to be clear, all OS’s provide native ways of doing this for quick and dirty screen shots, and publish mode gives you the print preview.

Yes, but native OS screenshot tools have a couple of gotchas:

     1) low DPI (as you concur)

     2a) AFAIK , on MacOS, if you have MuseScore's Invisibles, Formatting, Margins, Frames, Unprintables and Sound Flags showing, you have to toggle them all off to get the equivalent of Image Capture's Print Mode—which is a single-step process! Then, to return to his or her working configuration, the user must re-toggle those Show settings.

     2b) I am unaware of a "print preview" native screenshot option on MacOS. Granted one could print to PDF and then do a screen capture, but I think the prevailing preferences for Image Capture cite its versatility and simplicity, i.e. no "rigamarole-ing." Are you aware of a "print preview" native screenshot option on MacOS?

     2c) Are you stating that there's definitely a "print preview" screenshot option native on Windows?

> For those cases where you need the higher DPI quality for print, or transparency for some special effect, or fine control over sizing for consistency in publication, the export function in the file menu works great as well.

MS3 had PDF, PNG and SVG Export options, albeit with transparency only available in PNG.

MS4's graphical File>Export options of PDF, PNG and SVG are quite welcomed, and are more versatile than MS3's because each format now has the option of a transparent background. Of course that was possible in MS3's Image Capture.

But MS4 export falls short of Image Capture in the area of scope/selectivity:

     • in MS4, there's just one choice regarding the export range, that's the entire score!

     • Maybe this is a reasonable feature request that development adds a "Export selection only" checkbox to MS4's Export dialog.

. . .

> So while it the built-in image capture tool was useful indeed and I would love to see it return someday, there are perfectly good ways to get the job done ... I haven’t encountered a case I can’t solve very well in MU4.

AFAIK, this perspective overlooks the matters of core importance listed above.

scorster

Reply

• Oct 13, 2024 - 23:47

Wow everyone, I really can't thank you all for the input! I'll boot up MU4 again and try some of the solutions mentioned before responding.

P.S. You know what's funny? I spent over an hour proof-reading and editing before posting, and the final thought on my mind last night was, "Wait, it's parity not parody! I better change that quick!!" Then I fell asleep. Ha! Still appreciate that parody video though. It's one of my favorites, especially the "add an alto part" and the "Live Recorder" mode. 😆

Thanks!

Reply

• Oct 14, 2024 - 02:32

Almost every screen shot tool has that same functionality. If your OS built-in tool doesn’t, there are plenty of free / open source options available.

But again, for cases where you truly need consistent sizing, export is the better option anyhow. Because then it’s not just the size but the margins etc that are consistent.

Reply

• Oct 13, 2024 - 22:30

And of course, don't forget you can also just export images and crop them. Bit more work, admittedly, but if you need it, there are options.

By the way, it is likely that the image capture tool will come back at some point, but it is not yet known when exactly.

Reply

• Oct 13, 2024 - 22:37

Re 2a) AFAIK , on MacOS, if you have MuseScore's Invisibles, Formatting, Margins, Frames, Unprintables and Sound Flags showing, you have to toggle them all off to get the equivalent of Image Capture's Print Mode

If you capture from the publish tab you don't capture any of those. The publish tab is a WYSIWY Really G (AKA print preview).

Reply

• Oct 13, 2024 - 10:14

Ah, version 4.4.0 had an issue that it couldn't connect to the internet for some people (it has always been unclear why it didn't work for some people and did work for others).
But if you're unlucky, that also means that it can't check for updates.
You can download and install the latest version from MuseScore.org or via Muse Hub, and after that, everything should be fine again.

Reply

• Oct 13, 2024 - 09:28

Can you bring back the easily change speed tempo tool of the project? (Image attached) It was available on musescore 3.6 when you pressed F11 (Toggle play panel) And you could adjust the tempo speed of the whole project without having to add a tempo mark or text. I find it pretty useful and I don't know if it's gone or is hidden cause if you press F11 on musecore 4 now, it only activate fullscreen mode. Also bring support for really customizable templates with images and titles. The custom templates only respect the footer text you save but not the composer, other text or images added. For example, I'm currently working in a 15 piano pieces set, all of them have the same title, different number, composer name, and a big number in the staff, but when I open the template I saved everything is gone except by the footer and header, and that's frustrating! I don't like to waste time to re-edit it again. I'll attach a pictures of what I'm talking about
The first picture called "Example Musescore" is how it's supposed ot look
I'm attaching a preview of the template hub and it shows a preview of how the score would look like...
And then the empty template (last picture named empty template) It only has the footer and everything else is gone.

Lampiran Ukuran
Example Musescore template.png 107.5 KB
Preview template.png 85.05 KB
Template empty.png 29.47 KB
musecore 3.6 play panel.png 19.59 KB

Reply

• Oct 13, 2024 - 10:25

Re. tempo override:
This functionality still exists. Just undock the playback toolbar, and that slider will appear.
(Some people say they find this difficult to discover, and I think they have a point; perhaps this will be changed a little bit in a future update.)

Re. templates:
I believe there was no intention to change the behaviour w.r.t. MS3 w.r.t. what's preserved and what not. Feel free to open an official bug report about it at https://github.com/musescore/MuseScore/issues/new/choose.

Reply

• Oct 13, 2024 - 21:36

I am using MuseScore 4.4.2 under Ubuntu 22.04 LTS, and I try to create a template where the field: Komponist/Arrangeur is always the same. Where or how can I enter/change the Title ..Komponist... etc fields on my template?.
Where is the menu for "Score properties"?. If I look under "Eigenschaften..(Properties)" once the muster score is on the screen, I do not see any field where I can enter this information. If I try the menu File->Projekt properties and enter my information, it will not be preserved in my template and if I try to create a new tamplate by defining it as New Score, entering the field Komponist/Arrangeur and then saving the result in the directory "Templates", this information is lost when I load this template later.
Maybe I miss something or I made something wrong, but in MSC3.6.2 it was not possible to keep this type of information in the Templates.

Reply

• Oct 13, 2024 - 21:42

For support questions, it's really better to start a new thread in the Support forum. But the short answer is, templates are about setting up the structure of your score, not the content. So the specific title or composer or other text in the template is not copied to the scores made from that template, any more than the specific notes and rests in the score are. Just the list of instruments, style settings, etc. If by "score properties" you mean the dialog where you can enter metadata that gets saved along with your score, see File / Project properties. To actually add the relevant information to the score itself (not just metadata), enter it into the wziard when creating the score, or use there Add menu at any time thereafter.

Reply

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