Re: Auto-transposition

Thomas Morley writes: > 2017-12-18 16:08 GMT+01:00 Kieren MacMillan : > >> I suppose I could use single variables more if Lilypond had better >> "at runtime" methods of reusing material (e.g., inline variable >> definition) > > Have a look

Re: Auto-transposition

Hi Harm, > Have a look at > https://lilypondforum.de/index.php/topic,195.msg1231.html#msg1231 Ooh! It even works outside of the parent variable (as would be absolutely necessary in my usage): %%% SNIPPET BEGINS \version "2.19.80" tee = #(define-music-function (name mus) (string? ly:music?)

Re: Auto-transposition

2017-12-18 16:08 GMT+01:00 Kieren MacMillan : > I suppose I could use single variables more if Lilypond had better "at > runtime" methods of reusing material (e.g., inline variable definition) Have a look at

Re: Auto-transposition

On 18/12/17 15:08, Kieren MacMillan wrote: Hi Saul, \resetRelativeOctave belongs IMO always as part of the definition of a music expression, ideally on the line directly preceding note entry. Agreed. Until it's a repeated phrase, but not necessarily the same octave. iirc (as I said it's a

Re: Auto-transposition

Hi David, > This is, in part, a result of our documentation being so granular. True. > Putting it another way: I doubt that many of the issues with \relative rear > their heads in the examples in the docs. So true. And thus newbies aren't really [explicitly] taught how to use relative mode

Re: Auto-transposition

Hi Saul, > \resetRelativeOctave belongs IMO always as part of the definition of a music > expression, ideally on the line directly preceding note entry. Agreed. > Personally, I think it is preferable to define all of the music for each > context by explicitly typing it in a single variable.

Re: Auto-transposition

I would highly recommend against this type of coding style. \resetRelativeOctave belongs IMO always as part of the definition of a music expression, ideally on the line directly preceding note entry. Personally, I think it is preferable to define all of the music for each context by explicitly

Re: Auto-transposition

> Subject: Re: Re: Auto-transposition > > By the way, whoever is working on the Changes document for upcoming 2.20, > don't forget to mention about \fixed! > >/Mats > I volunteered to do this, so I will make sure to work on describing this feature. > > I d

Re: Auto-transposition

Flaming Hakama by Elaine writes: > On Fri, Dec 15, 2017 at 7:57 AM, David Kastrup wrote: > >> Flaming Hakama by Elaine writes: >> >> > Actually, I think it had to do with midi output for bass clarinet. The >> > sample I used

Re: Auto-transposition

On 15/12/17 17:48, Flaming Hakama by Elaine wrote: > > Actually, I think it had to do with midi output for bass > clarinet. The > > sample I used was not transposed the octave, and I had to > compensate by > > transposing the music down. > > According to Wikipedia, bass

Re: Auto-transposition

On Fri, Dec 15, 2017 at 7:57 AM, David Kastrup wrote: > Flaming Hakama by Elaine writes: > > > David Kastrup writes: > > > >> Flaming Hakama by Elaine writes: > >> > >>> And the behavior of \relative that is

Re: Auto-transposition

On Fri 15 Dec 2017 at 15:52:28 (+), Wols Lists wrote: > On 15/12/17 13:45, David Wright wrote: > > On Fri 15 Dec 2017 at 10:02:19 (+), Wols Lists wrote: > >> On 15/12/17 06:20, Saul Tobin wrote: > >>> Relative mode makes perfect sense if you're entering music that cares > >>> mainly about

RE: Auto-transposition

> Hi List, > > I have used Lilypond for a few years now. I (almost) always use > \relative and I have never had trouble with it. Indeed, as a lay > person, I have no idea which octave > c'4 d' e' f' g'1 > is – I know I could look it up, but it is certainly not in my head. So what reference

Re: Auto-transposition

Flaming Hakama by Elaine writes: > David Kastrup writes: > >> Flaming Hakama by Elaine writes: >> >>> And the behavior of \relative that is weirdest: >>> >>> * The octave of \relative is lowered when used with bass clef. >>>

Re: Auto-transposition

On 15/12/17 13:45, David Wright wrote: > On Fri 15 Dec 2017 at 10:02:19 (+), Wols Lists wrote: >> On 15/12/17 06:20, Saul Tobin wrote: >>> Relative mode makes perfect sense if you're entering music that cares >>> mainly about the relationship between notes within a phrase (i.e. most >>>

Re: Auto-transposition

