Re: Switching to drummode and back

[foxfanfare]

Hi everyone,

I'm currently working on a score in which I'd like to alternate from drums
notation to instrument.

I found this topic which explained how to make this, but in my case, I would
like to start the score with the percussion line. 

If I take the previous exemple given by Malte and uncomment the first line,
it doesn't work :

\new Staff \with {
   \accepts DrumStaff
} {
   %\repeat unfold 8 {e''8}
   \drums {
 hh4. r4. hh4
 % else an additional clef would be printed
 \once \omit DrumStaff.Clef
   }
   \clef bass d1 e f g
} 

The notes after the bass clef are all the same, except when the staff didn't
start directly with the \drums occurence.

How could I solve this?



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching to drummode and back

[David Kastrup]

foxfanfare  writes:

> Hi everyone,
>
> I'm currently working on a score in which I'd like to alternate from drums
> notation to instrument.
>
> I found this topic which explained how to make this, but in my case, I would
> like to start the score with the percussion line.

Well, you'll need to remove the first clef from the Staff line then or
reverse the context order (namely enclose in a DrumStaff).

> If I take the previous exemple given by Malte and uncomment the first line,
> it doesn't work :
>
> \new Staff \with {
>\accepts DrumStaff
> } {
>%\repeat unfold 8 {e''8}
>\drums {
>  hh4. r4. hh4
>  % else an additional clef would be printed
>  \once \omit DrumStaff.Clef
>}
>\clef bass d1 e f g
> } 
>
> The notes after the bass clef are all the same, except when the staff didn't
> start directly with the \drums occurence.

The problem here is that the DrumVoice context doesn't end since it is
the first context in the first context started in the sequential
iterator.

You can force this using

\new Voice { \clef bass ... }

since the \new Voice can only be created in the enclosing Staff
(\context Voice does not work since it would accept the Voice alias from
the existing DrumVoice context).

Alternatively, you can write
<< \drums { ... } >>

since the parallel music iterator blocks the magic continuation of the
first context from leaking into the sequential music around it.  That
is, well, sort-of hackish.  I know what happens here but don't really
have a good idea what technical problems that mechanism is intended to
solve.  Probably making sure that when writing
\new Staff { { ... } { ... } }
that the second sequential expression (which could be unavoidable
because of being returned by a music function)  does not start a new
Voice, disrupting slurs and ties.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching to drummode and back

[foxfanfare]

David Kastrup wrote
> The problem here is that the DrumVoice context doesn't end since it is
> the first context in the first context started in the sequential
> iterator.
> 
> You can force this using
> 
> \new Voice { \clef bass ... }
> 
> since the \new Voice can only be created in the enclosing Staff
> (\context Voice does not work since it would accept the Voice alias from
> the existing DrumVoice context).
> 
> Alternatively, you can write
> << \drums { ... } >>

Thank you David, both solutions works well!
What would be best if I want to write some ryhthmic passages on 1-line and
alternate with normal 5-lines pitch notation:

1) use a RhythmicStaff (but when I do so, it fails to engrave only 1 line)
2) keep a DrumStaff and change the number of lines with \stopStaff and
\startStaff?



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching to drummode and back

[foxfanfare]

for illustration, this works but I wonder if it is the "easiest" way to do
it:

\new Staff \with {
   \accepts DrumStaff
} {
  \override Staff.StaffSymbol.line-count = #1
  \clef percussion
  \drums {
hh8 8 8 8 8 8 8 8 }
  
  \stopStaff
  \new Voice {
\override Staff.StaffSymbol.line-count = #5
\startStaff
\clef bass
\key bes \major
c4 d e f g
}
} 



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching to drummode and back

[David Kastrup]

foxfanfare  writes:

