Ugly Musescore to Youtube Upload

• Nov 29, 2023 - 00:46

All the scores that I have published on musescore.com, when I send them to youtube, they got completely twisted and bent, basically the whole format of the scores is lost, this is mainly because the engine is not taking in consideration the proper spacing and system/page breaks of the scores, resulting in ugly and messy (unlegible) scores.

this is my youtube channel with some examples
https://www.youtube.com/channel/UC8eTDA5lcUyoPi8ljAfiNWA


Comments

I think we need to see what the scores are supposed to look like. Unless that's what the images are for. They different. Have you tried scores that show the rests and aren't so color coded? Just as an experiment?

In reply to by yonah_ag

Thank you for the suggestion, yes I could edit them manually but I am talking specifically about this problem which is a feature of both musescore.com and musescore.org and nobody seems to even grasp, being so simple to depict and to demonstrate!

In reply to by yonah_ag

Clearly I dont think "all you" grasp the issue, not even remotely. And indeed, it NEEDS a fix. It's not by design. I don't want it to work in any strange and personal kind of way. I want to be fixed in order for me and for probably millions of people need to work as expected. I am not talking about as enhacement, I am talking about a bug or failure, or misbehaviour or however you might want to call it

It is expected behaviour that the video feature does not follow the page view layout. It basically uses a version of "continuous view". The reason is that the page size is never 16:9, which is what would be required for a video.

In reply to by cbjeukendrup

thats not the issue, if you format a score, the expected behaviour should be that you see in the video the elements the way you set them, thats whats an editor is for. the video engine renderer or whichever process in charge of converting the systems/staves/measures is not taking in consideration some of the formatting elements, like page or system breaks specially. the conversion from a4 to 16:9 should be automatically done, but they keep getting this wrong

In reply to by Jojo-Schmitz

Well it should do! The "send to youtube" thing appears on musescore.com but the render engine/software depends on musescore.org (the program notation) not the musescore.com portal.
Anyhow, the Send to youtube function always works bad, 9 out of 10 times, the end result its messy, horrible to the view, and it's just junk

In reply to by al brin

" but the render engine/software depends on musescore.org (the program notation) not the musescore.com portal."
I would think this would be so if the "send to YouTube button was in an open score in MU4. Even .com makes changes to a score before it appears on the .com site. So that site is the last one with the score.
.Org isn't really involved.

In reply to by bobjp

That's what i thought in the first instance, but after sending hundreds of requests without any success, i've talked with Simon which works in the engraving/notation section in Musescore and he confirmed that even though the "send to youtube" appears on M.com the render work is done "somehwere" in M.org servers and then transferred back to M.com

In reply to by al brin

No, the rendering for musescore.com is done in the MuseScore backend (a Linux version or MuseScore Studio) on musescore.com.
And that does honor the layout.
Then there's the rendering engine of the mobile apps, which indeed does not honor the layout, but uses a floating layout. And that is closed source.

In reply to by Jojo-Schmitz

either way, the end result is not doing any honor to the score, as you can find on my examples and try for yourself if you just upload a score and then send it to youtube, the end result does not only "not respect" the layout that you gave, but also messes all the elements making the end result, simply and plainly useless.

"No, the rendering for musescore.com is done in the MuseScore backend (a Linux version or MuseScore Studio) on musescore.com." That's what i am trying to explain to all of those that don't get it, despite the fact that M.com offers that "send to youtube" function, the real rendering work is done through some kind of "musescore editor" if you will. The problem here is that the issue affects both M.com and M.com in I would say equal parts, and none of them are taking account for it

In reply to by al brin

That only makes partial sense to me.
On the .com site there is an upload option. have you tried uploading an mscz file from there? How could the .org servers do anything with a file that never had anything to do with them. I wonder what kind of rendering is happening.
I get that something is not doing a good job of something, somewhere along the line.

In reply to by bobjp

