Re: scholarly/annotate

[Urs Liska]

Oops,  sent instead of saved ...
I'll have to return to this later.

Am 2. November 2015 08:50:39 MEZ, schrieb Urs Liska :
>Hi Craig,
>
>actually I see there's nothing *I* have to look into right now. Rather
>you should tell me what you would like to achieve. Tell me what - from
>your experience with an actual project - would be good to have in
>ScholarLY. While not exactly rich in time I'm more than ready to bring
>this package further.
>
>So far custom properties are just translated into key-value properties
>to the LaTeX command. It's then the task of LaTeX to do something
>useful
>with them. As I said the current set-up simply guarantees that
>
>Am 29.10.2015 um 22:58 schrieb Craig Dabelstein:
>> Thanks Urs. I'm working on a 900-page score from 1842 and
>> scholarly/annotate is proving invaluable. Thanks for all your hard
>> work on this.
>>
>> Craig
>>
>>
>> On Thu, 29 Oct 2015 at 18:05 Urs Liska > > wrote:
>>
>> I'll have to try this on a PC, but for now two remarks:
>>
>> You seem to have misplaced the space before \transposition so
>this
>> can't be expected to produce anything meaningful.
>>
>> The custom properties that end up in the optional argument
>(square
>> brackets) don't have any implementation so far. This is jzst a
>> state where you can enter arbitrary stuff in the annotation and
>> have *valid* LaTeX produced.
>>
>> Please remind me if I fail to come back to this.
>>
>> Urs
>>
>> Am 29. Oktober 2015 08:45:06 MEZ, schrieb Craig Dabelstein
>> mailto:craig.dabelst...@gmail.com>>:
>>
>> Dear Urs (or any other Annotate experts),
>>
>> I have created this entry in my input file, taking the idea
>> from the example given on git:
>>
>> \criticalRemark \with {
>> message = "Originally \\textit{Flauti in F} which is an
>> E\flat\ transposition."
>> original-instrument-key = \key ef \major
>> original-score-key = \key c \major
>>   }
>>
>> Can anyone tell me how this should translate into the latex
>> file? Is it expected to produce a real key signature in the
>> latex file?
>>
>> The console output produces:
>>
>>   \criticalRemark \with {
>>
>> Measure 1184, beat 1
>>
>> Context: Flute 1
>>
>> Affected Item: NoteHead
>>
>> Message: Originally \textit{Flauti in F} which is an E\flat\
>> transposition.
>>
>> original-instrument-key: Key: #
>>
>> original-score-key: Key: #
>>
>>
>> The .inp file produces:
>>
>>
>> \criticalRemark
>>
>>[original-score-key={Key: #},
>>
>> original-instrument-key={Key: #}]
>>
>> {1184}{1}
>>
>> {Flute 1}
>>
>> {NoteHead}
>>
>> {Originally \textit{Flauti in F} which is an E\flat\
>> transposition.}
>>
>>
>> How would you have this display in your latex Critical
>report?
>>
>> I hope this makes sense.
>>
>> All the best,
>>
>> Craig
>>
>>
>>
>> *Craig Dabelstein*
>> e:craig.dabelst...@gmail.com
>
>> 
>
>>
>>
>
>>
>> lilypond-user mailing list
>> lilypond-user@gnu.org 
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>> -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9
>> Mail gesendet.
>>
>
>
>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: scholarly/annotate

[Urs Liska]

Hi Craig,

actually I see there's nothing *I* have to look into right now. Rather
you should tell me what you would like to achieve. Tell me what - from
your experience with an actual project - would be good to have in
ScholarLY. While not exactly rich in time I'm more than ready to bring
this package further.

So far custom properties are just translated into key-value properties
to the LaTeX command. It's then the task of LaTeX to do something useful
with them. As I said the current set-up simply guarantees that

Am 29.10.2015 um 22:58 schrieb Craig Dabelstein:
> Thanks Urs. I'm working on a 900-page score from 1842 and
> scholarly/annotate is proving invaluable. Thanks for all your hard
> work on this.
>
> Craig
>
>
> On Thu, 29 Oct 2015 at 18:05 Urs Liska  > wrote:
>
> I'll have to try this on a PC, but for now two remarks:
>
> You seem to have misplaced the space before \transposition so this
> can't be expected to produce anything meaningful.
>
> The custom properties that end up in the optional argument (square
> brackets) don't have any implementation so far. This is jzst a
> state where you can enter arbitrary stuff in the annotation and
> have *valid* LaTeX produced.
>
> Please remind me if I fail to come back to this.
>
> Urs
>
> Am 29. Oktober 2015 08:45:06 MEZ, schrieb Craig Dabelstein
> mailto:craig.dabelst...@gmail.com>>:
>
> Dear Urs (or any other Annotate experts),
>
> I have created this entry in my input file, taking the idea
> from the example given on git:
>
> \criticalRemark \with {
> message = "Originally \\textit{Flauti in F} which is an
> E\flat\ transposition."
> original-instrument-key = \key ef \major
> original-score-key = \key c \major
>   }
>
> Can anyone tell me how this should translate into the latex
> file? Is it expected to produce a real key signature in the
> latex file?
>
> The console output produces:
>
>   \criticalRemark \with {
>
> Measure 1184, beat 1
>
> Context: Flute 1
>
> Affected Item: NoteHead
>
> Message: Originally \textit{Flauti in F} which is an E\flat\
> transposition.
>
> original-instrument-key: Key: #
>
> original-score-key: Key: #
>
>
> The .inp file produces:
>
>
> \criticalRemark
>
>[original-score-key={Key: #},
>
> original-instrument-key={Key: #}]
>
> {1184}{1}
>
> {Flute 1}
>
> {NoteHead}
>
> {Originally \textit{Flauti in F} which is an E\flat\
> transposition.}
>
>
> How would you have this display in your latex Critical report?
>
> I hope this makes sense.
>
> All the best,
>
> Craig
>
>
>
> *Craig Dabelstein*
> e:craig.dabelst...@gmail.com 
>  
> 
>
> 
> 
>
> lilypond-user mailing list
> lilypond-user@gnu.org 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9
> Mail gesendet.
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Pair of eyes needed

[Johan Vromans]

On Sun, 1 Nov 2015 21:27:52 +
Alberto Simões  wrote:

> If you are willing to help, you do not need to mess with the lilypond 
> code. You can just annotate somehow the PDF, and I'll fix the code.

Small nitpick: *you* did the transcribing, LilyPond did the typesetting.
"Transcribed with LilyPond" would imply (to me, at least) that you fed the
document to LP and LP did the rest.

Suggested replacement: "Transcribed by Alberto Simões for GNU LilyPond".

-- Johan

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

Page Turns During Cues

[Nick Baskin]

Hey all,

I have a piece that, due to its rhythmic complexity, needs a lot of cues in
the parts. Unfortunately, as a result, several of the parts have three
pages of consecutive music where LilyPond can't put a page turn. Is there a
setting somewhere I can use to tell the page turn engraver that it's OK to
put a page turn in the middle of a cue? I would really like to not have to
enter page turns manually.

Many thanks,
Nick

-- 
And she forgot the stars, the moon, and sun,
And she forgot the blue above the trees,
And she forgot the dells where waters run,
And she forgot the chilly autumn breeze...

— Keats, "Isabella, or the Pot of Basil"
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: LilyPond initiative in french conservatoires in Paris

[Mathieu Demange]

Hi Noeck,

What was the range of ages in the auditorium and their (musical) 
background?


Students were from 7 to 18 years old. Average age was around 9. All 
these students globally started learning music at age 6 or 7. In most 
french conservatories, students have both an instrument course and a 
music education ("Formation Musicale") course. So these students you saw 
(hopefully) have a common background based on "sensoriality", full 
participation of the whole body, singing, memorizing, etc. Huge 
(possibly off) topic though, and very related to teachers themselves.



I was wondering: Why don't you introduce \language "français" from the
beginning?


Very interesting. When we first tried to imagine how we could introduce 
LilyPond and its representation of music to young people, we thought 
we'll need to stick to what is the most natural expression of music for 
them, which turned out not to be about note names but sound itself. And 
we observed that being in presence of another form of representation of 
a musical component (pitch, here, with alphabet letters) is really 
positive and stimulating their musical senses. After that, we decided to 
stick to the default note names and that this also was a little step 
toward international music things ;)



Best wishes this project!


Thank you Noeck!

Yours,

Mathieu

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

Re: Remove empty staves but one.

[David Kastrup]

Peter Reid  writes:

> That works for me and is simpler than the solution that I posted previously.  
>
> I also need to cancel the effect of the command later on. I assumed I
> just had to add :
> \revert Staff.VerticalAxisGroup.remove-empty
>
> But this doesn't seem to have any effect.

An override you want to cancel later has to written as

\temporary \override ...

That way, it will only _mask_ the original setting rather than replace
it, and the following \revert will be able to restore the original
setting.

-- 
David Kastrup

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

Re: Q regarding best practice with \relative

[Simon Albrecht]

On 01.11.2015 12:59, David Kastrup wrote:

So there's not really a "best practice" but rather one that requires
least choice-making for those not interested in making more choices than
necessary.


It’s also the one with the least superficial elements, in other words: 
least to type.


Yours, Simon

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

Pair of eyes needed

[Alberto Simões]

Hello

Just finished a transcription of a simple piece (four pages, for piano).
I took all my care to correctly transcribe it, but I would love if 
someone could help proofreading it.


All the details are in [1] (source, pdf, lilypond).

If you are willing to help, you do not need to mess with the lilypond 
code. You can just annotate somehow the PDF, and I'll fix the code.


After this validation step is done, I'll request help for some lilypond 
details (but probably better to ask one thing at a time).


Thank you,
Alberto

[1] https://github.com/ambs/music/tree/master/Gounod/ValseDesSylphes

PS: of course you will be credited for your work.

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

Re: Remove empty staves but one.

[Peter Reid]

That works for me and is simpler than the solution that I posted previously.  

I also need to cancel the effect of the command later on. I assumed I just had 
to add :
\revert Staff.VerticalAxisGroup.remove-empty

But this doesn't seem to have any effect.

Thanks again,
Peter


> Le 2015 Nov 1 à 21:37, David Kastrup  a écrit :
> 
> Peter Reid  writes:
> 
>> Hi David, 
>> 
>> Thanks for getting back to me.
>> 
>> I'm not sure where I need to put that.  Sorry... I've tried putting it
>> with my notes ; in the \score part...  no luck.
>> 
>> I get this sort of error message:
>> 
>> Avertissement : vérification du type de propriété pour « remove-empty
>> » (translation-type?) non trouvée Probable faute de frappe
>> 
>> Can't seem to get this error message into English, but basically it
>> means there is probably a "typo".
>> 
>> I'm still a beginner so I'm probably missing something obvious, thanks
>> for your help.
>> 
>> Peter
>> 
>>> Le 2015 Nov 1 à 19:08, David Kastrup  a écrit :
>>> 
>>> \set Staff.remove-empty = ##f maybe
> 
> My fault, I misremembered.  It's likely
> 
> \override Staff.VerticalAxisGroup.remove-empty = ##f
> 
> instead.
> 
> -- 
> David Kastrup


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

Re: Remove empty staves but one.

[David Kastrup]

Peter Reid  writes:

> Hi David, 
>
> Thanks for getting back to me.
>
> I'm not sure where I need to put that.  Sorry... I've tried putting it
> with my notes ; in the \score part...  no luck.
>
> I get this sort of error message:
>
> Avertissement : vérification du type de propriété pour « remove-empty
> » (translation-type?) non trouvée Probable faute de frappe
>
> Can't seem to get this error message into English, but basically it
> means there is probably a "typo".
>
> I'm still a beginner so I'm probably missing something obvious, thanks
> for your help.
>
> Peter
>
>> Le 2015 Nov 1 à 19:08, David Kastrup  a écrit :
>> 
>> \set Staff.remove-empty = ##f maybe

My fault, I misremembered.  It's likely

\override Staff.VerticalAxisGroup.remove-empty = ##f

instead.

-- 
David Kastrup

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

Re: 2.19.30 returns error code -1073741819

[Hans Aikema]

My guess would be that you have a 64-bit binary version of a utility package 
that is also used (and installed) as a 32bit library by lilypond apearing 
before Lilypond on the system path.

I've seen other products running into access violations like you mentioned due 
to a 64-bit binary trying to use a 32-bit library. I can imagine the same holds 
the other way around (32bit binaries like Lilypond trying to use a 64bit 
library). If that's indeed the issue you may be able to resolve it by putting 
Lilypond binaries at the start of your system path.

Hans Aikema

> Op 1 nov. 2015 om 19:59 heeft guoguocuozuoduo  het 
> volgende geschreven:
> 
> Yes, I have reinstalled several times already, but the problem still appears.
> 
> 发自我的 iPad
> 
>>> 在 2015年11月1日，下午11:18，Nick Payne  写道：
>>> 
>>> On 01/11/2015 18:02, Brian Guo wrote:
>>> Hi,
>>> 
>>> I have just installed LilyPond version 2.19.30 on a Windows 10 (64 bit) 
>>> laptop, b
>>> laptop, but when I try to compile a simple score, such as:
>>> \version "2.19.30"
>>> \score {
>>>  \new Staff \relative c' {
>>>c
>>>  }
>>> }
>> 
>> Have you tried an uninstall/reinstall of 2.19.30? Your example builds 
>> without any problem on my laptop, which is running same OS and same version 
>> of Lilypond. The 2.19.30 install exe I downloaded is 30,178,860 bytes. There 
>> don't seem to be any checksums provided to verify the downloads.
>> 
>> Nick
>> 
>> ___
>> 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: 2.19.30 returns error code -1073741819

[guoguocuozuoduo]

Hi all,

I have reinstalled it once again and it finally works.
Thanks!

Regards,
Brian

发自我的 iPad

> 在 2015年11月2日，上午8:25，guoguocuozuoduo  写道：
> 
> Yes, I have reinstalled several times already, but the problem still appears.
> 
> 发自我的 iPad
> 
>>> 在 2015年11月1日，下午11:18，Nick Payne  写道：
>>> 
>>> On 01/11/2015 18:02, Brian Guo wrote:
>>> Hi,
>>> 
>>> I have just installed LilyPond version 2.19.30 on a Windows 10 (64 bit) 
>>> laptop, b
>>> laptop, but when I try to compile a simple score, such as:
>>> \version "2.19.30"
>>> \score {
>>>  \new Staff \relative c' {
>>>c
>>>  }
>>> }
>> 
>> Have you tried an uninstall/reinstall of 2.19.30? Your example builds 
>> without any problem on my laptop, which is running same OS and same version 
>> of Lilypond. The 2.19.30 install exe I downloaded is 30,178,860 bytes. There 
>> don't seem to be any checksums provided to verify the downloads.
>> 
>> Nick
>> 
>> ___
>> 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: 2.19.30 returns error code -1073741819

[guoguocuozuoduo]

Yes, I have reinstalled several times already, but the problem still appears.

发自我的 iPad

> 在 2015年11月1日，下午11:18，Nick Payne  写道：
> 
>> On 01/11/2015 18:02, Brian Guo wrote:
>> Hi,
>> 
>> I have just installed LilyPond version 2.19.30 on a Windows 10 (64 bit) 
>> laptop, b
>> laptop, but when I try to compile a simple score, such as:
>> \version "2.19.30"
>> \score {
>>   \new Staff \relative c' {
>> c
>>   }
>> }
> 
> Have you tried an uninstall/reinstall of 2.19.30? Your example builds without 
> any problem on my laptop, which is running same OS and same version of 
> Lilypond. The 2.19.30 install exe I downloaded is 30,178,860 bytes. There 
> don't seem to be any checksums provided to verify the downloads.
> 
> Nick
> 
> ___
> 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: Remove empty staves but one.

[Peter Reid]

Thanks for your reply David, 

I couldn't work out how to integrate your code into my score (I'm a beginner at 
Lilypond) but I searched for it on google and found what I was looking for here 
:

http://lilypond.1069038.n5.nabble.com/override-VerticalAxisGroup-remove-empty-works-only-at-the-beginning-of-a-score-td52152.html
 


Thanks again David and the Lilypond community,
Peter

> Le 2015 Nov 1 à 19:08, David Kastrup  a écrit :
> 
> preid mailto:p...@peterreid.org>> writes:
> 
>> Dear list, 
>> 
>> I'm working on a stage musical type score in which the last few bars contain
>> only spoken text over rests.  I am using this code :
>> 
>>  \layout {
>>\context {
>>  \Staff
>>  \RemoveEmptyStaves
>>  % To use the setting globally, uncomment the following line:
>>  \override VerticalAxisGroup #'remove-first = ##t
>>} 
>> }
>> \version "2.18.2"
>> 
>> I'm using this code within \score to display my spoken text as recommended
>> in the fine manual.
>>  \override LyricText.font-shape = #'italic
>>  \override LyricText.self-alignment-X = #LEFT
>> 
>> Everything works great except that the last staves are hidden since they
>> contain only rests, and the spoken text floats in the void. Is there a way
>> of overriding RemoveEmptyStaves temporarily, perhaps by forcing a bar rest
>> to appear for instance.  
>> 
>> I've done lots of searching and up to now I've always found solutions to my
>> problems but this one has got me stumped.
>> 
>> Thanks in advance, 
>> Peter
>> 
>> PS. Thanks to everyone who contributes to Lilypond I'm really enjoying using
>> it and I really appreciate all the hard work that goes into it.
> 
> \set Staff.remove-empty = ##f maybe?
> 
> -- 
> David Kastrup

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

Re: Remove empty staves but one.

[David Kastrup]

preid  writes:

> Dear list, 
>
> I'm working on a stage musical type score in which the last few bars contain
> only spoken text over rests.  I am using this code :
>
>   \layout {
> \context {
>   \Staff
>   \RemoveEmptyStaves
>   % To use the setting globally, uncomment the following line:
>   \override VerticalAxisGroup #'remove-first = ##t
> } 
> }
> \version "2.18.2"
>
> I'm using this code within \score to display my spoken text as recommended
> in the fine manual.
>   \override LyricText.font-shape = #'italic
>   \override LyricText.self-alignment-X = #LEFT
>
> Everything works great except that the last staves are hidden since they
> contain only rests, and the spoken text floats in the void. Is there a way
> of overriding RemoveEmptyStaves temporarily, perhaps by forcing a bar rest
> to appear for instance.  
>
> I've done lots of searching and up to now I've always found solutions to my
> problems but this one has got me stumped.
>
> Thanks in advance, 
> Peter
>
> PS. Thanks to everyone who contributes to Lilypond I'm really enjoying using
> it and I really appreciate all the hard work that goes into it.

\set Staff.remove-empty = ##f maybe?

-- 
David Kastrup

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

Remove empty staves but one.

[preid]

Dear list, 

I'm working on a stage musical type score in which the last few bars contain
only spoken text over rests.  I am using this code :

  \layout {
\context {
  \Staff
  \RemoveEmptyStaves
  % To use the setting globally, uncomment the following line:
  \override VerticalAxisGroup #'remove-first = ##t
} 
}
\version "2.18.2"

I'm using this code within \score to display my spoken text as recommended
in the fine manual.
  \override LyricText.font-shape = #'italic
  \override LyricText.self-alignment-X = #LEFT

Everything works great except that the last staves are hidden since they
contain only rests, and the spoken text floats in the void. Is there a way
of overriding RemoveEmptyStaves temporarily, perhaps by forcing a bar rest
to appear for instance.  

I've done lots of searching and up to now I've always found solutions to my
problems but this one has got me stumped.

Thanks in advance, 
Peter

PS. Thanks to everyone who contributes to Lilypond I'm really enjoying using
it and I really appreciate all the hard work that goes into it.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Remove-empty-staves-but-one-tp183033.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: Using fonts installed on the system

[Klaus Blum]

At least, I can confirm that there must have been a change since 2.19.25:

In the docs there's a command to enumerate all available fonts:
$lilypond -dshow-available-fonts x

2.19.25 reports "Wingdings" as
family Wingdings
 Wingdings:style=Regular

2.19.30 reports it as
family Wingdings

Wingdings:style=Regular,normal,Standard,Normaali,Normale,Standaard,Normálne,Navadno

I have no idea if this helps to narrow the problem. 
I even don't know if it's caused by a change in LilyPond itself or some
third party library/module or the mingw environment...

Can anybody help?

Thanks, 
Klaus



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Using-fonts-installed-on-the-system-tp182919p183030.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: Q regarding best practice with \relative

[David Kastrup]

Michael Gerdau  writes:

> Hello lilyponders,
>
> in (very?) recent versions of the manuals I've seen notations like
> \relative { c' d e f g a b c }
> while older editions and e.g. all the templates in frescobaldi use
> \relative c' { c d e f g a b c }
>
> Obviously both produce exactly the same result.
>
> Is there something like a "best practice" w/r to the use of \relative?
> Or why does this difference exist ?

Historically, \relative { ... } was equivalent to \relative c' { ... }.
This historic use (at one time the only possible one) was deprecated
since c' seems rather arbitrary and it seemed to make better sense to
make the reference point explicit.  Particularly so since
\relative { f } resolved to f' while \relative { g } resolved to g.

The reference point itself was the issue of several conflicting
conventions.  The documentation suggested using an octave of c (but did
not really follow this convention entirely consistently).  Others
preferred using the first pitch in the music, just with the correct
octave added.

After it was pointed out that one could instead just add the correct
octave to the first pitch itself when using \relative f { ... } which
makes the first pitch inside be interpreted just like absolute pitch.
So this started sort of another convention that some people were fond
of.  In contrast to other conventions, it had a somewhat less than
arbitrary reason for its choice of the reference pitch (namely being
able to just write the first pitch absolute).  However, the reason for
this being a somewhat non-arbitrary choice of reference pitch is a
calculated reason (namely f being exactly the middle of the normal
scale) rather than a reason _associated_ with the pitch f in any
discernible manner.

So \relative f { ... } just looked weird because the "f" was just an
artifact of the way the scale is organized while still having some
reasonable justification _not_ really associated with f.

So there was a (not particularly overwhelming) agreement on making this
the default behavior of \relative without explicit reference pitch (it
actually does not use "f" but rather the middle of the current scale, so
when you use something other than the standard diatonic scale, the
salient point of the first pitch being specified absolutely is still
retained).  And after a while, a change to mostly use this convention in
our documentation.

So it was sort of an evolutionarily achieved agreement to go with this
change as it benefits those who like leaving the reference pitch as the
first pitch inside of \relative itself since people with other
preferences can still express them reasonally naturally with an explicit
reference pitch while the reference pitch of "f" detracts from the
_meaning_ of this construct.

There was also weak(er) agreement over using this convention in
preference to others in our documentation examples as it's basically the
only one without an arbitrary element.

So there's not really a "best practice" but rather one that requires
least choice-making for those not interested in making more choices than
necessary.

-- 
David Kastrup

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

Q regarding best practice with \relative

[Michael Gerdau]

Hello lilyponders,

in (very?) recent versions of the manuals I've seen notations like
\relative { c' d e f g a b c }
while older editions and e.g. all the templates in frescobaldi use
\relative c' { c d e f g a b c }

Obviously both produce exactly the same result.

Is there something like a "best practice" w/r to the use of \relative?
Or why does this difference exist ?

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver

signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 2.19.30 returns error code -1073741819

[Stephan Neuhaus]

On 2015-11-01 11:18, Nick Payne wrote:
> On 01/11/2015 18:02, Brian Guo wrote:
>> Hi,
>>
>> I have just installed LilyPond version 2.19.30 on a Windows 10 (64
>> bit) laptop, b
>> laptop, but when I try to compile a simple score, such as:
>> \version "2.19.30"
>> \score {
>>\new Staff \relative c' {
>>  c
>>}
>> }
> 
> Have you tried an uninstall/reinstall of 2.19.30? 

If it's an access control problem, I would rather guess that either the
output file already exists and isn't writeable, or perhaps it's a directory.

Best,

Stephan
-- 
GPG key ID 4BDA81D3
fingerprint 5F88 399F 8811 72BE B36A  FC93 4D13 FCB2 4BDA 81D3

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

Re: Help with accaciatura

[Alberto Simões]

On 01/11/15 08:22, David Kastrup wrote:

tisimst  writes:


As in

\acciacciatura s8

Or whatever the right duration is.


More like \grace s8 since \acciaccatura [sic!] adds a slur if I am not
mistaken.



Thank you all.
Although it is a bug, as someone pointed out, after we are aware it 
exists, is easy to workaround ;)


Thank you
Alberto

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

Re: 2.19.30 returns error code -1073741819

[Nick Payne]

On 01/11/2015 18:02, Brian Guo wrote:

Hi,

I have just installed LilyPond version 2.19.30 on a Windows 10 (64 bit) laptop, 
b
laptop, but when I try to compile a simple score, such as:
\version "2.19.30"
\score {
   \new Staff \relative c' {
 c
   }
}


Have you tried an uninstall/reinstall of 2.19.30? Your example builds 
without any problem on my laptop, which is running same OS and same 
version of Lilypond. The 2.19.30 install exe I downloaded is 30,178,860 
bytes. There don't seem to be any checksums provided to verify the 
downloads.


Nick

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

Re: 2.19.30 returns error code -1073741819

[lilyp...@andis59.se]

-1073741819(0xc005)  means Access Violation, but we need to know a bit more 
to find the culprit.

Please run LilyPond with Verbose output-V, --verbose and post the output. 
http://www.lilypond.org/doc/v2.19/Documentation/usage/command_002dline-usage#basic-command-line-options-for-lilypond 



Is the pdf created?

// Anders

On 2015-11-01 08:02, Brian Guo wrote:

Hi,

I have just installed LilyPond version 2.19.30 on a Windows 10 (64 bit) laptop, 
b
laptop, but when I try to compile a simple score, such as:
\version "2.19.30"
\score {
   \new Staff \relative c' {
 c
   }
}
Everything seems to be fine up to "Converting to `document.pdf'...", but th
then I get an "Exited with return code -1073741819" error message.

Is there a way that I can fix this problem?
Thanks a lot!

Regards,
Brian


___
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: Help with accaciatura

[David Kastrup]

tisimst  writes:

> As in
>
> \acciacciatura s8
>
> Or whatever the right duration is.

More like \grace s8 since \acciaccatura [sic!] adds a slur if I am not
mistaken.

-- 
David Kastrup

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

2.19.30 returns error code -1073741819

[Brian Guo]

Hi,

I have just installed LilyPond version 2.19.30 on a Windows 10 (64 bit) laptop, 
b
laptop, but when I try to compile a simple score, such as: 
\version "2.19.30"
\score {
  \new Staff \relative c' {
c
  }
}
Everything seems to be fine up to "Converting to `document.pdf'...", but th
then I get an "Exited with return code -1073741819" error message.

Is there a way that I can fix this problem?
Thanks a lot!

Regards,
Brian


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