Re: Possible Bug with \numericTimeSignature

[Urs Liska]

Am 13.05.2014 04:56, schrieb Keith OHara:

Whenever you write a grace note in LilyPond, you need grace
n


Fortunately that's not _whenever_ but only in situations at events like 
time signature (changes).


Urs

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

Re: Possible Bug with \numericTimeSignature

[Keith OHara]

Joshua Nichols  gmail.com> writes:

> I've never experienced this before now...

Oops, I just realized you mean the grace-note bug.

Whenever you write a grace note in LilyPond, you need grace
notes or skips of the same duration in every other staff.

So here in the upper staff you need \grace {s8}


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

Re: Possible Bug with \numericTimeSignature

[Keith OHara]

Joshua Nichols  gmail.com> writes:

> global = {
>   \key c \major
>   \numericTimeSignature

It is a bug, but you can fix this one yourself if you like.

In 'property-init.ly' the definition is
numericTimeSignature = \override Staff.TimeSignature.style = #'numbered
but we want it to apply to the entire Score, not just one Staff.




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

Possible Bug with \numericTimeSignature

[Joshua Nichols]

I've never experienced this before now...

I go to use the following settings:

global = {

\key c \major

\numericTimeSignature

\time 4/4

\tempo 4=100

}


and I got the attached picture. I have no idea what I'm doing wrong, or if
this is a bug worth noting.
I was using absolute pitch mode. Thanks in advance.


Sincerely,

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

Re: "dal segno" several times

[Jim Long]

On Mon, May 12, 2014 at 05:53:33PM -0400, David Raleigh Arnold wrote:
> On Mon, 12 May 2014 12:56:27 -0700
> Jim Long  wrote:
> 
> > On Mon, May 12, 2014 at 12:18:37PM +0100, Carlo Vanoni wrote:
> > > 
> > > I have a simple song, where the verse is 4 measures repeated
> > > twice, and the chorus again 4 measures repeated twice.
> 
> What would you do if you had seven verses? Or twenty?

I would still give the same advice:  Don't write

(Intro)
/Segno/
|: 4-bar verse  :|
|: 4-bar chorus :| "D.S. 7 times" (or 20)
(Outro)

but instead write:

(Intro)
|: 8-bar verse   |
|  8-bar chorus :| "play 7 times" (or 20)
(Outro)

The OP didn't mention lyrics, but sure, if there are some,
stack the stanzas up 7 or 20 deep under the melody staff.  Or
perhaps if there are that many stanzas, list them at the end
of the music, as per

http://lilypond.org/doc/v2.18/Documentation/notation/stanzas#printing-stanzas-at-the-end

Then the performer should see pretty clearly how many times to
play the verse-chorus pair.



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

Re: "dal segno" several times

[David Raleigh Arnold]

On Mon, 12 May 2014 12:56:27 -0700
Jim Long  wrote:

> On Mon, May 12, 2014 at 12:18:37PM +0100, Carlo Vanoni wrote:
> > 
> > I have a simple song, where the verse is 4 measures repeated
> > twice, and the chorus again 4 measures repeated twice.

What would you do if you had seven verses? Or twenty?
Indicate what is verse and what is chorus, and with two
or three lines of lyrics underneath the music, repeat signs are not 
necessary at all.

 Regards, Rale

-- 
Guitar teaching materials and original music for all styles and
levels. Site: http://www.openguitar.com (()) eMail:
d.raleigh.arn...@gmail.com Contact:
http://www.openguitar.com/contact.html



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

Re: Issue with jazz-test.ly

[Steve Noland]

Ahhh...thank you!

Steve

On May 12, 2014, at 12:55 PM, Federico Bruni 
mailto:fedel...@gmail.com>> wrote:

2014-05-12 20:45 GMT+02:00 safvet 
mailto:st...@thenolands.us>>:
Downloaded fresh copy of jazz-chords.ily and jazz-test.ly 
from the
"canonical" site:

http://lists.gnu.org/archive/html/lilypond-user/2011-11/msg00285.html

Opened jazz-test lily, updated using convert-ly for 2.18.2, and compiled
file.  It yielded a PDF and Midi output, but also gave the attached error
log.

Suggestions?

LilyPond_--_jazz-test.pdf



I think that you forgot to update jazz-chords.ily (see attached screenshot).
It's compiling without errors here.

Try attached files
http://jazz-test.ly>>

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

Frescobaldi/Mac question

[Tim McNamara]

Running convert-ly results in:

 Traceback (most recent call last):
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/py2app/apptemplate/lib/site.py",
 line 22, in 
import os
zipimport.ZipImportError: can't decompress data; zlib not available



“locate zlib” finds multiple instances including slib.h, zlib.so, zlib.py, 
zlib.pyc, zlib.pyo, zlib.tcl, etc..  I’ve got zlib coming out of my ears.  
What’s being looked for that I don’t have?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: multiple marks

[Simon Albrecht]

Am 12.05.2014 14:11, schrieb Carlo Vanoni:

Hi everyone,

I'm using this nice function to add a right-aligned text that states 
the number of repeats of a repeat block:

repeatMark =
#(define-music-function
 (parser location volte visible)
 (number? boolean?)
 (if visible
   #{
 \once \override Score.RehearsalMark #'break-visibility =
 #begin-of-line-invisible
 \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
 \once \override Score.RehearsalMark #'font-size = #0
 \mark \markup $(string-join (list "repeat" (number->string volte)
 "times"))
   #}
   #{ #}
   ))

It is called with this code at the end of a section
\repeatMark #4 ##t% writes "repeat 4 times"

I usually wrote section name using a markup on single notes 
(a1^\markup{ \bold Intro}). Now I'm separating the various song 
sections in different variables. Since the same section can be used, 
e.g., as a chorus and during the solo, I need to write the section 
name using a \mark before the section in the main score. This 
unfortunately generates a "multiple mark" error when repeats are involved.
The following might help you: 
http://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00157.html
It defines a multi-mark-engraver, which allows to have more than one 
mark at the same point of time.


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

Re: multiple marks

[Jim Long]

On Mon, May 12, 2014 at 01:11:03PM +0100, Carlo Vanoni wrote:
> Hi everyone,
> 
> I'm using this nice function to add a right-aligned text that states the 
> number of repeats of a repeat block:

[snip]

> It is called with this code at the end of a section
> \repeatMark #4 ##t??? % writes "repeat 4 times"

For clarity, you may want to consider changing your code to say
"play 4 times", assuming that is what you mean.  Others on this
list have raised this point in the past, so while I agree with
their reasons, I can't credit for the original idea.

I'll leave the multiple marks issue for someone else, but you
may find the LSR helpful, as I recall.


Jim



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

Re: "dal segno" several times

[Jim Long]

On Mon, May 12, 2014 at 12:18:37PM +0100, Carlo Vanoni wrote:
> 
> I have a simple song, where the verse is 4 measures repeated twice, and the 
> chorus again 4 measures repeated twice.

[snip]

> I can print all the section as stated above, but it will be easier to have 
> something like this
> intro
> ||: verse
> chorus :|| x3 times
> outro

If the verse and the chorus are so brief, I would not engrave
repeat bar lines around the four-bar repeated sections, only the
outer "3x" repeat that wraps the entire 16-bar verse-chorus
section.

If you wish, you could use 'repeat unfold' in your code:

myVerse = \relative f {
% four bars, engraved twice:
  \repeat unfold 2 {
a1 b1 c1 b1
  }
} % myVerse

myChorus = \relative f {
% four bars, engraved twice:
  \repeat unfold 2 {
c1 a1 b1 a1 
  }
} % myChorus

threeTimes = \repeat 3 {
  \myVerse
  \myChorus
}


Jim


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

Issue with jazz-test.ly

[safvet]

Downloaded fresh copy of jazz-chords.ily and jazz-test.ly from the
"canonical" site:

http://lists.gnu.org/archive/html/lilypond-user/2011-11/msg00285.html

Opened jazz-test lily, updated using convert-ly for 2.18.2, and compiled
file.  It yielded a PDF and Midi output, but also gave the attached error
log.  

Suggestions?

LilyPond_--_jazz-test.pdf
  





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Issue-with-jazz-test-ly-tp162359.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: split system

[Steven Arntson]

This is what I will do--thank you!