> David Kastrup wrote
>> The problem here is that the DrumVoice context doesn't end since it is
>> the first context in the first context started in the sequential
>> iterator.
>> 
>> You can force this using
>> 
>> \new Voice { \clef bass ... }
>> 
>> since the \new Voice can only be created in the enclosing Staff
>> (\context Voice does not work since it would accept the Voice alias from
>> the existing DrumVoice context).
>> 
>> Alternatively, you can write
>> << \drums { ... } >>
>
> Thank you David, both solutions works well!
> What would be best if I want to write some ryhthmic passages on 1-line and
> alternate with normal 5-lines pitch notation:
>
> 1) use a RhythmicStaff (but when I do so, it fails to engrave only 1 line)

> 2) keep a DrumStaff and change the number of lines with \stopStaff and
> \startStaff?

I have no idea what you try doing here.  A RhythmicStaff uses normal
notes on a single line for showing rhythms.  A DrumStaff uses several
different noteheads in a fiveline system for showing different drum
types.

Your example uses drummode (and drum types that are not typeset on the
middle line) with a single line.  Which makes no real sense.

So first you need to decide what it is that you actually want to convey,
and then pick your recipe accordingly.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Cannot PNG capture with Frescobaldi macOS 10.13.5

[Joshua Nichols]

I have tried to use the PNG capture feature in the viewer on Frescobaldi
and it will no longer work. It was working literally one moment before. Any
ideas what to do? I did a fresh install of Frescobaldi before pasting the
error below.

Traceback (most recent call last):
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.5/frescobaldi_app/musicview/__init__.py",
> line 312, in copyImage
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.5/frescobaldi_app/copy2image.py",
> line 57, in copy_image
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.5/frescobaldi_app/copy2image.py",
> line 108, in __init__
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.5/frescobaldi_app/copy2image.py",
> line 150, in readSettings
> TypeError: unable to convert a QVariant of type 10 to a QMetaType of type
> 67


Any ideas? Thanks!

--
Josh
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Cannot PNG capture with Frescobaldi macOS 10.13.5

[Andrew Bernard]

HI Joshua,

As per normal, it would be most helpful if you provide version information
for the operating system and Frescobaldi, and any other Pythons you have
that may be involved. Otherwise it's a bit hard for people to help and/or
replicate.

Andrew


On 20 June 2018 at 00:30, Joshua Nichols  wrote:

> I have tried to use the PNG capture feature in the viewer on Frescobaldi
> and it will no longer work. It was working literally one moment before. Any
> ideas what to do? I did a fresh install of Frescobaldi before pasting the
> error below.
>
> Traceback (most recent call last):
>> File "/Applications/Frescobaldi.app/Contents/Resources/lib/
>> python3.5/frescobaldi_app/musicview/__init__.py", line 312, in copyImage
>> File "/Applications/Frescobaldi.app/Contents/Resources/lib/
>> python3.5/frescobaldi_app/copy2image.py", line 57, in copy_image
>> File "/Applications/Frescobaldi.app/Contents/Resources/lib/
>> python3.5/frescobaldi_app/copy2image.py", line 108, in __init__
>> File "/Applications/Frescobaldi.app/Contents/Resources/lib/
>> python3.5/frescobaldi_app/copy2image.py", line 150, in readSettings
>> TypeError: unable to convert a QVariant of type 10 to a QMetaType of type
>> 67
>
>
> Any ideas? Thanks!
>
> --
> Josh
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

omit fingering

[Gianmaria Lari]

On the accordion scores to indicate that the button to press is on the
counter bass we put a small dash under the finger number. This is how David
Kastrup suggest me to do it:

\version "2.19.81"
{a_\markup \underline \finger 3}


This is perfect.

But, is there any way to make it removed when I specify  "\omit Fingering"
like in the following example:

\version "2.19.81"
{\omit Fingering a_\markup \underline \finger 3}


?
Thank you, Gianmaria
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: omit fingering

[David Kastrup]

Gianmaria Lari  writes:

> On the accordion scores to indicate that the button to press is on the
> counter bass we put a small dash under the finger number. This is how David
> Kastrup suggest me to do it:
>
> \version "2.19.81"
> {a_\markup \underline \finger 3}

