Tabs behaviour change - Opening two scores on the same window
S3 - Major
In musescore 3, opening multiple scores led to multiple tabs being created, and these tabs contained all the individual parts of the score.
In musescore 4, it takes as many windows as open scores, and the tabs are just there for the different parts of a score.
It was much more practical in musescore 3, especially while using musescore.com, as often many scores exist for a single piece of music, and easily switching between them is key in making your own arrangement.
Came up many times in the forum
OTOH the current behaviour has been asked for numerous times too
In reply to OTOH the current behaviour… by Jojo-Schmitz
Maybe make that an option, like in a web browser, either you open a new tab or a new window, and when dragging around the tab it snaps either to a preexisting window or to its own ? The tab would be a song, containing its individual parts, and you can either have all songs in the same window or in a different one.
Making is a Suggestion, AKA Feature request, as the current behavoir is By Design
See e.g. #336366: Each file opened with Musescore 4 editor opens into a new window (like alt + tab window, not tab), #338634: Ouverture de fichiers multiples, #338596: Clicking "New Score" or just opening a score in generael opens a new window, #338524: Creating a new score opens a new window, #338022: Opening multiple scores
See also https://github.com/musescore/MuseScore/issues/12647
In reply to See also https://github.com… by Jojo-Schmitz
this is waaay far a compromise!
moreover when running in full screen it is not possible to switch without closing or minimizing the active window, since it never releases the taskbar!??
it's definitely very surprising
and the whole thing is really too penalizing...
Are you saying Alt+Tab isn't working normally for you? Id eos for me on both WIndows and Linux.
In reply to Are you saying Alt+Tab isn't… by Marc Sabatella
sorry, I'm afraid I can't verify that point, I just downgrade to 3.2.
But I meant that lowering the mouse pointer to the very bottom of the screen does not bring up the taskbar, thus forcing to minimize the window
Why 3.2 rather than the much better and newer 3.6.2?
no idea !! but 3.6.2 is not (yet?) available for download
In reply to no idea !! but 3.6.2 is not … by MINOSI
but many thanks to you, I found it!
For Linux newer Appimage versions are on GitHub
In reply to sorry, I'm afraid I can't … by MINOSI
No need to uninstall MuseScore 4 just to try out older versions - they can peacefully coexist. As mentioned, Alt+Tab works as usual, so the loss of the taskbar in full screen mode should not cause any special problems.
Yes but no ! it is precisely this page that stops at 3.2.
I found 3.6 here: https://musescore.org/fr/node/317219
(for Windows in my case)
In reply to No need to uninstall… by Marc Sabatella
it's out of habit to work with the mouse... I don't practice alt-tab.
another really annoying thing with this version 4 ... I just noticed that now version 3.6.2 can no longer open scores that V4 had modified! So no backward compatibility... ohoh not good at all that!!
(however musescore is still a marvelous creation. It absolutely has to be said)
Export to MusicXML in Mu4, import in Mu3
In reply to Export to MusicXML in Mu4,… by Jojo-Schmitz
I very deeply agree with the many user complaints about this new "by design" UI/UX frankly atrocity. It is so bad, that it really does discourage the use of the new 4 vs. 3 at all (and, what sucks in my experience at least, and I cannot nor have the time to explain why this is, but 3 always crashed for me – it is a guarantee, seemingly randomly (typically when doing something a bit more complex / computationally demanding, like, select all then perform some change of property of sth, etc.), the app will crash out of the blue and hopefully any work I've done in the last two minutes since auto-save wasn't critical or difficult to have to redo).
Please allow us to open multiple musescore files in ONE application window (specifically, I am on a macOS desktop). On macOS, a new application icon is created in the dock for every single new window¹. If this is by design, it cannot be considered "good" design. This cannot be by design, but by oversight.
¹ FURTHERMORE, even after closing the window (and this is the real crux of the issue where this cannot be "by design" – it has to be an oversight), these additional Dock applications icons in macOS persist. One has to explicitly right-click and then choose "remove from Dock" even after having closed down the window (even after having entirely shut down all instances of MuseScore4). So you see, macOS is confused, thinking that you are initiating new applications (not merely new windows) for each new window. What happens is in a single day of work one could end up with 20+ MuseScore4 application icons in their macOS Dock even after the program has been entirely shut down.
This is a bug.
USER CASE — EXAMPLE (See screenshots attached):
So for example, as a test, I opened many files at once, you can clearly see in the screenshot after the first MuseScore4 file is open (which uses the regular, single standard application Dock icon (as all other macOS applications behave - virtually). But then for all additional files beyond the first, "extra" new application icons are initiated and you can see those have piled up specifically in the section of the macOS Dock for "extra"/auxiliarily-instantiated apps. Curiously, if one does shut down the main first opened MuseScore4 window/"app" first, what happens (as shown in attached screenshot), is indeed all the other apps/windows (they should be windows, not apps!!), will attempt to close (notice them all jumping chaotically annoyingly excessively as one would expect - they are prompting "Are you sure you want to close before saving?" - of course).
In regards to my previous statement about "twenty" persisting "ghost" (if you will) MuseScore4 app icons, it seems there is some limit, actually, specifically of 3 (I would need to test further and see if this was related to the fact that I first closed the primary Dock MuseScore4 app icon/"window" - what would happen if I left that main instantiation of the app running and attempted to close all the extra windows? I wonder if more than 3 would persist as ghosts). Only 3 extra of these MuseScore4 applications icons will persist in the Dock once all have been shut down / closed ² (and mind you I had to one by one click on each dock icon to get to the window, say no I do not want to save shut down as I have hopefully wanted to do with one simple click). But aside from the ludicrous clutter this causes in the Dock while working with MuseScore4 running, the undeniable bug is that no extra/additional Dock app icons should be persisting once the program and all windows have been entirely shut down.
² And for those who may not be aware, on current (and for some time now) macOS, a small white circle beneath an app icon in the Dock indicates that that app is running. As can be seen in the attached screenshot here (displaying the 3 "ghost" MS4 app "extra" icons - persisting after complete shutdown): the lack of white circles beneath all of the four※ total, shows that I had entirely closed down the program.
※The main one, which should be always the only one ever showing; plus the three extra grouped at the right end of Dock.
→: Why are there now 3 permanent extra MS4 app icons in my Dock? This is the question/bug.
I did just discover a workaround, for macOS users (see attached screenshot for a setting that can be unchecked under the Dock System Preferences section), which eliminates the appearance of permanent extra MS4 Dock icons. But this is not ideal. This setting exists for a reason on macOS and is convenient in various other instances to have turned on; so one is forced to sacrifice the functionality of the entire OS, in part, for this workaround.
Also, I have not yet tried using MS4 again now. I am not sure what the behavior will be like now when I try opening multiple different projects. Again, in short/summary, it appears there was some oversight specifically in regards to how MS4 will operate on macOS, and more specifically, the macOS Dock.
(See detailed comment above where I rebut the defense of this being "by design" – it is a macOS-specific Major Graphical UI issue, detrimental to the use of the application.)
In reply to (See detailed comment above… by johnxcollins
It is additionally an Ergonomical (UX) issue, which itself is hugely problematic. But the persisting ghost app icons in macOS Dock I provide example proof/evidence of demonstrates the severity overrides being merely ergonomic and is unfortunately instead outright Graphical software design oversight.
I also would like to have the score tabs back.
In MuseScore 4 there are three tabs: Home, Score and Publish. 'Score' and 'Publish' are somehow the two aspects of a score, but 'Home' is not, so it feels like things are pushed here together, that do not belong together. Logically 'Publish' should also be somehow the child of the 'Score'.
I have also read elsewhere that each score needs a separate window because of the playback.
Can somebody tell me how the number of windows influences the playback?
In reply to Hello, I also would like to… by kovianyo
MuseScore 3 had a very severe limitation because of the single window: all scores were forced to play with the same set of loaded soundfonts. This was just barely tolerable (but still a royal pain in many cases) when all you have to deal with are soundfonts. But it's completely unworkable now that there are Msue Sounds and also VST's. Forcing all scores to use the same sets of sounds would be completely unworkable, as would unloading and loading all sounds every time you switched tabs. Separate instances are the solution.
In general, it's a good solution - multiple windows are easier to work with than tabs within a single window on Windows and most Linux systems, including ChromeOS, because the OS was designed from the ground up to support this (heck, Micrisoft even named their OS around this). But macOS definitely makes multiple instances awkward because it doesn't manage the icons on the taskbar nicely like other systems do. So, it would definitely be good to find a solution to that shortcoming.
Hello Marc, thank you for your reply. I would be interested in why is the loading and unloading of the sounds tied to the number of tabs or windows? Tabs and windows seems to be a 'user interface' concern to me, and playback a 'backend' concern. Like for Chrome, you have a seamless transition between tabs and windows. Do the separate windows use separate processes, and separate processes are necessary to have multiple sounds loaded? Or why would you need to unload the sounds if you switch tabs?
It's not about the number of windows, it's about the number of "instances" (processes). By putting each score into a separate process, you can easily have different sets of sounds for different scores and the OS can manage the swapping very efficiently. Trying to do that within a single process - well, if you think you can pull it off, we welcome your PR implementing it!
Yes, I wanted to avoid looking into the source code. :)
If it is about the processes, then I think a single window containing the tabs could talk to multiple playback processes via some inter-process communication. Even seems a nice separation to me, could be challenging though on multiple operating systems. I see more and more programs using multiple processes, for example Chrome, so it looks like it can be done. But I don't know at which cost of complexity.
With the pro subscription and publishing scores I think I contribute to MuseScore sufficiently for me, so I don't plan to send a Pull Request, but thank you for answering my question.
Marc, this is very unfortunate. I understand that it is much easier to let an operating system deal with the process management (also at some point in Windows 11 new MS4 window crashes all of them), but this is not a good excuse to completely alter a good user experience. I've been constantly going back to 3.6.2...
... and yes, Alt-Tab works... as well as directly editing musicxml in either Oxygen or Visual Studio. ;)
As explained above, the reason for the change is efficiency and smoother workflow. There simply is no other known way to achieve the same level of smoothness when switching between scores that use different sound configurations - and forcing all scores to use the same sound configuration as MsueScore 3 would be very obviously unacceptable once you consider the new features of Muse Sounds and VST. So if you believe you have the solution, your PR to address this would be welcome, but so far, no one has found a way, so this is the best known solution to a difficult problem.
Not sure what you found preferable about having tabs that are essentially unreadable once you have more than a handful of scores open, compared to the elegant simplicity of Alt+Tab, but it's important to remember that preferences are personal, and that sometimes progress dictates that the needs of the many outweigh the needs of the few.
In reply to As explained above, the… by Marc Sabatella
I've had a similar situation years ago when my team had to compromise some UX capabilities to maximize process effectiveness - it didn't end up well - we had to redesign a lot. Without looking at the source code (and I am not a developer anymore) I can't say exactly what can be done, however, you may look at the dynamic load/unload of sound configuration at the tab switch (so only one active config is loaded at a time).
As it comes to many vs. few, if you've done a VoC and know for sure that it is really many vs. few then it is fine.:)
In reply to I've had a similar situation… by imandrosov
It's certainly possible to unload and load sounds every time you switch scores - it's just incredibly inefficient. I don't think people would be happy if it took 10-30 seconds or more just to switch from one open score to another. That's why, again, the current situation is as good as anyone has been able to come up with, but alternative technologies are still being actively pursued as well.
I'm not familiar with the acronym VoC, but yes, usability tests are run often for all sorts of aspects of the user interface. I don't think, though, that anyone tried implementing the 30-seconds-to-switch-scores model just to perform a test of this versus separate instances. It's just a sort of common sense assumption that people wouldn't like that. Most modern operating systems are designed to make multiple instances work well and naturally, selecting between open instances either via Alt+Tab or by simply clicking in the list that appears when you click a taskbar icon. macOS seems to be the odd man out here, not supporting this model well at all, unfortunately. And that's why much of the effort being spent on this problem is being directed on how to work around that limitation specifically
In reply to It's certainly possible to… by Marc Sabatella
I assume the load time depends on how much really needs to be loaded/unloaded, what "unloaded" really means and how many things are shared (I haven't seen the code), however, if you say 10-30 seconds it really is long. Also, depending on how many apps someone has opened the Alt-Tab can easily take the same 10 seconds.
VoC stands for "Voice of Customer" and there are several VoC methodologies that can be used for new product development. One important question would be to estimate "the customer population positively vs. negatively impacted" by a feature.
Also, for a test's sake, I've just tried to open 5 scores and the 5th score crashed them all. :(
Regardless of how many apps one has open, I've never seen Alt+Tab take ten seconds, that would seem to indicate an extreme RAM shortage that no amount of redesign of the application would solve.
One of the advantages of multiple instances is that it shouldn't be possible for one crash to affect other instances. Certain;y I've never seen this happen. But if you have a case where it does, best to ask for help on the Support forum and give more details. Then if someone else can reproduce the problem, you can open an issue on GitHub. This old-style issue tracker here has been retired and is no longer maintained.
In reply to Regardless of how many apps… by Marc Sabatella
I think my biggest gripe with this change is that I see a bunch of icons on my dock with no way of know what is what until I cycle through them. With 3.x I could see what the tab is called and instantly know what score I'm switching back to. It would be nice to allow users to toggle this feature.. I personally have no reason to have multiple playbacks going on at once, and never had crashes affect me to the point where I wish I had separate instances to mitigate it. While I understand this makes things easier for you guys under the hood, it makes for an extremely counter-intuitive and hateful UX lol I'm pretty much forced to downgrade back to 3.x.
I also think that while this is a free program, if you have so many users asking about this feature that its affecting the SEO of the program (Musescore 4 open tabs and Musescore 4 open windows come up before Musescore 4 open source - check it out), maybe you guys should pay attention to the complaints instead of telling people to front their own code. It comes off pretty snide and shows a lack of understanding of how people actually use MuseScore.
I don't think most people care about the technical details. This design is just horrible. Please add an option to open in a new tab, otherwise the new version would never be adopted widely.
It's all about why it's being used isn't it? If, like me, you're using it as notation software you don't care about playback quality or massive orchestras (I've got all that in my DAW, I don't need that here. a simple sketch of the sound is fine). And if like me you're working with lots of different pieces of music, mashing versions, it's been fabulous being able to just tab between the different versions, and pasting between them, etc. extracting certain bits I like. I shall be downgrading to 3 until this gets sorted. Shame as otherwise 4 looks good. And it still has the physical look of tabs. But a new instance of the software opening up for every new file? Nah.
I listed the inability of MS4 to open more than one score at a time to be a "bug". I can understand that using Alt+Tab is one workaround, BUT ... it only works with two songs. Alt+Tab goes from one open program song to another. If 3 scores are open, it does not jump to it, and you have to locate and click on its title somewhere in the taskbar at the bottom of Windows to display it, then copy/paste a piece of notation from it, then locate and click on the original open score using the taskbar at the bottom, then paste the notes into that open program, etc. It just seems a key step back from MS3.6, which may have used the same soundfonts for all scores but gave you the ability to quickly jump between all versions of a song easily.
Further, every time you launch a new copy of a program, you are taking up significant ROM, RAM, CPU and Memory.
So, I also support allowing one copy of the MS4 program to open more that one score by returning the feature found in MS3.6.
Alt+Tab lets you switch between as many open apps as you like, on every OS I've used - just press it multiple times as needed.
Also on most systems, locating the correct score is as simple as clicking the taskbar icon then selecting the score from the list that appears. This is actually simpler than selecting it from an open tab in that the tab names are often truncated and may scroll of the side of the window.
So its shouldn't be any hard to copy and paste between files in MU4 than in MU3, other than macOS which has a limitation in this area where each instance gets a separate icon.
It's a fallacy to assume that multiple instances requires significantly more resource than a single instance with many scores open at once. Operating systems are designed to handle this well.
In reply to Alt+Tab lets you switch… by Marc Sabatella
Sorry to disagree, but when I press Alt+Tab multiple times, it does not jump from MS file 1 to MS file 2 to MS file 3, etc. Rather, it jumps from file 1 to file 2 back to file 1, back to file 2, etc. I in fact cannot reach file 3 using that method. I have to locate the file in the taskbar and then click on it. If I am somehow doing it wrong, please let me know. Nevertheless, we do have a difference of opinion. I enjoy MS3 and its ability to open multiple file tabs while in the same program, but if MS4 just cannot be made to do that, I guess we can all get used to using the taskbar. The key here is capability! If the programmers simply cannot get multiple tabs to work in MS4, then that is our reality. Alternatively, if they can, then eventually lots of MS users want to see it returned to the MS3 approach, based on the comments made here about this option.
As far as using system resources, three or four programs running at once always uses more system resources than running only 1 program. You are correct that most newer computers can handle it OK, but I checked my system resources with 3 copies of MS4 running, and they are definitely more in use than only one copy. That said, I stand corrected that my computer would strain to handle it. I have a multi-GB system and it doesn't really notice 3 copies running.
In reply to Sorry to disagree, but when… by fsgregs
You’re on Windows, right? As I recall it’s a matter of continuing to hold Alt to show all open apps. It’s a very common operation since so many other apps work this way too, so Windows definitely supports it well. See for instance https://www.howtogeek.com/429223/master-windows-10s-alttab-switcher-wit…. Not a matter of opinion at all, just a Windows technique you apparently weren’t familiar with.
As for resouce usage, what you are seeing is the max needed, not what is actually needed at any given moment. Again, o this is such a common operation, operating systems are highly optimized to support it well.
Well ... I'll be! Never knew you could switch between files by holding down the Alt key and tapping Tab multiple times. Thanks as always. I learn something new every day.
As to opinions, I was talking about the topic of the post, not Windows ... the use of tabs inside the same single process in MS3 rather than multiple files running separately in MS4. I strongly prefer MS3's approach, but as I said, if that is too hard for the programmers to create, I will just get used to using Alt+Tab and different copies of files in MS4. Thanks for your comments. They are always most informative.
To be fair, you only just learned how to fully use Atl+Tab a few minutes ago, you might want to give it more a chance before jumping to conclusions.
There is a good reason why almost every other major program dealing in large documents uses a similar approach. It's not about what is hard for the programmers for to create - it's easy to do tabs, too. It's about what allows for greater capability (different sounds for different scores), which is generally more in keeping with modern design principles, and which which is actually handled more efficiently by modern operating systems. One can do tabs but then one sacrifices everything else.
I would add here that Chrome transitions seamlessly between application windows and tabs in a single window, and between how operating system processes are associated with tabs and windows.
Yes, but that's because Chrome doesn't have to load potentially gigabytes worth of audio every time you switch tabs :-). As explained previously, there's a reason multiple tabs isn't really viable anymore in a world of VST instruments, Muse Sounds, etc.