This project forked from musescore/musescore
MuseScore is a open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
Home Page: http://musescore.org
License: Other
UX/Interaction bug (incorrect behaviour)
In some cases, when removing horizontal or text blocks, some elements (such as slur and volta) lose some properties. The problem is present in versions 3.6.2, 3.7 and 4.2
3.6.2
No
Linux (Debian 12)
No response
Hi. Trying to figure out how to submit a PR that I developed against the 3.x branch on your fork. I currently do not have permissions to push it.
Don't know if this can be resolved.
Steps I did.
create score with 3 times the same scale.
Change instrument for measure 3,4 to alt sax
Change instrument for measure 5,6 to clarinet.
The key signature for the clarinet is wrong.
change instrument.zip
Kind regards,
File corruption
Importing MS4.x scores to Mu3.7 is a very interesting feature, but at that early implementation state
a) a load error message pops up and must be clicked away
b) many elements and some styles go lost during import
c) the page layout gets corrupt due to erroneous rescaled element positions and spacer/gap-distances (should be 1=1)
NOTE - page layout corruption problems are already reported here:
#165
#141
musescore#19014
Due to the corrupted page layout in MS3.7, it is difficult to reference to a page or a point in the attached score-examples, where a problem has detected.
First referencing the section/frame number in the score and then referencing a measure number in that section may identify the place (or just watch the screenshots).
-> MuseScore 3.7.0_Staff Texts Style Expression - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 159]
MuseScore 3.7.0_Crescendo Hairpins - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 155]
MuseScore 3.7.0_Ornaments Short Trills - Import from MS4 failed [Missa brevis in G-major, Section 6, Measures 134,142,148,151]
MuseScore 3.7.0_Ornaments Trills - Import from MS4 failed [Gloria in D-major, Section 10, Measures 120,130]
and probably many other elements not yet tested ...
MuseScore 3.7.0_Crescendo Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Text Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Elements Style Dynamic - Import from MS4 incomplete (text style and size wrong) [Missa brevis in G-major, Section 6, Measures 131,139,143,153,157]
and probably some other styles not yet tested ...
1.) take a MS3.6.2-score and import it to MS4.x; save it there
2.) take that MS4.x-score and import it back to MS3.7
NOTE: check attached testscores and screenshots
MuseScore-3.7.0.6145742308-x86_64
No.
Windows10 and 11, 64-bit
File corruption
Importing MS4.x scores to Mu3.7 is a very interesting feature, but at that early implementation state
a) a load error message pops up and must be clicked away
b) many elements and some styles go lost during import
c) the page layout gets corrupt due to erroneous rescaled element positions and spacer/gap-distances (should be 1=1)
NOTE - page layout corruption problems are already reported here:
#165
#141
musescore#19014
Due to the corrupted page layout in MS3.7, it is difficult to reference to a page or a point in the attached score-examples, where a problem has detected.
First referencing the section/frame number in the score and then referencing a measure number in that section may identify the place (or just watch the screenshots).
MuseScore 3.7.0_Staff Texts Style Expression - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 159]
MuseScore 3.7.0_Crescendo Hairpins - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 155]
=> MuseScore 3.7.0_Ornaments Short Trills - Import from MS4 failed [Missa brevis in G-major, Section 6, Measures 134,142,148,151]
MuseScore 3.7.0_Ornaments Trills - Import from MS4 failed [Gloria in D-major, Section 10, Measures 120,130]
and probably many other elements not yet tested ...
MuseScore 3.7.0_Crescendo Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Text Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Elements Style Dynamic - Import from MS4 incomplete (text style and size wrong) [Missa brevis in G-major, Section 6, Measures 131,139,143,153,157]
and probably some other styles not yet tested ...
1.) take a MS3.6.2-score and import it to MS4.x; save it there
2.) take that MS4.x-score and import it back to MS3.7
NOTE: check attached testscores and screenshots
MuseScore-3.7.0.6145742308-x86_64
No.
Windows10 and 11, 64-bit
See musescore#18790
See musescore#18123
See musescore#18790
No response
Be able to have a parameter "ignore" for a pedal setting and/or 8va. settings.
No problem, just an idea.
But for piano scores with lots of pedal settings, it is not possible to change the instrument to organ and keep the pedal settings. That sound quite bad!
So a flag to ignore them would be useful.
No response
Perhaps an idea also for v4?
Sort soundfont listing so it matches the soundfont organization
You might consider sorting the soundfont list by soundfont, then by bank number, then by program number. This would certainly help with organ fonts, which tend to have related fonts in their own bank.
No response
No response
Engraving bug
And not flat cap. It's possible simply changing
pen.setCapStyle(Qt::FlatCap);to
pen.setCapStyle(Qt::SquareCap); will do the trick for when drawing hooks
@ libmscore/textlinebase.cpp
@line 117 on 3.x branch at the moment.
Think it was a left over change from transitioning when right before switching to polyline for hairpins because it used to overlap way too much and look like hexagons
.
No response
3.x
Yes, this used to work in MuseScore 3.x and now is broken
.
No response
Crash or freeze
Oh gosh, this one took me a while to figure out (realize that there was a problem, let alone solve it). Since I'm still on 3.7 for now this was rare but important enough under certain circumstances
The crash actually doesn't happen often (but it did happen often on one particular score I was working on when switching into continuous view. Not sure what it's contingent upon. I think it has to do with the spacing of staves and the footer/header. Anyways...
1.) Make a score
2.) Make sure to have header/footers on
3.) Make sure to have score be filled up to an entire page to some sort, spilling into page 2
4.) Click on score elements while in continuous view after switching from page view
Now open that score in page-view, then switch to continuous view
Then attempt to select an element on the score. Odds are a crash occurs, but not always couldn't figure out what it was... The reason has something to do with a text pointer being given a parent of type "page" instead of null... when from backporting musescore#9193
I figured I'd bring this up as one of those "Obscure" 3.7 bugs.
Author: Nick Mazuk [email protected] 2021-09-21 00:03:03
Committer: Joachim Schmitz [email protected] 2022-05-11 23:34:48
and i'm 99% sure the culprit is that "pseudo" valid text pointer which will trigger a "valid" parent but it isn't set up so that when handling the mouse press event handler to find the elements surrounding it... it picks up sometimes this "text" that doesn't have a full setup to it, but it passes the null pointer check and then hell breaks loose later
Text* Page::layoutHeaderFooter(int area, const QString& ss) consthas this:
text->setParent((Page*) this); <-------
Align flags = Align::LEFT;
switch (area) {
case 0: flags = Align::LEFT | Align::TOP; break;and the text->setParent((Page*)this) needs to become
text->setParent(nullptr);since the text has no business being attached to the score like that, from what I can tell. After setting parent to nullptr, I can't replicate the crash. Apparently in the 4.0 code they had something like text->moveToDummy();
... just in case I'm not the only one who cares about this shit..
Here's a peculiar score demonstrating the crash
3.7
Yes, this used to work in MuseScore 3.x and now is broken
XFCE
No response
Other type of issue
Chords and staff text attached to the triplets are lost if time signature is changed or measures are joined.
(1) In the attached file, drag 4/4 time signature over the existing 2/4 time signature; the Cm chords and staff text attached to the triplets disappear.
(2) In the attached file, join measures 6 and 7 (leaving the existing 2/4 time signature unchanged). The Cm chords and staff text attached to the triplets disappear.
No response
3.7.0.5389870991, revision: github-musescore-musescore-5ac2a85
No.
Windows 10
I reported this issue first in v3.6.2 (github.com/musescore/issues/15090). It is fixed in v4.1 (beta)
File corruption
Importing MS4.x scores to Mu3.7 is a very interesting feature, but at that early implementation state
a) a load error message pops up and must be clicked away
b) many elements and some styles go lost during import
c) the page layout gets corrupt due to erroneous rescaled element positions and spacer/gap-distances (should be 1=1)
NOTE - page layout corruption problems are already reported here:
#165
#141
musescore#19014
Due to the corrupted page layout in MS3.7, it is difficult to reference to a page or a point in the attached score-examples, where a problem has detected.
First referencing the section/frame number in the score and then referencing a measure number in that section may identify the place (or just watch the screenshots).
MuseScore 3.7.0_Staff Texts Style Expression - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 159]
MuseScore 3.7.0_Crescendo Hairpins - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 155]
MuseScore 3.7.0_Ornaments Short Trills - Import from MS4 failed [Missa brevis in G-major, Section 6, Measures 134,142,148,151]
MuseScore 3.7.0_Ornaments Trills - Import from MS4 failed [Gloria in D-major, Section 10, Measures 120,130]
and probably many other elements not yet tested ...
MuseScore 3.7.0_Crescendo Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Text Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
=> MuseScore 3.7.0_Elements Style Dynamic - Import from MS4 incomplete (text style and size wrong) [Missa brevis in G-major, Section 6, Measures 131,139,143,153,157]
and probably some other styles not yet tested ...
1.) take a MS3.6.2-score and import it to MS4.x; save it there
2.) take that MS4.x-score and import it back to MS3.7
NOTE: check attached testscores and screenshots
MuseScore-3.7.0.6145742308-x86_64
No.
Windows10 and 11, 64-bit
File corruption
Importing MS4.x scores to Mu3.7 is a very interesting feature, but at that early implementation state
a) a load error message pops up and must be clicked away
b) many elements and some styles go lost during import
c) the page layout gets corrupt due to erroneous rescaled element positions and spacer/gap-distances (should be 1=1)
NOTE - page layout corruption problems are already reported here:
#165
#141
musescore#19014
Due to the corrupted page layout in MS3.7, it is difficult to reference to a page or a point in the attached score-examples, where a problem has detected.
First referencing the section/frame number in the score and then referencing a measure number in that section may identify the place (or just watch the screenshots).
MuseScore 3.7.0_Staff Texts Style Expression - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 159]
MuseScore 3.7.0_Crescendo Hairpins - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 155]
MuseScore 3.7.0_Ornaments Short Trills - Import from MS4 failed [Missa brevis in G-major, Section 6, Measures 134,142,148,151]
=> MuseScore 3.7.0_Ornaments Trills - Import from MS4 failed [Gloria in D-major, Section 10, Measures 120,130]
and probably many other elements not yet tested ...
MuseScore 3.7.0_Crescendo Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Text Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Elements Style Dynamic - Import from MS4 incomplete (text style and size wrong) [Missa brevis in G-major, Section 6, Measures 131,139,143,153,157]
and probably some other styles not yet tested ...
1.) take a MS3.6.2-score and import it to MS4.x; save it there
2.) take that MS4.x-score and import it back to MS3.7
NOTE: check attached testscores and screenshots
MuseScore-3.7.0.6145742308-x86_64
No.
Windows10 and 11, 64-bit
Other type of issue
There have been warnings like this since quite a while on previous builds:
The macOS-10.15 environment is deprecated, consider switching to macos-11(macos-latest), macos-12 instead. For more details see actions/runner-images#5583
Seems now the time has finally come where it got disabled
No response
3.7
Yes, this used to work in MuseScore 3.x and now is broken
macOS 10.15
No response
Wonder if it would be worth attempting to backport 4.x beam layout code into 3.7, if it is absolutely deemed an improvement? Might be more trouble than it's worth. . ., as it would require updating of unit tests and everything else. Still, it would be nice to "snap the fingers" and have it all done.
Muse Sounds bug
• clicked notes sound flat compared to playback
• dynamics are not at parity from one staff/part to the next
• note tails swell unintendedly. Since MS4.0 I've notice this in Muse Sounds Strings and Choir
Download this score and listen for the issues described in the text objects.
No response
MuseScore 4.2
I don't know
MacOS 13.5.2
No response
File corruption
Importing MS4.x scores to Mu3.7 is a very interesting feature, but at that early implementation state
a) a load error message pops up and must be clicked away
b) many elements and some styles go lost during import
c) the page layout gets corrupt due to erroneous rescaled element positions and spacer/gap-distances (should be 1=1)
NOTE - page layout corruption problems are already reported here:
#165
#141
musescore#19014
Due to the corrupted page layout in MS3.7, it is difficult to reference to a page or a point in the attached score-examples, where a problem has detected.
First referencing the section/frame number in the score and then referencing a measure number in that section may identify the place (or just watch the screenshots).
MuseScore 3.7.0_Staff Texts Style Expression - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 159]
MuseScore 3.7.0_Crescendo Hairpins - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 155]
MuseScore 3.7.0_Ornaments Short Trills - Import from MS4 failed [Missa brevis in G-major, Section 6, Measures 134,142,148,151]
MuseScore 3.7.0_Ornaments Trills - Import from MS4 failed [Gloria in D-major, Section 10, Measures 120,130]
and probably many other elements not yet tested ...
MuseScore 3.7.0_Crescendo Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
=> MuseScore 3.7.0_Text Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Elements Style Dynamic - Import from MS4 incomplete (text style and size wrong) [Missa brevis in G-major, Section 6, Measures 131,139,143,153,157]
and probably some other styles not yet tested ...
1.) take a MS3.6.2-score and import it to MS4.x; save it there
2.) take that MS4.x-score and import it back to MS3.7
NOTE: check attached testscores and screenshots
MuseScore-3.7.0.6145742308-x86_64
No.
Windows10 and 11, 64-bit
Other type of issue
After about 10 minutes or so of playing the keyboard freezes. It doesn't update unless you close and open it again. But even then it won't update itself normally anymore. I cannot get it to work again unless I restart the program.
Every time I use the program for some time the problem appears. I cannot reliably reproduce it with an action - it just freezes suddenly during playback.
No response
3.7
Yes, this used to work in MuseScore 3.x and now is broken
Windows 10
Version 3.7.0.719899236
Which is the one titled "Fix "Minimum Distance" property for lyrics #256"
Choose option...
Edit->Select All does not select triplet markings (brackets and numbers) or volta segments with their numbers. Likewise measure numbers.
Add triplets and/or voltas to score.
Edit-> Select All
Result: Above items remain black. With everything else still selected, clicking Set Invisible in the Inspector does not make the items invisible.
OS: Windows 10 (10.0) or later, Arch.: x86_64, MuseScore version (32-bit): 3.7.0.4843924417, revision: github-musescore-musescore-51d07aa
I don't know
Windows 10 Pro
https://musescore.org/en/node/304562 for previous similar report. Couldn't find a bug report. For me, cresc/dim and mf+hairpin are included in the selection with Select All.
Crash or freeze
After the dialogue, that appears after uploading a score to musescore.com or when trying to log in, opens, the software crashes after ~1 second.
It works without problems with 3.6.2 and 4.2
No response
3.7
Yes, this used to work in MuseScore 3.x and now is broken
Windows 10
My locale is set to Japanese despite the rest of my system being in German. (Just listing it here in case it only crashes for me and this might be the reason.)
Other type of issue
I'm being lazy and not sending PR requests... but real quick I'll msg here about:
Crescendo hairpins at the starting point where the lines meet look slightly bad in 3.x sometimes. MS4 doesn't seem to have this problem. It seems to do with the cap style, and can be fixed adding the setCapStyle call within when if (twoLines):
void TextLineBaseSegment::draw(QPainter* painter) const
@ the line having:
if (twoLines) {
add the following:
pen.setCapStyle(Qt::FlatCap);
I think there's also a mitre setting that could make it even better but i didn't experiment with that.
Another little problem is that frames don't update the bounding boxes of a chord symbol. This is a big corner case since most people probably don't use frames on chord symbols, but I was doing some inverted color scheme for some negative harmony stuff and found the problem that way. It draws ok, but you can notice on occasion a screw up of a frame because the bbox is reset to be bounded to the chord letters and not take into account a frame and its margins.
You can test the veracity by turning on bounding boxes of a chord symbol when there's a frame existing on it.
To fix this, i provide a screenshot of the code difference from git:
You see, the calculateBoundingRect() function returns a point and is passed as an argument into setPos(), but that ends up overriding the results of the previous layout1() function, which is where the frame is taken into account. Making the above changes will fix it. Have a nice day!
.
No response
3.x
I don't know
.
.
Crash or freeze
For months I've been running v3.7.0.4524440406 on Mac OS Ventura 13.3.1
macOS 10.16, Arch.: x86_64, MuseScore version (64-bit): 3.7.0.4524440406, revision: github-musescore-musescore-f3d36a3
I'll start by saying I'm deeply appreciative of all the work dedicated to making 3.7 exist!
Today I tried to install the latest version but got the error that MuseScore "is damaged can't be opened"
After that I downloaded a revision a few versions back, but I got the same alert with 44930:
Any special steps required to get beyond this?
Is this perhaps related to the unsigned issue which I overcame when first opening v40406?
Thanks!
Scorster
No response
Never opens.
Choose option...
MacOS 13.3.1
No response
UI bug
MuseScore 3.7 Palettes Menu fail to load in the 64-bit version for Windows. There only is an empty gray field with no content at all (not even the add palettes button).
3.7.0 (any 64-bit Windows version)
Choose option...
Windows 10, 64-bit
Any build of MuseScore 3.7.0, but only 64-bit Windows-Versions (not in x86 Versions).
(Note: Plugins also will not appear in 64-bit Windows versions - may be any dependence)
File corruption
Importing MS4.x scores to Mu3.7 is a very interesting feature, but at that early implementation state
a) a load error message pops up and must be clicked away
b) many elements and some styles go lost during import
c) the page layout gets corrupt due to erroneous rescaled element positions and spacer/gap-distances (should be 1=1)
NOTE - page layout corruption problems are already reported here:
#165
#141
musescore#19014
Due to the corrupted page layout in MS3.7, it is difficult to reference to a page or a point in the attached score-examples, where a problem has detected.
First referencing the section/frame number in the score and then referencing a measure number in that section may identify the place (or just watch the screenshots).
MuseScore 3.7.0_Staff Texts Style Expression - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 159]
=> MuseScore 3.7.0_Crescendo Hairpins - Import from MS4 failed [Missa brevis in G-major, Section 6, Measure 155]
MuseScore 3.7.0_Ornaments Short Trills - Import from MS4 failed [Missa brevis in G-major, Section 6, Measures 134,142,148,151]
MuseScore 3.7.0_Ornaments Trills - Import from MS4 failed [Gloria in D-major, Section 10, Measures 120,130]
and probably many other elements not yet tested ...
MuseScore 3.7.0_Crescendo Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Text Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
MuseScore 3.7.0_Elements Style Dynamic - Import from MS4 incomplete (text style and size wrong) [Missa brevis in G-major, Section 6, Measures 131,139,143,153,157]
and probably some other styles not yet tested ...
1.) take a MS3.6.2-score and import it to MS4.x; save it there
2.) take that MS4.x-score and import it back to MS3.7
NOTE: check attached testscores and screenshots
MuseScore-3.7.0.6145742308-x86_64
No.
Windows10 and 11, 64-bit
Allow the user to define the color of strings on an individual basis.
TAB for a standard guitar has no center string as a frame of reference so it is easy to mis-read strings 3 and 4. Allowing users to define the color would provide a useful visual reference. (Additionally it could be used to make the TAB stave look more like a guitar fretboard).
TablEdit allows the top 3 strings to be displayed in a different shade of grey and thickness to the bottom 3 strings.
See https://tabledit.com/help/english_m/other_options.shtml
My workaround is to add a colored line overlay with the correct Z-order but it's a bit painstaking since this can only be done manually and not via a plugin.
Other type of issue
Plugins using QtQuick (import QtQuick 2.2 or the like, like almost all plugins do) fail to load in the 64-bit version for Windows (which uses Qt 5.15.2) for some users (not for me though)
OR
No response
3.7
Yes, this used to work in MuseScore 3.x and now is broken
Windows
See https://musescore.org/en/node/342126#comment-1172480 ff. and https://musescore.org/en/node/351021
With the 32-bit version of MuseScore (which uses Qt 5.9.9) plugins work.
64-bit Windows can run 32-bit applications.
Engraving bug
Some glyphs fall back to the default music font (Bravura), even though they render correctly in MuseScore 4
For example:
Finale Maestro
MuseScore 3.7 with Maestro loaded
3.7
Not really, but this works in a later version of MuseScore 4.x
Windows 10
No response
Title. Is there a way to see a list of changes without having to look at the git commits?
Also might be a good idea to set the default branch on this repository to 3.x, assuming that's where all the activity is happening.
The 3.7 mixer is really nice, but it would be even nicer if there were keyboard shortcuts and tabbing. For instance, tabbing to sound, name, volume, expansion arrows. Alt-key shortcuts would be nice also; underline Sound, Name, and so on.
Would make it more accessible, would speed up work in the mixer, might make it easier to select sounds.
No response
No response
Engraving bug (incorrect score rendering)
Any time I try to add a slur to a score, it gets placed at the very beginning of the staff (before the clef) rather than on the notes. It seems automatic placement is failing.
The slur can be moved, but doing so changes the offset from 0, and thus likely would be incompatible with other versions.
No response
3.7.0.7584536684, revision: 14c206d
Yes, this used to work in MuseScore 3.x and now is broken
Windows 10
No response
I just updated the Chord Level Selector plugin and found that I had to make changes multiple times to the .qml file with an external editor and then re-test it for moving some elements around and got perturbed that I had to press the "Reload" button and then press Run over and over again, instead of just Run as a keyboard shortcut.
I present a quick change that you can choose to implement if you'd like or not, but I see no reason not:
mscore/plugin/pluginCreator.cpp
merely add load();
void PluginCreator::runClicked()
{
+ load();
log->clear();
msg(tr("Running…\n"));This will do what I wanted, with the only problem that if you edit code in the editor itself, you'd want to make sure to save before running (which I think you'd do anyways)
Additionally, I gave the Run and Stop buttons the ampersands so Alt+R and Alt+S would work as keyboard shortcuts:
------------------------ mscore/plugin/pluginCreator.ui ------------------------
index 9a7c342fd5..ccd93a4171 100644
@@ -43,26 +43,26 @@
<sizepolicy hsizetype="Expanding" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
- <string>Run</string>
+ <string>&Run</string> <widget class="QPushButton" name="stop">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
- <string>Stop</string>
+ <string>&Stop</string>
</property>
</widget>
</item>After saving externally, merely press Alt+R and it will run the updated plugin if you keep your plugin-creator open. Less clicking around.
No response
No response
Please implement in MuseScore 3.7 (i.e. alternates to 4.x) the new capo element ... or at least it's partial capo functionality and it's ability to transpose chord symbols.
The new capo element simplifies the addition of capo elements. It also performs a welcomed automatic transposition and affects chords symbols.
No response
I've posted my appreciation for this progress and also a critique here, expressing the need for capo-raltive frets (as well as nut-relative fret numbering, i.e. absolute fret numbers. The discussion also underscores the importance of supporting combinations of a full capo and one or more partial capos:
https://musescore.org/en/node/353203
... and I added to the .org post the link to the Github v4 pull request.
Engraving bug
In MuseScore 3.7.0 (any Windows version) NOT hiding empty staff after crescendo line in measure before.
If a crescendo line or hairpin ends just at a measure before the next few empty measures in a staff should go hidden, then the hiding fails. After deleting the hairpin or shifting to left (so it doesn't end at the end of the measure before), the hiding will work.
3.7.0 (any windows version)
Yes, this used to work in MuseScore 3.x and now is broken
Windows 10
If the crescendo line/hairpin is deleted or moved to left, then and only then the empty subsequent measures will go hidden.
File corruption
Importing MS4.x scores to Mu3.7 is a very interesting feature, but at that early implementation state
a) a load error message pops up and must be clicked away
b) many elements and some styles go lost during import
c) the page layout gets corrupt due to erroneous rescaled element positions and spacer/gap-distances (should be 1=1)
NOTE - page layout corruption problems are already reported here:
#165
#141
musescore#19014
Due to the corrupted page layout in MS3.7, it is difficult to reference to a page or a point in the attached score-examples, where a problem has detected.
First referencing the section/frame number in the score and then referencing a measure number in that section may identify the place (or just watch the screenshots).
=> MuseScore 3.7.0_Crescendo Lines - Import from MS4 incomplete (Lines style wrong and not visible) [Gloria in D-major, Section 12, Measures 76-77]
1.) take a MS3.6.2-score and import it to MS4.x; save it there
2.) take that MS4.x-score and import it back to MS3.7
NOTE: check attached testscores and screenshots
MuseScore-3.7.0.6145742308-x86_64
No.
Windows10 and 11, 64-bit
Crash or freeze
Crash occurs by clicking on the "move to bottom" button in the synthesizer. On windows. I tried in both administrator mode and non-admin mode. The program often crashes when trying to load predefined values also in the synthesizer (doesn't seem to be happening after opening MS with admin perms).
Here you are two videos. First one is about the crash I described it could occur with non-admin perms in step 3. Second one is this other crash that spits out the "Runtime error!" window.
The latest one to date. I literally downloaded the last build 20 minutes ago.
Yes, this used to work in MuseScore 3.x and now is broken
Windows 10
Github doesn't let me upload mscz files, it seems not to support it but I chose that one as I could've chosen any other, really. I can provide it anyway if you deem necessary.
Many thanks in advance. This is a summary of the guts of my PC, too:
Kind regards,
Daniel–Ømicrón.
UI bug
Importing MS4.x scores to Mu3.7 is a very interesting feature, but at that early implementation state
a) a load error message pops up and must be clicked away
b) many elements and some styles go lost during import
c) the page layout gets corrupt due to erroneous rescaled element positions and spacer/gap-distances (should be 1=1)
NOTE - page layout corruption problems are already reported here:
#165
#141
musescore#19014
In MuseScore 3.7.0 a "Load Error message" pops up when importing from MS4 scores
1.) take a MS3.6.2-score and import it to MS4.x; save it there
2.) take that MS4.x-score and import it back to MS3.7
MuseScore-3.7.0.6145742308-x86_64
No.
Windows10 and 11, 64-bit
No response
I have problems reading portable nightly MS4 files in 3.7
Is it still possible?
Kind regards
General playback bug
No response
Playback Loop Bugs when Bar ends on Rest.zip
No response
MuseScore version (64-bit): 3.7.0.5877292886, revision: GitHub-Jojo-Schmitz-MuseScore-1971a5b
No.
OS: Windows 7 Version 6.1 (Build 7601: SP 1), Arch.: x86_64
No response
UI bug
In the latest artifact "3.7.0.5784330917-x86_64" the Plugins and Palettes bugs [#128,#140] seams to be resolved, many thanks, but:
The Header and Footer Texts are now misplaced (not placed with the correct distance from page in X and Y directions - all texts overlap, see screenshots below.
Open attached score in ZIP and switch Header/Footer on and off (Format / Style / Header, Footer), see screenshots.
a) All the texts overlap at the left side of the page!
b) Switching on/off the Header-Text unexpectedly shifts down the hole score, causing unnecessary page breaks!
Detected Problems MuseScore-3.7.X.zip
3.7.0 (any windows version)
Yes, this used to work in MuseScore 3.x and now is broken
Windows 10, 64-bit
No response
UI bug
Note stems can be moved in both X and Y directions.
Note beams can only be moved in Y direction.
This is the case for guitar tablature scores.
The beam does not move horizontally.
No response
3.6.2 & 3.7
No.
Windows 10
No response
Audio
For some background, I have not used MuseScore 3.7 previously. I downloaded the latest build and ran into the MuseScore "is damaged can't be opened" issue, which I solved by running xattr -c.
After opening this version of MuseScore for the first time, I noticed that the playback and synthesizer tabs are greyed out. I am unable to use the playback.
Looking in the preferences, it seems like it's caused by MuseScore not recognizing the audio output device. The dropdowns in the I/O menu are empty and do not react at all when I try to click on them.
I tried clicking Restart Audio and MIDI Devices, as well as restarting my computer, but that didn't seem to do anything.
I opened my existing version of MuseScore 3.6.2 (which was downloaded a couple years back) to check, and that works just fine. Seems like I'm only having this issue with 3.7. I'm not sure if the xattr -c had a role to play. I tried downloading a version that's a few builds back (still having to use xattr -c to make it runnable), but the issue persists.
xattr -c /path/to/MuseScore.app3.7.0.6901522932
MacOS 14.1.1
Other type of issue
I didn't test all the options, but with the Show barlines box unchecked, only the left/start repeat sign remains visible — right/end repeat sign/barline and double barlines vanish, as do regular barlines.
Right click a staff.
Choose Staff/Part Properties
Uncheck "Show barlines"
Click OK or Apply.
Result: all barlines vanish from the staff, except the left/start repeat sign.
OS: Windows 10 (10.0) or later, Arch.: x86_64, MuseScore version (32-bit): 3.7.0.4843924417, revision: github-musescore-musescore-51d07a
I don't know
Windows 10 Pro
No response
Engraving bug
This thing has existed since somewhere in 3.x prior to PR#9000, if I remember correctly. It was corrected in transition though so it's not in 4.x, but is in 3.7:
3.7
Yes, this used to work in MuseScore 3.x and now is broken
...
A naive way to fix this is to just pull out of all adjustments if the conditions are met. That's what I did in the past
For example, in libmscore/tie.cpp:void TieSegment::adjustX()
if (isNudged() || isEdited())
return;
+ if (sn->noteType() != NoteType::NORMAL) {
+ if (en->chord() && en->chord()->notes().size() > 1) {
+ return;
+ }
+ }
+Where not normal = practically grace notes and the end chord has more than one note on it, i just quit all further adjustments. Certainly there's another way to include some niceties of further adjustment, in the meantime that will work and give:
Not mine actually, check this: musescore#17368
Described in the musescore#17368, brackets and other vertical lines can be of use for, but not limited to:
• Pedal markings (arrow down between the notes, specially useful with passages that feature long 8/16/32/64+ths sections.
Example here: https://www.youtube.com/watch?v=SBhTmaiBxTo
• Voice clarification: Examples given in the above mentioned feature request. It can be handful for indicating that a set of voices must be performed in a certain way. I have also my own example here (though as you can see I only provide the left bracket since musescore does not feature a right bracket).
Also in the musescore#17368
I do not really know if this feature request is out of the scope of this project. Perhaps it's not useful enough, but I have not found any solid workaround. I also hope this wouldn't be specially difficult to implement, but in all honesty, I have little to no idea.
Engraving bug (incorrect score rendering)
Saving and reopening a score always resets the section break system indentation to default setting.
Add a section break and add a measure after the break.
Remove the system indentation flag.
Save score
Open score.
System indentation flag is set back to default.
No response
3.6 and 3.7
I don't know
Windows 10 & 11
No response
I'm very happy you are continuing to backport fixes to Musescore 3. However, it is currently really complicate to figure out how to download this Musescore 3.7 Evolution.
It would be nice if you'd modify the Readme file to include instructions on how to download the already compiled files. I did it once, and I wish to update, but I cannot find it.
It would make it easier for anyone who wants to continue using Musescore 3.
Also, it would make it easier to test and see if the latest version has a problem, so you don't report a bug that has already been fixed.
No response
No response
Engraving bug
It's too bad, since it works well for the program and the PDF/PNG export
Make a score and add a hairpin...
Export to SVG
load it up and notice:
3.7
Yes, this used to work in MuseScore 3.x and now is broken
...
I noticed this earlier but forgot to mention it to you here. First pass glance at code didn't make sense as to why this is happening. . .
Since I export a lot of stuff via SVG... i had to personally revert. Not sure what can be done about it. It's probably something stupid somewhere lying around in the old code :)
Other type of issue
This works (exports PDF) in v3.6.2 and v4.1:
"C:\Program Files\MuseScore 3\bin\MuseScore3.exe" -o Hora.pdf Hora.mscx
However it doesn't work using v3.7, neither 64 nor 32 bit.
Some command-line options do work in 3.7, eg, -h and -v
verified the bug using mscz.
Open a Windows command window, copy a mscx file into the active directory. Delete any PDF files in the active directory. then enter
"C:\Apps\MuseScore-3.7.0\bin\MuseScore3.exe" -o Hora.pdf Hora.mscx
(using the actual installed folder of course)
Look for PDF files in the active directory (confirm there are none)
No response
3.7.0.5740844078 / ca2865a
Yes, this used to work in MuseScore 3.x and now is broken
Windows 11 and 10
No response
File corruption
[transferred from MuseScore 3.6.2 to MuseScore 4.1.1 and to MuseScore-3.7.0.6132193596-x64]
The ability to open Mu4 mscz files in Mu3.7 is a very interesting feature as long as Mu4 shows too many problems for effectively working with it (especially in the playback system / mixer with soundfonts, instrument selection and playing ornaments like trills).
But at that time after importing Mu4 files in Mu3.7 also some problems are present:
1.)
When opening Mu4-files in Mu3.7, all distances (X-pos/Y-pos of elements, texts, images, spacers, frame distances, ...) are wrong scaled (upscaled) by a factor of 1.250.
So each previously well positioned element must be repositioned or moved back to the right position over the whole score to achieve again a proper readable layout.
2.)
Style "Instrument Name (Part)" is not recognized during import -> text-font, text-size and text-position are set somehow arbitrary.
3.)
"Measure properties / Layout stretch" is not properly recognized during import -> staff with is mostly set too wide, so breaking down before the desired line break.
NOTE: A test score and several screenshots may be found inside the ZIP attachment.
Mu3 opens Mu4 mscz files with wrong scaled element distances.zip
3.7.0.6132193596
No.
Windows10 and 11, 64-bit
A test score and several screenshots may be found inside the attached ZIP.
File corruption
Didn't know how to go about sending a message on here to you, so figured an issue makes sense. I'm wanting to see if you can verify this situation with 3.x (3.7):
Make new score
Do a screenshot or something to clipboard and paste it into a vertical frame for instance
Save
Close and reopen
Result: image exists
Result: image does not exist! appears with the grey-x like:
This is a big problemo... still using 3.x due to having too many niceties and customizations that 4.x doesn't come close to for now, and if you can verify this, maybe we can hunt it down.
.
No response
.
Yes, this used to work in Musescore 3.x and now is broken
.
.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