I did?

>
>
> This is perfect.
>
> But, is there any way to make it removed when I specify  "\omit Fingering"
> like in the following example:
>
> \version "2.19.81"
> {\omit Fingering a_\markup \underline \finger 3}
>
>
> ?

\version "2.19.81"

\new Voice \with { \omit Fingering }
{a\finger \markup \underline 3}

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Ties across voices

[Shachar Shemesh]

  
  
On 17/06/18 21:14, Simon Albrecht
  wrote:

I moved
  Tie_performer along, since you were talking about the importance
  of accurate MIDI for your use case. I don’t use MIDI (or hardly
  ever) so I can’t test reasonably, but it should work, I imagine.
  
  

It does. Thank you.

I will point out that the documentation for those is somewhat
lean.

Anyways, this solution is both correct and produces a clean source
code. Definitely the best one.

Maybe it's a good idea to amend the documentation to say that it is
possible to create ties across voices.

Shachar
  


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching to drummode and back

[Aaron Hill]

On 2018-06-19 06:41, foxfanfare wrote:
for illustration, this works but I wonder if it is the "easiest" way to 
do

it:

\new Staff \with {
   \accepts DrumStaff
} {
  \override Staff.StaffSymbol.line-count = #1
  \clef percussion
  \drums {
hh8 8 8 8 8 8 8 8 }

  \stopStaff
  \new Voice {
\override Staff.StaffSymbol.line-count = #5
\startStaff
\clef bass
\key bes \major
c4 d e f g
}
}


