Re: naturalize pitches

[Peter Bjuhr]

On 2016-03-30 13:49, Jaime Oliver wrote:

Sometimes it preferable to change the source directly instead of using function 
calls.

Could you explain when this is the case?


This was only a general reflection. The source code is more transparent 
without getting filtered by functions that change the output. Also if 
you want to change something after the function is applied things can 
get complicated.



If we take the example of transposing to be more specific - transposing 
by Lilypond (with \transpose) contra transposing by Frescobaldi 
(Tools->Pitch->Transpose). The functionality is identical but 
Frescobaldi's version changes the source code but LilyPond only the 
output. When does this difference matter?


If we for example have a music variable that we want to transpose from C 
(major) to B (Major), but want to change a couple of g# to g (natural) 
afterwards. Then I think the Frescobaldi method is preferable because we 
have to make a copy of the variable anyway. And it's more 
straightforward to actually change the pitches from g# to g than to 
change from a to ab.


On the other hand if you know that you're not going to do any 
manipulation of the variable afterwards it's perhaps preferable to use 
the LilyPond method - in this case to avoid having to make a copy of the 
variable.


In general I think working with LilyPond features a whole range of 
interesting decisions between manipulating the source code directly and 
using functions (internal or usermade) to manipulate the output.


This is only a transposing instrument situation so it should be doable.


Yes, not much to think about in that case.

But I hope a made my point clearer!? :)

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

Re: naturalize pitches

[Jaime Oliver]

> Sometimes it preferable to change the source directly instead of using 
> function calls.

Could you explain when this is the case? 

This is only a transposing instrument situation so it should be doable. I used 
the \transpose function and \naturalize form the documentation which ended up 
working fine. 

The problems I had were caused by conflicts with the arrow microtones I was 
using. 

best,

J


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

Re: Using Google to find documentation (was Re: naturalize pitches)

[J Martin Rushton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Also works with duckduckgo

On 29/03/16 15:56, Knute Snortum wrote:
> Something you can do with Google to find documentation is use the 
> "site:" syntax:
> 
> site:lilypond.org/doc/v2.19  search 
> terms here
> 
> Or, if you want to search several sites, set up a link or bookmark 
> something like this:
> 
> https://www.google.com/search?q=searchKey+site:lilypond.org/doc/v2.19+
OR+site:lsr.di.unimi.it/LSR+OR+site:lilypond.1069038.n5.nabble.com
>
> 
> 
> 
> Knute Snortum (via Gmail)
> 
> On Fri, Mar 18, 2016 at 12:02 PM, Jaime Oliver
> > wrote:
> 
> well, some examples of the LSR 
> have "2.18 or higher” so you’d technically miss those if you only
> search for 2.19 examples. I guess there are also a certain number
> of core features that remain compatible through all versions, so
> there is a fair chance that these might work even if the version
> says 2.16.
> 
> best,
> 
> J
> 
> 
> 
>> On Mar 18, 2016, at 2:57 PM, Kristin Rollins 
>> > wrote:
>> 
>> Searching with Google tends to be more effective for me in
>> solving my issues with learning LilyPond and troubleshooting my
>> work, especially with the ability to simply type the query into
>> the address bar of my browser. (Though that is after I took the
>> time to go through the learning manual and at least review what
>> documentation is available to become familiar with it.)
>> 
>> The one thing I have learned, after a couple of instances of 
>> finding the wrong version's documentation (or multiple versions
>> of the documentation): I always start my search with:
>> 
>> lilypond 2.19
>> 
>> and then my search terms. That will usually make the official 
>> documentation for the proper version come to the top of the
>> search results and lower the risk of finding answers that relate
>> to previous versions.
>> 
>> Kristin
>> 
>> -- Kristin Rollins kris...@verumsolum.com
>>  Portsmouth, VA
>> 
>> On Fri, Mar 18, 2016, at 06:44 AM, David Kastrup wrote:
>>> That's one reason why it makes sense to look at the
>>> accompanying documentation of a LilyPond installation rather
>>> than search blindly for something on the net (which will
>>> frequently deliver outdated information and infrequently
>>> advance information).
>> 
>> ___ 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
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJW+vZFAAoJEAF3yXsqtyBlpCgP/iXycSX7BWNmju9cOXC22BKL
Ybu4WWOUzqceeXCyi4xg1mkZWtiT3CwXzZrGxoB54JeSrZqQXE+7u5iCNeQmxC45
8MS2RrRLwzz+XrM3W1/x5N6UCIGErU/uk7kFk1bkasY0krOQSe2wIFcME4x727oF
/g1Ytqk9vC2Y3FvOvEccLSi1DxAdr3qy190DcOnqv2KINYiKywpgwxfWdrGys+oy
NIvUlweKBbFESHEmcrf04dSLViqj9dT0xnLX4K35y2ovoFQdSoteQ7hK7gmyWhrR
mp85z1w+lJPSzuUA5s9guur0vRL/9dUZ1ldDeneggrfQIMqG84WXEbg4oZRkIyGL
VTOL6QwELNS3+8lOa64DQHCwh2KJBv5C6cau4g7ur//hQ1xrsUz3gsILx/819lEz
8rrM4tzQuKehxpt5KkfmWU7pzgawF1E6k6hlAD5sC6VpM+ysXUi2RYaXyW8xgbDc
9s7n08oOhGzD8/ibczJjGXpZkPMfOk+W3NSYIcsn2GRC03/qSL2xGUt+NP6W0+t5
lqwfEVx2szIRLfKJDDgjex1mmvUt1sgaYAR1/NJI6pztzGp/MPSOW+HvrOLQpknC
wqbP66WZhCdnCj9ufOpZfIbyghaV6ju62sXHl9aROKpV3IVxWAO3RIgjiS8PsDQR
2AHcJoNllXmj+ZZ2oei/
=XJRY
-END PGP SIGNATURE-

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

