date:20171208

Hi Ben,

> I'm not too familiar with Ubuntu's update path, but is it possible for
> you to upgrade to 17.04 - maybe the poppler issue has been resolved in
> later releases? Just an idea for testing. If you're not wanting to leave
> your older-but-stable OS, I totally understand.

With 17.04 I had to install an older python3-poppler-qt5 as described
above to solve the issue. But with 17.10 Frescobaldi works again out of
the box on my computer.

Cheers,
Joram

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

Re: Frescobaldi 3,.0 CRAHES


On 12/8/2017 5:52 PM, Andrew Bernard wrote:

Hi Ben and All,

I have to run F 3 on Mint because I can't get the dependencies all 
lined up for Ubuntu 16.04. It's incredibly difficult, to the point 
that I had given up and I run a Mint VM just for F 3.


Now that others are also having problems, perhaps I will look into 
this again. As to what the differences in environment are between Mint 
and Ubuntu are that affect this, I just don't know. But I will find 
out for us all.


I wonder what platform F is developed on?

Andrew



I'm not too familiar with Ubuntu's update path, but is it possible for 
you to upgrade to 17.04 - maybe the poppler issue has been resolved in 
later releases? Just an idea for testing. If you're not wanting to leave 
your older-but-stable OS, I totally understand.



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

Re: Frescobaldi 3,.0 CRAHES

Cross reference in this thread:
https://lists.gnu.org/archive/html/lilypond-user/2017-12/msg00187.html

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

Re: Frescobaldi 3,.0 CRAHES

2017-12-08 Thread Saul Tobin

Possibly related, I've noticed that the 16.04 repository version of
Frescobaldi has been holding back python3-pyqt4 and python3-sip from
upgrading for several months.

On Fri, Dec 8, 2017 at 2:52 PM, Andrew Bernard 
wrote:

> Hi Ben and All,
>
> I have to run F 3 on Mint because I can't get the dependencies all lined
> up for Ubuntu 16.04. It's incredibly difficult, to the point that I had
> given up and I run a Mint VM just for F 3.
>
> Now that others are also having problems, perhaps I will look into this
> again. As to what the differences in environment are between Mint and
> Ubuntu are that affect this, I just don't know. But I will find out for us
> all.
>
> I wonder what platform F is developed on?
>
> Andrew
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi 3,.0 CRAHES

2017-12-08 Thread Andrew Bernard

Hi Ben and All,

I have to run F 3 on Mint because I can't get the dependencies all lined up
for Ubuntu 16.04. It's incredibly difficult, to the point that I had given
up and I run a Mint VM just for F 3.

Now that others are also having problems, perhaps I will look into this
again. As to what the differences in environment are between Mint and
Ubuntu are that affect this, I just don't know. But I will find out for us
all.

I wonder what platform F is developed on?

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

Re: Required font for simplified Chinese characters?

2017-12-08 Thread Andrew Bernard

Hello Jinsong,

I am having trouble seeing how your answer is different to mine, apart from
the fact that SimHei is not installed by default on Ubuntu. [Of course, he
can pick any font he likes.] Was there something else you wanted to add
that we should know about this technique?

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

Re: Python dependencies: plea for help

Hi Simon,

on which system? And do you need to build it or can you use a deb package?

As discussed on Sept 23rd on this list [1], I used this package
python3-poppler-qt5_0.24.2-3build1_amd64.deb on my Ubuntu machine. And
Jamie found out where it came from:

> This one worked for me: 
> https://answers.launchpad.net/~canonical-foundations/+archive/ubuntu/python3.6-as-default/+files/python3-poppler-qt5_0.24.2-3build1_amd64.deb

Does that solve your proplem?

Cheers,
Joram


[1]:
https://lists.gnu.org/archive/html/lilypond-user/2017-09/msg00428.html
(it was an Ubuntu package not debian)

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

Re: removing automatically generated natural signs


On 08.12.2017 23:18, Chris Jones wrote:

As a matter of fact without being an expert I have great respect for
quality typesetting, past and present... paper-oriented or digital.


Quality typesetting requires some degree of understanding about what you 
are typesetting; so if you’re going to do quality music engraving, 
you’ll need a decent understanding of music theory. LilyPond is designed 
to allow your typesetting solutions to be in line with how the music works.


Best, Simon

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

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 04:40:51PM EST, David Kastrup wrote:
> Chris Jones  writes:
> 
[..]
> 
> Don't underestinmate the anonymous grease monkeys in printers' shops.

