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

problem updating \gre@stafflinefactor #1461

Closed
asbloomf opened this issue May 6, 2019 · 7 comments
Closed

problem updating \gre@stafflinefactor #1461

asbloomf opened this issue May 6, 2019 · 7 comments

Comments

@asbloomf
Copy link

asbloomf commented May 6, 2019

This was happening on 5.2.1

If \greconffactor is different than what the staff size is set to, it seems to cause a problem when loading the new space file. It multiplies by the staff size but divides by \greconffactor. Anyway I think that is what was going on. So if you have the staff size set to something big like 23 and the regular \greconffactor of 17, when you load the new spacing, \gre@stafflinefactor gets set to 31 (23 * 23 / 17). It's easy to workaround so it's not a big deal. I'm not sure if anything else is affected, but the line thickness was certainly quite noticeable.

@rpspringuel
Copy link
Contributor

It sounds like expected behavior. Your new spacing file should have its own \greconffactor. This variable indicates what size staff the gsp file assumes so that the distances loaded by the file can be scaled appropriately if a different staff size is currently in effect. This prevents odd order effects in changing staff size and loading custom spaces.

Example: I have a project for which I expect to print staves at 20. In designing a custom gsp file for the project I set \greconffactor to 20 so that I can enter custom spaces directly based on page measurements without any math for scaling. Later on, I create another project in which I want to include a scaled down version of one of the scores in the first project, say at size 10 (half scale). Because of \greconffactor, I can load my custom gsp file either before or after switching to size 10, and I never have to switch to size 20 (if that isn’t used elsewhere in the new project).

Sent with GitHawk

@asbloomf
Copy link
Author

asbloomf commented May 6, 2019

It didn't seem like expected behavior, but maybe it is. What confused me was that I got different behavior when I changed the order of \grechangestaffsize{17} and \greloadspaceconf{default} when switching back. It seemed to me that loading the spacing configuration wouldn't be dependent on what the staff size was set to but then it was. Anyway, like I said, now that I understand how it works it's not a big deal.

@asbloomf asbloomf closed this as completed May 6, 2019
@rpspringuel
Copy link
Contributor

Order effects are exactly what \greconffactor was implemented to avoid. If you saw one, then there's a bug to be worked out. Can you post a MWE which shows the order effect?

@rpspringuel rpspringuel reopened this May 6, 2019
@asbloomf
Copy link
Author

asbloomf commented May 7, 2019

I think this shows it. I set the staff size and then each time I load the default spacing, it makes the lines a little thicker.
mwe.pdf
mwe.tex.txt

@rpspringuel
Copy link
Contributor

That's definitely a bug. I'm in the midst of exams, and have my pre-ordination retreat next week, but I'll put this on the to-do list.

@rpspringuel
Copy link
Contributor

Fix is up (#1464). Please test and indicate if it is acceptable.

@asbloomf
Copy link
Author

asbloomf commented May 21, 2019 via email

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