Re: naturalize pitches

[Peter Bjuhr]

On 2016-03-18 11:39, Jaime Oliver wrote:


I am using version 2.18.2-1, with frescobaldi on a mac os x 10.11.2

Any help would be greatly appreciated!


As you are using Frescobaldi you may want to take a look at Transpose, 
Modal transpose and Mode shift in Tools->Pitch.


Sometimes it preferable to change the source directly instead of using 
function calls.


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

Re: Using Google to find documentation (was Re: naturalize pitches)

[Knute Snortum]

Something you can do with Google to find documentation is use the "site:"
syntax:

site:lilypond.org/doc/v2.19 search terms here

Or, if you want to search several sites, set up a link or bookmark
something like this:

https://www.google.com/search?q=searchKey+site:lilypond.org/doc/v2.19+OR+site:lsr.di.unimi.it/LSR+OR+site:lilypond.1069038.n5.nabble.com



Knute Snortum
(via Gmail)

On Fri, Mar 18, 2016 at 12:02 PM, Jaime Oliver 
wrote:

> well, some examples of the LSR  have
> "2.18 or higher” so you’d technically miss those if you only search for
> 2.19 examples. I guess there are also a certain number of core features
> that remain compatible through all versions, so there is a fair chance that
> these might work even if the version says 2.16.
>
> best,
>
> J
>
>
>
> On Mar 18, 2016, at 2:57 PM, Kristin Rollins 
> wrote:
>
> Searching with Google tends to be more effective for me in solving my
> issues with learning LilyPond and troubleshooting my work, especially
> with the ability to simply type the query into the address bar of my
> browser. (Though that is after I took the time to go through the
> learning manual and at least review what documentation is available to
> become familiar with it.)
>
> The one thing I have learned, after a couple of instances of finding the
> wrong version's documentation (or multiple versions of the
> documentation): I always start my search with:
>
> lilypond 2.19
>
> and then my search terms. That will usually make the official
> documentation for the proper version come to the top of the search
> results and lower the risk of finding answers that relate to previous
> versions.
>
> Kristin
>
> --
>  Kristin Rollins
>  kris...@verumsolum.com
>  Portsmouth, VA
>
> On Fri, Mar 18, 2016, at 06:44 AM, David Kastrup wrote:
>
> That's one reason why it makes sense to look at the accompanying
> documentation of a LilyPond installation rather than search blindly for
> something on the net (which will frequently deliver outdated information
> and infrequently advance information).
>
>
> ___
> 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: Using Google to find documentation (was Re: naturalize pitches)

[Jaime Oliver]

well, some examples of the LSR  have "2.18 
or higher” so you’d technically miss those if you only search for 2.19 
examples. I guess there are also a certain number of core features that remain 
compatible through all versions, so there is a fair chance that these might 
work even if the version says 2.16. 

best,

J