Far from my intention I can assure you.

As a matter of fact without being an expert I have great respect for
quality typesetting, past and present... paper-oriented or digital.

And that is precisely the reason I am currently looking at epub's
capabilities and so far I have not come across anything that I like.

Thanks,

CJ

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

Python dependencies: plea for help


Hello everybody,

following the post by Vincenzo I take the liberty of turning to this 
group for advice, even if it’s OT. It’s such a hassle working with 
LilyPond without Frescobaldi, and I couldn’t solve the problem described 
in .


So I beg your pardon and beg for advice on how to proceed, even if it’s 
just about how to completely purge all of python3.x and frescobaldi and 
the packages inbetween and reinstalling so that everything works…


Best, Simon


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

Re: Frescobaldi CRASHES

2017-12-08 Thread Robert Schmaus

There's not much information in your mail but fwiw: I had the problem of 
Frescobaldi crashing right away when I opened it (on a Mac). Solved it by 
completely trashing the preferences. 



> On 8 Dec 2017, at 19:53, Son_V  wrote:
> 
> I'm no more able to open any .ly file in UbuntuStudio, Frescobaldi crashes in
> a breath, what can I do?
> Thanks.
> 
> 
> 
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
> 
> ___
> 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: Frescobaldi 3,.0 CRAHES


On 12/8/2017 4:59 PM, Simon Albrecht wrote:

Hi Vincenzo,

I haven’t been able to get any version of Frescobaldi working under 
Ubuntu 16.04, sadly. I made several attempts at fixing it, and there’s 
some information here: 



Unfortunately, the dependencies seem to be terribly difficult to get 
right, at least under certain circumstances.


Best, Simon


On 08.12.2017 20:04, Son_V wrote:

It's the second message on the same subject I post, but I don't see the
first, in case excuse me...
If I try to open a .ly file in Frescobaldi 3.0 (installed blindly as an
update) it (Frescobaldi) crashes in a breath.
What can I do? Thanks.



Linux Mint is based on Ubuntu and I have been successful in running 
Frescobaldi 3 for quite some time now on it without issue. I wonder why 
it would fail on Ubuntu and not it's derivatives.


Any guesses?


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

Re: Frescobaldi 3,.0 CRAHES


On 08.12.2017 20:04, Son_V wrote:

It's the second message on the same subject I post, but I don't see the
first, in case excuse me...


Both arrived, so please check in the online archives (they update about 
every half hour) before reposting your e-mail.

Best, Simon

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

Re: Frescobaldi 3,.0 CRAHES


Hi Vincenzo,

I haven’t been able to get any version of Frescobaldi working under 
Ubuntu 16.04, sadly. I made several attempts at fixing it, and there’s 
some information here: 



Unfortunately, the dependencies seem to be terribly difficult to get 
right, at least under certain circumstances.


Best, Simon


On 08.12.2017 20:04, Son_V wrote:

It's the second message on the same subject I post, but I don't see the
first, in case excuse me...
If I try to open a .ly file in Frescobaldi 3.0 (installed blindly as an
update) it (Frescobaldi) crashes in a breath.
What can I do? Thanks.



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
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: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 03:30:00PM EST, Simon Albrecht wrote:
> On 08.12.2017 20:09, Chris Jones wrote:
> > Wouldn't this become rather painful/tedious if the gentleman who wrote
> > this particular song had had the bright idea of transposing it to
> > a fancier key like... G# major for instance?
> > 
> > If that were the case I would have to add an "is" to just about every
> > single note in the score!
> 
> You could use e.g. english note names if it’s only about the typing: that
> saves you one keystroke per flat/sharp/doublesharp.
> 

I can type reasonably fast... much faster than I can think, anyway.

I made the decision to stick with the Dutch [is/es] because with two
letters I find it easier to spot the accidentals.

The reason behind this is that a beginner like myself is likely to spend
far more time reading what he typed over and over in order to fix
mistakes than typing.

So I decided I might as well stick with a notation that is a bit less
cryptic than the [b,s] English form. 

The extra letter helps make the accidentals stand out.

Thanks,

CJ

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

Frescobaldi 3,.0 CRAHES

2017-12-08 Thread Son_V

