Re: Octave control.

Yes, as Paul already answered, Lilypond does exactly what you describe in the example you sent. This is what happens since you used  \relative{...}. In some cases when you have music that mostly stays within a single octave, it may be more convenient to use

Re: Octave control.

The intervals in the image are all going to the nearest option.  You need to mark some of your notes with ' in order (I presume) to convert some of the downward fourths into upward fifths. Paul From: To: Sent: 15/10/2023 19:47 Subject: Octave control. For the init

Octave control.

1. For the initiated this is a simple question but I have Been away from Lilypond for some time. Now when I compile a simple piece of music the control of note range seems to have disappeared. And I get increasing or decreasing octaves - see example. Previously the program remembered where the

Re: Trying to create a two-octave ascending C Major scale using the change Staff example in NR

Kenneth Wolcott > wrote: > > > > Hi; > > > > Starting a new email thread regarding my difficulty in understanding > > how to use the Lilypond \change Staff feature... > > > > I'm trying to create a two-octave ascending C Major scale using the >

Re: Trying to create a two-octave ascending C Major scale using the change Staff example in NR

e Staff feature... > > I'm trying to create a two-octave ascending C Major scale using the > change Staff example in NR. > > https://lilypond.org/doc/v2.22/Documentation/notation-big-page.html#changing-staff-manually > > I'm losing the lower staff. What am I doing wr

Trying to create a two-octave ascending C Major scale using the change Staff example in NR

Hi; Starting a new email thread regarding my difficulty in understanding how to use the Lilypond \change Staff feature... I'm trying to create a two-octave ascending C Major scale using the change Staff example in NR. https://lilypond.org/doc/v2.22/Documentation/notation-big-page

Re: Can I put the F key sign # down one octave? *KeySignature*

> On 30 Jun 2021, at 20:47, Lukas-Fabian Moser wrote: > > So, "three sharps" (but not in modern arrangement) for the two violins, "four > sharps" (which are actually three) for soprano and bass. That's interesting > insofar as today we're basically used to only counting the total number of >

Re: Can I put the F key sign # down one octave? *KeySignature*

On Wed, Jun 30, 2021 at 12:02 PM Lukas-Fabian Moser wrote: > Hi, > > Why is the key sharp even so high on the staff in the first place? Is there a > point to it beside the maybe visually? If not, we will just change it all > around the world I guess! ;) > > I’m not a music historian, so can’t t

Re: Can I put the F key sign # down one octave? *KeySignature*

Hi, Why is the key sharp even so high on the staff in the first place? Is there a point to it beside the maybe visually? If not, we will just change it all around the world I guess! ;) I’m not a music historian, so can’t tell you that. Once a player has some familiarity with key signatures, t

Re: Can I put the F key sign # down one octave? *KeySignature*

> On 30 Jun 2021, at 14:49, darki...@jesusgod-pope666.info wrote: > > , No I don't think so... The Problem I had, and as far as I know my other > friend that started on the Tin Whistle - was to figure out what they in the > first place was. As the # is so far up on the line - you never get t

Re: Can I put the F key sign # down one octave? *KeySignature*

Whatever the case, I can do whatever I want, and if people wanna change it - they can freely do it - everything I make is release for anyone who wanna do whatever with it :P But... Anyway, thanks for your thoughts and spitting in on the topic. - Darkijah

Re: Can I put the F key sign # down one octave? *KeySignature*

, No I don't think so... The Problem I had, and as far as I know my other friend that started on the Tin Whistle - was to figure out what they in the first place was. As the # is so far up on the line - you never get the connection as you don't get to that note before a lot later. I think i

Re: Can I put the F key sign # down one octave? *KeySignature*

> On 27 Jun 2021, at 02:45, darki...@jesusgod-pope666.info wrote: > > If I had just payed more attention to your mail, I went for the link and > tried to figure something out. I should could not sort it out and went for > your post again going to complain :P And there the solution was in the fir

Re: Can I put the F key sign # down one octave? *KeySignature*

.@jesusgod-pope666.info: I really do like it already, gives much more understanding being an octave down on the staff. one could maybe make a ghost # at the normal place, maybe some color coding as well might be helpful... But that would be needed for an individual, each one of them. Mostly only 2