> On Mar 18, 2016, at 2:57 PM, Kristin Rollins  wrote:
> 
> Searching with Google tends to be more effective for me in solving my
> issues with learning LilyPond and troubleshooting my work, especially
> with the ability to simply type the query into the address bar of my
> browser. (Though that is after I took the time to go through the
> learning manual and at least review what documentation is available to
> become familiar with it.)
> 
> The one thing I have learned, after a couple of instances of finding the
> wrong version's documentation (or multiple versions of the
> documentation): I always start my search with:
> 
> lilypond 2.19
> 
> and then my search terms. That will usually make the official
> documentation for the proper version come to the top of the search
> results and lower the risk of finding answers that relate to previous
> versions.
> 
> Kristin
> 
> -- 
>  Kristin Rollins
>  kris...@verumsolum.com
>  Portsmouth, VA
> 
> On Fri, Mar 18, 2016, at 06:44 AM, David Kastrup wrote:
>> That's one reason why it makes sense to look at the accompanying
>> documentation of a LilyPond installation rather than search blindly for
>> something on the net (which will frequently deliver outdated information
>> and infrequently advance information).
> 
> ___
> 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: naturalize pitches

[David Kastrup]

Jaime Oliver  writes:

> Hi all, 
>
> I am trying to use the code for naturalizing pitches after a
> transposition from the documentation:
> http://www.lilypond.org/doc/v2.19/Documentation/notation/changing-multiple-pitches

Do you see the v2.19 in that link?

> Starting lilypond 2.18.2 [Main-Score.ly]...

Do you see the 2.18 in that message?

If you replace the v2.19 with v2.18 in the link, you'll get
documentation/program matching your version of LilyPond.

That's one reason why it makes sense to look at the accompanying
documentation of a LilyPond installation rather than search blindly for
something on the net (which will frequently deliver outdated information
and infrequently advance information).

-- 
David Kastrup

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

Re: naturalize pitches

[Jaime Oliver]

or you can search blindly because you forgot there is no backward compatibility 
and it is faster and because the best approaches to a problem aren’t always in 
the documentation page and then just remember to switch versions…

thanks!

J


> On Mar 18, 2016, at 6:44 AM, David Kastrup  wrote:
> 
> Jaime Oliver  writes:
> 
>> Hi all, 
>> 
>> I am trying to use the code for naturalizing pitches after a
>> transposition from the documentation:
>> http://www.lilypond.org/doc/v2.19/Documentation/notation/changing-multiple-pitches
> 
> Do you see the v2.19 in that link?
> 
>> Starting lilypond 2.18.2 [Main-Score.ly]...
> 
> Do you see the 2.18 in that message?
> 
> If you replace the v2.19 with v2.18 in the link, you'll get
> documentation/program matching your version of LilyPond.
> 
> That's one reason why it makes sense to look at the accompanying
> documentation of a LilyPond installation rather than search blindly for
> something on the net (which will frequently deliver outdated information
> and infrequently advance information).
> 
> -- 
> David Kastrup


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

naturalize pitches

[Jaime Oliver]

Hi all, 

I am trying to use the code for naturalizing pitches after a transposition from 
the documentation:
http://www.lilypond.org/doc/v2.19/Documentation/notation/changing-multiple-pitches
 


However I get: 

Starting lilypond 2.18.2 [Main-Score.ly]...
Processing 
`/Users/joliver/Documents/PIECES/WSCMS-silbadores/patches/TRIO/LAST-TRIO/take-2/Main-Score.ly'
Parsing.../Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/ly-syntax-constructors.scm:56:23
 : In expression (apply 
(ly:music-function-extract fun) parser ...):
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/ly-syntax-constructors.scm:56:23
 : Wrong number of 
arguments to #
Exited with return code 1.

I am using version 2.18.2-1, with frescobaldi on a mac os x 10.11.2

Any help would be greatly appreciated!

best,

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

Using Google to find documentation (was Re: naturalize pitches)

[Kristin Rollins]

Searching with Google tends to be more effective for me in solving my
issues with learning LilyPond and troubleshooting my work, especially
with the ability to simply type the query into the address bar of my
browser. (Though that is after I took the time to go through the
learning manual and at least review what documentation is available to
become familiar with it.)

The one thing I have learned, after a couple of instances of finding the
wrong version's documentation (or multiple versions of the
documentation): I always start my search with:

lilypond 2.19

and then my search terms. That will usually make the official
documentation for the proper version come to the top of the search
results and lower the risk of finding answers that relate to previous
versions.

Kristin

-- 
  Kristin Rollins
  kris...@verumsolum.com
  Portsmouth, VA

On Fri, Mar 18, 2016, at 06:44 AM, David Kastrup wrote:
> That's one reason why it makes sense to look at the accompanying
> documentation of a LilyPond installation rather than search blindly for
> something on the net (which will frequently deliver outdated information
> and infrequently advance information).

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