It's the second message on the same subject I post, but I don't see the
first, in case excuse me...
If I try to open a .ly file in Frescobaldi 3.0 (installed blindly as an
update) it (Frescobaldi) crashes in a breath.
What can I do? Thanks.



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Frescobaldi CRASHES

2017-12-08 Thread Son_V

I'm no more able to open any .ly file in UbuntuStudio, Frescobaldi crashes in
a breath, what can I do?
Thanks.



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: removing automatically generated natural signs

2017-12-08 Thread David Kastrup

Chris Jones  writes:

> But that is precisely the documentation I have been reading over and
> over without being able to quite understand the implications. 
>
> And I think that my problem lies with the last word: "... hear". 
>
> Since I am not a musician but a mere scribe when I am looking at sheet
> music... I do *not* hear anything. ;)

LilyPond can be easily made to produce Midi files which one can replay
proper software.  It's probably a good idea to "proofhear" your
rendition in order to figure out whether it sounds sensible.

The problem with not spelling notes out properly but merely copying
their visuals is that this is not robust against a whole number of
modifications (like a canon shifted by half a measure), that it is a
nightmare to change the notation conventions, that copy does not
work musically.

> But since I am not a musician not by any stretch of the imagination...
> and therefore I do not understand whether any changes that creep in
> matter or not... I am trying to have my lilypond output reproduce the
> original as faithfully as possible.
>
> So now that I have reached the point where song #1 is almost ready
> there are still a couple of minor but nonetheless annoying issues that
> need to be addressed before I can move on to the remaining eleven.
>
> And one of them is getting rid of these naturals that are not in the
> original.

They will likely disappear when using the "correct" note names.  The
problem with wanting to use LilyPond only as a musical typewriter is
that LilyPond takes care of a number of fine points of typesetting that
just depend on more than a superficial understanding of the content.
For example, there are accidentals that only appear right after a line
break but are otherwise removed.  So the output depends on line break
decisions.

> Obviously rather than tampering with lilypond's output after the fact
> I would much rather find a way to force the software to reproduce the
> original score down to every detail.
>
> Anyway, sorry for the lenghty explanation but since this mailing list
> appears to be mostly a haunt for the the music-savvy... I thought I
> might make it clear that I am not trying to emulate Ludwig Van or
> Johannes B. but rather the anonymous grease monkey in the printer's
> shop.

Don't underestinmate the anonymous grease monkeys in printers' shops.

Sorry for your pains.  Unfortunately, I cannot really think of a way to
make this more to your liking in a manner that would not become even
more prone to problems.

-- 
David Kastrup

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

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 03:23:35PM EST, Noeck wrote:
> Hi,
> 
> this isa bad hack I would not recommend, but you *could* revert the key
> back to c major without showing it:
> 
> \relative {
>   \key g \major
>   c'
>   \once \omit Staff.KeyCancellation
>   \key c \major
>   d e f g a b c
> }
> 
> Midi, transposition etc. will be broken, of course.

Indeed. Never shy of an ugly hack... I was vaguely contemplating
something along these lines. ;)

Thanks,