-steven

Knute Snortum  writes:

> Well, you can use two different scores for the different systems:
>
> \version "2.18.2"
>
> mainPiece = {
> c4 d e f g a b c d c b a g f e d c1
> \bar "||"
> }
>
> \score {
> \new PianoStaff <<
> \new Staff {
> \relative c' {
> \mainPiece
> }
> }
> \new Staff {
> \clef bass
> \relative c {
> \mainPiece
> }
> }
>>>
> }
>
> \score {
> \new PianoStaff <<
> \new Staff {
> \relative c' {
> c4 \coda c c c \bar "|."
> }
> }
> \new Staff {
> \relative c {
> \clef bass
> \relative c {
> c c c c
> }
> }
> }
>>>
> }
>
> Knute Snortum
> (via Gmail)
>
> On Sun, May 11, 2014 at 8:29 PM, Steven Arntson
>  wrote:
>
> I'm trying to learn how to set up a coda for a piano piece, which
> seems
> complex to me right now, so I'm breaking the process into parts.
> Part
> one is to figure out how to split the system--ending the regular
> music,
> and starting the coda section--which I think should be done with
> some
> combination of \stopStaff and \startStaff, but I can't get it
> working. Am I barking up the right tree?
> 
> Thank you!
> Steven Arntson
> 
> 
> ___
> 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: Problem with Staff Grouping

[Phil Holmes]

- Original Message - 
From: "Dave Higgins" 

To: 
Sent: Monday, May 12, 2014 6:14 PM
Subject: Re: Problem with Staff Grouping



What's happening is that part1 has a single staff and then splits into a
divisi staff.  In that part's compilation, everything looks fine.

I also have a part2 that does the same thing, single staff that splits
into a divisi staff.

The staves are out of order when I compile the score, as the layout
description below indicates.

I'm not saying the staff feature is broken, just my staff lines in the
score are in the wrong places.


I think you'll find this is easiest by having all the staves present at all 
times, but hiding empty ones.  See


http://lilypond.org/doc/v2.18/Documentation/notation/modifying-single-staves#hiding-staves

and in particular, RemoveEmptyStaves and override 
VerticalAxisGroup.remove-first = ##t


--
Phil Holmes 



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

Re: Problem with Staff Grouping

[Dave Higgins]

What's happening is that part1 has a single staff and then splits into a
divisi staff.  In that part's compilation, everything looks fine.

I also have a part2 that does the same thing, single staff that splits
into a divisi staff.

The staves are out of order when I compile the score, as the layout
description below indicates.

I'm not saying the staff feature is broken, just my staff lines in the
score are in the wrong places.

On 05/12/2014 11:06 AM, Phil Holmes wrote:
> - Original Message - From: "Dave Higgins" 
> To: 
> Sent: Monday, May 12, 2014 4:42 PM
> Subject: Re: Problem with Staff Grouping
> 
> 
>> Without the includes.  Sorry.
>>
>> On 05/12/2014 09:41 AM, Dave Higgins wrote:
>>> Revisiting with a compilable example...
>>>
>>> I'm transcribing a piece that has multiple parts and in those multiple
>>> parts, I have multiple staves.
>>>
>>> After compiling, the staff layout becomes:
>>> part1:staff1
>>> part2:staff1
>>> part1:staff2
>>> part2:staff2
>>>
>>> Obviously for the score, I'd like:
>>> part1:staff1
>>> part1:staff2
>>> part2:staff1
>>> part2:staff2
>>>
>>> I'm sure I just have something not correct.
>>>
>>>
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> I'm afraid I can't follow what it is you're trying to do.  However, you
> may find some help on the documentation for vocal music:
> 
> http://lilypond.org/doc/v2.18/Documentation/notation/opera-and-stage-musicals
> 
> 
> -- 
> Phil Holmes

-- 
Dave Higgins
Littleton, Colorado
dave.higg...@dkds.us
See my photos at
https://www.dkds.us/gallery3
--
Hanging on in quiet desperation is the English way.
-- Pink Floyd

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

Re: [SPAM] Re: Transcribing individual score pages from scans

[David Cuenca]

On Mon, May 12, 2014 at 5:46 PM, Urs Liska  wrote:

> What I haven't fully understood yet is how your users are entering
> content. Do they have an input field on a web page that they submit?
>

Yes, there is a text input field. For instance this page:
https://en.wikisource.org/wiki/Page:Childs_own_music_book.djvu/52

When you click "edit" becomes:
https://en.wikisource.org/w/index.php?title=Page:Childs_own_music_book.djvu/52&action=edit

And there you can write the lilypond code wrapped with  and 

>
> Then I'd repeat my suggestion. Let them enter parts of the content one by
> one, presumably providing them with user interface elements to define
> exactly what they are meaning (e.g. "the violin part for page 3").
> If you can't use variables in LilyPond's safe mode then you might want to
> preprocess this input with a server side script. That is: store all
> fragments in individual text files with LilyPond variables, and before
> passing anything to LilyPond let some script generate a "flat" LilyPond
> file without variables.


I thought that maybe we could use comments to signal the different parts to
a script to generat the "flat" version, but then I realized that there are
many special cases, like "add lyrics" and I am unsure about how well it
would play with Lilypond structure... It seems like forcing the sw to do
something it is not prepared to..

About pre-parsing the variables before calling lilypond, I will have to ask
the developer who wrote the extension to see if it is possible with the
current pipeline.

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

Re: Problem with Staff Grouping

[Phil Holmes]

- Original Message - 
From: "Dave Higgins" 

To: 
Sent: Monday, May 12, 2014 4:42 PM
Subject: Re: Problem with Staff Grouping



Without the includes.  Sorry.

On 05/12/2014 09:41 AM, Dave Higgins wrote:

Revisiting with a compilable example...

I'm transcribing a piece that has multiple parts and in those multiple
parts, I have multiple staves.

After compiling, the staff layout becomes:
part1:staff1
part2:staff1
part1:staff2
part2:staff2

Obviously for the score, I'd like:
part1:staff1
part1:staff2
part2:staff1
part2:staff2

I'm sure I just have something not correct.


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


I'm afraid I can't follow what it is you're trying to do.  However, you may 
find some help on the documentation for vocal music:


http://lilypond.org/doc/v2.18/Documentation/notation/opera-and-stage-musicals

--
Phil Holmes 



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

Re: Transposing instruments in orchestra score

[Jan-Peter Voigt]

Hello,

I added a snippet to open-lily-lib:
https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose

README follows.

Best, Jan-Peter

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

Re: [SPAM] Re: Transcribing individual score pages from scans

[Urs Liska]

Am 12.05.2014 17:37, schrieb David Cuenca:

Hi Federico,

What I need is the ability to generate score in two view modes: each page
individually, or all pages together.

Imagine the use case. A user works page scan by page scan to make the
lilypond engraving look exactly like it was originally published (possible
already). Then they want to visualize all pages together (possible but only
as images, one after the other), and finally they want to download a single
.ly file or to render a typeset pdf, or generate a midi file from all the
pages together (not possible).

Yes, with the mediawiki extension we already can put all pages together
(see [1], if you hover your mouse over the small number on the left you
will see that is composed of two pages "100", "101"). When you click on
that number you go to the page view of either one, and  if you click edit
you will see the lilypond source of the corresponding page. But to
associate several independent pages as a bundle (for rendering, download,
or midi generation), that doesn't work.

 From our side we are considering each page as an individual independent
file. It was suggested by Urs to use one variable for each page, and then
render them either individually (when the user is in page view) or all
together (when the user request a download of the whole book/score).
However, lilypond is running in safe mode, thus variables are not
supported...

I hope I have better explained the problem now... any ideas about how to
proceed?


What I haven't fully understood yet is how your users are entering 
content. Do they have an input field on a web page that they submit?


Then I'd repeat my suggestion. Let them enter parts of the content one 
by one, presumably providing them with user interface elements to define 
exactly what they are meaning (e.g. "the violin part for page 3").
If you can't use variables in LilyPond's safe mode then you might want 
to preprocess this input with a server side script. That is: store all 
fragments in individual text files with LilyPond variables, and before 
passing anything to LilyPond let some script generate a "flat" LilyPond 
file without variables.


HTH
Urs




