Volume Events Appearing In MIDI File
I had to re-install Lilypond and Frescobaldi on a new computer so they are much newer version than I had since I usually don't fix things that aren't broken :-) But I noticed now there are volume events in the MIDI outoupt that were not there before. I don't even remember what version I was running before, but now, when I bring the MIDI into Logic Pro, I can't set the volume channels because the volume events keep setting it back. I have to delete all the volume events for every MIDI file I bring in. Is this a new default behavior? Is there a way to have Lilypond not include volume events in the MIDI output? Thanks, Tim ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volume Events Appearing In MIDI File
Have you read http://lilypond.org/doc/v2.19/Documentation/notation/controlling-midi-dynamics#setting-midi-block-properties and tried removing the dynamic performer? -- Phil Holmes - Original Message - From: Mr Tim To: lilypond-user@gnu.org Sent: Saturday, May 18, 2019 2:37 PM Subject: Volume Events Appearing In MIDI File I had to re-install Lilypond and Frescobaldi on a new computer so they are much newer version than I had since I usually don't fix things that aren't broken :-) But I noticed now there are volume events in the MIDI outoupt that were not there before. I don't even remember what version I was running before, but now, when I bring the MIDI into Logic Pro, I can't set the volume channels because the volume events keep setting it back. I have to delete all the volume events for every MIDI file I bring in. Is this a new default behavior? Is there a way to have Lilypond not include volume events in the MIDI output? Thanks, Tim -- ___ 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
Re: tie four 8 note to 4 chord
Hi Ming, it depends on the music you are working with and your preference. I personally have it set to ##t as my personal default. I don't see the downside to having it turned on: if this happens often in your music it's cumbersome to keep setting and resetting it, and I also find that it helps to instantly spot input mistakes (if you have a tie flying all the way through your score you know you messed up somewhere). Hope that helps, Stéfano El vie., 17 may. 2019 a las 11:59, MING TSANG () escribió: > Andrew: > > Thank you very much. > > Once the tieWaitForNote = ##t is set, it continues to work. Is this the > intention? Is it necessary to reset to it's default? > > Thanks, > Ming > > On Thursday, May 16, 2019, 7:41:14 p.m. EDT, Andrew Bernard < > andrew.bern...@gmail.com> wrote: > > > Hi Ming, > > \set tieWaitForNote = ##t > > It's in the Notation Reference manual. > > Andrew > > > ___ > 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
Re: Volume Events Appearing In MIDI File
Thanks, Phil. That did the trick. On Sat, May 18, 2019 at 10:17 AM Phil Holmes wrote: > Have you read > http://lilypond.org/doc/v2.19/Documentation/notation/controlling-midi-dynamics#setting-midi-block-properties > and > tried removing the dynamic performer? > > -- > Phil Holmes > > > > - Original Message - > *From:* Mr Tim > *To:* lilypond-user@gnu.org > *Sent:* Saturday, May 18, 2019 2:37 PM > *Subject:* Volume Events Appearing In MIDI File > > I had to re-install Lilypond and Frescobaldi on a new computer so they are > much newer version than I had since I usually don't fix things that aren't > broken :-) But I noticed now there are volume events in the MIDI outoupt > that were not there before. I don't even remember what version I was > running before, but now, when I bring the MIDI into Logic Pro, I can't set > the volume channels because the volume events keep setting it back. I have > to delete all the volume events for every MIDI file I bring in. > > Is this a new default behavior? > > Is there a way to have Lilypond not include volume events in the MIDI > output? > > Thanks, > Tim > > -- > > ___ > 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
Re: tie four 8 note to 4 chord
Stefano & Andrew: Thank you for the solution and explanation. Thanks,Ming. On Saturday, May 18, 2019, 11:00:41 a.m. EDT, Stefano Troncaro wrote: Hi Ming, it depends on the music you are working with and your preference. I personally have it set to ##t as my personal default. I don't see the downside to having it turned on: if this happens often in your music it's cumbersome to keep setting and resetting it, and I also find that it helps to instantly spot input mistakes (if you have a tie flying all the way through your score you know you messed up somewhere). Hope that helps,Stéfano El vie., 17 may. 2019 a las 11:59, MING TSANG () escribió: Andrew: Thank you very much. Once the tieWaitForNote = ##t is set, it continues to work. Is this the intention? Is it necessary to reset to it's default? Thanks,Ming On Thursday, May 16, 2019, 7:41:14 p.m. EDT, Andrew Bernard wrote: Hi Ming, \set tieWaitForNote = ##t It's in the Notation Reference manual. Andrew ___ 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
Two simultaneous mark events
I'm often in this situation:
\version "2.21.0"
fine = {
\once \override Score.RehearsalMark #'break-visibility = #'#(#t #t #f)
\once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
\mark \markup \italic "Fine"
}
\fixed c' {
c d e f \bar "|." \fine \break
\mark A c c c c
}
So, I would like the text "Fine" at the end of the first measure (and in
this case at the end of the line) and the rehearsal mark "A" at the
beginning of the next measure (and in this case at the beginning of the
second line).
In the past I used some snippet I found on LSR giving the possibility to
write multiple rehearsal marks, but I was wondering if there is a simpler
way. Isn't this something happen frequently and so should be easy to do?
Thank you, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unconventional score and unwanted stray staff lines
Hi David, I think this may be easy to fix but neither of your examples compiles for me on Ubuntu 19.04 with Lilypond 2.19.83. Ghostscript crashes. I don't have this problem with other scores. Andrew On Sun, 19 May 2019 at 09:14, David Bellows wrote: > > I tried to keep the examples minimal but I also needed to show the > full extent of what is going on. > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Two simultaneous mark events
Why not just use markup for 'fine'? Position it as you wiil.
Andrew
On Sun, 19 May 2019 at 03:15, Gianmaria Lari
wrote:
> I'm often in this situation:
>
> \version "2.21.0"
> fine = {
> \once \override Score.RehearsalMark #'break-visibility = #'#(#t #t #f)
> \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
> \mark \markup \italic "Fine"
> }
>
> \fixed c' {
> c d e f \bar "|." \fine \break
> \mark A c c c c
> }
>
>
> So, I would like the text "Fine" at the end of the first measure (and in
> this case at the end of the line) and the rehearsal mark "A" at the
> beginning of the next measure (and in this case at the beginning of the
> second line).
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unconventional score and unwanted stray staff lines
Hey Andrew,
Hmm, I'm running Kubuntu 19.04. You wouldn't think there'd be that
much difference between the two? I also wouldn't think there would be
anything we could do in our Lilypond files to cause Ghostscript
problems for one file but not another.
I do wonder if maybe there's a spacing/indention issue? I've attached
less indented versions of both files -- maybe that'll help?
On Sat, May 18, 2019 at 6:07 PM Andrew Bernard wrote:
>
> Hi David,
>
> I think this may be easy to fix but neither of your examples compiles for me
> on Ubuntu 19.04 with Lilypond 2.19.83. Ghostscript crashes. I don't have this
> problem with other scores.
>
> Andrew
>
>
> On Sun, 19 May 2019 at 09:14, David Bellows wrote:
>>
>>
>> I tried to keep the examples minimal but I also needed to show the
>> full extent of what is going on.
>>
\version "2.19.83"
\language "english"
\pointAndClickOff
scoreinfo = {\time 4/4 \tempo "andante" 4 = 90}
voice_oneone = {\key c \major r64 r128 r4 r4 ds''1\p fs'64\ g4.\pp cs64\fff fs1\ gs2\pp c'32\fff r32%{%} \bar "|."}
voice_twoone = {\key c \major e,,64\mp cs128\ppp g4 gs4\fff r1 r64 r4. r64 r1 r2 r32 b,,32\p%{%} \bar "|."}
voice_onetwo = {\key c \major r1 fs'''4\ppp fs''4\p r64 r1. e\breve\ppp r1 r2.. d''4.\f r4 gs8\mf r2...%{%} \bar "|."}
voice_twotwo = {\key c \major d,1\ppp r4 r4 g64\pp g,,1.\mp r\breve d1\p e,2..\p r4. d,4\fff r8 a,2...\p%{%} \bar "|."}
voice_onethree = {\key c \major r4. r1 g'1.\pp ds'8\ppp r2... r1. cs'4.\fff r8 r4. fs'''2.\mf r128 as''64\ff%{%} \bar "|."}
voice_twothree = {\key c \major e4.\mp r1 r1. r8 e,2... r1. r4. r8 e4.\f r2. r128 r64%{%} \bar "|."}
voice_onefour = {\key c \major cs''2\mf e'''2.\p as''2\ f''64\mp r32 a1.\ a'''4.\ppp a'''2\p r8 fs''2\ e'1\ff cs8\p%{%} \bar "|."}
voice_twofour = {\key c \major r2 r2. r2 r64 b,32\ r1. r4. r2 g8\ r2 r1 r8%{%} \bar "|."}
voice_onefive = {\key c \major cs128\mf r32 r2 gs4\mp r4.. r8 r8 f'''4\p r4.. r64 gs'''\breve\p cs'''4\mf%{%} \bar "|."}
voice_twofive = {\key c \major r128 r32 as2 r4 gs4..\ff as,,,8\mf b,,,8\fff r4 r4.. c64\p r\breve r4%{%} \bar "|."}
\paper {#(set-paper-size "letter") }
\score { <<
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_oneone >>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twoone >>
>>
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_onetwo >>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twotwo >>
>>
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_onethree >>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twothree >>
>>
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_onefour >>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twofour >>
>>
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_onefive >>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twofive >>
>> >>
\layout{ragged-bottom = ##t
\context { \Score \remove "Timing_translator" \remove "Default_bar_line_engraver"}
\context { \Staff \consists "Timing_translator" \consists "Default_bar_line_engraver"}
\context { \Voice \remove "Note_heads_engraver" \consists "Completion_heads_engraver" \remove "Rest_engraver" \consists "Completion_rest_engraver" completionUnit = #(ly:make-moment 2/4)}}
}\version "2.19.83"
\language "english"
\pointAndClickOff
scoreinfo = {\time 4/4 \tempo "andante" 4 = 90}
voice_oneone = {\key c \major r64 r128 r4 r4 ds''1\p fs'64\ g4.\pp cs64\fff fs1\ gs2\pp c'32\fff r32 s128 \bar "|."}
voice_twoone = {\key c \major e,,64\mp cs128\ppp g4 gs4\fff r1 r64 r4. r64 r1 r2 r32 b,,32\p s128 \bar "|."}
voice_onetwo = {\key c \major r1 fs'''4\ppp fs''4\p r64 r1. e\breve\ppp r1 r2.. d''4.\f r4 gs8\mf r2... s128 \bar "|."}
voice_twotwo = {\key c \major d,1\ppp r4 r4 g64\pp g,,1.\mp r\breve d1\p e,2..\p r4. d,4\fff r8 a,2...\p s128 \bar "|."}
voice_onethree = {\key c \major r4. r1 g'1.\pp ds'8\ppp r2... r1. cs'4.\fff r8 r4. fs'''2.\mf r128 as''64\ff s128 \bar "|."}
voice_twothree = {\key c \major e4.\mp r1 r1. r8 e,2... r1. r4. r8 e4.\f r2. r128 r64 s128 \bar "|."}
voice_onefour = {\key c \major cs''2\mf e'''2.\p as''2\ f''64\mp r32 a1.\ a'''4.\ppp a'''2\p r8 fs''2\ e'1\ff cs8\p s128 \bar "|."}
voice_twofour = {\key c \major r2 r2. r2 r64 b,32\ r1. r4. r2 g8\ r2 r1 r8 s128 \bar "|."}
voice_onefive = {\key c \major cs128\mf r32 r2 gs4\mp r4.. r8 r8 f'''4\p r4.. r64 gs'''\breve\p cs'''4\mf s128 \bar "|."}
voice_twofive = {\key c \major r128 r32 as2 r4 gs4..\ff as,,,8\mf b,,,8\fff r4 r4.. c64\p r\breve r4 s128 \bar "|."}
\paper {#(set-paper-size "letter") }
\score { <<
\new PianoStaff
Re: Unconventional score and unwanted stray staff lines
These both complie. Andrew On Sun, 19 May 2019 at 12:09, David Bellows wrote: > Hey Andrew, > > Hmm, I'm running Kubuntu 19.04. You wouldn't think there'd be that > much difference between the two? I also wouldn't think there would be > anything we could do in our Lilypond files to cause Ghostscript > problems for one file but not another. > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unconventional score and unwanted stray staff lines
Andrew, > These both complie. That's a relief! I changed the formatting in the master program that generates these Lilypond files to be more sane. Spaces instead of tabs. On Sat, May 18, 2019 at 7:25 PM Andrew Bernard wrote: > > These both complie. > > Andrew > > > On Sun, 19 May 2019 at 12:09, David Bellows wrote: >> >> Hey Andrew, >> >> Hmm, I'm running Kubuntu 19.04. You wouldn't think there'd be that >> much difference between the two? I also wouldn't think there would be >> anything we could do in our Lilypond files to cause Ghostscript >> problems for one file but not another. >> ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unconventional score and unwanted stray staff lines
Hi David,
I can't quite grasp what your score is. Is it for five pianos, as all the
piano staves are grouped into one system?
Anyway, adding \stopStaff at the end of the sections - does this do what
you want? There seems to be some stray clefs in this, but I am sure you can
tidy this up. I assume this is algorithmically generated music?
Andrew
\version "2.19.83"
\language "english"
%\pointAndClickOff
scoreinfo = {\time 4/4 \tempo "andante" 4 = 90}
voice_oneone = {\key c \major r64 r128 r4 r4 ds''1\p fs'64\ g4.\pp cs64\fff fs1\ gs2\pp c'32\fff r32%{%} \bar "|."}
voice_twoone = {\key c \major e,,64\mp cs128\ppp g4 gs4\fff r1 r64 r4. r64 r1 r2 r32 b,,32\p%{%} \bar "|."
\stopStaff
}
voice_onetwo = {\key c \major r1 fs'''4\ppp fs''4\p r64 r1. e\breve\ppp r1 r2.. d''4.\f r4 gs8\mf r2...%{%} \bar "|."}
voice_twotwo = {\key c \major d,1\ppp r4 r4 g64\pp g,,1.\mp r\breve d1\p e,2..\p r4. d,4\fff r8 a,2...\p%{%} \bar "|."}
voice_onethree = {\key c \major r4. r1 g'1.\pp ds'8\ppp r2... r1. cs'4.\fff r8 r4. fs'''2.\mf r128 as''64\ff%{%} \bar "|."
\stopStaff}
voice_twothree = {\key c \major e4.\mp r1 r1. r8 e,2... r1. r4. r8 e4.\f r2. r128 r64%{%} \bar "|."}
voice_onefour = {\key c \major cs''2\mf e'''2.\p as''2\ f''64\mp r32 a1.\ a'''4.\ppp a'''2\p r8 fs''2\ e'1\ff cs8\p%{%} \bar "|."
\stopStaff
}
voice_twofour = {\key c \major r2 r2. r2 r64 b,32\ r1. r4. r2 g8\ r2 r1 r8%{%} \bar "|."}
voice_onefive = {\key c \major cs128\mf r32 r2 gs4\mp r4.. r8 r8 f'''4\p r4.. r64 gs'''\breve\p cs'''4\mf%{%} \bar "|."}
voice_twofive = {\key c \major r128 r32 as2 r4 gs4..\ff as,,,8\mf b,,,8\fff r4 r4.. c64\p r\breve r4%{%} \bar "|."}
\paper {#(set-paper-size "letter") }
\score {
<<
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_oneone
>>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twoone >>
>>
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_onetwo
>>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twotwo >>
>>
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_onethree
>>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twothree >>
>>
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_onefour
>>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twofour >>
>>
\new PianoStaff <<
\new Staff = "upper" <<
\scoreinfo \clef "treble" \voice_onefive
>>
\new Staff = "lower" << \scoreinfo\clef bass \voice_twofive >>
>>
>>
\layout{
ragged-bottom = ##t
\context { \Score \remove "Timing_translator" \remove "Default_bar_line_engraver"}
\context { \Staff \consists "Timing_translator" \consists "Default_bar_line_engraver"}
\context { \Voice \remove "Note_heads_engraver" \consists "Completion_heads_engraver" \remove "Rest_engraver" \consists "Completion_rest_engraver" completionUnit = #(ly:make-moment 2/4)}
}
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unconventional score and unwanted stray staff lines
Hi Andrew, > adding \stopStaff at the end of the sections - does this do what you want? That gets me really close except ... > There seems to be some stray clefs in this, but I am sure you can tidy this > up. I have no idea where those stray clefs are coming from. In the first pdfs I sent they didn't show up. However, the one bass clef I see in these new versions does correspond to where a bass clef was in the original pdfs I sent. As in the stray bass clef is where a stray empty staff was originally. I'm guessing it's related. > I can't quite grasp what your score is. Is it for five pianos, as all the > piano staves are grouped into one system? ... I assume this is > algorithmically generated music? The piece is really for any number of instruments but all of one kind. Like 20 violins or, as in this example, 5 pianos. And yes, the music is generated algorithmically. This particular example just uses the most basic function for generating pitches, durations and dynamics without trying to make it sound good. So what you have here are five different "melodies" generated for five different pianos that all get played at the same time. I think the way I have it grouped makes the most sense but I'm always open to suggestions. I haven't put in the instrument labels yet and I left off the title stuff. On Sat, May 18, 2019 at 7:36 PM Andrew Bernard wrote: > > Hi David, > > I can't quite grasp what your score is. Is it for five pianos, as all the > piano staves are grouped into one system? > > Anyway, adding \stopStaff at the end of the sections - does this do what you > want? There seems to be some stray clefs in this, but I am sure you can tidy > this up. I assume this is algorithmically generated music? > > Andrew > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Unconventional score and unwanted stray staff lines
David Maybe use bar checks? Mark -Original Message- From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of David Bellows Sent: Saturday, May 18, 2019 3:59 PM To: lilypond-user Subject: Unconventional score and unwanted stray staff lines Hello everyone, I tried to keep the examples minimal but I also needed to show the full extent of what is going on. Attached are two Lilypond files and pdfs showing an unconventional score. Each part has the same number of notes but since the durations are random, each part ends at its own time. badtest.ly and badtest.pdf show the default behavior. When a part ends, one of its staves continues on till the last part ends. I don't want this behavior. test.ly and test.pdf do a better job of showing what happens with the workaround hack of adding s128 at the end of each part. The problem with that -- and I didn't include examples -- is that if all the durations are the same and end at a natural bar line, an extra empty measure is added at the end of each part. I can't check for this occurrence ahead of time in my own software as it would be insane to keep track of all of that. You'll notice a lot of context commands all of which I think are necessary to get everything else to look as it should. So I'm hoping someone has an idea about what's going on here and how to prevent those extra staves like in test.pdf Also, these Lilypond files are generated automatically by another program I've created so the layout of the Lilypond file can't really be changed without a massive amount of work. Hopefully a solution won't require something like that. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unconventional score and unwanted stray staff lines
Hey Mark, > Maybe use bar checks? Given that a lot of the music isn't generated to fit any particular time signature (ie, the bar lines are often there just to break things up to ease reading), I would get tons of bar check errors. Plus, keeping track of when bars should be inserted in my software seems like it would be a huge chore. Is this something you think would solve the problem? On Sat, May 18, 2019 at 10:25 PM Mark Stephen Mrotek wrote: > > David > > Maybe use bar checks? > > Mark > > -Original Message- > From: lilypond-user > [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of > David Bellows > Sent: Saturday, May 18, 2019 3:59 PM > To: lilypond-user > Subject: Unconventional score and unwanted stray staff lines > > Hello everyone, > > I tried to keep the examples minimal but I also needed to show the full > extent of what is going on. > > Attached are two Lilypond files and pdfs showing an unconventional score. > Each part has the same number of notes but since the durations are random, > each part ends at its own time. > > badtest.ly and badtest.pdf show the default behavior. When a part ends, one > of its staves continues on till the last part ends. I don't want this > behavior. > > test.ly and test.pdf do a better job of showing what happens with the > workaround hack of adding s128 at the end of each part. The problem with that > -- and I didn't include examples -- is that if all the durations are the same > and end at a natural bar line, an extra empty measure is added at the end of > each part. I can't check for this occurrence ahead of time in my own software > as it would be insane to keep track of all of that. > > You'll notice a lot of context commands all of which I think are necessary to > get everything else to look as it should. > > So I'm hoping someone has an idea about what's going on here and how to > prevent those extra staves like in test.pdf > > Also, these Lilypond files are generated automatically by another program > I've created so the layout of the Lilypond file can't really be changed > without a massive amount of work. Hopefully a solution won't require > something like that. > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