To indicate a single backing rhythm between melodic phrases, I would 
just use a CueVoice and slash notes:



  \version "2.19.81"
  melody = { s2. s8 e'16 f' | g'8 16 16~ 16 8 16~ 4 s4 }
  rhythms = { b'8. 16 4 r4 16 16 s8 | s2. 16 8. }
  \new Staff <<
\new Voice \melody
\new CueVoice
  \with { \override NoteHead.style = #'slash }
  \rhythms
  >>


This might be "easier" than switching back and forth between staff types 
and clefs, providing you don't need the expressiveness of an actual 
DrumStaff.


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Ties across voices

[Karlin High]

On Tue, Jun 19, 2018 at 12:03 PM, Shachar Shemesh  wrote:
> I will point out that the documentation for those is somewhat lean.

> Maybe it's a good idea to amend the documentation to say that it is possible
> to create ties across voices.

You just might be the best-qualified person to write such an amendment.



"A formal patch to the source code is not required; we can take care
of the technical details."

Writing an email and providing a documentation reference is all it
takes to get started.
-- 
Karlin High
Missouri, USA

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching to drummode and back

[foxfanfare]

Thanks for your answers. Here is the example of what I'm trying to typeset:

\version "2.19.81"

#(define cross '((snare cross #t 0)))

\new Staff \with {
  \accepts DrumStaff
}

\relative c' {
  \override Staff.StaffSymbol.line-count = #1
  \clef percussion
  \numericTimeSignature
  \time 4/4
  
  \drums \with { 
\remove Time_signature_engraver
\remove Clef_engraver } 
  {
\stemUp
\override Score.MetronomeMark.padding = #3.5
\tempo "Marziale"
\set DrumStaff.drumStyleTable = #(alist->hash-table cross)
\grace { sn16 16 16 16 }
sn8\ff 8 r4 
\grace { 16 16 16 16 }
sn8 8 r4 |
sn2:32 8 8 r4 |
sn8. 32 32 4:32~ 8 r r4 |
 }
  
  \new Voice {
\stopStaff
\override Staff.StaffSymbol.line-count = #5
\startStaff
\clef treble
\key bes \major
R1 |
r2. \tuplet 3/2 { bes'8( d f) } |
g2. \tuplet 3/2 { c,8( es g) } |
bes2~ bes8[ \breathe 
\shape #'((0 . 0)(0 . 0.25)(0 . 0.25)(0 . 0.25)) Slur
c,(-- es-- ges])-- |

\time 6/4 
bes2~ 
1\< ~ |
8\! r r4 r2 r \bar "|."
}
  }

This is a saxophone part, and I wanted him to play the rhythm of the first 3
measures (probably with sticks). I thought it was best to have this part
only on one line since it isn't written for multiple pitched drums.

This solution works but it is the first time I write for percussions and I
don't know if it is the "good" way to achieve this. As the RythmicStaff was
allready meant to use only one line, I wondered if it wasn't more
appropriate?

Also any suggestions on the correct way to engrave this exemple would be
very appreciated! I didn't find where E. Gould could pproach this problem.



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: omit fingering

[Gianmaria Lari]

On Tue, 19 Jun 2018 at 19:01, David Kastrup  wrote:

> Gianmaria Lari  writes:
>
> > On the accordion scores to indicate that the button to press is on the
> > counter bass we put a small dash under the finger number. This is how
> David
> > Kastrup suggest me to do it:
> >
> > \version "2.19.81"
> > {a_\markup \underline \finger 3}
>
> I did?
>
Yes :) This is what you wrote me on  June 13 2017

DK>Here are a few versions:
DK>
DK> \version "2.19.60"
DK> {\clef bass c,_3 d,_\finger "3x" e,_\markup \underline \finger 3 }


> >
> >
> > This is perfect.
> >
> > But, is there any way to make it removed when I specify  "\omit
> Fingering"
> > like in the following example:
> >
> > \version "2.19.81"
> > {\omit Fingering a_\markup \underline \finger 3}
> >
> >
> > ?
>
> \version "2.19.81"
>
> \new Voice \with { \omit Fingering }
> {a\finger \markup \underline 3}


Thank you David it works! And it works also if I don't specify \new Voice
like in the following.

\version "2.19.81"
{ a\finger \markup \underline 3
  \omit Fingering
  a\finger \markup \underline 3}


Can I use \omit Fingering like I did or I shouldn't?
Thank you, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: omit fingering

[David Kastrup]

Gianmaria Lari  writes:

> On Tue, 19 Jun 2018 at 19:01, David Kastrup  wrote:
>
>> Gianmaria Lari  writes:
>>
>> > On the accordion scores to indicate that the button to press is on the
>> > counter bass we put a small dash under the finger number. This is how
>> David
>> > Kastrup suggest me to do it:
>> >
>> > \version "2.19.81"
>> > {a_\markup \underline \finger 3}
>>
>> I did?
>>
> Yes :) This is what you wrote me on  June 13 2017
>
> DK>Here are a few versions:
> DK>
> DK> \version "2.19.60"
> DK> {\clef bass c,_3 d,_\finger "3x" e,_\markup \underline \finger 3 }

I did not express a preference between the different versions or
explained the difference?  Maybe I should have.

>> \version "2.19.81"
>>
>> \new Voice \with { \omit Fingering }
>> {a\finger \markup \underline 3}
>
>
> Thank you David it works! And it works also if I don't specify \new Voice
> like in the following.
>
> \version "2.19.81"
> { a\finger \markup \underline 3
>   \omit Fingering
>   a\finger \markup \underline 3}
>
>
> Can I use \omit Fingering like I did or I shouldn't?

Sure.  I tend to use \with when expressing something that I want to hold
for the whole lifetime of a context.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: how to created related tempo marks

[Stefan Thomas]

Dear Simon,
thanks for Your answer. Your solution is what I hat in mind!

2018-06-09 20:32 GMT+02:00 Simon Albrecht :

> On 09.06.2018 12:44, Stefan Thomas wrote:
>
>> I would like to create related tempo marks. For example, in bar 1 I would
>> like to have a tempo 4=60, some bars later tempo 4=90.
>> The tempi are in the proportion 3/2. I would like to write something like
>>
>> TempoA = {\tempo 4 =60}
>> TempoB = \TempoA*1.5
>>
>> I want to create a midi-file with metronome clicks of a piece with many
>> time signature and tempo changes and I want to practise with this file. I
>> want to be able to practise in different tempi and I don't want to retype
>> all the tempo changes again and again.
>> Is it possible to define tempo-relations in scheme?
>>
>
> Hi Stefan,
> how about this?
>
> %%
> bpmA = 60
>
> {
>   \tempo 4 = \bpmA
>   c'1
>   \tempo 4 = #(* 3/2 bpmA)
>   c'
> }
> %%
>
> Best, Simon
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Cannot PNG capture with Frescobaldi macOS 10.13.5

[Andrew Bernard]

Apologies - your subject has the Mac OS version. Missed that in my haste.

What version of Frescobaldi?

Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching to drummode and back

[Aaron Hill]

On 2018-06-19 12:55, foxfanfare wrote:
This is a saxophone part, and I wanted him to play the rhythm of the 
first 3
measures (probably with sticks). I thought it was best to have this 
part

only on one line since it isn't written for multiple pitched drums.


As an aside, I really hope you subtitle this part "sax'n'stix".  :)