If you want to dig deeper you can take a look to our Extension:Proofread
Page [2] which manages transclusion. And if you'd like to go even a step
further and have a test environment, it is easy to set up a virtual machine
with Vagrant [3].

Cheers,
Micru

[1]
https://ca.wikisource.org/wiki/Segona_serie_de_can%C3%A7ons_populars_catalanes/Fum,_fum,_fum
[2] https://www.mediawiki.org/wiki/Extension:Proofread_Page
[3] https://www.mediawiki.org/wiki/MediaWiki-Vagrant



On Mon, May 12, 2014 at 4:53 PM, Federico Bruni  wrote:


Hi David

I haven't totally understood what you need, but it seems to me that what
you are looking for should be achieved by the Mediawiki extension, not by
LilyPond.



2014-05-09 13:21 GMT+02:00 David Cuenca :

Hi Urs,


unfortunately we cannot work with files, nor variables. The only thing we
can do is to join text inputs. What we are after is a way to append the
source texts that generate individual pages and generate a valid lilypond
input just by adding a header/footer.

Is that possible?

Thanks
David


On Fri, May 9, 2014 at 12:31 PM, Urs Liska  wrote:


Am 09.05.2014 12:26, schrieb Urs Liska:

  Am 09.05.2014 12:16, schrieb David Cuenca:



Hi,

I'm a contributor from Wikisource, an online digital library part of
the
Wikimedia Foundation, where we transcribe works in the public domain.
Since
last year we have enabled a mediawiki extension to render scores [1],
which
now enables our users to transcribe pages with music like these [2] [3]

Of course that is great when a work is only one page long, but for us
it
becomes problematic to stitch together all the different pages into a
single one (what we call "transclusion").
Some users are just considering each page independent, but that doesn't
allow us to generate a whole lilypond file for download. For instance
check
this Catalan song [4], if you click on "edit" you will see that we are
combining two pages [5] and [6], where the text resides.

What we would like is to combine these pages to generate the lilypond
file.
I have been checking the input structure documentation [7] and I found
"\book" and "\bookpart", but I didn't see anything like "\bookpage".
Is there any command that would help us to achieve the page separation
that
we need?



If I'm not mistaken that should be quite easy to achieve.
You can organize LilyPond input in variables, and you can combine those
variables to larger units. That is, you don't use variables only to
store the different parts in a score, but you can also separate
different sections of it.

I'm not completely sure if that fits your use case, but you may have a
start with something like:

violinPageI = ŗelative c'' {
% some music
}

violinPageII = ŗelative c'' {
% some music
}

violinMusic = {
\violinPageI
\violinPageII
}

\score {
\new Staff \violinMusic

Re: Problem with Staff Grouping

[Dave Higgins]

Without the includes.  Sorry.

On 05/12/2014 09:41 AM, Dave Higgins wrote:

Revisiting with a compilable example...

I'm transcribing a piece that has multiple parts and in those multiple
parts, I have multiple staves.

After compiling, the staff layout becomes:
part1:staff1
part2:staff1
part1:staff2
part2:staff2

Obviously for the score, I'd like:
part1:staff1
part1:staff2
part2:staff1
part2:staff2

I'm sure I just have something not correct.


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

\version "2.18.2"

\score {
<<
	\new Staff { \relative c' { c1 \break | << { c } \new Staff { g' } >> \break | c, } }
	\new Staff { \relative c' { b \break | << { b } \new Staff { f' } >> \break | b, } }
>> }
\layout
{
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Problem with Staff Grouping

[Dave Higgins]

Revisiting with a compilable example...

I'm transcribing a piece that has multiple parts and in those multiple
parts, I have multiple staves.

After compiling, the staff layout becomes:
part1:staff1
part2:staff1
part1:staff2
part2:staff2

Obviously for the score, I'd like:
part1:staff1
part1:staff2
part2:staff1
part2:staff2

I'm sure I just have something not correct.
\version "2.18.2"
\include "2.1.violin1.ly"
\include "2.1.violin2.ly"

\score {
<<
	\new Staff { \relative c' { c1 \break | << { c } \new Staff { g' } >> \break | c, } }
	\new Staff { \relative c' { b \break | << { b } \new Staff { f' } >> \break | b, } }