Re: Can I put the F key sign # down one octave? *KeySignature*

ev darki...@jesusgod-pope666.info: > > I really do like it already, gives much more understanding being an octave > down on the staff. one could maybe make a ghost # at the normal place, maybe > some color coding as well might be helpful... But that would be needed for an > indiv

Re: Can I put the F key sign # down one octave? *KeySignature*

I really do like it already, gives much more understanding being an octave down on the staff. one could maybe make a ghost # at the normal place, maybe some color coding as well might be helpful... But that would be needed for an individual, each one of them. Mostly only 2 Sharps are used for

Can I put the F key sign # down one octave? *KeySignature*

way to move the Key Signature sign down one octave? :) I think that would be more understandable to a newcomer overall, and I am always looking for things that can make it easier for beginners like myself. Dearly Regards and Jayshua be with you! :) - In Christ - Darkijah

Re: Current octave in relative mode

Peace be with you, guys...   ;-) The OP's eXample is more complicated but as far as I can tell this is what he's aiming at. Of course, I did some experimenting on my own before asking here on the list. I was aware that the problem only appears if I use my function inside a \relative statement,

Re: Current octave in relative mode

antlists writes: > On 17/05/2020 00:04, David Kastrup wrote: >> antlists writes: >> >>> On 16/05/2020 23:19, David Kastrup wrote: > As I say, I think this function or something similar has made its way > into lilypond proper. >>> What advantage over the solution using make-relative

Re: Current octave in relative mode

On 17/05/2020 00:04, David Kastrup wrote: antlists writes: On 16/05/2020 23:19, David Kastrup wrote: As I say, I think this function or something similar has made its way into lilypond proper. What advantage over the solution using make-relative that I posted do you see here? Because if

Re: Current octave in relative mode

antlists writes: > On 16/05/2020 23:19, David Kastrup wrote: >>> As I say, I think this function or something similar has made its way >>> into lilypond proper. > >> What advantage over the solution using make-relative that I posted do >> you see here? > > Because if I understand the OP correctly

Re: Current octave in relative mode

On 16/05/2020 23:19, David Kastrup wrote: As I say, I think this function or something similar has made its way into lilypond proper. What advantage over the solution using make-relative that I posted do you see here? Because if I understand the OP correctly, what he wants is \resetRelative

Re: Current octave in relative mode

antlists writes: > On 15/05/2020 12:28, antlists wrote: >> There's a function Han Wen wrote for me years ago, that's made its >> way in to standard lilypond. It's probably mentioned in the docu >> about relative mode. Something along the lines of >>   c1  \highlight { c8 d e f g f e d } >>

Re: Current octave in relative mode

proper. Cheers, Wol On 15/05/2020 11:01, Klaus Blum wrote: Hi, I have a function that uses a music expression twice. My problem is: In relative mode, this expression can lead into a different octave. Then the second application of the music expression starts from that new octave. (See the l

Re: Current octave in relative mode

; >> To: "lilypond-user@gnu.org" > >> Cc: > >> Bcc: > >> Date: Fri, 15 May 2020 12:01:06 +0200 > >> Subject: Current octave in relative mode > >> Hi, > >> > >> I have a function that uses a music expression twice.

Re: Current octave in relative mode

Flaming Hakama by Elaine writes: >> From: Klaus Blum >> To: "lilypond-user@gnu.org" >> Cc: >> Bcc: >> Date: Fri, 15 May 2020 12:01:06 +0200 >> Subject: Current octave in relative mode >> Hi, >> >> I have a function that uses a mus

Re: Current octave in relative mode

> > -- Forwarded message -- > From: Klaus Blum > To: "lilypond-user@gnu.org" > Cc: > Bcc: > Date: Fri, 15 May 2020 12:01:06 +0200 > Subject: Current octave in relative mode > Hi, > > I have a function that uses a music expression twice

Re: Current octave in relative mode

Klaus Blum writes: > Hi David, > > That's perfect, thanks a lot! > Cool to know that this doesn't require complicated tweaks and hacks... If you think this isn't a complicated hack, you haven't looked at the source code of make-relative... Its three arguments, by the way, are a list of variable

Re: Current octave in relative mode

Hi David, That's perfect, thanks a lot! Cool to know that this doesn't require complicated tweaks and hacks... Cheers, Klaus

Re: Current octave in relative mode

8 d e f g a b c } Don't quote me on the function name though ... (I needed it for Pennsylvania 6-5-0-0-0 Cheers, Wol On 15/05/2020 11:01, Klaus Blum wrote: Hi, I have a function that uses a music expression twice. My problem is: In relative mode, this expression can lead into a differ