The issue is not as simple as it could look like in the first instance, and that's what i am trying to explain, this issue affects both M.com and MStudio. I've tried all possible combinations for more than three years now with the exact same result.
Look for the image references for better understanding

In reply to by al brin

I don't think that you get to define what it "should do": it's your opinion and the developers have a different opinion. It is not unreasonable to have a standard YouTube format which is independent of the MS WYSIWYG layout.

You could raise a request for other options and, if there is sufficient interest, then it will get implemented.

I wanted more control so I took the approach outlined above. Sure, it's not fully automated but it doesn't take long.

In reply to by yonah_ag

What you think have nothing to do with the problem. It's not my opinion. It's a bug, which makes youtube scores unreadable, and when you work with an editor, the minimum you expect is that the end result is at least close to what you tried to express. There's not any "standard" youtube format as you imagine, very probably the idea is simple "send your score to youtube" with one click, but the end result is completely unlegible. Even though Musescore is "free" I've paid for M.com subscription and with the same result. Try to navigate youtube in search of a single musescore video and you will have a hard time even finding one. That speaks for itself, the feature "send to yotubue" is cheap, wacky, doesnt respect the format that you give to the score most of the times, and most importantly, the end result is ugly and unreadable, nasty, and is a waste of time each time.
Of course i can export my score and edit all together in davinci resolve or some other editor, but i am not talking about that i am talking about "SEND TO YOUTUBE" button that works just as a pile of trash. That doesn't need an enhacement, that would be for example, adding different colors to the score, or formatting your video export in some way, but this is not an enhacement request., This is a very badly implemented function that nobody cares to fix, and i am not talking about some minor issue that affects minority i am talking about something that is as important as it would be if it worked properly.

In reply to by al brin

There may be a bug (or two) to fix in the rendering but the YouTube upload is not obliged to replicate your studio layout, this is up to the developers. It would be nice if it did but it doesn't have to. It does, of course, need to be legible.

Clarification: by "standard" I meant MuseScore's standard for rendering YouTube videos.

Your subscription pays for download of some copyrighted scores.

In reply to by yonah_ag

There are not one or two bugs, this is a massive fault in the whole "send to youtube" feature. Youtube clearly does not have anything to do with the issue, clearly, the rendering process gives the same result if you "download the video to your computer" or "upload to youtube"
This is not an issue discussing personal preferences of the developers, this is very important issue that affects all and each Musescore user. The developers should listen to the users and take actions if they are advised of so. That's how the community operates and that's exactly what I am doing here, reporting a "bug" in the space that is designated to. Either if you say "bug" referring at some specific programming issue or a "broken feature" this issue that i am referring applies for both.
And I am talking about the payment of subscriptions to clarify that even if I pay or not for a feature that the platform is offering, doesn't change the result. If you get something for free you usually can't demand things but if you were to pay for a product, you are fully qualified for demanding that the service or products work as expected. This is not some "experimental" kind of plugin or feature like those by google, this is a "fully developed" feature that they are offering in front of each score that you upload. This is not a minor one.

In reply to by al brin

If it's an issue with MS Studio then you need to report it on GitHub and wait for the developers to address it. You have not paid for MuseScore Studio, it is completely free, therefore, as you said, you are not entitled to demand anything. If the problem is with Studio then you will have to wait for the (mostly unpaid) developers to have time and inclination to fix it. If the problem is with the .com site then you are complaining in the wrong place as this is the .org site.

It doesn't affect all and each MuseScore user. It doesn't affect me and I would rather the developers worked on a piano roll editor and a fully fledged plugin api.

In reply to by yonah_ag

It is not an issue with MS Studio. It's an issue that goes way back in time, since Musescore 3x. I've reported the issue on GitHub also. I am not demanding anything I am just doing what i am explaining over and over again: Reporting a bug/misbehaviour/broken feature or whatever you want to call it, which has been depicted, and described fully in details. Before talking about time and inclination of the developers to fix it is important to address the problem. If each "M.com" user has a button that says "send to youtube" and when they click, the result is a completely ineligible, twisted and ugly to see "video-score", then each "M.com" user is affected by this.
If you would rather prefer the developers on working on different stuff, that's great. I am doing something very different, which is, again, reporting something that is not working properly in the place designated to. This issue goes beyond the scope of "M.com is not the same as M.org or Mstudio". And yes I did my research and I've reported the issue on GitHub, talked with people in higher positions, tried to reach many people in charge, and submitted reports on M.com as well.

