Re: .ly to .svg - can't manage to get anything working

2014-07-20 Thread Stefaan Himpe
Pieter-Jan Van Damme wrote:

> Would you guys have any suggestions for a novice like myself?

When I needed SVG in the past, I found it straightforward to generate it 
from Frescobaldi (http://frescobaldi.org ).

In the Lilypond menu, use "Engrave (Custom)" and choose svg as backend.

If your problem is one of wrong command line arguments, then this approach
might work around it.

Best regards,
Stefaan.

-- 
http://technogems.blogspot.com
http://a-touch-of-music.blogspot.com
http://youtube.com/stefaanhimpe



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


Re: .ly to .svg - can't manage to get anything working

2014-07-20 Thread tisimst
Pieter-Jan Van Damme wrote
> Hello guys,
> 
> I've been looking for a method to get Lilypond to output to .svg but none
> of the methods described online worked for me (I'm using Windows 7).
> 
> I tried:
> 
> 1) using the command line... well, the documentation has left me even more
> confused than before I tried it. That may be because I am not overly
> familiar with the command line. And I'm suspecting the documentation is
> Linux-oriented.
> 
> 2) when importing a .pdf into Inkscape the note heads and clefs fail to
> materialize. Somewhere online it was said I should either uninstall some
> Windows updates (https://plus.google.com/+inkscape/posts/RV4qMPKFXkn -
> didn't work) or install a font (didn't find the ones referenced; either
> Feta ).
> 
> Would you guys have any suggestions for a novice like myself?
> 
> ___
> lilypond-user mailing list

> lilypond-user@

> https://lists.gnu.org/mailman/listinfo/lilypond-user

Pieter,

The font files aren't in the regular system font folder (you probably
already figured that out). Thay should be found in a folder like:

C:\Program Files\LilyPond\usr\share\lilypond\current\fonts\otf

The font files are actually called "emmentaler-XX.otf". Just copy all of
them (including the Century Schoolbook ones) to the regular system font
folder (C:\Windows\Fonts) and everything should work in Inkscape. On
Windows, this would be the easiest thing for now.

To create SVG output scores, you need to add the lilypond.exe directory
(C:\Program Files\LilyPond\usr\bin) to the PATH environment variable, but
then you should be able to follow any of the regular command line
instructions in the online manual, like:

lilypond -dbackend=svg test.ly

Regards,
Abraham



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ly-to-svg-can-t-manage-to-get-anything-working-tp164744p164745.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


.ly to .svg - can't manage to get anything working

2014-07-20 Thread Pieter-Jan Van Damme
Hello guys,

I've been looking for a method to get Lilypond to output to .svg but none
of the methods described online worked for me (I'm using Windows 7).

I tried:

1) using the command line... well, the documentation has left me even more
confused than before I tried it. That may be because I am not overly
familiar with the command line. And I'm suspecting the documentation is
Linux-oriented.

2) when importing a .pdf into Inkscape the note heads and clefs fail to
materialize. Somewhere online it was said I should either uninstall some
Windows updates (https://plus.google.com/+inkscape/posts/RV4qMPKFXkn -
didn't work) or install a font (didn't find the ones referenced; either
Feta ).

Would you guys have any suggestions for a novice like myself?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: thanks again for the editionEngraver

2014-07-20 Thread Jan-Peter Voigt
Hi Kieren,

I almost missed your mail ... right now I am on a rehearsal and concert
trip.

On 18.07.2014 21:02, Kieren MacMillan wrote:
> Hello all,
>
> This is just another note of thanks to everyone (especially Jan-Peter) who 
> makes things like the editionEngraver possible in Lilypond.
> The power of this tool blows my mind.
you're very welcome and I am happy to read this :)

> I’m not sure if it can be made any easier to include and implement/use, but 
> if it can, we really OWE IT to the Lilypond user-base to do so. Regardless, 
> it — or something sufficiently similar — should be part of the regular distro.

