Mu3 opens Mu4 mscz files with wrong scaled element distances #165
Comments
|
Item 1, that distance factor of 1.25: I can confirm, but have no idea where it stems from, nor where to fix it. Item 2, "Instrument Name (Long)" from 3.x has been renamed "instrument_excerpt" in Mu4, (and "Composer" to "poet") the others just converted from Sentence case to lower case. So I'd need to specual case this, will do shortly, seems an easy fix. Item 3, layout stretch, as far as I can tell it does get imported correctly in 3.7, but after import from 3.6.2, save and reload gets lost already, hence not saved, hence not imported in 3.7. In a 4.x score that does set measure stretch, it'd import correctly in 3.7. |
|
Actually item 3 is not just about the individial stretch of a measure (that seems a bug in Mu4, see above), but also about Format > Style > Measure > Stretch, which have different defaults, 1.2 in Mu2 and 1.5 in Mu4, but apparently do get imported as 1.5 in 3.7. As we're reading in score_style.mss, we're getting all the Mu4 defaults. Guess we'd need s similar mechanism as when reading a 2.x or pre 3.6 score, i.e. read in a defaults style file on Mu4 import. |
|
Thanks for recognizing Item1, which is really too much work to adjust all of thousends of elements in a score...
Item2 seems to have the same name in Mu4 (see screenshot). Mu4 also imports a Mu3.6 score absolut correctly (due to the same style), so it seems to be an import problem in Mu3.7.
Item3: In Mu4 everything is well placed, the line breaks are at the correct positions (see screenshot of the first few lines in the first score page in Mu4 and then in Mu3.7). So it is definitively an import error in 3.7, probably also upscaling all elements (notes, rests, bars, ..) to be fae too big or too wide and then not having the room on a line as it had in Mu4.
|
|
Reg item 1: all these manual positioning are and always have been a problem when going from one major release to the other. Well. internally, in the score, for item 2 the tag changed from For item 3 there are 2 parts, the individual measure stretch, which apparently gets lost and the default setting for the measure distance, the former to me is a Mu4 import bug. It shows them directly after imporet, but no longer after a save/close/reopen |
|
I guess I found the cause for item 1, the offsets: |
|
There are a lot of other styles not importing:
Staff text style Expression (completely missing)
Style Dynamics
Style Tempo
...
...
Crescendo Line Type Crescendo Hairpin (completaly missing)
Crescendo Line Type Crescendo Line (Line Style Custom dashed)
and probably many more.
All existing/defined styles may be checked, if they do import or not and if yes then with which parameters. I know, that's complicated, but many thanks again.
|
|
I did not change anything in settings.
I just imported a 3.6.2-score to 4.1.1, saved it there and reimported that to 3.7.
In 3.6.2 and in 4.1.1, all elements are present and scaled correct.
After back import to 3.7 many elements are missing (eg. crescendo lines or expression texts) and the cached elements are upscaled. I don't know where the scaling change effectively is done but i think it should be adapted/corrected at the back import.
|
|
Where can this space setting be found?
|
I know, but we can only import those that do have a 3.x counterpart. I do see quite many that don't and I don't see any that do have a counterpart but have a different name, so nothing we can do about this.
Well, you did, your scores uses a space setting of 1.4, the default is 1.7.5 (and was 1.7.64 prior to 3.6)
Format > Page Settings > Scaling > Space |
|
These offsets are correct, when extracting and using the mscx, but not when using the mscz, so the difference must come from the score_style.mss, some style setting thai is now somehow either different or treated differently between Mu3 and Mu4. Just which one???
OTOH on importing the mscx, that "Spatium" value is set to default (as are all others), 1.75, the sample score here though is using 1.4, and that's being used when reading the mscz, and the ratio between both is exactly the factor we see here. But then again changing the Spatium to 1.4 doesn't fix those offsets |
|
Ok, that are program setting values or defaults which is an other thematic.
Our problem is, that x/y-positioning coordinate values get somehow scrambled during the import process, instead of leaving all the numbers untouched or unchanged, so the imported elements leave exactly at the same point in that measure where they are referenced to.
|
|
The problem with those x/y -positions definitly is related to these style setting, I just haven't yet found how and to which. Proof is that they are wrong only when reading the mscz (and along with that the style settings), but not when reading the mscx (and with that taking all the Mu3 defaults), which does not change those positions. But yes, it is not about those default settings, not neccesarily at least OK, it definitly is the Spatium setting, as soon as I load this minimal style file: <?xml version="1.0" encoding="UTF-8"?>
<museScore version="4.10">
<Style>
<Spatium>1.4</Spatium>
</Style>
</museScore>on top of the mscx, I do get those wrong positions. Now need to find why this behaves differently... |
|
Ok, but offset positions and spacers are relative numbers for any spatium (or overall page) scaling, so the numbers should not be changed or rescaled during any import procedure. In the same way manually changing the spatium (page) scaling should not affect relative offsets and spacer lengths. Is there a way to "compensate" the unwanted rescaling during import, if the actual spatium setting is known or read first or last? Note: Importing Mu3 scores to Mu4 as well do NOT rescale offsets and spacers (but correctly import the spatium setting), so it should be expected vice versa. |
|
A workaround is to reset the Spatium to 1.75 in Mu4, before importing the score in Mu3, and then in Mu3 set it to the desired value. |
|
Yes shure, but I think that's not a real option for the mass of world wide people. It would need an instruction.
|
|
I'm well aware of that |
|
An other question: Why does the import of Mu3-mscz-scores work correctly on that behavior? Doesn't it pass exactly the same import/opening procedure sequence as reading Mu4-mscz-scores for interpreting all the tags? |
|
No. Mu4 files always contain all style settings, Mu3 files only the ones chyanged away from the default. Hmm, hold on, that might be the trick... That nailed it!! (along with another small change) See #195 I'll still deal with those other default changes, separately |
|
I just tried out the release MuseScore-3.7.0.6340026096-x64. For the Mu4.x-import feature now it only remains issue #174 where all informative texts get lost. Hope this can be fixed as well now, so that Mu4.x-import then will get to a fairly stable feature. Thanks. |
|
Stretch seems to get lost in Mu4 already, on Mu3 score import. On the way back it should work, so it seems there's a bug in Mu4 |
|
OK,I'll merge #195 then |
|
The lost of stretch has been reported upstream now, see musescore#19625 |
Issue type
File corruption
Bug description
Mu3 opens Mu4 mscz files with wrong scaled element distances
[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.
Steps to reproduce
Screenshots/Screen recordings
Mu3 opens Mu4 mscz files with wrong scaled element distances.zip
MuseScore Version
3.7.0.6132193596
Regression
No.
Operating system
Windows10 and 11, 64-bit
Additional context
A test score and several screenshots may be found inside the attached ZIP.
The text was updated successfully, but these errors were encountered: