Re: Distance of secondary beams

Hi Abraham, Am 17.01.2017 um 16:41 schrieb Abraham Lee: > Hi, Urs! > > On Tue, Jan 17, 2017 at 8:26 AM, Malte Meyn > wrote: > > > > Am 17.01.2017 um 11:43 schrieb Urs Liska: > > I don't find the appropriate property to modify the

Re: Distance of secondary beams

Am 17.01.2017 um 11:43 schrieb Urs Liska: > I don't find the appropriate property to modify the distance between > secondary stems. Attached you'll find the result of \override > Beam.beam-thickness = 0.15, and I need to adjust the beams to be closer > together, e.g. to 0.5 staff spaces. I don't

Re: Distance of secondary beams

Hi, Urs! On Tue, Jan 17, 2017 at 8:26 AM, Malte Meyn wrote: > > > Am 17.01.2017 um 11:43 schrieb Urs Liska: > > I don't find the appropriate property to modify the distance between > > secondary stems. Attached you'll find the result of \override > > Beam.beam-thickness =

Re: addFingering

David Wright wrote: > But your response here addresses a second point, the > interpretation of \repeat unfold. Looking at my attached > example, it seems to me that you want "\repeat unfold 2 { foo }" > to behave like "foo foo" (B and C). Yes, that's exact! > But, if that's what you want, >

Re: Distance of secondary beams

On 17.01.2017 22:23, Noeck wrote: PS: While we are at it: LilyPond has flags until 1/128 (5 ‘flaglets’). Shorter durations (1/256, 1/512, etc.) are actually understood and typeset when they have beams. I gave up checking after 1/131072 = 1/2^17. See my contribution to

brittenPhrygolydian

Hello everybody, this is a big thank you and a shout of joy over having LilyPond! The question came up about a curious key signature used by Britten, which indicates only Ab and C#, and how to replicate this in Sibelius. Which involves a fake clef, lots of manual work, and hidden accidentals

Re: brittenPhrygolydian

On 17.01.2017 22:42, Simon Albrecht wrote: Hello everybody, this is a big thank you and a shout of joy over having LilyPond! The question came up about a curious key signature used by Britten, which indicates only Ab and C#, and how to replicate this in Sibelius. Which involves a fake clef,

Re: Distance of secondary beams

> runtime of lilypond for 32768 notes For completeness: 65'25" => ~ 8 notes / second ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Distance of secondary beams

Thanks, Simon! That answers two questions of mine (the lilypond limit and the shortest note in published music). Mail mail lacked the runtime of lilypond for 32768 notes in the last sentence. Not really relevant, but it is still running after an hour. Cheers, Joram

Re: Distance of secondary beams

Hi Abraham, Am 17.01.2017 um 17:30 schrieb Abraham Lee: > > I'm not sure why the calculation for this is so convoluted. I am not sure if this is the "why" you are looking for (if this is the answer to what you were wondering about). But I think the equation can be explained by the following

Coda for piano without breaking the line?

Hey, I'm having a problem with inserting a coda in the piano setting. I used available coda snippet, but I want to insert the piano bracket as well (so it looks like fresh piano staff near the end of the line), not sure how to do this. Stopping and starting staff just prints clefs, can you just

cmn

Hi, did anybody know this: https://ccrma.stanford.edu/software/cmn/cmn/cmn.html? I saw it for the first time. Scheme syntax and some other features makes it look quite familiar. The images have a low resolution but that's not necessarily the fault of the program. I thought I mention it in case

128 beaming

Hi, is this a bug or done on purpose? The following snippet produces beams of which the lowest beam does not touch the staff line below. { g128[ g] } The small-gaps-fill-with-ink theory should avoid this. IMHO the output would look better like this: { \override Beam.positions = #'(2.7 . 2.7)

Re: [Frescobaldi] State of Frescobaldi development

Dear Friends, I apologize for being so silent in the Frescobaldi world the past months, and not taking the time to respond to some private e-mails, which I surely did read and highly appreciated! I had so many, and demanding, recitals with Christmas that I even didn't get out a new release... I

Re: Frescobaldi segfault with PyQt4-

Op Wed, 11 Jan 2017 22:36:06 +0100 "N. Andrew Walsh" schreef: > Hi List, > > I'm wondering if anybody is having recent issues with Frescobaldi. I > run a rolling-release distro (gentoo), so I install/update packages > on an ongoing basis. In this case, the only package

Distance of secondary beams

Hi all, I don't find the appropriate property to modify the distance between secondary stems. Attached you'll find the result of \override Beam.beam-thickness = 0.15, and I need to adjust the beams to be closer together, e.g. to 0.5 staff spaces. I don't see any promising properties in Beam and

Re: Frescobaldi segfault with PyQt4-

Hi Wilbert, python-poppler-qt4 no longer compiles on my system (I suspect due to incompatibility with recent ABI changes in sip, but I'm just speculating), so I'm trying to install frescobaldi and python-poppler-qt5 from your git repository. I'm encountering an error with python-poppler-qt5, in

Re: Frescobaldi segfault with PyQt4-

Am 17. Januar 2017 13:16:51 MEZ schrieb "N. Andrew Walsh" : >Hi Wilbert, > >python-poppler-qt4 no longer compiles on my system (I suspect due to >incompatibility with recent ABI changes in sip, but I'm just >speculating), >so I'm trying to install frescobaldi and

Re: Frescobaldi segfault with PyQt4-

Hi Urs, On Tue, Jan 17, 2017 at 1:31 PM, Urs Liska wrote: > > Ah, try to use SVG as a temporary workaround. > > Urs > > SVG output works (though, since I use a dark color scheme, the output appears as black on dark, which makes it hard to read. But I can cope with that for

Re: [Frescobaldi] State of Frescobaldi development

On Tue, Jan 17, 2017 at 4:08 AM, Wilbert Berendsen wrote: > Dear Friends, > > I apologize for being so silent in the Frescobaldi world the past > months, and not taking the time to respond to some private e-mails, > which I surely did read and highly appreciated! Thanks for all

Re: [Frescobaldi] State of Frescobaldi development

Hi Wilbert, On Tuesday, January 17, 2017 at 10:08:42 AM UTC+1, Wilbert wrote: > > Dear Friends, > > I apologize for being so silent in the Frescobaldi world the past > months, and not taking the time to respond to some private e-mails, > which I surely did read and highly appreciated! >