On Dec 15, 2017 12:59 AM, "David Kastrup" wrote: David Kastrup writes: > Flaming Hakama by Elaine writes: > >> And the behavior of \relative that is weirdest: >> >> * The octave of \relative is lowered when used with bass clef. >> >>

Re: Auto-transposition

writes: > Hi List, > > I have used Lilypond for a few years now. I (almost) always use > \relative and I have never had trouble with it. Indeed, as a lay > person, I have no idea which octave > c'4 d' e' f' g'1 > is – I know I could look it up, but it is certainly not in my

Re: Auto-transposition

Kieren MacMillan writes: > Hi all, > > Mats wrote: >> By the way, whoever is working on the Changes document for upcoming >> 2.20, don't forget to mention about \fixed! > > +1 2.19.22 apparently. I'd have pegged it at 2.18 already. -- David Kastrup

RE: Auto-transposition

or no formal musical training, I think \relative is the best way to go – and I selfishly think that the documentation should be written for people such as me. Regards, Mogens From: Kieren MacMillan Sent: December 15, 2017 7:28 To: Lilypond-User Mailing List Cc: Mats Bengtsson Subject: Re: Auto

Re: Auto-transposition

Hi all, Mats wrote: > By the way, whoever is working on the Changes document for upcoming 2.20, > don't forget to mention about \fixed! +1 David W wrote: > Just use \relative early. The fact that this works like it does is further evidence that \relative is not sufficiently intuitive. I'm

Re: Re: Auto-transposition

On 2017-12-15 13:30, Ralph Palmer wrote: Greetings - Just a reminder and note: I have been using \relative for years and have been quite happy with it. Perhaps my situation is fairly unique. I transcribe a lot of fiddle tunes, then transpose them down an octave and into alto clef. Using

Re: Auto-transposition

On Fri 15 Dec 2017 at 10:02:19 (+), Wols Lists wrote: > On 15/12/17 06:20, Saul Tobin wrote: > > Relative mode makes perfect sense if you're entering music that cares > > mainly about the relationship between notes within a phrase (i.e. most > > music). IMO absolute mode might be easier from

Re: Auto-transposition

On Thu, Dec 14, 2017 at 5:04 PM, Neo Anderson wrote: > Dear All, > > Anyway, I'm thankful you've taken your time to solve my problem. > > On Thursday, December 14, 2017, 1:29:22 AM GMT+1, Kieren MacMillan < > kieren_macmil...@sympatico.ca> wrote: > > > Hi David, > > >>

Re: Auto-transposition

On 15/12/17 06:20, Saul Tobin wrote: > Relative mode makes perfect sense if you're entering music that cares > mainly about the relationship between notes within a phrase (i.e. most > music). IMO absolute mode might be easier from the perspective of the > software, but it's not how most musicians

Re: Auto-transposition

David Kastrup writes: > Flaming Hakama by Elaine writes: > >> And the behavior of \relative that is weirdest: >> >> * The octave of \relative is lowered when used with bass clef. >> >> The fix for the clef issue is to use a \transpose when you use it

Re: Auto-transposition

Flaming Hakama by Elaine writes: > And the behavior of \relative that is weirdest: > > * The octave of \relative is lowered when used with bass clef. > > The fix for the clef issue is to use a \transpose when you use it with bass > clef. That one is nonsense.

Re: Auto-transposition

From: Flaming Hakama by Elaine <ela...@flaminghakama.com> > Subject: Re: Auto-transposition It was pointed out to me that this claim is untrue: > And the behavior of \relative that is weirdest: > > * The octave of \relative is lowered when used with bass clef. > &

Re: Auto-transposition

On 15 December 2017 at 07:20, Saul Tobin wrote: > Reading your example, it seems to me that the "FAIL" is caused by the > hypothetical user misunderstanding the semantics of relative mode. Using > relative mode without explicitly defining what pitch the phrase is

Re: Auto-transposition

Reading your example, it seems to me that the "FAIL" is caused by the hypothetical user misunderstanding the semantics of relative mode. Using relative mode without explicitly defining what pitch the phrase is meant to be relative to is unreadable and prone to break. If it were written properly,

Re: Auto-transposition

> -- Forwarded message -- > From: Neo Anderson <sebulb...@yahoo.com> > To: Lilypond-User Mailing List <lilypond-user@gnu.org> > Subject: Re: Auto-transposition > ... > >> For future list-readers: Using absolute and fixed entry modes all

Re: Auto-transposition

Hi, > it's really hard to "cease bringing any questions about \relative to the > list" if one of the very the first > things you learn about Lilypond is \relative mode - it certainly was mine > experience with all the official > documentation. I agree 100%. Don't worry about your question(s) —

