Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limitations with the copyright functionality in MU4 #14947

Open
oMrSmith opened this issue Dec 5, 2022 · 8 comments
Open

Limitations with the copyright functionality in MU4 #14947

oMrSmith opened this issue Dec 5, 2022 · 8 comments
Assignees
Labels
engraving feature request Used to suggest improvements or new capabilities needs design Design is needed P1 Priority: High

Comments

@oMrSmith
Copy link

oMrSmith commented Dec 5, 2022

As I regularly write arrangements for copyrighted songs,
most of them having longer multi-line copyrights,
I want to mention three issues with the copyright functionality
in Muse Score that still remain in version 4.

  1. By design it is not possible to change font and size
    of a copyright text without changing
    other footer or header text,
    like page numbering, as well.

  2. The field to enter the copyright
    shows only one line even though
    many if not most copyrights
    consist of several lines.

  3. There is no footer tag
    to insert a copyright
    only on page number 1
    which is not the same as "first page",
    if there is a tilte-page on page number 0.

Because of these issues I never actually use the copyright functionality
of Muse Score but rather create the copyright as a text frame unless
I'm writing a score which will be delivered with the individual parts.

I the future I would love to see further innovation on the copyright functionality in Muse Score...

From my user-perspective it could look like this:
Entering or editing the copyright happens inside the score via double click on "copyright"
and feels pretty much like editing a text frame. There is a copyright tab inside the style page,
which let's you specify text-font and size and on which pages the copyright shall appear.

@MarcSabatella
Copy link
Contributor

These would be good enhancements indeed. Meanwhile, though, there are better workarounds than resorting to text frames - you can use "font" tags in the footer to change size, you can paste multi-line text from elsewhere, and you add title pages separately. Note also, the copyright itself is always just the one line; the rest is just usage info should probably be entered into the footer separately. For more help with this, feel free to ask on the support forum.

@AntonioBL
Copy link
Contributor

AntonioBL commented Dec 6, 2022

Regarding item 1, as Marc said, you can somehow do something with a semi-hidden feature of MuseScore: you can use some sort of html tags to edit individual portions of a single text in headers and footers, see for example this old comment here (those tags still work in MuseScore 4, but not all of Qt rich text tags are supported)

@Tantacrul

This comment was marked as outdated.

@Tantacrul Tantacrul added needs design Design is needed feature request Used to suggest improvements or new capabilities labels Dec 6, 2022
@oktophonie
Copy link
Contributor

oktophonie commented Dec 7, 2022

It's certainly often desirable to have a copyright indication only on the first page (or just a different footer on p1 than on subsequent pages).

There is the ability to reference the copyright string from the score metadata and show it only on the first page with the $C tag. This can work, but poses a few difficulties (challenges with formatting etc), and also doesn't solve the problem of what do to if you want that on the first page but then something else on subsequent pages. (I encountered this recently: I needed a catalogue number centered on all pages except the first, where the catalogue number would appear right-justified, and the copyright text left-justified.)

The easiest way to do this would be by turning off the existing 'Show on first page' option and to manually insert a custom footer on that page.

We can do this with a text frame but that's problematic for a few reasons, including:

  • Text frames are hese are inserted in the flow of the music, i.e. after the last system on the page, so can move around if the layout changes; they also then appear in that same place in parts, where they will almost certainly interfere with the layout
  • They interfere with vertical justification
  • They don't appear at the actual footer position, but are padded against it, so won't be consistent with footers elsewhere. You can fudge this with offsets, but it's a pain

I'd propose implementing a new 'Footer' item, which is a special type of text frame which:

  • can be added anywhere in the score (for a copyright notice this would be at the very beginning)
  • will show at the bottom of the page on which that point occurs. It will appear at footer position if there is no footer present, or just above it ('bottom justified') if there is one. (Perhaps we make it configurable whether it just replaces any footer that is present on that page; that allows you to create copyright lines on subsequent pages, which may be useful if you are creating a compilation of songs/pieces)
  • remains attached to that point in the score, and appears in parts relative to that same point
  • can obviously have default space above and other style settings
  • can use the same tags as the existing Header/Footer do, so one can reference metadata

Note that this functionality can then also be used to create footnotes, though a proper implementation of such a feature (multiple footnotes on one page, specifying whether a footnote applies to specific instruments or to the whole system, etc) would require extra work.

Just a thought!

@oMrSmith
Copy link
Author

oMrSmith commented Dec 7, 2022

I'd propose implementing a new 'Footer' item, which is a special type of text frame which:

That sounds really good, I also like your idea of designing the footer as special type of text frame.

@oMrSmith
Copy link
Author

Regarding item 1, as Marc said, you can somehow do something with a semi-hidden feature of MuseScore: you can use some sort of html tags to edit individual portions of a single text in headers and footers, see for example this old comment here (those tags still work in MuseScore 4, but not all of Qt rich text tags are supported)

Thanks for the info! It works and is fairly simply.

@Tantacrul Tantacrul added this to Triage in MS4.X Design Tasks Feb 17, 2023
@iainhallam
Copy link

I'd propose implementing a new 'Footer' item, which is a special type of text frame which:

A proper ad-hoc footer frame would be awesome - I often need footnotes for critical editions, and being able to work around the current repeated footer's limitations for copyright would be great. I also like the idea of them stacking automatically in score order, followed by the repeating footer; that would make footnotes really easy to format.

@oktophonie oktophonie changed the title [MU4.xx] Limitations with the copyright functionality in MU4 Limitations with the copyright functionality in MU4 Feb 28, 2023
@marcstober
Copy link

Hi everyone, I was pointed here from https://musescore.org/en/node/286521. I was a little confused as that was a feature request for footnotes including a number or symbol (possibly even auto-numbered) as may be desired in more "academic" works, and the title of this issue and the request about copyright text above aren't exactly the same thing as the suggestion on the old tracker. Although, it seems to me that @oMrSmith's requirements could be easily satisfied with such footnote functionality (plus probably needing to hide the number/symbol). Should this issue be used to track the footnote functionality (that the page on the old tracker and @iainhallam and I want) and the title perhaps changed, or is this copyright text feature something that should be separate from footnotes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engraving feature request Used to suggest improvements or new capabilities needs design Design is needed P1 Priority: High
Projects
Status: Issues to fix
Development

No branches or pull requests

8 participants