Multi-line staves are not just for pitched percussion.  The standard 
trap set is written to five lines, for instance.  Of course, if you have 
only one instrument, a single line is certainly sufficient.


I have never encountered a mixture of staff types as in your example; 
but that said, I probably wouldn't be that confused by it.  It certainly 
does help make the part stand out, but I would argue the "cross" note 
head alone would be enough.  So, I would probably stick with the 
five-line normal staff and just annotate the percussion notes suitably 
anytime they appear.


Another thing to consider: Is this stick part a recurring thing in the 
song or just part of the introduction?  If the latter, you might 
consider typesetting the parts independently of each other.  Have the 
first system on the page be a simple RhythmicStaff (or DrumStaff), and 
then break for a normal melodic Staff for the rest of the song.  You'll 
need to correct the measure numbering, but otherwise it might be a 
cleaner way to do it from the perspective of the .ly file.


This solution works but it is the first time I write for percussions 
and I
don't know if it is the "good" way to achieve this. As the RythmicStaff 
was

allready meant to use only one line, I wondered if it wasn't more
appropriate?


As in English grammar, I ascribe to a descriptivist approach where there 
is rarely a definitive, singular "right" way to communicate.  That is, 
as long as your notation is able to relay your ideas clearly enough for 
musicians to follow and produce a desirable outcome, it is by all means 
sufficiently correct.  On the other hand, if your notation ever confuses 
people or becomes an obstacle, then it needs improvement.


At the end of the day, you could always take what you have (or an early 
preview) and see if your instrumentalist likes it or not.  Unless you 
are preparing something for a wide and unknown audience, you probably 
have more latitude than you realize.


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

dynamics and line spanning

[Reilly Farrell]

Hi All,

Is there an easy way to configure dynamics and markup text so that they
occupy they share the same vertical alignment relative to the staff?  My
hope is that I can align regular dynamic marks with special dynamic
instructions (\cresc won't cut it in this case) as seamlessly as possible.
Example below:

c1\p c1 c1\markup{\italic { cresc. poco a poco } } c1

Any assistance is appreciated.  Thank you!

-Reilly
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: dynamics and line spanning

[Pierre Perol-Schneider]

Hi Reilly,

How about :

\version "2.19"
<<
  \new Staff { c1 1 1 1 }
  \new Dynamics { s1\p s s-\markup { cresc. poco a poco } s }
>>

Cheers,
Pierre

2018-06-20 6:24 GMT+02:00 Reilly Farrell :

> Hi All,
>
> Is there an easy way to configure dynamics and markup text so that they
> occupy they share the same vertical alignment relative to the staff?  My
> hope is that I can align regular dynamic marks with special dynamic
> instructions (\cresc won't cut it in this case) as seamlessly as possible.
> Example below:
>
> c1\p c1 c1\markup{\italic { cresc. poco a poco } } c1
>
> Any assistance is appreciated.  Thank you!
>
> -Reilly
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user