Re: Auto-transposition

Hi David, >> Because my only goal was to clarify for future readers of the list that >> "manipulations on stuff" are not the only thing that can cause headaches. > I failed to see how cut and paste differed from manipulations on stuff. I think of "manipulations on stuff" as being foo = { stuff

Re: Auto-transposition

On Wed 13 Dec 2017 at 15:15:14 (-0500), Kieren MacMillan wrote: > Hi David, > > >> … and if you don't take extra care when simply cutting and pasting, etc. > >> etc. etc. > > > > Yes, so I'm not sure why you cut the helpful lines above the ones > > you quoted from my post (that were not my

Re: Auto-transposition

Hi David, >> … and if you don't take extra care when simply cutting and pasting, etc. >> etc. etc. > > Yes, so I'm not sure why you cut the helpful lines above the ones > you quoted from my post (that were not my words, however). Because my only goal was to clarify for future readers of the

Re: Auto-transposition

On Wed 13 Dec 2017 at 12:06:24 (-0500), Kieren MacMillan wrote: > Hi all, > > > Kieran is correct relative pitch entry can cause headaches > > if you start doing manipulations on stuff. > > … and if you don't take extra care when simply cutting and pasting, etc. etc. > etc. Yes, so I'm not

Re: Auto-transposition

Hi all, > Kieran is correct relative pitch entry can cause headaches > if you start doing manipulations on stuff. … and if you don't take extra care when simply cutting and pasting, etc. etc. etc. Cheers, Kieren. Kieren MacMillan, composer ‣ website:

Re: Auto-transposition

On 12/13/2017 11:54 AM, David Wright wrote: I prefer relative as a pitch entry for ease and speed. Kieran is correct relative pitch entry can cause headaches if you start doing manipulations on stuff. Agreed; if definitions like *foo = \relative { stuff in notemode ... } * are used, then

Re: Auto-transposition

On Tue 12 Dec 2017 at 22:00:47 (-0500), Shane Brandes wrote: > Frescobaldi has a neat little tool to convert from relative to absolute pitch. … and AIUI the same tool is available as a standalone in ly, aka python-ly/python3-ly/…. > I prefer relative as a pitch entry for ease and speed. > Kieran

Re: Auto-transposition

Frescobaldi has a neat little tool to convert from relative to absolute pitch. I prefer relative as a pitch entry for ease and speed. Kieran is correct relative pitch entry can cause headaches if you start doing manipulations on stuff. regards, Shane On Tue, Dec 12, 2017 at 5:48 PM, David Wright

Re: Auto-transposition

On Tue 12 Dec 2017 at 20:32:34 (+0100), Simon Albrecht wrote: > On 12.12.2017 20:30, Shevek wrote: > >The alternative is to use \relative {} but to use \resetRelativeOctave > >religiously before every phrase, even the first one in a block. I find that > >more natural for composing, personally. >

Re: Auto-transposition

On 12.12.2017 20:30, Shevek wrote: The alternative is to use \relative {} but to use \resetRelativeOctave religiously before every phrase, even the first one in a block. I find that more natural for composing, personally. I find that this has the disadvantage of not checking the notes

Re: Auto-transposition

> But as a user of Lilypond for over fifteen years, I *will* recommend that you consider avoiding relative entry mode — using absolute mode (and, when appropriate, \fixed) will like save you headaches (like the one you're encountering right now) in both the short and long term. The alternative

Re: Auto-transposition

Hi Neo, > I'm new to Lilypond, coming over from a commercial program. Welcome! > The issue: > I seem to get measures auto-transposed one by one. > I have one bar of music, then the second one gets transposed one octave > higher, the next one even one octave higher, and so on. > > Without

Re: Auto-transposition

On Sun 10 Dec 2017 at 20:37:03 (+), Neo Anderson wrote: > Hi, > I'm new to Lilypond, coming over from a commercial program. Please, bear with > me as I'm still learning. > The issue: > I seem to get measures auto-transposed one by one. > I have one bar of music, then the second one gets

Re: Auto-transposition

Neo Anderson writes: > I'm new to Lilypond, coming over from a commercial program. > Please, bear with me as I'm still learning. > > The issue: > > I seem to get measures auto-transposed one by one. I have one bar of > music, then the second one gets transposed one octave

Auto-transposition

Hi, I'm new to Lilypond, coming over from a commercial program. Please, bear with me as I'm still learning. The issue: I seem to get measures auto-transposed one by one. I have one bar of music, then the second one gets transposed one octave higher, the next one even one octave higher, and so