In reply to by al brin

Firstly sincere apologies: I did get the wrong end of the stick. Sorry for the hassle.

If a user presses the button then they are affected. Not all users press the button, therefore not all users are affected. I have no idea what % of scorers use the send-to-youtube option.

If MS4/MS3 is the root cause then I'm sure they will fix it in the course of time. I know that they have limited resources so this can take a while.

If .com is the root cause then they may or may not fix it. My experience with them is that they are very slow and not really interested. I have been trying for years to get them to improve the rendering of TAB in the Android app because it is a shambles; probably worse than the YouTube rendering:

Screenshot_20241030-065556_MuseScore.jpg

This is what it should look like:

Screenshot_20241030-070133_Samsung Internet.jpg

I have no workaround, I only use TAB so I have no useable tablet app. They are not interested in fixing the issue. It's fair enough for them to impose some changes in the rendering, (e.g. no colour, no images, different layout), but it really should be legible.

In reply to by yonah_ag

hey there, so no problem bc this one is actually a bit tricky.
ok let's say "potentially" affected, if you will, bc almost zero people are using that function (maybe exactly because the issue that i am describing, which makes the whole render to video completely useless? maybe?)
Again this is not solely an issue with M.com and M.org, this is actually a very particular kind of problem. many people jump up to conclusions without doing proper research beforehand.
Will they fix this in the future? I hope so, they sey that they will do it, since idk how many years back.
Also had the same experience, they are not interested in fixing that, and they are pushing this whole MuseHub, Musesounds, and that fake "offer 400%off whatever" thing and many things that i particularly don't like, but that's another issue.
Anyhow, there are really thousands of "rendering" problems going on and they are so important, i get it, M4 is very different than M3, times change, and all of that. For the moment I am exposing this particular problem of the video rendering thing. I am sure that there are lots of different things to fix, imo there are lots of things to fix before jumping to new sounds, new UI, new platforms and all of that.
good luck!

In reply to by al brin

Agreed, it potentially affects every MS user.

Jojo has said that it is definitely a .com issue rather than with the MS Studio software. Since he has been a long term developer on the project, and is the main custodian of MS3.7 Evolution, I very much believe that he is correct. Sadly this leaves you in the same position that I am with the Android app: unusable rendering with little hope of a fix. So I make my mp4's manually for YouTube and can also use them on my Android tablet.

I wonder how difficult it is to write a replacement YouTube video generator. I will do some research but my C++ skills are rudimentary and my spare time for this is quite limited. Maybe there are 3rd party automation tools which would preserve the MS Studio rendering and send directly to YouTube.

There may be something promising in here:
https://filmora.wondershare.com/youtube-video-editing/record-screen-and…
They have a paid product to promote but also short reviews on other software, some of which appear to integrate video capture with send to YouTube.

In reply to by yonah_ag

Literal words by Jojo:

"No, the rendering for musescore.com is done in the MuseScore backend (a Linux version or MuseScore Studio) on musescore.com."

So if he is one of the main characters in this project, he is giving me the right: 1) The whole issue with the video rendering is located somehow in some version of MusescoreStudio (Editor). Therefore, I am right, this is the place to discuss the issue because this is musescore."org". stuff (editor) despite the fact that it goes through M.com servers or whatever.

Yes, i am in this sad position, in which If i want to make "youtube video scores" i have to do it manually, having everytime to see a giant "SEND TO YOUTUBE" button which is useless.

Again, if we were talking about some personal wish, or some 3d party plugin or whatever, ok then i would be trying to put nails in the air, but this is a "main" feature that doesnt work properly and belongs both to M.org and M.com departments.