>> }
\layout
{
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Transcribing individual score pages from scans

[David Cuenca]

Hi Federico,

What I need is the ability to generate score in two view modes: each page
individually, or all pages together.

Imagine the use case. A user works page scan by page scan to make the
lilypond engraving look exactly like it was originally published (possible
already). Then they want to visualize all pages together (possible but only
as images, one after the other), and finally they want to download a single
.ly file or to render a typeset pdf, or generate a midi file from all the
pages together (not possible).

Yes, with the mediawiki extension we already can put all pages together
(see [1], if you hover your mouse over the small number on the left you
will see that is composed of two pages "100", "101"). When you click on
that number you go to the page view of either one, and  if you click edit
you will see the lilypond source of the corresponding page. But to
associate several independent pages as a bundle (for rendering, download,
or midi generation), that doesn't work.

>From our side we are considering each page as an individual independent
file. It was suggested by Urs to use one variable for each page, and then
render them either individually (when the user is in page view) or all
together (when the user request a download of the whole book/score).
However, lilypond is running in safe mode, thus variables are not
supported...

I hope I have better explained the problem now... any ideas about how to
proceed?

If you want to dig deeper you can take a look to our Extension:Proofread
Page [2] which manages transclusion. And if you'd like to go even a step
further and have a test environment, it is easy to set up a virtual machine
with Vagrant [3].

Cheers,
Micru

[1]
https://ca.wikisource.org/wiki/Segona_serie_de_can%C3%A7ons_populars_catalanes/Fum,_fum,_fum
[2] https://www.mediawiki.org/wiki/Extension:Proofread_Page
[3] https://www.mediawiki.org/wiki/MediaWiki-Vagrant



On Mon, May 12, 2014 at 4:53 PM, Federico Bruni  wrote:

> Hi David
>
> I haven't totally understood what you need, but it seems to me that what
> you are looking for should be achieved by the Mediawiki extension, not by
> LilyPond.
>
>
>
> 2014-05-09 13:21 GMT+02:00 David Cuenca :
>
> Hi Urs,
>>
>> unfortunately we cannot work with files, nor variables. The only thing we
>> can do is to join text inputs. What we are after is a way to append the
>> source texts that generate individual pages and generate a valid lilypond
>> input just by adding a header/footer.
>>
>> Is that possible?
>>
>> Thanks
>> David
>>
>>
>> On Fri, May 9, 2014 at 12:31 PM, Urs Liska  wrote:
>>
>>> Am 09.05.2014 12:26, schrieb Urs Liska:
>>>
>>>  Am 09.05.2014 12:16, schrieb David Cuenca:

> Hi,
>
> I'm a contributor from Wikisource, an online digital library part of
> the
> Wikimedia Foundation, where we transcribe works in the public domain.
> Since
> last year we have enabled a mediawiki extension to render scores [1],
> which
> now enables our users to transcribe pages with music like these [2] [3]
>
> Of course that is great when a work is only one page long, but for us
> it
> becomes problematic to stitch together all the different pages into a
> single one (what we call "transclusion").
> Some users are just considering each page independent, but that doesn't
> allow us to generate a whole lilypond file for download. For instance
> check
> this Catalan song [4], if you click on "edit" you will see that we are
> combining two pages [5] and [6], where the text resides.
>
> What we would like is to combine these pages to generate the lilypond
> file.
> I have been checking the input structure documentation [7] and I found
> "\book" and "\bookpart", but I didn't see anything like "\bookpage".
> Is there any command that would help us to achieve the page separation
> that
> we need?
>

 If I'm not mistaken that should be quite easy to achieve.
 You can organize LilyPond input in variables, and you can combine those
 variables to larger units. That is, you don't use variables only to
 store the different parts in a score, but you can also separate
 different sections of it.

 I'm not completely sure if that fits your use case, but you may have a
 start with something like:

 violinPageI = ŗelative c'' {
 % some music
 }

 violinPageII = ŗelative c'' {
 % some music
 }

 violinMusic = {
\violinPageI
\violinPageII
 }

 \score {
\new Staff \violinMusic
 }

 With this you can as well create alternative scores for individual pages
 if you like.

 Does that sound plausible?

 Best
 Urs


>>> Oh, I've already a few additional remarks that I forgot.
>>>
>>> Of course you will want to store the variables in individual files and
>>> include them.
>>>
>>> If you have spanners reaching from one

Re: Transcribing individual score pages from scans

[Federico Bruni]

Hi David

I haven't totally understood what you need, but it seems to me that what
you are looking for should be achieved by the Mediawiki extension, not by
LilyPond.



2014-05-09 13:21 GMT+02:00 David Cuenca :

> Hi Urs,
>
> unfortunately we cannot work with files, nor variables. The only thing we
> can do is to join text inputs. What we are after is a way to append the
> source texts that generate individual pages and generate a valid lilypond
> input just by adding a header/footer.
>
> Is that possible?
>
> Thanks
> David
>
>
> On Fri, May 9, 2014 at 12:31 PM, Urs Liska  wrote:
>
>> Am 09.05.2014 12:26, schrieb Urs Liska:
>>
>>  Am 09.05.2014 12:16, schrieb David Cuenca:
>>>
 Hi,

 I'm a contributor from Wikisource, an online digital library part of the
 Wikimedia Foundation, where we transcribe works in the public domain.
 Since
 last year we have enabled a mediawiki extension to render scores [1],
 which
 now enables our users to transcribe pages with music like these [2] [3]

 Of course that is great when a work is only one page long, but for us it
 becomes problematic to stitch together all the different pages into a
 single one (what we call "transclusion").
 Some users are just considering each page independent, but that doesn't
 allow us to generate a whole lilypond file for download. For instance
 check
 this Catalan song [4], if you click on "edit" you will see that we are
 combining two pages [5] and [6], where the text resides.

 What we would like is to combine these pages to generate the lilypond
 file.
 I have been checking the input structure documentation [7] and I found
 "\book" and "\bookpart", but I didn't see anything like "\bookpage".
 Is there any command that would help us to achieve the page separation
 that
 we need?

>>>
>>> If I'm not mistaken that should be quite easy to achieve.
>>> You can organize LilyPond input in variables, and you can combine those
>>> variables to larger units. That is, you don't use variables only to
>>> store the different parts in a score, but you can also separate
>>> different sections of it.
>>>
>>> I'm not completely sure if that fits your use case, but you may have a
>>> start with something like:
>>>
>>> violinPageI = ŗelative c'' {
>>> % some music
>>> }
>>>
>>> violinPageII = ŗelative c'' {
>>> % some music
>>> }
>>>
>>> violinMusic = {
>>>\violinPageI
>>>\violinPageII
>>> }
>>>
>>> \score {
>>>\new Staff \violinMusic
>>> }
>>>
>>> With this you can as well create alternative scores for individual pages
>>> if you like.
>>>
>>> Does that sound plausible?
>>>
>>> Best
>>> Urs
>>>
>>>
>> Oh, I've already a few additional remarks that I forgot.
>>
>> Of course you will want to store the variables in individual files and
>> include them.
>>
>> If you have spanners reaching from one variable to another (e.g. slurs)
>> you will have to enclose the variables in an explicitly created voice:
>>
>> violinMusic = \new Voice {
>> % ...
>> }
>>
>> Urs
>>
>>
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
>
>
> --
> Etiamsi omnes, ego non
>
> ___
> 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: multiple marks

[Carlo Vanoni]

Hi Jaques,

thanks for the hint!
By now, the hidden measure does the trick. The main drawback is the time 
change, that can led to some issue. In my previous example, since the repeat 
mark is on a bar before a break, adding the hidden measure there print a time 
change hint at the end of the line, as well as a useless new line at the end of 
the song (adding the hidden measure part after the mark in the repeatMark 
function).

To get rid of this, I created a function to print section titles and added the 
hidden measure there. In this way the time change will never be displayed.
Here is the new code:

%%%
\version "2.18.0"

chorus = \relative c'' { c d e c | c d e c | \break }
verse = \relative c'' { c c d d | c c d d | \break }

Time = \time 4/4

HiddenMeasureAndBarLine =
{ 
    \cadenzaOn
    \once \omit Score.TimeSignature
    \time 1/16
    s16 \bar ""
    \cadenzaOff
}

repeatMark =
#(define-music-function
 (parser location volte visible)
 (number? boolean?)
 (if visible
   #{
 \once \override Score.RehearsalMark #'break-visibility =
 #begin-of-line-invisible
 \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
 \once \override Score.RehearsalMark #'font-size = #0
 \mark \markup $(string-join (list "repeat" (number->string volte)
 "times"))
   #}
   ))
     
sectionTitleMark =
#(define-music-function
 (parser location sectionTitle)
 (string?)
 #{
        \HiddenMeasureAndBarLine
        \Time
        \mark \markup { $sectionTitle }
    #}
    )
         
song =
{
    \new Staff
    {    
        \Time
        
        \verse
        \repeat volta 4
        {
            \sectionTitleMark "Chorus"
            \chorus
            \repeatMark #4 ##t
        }
        \repeat volta 6
        {
            \sectionTitleMark "Solo"
            \chorus
            \repeatMark #6 ##t
        }
    }
}

\score {   
    \song
}
%%%

Still, the time change can be tricky if the song changes time, so the 
sectionTitleMark function can't use the \Time variable, but a new function 
parameter with the current time is needed.

It is enough for me at the moment.
By the way, if someone have further hints let us know.

Thanks!

Il Lunedì 12 Maggio 2014 15:14, Jacques Menu  ha scritto:
 
Hello Carlo,

Adding:

HiddenMeasureAndBarLine = { % from the snippets repository
% the hidden measure and bar line
% \cadenzaOn turns off automatic calculation of bar numbers
\cadenzaOn
%  \once \override Score.TimeSignature #'stencil = ##f
\once \omit Score.TimeSignature
\time 1/16
s16 \bar ""
\cadenzaOff
}

and replacing:

\mark "Solo"

with:

\HiddenMeasureAndBarLine
\time 4/4

\mark "Solo"

solves the issue.

But you’ll probably be better of placing the equivalent of this in repeatMark 
itself?


JM

Le 12 mai 2014 à 14:11:03, Carlo Vanoni  a écrit :

Hi everyone,
>
>I'm using this nice function to add a right-aligned text that states the 
>number of repeats of a repeat block:
>repeatMark =
>#(define-music-function
> (parser location volte visible)
> (number? boolean?)
> (if visible
>   #{
> \once \override Score.RehearsalMark #'break-visibility =
> #begin-of-line-invisible
> \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
> \once \override Score.RehearsalMark #'font-size = #0
> \mark \markup $(string-join (list "repeat" (number->string volte)
> "times"))
>   #}
>   #{ #}
>   ))
>
>It is called with this code at the end of a section
>\repeatMark #4 ##t    % writes "repeat 4 times"
>
>I usually wrote section name using a markup on single notes (a1^\markup{ \bold 
>Intro}). Now I'm separating the various song sections in different variables. 
>Since the same section can be used, e.g., as a chorus and during the solo, I 
>need to write the section name using a \mark before the section in the main 
>score. This unfortunately generates a "multiple mark" error
 when repeats are involved.
>Here is an example code:
>
>%%%
>\version "2.18.0"
>
>chorus = \relative c'' { c d e c | c d e c | \break}
>verse = \relative c'' { c c d d | c c d d | \break }
>
>repeatMark =
>#(define-music-function
> (parser location volte visible)
> (number? boolean?)
> (if visible
>   #{
> \once \override Score.RehearsalMark #'break-visibility =
> #begin-of-line-invisible
> \once \override Score.RehearsalMark #'self-alignment-X =
 #RIGHT
> \once \override Score.RehearsalMark #'font-size = #0
> \mark \markup $(string-join (list "repeat" (number->string volte)
> "times"))
>   #}
>   #{ #}
>   ))
>
>song =
>{
>    \new Staff
>    {    
>        \verse
>        \repeat volta 4
>        {
>            \mark "Chorus"
>            \chorus
>            \repeatMark #4 ##t
>        }
>        \repeat volta 6
>        {
>            \mark "Solo"
>            \chorus
>            \repeatMark #6 ##t
>        }
>    }
>}
>
>\score {   
>    \song
>}
>%%%
>
>Here, the

Tremolos not working in cued voice

