Re: fingering notation alternative

On 5 May 2018 at 17:18, Malte Meyn wrote: > > > Am 05.05.2018 um 16:33 schrieb Gianmaria Lari: > >> This is more a notation question than a lilypond question. >> >> Does exist a standard fingering notation to indicate that a note can be >> played for example with 2 or 3?

Re: fingering notation alternative

Am 05.05.2018 um 16:33 schrieb Gianmaria Lari: This is more a notation question than a lilypond question. Does exist a standard fingering notation to indicate that a note can be played for example with 2 or 3? I agree with David and Ralph: put them on top of each other or at oppisite

Re: fingering notation alternative

On Sat, May 5, 2018, 7:35 AM Gianmaria Lari wrote: > This is more a notation question than a lilypond question. > > Does exist a standard fingering notation to indicate that a note can be > played for example with 2 or 3? I normally write > > \finger "2(3)" > > or > >

Re: fingering notation alternative

Gianmaria Lari writes: > This is more a notation question than a lilypond question. > > Does exist a standard fingering notation to indicate that a note can be > played for example with 2 or 3? I normally write > > \finger "2(3)" > > or > > \finger "2/3" > > > but I'm

fingering notation alternative

This is more a notation question than a lilypond question. Does exist a standard fingering notation to indicate that a note can be played for example with 2 or 3? I normally write \finger "2(3)" or \finger "2/3" but I'm not sure this is correct. Thank you, g.

Re: DynamicText.X-offset in StaffGroups

Am 05.05.2018 um 11:23 schrieb Malte Meyn: > • or \override DynamicText.extra-spacing-width = #empty-interval for the > lowest Staff in a StaffGroup. That is very useful to know!  Also when the dynamics would actually cross a barline in combination with whiteout: violinIIa = \relative c'' {  

Re: {SPAM 04.7} Re: {SPAM 01.9} Re: Tie across voices

David Sumbler writes: > The automatic creation of contexts is obviously very useful, especially > when one is just a beginner at Lilypond.  But I almost wish that there > were an option to turn it off, which would be useful for forcing > oneself to understand how this all

Re: {SPAM 04.7} Re: {SPAM 01.9} Re: Tie across voices

On Fri, 2018-05-04 at 23:55 +0200, Simon Albrecht wrote: > On 04.05.2018 19:23, David Sumbler wrote: > > > > It seems that if, in a > > <<{\musicA} {\musicB}>> > > passage, \musicA does not specify a new Voice, then the music > > before > > the << >> passage and, importantly, also the music

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Hi Torsten, 5. Mai 2018 11:44, "Torsten Hämmerle" schrieb: > Hi Urs, > > Sibelius works fine: > > > Thanks. > > As my Dorico evaluation period has expired, I can't even start it. > All the

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Hi Urs, Sibelius works fine: As my Dorico evaluation period has expired, I can't even start it. All the others allow testing w/o save/export functionality, but Steinberg is much more restrictive in that respect. All the

Re: tenuto fingering: 3t, 2t, 4t, etc.

Il giorno ven 4 mag 2018 alle 12:16, Aaron Hill ha scritto: On 2018-05-04 05:19, Federico Bruni wrote: Perhaps a smart function may be created but as I need only 4 variations I can simply use 4 variables: unoT = \markup \concat { \finger 1 \fontsize #-2.5

Re: DynamicText.X-offset in StaffGroups

Am 05.05.2018 um 11:10 schrieb Malte Meyn: I think that’s a buggy feature: You’re right, this is to avoid collisions with SpanBars (the bar lines between staves) but of course there is no SpanBar above the highest or below the lowest Staff in a StaffGroup. It has been added in 2.19.0 as

Re: DynamicText.X-offset in StaffGroups

Am 05.05.2018 um 10:32 schrieb Thomas Weber: when I compile the below example with 2.18.2, I get the output that I want - the "pp" below the staff is offset as expected. When I compile with 2.19.54, more unnecessary space is created after the barline to avoid that the dynamic crosses below

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Sibelius 8.1.1 creates exactly the same beaming. Am 05.05.2018 um 09:38 schrieb Robert Blackstone: > Hi Urs, > > This is what your file produces with Finale 2024.5, on a MacBook with > OSX 10.9.5. > > > > (I should have compressed it a bit.) > > Best regards, > >

DynamicText.X-offset in StaffGroups

Hi all, when I compile the below example with 2.18.2, I get the output that I want - the "pp" below the staff is offset as expected. When I compile with 2.19.54, more unnecessary space is created after the barline to avoid that the dynamic crosses below the barline.  (See attached images.) Is

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Hi Robert, thanks for testing. Given that I'm not interested in the *looks* of it this is what I hoped to get :-) Thanks Urs Am 05.05.2018 um 09:38 schrieb Robert Blackstone: Hi Urs, This is what your file produces with Finale 2024.5, on a MacBook with OSX 10.9.5. (I should have

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Hi Urs, This is what your file produces with Finale 2024.5, on a MacBook with OSX 10.9.5. 05-beam_Finale_2014_5.pdf Description: Adobe PDF document (I should have compressed it a bit.) Best regards, Robert Blackstone > Hi, > > I'm trying to add support to python-ly for exporting manual

Need someone testing XML file in Finale and Sibelius (and Dorico)

Hi, I'm trying to add support to python-ly for exporting manual beams to MusicXML. I managed to export the commands to start and end a beam, but that's not sufficient. In theory (https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-beam.htm) the beaming pattern is described in