Re: Current octave in relative mode

Klaus Blum writes: > Hi, > > I have a function that uses a music expression twice. > My problem is: > In relative mode, this expression can lead into a different octave. Then > the second application of the music expression starts from that new octave. > (See the la

Current octave in relative mode

Hi, I have a function that uses a music expression twice. My problem is: In relative mode, this expression can lead into a different octave. Then the second application of the music expression starts from that new octave. (See the last two invocations of "\highlight" in the example

\absolute, was Re: Stop Tablature from moving up an octave

elative c' > > > {\song } > > >} Using \relative here, and in this way, is very unwise³. If you want to use \relative, use it in the definition of song, thus: song = \relative c' { e,, … } or song = \relative e, { e … } so that \son

Re: Stop Tablature from moving up an octave

Hi Pierre-Luc, >> NO! Instead, use a transposing clef: > > I guess people (and books) diverge in opinion here. > But I do not write bass parts with \clef "bass_8" neither guitar with > \clef "treble_8". That’s fine, from a visual perspective — just turn off the ClefModifier. The problem I see w

Re: Stop Tablature from moving up an octave

Le sam. 15 févr. 2020 à 10:45, Kieren MacMillan a écrit : > > guitarStaff = \transpose c c' { > > % Here we transpose > NO! Instead, use a transposing clef: I guess people (and books) diverge in opinion here. But I do not write bass parts with \clef "bass_8" neither guitar with \clef "treble_8

Re: Stop Tablature from moving up an octave

Thanks to all for the excellent support an help. It is clear to me now and I have it working properly. Bob

Re: Stop Tablature from moving up an octave

Hi Pierre-Luc, > \version "2.21.0" > > song = { > % here you write the music the > % way it should sound > >| > } Yes. > guitarStaff = \transpose c c' { > % Here we transpose NO! Instead, use a transposing clef: guitarStaff = { \clef "treble_8" \new Voice { \song } } I

Re: Stop Tablature from moving up an octave

Frescobaldi on Ubuntu 18.04. > > > > \version "2.18.2" > > > > song = { > > > > } > > > > \score { > > << > > % \override StringNumber #'transparent = ##t > >\relative c' > > > &

Re: Stop Tablature from moving up an octave

#x27; > > {\song } >} > >\new TabStaff > > {\song} >>> > } Looks to me like you are entering everything an octave too high. From \relative c' the note e, just gives e while the lowest note of a guitar is actually e, . You are aware tha

Stop Tablature from moving up an octave

I am new to Lilypond and can not get Tablature for guitar to work like I think it should. The documentation indicates Lilypond will select the lowest fret and open strings. When I run my example below the tablature selects fret position 12 and not zero for three of the note groups. I want it t

Re: workflow advice: avoiding wrong octave errors?

lent to {f' g' a' b' c'' d'' e''} This way, notes inside the staff would need no "," or "'", and most notes outside would need only a single "," or "'". I think I could keep track of octaves pretty

Re: workflow advice: avoiding wrong octave errors?

Hi Mason, > I thought of that, but my worry is that I'll still make octave errors, > but each will result in one transposed note instead of a transposed > phrase, which might be even less apparent than proofreading. That is a concern… > I also find relative note entry to be m

Re: workflow advice: avoiding wrong octave errors?

Thanks Kieren, On 08/23, Kieren MacMillan wrote: > My primary suggestion: use absolute instead of relative note entry, and you > will never have incorrect octavation again. :) I thought of that, but my worry is that I'll still make octave errors, but each will result in one tran

Re: workflow advice: avoiding wrong octave errors?

Hi Mason, > placing a note in the wrong octave My primary suggestion: use absolute instead of relative note entry, and you will never have incorrect octavation again. :) My secondary suggestion: to make entry fast and super-accurate, use MIDI entry if possible. If you stick with relat

RE: workflow advice: avoiding wrong octave errors?

Sent: Friday, August 23, 2019 1:41 PM To: lilypond-user@gnu.org Subject: workflow advice: avoiding wrong octave errors? I typically make few errors while inputting music. The two most common exceptions are incorrect note durations and placing a note in the wrong octave. The former generally is not

Re: workflow advice: avoiding wrong octave errors?

"Octave checks" occurred to me while I was writing. I should have thought to RTFM before sending... http://lilypond.org/doc/v2.18/Documentation/notation/changing-multiple-pitches#octave-checks Mason On 08/23, ma...@masonhock.com wrote: > I typically make few errors while inputti

workflow advice: avoiding wrong octave errors?

I typically make few errors while inputting music. The two most common exceptions are incorrect note durations and placing a note in the wrong octave. The former generally is not a problem, because bar checks catch the error and tell me where to look. However, the latter slips by more easily. If

Re: Octave shifts in polyphonic setting

On 25.09.2018 21:13, Jogchum Reitsma wrote: Hi, When entering a piece of music with some one-, some two- and some three-voiced bars, quite often notes in previous bars go up or down an octave, when entering new bars. Restoring this from the first bars affected by adding or deleting

Re: Octave shifts in polyphonic setting

ssage- From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Jogchum Reitsma Sent: Tuesday, September 25, 2018 12:13 PM To: lilypond-user Subject: Octave shifts in polyphonic setting Hi, When entering a piece of music with some one-, some two- and some t

RE: Octave shifts in polyphonic setting

-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Jogchum Reitsma Sent: Tuesday, September 25, 2018 12:13 PM To: lilypond-user Subject: Octave shifts in polyphonic setting Hi, When entering a piece of music with some one-, some two- and some three-voiced bars, quite often

Re: Octave shifts in polyphonic setting

octave, when entering new bars. Restoring this from the first bars affected by adding or deleting apostrophes or comma's, sometimes lead again to side effects. Rather frustrating... Is there a way to prevent this? Use \fixed note entry instead of \relative . It stops the notes being depende

Re: Octave shifts in polyphonic setting

absolute, myself; every pitch specifies its octave and they don't change depending on the cutting and pasting of other notes. I find that the annoyance of having to debug this kind of thing in relative mode outweighs the convenience of leaving out octaves on some pitches. -- Matthew Skala ms

Re: Octave shifts in polyphonic setting

Jogchum Reitsma writes: > Hi, > > When entering a piece of music with some one-, some two- and some > three-voiced bars, quite often notes in previous bars go up or down an > octave, when entering new bars. > Restoring this from the first bars affected by adding or deletin

Octave shifts in polyphonic setting

Hi, When entering a piece of music with some one-, some two- and some three-voiced bars, quite often notes in previous bars go up or down an octave, when entering new bars. Restoring this from the first bars affected by adding or deleting apostrophes or comma's, sometimes lead again to

Re: Is there a short way of forcing a particular octave?

On Fri 23 Dec 2016 at 11:02:59 (+0100), Gianmaria Lari wrote: > On 23 December 2016 at 10:39, ptoye wrote: > > Not exactly, I think. In a chord \relative controls the first note as typed. Quite right, my mistake, late nights... s/top/first/ [saves me a post] > > [...] I really didn't mean to st

Re: Is there a short way of forcing a particular octave?

On 23 December 2016 at 10:39, ptoye wrote: > [...] I really didn't mean to start a theological discussion about how one > should > type in music, but obviously some people feel much stronger about it than I > do. There are three ways of telling LilyPond what the pitch of a particular > note shoul

Re: Is there a short way of forcing a particular octave?

d and > libraries harder to maintain. > > I even use \resetRelativeOctave at the beginning of a \relative block, just > for consistency. It is much easier to deal with \relative mode when you > only > have to look to the line directly above the music to see the octave > setting,

Re: Is there a short way of forcing a particular octave?

-- View this message in context: http://lilypond.1069038.n5.nabble.com/Is-there-a-short-way-of-forcing-a-particular-octave-tp198225p198397.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http

Re: Is there a short way of forcing a particular octave?

t the beginning of a \relative block, just for consistency. It is much easier to deal with \relative mode when you only have to look to the line directly above the music to see the octave setting, rather than the beginning of a code block. -- View this message in context: http://lilypond.10690

Re: Is there a short way of forcing a particular octave?

to figure out at a quick glance how the last c > relates to the first. Are they the same octave? Is the last c higher than the > first? Lower? By how much?? And, of course, the further apart two notes are > in the code — that is, the more notes there are intervening — the more > dif

Re: Is there a short way of forcing a particular octave?

Hi again, >> I find \relative mode quite helpful in orchestral works because it lends >> itself very well to copy-n-paste octave doublings. Trying to do that in >> absolute mode and needing to edit tens of 's and ,s after you copy a >> line that needs to be tra

Re: Is there a short way of forcing a particular octave?

Hi, > I find \relative mode quite helpful in orchestral works because it lends > itself very well to copy-n-paste octave doublings. Trying to do that in > absolute mode and needing to edit tens of 's and ,s after you copy a > line that needs to be transposed by an octave is quite

Re: Is there a short way of forcing a particular octave?

n the kind of music you're using it for. If you're writing modern stuff that rarely sticks to traditional melody lines, then \relative mode is probably not for you, because its determination of octave appears to be designed around traditional melody lines. But if you're writing highly m

Re: Is there a short way of forcing a particular octave?

Hi David, > Do you mean things like > \relative { } > ? Yes. Your example brings up another major limitation (IMO) to \relative mode: It is essentially impossible to figure out at a quick glance how the last c relates to the first. Are they the same octave? Is the last c higher

Re: Is there a short way of forcing a particular octave?

On Wed 21 Dec 2016 at 20:43:20 (-0500), Kieren MacMillan wrote: > Hi David, > > > I haven't noticed any effect with polyphony: the octavation of the > > next note in the source is always determined by the previous one. > > Cut and paste one section and move it later — it has a better than 50/50

Re: Is there a short way of forcing a particular octave?

Hi David, > I haven't noticed any effect with polyphony: the octavation of the > next note in the source is always determined by the previous one. Cut and paste one section and move it later — it has a better than 50/50 chance of being wrong. Change the order of voices — it has a better than 50/

Re: Is there a short way of forcing a particular octave?

On Wed 21 Dec 2016 at 14:22:28 (-0800), Nathan Ho wrote: > On 2016-12-21 11:55, Kieren MacMillan wrote: > >Hi David, > > > >>I can't see the point in avoiding any methodology > >>that makes things easier and more reliable. > > > >I agree 100%. Which is exactly why I abandoned \relative and use only

Re: Is there a short way of forcing a particular octave?

Hi Nathan, > I also stopped using \relative a few years ago (I think it was in response to > one of your posts here). Aw, shucks… ;) > No regrets here. Whew. > it gets in the way when engraving anything with chords or polyphony. Also, if > you break your music into sections and assign them