[Gez]

When inserting a cue which contains a tremolo, the note heads and stems 
are showing up but not the beams.  Is it something I've done or missed 
out?  I've made a (reasonably) tiny example:


\version "2.16.2"

cueVoice =

\relative c'' {

R2.

\repeat tremolo 3 { b8 e }

}

mainVoice =

\relative c'' {

\time 3/4

\repeat tremolo 3 { b8 e }

\new CueVoice {\set instrumentCueName = "cue"}

\cueDuring "cue"#UP

{R2. }

\addQuote "cue"{ \cueVoice }

}

\score {

\new Staff \mainVoice

\layout { }

}
___


Gez



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

Re: multiple marks

[Jacques Menu]

Hello Carlo,

Adding:

HiddenMeasureAndBarLine = { % from the snippets repository
% the hidden measure and bar line
% \cadenzaOn turns off automatic calculation of bar numbers
\cadenzaOn
% \once \override Score.TimeSignature #'stencil = ##f
\once \omit Score.TimeSignature
\time 1/16
s16 \bar ""
\cadenzaOff
}

and replacing:

\mark "Solo"

with:

\HiddenMeasureAndBarLine
\time 4/4

\mark "Solo"

solves the issue.

But you’ll probably be better of placing the equivalent of this in repeatMark 
itself?

JM

Le 12 mai 2014 à 14:11:03, Carlo Vanoni  a écrit :

> Hi everyone,
> 
> I'm using this nice function to add a right-aligned text that states the 
> number of repeats of a repeat block:
> repeatMark =
> #(define-music-function
>  (parser location volte visible)
>  (number? boolean?)
>  (if visible
>#{
>  \once \override Score.RehearsalMark #'break-visibility =
>  #begin-of-line-invisible
>  \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
>  \once \override Score.RehearsalMark #'font-size = #0
>  \mark \markup $(string-join (list "repeat" (number->string volte)
>  "times"))
>#}
>#{ #}
>))
> 
> It is called with this code at the end of a section
> \repeatMark #4 ##t% writes "repeat 4 times"
> 
> I usually wrote section name using a markup on single notes (a1^\markup{ 
> \bold Intro}). Now I'm separating the various song sections in different 
> variables. Since the same section can be used, e.g., as a chorus and during 
> the solo, I need to write the section name using a \mark before the section 
> in the main score. This unfortunately generates a "multiple mark" error when 
> repeats are involved.
> Here is an example code:
> 
> %%%
> \version "2.18.0"
> 
> chorus = \relative c'' { c d e c | c d e c | \break}
> verse = \relative c'' { c c d d | c c d d | \break }
> 
> repeatMark =
> #(define-music-function
>  (parser location volte visible)
>  (number? boolean?)
>  (if visible
>#{
>  \once \override Score.RehearsalMark #'break-visibility =
>  #begin-of-line-invisible
>  \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
>  \once \override Score.RehearsalMark #'font-size = #0
>  \mark \markup $(string-join (list "repeat" (number->string volte)
>  "times"))
>#}
>#{ #}
>))
> 
> song =
> {
> \new Staff
> {
> \verse
> \repeat volta 4
> {
> \mark "Chorus"
> \chorus
> \repeatMark #4 ##t
> }
> \repeat volta 6
> {
> \mark "Solo"
> \chorus
> \repeatMark #6 ##t
> }
> }
> }
> 
> \score {   
> \song
> }
> %%%
> 
> Here, the "Solo" mark is dropped, due to the previous \repeatMark. What I 
> want is to have the "Solo" mark written like the "Chorus" one. And, of 
> course, the "reapeat N times" mark, too.
> Is there a better (more correct) approach to get this behavior? Maybe with a 
> little different \repeatMark function...
> 
> Thanks!
> 
> 
> 
> ___
> 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

multiple marks

[Carlo Vanoni]

Hi everyone,

I'm using this nice function to add a right-aligned text that states the number 
of repeats of a repeat block:
repeatMark =
#(define-music-function
 (parser location volte visible)
 (number? boolean?)
 (if visible
   #{
 \once \override Score.RehearsalMark #'break-visibility =
 #begin-of-line-invisible
 \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
 \once \override Score.RehearsalMark #'font-size = #0
 \mark \markup $(string-join (list "repeat" (number->string volte)
 "times"))
   #}
   #{ #}
   ))

It is called with this code at the end of a section
\repeatMark #4 ##t    % writes "repeat 4 times"

I usually wrote section name using a markup on single notes (a1^\markup{ \bold 
Intro}). Now I'm separating the various song sections in different variables. 
Since the same section can be used, e.g., as a chorus and during the solo, I 
need to write the section name using a \mark before the section in the main 
score. This unfortunately generates a "multiple mark" error when repeats are 
involved.
Here is an example code:

%%%
\version "2.18.0"

chorus = \relative c'' { c d e c | c d e c | \break}
verse = \relative c'' { c c d d | c c d d | \break }

repeatMark =
#(define-music-function
 (parser location volte visible)
 (number? boolean?)
 (if visible
   #{
 \once \override Score.RehearsalMark #'break-visibility =
 #begin-of-line-invisible
 \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
 \once \override Score.RehearsalMark #'font-size = #0
 \mark \markup $(string-join (list "repeat" (number->string volte)
 "times"))
   #}
   #{ #}
   ))

song =
{
    \new Staff
    {    
        \verse
        \repeat volta 4
        {
            \mark "Chorus"
            \chorus
            \repeatMark #4 ##t
        }
        \repeat volta 6
        {
            \mark "Solo"
            \chorus
            \repeatMark #6 ##t
        }
    }
}

\score {   
    \song
}
%%%

Here, the "Solo" mark is dropped, due to the previous \repeatMark. What I want 
is to have the "Solo" mark written like the "Chorus" one. And, of course, the 
"reapeat N times" mark, too.
Is there a better (more correct) approach to get this behavior? Maybe with a 
little different \repeatMark function...

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

Re: Transposing instruments in orchestra score

[Jan-Peter Voigt]

Hi again,

I didn't actually tell what the engraver is actually for:
The "autoTranspose"-engraver transposes music automatically, if there
are three context-properties set:
* instrumentTransposition is the pitch, which is set by \transposition
* music-concert-pitch tells whether the music in this context is
provided in concert-pitch (boolean)
* print-concert-pitch tells whether the music shall be printed in
concert-pitch (boolean)

Now, if you set music-concert-pitch to #t and print-concert-pitch to #f,
the music is transposed by instrumentTransposition. There are no extra
transpose{}-constructs needed and \instrumentSwitch may set
'instrumentTransposition.

Cheers, Jan-Peter

Am 12.05.2014 11:16, schrieb Jan-Peter Voigt:
> Hi there,
> 
> I read a few of the messages regarding the given subject. I don't have a
> once-and-for-all-solution, but I want bring in another scheme-engraver:
> 
> It uses context-properties 'instrumentTransposition, (newly defined)
> 'music-concert-pitch' and 'print-concert-pitch'. If the music in the
> staff is in concert-pitch, but it shall be displayed in
> instrument-pitch, it is transposed from concert-pitch to
> instrument-pitch and vice versa. The transposition is done on
> note-events and key-change-events. Propably the engraver needs to listen
> to a few more.
> 
> Two problems:
> 1. If the music is in instrument-pitch and shall be displayed in
> concert-pitch, the transposition is still active - so the midi is wrong
> 2. The engraver doesn't create a key-signature yet, if
> 'instrumentTransposition changes.
> 
> Now, what do you think?
> 
> Best, Jan-Peter

\version "2.18.2"

