I cannot create a new bug report
When I click on '+ Add new issue' from page musescore.org/en/project/issues/musescore (see first picture), I am taken instead to my own user profile at musescore.org/en/user/20870 (see second picture)...
In case it saves time, the 2 bugs I would like to report are:
1) When 'Create multibar rests' option is checked on a score/part (within menu option Style, General and first tab 'Score'), if I attempt to insert a line or page break on a multibar rest, Musescore 2.1.0 (revision 871c8ce) crashes... I know that under Musescore 1.*, this worked correctly (break was inserted after the last bar of the multibar rest).
2) Print quality of PDFs exported (from all versions of Musescore) is inadequate for any score where demi-semi-quavers (3 beams) are required - the beams merge together in a single blotch. Even for other scores the quality is crude. There may be some method of specifying desired print quality which I am unaware of but currently my workaround is to export png format and import the pictures into Microsoft Publisher, from where I then export to PDF - which gives a far superior quality - but this is very time-consuming.
| Attachment | Size |
|---|---|
| Musescore.org_en_project_issues_musescore.png | 22.97 KB |
| musescore.org_en_user_20870.png | 33.36 KB |
Comments
To adjust the PDF export quality:: Edit Menu -> Preferences -> Export Tab:
PDF
Resolution: [ xyz dpi ]
In reply to To adjust the PDF export… by Ziya Mete Demircan
Many thanks for the tip Ziya. I am surprised though that I need to have 4x the dpi for PDF export - 1200dpi to get a quality that is acceptable but still less good than png at the default 300dpi setting. Even the 1200dpi PDF has beams that extend beyond the stems of the notes in many cases, creating what to me is an untidy/unprofessional appearance that I do not get with a png export.
1) How are you attempting to add the line break? I'm not able to reproduce problem here. Best to attach the score you are having trouble with (could be a problem unique to that score, or to something you commonly do if you see it in multiple scores) and give precise steps to reproduce the problem.
2) Also, I can't reproduce a problem on my system. So again, can you attach a score and steps to reproduce the problem? might also in this case be useful to attach the PDF you obtain. Could possibly be a problem with the viewer you are using. Also, be sure to use MsueScore's own PDF export, not any third party "PDF print driver" type of application.
Thanks Marco...
For issue 1), having put up with the crash for so long (changing the multibar preferences back and forth), I realize it may have been a few weeks since I tried it... and now it seems to be fixed. Great!
For issue 2), Ziya's tip helps a lot too, but still you can see that a png file at 300 dpi is better than a pdf at 1200 dpi (exported via MuseScore Export and viewed in Adobe Reader XI). Compare the attachments - have a close look at the beams in bars 168 & 170 (problem here seems to be stem slightly too short for the 3rd beam in PDF version).
As for the ability to report a problem directly, is it a bug, or is it that the ability to report formally is limited to developers?
In reply to Thanks Marco… by Toby Miller
The ability to report a problem is open to anyone. There seems to have been a glitch at some point that few saw. You can test it again, and if you still cannot use the issue tracker then report it again with your operating system and browser info. You can also test it on another browser if you have one. When you test it, just close the window before saving so you don't have a bogus issue that will be visible forever. It is preferred that you report a bug in the forums before posting an issue so others can verify it and possibly give hints on how to write it.
In reply to Thanks Marco… by Toby Miller
Even if there is some glitch with where "Help / Report a Bug" from within MuseScore sends you, it is always still possible to submit bug reports from the web site. Just click "Activity" in the top menu, then "Issue tracker".
Anyhow, I'm not seeing any obvious issues with the PDF you posted, even when I zoom way in on measure 168 or 170. Can you maybe post a screenshot showing it zoomed in on your system? Could be maybe just your PDF viewer not having optimal settings for screen display at high magnifications.
In reply to Thanks Marco… by Toby Miller
Also, no problem here. measures 168-170 looking good.
@Toby the bug with the "Add new issue" has been fixed. There was a browser cache issue which only occurred when logging in. If you were logged into the musescore.org site, this problem didn't occur. Anyhow, thanks again for reporting.