Re: Is there a short way of forcing a particular octave?

On 21 December 2016 at 23:22, Nathan Ho wrote: > [...] > I also stopped using \relative a few years ago (I think it was in response to one of your posts here). No regrets here. > > It's alright for simple monophonic melodies, but it gets in the way when engraving anything with chords or polyphony.

Re: Is there a short way of forcing a particular octave?

On 2016-12-21 11:55, Kieren MacMillan wrote: Hi David, I can't see the point in avoiding any methodology that makes things easier and more reliable. I agree 100%. Which is exactly why I abandoned \relative and use only \absolute. ;) I also stopped using \relative a few years ago (I think i

Re: Is there a short way of forcing a particular octave?

On 21 December 2016 at 20:47, David Wright wrote: > > I don't understand "annoying"/"unannoying" mistakes, I'm not an expert user. I have used relative and absolute entry and with relative I makes mistakes more frequently and spend much time fixing it. I personally consider these mistakes annoy

Re: Is there a short way of forcing a particular octave?

Hi David, > I can't see the point in avoiding any methodology > that makes things easier and more reliable. I agree 100%. Which is exactly why I abandoned \relative and use only \absolute. ;) YMMV, of course… but as soon as my use of Lilypond advanced beyond simple songs (e.g., I’m now regula

