lol sorry David - I didn't connect the dots with being able to just use the
"*" and the meter following :)
Thanks guys!
Ben
David Kastrup wrote
> Jay Anderson <
> horndude77@
> > writes:
>
>> On Mon, Mar 11, 2013 at 10:09 PM, SoundsFromSound
>> <
> soundsfromsound@
> > wrote:
>>> But, how
Jay Anderson writes:
> On Mon, Mar 11, 2013 at 10:09 PM, SoundsFromSound
> wrote:
>> But, how do you get full measure rests to show up? I seem to only
>> get them
>> to work using "R1" if the meter is 4/4, etc.
>>
>> But 3/4 time and other variants show incorrectly when I render/engrave.
>> Ple
Sarah k Alawami writes:
> Ok. I suck at reading staff lines. I come from braille music where th
> eoctive signs are given to me and I sing or play badly the correct
> pitches based on the octave mark.
You don't need to use \relative if you are more comfortable with
absolute pitches.
--
David K
On Mon, Mar 11, 2013 at 10:09 PM, SoundsFromSound
wrote:
> But, how do you get full measure rests to show up? I seem to only get them
> to work using "R1" if the meter is 4/4, etc.
>
> But 3/4 time and other variants show incorrectly when I render/engrave.
> Please see the GIF attached.
> I am ce
Hi all,
I'm stumped. I've read the documentation (back when I was using 2.14 I
remember I wondered this same thing)
http://lilypond.org/doc/v2.14/Documentation/notation/writing-rests#full-measure-rests
But, how do you get full measure rests to show up? I seem to only get them
to work using "R1"
Hi Sarah.
You need a midi block which then needs to be in a score block.
\version "2.16.2"
\score {
\new Staff
\relative c' {
\key d\minor
\time 3/2
\set Staff.midiInstrument = #"Acoustic Grand"
2 |
4 8 2 |
}
\midi {}
\layout {}
}
On 12/03/2013 2:31 PM, Sarah k Alawami wrote
I decided to change threads to make the list archives more clean *smiles* Ok.
now that I have the bar checks sorted at least for these 4 measures and I"ll
stop there for tonight, how do I render it as a midi so I can hear if I"m right
int he octaves or not. I want to do this until I'm comfortabl
Cool. it worked! Now why did the midi file not create? only the pdf. I don't'
want to move on unless I know my octaves are correct. in the right hand
anyways. lol!
Thanks and be blessed.
On Mar 11, 2013, at 8:09 PM, wjm wrote:
> Hi,
> If you move the opening curly brace to below the \relat
>> The contrast is not strong enough if you are viewing the image from
>> a greater distance. As it is, it looks irritating to my eye.
>
> Agreed ― the "lighter" chosen here is insufficiently light.
> However, the concept is one I'm interested in exploring.
Mhmm. Your suggestion of handling on
Oh crap! Ok! Why oh why did I not think of that! Ok. I could kick myself. but
I'll do that later lol! Now back to work, I hope.
On Mar 11, 2013, at 7:55 PM, Graeme Lee wrote:
> Hi Sarah.
>
> notes and key/time signature should follow the \relative c' in a block.
> Everything is being reset w
Hi Sarah.
notes and key/time signature should follow the \relative c' in a block.
Everything is being reset with the new staff block.
Hope this helps!
Graeme
On 12/03/2013 12:13 PM, Sarah k Alawami wrote:
Hello. I have 1 bar check failing at what it says is at 1/2
I looked at the second
Hi,
If you move the opening curly brace to below the \relative line
and remove the \new Staff line altogether the result should compile with
no bar-check errors and no, possibly unwanted, empty staff lines.
The altered result is below.
I hope this helps.
Regards
Bill
\relative c'
{
\key d\minor
Yeah. Here is the log.
I already know I don't have a version statement in lol! This is starting after
the version statement error which I already know about.
warning: no music found in score
warning: no music found in score
Interpreting music...
/Users/SA/Desktop/piano reduction 03-11-2013.ly:
On 12/03/13 12:13, Sarah k Alawami wrote:
Hello. I have 1 bar check failing at what it says is at 1/2
I looked at the second beat of the first measure and the cord is still a half
note. the time is 3/2 Here is my .li file
Note that I did not even attempt to put it in a piano staff first.
Hello. I have 1 bar check failing at what it says is at 1/2
I looked at the second beat of the first measure and the cord is still a half
note. the time is 3/2 Here is my .li file
piano reduction 03-11-2013.ly
Description: Binary data
Note that I did not even attempt to put it in a piano s
Ok. I suck at reading staff lines. I come from braille music where th eoctive
signs are given to me and I sing or play badly the correct pitches based on the
octave mark.
I'll try and give this mental thing a go since I bass in treble anyways around
middle c so that might or might not help. l
On Mon, Mar 11, 2013 at 7:55 PM, Werner LEMBERG wrote:
>
>> This reminds me of an idea i had: make stafflines under rests grey,
>> to make it immediately obvious where an instrument is resting (see
>> attached - obviously a bigger example would demonstrate this idea
>> better, but i don' have one)
Hi Werner,
> The contrast is not strong enough if you are viewing the image from a greater
> distance.
> As it is, it looks irritating to my eye.
Agreed — the "lighter" chosen here is insufficiently light.
However, the concept is one I'm interested in exploring.
Cheers,
Kieren.
> This reminds me of an idea i had: make stafflines under rests grey,
> to make it immediately obvious where an instrument is resting (see
> attached - obviously a bigger example would demonstrate this idea
> better, but i don' have one). How do you like it?
Well, I don't like it. The contrast
Klaus Föhl writes:
> Olivier Biot wrote:
>> If no hyphen is needed, then write "lecker". Otherwise write "lek-ker".
>
> A manually written hyphen as in lek-ker looks different to lek -- ker,
> and then there is the alignment difference when writing lecker _
>
>> On a side note, I didn't know thi
Olivier Biot wrote:
> If no hyphen is needed, then write "lecker". Otherwise write "lek-ker".
A manually written hyphen as in lek-ker looks different to lek -- ker,
and then there is the alignment difference when writing lecker _
> On a side note, I didn't know this German hyphenation variant.
Alexander Kobel wrote:
> I think Klaus did not ask for forcing the hyphen to be visible,
> or forcing it to be hidden, but instead choose the letters
> depending on whether the hyphen appears or not in that place
> (with automatic deduction how cramped the space is).
Correct. Nevertheless if a for
- Original Message -
From: "Karim Haddad"
To:
Sent: Monday, March 11, 2013 3:32 PM
Subject: documentation system
Hi,
Can somebody tell me what is the documentation system lilypond uses for
it's
HTML and pdf generation? Is it Texinfo, docbook or Latex ?
THanx
K
http://lilypond.o
Karim Haddad writes:
> Hi,
>
> Can somebody tell me what is the documentation system lilypond uses
> for it's HTML and pdf generation? Is it Texinfo, docbook or Latex ?
Texinfo.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
Hi,
Can somebody tell me what is the documentation system lilypond uses for it's
HTML and pdf generation? Is it Texinfo, docbook or Latex ?
THanx
K
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-u
On Mon, Mar 11, 2013 at 8:56 AM, David Nalesnik wrote:
[...]
> In any case, I still am passing the grob to the callback function:
>
> #(define (path-gliss handle)
> (lambda (grob)
> [...]
>
> BTW, I could also have written the above as follows:
>
> #(define ((path-gliss handle) grob)
>
Perh
Hi Janek,
> This reminds me of an idea i had: make stafflines under rests grey, to
> make it immediately obvious where an instrument is resting (see
> attached - obviously a bigger example would demonstrate this idea
> better, but i don' have one). How do you like it?
I was considering trying th
Hi,
On Mon, Mar 11, 2013 at 1:49 PM, Kieren MacMillan
wrote:
> Hi Jan-Peter (and anyone else still interested in this thread):
>
> In the end, the conductor of my chamber opera asked to have the bar lines
> solid for all measures, but 50% grey and slightly thicker than default as the
> "baselin
Hi Rama,
On Mon, Mar 11, 2013 at 12:06 AM, Rama Gottfried
wrote:
> Thanks David -- This is great, I can almost start with the score now.
>
> Glad to hear it!
> I was (am still a bit) unclear about how the grob gets passed to the
> callback function.
>
> interesting that the grob is still availa
Kieren MacMillan writes:
> Hi Jan-Peter (and anyone else still interested in this thread):
>
> In the end, the conductor of my chamber opera asked to have the bar
> lines solid for all measures, but 50% grey and slightly thicker than
> default as the "baseline", and black and slightly thicker sti
Hi Jan-Peter (and anyone else still interested in this thread):
In the end, the conductor of my chamber opera asked to have the bar lines solid
for all measures, but 50% grey and slightly thicker than default as the
"baseline", and black and slightly thicker still for bar lines concurrent with
In relative, a note with no ' or , indicates the closest octave, e.g. for
adjacent notes
a b means the B one note above whatever A it was,
d c means the C one note below whatever D it was,
Effectively this means that using no ' or , will always produce a note
within a fourth of the previous one
Eluze writes:
> Jim Long wrote
>> What is the recommended way to align a whole-note chord over a
>> whole-measure rest? The rest gets centered in the bar, whereas
>> the chord gets placed above where beat 1 of the measure would be.
>
> would be? - it is!
>
> imo this is correct!
>
> if you still
Jim Long wrote
> What is the recommended way to align a whole-note chord over a
> whole-measure rest? The rest gets centered in the bar, whereas
> the chord gets placed above where beat 1 of the measure would be.
would be? - it is!
imo this is correct!
if you still want to shift it around you c
Wols Lists writes:
>.. not only in the fact that concert pitch has a single-digit ISO
>standard to its credit!
Hexadecimal?
-- Johan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
35 matches
Mail list logo
