"Arranger" Slot
Hi, I'd really appreciate an "Arranger" slot in the score setup wizard. While it's easy to add a line under the composer's name after you've left the wizard, musescore.com creates an unnatural look when you have something like:
Composer: Blah Blah Arr. Blah Blah
I think other users would appreciate it as well. Thanks for reading. :)
Comments
Good idea,
I support this a lot, I really could use this on my current project.
In reply to Great Idea by techdude42
Just to be clear, there is nothing stopping you from adding areangers info to the composer field, or adding a new field. Somif you need this, it's already possible. Adding it to the wizard would just be a matter or maybe ssving a click or two..
In reply to Just to be clear, there is by Marc Sabatella
I have found that when editing the composer info in the score, adding a carriage return after the composer and then adding the arranger, the two lines no longer print right-justified. It looks fine on screen. Note this was in 1.2, 2.0 may work better.
In reply to I have found that when by schepers
??? Is your Composer text style set to right justify? Could you post a sample score? I've never seen any problems with right justification.
In reply to ??? Is your Composer text by Marc Sabatella
Marc, this only happens when I print or export a PS file, not on screen or PDF or PNG export. This field is always right-justified, it's just a bug I noticed quite a while ago in 1.2. Version 2.0 seems OK.
In reply to Marc, this only happens when by schepers
Interesting - does it happen on all scores or just some? What OS? Are we talking off by just a couple of pixels, or just completely off? I've never experienced this at all. Wonder if maybe there is some sort of special setting you have somewhere on 1.2 that is triggering this. And it would be good to make sure the same setting won't trigger it on 2.0.
In reply to Interesting - does it happen by Marc Sabatella
I always notice it when adding an extra line to the Arranger slot. It seems to depend on the length of the lines being added. Short lines compared to the previous line are aligned OK, longer ones start to indent. I've done a factory reset and changed no settings and am on Windows 7 32-bit.
This is the MuseScore 1.2 window. Note the correct alignment of the text entries with the right edge of the box.
This is the PS export (same as the printout). Note the indenting of the lines, and the lack of alignment right from line 1.
In reply to I always notice it when by schepers
Seeing the actual score would help, of course. But this appears to be a font issue. Note that the left edges of each line are aligned pretty much exactly the same in both cases. What's different is that the characters are closer together in the PS export version. It seems the kerning info is being interpreted differently between the two, casuing MuseScore to insert more space between the characters on screen display than was used in PS the export.
Which is to say, it's not an issue with this field in particular, or with right alignment per se. This seems to be a case of inconsistent font handling on this particular font on this particular OS. My recollection is that kerning is handled by Qt and the specifics vary between OS's, but indeed, a version of Qt used in 2.0 is newer and should have fewer issues like this.
In reply to Seeing the actual score would by Marc Sabatella
The score I used was just by creating a new score and adding some text to the various fields in the wizard, then adding a linefeed to the composer text in the score and adding extra text. Try it yourself with varying line lengths.
Both my 1.2 and 2.0 are custom compiles and both use QT 4.8.0. Since 1.2 has the issue (and has for some time, I think I saw this in 1.1) and both have the fonts built-in, something else is different between 1.2 and 2.0. It's really a non-issue anyway since 1.2 is "dead" and 2.0 doesn't seem to have this issue.
In reply to The score I used was just by by schepers
That's the thing - I use right justified text often, and haven't seen that sort of effect before. So I wouldn't consider it a non-issue until it's understood a bit better, since on first glance at least, it doesn't affect all 1.2 users in the same way, so it obviously depends on some factors we don't yet know. Meaning it's hard to say for sure it is still immune to this effect on 2.0.
I've done a bit more investigating and found this:
1) I don't normally use Times New Roman, but I find I *can* reproduce what you see using that font
2) I don't normally generate PS files, but I often generate PDF, and PDF generation does not have this issue even with Times New Roman
3) the existing issues in the tracker I found that relate to this all seem to point to Qt issues and/or MacOS issues, but the fact that you are using a self-compiled 1.2 and I believe you are a Windows user, leads to me to think something else must be going on
In reply to That's the thing - I use by Marc Sabatella
Yes, I am a Windows user. I generally work with the defaults and Times New Roman is the default font for a lot of text, so I am surprised no one else has seen this. I am only generating PS files right now because, from my experiments, it produces the same effect as printing. However PDF, as it is not PostScript, doesn't do this.
Maybe because I am printing to a postscript printer, I would have to check... I just printed to a non-postscript printer and Times is still wacky, so the type of printer is not likely the issue. I tried Arial and the problem was definitely better, but still evident. I changed to Adobe Garamond Pro and it worked great.
So if I export to a PDF, the problem is gone. This seems to be the catch-all fix when having printing issues.