Re: Is there a short way of forcing a particular octave?

On Tue 20 Dec 2016 at 23:49:16 (+0100), Gianmaria Lari wrote: > Ciao Peter, > > I know this is a totally different story but I suggest also to give a try > to avoid the "\relative" and to use absolute octave entry. It takes some > weeks to get used but in my opinion it is

Re: Is there a short way of forcing a particular octave?

Hi All, On 21 December 2016 at 09:49, Gianmaria Lari wrote: > I suggest also to give a try to avoid the "\relative" and to use absolute > octave entry. > ​+2 :-) I used to use relative and found in large scores that when I went back to correct things large sections sh

Re: Is there a short way of forcing a particular octave?

Hi all, > On Dec 20, 2016, at 5:49 PM, Gianmaria Lari wrote: > I suggest also to give a try to avoid the "\relative" and to use absolute > octave entry. +1 Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmil

Re: \fixed absolute octave entry without brackets

On 21.12.2016 00:57, Simon Albrecht wrote: On 21.12.2016 00:23, Gianmaria Lari wrote: Is there any way to avoid this additional bracket? It’s funny how for the second time in 7 hours I get to reply with \resetRelativeOctave Oh man, I need to go to sleep. Obviously, since you’re using absol

Re: \fixed absolute octave entry without brackets