CJ

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

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 02:22:32PM EST, Ben wrote:
> (
> On 12/8/2017 2:09 PM, Chris Jones wrote:

[..]
>
> (from documentation)
> "...
> 
> To determine whether to print an *accidental*, LilyPond examines the pitches
> and the key signature. The key signature only affects the
> */printed/***accidentals, not the note’s pitch!
> 
> --> This is a feature that often causes confusion to newcomers, so let us
> explain it in more detail.
> 
> LilyPond makes a clear distinction between musical content and layout. The
> alteration (flat, natural sign or sharp) of a note is part of the pitch, and
> is therefore musical content. Whether an accidental (a */printed/***flat,
> natural or sharp sign) is printed in front of the corresponding note*is a
> question of layout*. Layout is something that follows rules, so accidentals
> are printed automatically according to those rules. The pitches in your
> music are works of art, so they will not be added automatically, and you
> must enter what you want to hear."
> 
> 
> Hope this helps :)

Indeed. 

But that is precisely the documentation I have been reading over and
over without being able to quite understand the implications. 

And I think that my problem lies with the last word: "... hear". 

Since I am not a musician but a mere scribe when I am looking at sheet
music... I do *not* hear anything. ;)

Moot point anyway... because in this particular instance my perspective
is completely different.

I am putting together an epub with images... and some of the images
happen to be the scores of a dozen songs, each one on a separate page. 

I initially tried to extract the images from the scanned PDF found
online but no matter how hard I tried fiddling the resolution, boosting
brightness & constrast, smoothing or sharpening... the end result was
barely legible and well... just too ugly for words.

So I figured I would look for something that produces high quality sheet
music output with the intention of creating a dozen .png images that
I could easily add to the epub.

That's how I came across lilypond and after spending the weekend reading
the documentation and experimenting I was able to come up with something
quite satisfactory. (cf. note 1)

But since I am not a musician not by any stretch of the imagination...
and therefore I do not understand whether any changes that creep in
matter or not... I am trying to have my lilypond output reproduce the
original as faithfully as possible. 

So now that I have reached the point where song #1 is almost ready there
are still a couple of minor but nonetheless annoying issues that need to
be addressed before I can move on to the remaining eleven.

And one of them is getting rid of these naturals that are not in the
original. 

I do realize that it is quite possible that the original typesetting of
the song is at best sloppy in this respect and that lilypond is right
amending it. 

But that's not for me to decide.

Obviously rather than tampering with lilypond's output after the fact
I would much rather find a way to force the software to reproduce
the original score down to every detail. 

Anyway, sorry for the lenghty explanation but since this mailing list
appears to be mostly a haunt for the the music-savvy... I thought
I might make it clear that I am not trying to emulate Ludwig Van or
Johannes B. but rather the anonymous grease monkey in the printer's
shop.

Thanks,

CJ

1. The rendering of my first .png on a 7" ~300 dpi android tablet is
   absolutely gorgeous... looks as good as high quality sheet music you
   could buy from the store.

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

Re: Required font for simplified Chinese characters?

2017-12-08 Thread James Harkins


On December 8, 2017 12:33:21 Andrew Bernard  wrote:


Hi James,

What platform are you on?

Do you want simplified or traditional characters?


Oh right, I forgot the OS. I'm on Ubuntu Studio 16.04.

I'm based in mainland China, so, simplified characters.

Btw my messages seem to be delayed pretty regularly -- the last message 
took a day and a half to go out on the list. Which isn't a big problem for 
me, except it looks like I'm not replying quickly :D


Thanks,
hjh

Sent with AquaMail for Android
http://www.aqua-mail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: removing automatically generated natural signs


On 08.12.2017 20:58, Urs Liska wrote:

I think this is a great way to explain this concept. And I also belong to the 
party of those who want to write down (encode) what it*is*  and not what it 
looks like.


However, sometimes in ancient music accidentals are _not_ part of the 
actual content, but truly up to the performer. In that case I’d 
sometimes like to code a pitch with ‘neutral’ accidental and add the -is 
or -es as part of the presentation.


Best, Simon

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

Re: removing automatically generated natural signs


On 08.12.2017 20:09, Chris Jones wrote:

Wouldn't this become rather painful/tedious if the gentleman who wrote
this particular song had had the bright idea of transposing it to
a fancier key like... G# major for instance?

If that were the case I would have to add an "is" to just about every
single note in the score!


You could use e.g. english note names if it’s only about the typing: 
that saves you one keystroke per flat/sharp/doublesharp.



Best, Simon

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

Re: removing automatically generated natural signs

Hi,

this isa bad hack I would not recommend, but you *could* revert the key
back to c major without showing it:

\relative {
  \key g \major
  c'
  \once \omit Staff.KeyCancellation
  \key c \major
  d e f g a b c
}

Midi, transposition etc. will be broken, of course.

Cheers,
Joram

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

Re: removing automatically generated natural signs

2017-12-08 Thread Urs Liska



Am 8. Dezember 2017 21:06:05 MEZ schrieb Ben :
>On 12/8/2017 2:58 PM, Urs Liska wrote:
>>
>>> (from documentation)
>>> "...
>>>
>>> To determine whether to print an *accidental*, LilyPond examines the
>>> pitches and the key signature. The key signature only affects the
>>> */printed/***accidentals, not the note’s pitch!
>>>
>>> --> This is a feature that often causes confusion to newcomers, so
>let
>>> us explain it in more detail.
>>>
>>> LilyPond makes a clear distinction between musical content and
>layout.
>>> The alteration (flat, natural sign or sharp) of a note is part of
>the
>>> pitch, and is therefore musical content. Whether an accidental (a
>>> */printed/***flat, natural or sharp sign) is printed in front of the
>>> corresponding note*is a question of layout*.
>> But to be fair one should note that there are serious encoding
>systems out there that work like the OP expects, for example the MEI
>encoding format or the Amadeus notation software.
>>
>
>I didn't think Amadeus was still being developed...?

It isn't but there still are a handful og users still around who had invested 
enormous amounts of money back in thr eighties ;-)
It seems the original developer is still alive snd can be talked into fixing 
small items occasionally.

Urs

>
>> When I discussed the topic with an Amadeus power user he said that he
>would go nuts with all the typing (of the extra is and es) with the
>thousands of pages of music he has to create every year.
>
>I went nuts typing with SCORE for years but looking back, it built 
>character I say :)
>
>> MEI on the other hand wants to encode "what is on the paper", that
>is: an "a" for any pitch on that step.  However, I don't accept that
>because that a flat in e flat major is *not* printed as an "a" that
>becomes an a flat through the key signature. Actually it's a note head
>in the second space that becomes an a through the treble clef and only
>then an a flat.
>>
>> Urs
>>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

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

Re: removing automatically generated natural signs

2017-12-08 Thread Kieren MacMillan

Urs,

> But to be fair one should note that there are serious encoding systems out 
> there that work like the OP expects, for example the MEI encoding format or 
> the Amadeus notation software. 
> When I discussed the topic with an Amadeus power user he said that he would 
> go nuts with all the typing (of the extra is and es) with the thousands of 
> pages of music he has to create every year.
> MEI on the other hand wants to encode "what is on the paper", that is: an "a" 
> for any pitch on that step.  However, I don't accept that because that a flat 
> in e flat major is *not* printed as an "a" that becomes an a flat through the 
> key signature. Actually it's a note head in the second space that becomes an 
> a through the treble clef and only then an a flat.

There is no reason one can't code some syntactic sugar to make it work “as 
expected” (i.e., without "all the 'extra' typing") in Lilypond as well.
I just don't think it's a great idea.  =)

Cheers,
Kieren.


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


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

Re: removing automatically generated natural signs

On 12/8/2017 2:58 PM, Urs Liska wrote:

(from documentation)
"...

To determine whether to print an *accidental*, LilyPond examines the
pitches and the key signature. The key signature only affects the
*/printed/***accidentals, not the note’s pitch!

--> This is a feature that often causes confusion to newcomers, so let
us explain it in more detail.

LilyPond makes a clear distinction between musical content and layout.
The alteration (flat, natural sign or sharp) of a note is part of the
pitch, and is therefore musical content. Whether an accidental (a
*/printed/***flat, natural or sharp sign) is printed in front of the
corresponding note*is a question of layout*.

But to be fair one should note that there are serious encoding systems out
there that work like the OP expects, for example the MEI encoding format or the
Amadeus notation software.

I didn't think Amadeus was still being developed...?

When I discussed the topic with an Amadeus power user he said that he would go
nuts with all the typing (of the extra is and es) with the thousands of pages
of music he has to create every year.

I went nuts typing with SCORE for years but looking back, it built
character I say :)

MEI on the other hand wants to encode "what is on the paper", that is: an "a" for any
pitch on that step. However, I don't accept that because that a flat in e flat major is *not* printed as an
"a" that becomes an a flat through the key signature. Actually it's a note head in the second space
that becomes an a through the treble clef and only then an a flat.

Urs

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

Re: removing automatically generated natural signs

2017-12-08 Thread Urs Liska



Am 8. Dezember 2017 20:22:32 MEZ schrieb Ben :
>(
>On 12/8/2017 2:09 PM, Chris Jones wrote:
>> I would need some help removing the autmatically generated natural
>signs
>> that I see in lilypond's output.
>>
>> |   melody = \relative c {
>> | \global
>> |   \partial 16 d'16 \bar "||"
>> |   \set melismaBusyProperties = #'()
>> |   \autoBeamOff
>> |   \set Staff.extraNatural = ##f
>> |   g4.. g16 f8. g16 a8. g16|   % b01
>>
>> ... expecting to see output with no accidentals.
>
>See below.
>
>>
>> Obvious workaround is coding "fis8l." instead of "f8." to get rid of
>> that extra natural sign:
>
>Yes. This is correct. It's one of the great things about LilyPond in my
>
>opinion. (how it works semantically, etc)
>
>>
>> |   g4.. g16 fis8. g16 a8. g16  |   % b01
>>
>> ... and remember to do the same for every "F" in my .ly file.
>>
>> I have read the section entitled "Warning: key signatures and
>pitches"
>> in the lilypond learning manual at least a dozen times and I still
>don't
>> see why I would need to do that.
>>
>> Wouldn't this become rather painful/tedious if the gentleman who
>wrote
>> this particular song had had the bright idea of transposing it to
>> a fancier key like... G# major for instance?
>>
>> If that were the case I would have to add an "is" to just about every
>> single note in the score!
>>
>>
>
>(from documentation)
>"...
>
>To determine whether to print an *accidental*, LilyPond examines the 
>pitches and the key signature. The key signature only affects the 
>*/printed/***accidentals, not the note’s pitch!
>
>--> This is a feature that often causes confusion to newcomers, so let 
>us explain it in more detail.
>
>LilyPond makes a clear distinction between musical content and layout. 
>The alteration (flat, natural sign or sharp) of a note is part of the 
>pitch, and is therefore musical content. Whether an accidental (a 
>*/printed/***flat, natural or sharp sign) is printed in front of the 
>corresponding note*is a question of layout*. Layout is something that 
>follows rules, so accidentals are printed automatically according to 
>those rules. The pitches in your music are works of art, so they will 
>not be added automatically, and you must enter what you want to hear."
>
>
>Hope this helps :)

I think this is a great way to explain this concept. And I also belong to the 
party of those who want to write down (encode) what it *is* and not what it 
looks like.

But to be fair one should note that there are serious encoding systems out 
there that work like the OP expects, for example the MEI encoding format or the 
Amadeus notation software. 

When I discussed the topic with an Amadeus power user he said that he would go 
nuts with all the typing (of the extra is and es) with the thousands of pages 
of music he has to create every year.

MEI on the other hand wants to encode "what is on the paper", that is: an "a" 
for any pitch on that step.  However, I don't accept that because that a flat 
in e flat major is *not* printed as an "a" that becomes an a flat through the 
key signature. Actually it's a note head in the second space that becomes an a 
through the treble clef and only then an a flat.

Urs

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

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

Re: removing automatically generated natural signs

2017-12-08 Thread David Wright

On Fri 08 Dec 2017 at 14:09:31 (-0500), Chris Jones wrote:
> I would need some help removing the autmatically generated natural signs
> that I see in lilypond's output.
> 
> I coded this:
> 
> |   global = {
> | \time 4/4
> | \key g \major
> | \tempo \markup { \concat {Mouv. \super t} de Marche}
> |   }
> |   
> |   #(set-global-staff-size 16.5)
> |   
> |   melody = \relative c {
> | \global
> |   \partial 16 d'16 \bar "||" 
> |   \set melismaBusyProperties = #'()
> |   \autoBeamOff
> |   \set Staff.extraNatural = ##f
> |   g4.. g16 f8. g16 a8. g16|   % b01
> 
> ... expecting to see output with no accidentals.
> 
> Now what happens is that lilypond adds a natural sign in front of the
> "f8"... thus changing the implied F# (key is G major) to an F... (?)

There is no "implied" F#. The \key specifies the key signature
to be printed. It has no effect on the pitches of following notes.

> Obvious workaround is coding "fis8l." instead of "f8." to get rid of
> that extra natural sign:

If the music contains an F#, you have to write fis.

> |   g4.. g16 fis8. g16 a8. g16  |   % b01
> 
> ... and remember to do the same for every "F" in my .ly file.
> 
> I have read the section entitled "Warning: key signatures and pitches"
> in the lilypond learning manual at least a dozen times and I still don't
> see why I would need to do that.

Well, you've found the correct section to read, but have
yet to understand its simplicity: for the musical pitch FOO,
write the note FOO into the LP file.

Cheers,
David.

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

Re: removing automatically generated natural signs


(
On 12/8/2017 2:09 PM, Chris Jones wrote:

I would need some help removing the autmatically generated natural signs
that I see in lilypond's output.

|   melody = \relative c {
| \global
|   \partial 16 d'16 \bar "||"
|   \set melismaBusyProperties = #'()
|   \autoBeamOff
|   \set Staff.extraNatural = ##f
|   g4.. g16 f8. g16 a8. g16|   % b01

... expecting to see output with no accidentals.


See below.



Obvious workaround is coding "fis8l." instead of "f8." to get rid of
that extra natural sign:


Yes. This is correct. It's one of the great things about LilyPond in my 
opinion. (how it works semantically, etc)




|   g4.. g16 fis8. g16 a8. g16  |   % b01

... and remember to do the same for every "F" in my .ly file.

I have read the section entitled "Warning: key signatures and pitches"
in the lilypond learning manual at least a dozen times and I still don't
see why I would need to do that.

Wouldn't this become rather painful/tedious if the gentleman who wrote
this particular song had had the bright idea of transposing it to
a fancier key like... G# major for instance?

If that were the case I would have to add an "is" to just about every
single note in the score!




(from documentation)
"...

To determine whether to print an *accidental*, LilyPond examines the 
pitches and the key signature. The key signature only affects the 
*/printed/***accidentals, not the note’s pitch!


--> This is a feature that often causes confusion to newcomers, so let 
us explain it in more detail.


LilyPond makes a clear distinction between musical content and layout. 
The alteration (flat, natural sign or sharp) of a note is part of the 
pitch, and is therefore musical content. Whether an accidental (a 
*/printed/***flat, natural or sharp sign) is printed in front of the 
corresponding note*is a question of layout*. Layout is something that 
follows rules, so accidentals are printed automatically according to 
those rules. The pitches in your music are works of art, so they will 
not be added automatically, and you must enter what you want to hear."



Hope this helps :)

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

Re: removing automatically generated natural signs


On 12/8/2017 2:09 PM, Chris Jones wrote:

I would need some help removing the autmatically generated natural signs
that I see in lilypond's output.

I coded this:

|   global = {
| \time 4/4
| \key g \major
| \tempo \markup { \concat {Mouv. \super t} de Marche}
|   }
|
|   #(set-global-staff-size 16.5)
|
|   melody = \relative c {
| \global
|   \partial 16 d'16 \bar "||"
|   \set melismaBusyProperties = #'()
|   \autoBeamOff
|   \set Staff.extraNatural = ##f
|   g4.. g16 f8. g16 a8. g16|   % b01

... expecting to see output with no accidentals.

Now what happens is that lilypond adds a natural sign in front of the
"f8"... thus changing the implied F# (key is G major) to an F... (?)

Obvious workaround is coding "fis8l." instead of "f8." to get rid of
that extra natural sign:

|   g4.. g16 fis8. g16 a8. g16  |   % b01

... and remember to do the same for every "F" in my .ly file.

I have read the section entitled "Warning: key signatures and pitches"
in the lilypond learning manual at least a dozen times and I still don't
see why I would need to do that.

Wouldn't this become rather painful/tedious if the gentleman who wrote
this particular song had had the bright idea of transposing it to
a fancier key like... G# major for instance?

If that were the case I would have to add an "is" to just about every
single note in the score!

This of course might be a non-issue e.g. for professional musicians who
think at a different level and hear what they are typing... but for
a mere "typesetter" like myself who has to make do with vague memories
of the very basics of music notation from his high school days this
could make life somewhat difficult...!

So... I initally looked for something that might let me globally
override this behavior via a single setting or command but I haven't
come across anything obvious.

As you can see above I tried adding a "\set Staff.extraNatural = #ff"
just in case--even though from what I read in the documentation it
didn't sound promising... but as I suspected this didn't help.

Is there any other way I could handle this?

Thanks,

CJ

PS. Attaching sample png's.



Sorry, I meant to say that *because *you're using that command ##f, the 
output should be as you have attached. :)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: removing automatically generated natural signs


On 12/8/2017 2:09 PM, Chris Jones wrote:

I would need some help removing the autmatically generated natural signs
that I see in lilypond's output.

I coded this:

|   global = {
| \time 4/4
| \key g \major
| \tempo \markup { \concat {Mouv. \super t} de Marche}
|   }
|
|   #(set-global-staff-size 16.5)
|
|   melody = \relative c {
| \global
|   \partial 16 d'16 \bar "||"
|   \set melismaBusyProperties = #'()
|   \autoBeamOff
|   \set Staff.extraNatural = ##f
|   g4.. g16 f8. g16 a8. g16|   % b01

... expecting to see output with no accidentals.


Not sure what version you're using in this project, but have you checked 
this page out? I believe it should help you. :)


http://lilypond.org/doc/v2.18/Documentation/notation/writing-pitches#accidentals


You can set extra naturals off easily in one command:

\set Staff.extraNatural = ##f


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

removing automatically generated natural signs