I've put so much effort into making "good looking" scores, (as they should be), and what I am asking is that SOMEONE at least in charge, can grasp the depth of this issue, and yes I am no programmer, but if you see the scores rendered, you can catch immediately what's wrong with the rendering proccess, it all comes mainly to respect mainly the system and page breaks. I've been working for years with the software and with notation editors, so I am pretty sure what I am talking about.

So yes let's hope they fix this and many other issues. Sadly this is one of those situations in which only if a famous youtuber expose those things, they will fix it immediately.

In reply to by al brin

Yes, I can see that it is a main feature and is broken.

Jojo has been involved in development of the front end software, (i.e. the MuseScore score editor for .org), but I don't think that he has been involved in the back end (.com) server software. He is thus well placed to confirm that this rendering issue is not an editor (.org) related issue because he knows in detail the scope of the editor software.

The issue appears to lie squarely and wholly with the .com developers.

In reply to by yonah_ag

To end hopefully all confusion (and hopefully the stream of messages in my inbox):

First I'll outline all different components:

  • MuseScore Studio, the notation program
  • MuseScore.org, this almost-static website with info about MuseScore Studio
  • MuseScore.com frontend, the html/js/css that's loaded in your browser when you visit MuseScore.com
  • MuseScore.com backend, which does internal processing; for some parts of this processing, it uses MuseScore Studio

Each of these components is maintained by a different team.

The source code of the video export feature is in the MuseScore Studio repository. You might think that should make it possible to expose this feature directly to users, so that users can export videos directly from MuseScore Studio; but this is not possible. Why? Short answer: FFMpeg distribution is problematic for licensing reasons. (And trying to make MuseScore Studio work with external FFMpeg distributions is very difficult because FFMpeg updates keep breaking compatibility; I'm basing that on what I heard from the Audacity team, who are of course experienced in this area).

The precise location of the source code is https://github.com/musescore/MuseScore/tree/master/src/importexport/vid…; so if you want to contribute to it, you could take a look there (or you can use it to build a custom video export program, as long as you do that in a way that complies with MuseScore Studio's GPLv3 license).

About who is supposed to handle feature requests relating to the video export: that's unclear, because it's not really a MuseScore Studio feature, but it is part of the MuseScore Studio codebase. And both teams are busy with things that take priority over this feature. I don't know why anyone ever built this feature, because it's an absolute pain to maintain (partly because nobody has ownership over it, partly because of technical reasons). Anyway, you could try logging a feature request in the MuseScore Studio repository: https://github.com/musescore/MuseScore/issues/new/choose
That way, it's at least listed at some place where it will be seen. It won't mean there will immediately be a fix though, because, again, everyone is busy.

However, please don't abuse that GitHub link, and only create issues on GitHub when a Muse developer (or long-time contributor like Jojo or Marc) has told you to do so, because GitHub is the direct to-do list of the developers, so must stay as clear as possible (i.e. it's not a forum to discuss vague ideas or to discuss things that turn out to be support requests rather than bug reports, etc.).

In reply to by cbjeukendrup

If you look at two of hundreds of examples that i could give, you would find clearly that the end result is not good enough, the elements of the score (text elements, page and system breaks mainly among others) are running wild all over the page. If that "version" of "continuous view" that you are talking about, were working decently, at least the "render" should take in account the spacing and the breaks that you gave to the score, despite de fact if you set your page in the editor to 16.9 or any other ratio.

Some final thoughts.

I've never used the save to youtube function. So I tried it with three different scores. And got three different results. One seemed to be of the score as it would appear in MU4. Only the top several staves were shown. This might point to some use of MU4.
Another result was a blank screen except for a single measure at the bottom that scrolled through as the music played.
The third seemed normal.
But in general, none where what I was expecting. And as the OP pointed out, not really acceptable.
At this point, the answer would be to, as has been pointed out, use a 3rd party screen recorder. It might be a hassle, but worth it in the end.

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