On 21.12.2016 00:23, Gianmaria Lari wrote: Is there any way to avoid this additional bracket? It’s funny how for the second time in 7 hours I get to reply with \resetRelativeOctave :-) I already made a patch to document it in the NR. Best, Simon

\fixed absolute octave entry without brackets

Few months ago I switched from relative to absolute octave entry. In the rare cases I need to write very high or very low octave notes and consequently I need to write too much single quote ( ' ) or comma ( , ) I use the "\fixed" function that I just discovered (before I was us

Re: Is there a short way of forcing a particular octave?

Ciao Peter, I know this is a totally different story but I suggest also to give a try to avoid the "\relative" and to use absolute octave entry. It takes some weeks to get used but in my opinion it is more easy to manage code in this way. IMHO "\relative" is too much prone

Re: Is there a short way of forcing a particular octave?

On 20.12.2016 19:04, Peter Toye wrote: Pity it isn't in the text part of either the learning or notation reference manual. You have to know about it in order to find it. That needs to be changed. :-) Best, Simon ___

Re: Is there a short way of forcing a particular octave?

.ptoye.com - Tuesday, December 20, 2016, 5:15:36 PM, you wrote: > On 20.12.2016 17:39, Peter Toye wrote: >> Is there a short way of forcing a particular octave? I tend to enter >> my music using the \relative notation. I want make sure, especially >> after a complicated se

Re: Is there a short way of forcing a particular octave?

On 20.12.2016 17:39, Peter Toye wrote: Is there a short way of forcing a particular octave? I tend to enter my music using the \relative notation. I want make sure, especially after a complicated set of new voices or a frequently-used music pattern that's been put into a variable, tha

Is there a short way of forcing a particular octave?

I tend to enter my music using the \relative notation. I want make sure, especially after a complicated set of new voices or a frequently-used music pattern that's been put into a variable, that the next note will be in the correct octave. I know that I can do an \octaveCheck but this thro

Re: music patterns and octave

f-the-NM" { c' geses } { \relative { c' geses } } { \naturalizeMusic \relative { c' geses } } { \relative \naturalizeMusic { c' geses } } { \relative c' { c geses } } { \naturalizeMusic \relative c' { c geses } } { \relative c' \naturalizeMusic { c geses } } rel

Re: music patterns and octave

I'm sorry I have not been clear in my old messages, hope my last one it is clearer. Regarding: \relative c' >{ >... > \setOctave c' > \relative c' \changePitch \rhythmPattern { ... > > I'm not even sure of how LP interprets that last \relative. > > Last "relative" applies only t

Re: music patterns and octave

Gianmaria Lari writes: > Thank you David for your help. I think the behaviour of "\relative" and > "\resetRelativeOctave" are clear. If the latter is not deprecated IMHO > there are cases where it can be very useful. That one you mention > (preventing up > and

Re: music patterns and octave

Ciao Patric, to use "changePitch.ly" with Lilypond 2.19 you need to convert it. In case you need you can check at the end of this old thread: http://lilypond.1069038.n5.nabble.com/changepitch-compilation-error-td187658.html g. ___ lilypond-user mailing

Re: music patterns and octave

Thank you David for your help. I think the behaviour of "\relative" and "\resetRelativeOctave" are clear. If the latter is not deprecated IMHO there are cases where it can be very useful. That one you mention (preventing up and down octave when changing code) it is just one. F

Re: music patterns and octave

On Wed 09 Mar 2016 at 07:56:21 (-0600), Patrick Karl wrote: > > > Message: 1 > > Date: Wed, 9 Mar 2016 01:07:47 +0100 > > From: Gianmaria Lari > > To: lilypond-user > > Subject: Re: music patterns and octave > > > > > > Then please have a lo

Re: music patterns and octave

> Message: 1 > Date: Wed, 9 Mar 2016 01:07:47 +0100 > From: Gianmaria Lari > To: lilypond-user > Subject: Re: music patterns and octave > > > Then please have a look to the code I *would* like to write to obtain it. > Do you know if does exist anything similar to &

Re: music patterns and octave

;ve had is to use \resetRelativeOctave but I can't quite see the necessity of using that in most static music. OTOH it could be very useful if you were composing the middle section of a work in LP and needed to prevent a later section from jumping up and down an octave each time you changed any

Re: music patterns and octave

Thank you Patrick, this works exactly as I expected. Why it is not documented? Can we use it or do we risk that it will deprecated? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: music patterns and octave

Dear Carl, thank you for pointing me out the octave check, didn't know it and now I'm testing it (even if it looks it doesn't work as I need). Thanks, g. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/m

Re: music patterns and octave

Am 09.03.2016 09:52, schrieb Blöchl Bernhard: Obviously does changePitch.ly not understand the construct \tuplet 3/2 { a8 a a }. The use of patterns is completely wrong. Check the documentation how to use the construct correctly. http://gillesth.free.fr/Lilypond/changePitch/changePitch-doc.pd

Re: music patterns and octave

Obviously does changePitch.ly not understand the construct \tuplet 3/2 { a8 a a }. \include "changePitch.ly" rhythmPattern = {a16 %\tuplet 3/2 { a8 a a } a16 a8 a4 a4} % a complex rhythm scoreViolinI = \relative c' { % \setOctave c' %this command is just an example and it does not exist! \c

Re: music patterns and octave

> \ > Message: 2 > Date: Wed, 9 Mar 2016 01:20:47 +0100 > From: Gianmaria Lari > To: Thomas Morley > Cc: lilypond-user > Subject: Re: music patterns and octave > > Do you know if does exist something to set > the absolute "octave"? > g. %%% How abo

Re: music patterns and octave

herPitchOctave, this is similar to what I was >thinking except that the parameter is not the "octave" but the "offset" >related to the current octave. Do you know if does exist something to set >the absolute "octave"? >g. > > > You can use the e

Re: music patterns and octave

is not the "octave" but the "offset" related to the current octave. Do you know if does exist something to set the absolute "octave"? g. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: music patterns and octave

Ciao David, let's put it in another way. Have a look to the attached image and please suggest me how you would write the code to generate it. Then please have a look to the code I *would* like to write to obtain it. Do you know if does exist anything similar to "\setOctave"? Do you see any logica

Re: music patterns and octave

x27;ve no idea about changePitch, it's not in the source. Please post (read: attach) the code or a link to it. (3) You may be looking for make-relative, for an example see: http://lsr.di.unimi.it/LSR/Item?id=465 In your use-case maybe: \version "2.19.36" pat = \relative c' {

  1   2   3   >