Unwanted barree finger in fret diagram

Why is there a barre sign in these fret diagrams? Far as I cn see, I haven't told LP to do a barre finger in teh first fret ... minimal example, this time I hope: \version "2.18.2" \paper{#(set-default-paper-size "a4") indent = 0 top-margin = 0\cm left-margin = 1\cm right-margin = 1.5\cm

Re: Unwanted barree finger in fret diagram

I cannot answer your question as you use another syntax for fret duiagrams as I do. (I do not want to analyse this ...) But may be you find http://lsr.di.unimi.it/LSR/Search?q=barre from the The LilyPond Snippet Repository helpful? Regards On 08.09.2015 11:38, ClausRogge wrote: Why is there a

Help with Auto-beaming rules

The attached bit of 18th century typesetting shows an 8.[ 32 32] beamed group and a series of 32[ 32 32 32] beamed groups in a 2/4 time signature. This is quite typical of the period and is IMHO more legible than if the 1/32 notes were beamed in larger groups. Can this be done by auto-beaming

Re: Unwanted barree finger in fret diagram

Thank you! Solved the issue ... funny that I didn't come across this earlier -- View this message in context: http://lilypond.1069038.n5.nabble.com/Unwanted-barree-finger-in-fret-diagram-tp180816p180820.html Sent from the User mailing list archive at Nabble.com.

Re: Unwanted barree finger in fret diagram