I think the most complicated part is addressing multiple voices in one
Staff. But propably there are more things to modify to make it more
intuitive. I will see, what I can do during the next two weeks.

Best, Jan-Peter


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


Re: Creating an ly:pitch? value

2014-07-20 Thread David Kastrup
Richard Shann  writes:

[...]

>> You could try
>> 
>> denemo-transpose = cis'
>
> ah - this is also Mark's suggestion. So a LilyPond assignment like that
> is defining a scheme variable of the given name to be the scheme
> structure that right hand side parses to. I get it (?). 
> (I wonder, does that mean that all sorts of standard scheme variable
> names such as "format" need to be avoided as names for LilyPond
> assignments?

Basically, yes.

> Or is some scoping stuff in play here ...)

That too.  Most uses of format before redefinition will continue to work
just fine as they are bound to the variable in the underlying GUILE
module.

-- 
David Kastrup

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


Re: Creating an ly:pitch? value

2014-07-20 Thread Richard Shann
On Sun, 2014-07-20 at 20:29 +0200, David Kastrup wrote:
> Richard Shann  writes:
> 
> > In music which has a commentary the commentary often refers to excerpts
> > from the main music. When the main music is transposed it is sometimes
> > desirable that the music excerpts in the commentary should have the same
> > transposition.
> > To save editing these separately I would like to create a music function
> > which would be invoked before both the music and any excerpts and would
> > apply a given transposition.
> >
> > I have got as far as this, for transposing up a semitone as in
> > \transpose c cis
> >
> > \version "2.18.0"
> >
> > #(define denemo-transpose (ly:make-pitch 0 0 (/ 1 2)))
> 
> You can write 1/2 instead of (/ 1 2) here.  In 2.19.0, you can actually
> write
> #(define denemo-transpose #{ cis #})
> but I am afraid that this interpretation is not available in 2.18.0
> 
> > myfunc = #(define-music-function
> >  (parser location arg)
> >  (ly:music?)
> >  #{
> > \transpose c' #denemo-transpose #arg
> >  #})
> >
> >
> > {c' d' e'
> > \myfunc 
> > {c' d' e'}}
> >
> > As you can see I have defined a global variable denemo-transpose to be
> > the pitch that c' should be transposed to.
> > My problem is that the syntax for ly:make-pitch is difficult to
> > generate, but I can't seem to find anything to convert a string like
> > "cis'" to an ly:pitch? datum.
> 
> You could try
> 
> denemo-transpose = cis'

ah - this is also Mark's suggestion. So a LilyPond assignment like that
is defining a scheme variable of the given name to be the scheme
structure that right hand side parses to. I get it (?). 
(I wonder, does that mean that all sorts of standard scheme variable
names such as "format" need to be avoided as names for LilyPond
assignments? Or is some scoping stuff in play here ...)

Thanks to both of you for speedy answers, sorry to ask what may seem so
elementary.

Richard



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


Re: Creating an ly:pitch? value

2014-07-20 Thread David Kastrup
Richard Shann  writes:

> In music which has a commentary the commentary often refers to excerpts
> from the main music. When the main music is transposed it is sometimes
> desirable that the music excerpts in the commentary should have the same
> transposition.
> To save editing these separately I would like to create a music function
> which would be invoked before both the music and any excerpts and would
> apply a given transposition.
>
> I have got as far as this, for transposing up a semitone as in
> \transpose c cis
>
> \version "2.18.0"
>
> #(define denemo-transpose (ly:make-pitch 0 0 (/ 1 2)))

You can write 1/2 instead of (/ 1 2) here.  In 2.19.0, you can actually
write
#(define denemo-transpose #{ cis #})
but I am afraid that this interpretation is not available in 2.18.0

> myfunc = #(define-music-function
>  (parser location arg)
>  (ly:music?)
>  #{
> \transpose c' #denemo-transpose #arg
>  #})
>
>
> {c' d' e'
> \myfunc 
> {c' d' e'}}
>
> As you can see I have defined a global variable denemo-transpose to be
> the pitch that c' should be transposed to.
> My problem is that the syntax for ly:make-pitch is difficult to
> generate, but I can't seem to find anything to convert a string like
> "cis'" to an ly:pitch? datum.

You could try

denemo-transpose = cis'

-- 
David Kastrup

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


Re: Creating an ly:pitch? value

2014-07-20 Thread Mark Polesky
Richard Shann wrote:
> My problem is that the syntax for ly:make-pitch is
> difficult to generate, but I can't seem to find anything
> to convert a string like "cis'" to an ly:pitch? datum.

Richard,

I'm having trouble visualizing what you're trying to
accomplish, couldn't you just do this?

**

myPitch = cis'

myfunc =
#(define-music-function
   (parser location arg)
   (ly:music?)
   #{ \transpose c' #myPitch #arg #})

{
  c' d' e'
  \myfunc { c' d' e' }
}

**

Otherwise, if for some reason you really need to convert
a string to a pitch object, here's one way to do it:

**

stringToPitch =
#(define-scheme-function
   (parser location str)
   (string?)
   (let* ((clone (ly:parser-clone parser '() location))
  (expr (ly:parse-string-expression clone str)))
   (ly:make-pitch (ly:pitch-octave expr)
  (ly:pitch-notename expr)
  (ly:pitch-alteration expr

myPitch = \stringToPitch #"cis'"

myfunc =
#(define-music-function
   (parser location arg)
   (ly:music?)
   #{ \transpose c' #myPitch #arg #})

{
  c' d' e'
  \myfunc { c' d' e' }
}

**

Hope this helps,
Mark
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Creating an ly:pitch? value

2014-07-20 Thread Richard Shann
In music which has a commentary the commentary often refers to excerpts
from the main music. When the main music is transposed it is sometimes
desirable that the music excerpts in the commentary should have the same
transposition.
To save editing these separately I would like to create a music function
which would be invoked before both the music and any excerpts and would
apply a given transposition.

I have got as far as this, for transposing up a semitone as in
\transpose c cis

\version "2.18.0"

#(define denemo-transpose (ly:make-pitch 0 0 (/ 1 2)))
myfunc = #(define-music-function
 (parser location arg)
 (ly:music?)
 #{
\transpose c' #denemo-transpose #arg
 #})


{c' d' e'
\myfunc 
{c' d' e'}}

As you can see I have defined a global variable denemo-transpose to be
the pitch that c' should be transposed to.
My problem is that the syntax for ly:make-pitch is difficult to
generate, but I can't seem to find anything to convert a string like
"cis'" to an ly:pitch? datum.
As you may guess, the code is intended to be generated programmatically
(from Denemo), which may limit the available solutions.

Any ideas?

Richard Shann



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


absolute baseline-skip

2014-07-20 Thread Karol Majewski
Hi,

I'm trying to redefine abs-fontsize from define-markup-commands.scm, so that 
baseline-skip is also absolute. Current behavior is that with abs-fontsize, 
baseline-skip scales to global-staff-size, which I don't like. I know that 
there was attempt made by Nicolas Sceaux 
(http://lilypond.1069038.n5.nabble.com/Markup-in-absolute-font-size-td34087.html),
 but no solution there. Here's original code:


#(define-markup-command (abs-fontsize layout props size arg)
  (number? markup?)
  #:category font
  (let* ((ref-size (ly:output-def-lookup layout 'text-font-size 12))
 (text-props (list (ly:output-def-lookup layout 'text-font-defaults)))
 (ref-word-space (chain-assoc-get 'word-space text-props 0.6))
 (ref-baseline (chain-assoc-get 'baseline-skip text-props 3))
 (magnification (/ size ref-size)))
(interpret-markup
 layout
 (cons
  `((baseline-skip . ,(* magnification ref-baseline))
(word-space . ,(* magnification ref-word-space))
(font-size . ,(magnification->font-size magnification)))
  props)
 arg)))


If you have any ideas, please share! Perhaps something like abs-baseline-skip 
is needed?

--Karol



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


Re: Default margins in Letter truncated

2014-07-20 Thread David Kastrup
Marc Mouries  writes:

> The doc says here:
> http://www.lilypond.org/doc/v2.18/Documentation/notation/the-paper-block
> says: "Except when specified otherwise, all \paper variables that
> correspond to distances on the page are measured in millimeters, unless a
> different unit is specified by the user. For example, the following
> declaration sets top-margin to ten millimeters:
>
> \paper {
>   top-margin = 10
> }
>
> "
>
>
> On Sun, Jul 20, 2014 at 8:58 AM, David Kastrup  wrote:
>
>> MarcM  writes:
>>
>> > I just set annotate-spacing = ##t and it's showing a 2.85
>> millimeters.
>> > That's pretty small. I don't remember being that small.
>> > <
>> http://lilypond.1069038.n5.nabble.com/file/n164707/top-margin_Lilypond_2014-07-20_at_8.png
>> >
>> >
>> > I added:
>> >   top-margin= 2\cm
>> >
>> > and it's showing a margin of 11.38. Shouldn't it be 20 ?
>> >
>> > 
>>
>> Sure that the units are mm rather than staff spaces?

Sure that the _displayed_ units are mm rather than staff spaces?

-- 
David Kastrup

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


Re: Default margins in Letter truncated

2014-07-20 Thread MarcM
The doc says here:
http://www.lilypond.org/doc/v2.18/Documentation/notation/the-paper-block
says: "Except when specified otherwise, all \paper variables that correspond
to distances on the page are measured in millimeters, unless a different
unit is specified by the user. For example, the following declaration sets
top-margin to ten millimeters:
 \paper {
  top-margin = 10
}
"




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Default-margins-in-Letter-truncated-tp164683p164711.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: Default margins in Letter truncated

2014-07-20 Thread Marc Mouries
The doc says here:
http://www.lilypond.org/doc/v2.18/Documentation/notation/the-paper-block
says: "Except when specified otherwise, all \paper variables that
correspond to distances on the page are measured in millimeters, unless a
different unit is specified by the user. For example, the following
declaration sets top-margin to ten millimeters:

\paper {
  top-margin = 10
}

"


On Sun, Jul 20, 2014 at 8:58 AM, David Kastrup  wrote:

> MarcM  writes:
>
> > I just set annotate-spacing = ##t and it's showing a 2.85
> millimeters.
> > That's pretty small. I don't remember being that small.
> > <
> http://lilypond.1069038.n5.nabble.com/file/n164707/top-margin_Lilypond_2014-07-20_at_8.png
> >
> >
> > I added:
> >   top-margin= 2\cm
> >
> > and it's showing a margin of 11.38. Shouldn't it be 20 ?
> >
> > 
>
> Sure that the units are mm rather than staff spaces?
>
> --
> David Kastrup
>



-- 
Marc Mouries
571-428-6771
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Default margins in Letter truncated

2014-07-20 Thread David Kastrup
MarcM  writes:

> I just set annotate-spacing = ##t and it's showing a 2.85 millimeters.
> That's pretty small. I don't remember being that small.
> 
>  
>
> I added:  
>   top-margin= 2\cm
>
> and it's showing a margin of 11.38. Shouldn't it be 20 ?
>
>  

Sure that the units are mm rather than staff spaces?

-- 
David Kastrup

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


Re: Template: String Quartet (score-only), first draft

2014-07-20 Thread MarcM
I found this thread via google and it dates from few years back.

I include the sample at the end of this mail.

You can compare it with the one here:
http://www.lilypond.org/doc/v2.18/Documentation/learning/string-quartet


The documentation shows a sample for string quartet parts  which requires to
uncomment lines.
http://www.lilypond.org/doc/v2.18/Documentation/learning/string-quartet-parts

Would anyone already have another template for quartet part that does not 
 require to uncomment lines of code like the one in the documentation? 
 When i am working on each part i want to print the score of the part then 
 if  i need to print the set of parts i just want to open the 
 quartet_AllParts.ly, typeset and print without having to uncomment lines 
of code everytime.


- String Quartet Template from Kieran - 


\version "2.11.55" 

\header 
{ 
title = "Quartett für 2 Violinen, Viola und Violoncell" 
composer = "Wolfgang Amadeus Mozart" 
} 

global = 
{ 
\time 4/4 
\key c \major 
s1*4 
\bar "|." 
} 

violinOneNotes = \relative c' 
{ 
c4.(\p d8) e4-. e-.   | % 1 
e8( d f e d4) r   | % 2 
d4.(\p e8) f4-. f-.   | % 3 
f8( e g f e4) r   | % 4 
} 

violinTwoNotes = \relative c' 
{ 
c4.(\p b8) c4-. c-.   | % 1 
c8( b d c b4) r   | % 2 
b4.(\p c8) d4-. d-.   | % 3 
d8( c e d c4) r   | % 4 
} 

violaNotes = \relative c' 
{ 
\clef alto 
g1\p ~   | % 1 
g2 ~ g8( b d b)   | % 2 
g1 ~   | % 3 
g2 ~ g8 e'( g e)   | % 2 
} 

celloNotes = \relative c 
{ 
\clef bass 
c8\p c c c c c c c   | % 1 
g g g g g4 r   | % 2 
g8 g g g g g g g   | % 3 
c c c c c4 r   | % 4 
} 

\score 
{ 
\new StaffGroup 
<< 
\new Staff \with { instrumentName = "Violin I" } 
<< \global \violinOneNotes >> 
\new Staff \with { instrumentName = "Violin II" } 
<< \global \violinTwoNotes >> 
\new Staff \with { instrumentName = "Viola" } 
<< \global \violaNotes >> 
\new Staff \with { instrumentName = "Violoncello" } 
<< \global \celloNotes >> 
>> 

\layout { } 
%\midi { }  %% uncomment this line to enable MIDI output 
} 
 






--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/no-subject-tp34746p164708.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: Default margins in Letter truncated

2014-07-20 Thread MarcM

I just set annotate-spacing = ##t and it's showing a 2.85 millimeters.
That's pretty small. I don't remember being that small.

 

I added:  
  top-margin= 2\cm

and it's showing a margin of 11.38. Shouldn't it be 20 ?

 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Default-margins-in-Letter-truncated-tp164683p164707.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: Default margins in Letter truncated

2014-07-20 Thread Robin Bannister

MarcM wrote:


I am wondering if this is an expected behavior or something is wrong my
computer and/or printer (HP Officejet Pro).
.
.
.
When i print with the default settings the margins are truncated and the
only half of the title of the piece is printed.


Does your printer maybe have an option called "Borderless Printing"?


Cheers,
Robin

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


Re: Default margins in Letter truncated

2014-07-20 Thread David Kastrup
MarcM  writes:

> I am wondering if this is an expected behavior or something is wrong my
> computer and/or printer (HP Officejet Pro).
>
> My music is set with \paper {   #(set-paper-size "letter")}
>
> I print on a printer on which the default paper is "letter"
>
> When i print with the default settings the margins are truncated and the
> only half of the title of the piece is printed. To print correctly i have to
> select the option to "print the entire image" which scale the page down to
> 91%. Is that normal?

Well, check your PDF file in a PDF viewer.  Most importantly, check the
paper format.  If it is indeed letter and properly positioned, the
problem is when going from PDF to your printer.

-- 
David Kastrup

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


Re: [SPAM] Re: [openlilylib] Discuss restructuring

2014-07-20 Thread Urs Liska

Am 20.07.2014 11:10, schrieb Janek Warchoł:

Hi folks,

as you can see, i'm falling behind with lilypond stuff, but i wanted
to let you know that i've skimmed through this discussion and it LGTM.
The only comment i have is: try to make things as simple as possible
(but not simpler, of course) - i wouldn't like openlilylib getting a
"java-smell" from trying to be overly generic and all-encompassing.
Please continue with my blessing ;-)

best,
Janek



I'll try to find a way through the options. I think that when there is 
an automatic way to generate the documentation this will encourage 
authors to do it right in the first place. Just an example: The 
"description" header field will be used in the documentation. And when 
one sees this in the HTML docs one will voluntarily take care of having 
a good description.


But I'll try to keep the complexity as low as possible.
I think the decision to have a single directory for all include files 
was a good one in that respect.


Best
Urs


2014-07-08 12:42 GMT+02:00 Urs Liska :

Am 07.07.2014 16:48, schrieb Paul Morris:


Urs Liska wrote



Hm, I think I_must not_  start with such a script right now, since I



know that this - although being not too complex - will eat up too much
of my time and concentration.

But your message triggered a little bit of thought, and I came to the
conclusion that we should use a website (i.e. openlilylib.org) for the
documentation.
The script will have two stages: parsing the content of the library and
generating documentation from the resulting internal representation. I
think generating complete HTML pages isn't more complicated than
generating Markdown, but the results are better to use: We have more
control over the layout and formatting options than on a Github Wiki,
_and_  we have a self-contained HTML site that can also be deployed
locally.


Yep.



This might be a good opportunity to get my feet wet with PyQt, i.e. not to
write a _script_ but an application. Initially this wouldn't do much more
than a mere script, but with more convenient interactivity. Later it could
add an interface to _edit_ the metadata (e.g. selecting from existing tags,
batch renaming of tags etc.) and also the documentation strings themselves.
And it can even incorporate a convenient documentation browser.

I think we should target the documentation output to be a self-contained
HTML site in the repository itself (in a /doc directory) and only them
consider making it available online too.

At least with the HTML part of such a documentation I'd be glad for
assistance (if I really get this started at all). Not that I'm unable to do
that part but others can do that better, and it's a convenient split-point
to share work.

Best
Urs


___
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




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


Re: Default margins in Letter truncated

2014-07-20 Thread Phil Holmes
- Original Message - 
From: "MarcM" 

To: 
Sent: Sunday, July 20, 2014 5:38 AM
Subject: Default margins in Letter truncated




I am wondering if this is an expected behavior or something is wrong my
computer and/or printer (HP Officejet Pro).

My music is set with \paper {   #(set-paper-size "letter")}

I print on a printer on which the default paper is "letter"

When i print with the default settings the margins are truncated and the
only half of the title of the piece is printed. To print correctly i have 
to

select the option to "print the entire image" which scale the page down to
91%. Is that normal?



I would guess your printer has a top margin that is larger than LilyPond 
sets by default, and larger than most printers.  Have you tried setting a 
larger top-margin?


--
Phil Holmes 



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


Re: Template: String Quartet (score-only), first draft

2014-07-20 Thread Phil Holmes
- Original Message - 
From: "MarcM" 

To: 
Sent: Sunday, July 20, 2014 5:23 AM
Subject: Re: Template: String Quartet (score-only), first draft





1) This String quartet example is much nicer than the one in the current
documentation.
http://www.lilypond.org/doc/v2.18/Documentation/learning/string-quartet

Can we include it in the documentation?


2) Would anyone already have another template for quartet part that does 
not

require to uncomment lines of code like the one in the documentation?
When i am working on each part i want to print the score of the part then 
if

i need to print the set of parts i just want to open the
quartet_AllParts.ly, typeset and print without having to uncomment lines 
of

code everytime.



Sorry, Marc, I don't follow you.  Which template?  Which commented lines?

--
Phil Holmes 



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


Re: Template: String Quartet (score-only), first draft

2014-07-20 Thread James
On 20/07/14 05:23, MarcM wrote:
>
> 1) This String quartet example is much nicer than the one in the current
> documentation. 
> http://www.lilypond.org/doc/v2.18/Documentation/learning/string-quartet
>
> Can we include it in the documentation?
>
>
>

Maybe I am going mad but when I am trying to look at the thread to this
to find out what example ' ... is much nicer ...' I am being taken back
to conversations from 2008!

Would you care to elaborate a bit more Marc (in case I am wrong) as I
cannot find anything else pertaining to this email.

James

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


Re: shiftOn shifts to the left

2014-07-20 Thread Alberto Simões

Hello, Abraham


I think part of the confusion is the musical context for what you are trying
to do. Is this something of your creation or are you transcribing an
existing score that we could look at to get a better understanding?


Yes, I was trying to mimic an existing score. That note is from a third 
voice in the staff below. I know I can change staff, but I though it 
would be easier adding it artificially.



2. Make the "e2." the only "\voiceTwo" notehead at that point in question
and put a spacer where the second voice's "e" would be.

\score {
   \new Staff \relative c'' <<
 {
   \time 3/4
   a4 b c
 }\\<<
   { s4 g a ~ | 2. }
   \new Voice { \voiceTwo e2. | s2. }
 >>
   >>
   \layout{}
}




Yes, this would be an option, but then I miss a note :-)

Oh well, thank you for your help. I will keep the note at the left :)

Best,
Alberto

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


Re: [openlilylib] Discuss restructuring

2014-07-20 Thread Janek Warchoł
Hi folks,

as you can see, i'm falling behind with lilypond stuff, but i wanted
to let you know that i've skimmed through this discussion and it LGTM.
The only comment i have is: try to make things as simple as possible
(but not simpler, of course) - i wouldn't like openlilylib getting a
"java-smell" from trying to be overly generic and all-encompassing.
Please continue with my blessing ;-)

best,
Janek

2014-07-08 12:42 GMT+02:00 Urs Liska :
> Am 07.07.2014 16:48, schrieb Paul Morris:
>>
>> Urs Liska wrote
>>>
>>> >Hm, I think I_must not_  start with such a script right now, since I
>>>
>>> >know that this - although being not too complex - will eat up too much
>>> >of my time and concentration.
>>> >
>>> >But your message triggered a little bit of thought, and I came to the
>>> >conclusion that we should use a website (i.e. openlilylib.org) for the
>>> >documentation.
>>> >The script will have two stages: parsing the content of the library and
>>> >generating documentation from the resulting internal representation. I
>>> >think generating complete HTML pages isn't more complicated than
>>> >generating Markdown, but the results are better to use: We have more
>>> >control over the layout and formatting options than on a Github Wiki,
>>> >_and_  we have a self-contained HTML site that can also be deployed
>>> >locally.
>>
>> Yep.
>
>
> This might be a good opportunity to get my feet wet with PyQt, i.e. not to
> write a _script_ but an application. Initially this wouldn't do much more
> than a mere script, but with more convenient interactivity. Later it could
> add an interface to _edit_ the metadata (e.g. selecting from existing tags,
> batch renaming of tags etc.) and also the documentation strings themselves.
> And it can even incorporate a convenient documentation browser.
>
> I think we should target the documentation output to be a self-contained
> HTML site in the repository itself (in a /doc directory) and only them
> consider making it available online too.
>
> At least with the HTML part of such a documentation I'd be glad for
> assistance (if I really get this started at all). Not that I'm unable to do
> that part but others can do that better, and it's a convenient split-point
> to share work.
>
> Best
> Urs
>
>
> ___
> 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: Alternative partcombine strategy possible?

2014-07-20 Thread Janek Warchoł
Hi Xavier,

sorry for delay.

2014-07-11 15:59 GMT+02:00 Xavier Scheuer :
> On 11 July 2014 15:08, Janek Warchoł  wrote:
>> https://github.com/openlilylib/openlilylib/tree/master/editorial-tools/merge-rests-engraver
>
> Hi Janek,
>
> Could this definition of Merge Rests Engraver (latest by Jay Anderson)
> be included directly in LilyPond?
>
> AFAICS it is quite different from the first version by Wilbert Berendsen
> and maybe the earliest comments that the way it was (firstly)
> implemented made it unsuitable to be merged directly into LilyPond are
> not valid anymore.
>
> https://code.google.com/p/lilypond/issues/detail?id=1228

Indeed, it seems that the approach used by Jay is the correct one
(i.e. using an engraver).

Would you like to help with making a patch and shepherding it through
the review process? As you can see, i don't have enough time for
lilypond work, so cannot do it myself.  Of course, i know that this is
an involved process, so i'm willing to offer you assistance (short
Skype call every other day).  It seems to me that Jay's code is of
good quality, so it shouldn't require a lot of work.

best,
Janek

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


Re: Articles on church music on Github in LilyPond format

2014-07-20 Thread Janek Warchoł
2014-07-17 4:01 GMT+02:00 Paul Morris :
> I came across a couple of articles on church music on Github in LilyPond
> format.  (Organ accompaniments for Gregorian Chant, a LilyPond transcription
> of the Nova Organi Harmonia.)
>
> http://createdigitalmusic.com/2014/07/fork-chant-github-goes-gregorian-open-source-notation/
>
> http://www.wired.com/2013/05/gregorian_github/
>
> Does this qualifies for a "ponding"?  In any case I thought it might be of
> interest.  Too bad the Wired article doesn't mention that it's LilyPond file
> format...

It's been done before (i have quite some music on github) but i think
it's worth a ponding anyway.

best,
Janek

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


Re: LilyPond meeting 2014?

2014-07-20 Thread Janek Warchoł
2014-07-17 8:41 GMT+02:00 Jan-Peter Voigt :
> Hi all,
>
> I'd also like to join the party, but I am quite busy in the next time. I
> would like to join in for a session via skype or google-hang-out or
> similar - I could talk about and discuss the edition-engraver.
> Online-participation might be an option for users outside europe?

Absolutely, but right now i'm not sure if there's not enough people
that could gather at one place at the same time.

Janek

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


Re: shiftOn shifts to the left

2014-07-20 Thread tisimst
Alberto Simões-2 wrote
> Dear Mark
> 
> Thank you for pointing me yet again to that page. This is the third time 
> I read it, and only now I noticed this sentence:
> 
>"When a shift is applied, voices with upstems (odd-numbered voices) 
> are shifted to the right, and voices with downstems (even-numbered 
> voices) are shifted to the left."
> 
> So, it doesn't matter what voices I choose (even if the text says 
> "even-numbered voices"), if I choose for force the stem down, then it 
> will be shifted left.
> 
> So, to get what I want I might need some kind of absolute positioning. 
> But I will keep it that way. Was just trying to understand how changing 
> stems changed note positioning.
> 
> Best,
> ambs

Alberto,

I think part of the confusion is the musical context for what you are trying
to do. Is this something of your creation or are you transcribing an
existing score that we could look at to get a better understanding?

Based on this discussion, it seems like you have two options:

1. Apply the "\voiceThree" to the "e2." which shifts the notehead to the
right, but puts the stem up, 

\score {
  \new Staff \relative c'' <<
{
  \time 3/4
  a4 b c
}\\<<
  { e,4 g a ~ | 2. } 
  \new Voice { \voiceThree e2. | s2. } 
>>
  >>
  \layout{}
}

 

or

2. Make the "e2." the only "\voiceTwo" notehead at that point in question
and put a spacer where the second voice's "e" would be.

\score {
  \new Staff \relative c'' <<
{
  \time 3/4
  a4 b c
}\\<<
  { s4 g a ~ | 2. } 
  \new Voice { \voiceTwo e2. | s2. } 
>>
  >>
  \layout{}
}

 

Personally, i like the second option better. Either way, proper usage of the
\voiceX commands  and "\\" syntax should provide the right solution.

Hope that helps,
Abraham

P.S. Changing the stem direction changes the note's NoteColumn for collision
identification, it doesn't _necessarily_ change the voice.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/shiftOn-shifts-to-the-left-tp164653p164684.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