% taken from "scm/define-context-properties.scm"
#(define (translator-property-description symbol type? description)
   (if (not (and
 (symbol? symbol)
 (procedure? type?)
 (string? description)))
   (throw 'init-format-error))

   (if (not (equal? #f (object-property symbol 'translation-doc)))
   (ly:error (_ "symbol ~S redefined" symbol)))

   (set-object-property! symbol 'translation-type? type?)
   (set-object-property! symbol 'translation-doc description)
   (set! all-translation-properties (cons symbol all-translation-properties))
   symbol)
% add context properties descriptions
%   music-concert-pitch
%   print-concert-pitch
#(translator-property-description 'music-concert-pitch boolean? "music is in concert pitch")
#(translator-property-description 'print-concert-pitch boolean? "print it in concert pitch")

% engraver to automatically transpose music
autoTranspose =
#(lambda (context)
   (let ((base (ly:make-pitch 0 0 0)) ; pitch c'
  (lasttransp (ly:context-property context 'instrumentTransposition))) ; last instrument transposition
 (define (cond-transp engraver music)
   (let ((mcp (ly:context-property context 'music-concert-pitch)) ; music is in concert-pitch t/f
  (pcp (ly:context-property context 'print-concert-pitch)) ; print it in concert-pitch t/f
  (transp (ly:context-property context 'instrumentTransposition)) ; instrument transposition
  (keysig (ly:context-property context 'keySignature)) ; key-signature
  (tonic (ly:context-property context 'tonic))) ; key-signature tonic

 (define (do-transp m)
   (cond
; music in concert-pitch / display in instrument pitch
((and mcp (not pcp) (ly:pitch? transp))
 (ly:music-transpose m (ly:pitch-diff base transp)))
; music in instrument pitch / display in concert pitch
((and (not mcp) pcp (ly:pitch? transp))
 (ly:music-transpose m transp))
))
 
 ; TODO: if instrument transposition changed, produce key signature
 (if (not (equal? transp lasttransp))
 (let ((key-sig (make-music 'KeyChangeEvent 'pitch-alist keysig 'tonic tonic)))
   (ly:broadcast (ly:context-event-source context)
 (ly:make-stream-event 'key-change-event `((music-cause . ,key-sig)) ))
   ))
 (set! lasttransp transp)
 
 ; execute transposition
 (do-transp music)
 ))
 
 ; create engraver
 (make-engraver
  (listeners
   ; transpose note-event
   ((note-event engraver event)
(cond-transp engraver (ly:event-property event 'music-cause)))
   ; transpose key-signature
   ((key-change-event engraver event)
(cond-transp engraver (ly:event-property event 'music-cause)))
   )
  )
 ))


%%% demo music
bach = \relative c'' { bes a c b }

\addInstrumentDefinition #"eb-clarinet"
  #`((instrumentTransposition . ,(ly:make-pitch 0 2 -1/2))
 (shortInstrumentName . "Es-Kl")
 (clefGlyph . "clefs.G")
 (middleCPosition . -6)
 (clefPosition . -2)
 (instrumentCueName . "Es-Kl")
 (midiInstrument . "clarinet"))

\addInstrumentDefinition #"b-clarinet"
  #`((instrumentTranspo

"dal segno" several times

[Carlo Vanoni]

Hi everyone,

this is more a generic music notation question than a LilyPond related. By the 
way, I will ask it here so I can get a LilyPond related solution if needed, too.

I have a simple song, where the verse is 4 measures repeated twice, and the 
chorus again 4 measures repeated twice.
The song is like this:
intro
verse
chorus
verse
chorus
verse
chorus
outro

I can print all the section as stated above, but it will be easier to have 
something like this
intro
||: verse
chorus :|| x3 times
outro

If the verse and the chorus don't have repeats themself, one can use a simple 
repeat. Since they have repeats, I can't use "nested repeat", can I? My idea is 
to use a "D.S. 3 times" (probably with a "take all repeats"), or similar, but 
I'm not sure it is the correct way.
Of course, in this example, I can remove the single section repeat (so verse 
becomes 8 measures, same for chorus) and use a simple repeat to get the result. 
By the way, I'm looking for a generic scenario solution.

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

Re: relative pitch with song sections

[Carlo Vanoni]

Uh, "bass_8"... that's a news.
I still use the relative to prevent some ' and , from the code. Since I also 
have (in the real code) also fingering and sting numbers, it will become a real 
mess otherwise.
Here is the now working code:

%
\version "2.18.0"

verse = 
\relative c,,
{
    a'4 b c a | a b c a | \break
}

chorus =
\relative c,,
{
    a'4 b c d | d e f g | \break
}

song = 
{
    \repeat volta 2
    {
        \verse
    }
    \chorus
    \verse
    \chorus
    \bar "|."
}

bass =  {
    <<
    \new Staff \with {
        \clef "bass_8"
        \omit Voice.StringNumber
    }
    { 
        \song
    }
    
    \new TabStaff \with {
        \clef moderntab
        stringTunings = #bass-tuning
    }
    {     
        \song 
    }
    \set Staff.instrumentName = #"Bass" 
    >>
}

\score {    
  \bass
}
%

Since to avoid all ' and , I have to still declare "\relative c" in the two 
sections to use traspose, I preferred to use the "\relative c,," and remove the 
score transpose.

Thanks guys!

Il Lunedì 12 Maggio 2014 11:56, Pierre Perol-Schneider 
 ha scritto:
 
2014-05-12 11:42 GMT+02:00 Carlo Vanoni :

 

As said, this set all verse/note to the correct pitch, but the tabs pitch will 
be wrong (the \relative definition in the TabScore section will be ignored).
>
 

Hi Carlo,

If you want to have the right pitch you have to put the right clef in the staff 
(\clef "bass_8").

Now if that causes you problem, why are you coding in a relative mode ?

You can do something like :

%
\version "2.18.0"


verse = {
   a4 b c' a | a b c' a | \break
}
chorus = {
   a4 b c' d' | d' e' f' g' | \break
}
song = {
    \repeat volta 2 { \verse }
    \chorus
    \verse
    \chorus
    \bar "|."
}

bass = \transpose c c,, {
<<
 \new Staff 
    \with {
\clef "bass_8"
        \omit Voice.StringNumber
   }
   {
        \song
    }
  \new TabStaff 
    \with {
  \clef moderntab
  stringTunings = #bass-tuning
  }
  { 
  \song
  }
\set Staff.instrumentName = #"Bass"
    >>
  }
  \score { 
    \bass
}
%___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: relative pitch with song sections

[Pierre Perol-Schneider]

2014-05-12 11:42 GMT+02:00 Carlo Vanoni :


> As said, this set all verse/note to the correct pitch, but the tabs pitch
> will be wrong (the \relative definition in the TabScore section will be
> ignored).
>

Hi Carlo,
If you want to have the right pitch you have to put the right clef in the
staff (\clef "bass_8").
Now if that causes you problem, why are you coding in a relative mode ?
You can do something like :

%
\version "2.18.0"

verse = {

  a4 b c' a | a b c' a | \break

}

chorus = {

  a4 b c' d' | d' e' f' g' | \break

}

song = {

   \repeat volta 2 { \verse }

   \chorus

   \verse

   \chorus

   \bar "|."

}


bass = \transpose c c,, {

<<

  \new Staff

   \with {

 \clef "bass_8"

  \omit Voice.StringNumber

   }

   {

  \song

}

  \new TabStaff

\with {

   \clef moderntab

   stringTunings = #bass-tuning

 }

 {

   \song

 }

 \set Staff.instrumentName = #"Bass"

   >>

  }

  \score {

\bass

}

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

Re: relative pitch with song sections

[Francisco Vila]

El 12/05/2014 11:42, "Carlo Vanoni"  escribió:
>
> Hi Francisco,
>
> thanks for the reply.
> But... I didn't understand it very well...
> Did you mean to do something like this?
> 
> verse =
> {

Yes.  This brace is not needed.

> \relative c,
> {
> a'4 b c a | a b c a | \break
> }
> }

Neither this is.

>
> chorus =
> {
> \relative c,
> {
>
> a'4 b c d | d e f g | \break
> }
> }
> 
>
> As said, this set all verse/note to the correct pitch, but the tabs pitch
will be wrong (the \relative definition in the TabScore section will be
ignored).

Use relative to define the correct pitches in music variables and nowhere
else. Do not nest relative  statements.

>
> Il Lunedì 12 Maggio 2014 11:16, Francisco Vila  ha
scritto:
> Using relative per variable at the moment of their definition is robust
pitchwise.
> Sorry for top posting
> El 12/05/2014 10:48, "Carlo Vanoni"  escribió:
>>
>> Hi everyone,
>>
>> I'm transcribing a song that is, as usual, versex2-chorus-verse-chorus.
Instead of copying all the notes of the verse/chorus section, I've created
the verse-chorus sections so than I can just add \verse \chorus in the main
score to print it.
>> I need to display both the score and the tabs. I noticed that I have to
set different relative pitches for the two notations, otherwise there is an
octave difference in the two (maybe I'm messing up something... Check the
example), so I need to state the relative pitch in the \new Staff - \new
TabStaff sections.
>> The problem is that, since I state the relative pitch there, I can't set
the pitch of the song sections, so I don't know how to let the first note
of the section to start always at a given pitch.
>>
>> Enough talking.
>> Here is a simple example:
>> 
>> \version "2.18.0"
>>
>> verse =
>> {
>> a'4 b c a | a b c a | \break
>> }
>>
>> chorus =
>> {
>> a'4 b c d | d e f g | \break
>> }
>>
>> song =
>> {
>> \repeat volta 2
>> {
>> \verse
>> }
>> \chorus
>> \verse
>> \chorus
>> \bar "|."
>> }
>>
>> bass = {
>> <<
>> \new Staff \with {
>> \clef bass
>> \omit Voice.StringNumber
>> }
>> {
>> \relative c,
>> \song
>> }
>>
>> \new TabStaff \with {
>> \clef moderntab
>> stringTunings = #bass-tuning
>> }
>> {
>> \relative c,,   % tabs relative to a lower octave!
>> \song
>> }
>> \set Staff.instrumentName = #"Bass"
>> >>
>> }
>>
>> \score {
>>   \bass
>> }
>> 
>>
>> What I want is that each section starts from the same note (a' relative
to c,). What happens is that each section will be relative to the previous
section last note, so everything start to jump up an octave.
>> This can probably be corrected setting the relative in the section
itself (verse/chorus). But then the Score and TabScore will display
different octaves.
>>
>> What am I missing?
>>
>> Thanks!
>>
>>
>>
>>
>>
>> ___
>> 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: relative pitch with song sections

[Carlo Vanoni]

Hi Francisco,

thanks for the reply.
But... I didn't understand it very well...
Did you mean to do something like this?
verse = 
{
    \relative c,
    {
        a'4 b c a | a b c a | \break
    }
}

chorus =
{
    \relative c,
    {
        a'4 b c d | d e f g | \break
    }
}



As said, this set all verse/note to the correct pitch, but the tabs pitch will 
be wrong (the \relative definition in the TabScore section will be ignored).


Il Lunedì 12 Maggio 2014 11:16, Francisco Vila  ha 
scritto:
 
Using relative per variable at the moment of their definition is robust 
pitchwise.
Sorry for top posting
El 12/05/2014 10:48, "Carlo Vanoni"  escribió:

Hi everyone,
>
>I'm transcribing a song that is, as usual, versex2-chorus-verse-chorus. 
>Instead of copying all the notes of the verse/chorus section, I've created the 
>verse-chorus sections so than I can just add \verse \chorus in the main score 
>to print it.
>I need to display both the score and the tabs. I noticed that I have to set 
>different relative pitches for the two notations, otherwise there is an octave 
>difference in the two (maybe I'm messing up something... Check the example), 
>so I need to state the relative pitch in the \new Staff - \new TabStaff 
>sections.
>The problem is that, since I state the relative pitch there, I can't set the 
>pitch of the song sections, so I don't know how to let the first note of
 the section to start always at a given pitch.
>
>Enough talking.
>Here is a simple example:
>
>\version "2.18.0"
>
>verse = 
>{
>    a'4 b c a | a b c a | \break
>}
>
>chorus =
>{
>    a'4 b c d | d e f g | \break
>}
>
>song = 
>{
>    \repeat volta 2
>    {
>        \verse
>    }
>    \chorus
>   
 \verse
>    \chorus
>    \bar "|."
>}
>
>bass = {
>    <<
>    \new Staff \with {
>        \clef bass
>        \omit Voice.StringNumber
>    }
>    { 
>        \relative c, 
>        \song
>    }
>    
>    \new TabStaff \with {
>        \clef moderntab
>        stringTunings =
 #bass-tuning
>    }
>    {     
>        \relative c,,   % tabs relative to a lower octave! 
>        \song 
>    }
>    \set Staff.instrumentName = #"Bass" 
>    >>
>}
>
>\score {    
>  \bass
>}
>
>
>What I want is that each section starts from the same note (a' relative to 
>c,). What happens is that each section will be relative to the previous 
>section last note, so everything start to jump up an octave.
>This
 can probably be corrected setting the relative in the section itself 
(verse/chorus). But then the Score and TabScore will display different octaves.
>
>What am I missing?
>
>Thanks!
>
>
>
>
>
>
>___
>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: Transposing instruments in orchestra score

[Jan-Peter Voigt]

Hi there,

... now, who's late ;)

I read a few of the messages regarding the given subject. I don't have a
once-and-for-all-solution, but I want bring in another scheme-engraver:

It uses context-properties 'instrumentTransposition, (newly defined)
'music-concert-pitch' and 'print-concert-pitch'. If the music in the
staff is in concert-pitch, but it shall be displayed in
instrument-pitch, it is transposed from concert-pitch to
instrument-pitch and vice versa. The transposition is done on
note-events and key-change-events. Propably the engraver needs to listen
to a few more.

Two problems:
1. If the music is in instrument-pitch and shall be displayed in
concert-pitch, the transposition is still active - so the midi is wrong
2. The engraver doesn't create a key-signature yet, if
'instrumentTransposition changes.

Now, what do you think?

Best, Jan-Peter

Am 09.05.2014 01:18, schrieb Kieren MacMillan:
> Hello all,
> 
> Sorry I’m late to the party…
> 
> A critical feature of a proper and useable multi-instrumentalist framework 
> would be the ability to put in global variables which include the key 
> signature(s) for the work, and the part would present the correct 
> transposition of that key signature (as well as the pitches, of course) upon 
> the switchInstrument call.
> 
> David and I played around with some options last year, and the thread ended 
> on a less-than-enthusastic note. Perhaps it’s time to revive this and clean 
> it up once and for all? I can tell you for certain that a killer 
> multi-instrumentalist framework would go a very long way to enticing some of 
> my composer and MD buddies over to The Pond (or, as they refer to it, “The 
> Dark Side”).

\version "2.18.2"

% taken from "scm/define-context-properties.scm"
#(define (translator-property-description symbol type? description)
   (if (not (and
 (symbol? symbol)
 (procedure? type?)
 (string? description)))
   (throw 'init-format-error))

   (if (not (equal? #f (object-property symbol 'translation-doc)))
   (ly:error (_ "symbol ~S redefined" symbol)))

   (set-object-property! symbol 'translation-type? type?)
   (set-object-property! symbol 'translation-doc description)
   (set! all-translation-properties (cons symbol all-translation-properties))
   symbol)
% add context properties descriptions
%   music-concert-pitch
%   print-concert-pitch
#(translator-property-description 'music-concert-pitch boolean? "music is in concert pitch")
#(translator-property-description 'print-concert-pitch boolean? "print it in concert pitch")

% engraver to automatically transpose music
autoTranspose =
#(lambda (context)
   (let ((base (ly:make-pitch 0 0 0)) ; pitch c'
  (lasttransp (ly:context-property context 'instrumentTransposition))) ; last instrument transposition
 (define (cond-transp engraver music)
   (let ((mcp (ly:context-property context 'music-concert-pitch)) ; music is in concert-pitch t/f
  (pcp (ly:context-property context 'print-concert-pitch)) ; print it in concert-pitch t/f
  (transp (ly:context-property context 'instrumentTransposition)) ; instrument transposition
  (keysig (ly:context-property context 'keySignature)) ; key-signature
  (tonic (ly:context-property context 'tonic))) ; key-signature tonic

 (define (do-transp m)
   (cond
; music in concert-pitch / display in instrument pitch
((and mcp (not pcp) (ly:pitch? transp))
 (ly:music-transpose m (ly:pitch-diff base transp)))
; music in instrument pitch / display in concert pitch
((and (not mcp) pcp (ly:pitch? transp))
 (ly:music-transpose m transp))
))
 
 ; TODO: if instrument transposition changed, produce key signature
 (if (not (equal? transp lasttransp))
 (let ((key-sig (make-music 'KeyChangeEvent 'pitch-alist keysig 'tonic tonic)))
   (ly:broadcast (ly:context-event-source context)
 (ly:make-stream-event 'key-change-event `((music-cause . ,key-sig)) ))
   ))
 (set! lasttransp transp)
 
 ; execute transposition
 (do-transp music)
 ))
 
 ; create engraver
 (make-engraver
  (listeners
   ; transpose note-event
   ((note-event engraver event)
(cond-transp engraver (ly:event-property event 'music-cause)))
   ; transpose key-signature
   ((key-change-event engraver event)
(cond-transp engraver (ly:event-property event 'music-cause)))
   )
  )
 ))


%%% demo music
bach = \relative c'' { bes a c b }

\addInstrumentDefinition #"eb-clarinet"
  #`((instrumentTransposition . ,(ly:make-pitch 0 2 -1/2))
 (shortInstrumentName . "Es-Kl")
 (clefGlyph . "clefs.G")
 (middleCPosition . -6)
 (clefPosition . -2)
 (instrumentCueName . "Es-Kl")
 (midiInstrument .

Re: relative pitch with song sections

[Francisco Vila]

Using relative per variable at the moment of their definition is robust
pitchwise.
Sorry for top posting
El 12/05/2014 10:48, "Carlo Vanoni"  escribió:

> Hi everyone,
>
> I'm transcribing a song that is, as usual, versex2-chorus-verse-chorus.
> Instead of copying all the notes of the verse/chorus section, I've created
> the verse-chorus sections so than I can just add \verse \chorus in the main
> score to print it.
> I need to display both the score and the tabs. I noticed that I have to
> set different relative pitches for the two notations, otherwise there is an
> octave difference in the two (maybe I'm messing up something... Check the
> example), so I need to state the relative pitch in the \new Staff - \new
> TabStaff sections.
> The problem is that, since I state the relative pitch there, I can't set
> the pitch of the song sections, so I don't know how to let the first note
> of the section to start always at a given pitch.
>
> Enough talking.
> Here is a simple example:
> 
> \version "2.18.0"
>
> verse =
> {
> a'4 b c a | a b c a | \break
> }
>
> chorus =
> {
> a'4 b c d | d e f g | \break
> }
>
> song =
> {
> \repeat volta 2
> {
> \verse
> }
> \chorus
> \verse
> \chorus
> \bar "|."
> }
>
> bass = {
> <<
> \new Staff \with {
> \clef bass
> \omit Voice.StringNumber
> }
> {
> \relative c,
> \song
> }
>
> \new TabStaff \with {
> \clef moderntab
> stringTunings = #bass-tuning
> }
> {
> \relative c,,   % tabs relative to a lower octave!
> \song
> }
> \set Staff.instrumentName = #"Bass"
> >>
> }
>
> \score {
>   \bass
> }
> 
>
> What I want is that each section starts from the same note (a' relative to
> c,). What happens is that each section will be relative to the previous
> section last note, so everything start to jump up an octave.
> This can probably be corrected setting the relative in the section itself
> (verse/chorus). But then the Score and TabScore will display different
> octaves.
>
> What am I missing?
>
> Thanks!
>
>
>
>
>
> ___
> 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: An old claveciniste's notation

[Richard Shann]

On Wed, 2014-05-07 at 20:23 +1000, Andrew Bernard wrote:
> This brings up the point that there do indeed seem to be a set of
> people trying to use lilypond for baroque music engraving. Lilypond
> seems heavily oriented around nineteenth century practice (leaving
> aside it's wonderful support for ancient notations) and the very usual
> and common set of baroque keyboard ornaments (meaning, in particular,
> the French ones) have to be done with complex special techniques that
> are not easily understood or manufactured by those who do not know
> Scheme.
> 
> Why can't lilypond be extended to have in the base code a full set of
> French baroque ornament signs and symbols? How would one initiate such
> a request?

There is a bug tracker for that, but from the lack of response I would
guess there isn't enough demand. However, I have been digging a bit into
this, as there is indeed at least one other ornament in the score I am
working from that is not available. The pincé appearing next to the note
is a rather special case, as is the coulé that I originally asked about,
but for many others here is a route which seems to work:

I created an eps file from the fermata.svg which is an image of the
fermata extracted from the emmentaler font, purely as an example to work
with, and placed it
in /home/rshann/git-denemo/denemo/pixmaps/fermata.eps

then I wrote four notes with the code

 a'4 a' 
 ^\markup {\combine 
\epsfile #X #2 #"/home/rshann/git-denemo/denemo/pixmaps/fermata.eps" 
\with-dimensions #'(0 . 6) #'(0 . 10)
\postscript #"
  newpath
  closepath
  "
} 
a'4 a' 

and the result is that the second a' note has a fermata over it.

Now, I cannibalized that code from 

http://www.lilypond.org/doc/v2.18/Documentation/notation/formatting-text#index-epsfile

but the documentation there is not sufficient for me to know what
exactly all the bits are doing; if anyone can prune that code further,
or say what can be usefully done with the parameters in it, I would be
grateful.

Anyway, this provides a route for including other special ornaments -
I'll include the one (the "suspension") I need right now in the next
Denemo release so that it can be applied via a simple command as with
any other ornament.

If anyone has other .svg's that they want including, please let me know.

Richard



> 
> It's interesting that it was only two or three weeks ago that I myself
> asked about pincé, and here it is again. So there is some growing
> demand.
> 
> I am of course aware that there is generally more than one way to
> notate the French ornaments, but that can be dealt with I imagine.
> 
> 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

Fwd: Re: Dotted half note showing as half note followed by a colon

[Urs Liska]

 Original-Nachricht 
Betreff: [SPAM] Re: Dotted half note showing as half note followed by a 
colon

Datum: Mon, 12 May 2014 10:09:44 +0100
Von: Trevor Daniels 
An: Urs Liska 


- Original Message -
From: "Urs Liska" 
To: 
Sent: Monday, May 12, 2014 6:12 AM
Subject: Re: Dotted half note showing as half note followed by a colon



Am 12.05.2014 05:45, schrieb Knute Snortum:

Well, I get warning with the example you posted.  You basically have two
voices trying to put rests and notes in the same place.  This is what I
would do:


Yes, that's the correct approach. But it still doesn't explain why there
are two different dots. (Although I don't know if you can call it a bug
when faulty input produces faulty output ;-) ).


Since the warning message is "ignoring too many clashing note columns",
it would be nice if the 'too many clashing dots' were also ignored.  This
would be in keeping with Lily's general aim of making as much sense of
the input as possible.  But note other notational elements are also doubled
in the printed output under these circumstances - dynamics and slurs, for
example.

Trevor



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

relative pitch with song sections

[Carlo Vanoni]

Hi everyone,

I'm transcribing a song that is, as usual, versex2-chorus-verse-chorus. Instead 
of copying all the notes of the verse/chorus section, I've created the 
verse-chorus sections so than I can just add \verse \chorus in the main score 
to print it.
I need to display both the score and the tabs. I noticed that I have to set 
different relative pitches for the two notations, otherwise there is an octave 
difference in the two (maybe I'm messing up something... Check the example), so 
I need to state the relative pitch in the \new Staff - \new TabStaff sections.
The problem is that, since I state the relative pitch there, I can't set the 
pitch of the song sections, so I don't know how to let the first note of the 
section to start always at a given pitch.

Enough talking.
Here is a simple example:

\version "2.18.0"

verse = 
{
    a'4 b c a | a b c a | \break
}

chorus =
{
    a'4 b c d | d e f g | \break
}

song = 
{
    \repeat volta 2
    {
        \verse
    }
    \chorus
    \verse
    \chorus
    \bar "|."
}

bass = {
    <<
    \new Staff \with {
        \clef bass
        \omit Voice.StringNumber
    }
    { 
        \relative c, 
        \song
    }
    
    \new TabStaff \with {
        \clef moderntab
        stringTunings = #bass-tuning
    }
    {     
        \relative c,,   % tabs relative to a lower octave! 
        \song 
    }
    \set Staff.instrumentName = #"Bass" 
    >>
}

\score {    
  \bass
}


What I want is that each section starts from the same note (a' relative to c,). 
What happens is that each section will be relative to the previous section last 
note, so everything start to jump up an octave.
This can probably be corrected setting the relative in the section itself 
(verse/chorus). But then the Score and TabScore will display different octaves.

What am I missing?

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