2015-09-08 12:08 GMT+02:00 Phil Holmes : > This is closer to minimal to illustrate the issue: or even: \markup { \fret-diagram #"1-0;" } %% unwanted output \markup { \fret-diagram #"1-o;" } > > You are using zero, for example "6-0". If you check the manuals you will > see

Re: Unwanted barree finger in fret diagram

If you use an "o" for open String it works as obviously expected. Use s1 s1^\markup{{\fret-diagram #"s:6;h:3;6-o;5-x;4-x;3-o;2-3;1-o;"}}s1\break instead of s1 s1^\markup{{\fret-diagram #"s:6;h:3;6-0;5-x;4-x;3-0;2-3;1-0;"}}s1\break For me it does not work with "0" (=zero)! Regards On

Error when using musicxml2ly - how to proceed ?

Dear Lilyponder, a couple of years ago I created a score in Sibelius that I now would like to continue to work on with Lilypond. I thus have exported from Sibelius (7.1.3) in MusicXML and tried to import in Lilypond using musicxml2ly (2.19.26). Unfortunately I get an error (see attached

Re: Unwanted barree finger in fret diagram

- Original Message - From: "ClausRogge" To: Sent: Tuesday, September 08, 2015 10:38 AM Subject: Unwanted barree finger in fret diagram Why is there a barre sign in these fret diagrams? Far as I cn see, I haven't told LP to do a barre

Re: Help with Auto-beaming rules

Hello Richard, Am 08.09.2015 um 13:43 schrieb Richard Shann: The attached bit of 18th century typesetting shows an 8.[ 32 32] beamed group and a series of 32[ 32 32 32] beamed groups in a 2/4 time signature. This is quite typical of the period and is IMHO more legible than if the 1/32 notes

Re: what's wrong with \partial

Hi Jinsong, I seem to have completely misunderstood your intentions, reading the other posts. To my eye, you wanted the \partial 2 and so two notes in the upbeat, but the others took the bar check as having precedence, so assumed one note in the upbeat! Anyway, you can do most anything you

Re: Error when using musicxml2ly - how to proceed ?

On Tue, 2015-09-08 at 21:25 +0200, Martin Tarenskeen wrote: > > On Tue, 8 Sep 2015, Richard Shann wrote: > > > Just in case it is of use to you I attach the LilyPond conversion that > > Denemo does from your MusicXML, there are some bugs in there but I think > > the vast bulk of the notes are

Re: Error when using musicxml2ly - how to proceed ?

On Tue, 8 Sep 2015, Richard Shann wrote: Just in case it is of use to you I attach the LilyPond conversion that Denemo does from your MusicXML, there are some bugs in there but I think the vast bulk of the notes are there for you to work with, separated into voices. I know Denemo only by

Re: Voice split across staves?

Am 08.09.2015 um 22:47 schrieb Joel C. Salomon: I’m trying to re-create John Crook’s original score to Peter Pan (yes, it’s in the public domain) Just a sidenote: I tried to find this John Crook or any detail about his life on the web and he seems to be famously obscure – there’s no

midi channel

Hello! I'm new to lilypond and trying to arrange mulit-voice (e.g. bigband arragement). this works find, only for the midi playback the channel assignment of the staffs does not always do what I expect it to do. Is there any way to assign explicit midi channels to voices (or staffs)? E.g. like

Voice split across staves?

I’m trying to re-create John Crook’s original score to Peter Pan (yes, it’s in the public domain) for the Mutopia project, and I’m finding that my lack of musical education is getting in the way. I’m trying to set “Pipe with the Ostrich”, as visible at

RE: Voice split across staves?

Joel: Does this work for you? (see attachment) Mafrk -Original Message- From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Joel C. Salomon Sent: Tuesday, September 08, 2015 1:48 PM To: LilyPond Users

Re: Voice split across staves?

Hello Joel, Am 08.09.2015 um 22:47 schrieb Joel C. Salomon: I’m trying to re-create John Crook’s original score to Peter Pan (yes, it’s in the public domain) for the Mutopia project, and I’m finding that my lack of musical education is getting in the way. I’m trying to set “Pipe with the

Re: Error when using musicxml2ly - how to proceed ?

Dear Michael, What I've found is that exporting and importing xml works best for single parts - so I would recommend exporting each part as an xml file and then including them in your lilypond score. I've even found that piano parts generally work better when each hand (and sometimes each

Re: Help with Auto-beaming rules

I've seen contemporary scores that follow the following basic rules: All notes within the pulse value (say, a quarter-note in 4/4) are beamed into one group. If the total group has values shorter than a 16th (this includes 16th-note tuplets) then only the first beam carries across the whole

Re: hide and omit behaviour

Noeck writes: > Thanks David, > >>> Not sure pushing things back is part of the "\once" functionality. >> >> It isn't. Correct. Plain context properties don't have either stack or >> the subproperty complications of \override, so \once\unset, as opposed >> to

Re: hide and omit behaviour

> I've decided to have a go at it. There is now an issue 4596 in our > tracker (currently at > ) with a patch > that should have made your > > \once \undo \omit ... > > approach work as expected. Hi David, I've seen the issue and

Re: Unwanted barree finger in fret diagram

Marc Hohl writes: > Am 08.09.2015 um 12:31 schrieb Thomas Morley: > [...] >> Do we want >> \markup { \fret-diagram #"1-0;" } %% unwanted output >> keep working? >> I can't imagine a use-case right now. > > IIRC, 1-o means "display first string as open string", and it is common >

Re: midi channel

Rob gmx.de> writes: > for the midi playback > the channel assignment of the staffs > does not always do what I expect it to do. > \new Staff \with { midiChannel = 1} > That control does not yet exist, but there are requests in the bug-tracker

Re: Voice split across staves?

Joel C. Salomon gmail.com> writes: > my specific > question is how best to show what seems to be a voice split across > staves. The following example should show what I mean: I’ve set the > piece’s first bar twice, the first time as seems logical to me, the > second time as it appears in the

Re: Error when using musicxml2ly - how to proceed ?

Just in case it is of use to you I attach the LilyPond conversion that Denemo does from your MusicXML, there are some bugs in there but I think the vast bulk of the notes are there for you to work with, separated into voices. Richard On Tue, 2015-09-08 at 14:47 +0200, Michael Gerdau wrote: >

Re: Unwanted barree finger in fret diagram

Am 08.09.2015 um 12:31 schrieb Thomas Morley: [...] Do we want \markup { \fret-diagram #"1-0;" } %% unwanted output keep working? I can't imagine a use-case right now. IIRC, 1-o means "display first string as open string", and it is common to mark open strings with a "0" (zero) within a score,