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

"Bar object assigned to all voices will be encoded on voice 1" #197

Open
th-we opened this issue Oct 2, 2022 · 1 comment
Open

"Bar object assigned to all voices will be encoded on voice 1" #197

th-we opened this issue Oct 2, 2022 · 1 comment
Assignees

Comments

@th-we
Copy link
Member

th-we commented Oct 2, 2022

This message is not very useful because it is printed too often and it's hard to work through all the occurrences based on the list. Instead, the user could be given the option (via dialog) to color all the problematic objects red so it's easier to fix things manually.

@rettinghaus and me discussed this briefly during the technical team workshop in Berlin. Any objections to creating a pull request that implements this, @ahankinson?

(This is independent of whether the message is actually sensible or not, like for tempo text where it does not make sense to attach it just to layer 1.)

@ahankinson
Copy link
Member

So far the sibelius exporter has avoided actually changing anything in the source score. I would like to keep it that way, so that it doesn't actually change anything in anyone's scores. Many people who use the plugin assign some specific meaning to color in order to aid later processing -- like the DuChemin project, that used colours for different readings. If we start messing with colours in the plugin, we might overwrite some of this work.

That said, I'm not opposed to a separate tool to help people fix their scores. Would you be willing to write this into a separate plug-in that we distribute with sibmei?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants