Re:

[Andrew Bernard]

Hi Paul,

Since this is simple polyphony, use voices throughout, instead of just
occasionally. The Notation Reference (NR) has a lot of information on
this. Section 1.5.2 (for 2.19.38). This addresses your slur problem.

Then

\override Notehead.color = #blue

Andrew

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

Re: OT help with midi2ly on command line mac os blind user

[Jacques Menu Muzhic]

Hello Daniel,

The contents of variable PATH (i.e. $PATH) is a sequence of directories names 
separated by colons :

bash-3.2$ echo $PATH
/Library/Frameworks/Python.framework/Versions/3.2/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/texbin:/usr/local/llvm-3.0/clang+llvm-3.0-x86_64-apple-darwin11/bin:/usr/local/llvm-2.9/bin:/opt/local/bin:/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Commands:/usr/local/bin:/usr/local/LocalLaTeX:/usr/local/erlang/bin:/usr/local/nagios/bin:/usr/local/nagios/libexec:/usr/local/rsync/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/TeX/texbin:/Users/menu/bin:/usr/X11R6/bin:/opt/gnome/bin:/usr/X11R6/bin:/usr/local/scripts:/condor/release/bin:/condor/release/sbin:1.4.4/bin:/usr/local/latex2html-2008/bin:/usr/bin:/usr/sbin:/Developer/Tools:/usr/libexec:/usr/local/openssl/bin:/usr/X11R6/bin:/usr/local/cvs/bin:/usr/texbin:/opt/local/bin:/usr/local/mysql/bin:/Users/menu/yagarto/yagarto-4.6.0/bin:/Applications/LilyPond.app/Contents/Resources/bin:/Developer/usr/libexec:/Developer/usr/llvm-gcc-4.2/bin:/Users/menu/bin

When you submit a command to bash, it looks first among its built-in commands 
and then in $PATH, in the order  of the directories, to find how to 
execute it.

You can ask bash which command will be executed if you type a command:

bash-3.2$ type pwd
pwd is a shell builtin

bash-3.2$ type bash
bash is /bin/bash

bash-3.2$ type foo
bash: type: foo: not found

This command add directory bin in your home directory (~) at the end of the 
PATH:

export PATH=$PATH:~/bin

bash-3.2$ type midi2ly
midi2ly is /Applications/LilyPond.app/Contents/Resources/bin/midi2ly

ash-3.2$ midi2ly -h
Traceback (most recent call last):
  File "/Applications/LilyPond.app/Contents/Resources/bin/midi2ly", line 54, in 

import midi
ImportError: 
dlopen(/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so,
 2): no suitable image found.  Did find:

/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so:
 mach-o, but wrong architecture

This shows that Python module midi.so is not usable on my machine. I run OS X 
10.11.3:

bash-3.2$ uname -a
Darwin macbookprojm 15.3.0 Darwin Kernel Version 15.3.0: Thu Dec 10 18:40:58 
PST 2015; root:xnu-3248.30.4~1/RELEASE_X86_64 x86_64

Can’t help you more there unfortunately, I’ve got no experience in handling 
MIDI files beyond playing them for scores control.

JM


> Le 15 mars 2016 à 04:16, Daniel Contreras  a écrit :
> 
> Hello all, 
> I am trying to wrap my head around this whole command line terminal. I am 
> attempting to follow the steps that are listed on the “Mac OS” section on the 
> lilypond website. I ,think, I have followed each step correctly through step 
> 4, which is to make the file executable. I am confused as to what step 5 is 
> talking about. It is the following: 
> Now, add this directory to your path. Modify (or create) a file called 
> .profile in your home directory such that it contains
> export PATH=$PATH:~/bin
> This file should end with a blank line. 
> 
> I guess my questions are the following: 
> How will these steps help me in using midi2ly?
> Also, can anyone give me an example of what to type in the terminal to 
> convert a midi file to lilypond format? 
> 
> Thanks for any answers and/or suggestions. I apologize for the long off-topic 
> email. Daniel, 
> Also, ha I don’t know why my computer is putting 1’s at the beginning of each 
> line. 
>  <> 
> ___
> 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

Set beam subdivision to #t by default

[Urs Liska]

Hi all,

at least mentally I'm starting to get back to the beaming pattern code.

I would like to ask for your opinion on the matter of switching beam
subdivisions on or off by default.

I would strongly suggest to switch the default setting so that
subdivideBeams is set to #t by default. I know that will affect existing
scores, but the more I think of it the more I think this should be the
default behaviour (after all, it's simple to switch it off).

Page 156 of "Behind Bars" clearly suggests to use beam subdivisions.
It's not stated as mandatory, but neither as purely optional or a matter
of taste. First she claims "Groups of notes are clearest to read when
..." followed by "In ... separate inner beams into ...". Followed then
by a negative example of "not recommended" beaming - which shows
LilyPond's default.

When faced with the attached example Elaine Gould states: "YES
absolutely, (c) as default".

So, before integrating that into my code I would collect opinions. Are
there any strong (and reasoned) objections against changing the default
here?

Best
Urs

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

Re: Set beam subdivision to #t by default

[David Kastrup]

Urs Liska  writes:

> Hi all,
>
> at least mentally I'm starting to get back to the beaming pattern code.
>
> I would like to ask for your opinion on the matter of switching beam
> subdivisions on or off by default.
>
> I would strongly suggest to switch the default setting so that
> subdivideBeams is set to #t by default. I know that will affect existing
> scores, but the more I think of it the more I think this should be the
> default behaviour (after all, it's simple to switch it off).

Something like

{
  \time 4/8
  \set subdivideBeams = ##t
  \repeat unfold 16 c'32
}
just does not look sensible.

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

Re: creating chords like F/A(D/F#) with \chordmode { }

[David Kastrup]

Eby Mani  writes:

> I'm getting the following error on Lilypond 2.18.2 while trying your
> "\altChord" function. Are those functions limited to Lilypond 2.19 ?.
>
> "Parsing.../opt/lilypond/usr/share/lilypond/current/scm/ly-syntax-constructors.scm:56:23:
> In expression (apply (ly:music-function-extract fun) parser ...):
> /opt/lilypond/usr/share/lilypond/current/scm/ly-syntax-constructors.scm:56:23:
> Wrong number of arguments to #"
>
> Eby

altChords =
#(define-music-function (m1 m2)(ly:music? ly:music?)

has to be

altChords =
#(define-music-function (parser location m1 m2)(ly:music? ly:music?)

in 2.18 instead.

-- 
David Kastrup

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

Capturing inconsistency in beam subdivision length

[Urs Liska]

Another puzzle/quiz/poll on beaming patterns for today.

Consider the attached renderings of a phrase with many notes, many beams
and inconsistent note durations (=> beam count). a) is rendered with a
base duration of 1/8 b) with 1/16.

(Note that unlike my previous post this is *not* about choosing a default)
In general I very much prefer b) because I think it's easier to read.

According also to Elaine Gould b) is preferrable, with one exception:
the subdivision of the second quaver in the second crotchet  is not
necessary. In this case she states (considering the "trade-off between
ideal note groupings and consistency of division length"): "The ideal
takes priority. Inconsistency in subdividing groups can sometimes be the
best solution".
In general she recommends dividing into groups of four equal notes and
not two.

Currently I don't see any way to capture such inconsistency short of
manually setting the stem's beam counts, as one can't change the value
of baseMoment during a beam. So what this seems to call for is an update
to the beaming pattern calculation, something like (an optional) "do not
further subdivide a group that already has exactly four notes" rule. But
somehow I'm afraid of skating on thin ice when going into that direction.

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

Re: Set beam subdivision to #t by default

[Urs Liska]

Am 15.03.2016 um 10:08 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Hi all,
>>
>> at least mentally I'm starting to get back to the beaming pattern code.
>>
>> I would like to ask for your opinion on the matter of switching beam
>> subdivisions on or off by default.
>>
>> I would strongly suggest to switch the default setting so that
>> subdivideBeams is set to #t by default. I know that will affect existing
>> scores, but the more I think of it the more I think this should be the
>> default behaviour (after all, it's simple to switch it off).
> Something like
>
>
>
> just does not look sensible.

Well, I must say something like

{
  \time 4/8
%  \set subdivideBeams = ##t
  \repeat unfold 16 c'32
}

just does not look sensible, in 4/8 even more than in 2/4 time.


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

Re: creating chords like F/A(D/F#) with \chordmode { }

[Thomas Morley]

2016-03-15 9:49 GMT+01:00 David Kastrup :
> Eby Mani  writes:
>
>> I'm getting the following error on Lilypond 2.18.2 while trying your
>> "\altChord" function. Are those functions limited to Lilypond 2.19 ?.
>>
>> "Parsing.../opt/lilypond/usr/share/lilypond/current/scm/ly-syntax-constructors.scm:56:23:
>> In expression (apply (ly:music-function-extract fun) parser ...):
>> /opt/lilypond/usr/share/lilypond/current/scm/ly-syntax-constructors.scm:56:23:
>> Wrong number of arguments to #"
>>
>> Eby
>
> altChords =
> #(define-music-function (m1 m2)(ly:music? ly:music?)
>
> has to be
>
> altChords =
> #(define-music-function (parser location m1 m2)(ly:music? ly:music?)
>
> in 2.18 instead.
>
> --
> David Kastrup

The arguments of applyOutput should be changed as well.
Complete 2.18.-code of the final function:

altChords =
#(define-music-function (parser location m1 m2)(ly:music? ly:music?)
"Return the default ChordName of @var{m1}, with an added parenthesized ChordName
derived from @var{m2}"
#{
   \applyOutput ChordNames %.ChordName
 #(lambda (g ctx p)
(let ((main-text (ly:grob-property g 'text))
  (alt-text
(apply
  ignatzek-chord-names
  (pitches-bass-inversion-context-list m2 ctx
 (ly:grob-set-property! g 'text
   #{
 \markup
   { $main-text \hspace #0.4 \fontsize #-3 \parenthesize $alt-text }
   #})))
   $m1
#})


Cheers,
  Harm

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

Re: Set beam subdivision to #t by default

[Werner LEMBERG]

> So, before integrating that into my code I would collect opinions.
> Are there any strong (and reasoned) objections against changing the
> default here?

Your suggestions looks sensible.


Werner

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

Re: Set beam subdivision to #t by default

[Trevor Daniels]

Urs Liska wrote Tuesday, March 15, 2016 8:44 AM

> I would like to ask for your opinion on the matter of switching beam
> subdivisions on or off by default.
> 
> I would strongly suggest to switch the default setting so that
> subdivideBeams is set to #t by default. I know that will affect existing
> scores, but the more I think of it the more I think this should be the
> default behaviour (after all, it's simple to switch it off).
> 
> Page 156 of "Behind Bars" clearly suggests to use beam subdivisions.
> It's not stated as mandatory, but neither as purely optional or a matter
> of taste. First she claims "Groups of notes are clearest to read when
> ..." followed by "In ... separate inner beams into ...". Followed then
> by a negative example of "not recommended" beaming - which shows
> LilyPond's default.
> 
> When faced with the attached example Elaine Gould states: "YES
> absolutely, (c) as default".
> 
> So, before integrating that into my code I would collect opinions. Are
> there any strong (and reasoned) objections against changing the default
> here?

I agree we  should switch the default, as long as it is clearly stated in
Changes, perhaps under a heading New Default(s).

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

Re: Adding acoustic guitar (steel) to MIDI

[Trevor Daniels]

David you wrote Tuesday, March 15, 2016 5:35 AM

> On Mon, Mar 14, 2016 at 10:23 PM -0700, "tisimst [via Lilypond]" wrote:

>> Frescobaldi doesn't actually provide the MIDI sound 
>> font, just the player interface. So, if you are only 
>> hearing piano, regardless of your choice of midiInstrument, 
>> then there must be a problem with your OS's built-in 
>> MIDI sound font. Which OS are you using?

> My OS is Windows Vista.

Your code works fine under Frescobaldi in Windows Vista
(with string->steel, of course).

But the default sound fonts are rather poor in Windows,
with many instruments barely distinguishable from piano.

I use VirtualMidiSynth from
http://coolsoft.altervista.org/en/virtualmidisynth
with the Fluid R3 GM bank from
http://www.synthfont.com/soundfonts.html
and the difference between piano and steel guitar is
quite clear.

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

Re: Set beam subdivision to #t by default

[Urs Liska]

Am 15.03.2016 um 10:58 schrieb Trevor Daniels:
>> So, before integrating that into my code I would collect opinions. Are
>> > there any strong (and reasoned) objections against changing the default
>> > here?
> I agree we  should switch the default, as long as it is clearly stated in
> Changes, perhaps under a heading New Default(s).

This is a good idea. I assume there will be a few more changed defaults
in the whole corpus of that patch that should be mentioned as well.
In addition I *consider* also rewriting the manual chapter a little bit,
mainly to include the beaming pattern considerations in the main text
(instead of only having them in "selected snippets"). But for that to
happen I will have to complete the work. And for that to happen I will
first have to pick up working on it ...

Urs

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

Re: Set beam subdivision to #t by default

[Ralph Palmer]

On Tue, Mar 15, 2016 at 6:11 AM, Urs Liska  wrote:

>
>
> Am 15.03.2016 um 10:58 schrieb Trevor Daniels:
> >> So, before integrating that into my code I would collect opinions. Are
> >> > there any strong (and reasoned) objections against changing the
> default
> >> > here?
> > I agree we  should switch the default, as long as it is clearly stated in
> > Changes, perhaps under a heading New Default(s).
>
> This is a good idea. I assume there will be a few more changed defaults
> in the whole corpus of that patch that should be mentioned as well.
> In addition I *consider* also rewriting the manual chapter a little bit,
> mainly to include the beaming pattern considerations in the main text
> (instead of only having them in "selected snippets"). But for that to
> happen I will have to complete the work. And for that to happen I will
> first have to pick up working on it ...
>
> Urs
>

My 2 cents - this sounds good to me, as well, Urs. Thanks again for all
your work on LilyPond. Thanks again to you, David, Trevor, and Werner, as
well.

Ralph


-- 
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Set beam subdivision to #t by default

[Simon Albrecht]

On 15.03.2016 09:44, Urs Liska wrote:

I would strongly suggest to switch the default setting so that
subdivideBeams is set to #t by default.


Agreed.

Best, Simon

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

no text

[Bernhard Kleine]

I do not see what is wrong, the text is not displayed. It is close to
what I used before. I am stymied.

Bernhard

\version "2.19.33"
\language "deutsch"
\header {
  title = "Erstanden ist der Herr"
  subtitle = "Ostermotette für gemischte Stimmen"
  subsubtitle = "Bearbeitung und Textfassung: P.J. Metschnabl"
  composer = "Valentin Rathgeber"
  tagline = \markup {
Engraved von Bernhard Kleine mit
\with-url #"http://lilypond.org/";
\line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
  }
}

global = {
  \numericTimeSignature
  \time 3/4
  \key b \major

}

soprano= \relative c'' {
  \global
  b4 b c | d2 e4| f2 f,4| \bar "|."
}

alto=  \relative c'' {
  \global
  d,4 f f f2
}


texttext= \lyricmode {
  \set stanza = "Er -- stan -- de ist der Herr, er"
}

\score {
  \new ChoirStaff
   <<
\new Staff \with {
  instrumentName = \markup \center-column { Sopran }
} <<
  \new Voice = "sopran" \soprano
>>

\new Lyrics \lyricsto "sopran" \texttext

\new Staff \with {
  instrumentName = \markup \center-column { Alt }
} <<

  \new Voice = "alto" { \alto }
>>

   >>
  \layout {}
  \midi {}
}

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

Re: no text

[Simon Albrecht]

On 15.03.2016 16:27, Bernhard Kleine wrote:

I do not see what is wrong, the text is not displayed. It is close to
what I used before. I am stymied.


All you do in the ‘texttext’ variable is set the stanza number to a very 
long string. So no text is displayed.


HTH, Simon


Bernhard

\version "2.19.33"
\language "deutsch"
\header {
   title = "Erstanden ist der Herr"
   subtitle = "Ostermotette für gemischte Stimmen"
   subsubtitle = "Bearbeitung und Textfassung: P.J. Metschnabl"
   composer = "Valentin Rathgeber"
   tagline = \markup {
 Engraved von Bernhard Kleine mit
 \with-url #"http://lilypond.org/";
 \line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
   }
}

global = {
   \numericTimeSignature
   \time 3/4
   \key b \major

}

soprano= \relative c'' {
   \global
   b4 b c | d2 e4| f2 f,4| \bar "|."
}

alto=  \relative c'' {
   \global
   d,4 f f f2
}


texttext= \lyricmode {
   \set stanza = "Er -- stan -- de ist der Herr, er"
}

\score {
   \new ChoirStaff
<<
 \new Staff \with {
   instrumentName = \markup \center-column { Sopran }
 } <<
   \new Voice = "sopran" \soprano
 >>

 \new Lyrics \lyricsto "sopran" \texttext

 \new Staff \with {
   instrumentName = \markup \center-column { Alt }
 } <<

   \new Voice = "alto" { \alto }
 >>

>>
   \layout {}
   \midi {}
}

___
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: no text

[tisimst]

Bernhard,

On Tue, Mar 15, 2016 at 9:38 AM, Dr. Bernhard Kleine [via Lilypond] <
ml-node+s1069038n188565...@n5.nabble.com> wrote:

> I do not see what is wrong, the text is not displayed. It is close to
> what I used before. I am stymied.
>
> [SNIP]
>
> texttext= \lyricmode {
>   \set stanza = "Er -- stan -- de ist der Herr, er"
> }
>
> [SNIP]
>

Two things are at play here:
1. Stanza text with no actual lyrics will print nothing, but seems to take
up the same horizontal space as if it were printed.
2. Did you really mean to make "Er -- stan -- de ist der Herr, er" the
stanza text and not the lyric text?

HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/no-text-tp188565p188567.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: OT help with midi2ly on command line mac os blind user

[David Wright]

On Mon 14 Mar 2016 at 22:16:28 (-0500), Daniel Contreras wrote:
>Hello all, 
>I am trying to wrap my head around this whole command line terminal. I am
>attempting to follow the steps that are listed on the �Mac OS� section on
>the lilypond website. I ,think, I have followed each step correctly
>through step 4, which is to make the file executable. I am confused as to
>what step 5 is talking about. It is the following: 
> 
> 1. Now, add this directory to your path. Modify (or create) a file
>called .profile in your home directory such that it contains
> 
>  export PATH=$PATH:~/bin
> 
>This file should end with a blank line. 
>I guess my questions are the following: 
>How will these steps help me in using midi2ly?

Starting at step 5 (called 1 in your quote above), when your bash
shell starts up as a login shell, it reads your ~/.profile file for
your personal initialisation.

(But only a login shell, so that these commands are not repeated every
time a subsequent shell starts.)

Users who write scripts and/or programs that they want to invoke just
by typing their name will typically place these scripts (or links to
them) in one directory conventionallly called ~/bin and step 1 of the
instructions shows you how to make that if it isn't already there.

(You can run scripts/programs from anywhere by giving a pathname,
ie something containing a /, but they must be in your $PATH if you
just want to be able to type a bare name without a slash.)

Steps 2 and 3 show how you can write scripts that you will execute
by typing their (short) name, which will in turn execute a program
that has a very long name. "$@" will pass on to that program any
options and arguments you give.

For you to be able to invoke a program in this way, your script must
be executable, and that's step 4. (You need to do it to each script.)
You will then be able to type, eg, midi2ly -h   or midi2ly --version
and bash will run that script, see that it starts with #!/bin/bash
and start a bash subshell which will execute the exec command on the
appropriate program.

So the final link in the chain is to put your ~/bin into your $PATH.
~/.profile does this with   export PATH=$PATH:~/bin

When this is executed in your ~/.profile, the righthandside is
expanded by the shell into

the-whole:of-the:preexisting:value-of-$PATH-in:a-list:~/bin

where you'll see lots of directories separated by : (colons) with
yours tacked onto the end. This string then becomes the new value of
$PATH. "export" is necessary to make bash pass it to all subsequent
commands and subshells.

>Also, can anyone give me an example of what to type in the terminal to
>convert a midi file to lilypond format? 

midi2ly name-of-midi-file.midi

On my system, it creates (or will overwrite without warning) a file in
the current directory called   name-of-midi-file-midi.ly   unless I
specify -o newfilename.

Cheers,
David.

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

Re: OT help with midi2ly on command line mac os blind user

[David Wright]

On Tue 15 Mar 2016 at 09:09:38 (+0100), Jacques Menu Muzhic wrote:
>bash-3.2$ echo $PATH
>
> /Library/Frameworks/Python.framework/Versions/3.2/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/texbin:/usr/local/llvm-3.0/clang+llvm-3.0-x86_64-apple-darwin11/bin:/usr/local/llvm-2.9/bin:/opt/local/bin:/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Commands:/usr/local/bin:/usr/local/LocalLaTeX:/usr/local/erlang/bin:/usr/local/nagios/bin:/usr/local/nagios/libexec:/usr/local/rsync/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/TeX/texbin:/Users/menu/bin:/usr/X11R6/bin:/opt/gnome/bin:/usr/X11R6/bin:/usr/local/scripts:/condor/release/bin:/condor/release/sbin:1.4.4/bin:/usr/local/latex2html-2008/bin:/usr/bin:/usr/sbin:/Developer/Tools:/usr/libexec:/usr/local/openssl/bin:/usr/X11R6/bin:/usr/local/cvs/bin:/usr/texbin:/opt/local/bin:/usr/local/mysql/bin:/Users/menu/yagarto/yagarto-4.6.0/bin:/Applications/LilyPond.app/Contents/Resources/bin:/Developer/usr/libexec:/Developer/usr/llvm-gcc-4.2/bin:/Users/menu/bin

That's a fearsome path! It seems to have almost a dozen duplicates in it.
I guess it's as well that bash hashes the contents.

Cheers,
David.

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

Re: OT help with midi2ly on command line mac os blind user

[Jacques Menu Muzhic]

Hello David,

Thanks for pointing this out.

I don’t use bash often in fact, since my default shell is tcsh.

And it turns out I have a lot of bash left-overs from the machines I was in 
charge professionally some time ago…

JM

> Le 15 mars 2016 à 17:15, David Wright  a écrit :
> 
> On Tue 15 Mar 2016 at 09:09:38 (+0100), Jacques Menu Muzhic wrote:
>>   bash-3.2$ echo $PATH
>>   
>> /Library/Frameworks/Python.framework/Versions/3.2/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/texbin:/usr/local/llvm-3.0/clang+llvm-3.0-x86_64-apple-darwin11/bin:/usr/local/llvm-2.9/bin:/opt/local/bin:/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Commands:/usr/local/bin:/usr/local/LocalLaTeX:/usr/local/erlang/bin:/usr/local/nagios/bin:/usr/local/nagios/libexec:/usr/local/rsync/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/TeX/texbin:/Users/menu/bin:/usr/X11R6/bin:/opt/gnome/bin:/usr/X11R6/bin:/usr/local/scripts:/condor/release/bin:/condor/release/sbin:1.4.4/bin:/usr/local/latex2html-2008/bin:/usr/bin:/usr/sbin:/Developer/Tools:/usr/libexec:/usr/local/openssl/bin:/usr/X11R6/bin:/usr/local/cvs/bin:/usr/texbin:/opt/local/bin:/usr/local/mysql/bin:/Users/menu/yagarto/yagarto-4.6.0/bin:/Applications/LilyPond.app/Contents/Resources/bin:/Developer/usr/libexec:/Developer/usr/llvm-gcc-4.2/bin:/Users/menu/bin
> 
> That's a fearsome path! It seems to have almost a dozen duplicates in it.
> I guess it's as well that bash hashes the contents.
> 
> Cheers,
> David.


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

Dynamics context and vertical positions

[Gilberto Agostinho]

Hi all,

I have been using the Dynamics context since short time ago, and I think it
substantially helps to improve the overall look of the score with its
horizontal alignment of all dynamics in a system. 

The problem I have with it is that I often find the distance between the
dynamics and the staff to be very large and for no apparent reason. For
instance, compare these two scores below:

\version "2.19.37"

A = {
  c''1
  c''1
  c''1
}

B = {
  s1\p |
  s1\f |
  s1\pp |
}

\new Staff << \A \B >>

<<
  \new Staff \A
  \new Dynamics \B
>>

 

The top staff shows the default position of dynamics without using the
Dynamics context. Surely both \p and \pp will have to move a bit downwards
in order to be horizontally aligned with the \f, but the Dynamics context
moves all of them quite a lot downwards (including the \f).

The amount of vertical shift is also not consistent between several staves
in a system. In the example below, the bottom staff has much more distance
between its lowest staff line and its dynamics (21 pixels in my image below)
than the other two upper staves (17 pixels):

\version "2.19.37"

A = {
  c''1
  c''1
  c''1
}

B = {
  s1\p |
  s1\f |
  s1\pp |
}

<<
  \new Staff \A
  \new Dynamics \B
  \new Staff \A
  \new Dynamics \B
  \new Staff \A
  \new Dynamics \B
>>

 

In some of my orchestral scores, I have seen even larger gaps between the
Dynamic context and the staff it belongs to, but I could not narrow down why
it happens in some of these cases and so I couldn't come up with a minimal
example. But for instance, here is an excerpt in a very simple texture of
what I came across:

 

So my question is: how is the best way to handle this? How can I bring the
Dynamic context closer to the Staff but still avoiding collisions? Are there
any overrides I could use for that?

Thanks in advance. 

Cheers,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Dynamics-context-and-vertical-positions-tp188571.html
Sent from the User mailing list archive at Nabble.com.

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

Adding acoustic guitar (steel) to MIDI

[David Landt]

Trevor, thank you for letting me know about the Windows default settings.  It
seems that my OS is the culprit. I thought that I heard a very slight
difference between the acoustic guitar and default piano, but wasn't sure. 
You and Abraham have confirmed that it is the case.  I will try to figure
out how to change the default sound font on my Windows Vista OS so that I
could enjoy hearing a guitar sound.

Also, I will view the links you provided.  This forum is wonderful.



-
David Landt
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Adding-acoustic-guitar-steel-to-MIDI-tp188538p188572.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Dynamics context and vertical positions

[tisimst]

Gilberto,

On Tue, Mar 15, 2016 at 11:15 AM, Gilberto Agostinho [via Lilypond] <
ml-node+s1069038n188571...@n5.nabble.com> wrote:
>
> The problem I have with it is that I often find the distance between the
> dynamics and the staff to be very large and for no apparent reason.
> ... [SNIP] ...
> So my question is: how is the best way to handle this? How can I bring the
> Dynamic context closer to the Staff but still avoiding collisions? Are
> there any overrides I could use for that?
>

Although it might not be apparent what's going on, there is a logical
explanation. In the first instance you are attaching the dynamics to the
NoteColumn (giving it vertical flexibility, independent of other dynamics
instances), the second uses a non-staff context which has its own spacing
relative to other [non]staff contexts. You can read about this in detail
here:

http://lilypond.org/doc/v2.19/Documentation/notation/flexible-vertical-spacing-within-systems


HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Dynamics-context-and-vertical-positions-tp188571p188573.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Capturing inconsistency in beam subdivision length

[Kieren MacMillan]

Hi Urs,

> Opinions?

I agree with Gould: (b), with the one adjustment, is superior.

> what this seems to call for is an update
> to the beaming pattern calculation, something like (an optional) "do not
> further subdivide a group that already has exactly four notes" rule. But
> somehow I'm afraid of skating on thin ice when going into that direction.

Yeah… As soon as you get into tuplets, that ice gets even thinner.  :\
Not sure how to advise.

But many many thanks for you efforts in this area — it’s bound to make a huge 
positive difference!

Best,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: Set beam subdivision to #t by default

[Kieren MacMillan]

Hi Urs,

> Are there any strong (and reasoned) objections against changing the default 
> here?

No. Your new default seems the superior choice.

Thanks!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Adding acoustic guitar (steel) to MIDI

[David Landt]

Trevor, I installed CoolSoft VirtualMIDISynth and the font bank you
mentioned.  After setting the CoolSoft as the default synthesizer in
Frescobaldi, I did notice a difference in the sound of various instruments
when compared with Microsoft GS Wavetable Synth, which is my OS's default
synthesizer.  You and Abraham are correct about the not-so-good quality of
the Microsoft default synthesizer.

The reason I kept hearing an unmistakable piano sound is channel 1 of the
MIDI player was playing a grand piano chord at just the beginning of every
measure, over the acoustic guitar sound playing on channel 2.  I simply
turned off the channel 1 piano sound using the displayed MIDI mixer, a
feature CoolSoft allows the user to enable.  The following attached images
should reinforce what it is I am describing:  MIDI_synth_on_Frescobaldi.jpg

  
configCoolSoft_VirtualMIDISyth.jpg

  
MIDI_Mixer_visible.jpg
  

The users of this forum greatly helped me to solve a problem I was trying to
solve on my own for over five days.



-
David Landt
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Adding-acoustic-guitar-steel-to-MIDI-tp188538p188576.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Adding acoustic guitar (steel) to MIDI

[David Kastrup]

David Landt  writes:

> Trevor, I installed CoolSoft VirtualMIDISynth and the font bank you
> mentioned.  After setting the CoolSoft as the default synthesizer in
> Frescobaldi, I did notice a difference in the sound of various instruments
> when compared with Microsoft GS Wavetable Synth, which is my OS's default
> synthesizer.  You and Abraham are correct about the not-so-good quality of
> the Microsoft default synthesizer.
>
> The reason I kept hearing an unmistakable piano sound is channel 1 of the
> MIDI player was playing a grand piano chord at just the beginning of every
> measure, over the acoustic guitar sound playing on channel 2.

ChordName or FretBoard context?

-- 
David Kastrup

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

Adding acoustic guitar (steel) to MIDI

[David Landt]

Hello David.


David Kastrup wrote
> ChordName or FretBoard context?

Yes, I used ChordNames.  I think the grand piano instrument sounded on
channel 1 because it was following the chord progression. I only wanted to
display chord names.  To shut off the sound of the chord "names" being
played as grand piano, I simply selected the "off" button for that channel
on the MIDI equalizer.  One has to enable the equalizer using Configure
VirtualMIDISynth program that should have been created when setting up
CoolSoft VirtualMIDISynthin order for it to show; and the CoolSoft
VirtualMIDISynth has to be selected in Frescobaldi--> Edit--> Preferences-->
MIDI Settings.



-
David Landt
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Adding-acoustic-guitar-steel-to-MIDI-tp188538p188579.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Adding acoustic guitar (steel) to MIDI

[Abraham Lee]

David,

On Tue, Mar 15, 2016 at 4:14 PM, David Landt 
wrote:

> Hello David.
>
>
> David Kastrup wrote
> > ChordName or FretBoard context?
>
> Yes, I used ChordNames.  I think the grand piano instrument sounded on
> channel 1 because it was following the chord progression. I only wanted to
> display chord names.  To shut off the sound of the chord "names" being
> played as grand piano, I simply selected the "off" button for that channel
> on the MIDI equalizer.


That makes so much more sense now! No wonder nobody else experienced the
problem you described since no ChordNames were included in your original
file. Yes, ChordNames (and FretBoards, as David K. mentioned) produces
sound, too! And it automatically assumes the default sound, which is a
piano. You can turn off any context's midi instrument like this:

\new ChordNames \with { midiInstrument = ##f }

that way you don't need to deal with the synthesizer to turn things on/off.

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

Adding acoustic guitar (steel) to MIDI

[David Landt]

David Kastrup wrote
> ChordName or FretBoard context?

Yes, I used ChordNames context.  Attached is my code. HereComestheSun.ly


It seems that the grand piano on channel 1 was created because of using
ChordNames.  The piano sound followed the chord (chord name) progression
even though I was using the chord names strictly for hand positioning
reference.  I simply shut off channel 1 on the MIDI equalizer that appears
when you enable it by using Configure VirtualMIDISynth, a program that
should have been created when setting up that synthesizer at the time of
installation.  Once that is enabled, you add the synthesizer to Frescobaldi
by going to Edit> Preferences> MIDI Settings and going to drop down menu in
MIDI Input box.  When you playback MIDI, the equalizer should appear.

There may be other ways to disable the grand piano sound if using
ChordNames.  I am a brand new, but I already like LilyPond, Frescobaldi, and
this forum.



-
David Landt
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Adding-acoustic-guitar-steel-to-MIDI-tp188538p188581.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Adding acoustic guitar (steel) to MIDI

[Simon Albrecht]

On 15.03.2016 23:31, Abraham Lee wrote:

David,

On Tue, Mar 15, 2016 at 4:14 PM, David Landt > wrote:


Hello David.


David Kastrup wrote
> ChordName or FretBoard context?

Yes, I used ChordNames.  I think the grand piano instrument sounded on
channel 1 because it was following the chord progression. I only
wanted to
display chord names.  To shut off the sound of the chord "names" being
played as grand piano, I simply selected the "off" button for that
channel
on the MIDI equalizer.


That makes so much more sense now! No wonder nobody else experienced 
the problem you described since no ChordNames were included in your 
original file. Yes, ChordNames (and FretBoards, as David K. mentioned) 
produces sound, too! And it automatically assumes the default sound, 
which is a piano. You can turn off any context's midi instrument like 
this:


\new ChordNames \with { midiInstrument = ##f }

that way you don't need to deal with the synthesizer to turn things 
on/off.


Alternatively you might use an extra \score for midi, i.e. one with a 
\midi{} block instead of \layout{}. This is recommendable for numerous 
situations.


Best, Simon

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

Adding acoustic guitar (steel) to MIDI

[David Landt]

Hello Simon.


Simon Albrecht-2 wrote
>> That makes so much more sense now! No wonder nobody else experienced 
>> the problem you described since no ChordNames were included in your 
>> original file. 

Initially, I was trying to follow the forum etiquette by only including what
is pertinent; however, since I am new, I thought that ChordNames strictly
meant a display of names and had no bearing on sound, which I come to find
out is not the case.I am learning much.

The line of code you provided helps with removing unwanted instrument sounds
without the need to toggle the synthesizer's mixer panel.

Is there any information available regarding the terminology and anatomy of
the actual LilyPond language?  Something like information for learning and
understanding the actual source code and all its components? 




-
David Landt
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Adding-acoustic-guitar-steel-to-MIDI-tp188538p188584.html
Sent from the User mailing list archive at Nabble.com.

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

Dashed Tie Design Improvement

[dtsmarin]

Hi folks,

The default shape of the tie's dashes looks a bit strange to me, is there a
way to modify it to look a bit like the second one which  in my opinion
looks fuller on page? Also how can I increase and thicken the dashes between
the tie end points? 

Thank you
 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Dashed-Tie-Design-Improvement-tp188585.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Adding acoustic guitar (steel) to MIDI

[Simon Albrecht]

Hello David,

we use to keep communication on-list, except to send really private 
information.


On 16.03.2016 02:53, david_la...@hotmail.com wrote:


Simon,

I didn't know how to write any code prior to using LilyPond.



Ok, so I misunderstood you from your speaking of the ‘source code’. I 
thought you meant the source code for LilyPond itself, not just any 
LilyPond input code.


  Everything I created was learned from reading the manuals, snippets, 
forum threads, and tutorials on YouTube.  It took me about three weeks 
to digest everything and to use what I learned to create my very 
simple .ly file.  Learning code and engraving is fun.


You know exactly what I meant by learning more about LilyPond 
language.  Thanks for providing me with all the information.  The 
months ahead are going to be partly filled with learning LilyPond.  I 
thought learning guitar was challenge.


This forum is very helpful.

David Landt



All the best for your way with LilyPond!
Simon

On Tue, Mar 15, 2016 at 6:15 PM -0700, "Simon Albrecht" 
mailto:simon.albre...@mail.de>> wrote:


On 16.03.2016 01:04, David Landt wrote:
> Hello Simon.
>
>
> Simon Albrecht-2 wrote
>>> That makes so much more sense now! No wonder nobody else experienced
>>> the problem you described since no ChordNames were included in your
>>> original file.
> Initially, I was trying to follow the forum etiquette by only 
including what
> is pertinent; however, since I am new, I thought that ChordNames 
strictly
> meant a display of names and had no bearing on sound, which I come 
to find

> out is not the case.

Typically, if you have a problem with a lilypond score, you’d try
removing more and more things and testing if the problem persists. Often
this helps you find the culprit yourself; else you’ll end up with a
minimal example with which you can ask on the list.

> Is there any information available regarding the terminology and 
anatomy of
> the actual LilyPond language?  Something like information for 
learning and

> understanding the actual source code and all its components?

Of course. First, the manuals of course. The Learning Manual gives an
introduction and needs definitely to be read to come to terms with the
basics. It will also help with how to use the other manuals. But from
your question I guess that you have some experience with coding already.
Some information of the kind you ask is found in the Notation Reference,
more in the Extending manual or in the Internals Reference, at some
point you’ll be interested in the Guile manual (either the R5RS for
Scheme in general or the Guile Reference Manual
 – yes,
Guile 1.8), and then of course you can delve into the source code
yourself – see .

HTH, Simon



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

Adding acoustic guitar (steel) to MIDI

[David Landt]

I did mean the source code.  You directed me to all those sources.  Thanks 
again.


David Landt






On Tue, Mar 15, 2016 at 7:01 PM -0700, "Simon Albrecht-2 [via Lilypond]" 
 wrote:







Hello David,

we use to keep communication on-list, except to send really private
information.

On 16.03.2016 02:53, david_la...@hotmail.com wrote:
>
> Simon,
>
> I didn't know how to write any code prior to using LilyPond.
>

Ok, so I misunderstood you from your speaking of the ‘source code’. I
thought you meant the source code for LilyPond itself, not just any
LilyPond input code.

>   Everything I created was learned from reading the manuals, snippets,
> forum threads, and tutorials on YouTube.  It took me about three weeks
> to digest everything and to use what I learned to create my very
> simple .ly file.  Learning code and engraving is fun.
>
> You know exactly what I meant by learning more about LilyPond
> language.  Thanks for providing me with all the information.  The
> months ahead are going to be partly filled with learning LilyPond.  I
> thought learning guitar was challenge.
>
> This forum is very helpful.
>
> David Landt
>

All the best for your way with LilyPond!
Simon

> On Tue, Mar 15, 2016 at 6:15 PM -0700, "Simon Albrecht"
> mailto:simon.albre...@mail.de>> wrote:
>
> On 16.03.2016 01:04, David Landt wrote:
> > Hello Simon.
> >
> >
> > Simon Albrecht-2 wrote
> >>> That makes so much more sense now! No wonder nobody else experienced
> >>> the problem you described since no ChordNames were included in your
> >>> original file.
> > Initially, I was trying to follow the forum etiquette by only
> including what
> > is pertinent; however, since I am new, I thought that ChordNames
> strictly
> > meant a display of names and had no bearing on sound, which I come
> to find
> > out is not the case.
>
> Typically, if you have a problem with a lilypond score, you’d try
> removing more and more things and testing if the problem persists. Often
> this helps you find the culprit yourself; else you’ll end up with a
> minimal example with which you can ask on the list.
>
> > Is there any information available regarding the terminology and
> anatomy of
> > the actual LilyPond language?  Something like information for
> learning and
> > understanding the actual source code and all its components?
>
> Of course. First, the manuals of course. The Learning Manual gives an
> introduction and needs definitely to be read to come to terms with the
> basics. It will also help with how to use the other manuals. But from
> your question I guess that you have some experience with coding already.
> Some information of the kind you ask is found in the Notation Reference,
> more in the Extending manual or in the Internals Reference, at some
> point you’ll be interested in the Guile manual (either the R5RS for
> Scheme in general or the Guile Reference Manual
>  – yes,
> Guile 1.8), and then of course you can delve into the source code
> yourself – see .
>
> HTH, Simon


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




___
If you reply to this email, your message will be added to the discussion below:
http://lilypond.1069038.n5.nabble.com/Adding-acoustic-guitar-steel-to-MIDI-tp188538p188586.html

To unsubscribe from Adding acoustic guitar (steel) to MIDI, visit 
http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=188538&code=ZGF2aWRfbGFuZHRAaG90bWFpbC5jb218MTg4NTM4fC0yMTI2ODU4NzEz




-
David Landt
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Adding-acoustic-guitar-steel-to-MIDI-tp188538p188587.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dashed Tie Design Improvement

[Malte Meyn]

Am 16.03.2016 um 01:18 schrieb dtsmarin:

The default shape of the tie's dashes looks a bit strange to me, is there a
way to modify it to look a bit like the second one which  in my opinion
looks fuller on page? Also how can I increase and thicken the dashes between
the tie end points?



http://lilypond.org/doc/v2.18/Documentation/notation/writing-rhythms#tie

\tieDashPattern is what you need.

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