Problem with playback on musescore.com website
I recently uploaded a remastered version of one of my old arrangements onto the musescore.com website. When it plays back, however, the right hand of the piano part cuts out as soon as the piccolo comes in. Can anyone fix this?
Just so we're clear, the MuseScore app plays this back just fine, except for not playing back accents. It's the WEBSITE (won't let me use italics) that won't play it back properly. I couldn't find where to post a bug report for the website itself, so I posted it here.
Here's the link so you can hear it yourself: https://musescore.com/user/7146791/scores/8861688
I also added the file itself to show that it's not the app that's the problem.
Please fix this. The issue persists when I upload it to YouTube, which is really a problem.
Comments
So got to that website and report it there rather then here
This forum is for users of the software and no one from the .COM website reads the posts. i had a look at your piece online but I don't have a PRO subscription so couldn't download it - and you did not attach a file, although you said that you did in your post.
Despite any suggestions or redirections from the .COM site, this isn't a MuseScore.com helpdesk. - oops, I did italics.
In reply to The forum is frequented by… by underquark
I clearly did attach a file, but let me try again.
And I don't know where the help desk is for MuseScore.com.
In reply to I clearly did attach a file,… by 2142Kitch
See How and where to ask for support
In reply to I clearly did attach a file,… by 2142Kitch
From measure 10 onwards, your piano top stave has velocities set to 15. Since everything else is set to 64 this makes the piano top stave virtually inaudible.
In reply to From measure 10 onwards,… by underquark
In MuS 3.7 I see that it is set to Offset 15, which means that it is 15 louder. And this is also how it is played in 3.7.
In reply to In MuS 3.7 I see that it is… by HildeK
Interesting. In 4.2 it shows as just Velocity and increasing to the same as other notes it makes the notes as audible as them. The score was created in 4.2, so does this mean that 4.2 and 3.7 assign velocities differently or that 3.7 interprets 4.2 file's velocities differently?
![Screenshot_20240414_093615.png]( "Screenshot_20240414_093615.png")
In reply to Interesting. In 4.2 it shows… by underquark
But isn't there a way in MuS 4 to differentiate between 'User' and 'Offset' for the velocity type?
In reply to But isn't there a way in MuS… by HildeK
No
In reply to But isn't there a way in MuS… by HildeK
Seems Offset isn't supported in Mu4 and gets changed into User, without calculating from (i.e. adding to) the default dynamic at the point.
Looks like a pretty bad import problem in Mu4 for Mu3 scores
And a known one, see https://github.com/musescore/MuseScore/issues/14768
In reply to Seems Offset isn't supported… by Jojo-Schmitz
So if the default setting in MuS 3 is USER=0, everything is imported correctly into MuS 4 and every time USER has a non-zero value, it is interpreted as an absolute value? Strange!
Surely you can't keep putting off the problem until later? It was already mentioned as a ToDo for 4.0 and is now on the list for 4.4 ...
In reply to So if the default setting in… by HildeK
Apparently they can...
In reply to I clearly did attach a file,… by 2142Kitch
The score stems from 3.x (creation date 22Oct2022 and (initial) upload onto musescore.com, 4.0.0 got released 14Dec2022). Do you still have the 3.x version?
In reply to I clearly did attach a file,… by 2142Kitch
Actually (also) from a musicxml import, so the musicxml file would be uesfull too
In reply to Actually (also) from a… by Jojo-Schmitz
Actually none needed, it is a known issue, see above
So turns out it is not at all a musescore.com issue