Re: Behavior of non-flag side with strictBeatBeaming

2016-01-14 Thread Urs Liska
Am 15.01.2016 um 08:49 schrieb Urs Liska: >> In solution G), I think that position 2 is really invalid. How can it >> > have a duration of 1/32 and 1/64 at the same time? > That's true. > I'll have to look into that (obviously the stem is also looking to the > right side and takes more beams tha

Re: Behavior of non-flag side with strictBeatBeaming

2016-01-14 Thread Urs Liska
Am 15.01.2016 um 06:52 schrieb Werner LEMBERG: >> I have pulled together a complicated example, which is engraved with >> a number of option combinations. For ease of discussion I have >> numbered the stems. > Thanks. My comments below are of general nature, not specific to > subdivisions. That

Re: Behavior of non-flag side with strictBeatBeaming

2016-01-14 Thread Werner LEMBERG
> I have pulled together a complicated example, which is engraved with > a number of option combinations. For ease of discussion I have > numbered the stems. Thanks. My comments below are of general nature, not specific to subdivisions. > B) and C) are with just subdivideBeams on, but with diff

Re: Behavior of non-flag side with strictBeatBeaming

2016-01-14 Thread Urs Liska
Am 15.01.2016 um 01:19 schrieb Simon Albrecht: > On 15.01.2016 01:09, Urs Liska wrote: >> F) is interesting as it*only* has strictBeatBeaming set. >> There is no subdivision in the middle of the beam (7-8) because >> subdivideBeams is not set. However, the beamlets at stems 2 and 10 force >> the

Re: Behavior of non-flag side with strictBeatBeaming

2016-01-14 Thread Simon Albrecht
On 15.01.2016 01:09, Urs Liska wrote: F) is interesting as it*only* has strictBeatBeaming set. There is no subdivision in the middle of the beam (7-8) because subdivideBeams is not set. However, the beamlets at stems 2 and 10 force the subdivisions 2-3 and 9-10, each resulting in the beam count

Re: Behavior of non-flag side with strictBeatBeaming

2016-01-14 Thread Urs Liska
Am 14.01.2016 um 12:33 schrieb Kieren MacMillan: >> So I suggest the following: >> >• Default behaviour is (as currently): point the extra beam to the side >> > with more stems (i.e. join them) >> >• strictBeatBeaming produces (as currently) the extra stemlet but (new) >> > joins the be

Re: Import pdf into Lilypond (no ocr/omr)

2016-01-14 Thread Rutger Hofman
On Windows, there is PDFtoMusicPro, which is (of course) not free. For Unix, it lets itself be installed under Wine. The free trial version only processes the first page of a document. Rutger On 01/14/2016 10:03 PM, T4b wrote: Hi, sorry if this has been asked before, didn't find anything. Is

Re: setting Notehead for a single chord which follows the custom Notehead

2016-01-14 Thread Ryan Michael
Precisely! Thank you! On Thu, Jan 14, 2016 at 1:04 PM, Thomas Morley wrote: > 2016-01-14 21:49 GMT+01:00 Ryan Michael : > > I am trying to use the triangle notepad for all of the notes in a chord, > but > > would not like the triangle notehead to appear anywhere else in the > score. > > > > I ha

Re: setting Notehead for a single chord which follows the custom Notehead

2016-01-14 Thread Thomas Morley
2016-01-14 21:49 GMT+01:00 Ryan Michael : > I am trying to use the triangle notepad for all of the notes in a chord, but > would not like the triangle notehead to appear anywhere else in the score. > > I have the following: > > > > \version "2.18.2" > > \relative { > \set shapeNoteSt

Import pdf into Lilypond (no ocr/omr)

2016-01-14 Thread T4b
Hi, sorry if this has been asked before, didn't find anything. Is there a free program which analyzes pdf files to produce Lilypond source code? That is, I don't mean analyzing raster graphics, I mean analyzing a pdf file (generated by some score writer) which already contains just instructions on

setting Notehead for a single chord which follows the custom Notehead

2016-01-14 Thread Ryan Michael
I am trying to use the triangle notepad for all of the notes in a chord, but would not like the triangle notehead to appear anywhere else in the score. I have the following: \version "2.18.2" \relative { \set shapeNoteStyles = ##(triangle triangle) 1~ 4 r16. e'32 fis,,8-> r8 b

Re: different margins for footer and music

2016-01-14 Thread Mike Solomon
> On Jan 14, 2016, at 10:27 PM, Robin Bannister wrote: > > Mike Solomon wrote: > >> I’d like to place page numbers to the left and right of the music’s margin > > How about duping \fill-line? > > evenHeaderMarkup = \markup \fill-line { > \with-dimensions #'(6 . 8) #'(0 . 0) > \fromproperty

Re: different margins for footer and music

2016-01-14 Thread Thomas Morley
2016-01-14 21:00 GMT+01:00 Mike Solomon : > Hey all, > > Is it possible to have different margins for the footer and for the music in > LilyPond? I’d like to place page numbers to the left and right of the > music’s margin but they seem to be flush with the music’s margin no matter > what marku

Re: different margins for footer and music

2016-01-14 Thread Robin Bannister
Mike Solomon wrote: I’d like to place page numbers to the left and right of the music’s margin How about duping \fill-line? evenHeaderMarkup = \markup \fill-line { \with-dimensions #'(6 . 8) #'(0 . 0) \fromproperty #'page:page-number-string \fromproperty #'header:title \with-dimension

different margins for footer and music

2016-01-14 Thread Mike Solomon
Hey all, Is it possible to have different margins for the footer and for the music in LilyPond? I’d like to place page numbers to the left and right of the music’s margin but they seem to be flush with the music’s margin no matter what markup hacking I try. Cheers, MS

Re: Ossia problem

2016-01-14 Thread Simon Albrecht
On 29.12.2015 17:32, Abraham Lee wrote: David, On Tuesday, December 29, 2015, David Kastrup > wrote: Ralph Palmer > writes: > Greetings - > > I'm running ly 2.19.33 under Win7. > > I'm trying to remove the first line of the ossia staff from the

Re: Behavior of non-flag side with strictBeatBeaming

2016-01-14 Thread Kieren MacMillan
Hi Urs, > Take the attached example "undivided". Of course the second line is easier to > read and therefore preferable Yes. > So I suggest the following: > • Default behaviour is (as currently): point the extra beam to the side > with more stems (i.e. join them) > • strictBeatBeam

Re: Behavior of non-flag side with strictBeatBeaming

2016-01-14 Thread Urs Liska
Am 13.01.2016 um 20:07 schrieb Pierre Perol-Schneider: > The second is simply the easiest to read. > HTH > Pierre > > 2016-01-13 18:59 GMT+01:00 Kieren MacMillan > mailto:kieren_macmil...@sympatico.ca>>: > > Hi Urs, > > > which of the attached engravings do you prefer, LilyPond's > cu