Re: Frescobaldi on Arch Linux
Il 06/01/21 05:51, Andrew Bernard ha scritto: I see the same exact versions, but no PDF output displayed in the music view. Have not had this before. So the question is, how o troubleshoot this, having checked for versionitis? Hello, I encountered the same issue on Manjaro. I resolved it simply rebuiliding the python-poppler-qt5 package, a suggested in a comment in https://aur.archlinux.org/packages/frescobaldi. I hope this can help! Happy new year, Luca Andrew On Sat, 26 Dec 2020 at 21:44, damianlegassick wrote: if it helps... poppler, poppler-glib and poppler-qt5 here are all 20.12.1-1 python-poppler-qt5 is 0.75.0-4 from AUR
Hiding/unhiding empty staves
Hello,
The following snippet hides "empty" staves in a system. But how can I unset
this behavior for selected staves?
For example: I want to hide the empty staff in the second measure but in
the fourth measure I want to print the staff with its rest...
Thanks for your help!
upper = {
c'1 \break
r \break
c' \break
r
}
middle = { d'1 d' d' d'}
lower = { e'1 e' e' d'}
\score {
\new PianoStaff <<
\new Staff = "upper" \upper
\new Staff = "middle" \middle
\new Staff = "lower" \lower
>>
\layout {
\context {
\Staff \RemoveEmptyStaves
}
\context {
\PianoStaff
\remove "Keep_alive_together_engraver"
}
}
}
Re: Hiding/unhiding empty staves
Am Mi., 6. Jan. 2021 um 13:04 Uhr schrieb Paolo Prete :
>
> Hello,
>
> The following snippet hides "empty" staves in a system. But how can I unset
> this behavior for selected staves?
> For example: I want to hide the empty staff in the second measure but in the
> fourth measure I want to print the staff with its rest...
>
> Thanks for your help!
>
>
>
> upper = {
>
> c'1 \break
> r \break
> c' \break
> r
>
> }
>
> middle = { d'1 d' d' d'}
> lower = { e'1 e' e' d'}
>
>
> \score {
> \new PianoStaff <<
> \new Staff = "upper" \upper
> \new Staff = "middle" \middle
> \new Staff = "lower" \lower
> >>
> \layout {
> \context {
> \Staff \RemoveEmptyStaves
> }
> \context {
> \PianoStaff
> \remove "Keep_alive_together_engraver"
> }
> }
> }
Probably
http://lsr.di.unimi.it/LSR/Item?id=312
helps.
Cheers,
Harm
Re: Hiding/unhiding empty staves
On Wed, Jan 6, 2021 at 1:12 PM Thomas Morley
wrote:
>
>
> Probably
> http://lsr.di.unimi.it/LSR/Item?id=312
> helps.
>
> Cheers,
> Harm
>
Great, thanks!
Here's the patched code:
-
showMultiRests = {
\set Staff.keepAliveInterfaces = #'(
rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface)
}
hideMultiRests = \unset Staff.keepAliveInterfaces
upper = {
c'1 \break
r \break
c' \break
\showMultiRests r \hideMultiRests \break
c' \break
r
}
middle = { d'1 d' d' d' d' d' }
lower = { e'1 e' e' e' e' e' }
\score {
\new PianoStaff <<
\new Staff = "upper" \upper
\new Staff = "middle" \middle
\new Staff = "lower" \lower
>>
\layout {
\context {
\Staff \RemoveEmptyStaves
}
\context {
\PianoStaff
\remove "Keep_alive_together_engraver"
}
}
}
Re: Repeats with bar-engraver removed
Hi Laura, > The short answer is because I didn't know about \omit. > > The longer answer is that what I do now is a direct descendant of what I > figured out to do back in 1996 or so. At that time, the options were > very different from what they are now. And there was a lot less > support/documentation for how to write music without barlines. That makes sense! As someone with literally hundreds of scores engraved in various applications over more than three decades, I totally get the “inertia” factor… :) Nowadays, Lilypond has both \omit and \hide, each of which does a different and potentially useful thing. Just an FYI, in case you didn’t know! Best, Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www.kierenmacmillan.info ‣ email: kie...@kierenmacmillan.info
Re: Why does -dbackend=svg -dcrop remove system-system-spacing?
On Tue, Jan 5, 2021 at 11:31 PM David Wright wrote: > On Tue 05 Jan 2021 at 19:05:30 (-0500), Trevor Bača wrote: > > I love the functionality for cropped SVGs! (Added back in 2019, or around > > then?) > > > > Question: it appears that cropped multisystem SVGs remove all whitespace > > between systems. Is this supposed to happen? > > I think that removing all the margins is the functionality "crop" is > supposed to add to LP. To generate the equivalent cropped and packed > image without this facility would be quite tedious to do (unless > someone has a trick for doing it?). > > > %%% BEGIN %%% > > […] > > %%% END %%% > > > > Called with ... > >lilypond -dbackend=svg -dcrop test.ly > > ... produces test.cropped.svg as attached here. > > > > Screenshot: > > […] > > > > Seems like cropping should be around the edges of the image (rather than > > between systems)? > > If you just want to crop the whole page image, you can do that easily > at the end of a normal run with the usual utilities. If you require > LP to set the entire score on a single page, just use a very long > custom page (as in NR §4.1.2: width, then length). > I'm sorry; I don't understand. What I want Lily to do: remove whitespace from the *edges* of an SVG. What Lily actually does when -dcrop is set: removes whitespace from the edges *and from between all systems* of an SVG. So my question is: is Lily supposed to remove whitespace from *between* systems when -drop is set? -- Trevor Bača www.trevorbaca.com soundcloud.com/trevorbaca
Re: ANN: Frescobaldi 3.1.3
> On 5 Jan, 2021, at 5:22 PM, Davide Liessi wrote: > > If you are running macOS 11, I would be grateful if you could test the > application and report the results. I can confirm that basic operations seem to work. Will report back as I use further. ✝✝ Fr. Samuel, OSB (R. Padraic Springuel) St. Anselm’s Abbey 4501 South Dakota Ave, NE Washington, DC, 20017 202-269-2300 (c) 202-853-7036 PAX ☧ ΧΡΙΣΤΟΣ
Re: Why does -dbackend=svg -dcrop remove system-system-spacing?
On Wed 06 Jan 2021 at 11:34:24 (-0500), Trevor Bača wrote:
> On Tue, Jan 5, 2021 at 11:31 PM David Wright wrote:
> > On Tue 05 Jan 2021 at 19:05:30 (-0500), Trevor Bača wrote:
> > > I love the functionality for cropped SVGs! (Added back in 2019, or around
> > > then?)
> > >
> > > Question: it appears that cropped multisystem SVGs remove all whitespace
> > > between systems. Is this supposed to happen?
> >
> > I think that removing all the margins is the functionality "crop" is
> > supposed to add to LP. To generate the equivalent cropped and packed
> > image without this facility would be quite tedious to do (unless
> > someone has a trick for doing it?).
> >
> > > %%% BEGIN %%%
> > > […]
> > > %%% END %%%
> > >
> > > Called with ...
> > >lilypond -dbackend=svg -dcrop test.ly
> > > ... produces test.cropped.svg as attached here.
> > >
> > > Screenshot:
> > > […]
> > >
> > > Seems like cropping should be around the edges of the image (rather than
> > > between systems)?
> >
> > If you just want to crop the whole page image, you can do that easily
> > at the end of a normal run with the usual utilities. If you require
> > LP to set the entire score on a single page, just use a very long
> > custom page (as in NR §4.1.2: width, then length).
>
> I'm sorry; I don't understand.
>
> What I want Lily to do: remove whitespace from the *edges* of an SVG.
As I said, you run LP as normal, and then trim to taste. So, taking
your example, I ran it with
$ lilypond-2.21.80-1.linux-64/bin/lilypond --svg -dno-point-and-click Bača.ly
and then edited the first line of Bača.svg, resulting in Bača-trimmed.svg.
The end of the first line is modified from
width="210.00mm" height="297.00mm" viewBox="0 0 119.5016 169.0094">
to
width="192.00mm" height="297.00mm" viewBox="4.5 0 109.5016 169.0094">
which I did by inspection. As you use SVG files in your workflow,
I assume you can carry this out more easily and precisely¹ with some
particular tool. (I'm PDF-centric myself.) I only considered X because
I was inspecting the file on a landscape screen (and you didn't remove
the tagline anyway).
> What Lily actually does when -dcrop is set: removes whitespace from the
> edges *and from between all systems* of an SVG.
That's right, so that your file contains all the information,
unencumbered by margins, ready for some sort of further processing.
Obviously, I don't know what that will be in your case.
It reminds me of those PNG files that you find in browsers' cache,
which have a strip or grid of little images that are used internally,
either as a toolbar, or displayed sequentially like a movie.
> So my question is: is Lily supposed to remove whitespace from *between*
> systems when -d[c]rop is set?
AIUI yes. But this is policy: I await pronouncements from higher-ups.
¹ I believe the modifications need to be kept proportional, in order
to preserve the aspect ratio.
Cheers,
David.
\paper
{
system-system-spacing.minimum-distance = #20
}
\new Score {
c'1
\break
c'1
\break
c'1
}
Re: Why does -dbackend=svg -dcrop remove system-system-spacing?
Hello, On 06/01/2021 20:29, David Wright wrote: On Wed 06 Jan 2021 at 11:34:24 (-0500), Trevor Bača wrote: What I want Lily to do: remove whitespace from the *edges* of an SVG. As I said, you run LP as normal, and then trim to taste. So, taking your example, I ran it with $ lilypond-2.21.80-1.linux-64/bin/lilypond --svg -dno-point-and-click Bača.ly and then edited the first line of Bača.svg, resulting in Bača-trimmed.svg. The end of the first line is modified from width="210.00mm" height="297.00mm" viewBox="0 0 119.5016 169.0094"> to width="192.00mm" height="297.00mm" viewBox="4.5 0 109.5016 169.0094"> which I did by inspection. As you use SVG files in your workflow, I assume you can carry this out more easily and precisely¹ with some particular tool. (I'm PDF-centric myself.) I only considered X because I was inspecting the file on a landscape screen (and you didn't remove the tagline anyway). In term of particular tool, I personnaly use Inkscape for this task. This is probably far from optimal but it works nicely. For Inkscape < 1.0, the following: inkscape --without-gui --export-area-drawing --export-plain-svg=output.cropped.svg input.svg For Inkscape >= 1.0, the following: inkscape --export-area-drawing --export-plain-svg --export-filename=output.cropped.svg input.svg or in short: inkscape -Dlo output.cropped.svg input.svg I suppose there might be faster lighter tools for that and I would love to hear from them. Best, — Niols
Re: ANN: Frescobaldi 3.1.3
Hello Wilbert, Thanks for the updated version. Despite my best efforts and decades of experience with UNIX, I am utterly unable to get Frescobaldi document view working on current Arch Linux. The python-poppler-qt5 refuse to build with complex dependencies on sip that are beyond my ken. I am just alerting you to this. Others here seem to have got it working by rebuilding these dependencies, but Arch system, can vary widely as they are so customised. It's at the point that I have to use Ubuntu to use Frescobaldi, but this is not my desired outcome. I don't imagine anybody has the time or resources to solve this one, so I'll just abandon, having spent days on it. Not a complaint, just a notice. Again, thanks for all your work! Andrew
Staff space size
If staff height is 20 points, then what is the staff space size? Maybe I am overthinking this but suddenly I thought there may be some factor of including or not including the staff lines in the measurement. It is not immediately apparent to me where staff space is defined in the NR. Somebody help out my overworked brain! All the best to all for 2021. Andrew
Re: Staff space size
On 2021-01-06 6:41 pm, Andrew Bernard wrote: If staff height is 20 points, then what is the staff space size? Maybe I am overthinking this but suddenly I thought there may be some factor of including or not including the staff lines in the measurement. It is not immediately apparent to me where staff space is defined in the NR. Somebody help out my overworked brain! All the best to all for 2021. If you are open to looking at the code, see layout-set-absolute-staff-size-in-module in paper.scm. The default staff size is indeed 20pt. For a standard 5-live staff symbol, the staff height is 4 staff spaces. As such, a staff space is then by default 5pt. Note that this is not the actual space between ink rather it is the distance between staff lines *on center*. The actual whitespace measurement would then be the staff space less the staff line thickness. Line thickness is computed based on a linear interpolation. From a comment in feta-params.mf, the line thickness measured from reference scores was generally 0.5pt irrespective of staff size; however, it was determined that smaller staff sizes in LilyPond should use a little less ink. For the default staff space of 5pt, then line thickness is exactly 0.5pt. However, as staff space drops to 4.125pt, line thickness should only reduce to 0.47pt. -- Aaron Hill
