Well, that was humbling. I honestly thought that NR 1.1 Pitches
was almost perfect, but the comments (thank you!) from last time
clearly indicated otherwise. When I tried to read the material
with a fresh mind (aided by the comments), I found many, many
things to fix.
As always, GDP here:
In addition to removing the forbid_line_engraver, you may want to use
\set Score.allowBeamBreak = ##t
(if you use version 2.10) or
\override Beam #'breakable = ##t
(if you use version 2.11.10 or later)
to allow for line breaks when there is a beam in some part.
See section Line breaking in the
In addition:
- For some people who have asked similar questions earlier, the real
question has
rather been how do I start a command prompt and change directory to the
folder where my MIDI file is. For MS Windows, you can find such
instructions
at
Graham Percival wrote:
Some sections have been completely rewritten (particularly Octave
check). Please read the new Pitches section and send comments.
- The text in Octave corrections and checks is contradictory. First it
says that
an octave check does not change the pitch, then it says
On Mon, 21 Jan 2008 11:24:22 +0100
Mats Bengtsson [EMAIL PROTECTED] wrote:
Graham Percival wrote:
Some sections have been completely rewritten (particularly Octave
check). Please read the new Pitches section and send comments.
- The text in Octave corrections and checks is
Graham Percival wrote:
On Mon, 21 Jan 2008 11:24:22 +0100
Mats Bengtsson [EMAIL PROTECTED] wrote:
Graham Percival wrote:
Some sections have been completely rewritten (particularly Octave
check). Please read the new Pitches section and send comments.
- The text in Octave
The layout object used to typeset these letters is TabNoteHead, so you can
change any of the font related properties on that object, in the same way
as is done for the TimeSignature object in example in section Font
selection.
The detailed documentation of all these properties can be found at
James,
the more I actually *read* the lilypond manuals, the more
I believe that everything is possible in the program.
No question! =)
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
Daniel Tonda wrote:
Maybe when writing guitar parts, adding a \clef G_8 would be an option?
Daniel Tonda C.
Daniel,
Could you elaborate on the function of this command? I'm not familiar with it.
~ Eric.
___
lilypond-user mailing list
Bertalan Fodor (LilyPondTool) wrote:
I'm always curious why people spend a lot of time to create something
for an editor that has been supported out of the box in jEdit for more
than 3 years now.
Well, it's bad enough trying to learn LilyPond, without struggling against
jEdit, too.
Hi everybody!
Currently I'm dealing with extending/altering lily's music font
according to my needs. Now I'm stuck with the following:
I want to alter a symbol, e.g. the notehead noteheads.s2. To do so I
open feta20.pfa from /usr/share/lilypond/2.10.5/fonts/type1 in FontForge
(v20061220),
But there is no LilyPondTool in NotePad++, so it is not fair to say
hey, LilyPondTool is buggy, so I use notepad++ .
My question was regarding this. JEdit supports LilyPond syntax highlight
out of the box since the end of 2004.
Also, even if you have problems with LilyPondTool, ie. you can't use
2008/1/21, Bertalan Fodor (LilyPondTool) [EMAIL PROTECTED]:
If I didn't use Java it would not exist at all, and certainly I would
not have users from Linux, Mac and Windows world. So we must accept this
trade-off: I don't like Java, but it is the platform which provides the most
features in
Bertalan Fodor (LilyPondTool) wrote:
And don't get this as an offense. My question was really curiosity.
...
So I want to make it a product that everyone uses for LilyPond.
No offence taken. It has been a very frustrating time, just to get a half
working LilyPondTool and jEdit. I know
Valentin Villenave wrote:
Another cool thing could be to develop a bundled Lily+jEdit+LPT
pre-configured easy installer :)
Fully cross-platform? :^)
Anyway, who would have the time to do that. ;-) (Rhetorical: I know you
did, but only for Windows ...)
--
Nick.
--
View this message in
On Jan 21, 2008, at 12:10 PM, Valentin Villenave wrote:
2008/1/21, Bertalan Fodor (LilyPondTool) [EMAIL PROTECTED]:
If I didn't use Java it would not exist at all, and certainly I would
not have users from Linux, Mac and Windows world. So we must
accept this
trade-off: I don't like Java, but
Op maandag 21 januari 2008, schreef Thies Albrecht:
Hi everybody!
Currently I'm dealing with extending/altering lily's music font
according to my needs. Now I'm stuck with the following:
I want to alter a symbol, e.g. the notehead noteheads.s2. To do so I
open feta20.pfa from
On Mon, 21 Jan 2008 11:41:20 -0400
Eric Patton [EMAIL PROTECTED] wrote:
Daniel Tonda wrote:
Maybe when writing guitar parts, adding a \clef G_8 would be an
option?
Could you elaborate on the function of this command? I'm not familiar
with it.
You can find information about \clef by look
Graham-
I think on this side of the pond that key is as close as you'll come
I just read the section through and it makes perfect sense to me and I use
transpose etc frequently
Yours-
Jay
Jay Hamilton
www.soundand.com
206-328-7694
--- [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
To:
I have never been able to get all the features of LilyPondTool to work
in jEdit. The advanced render and open as PDF has rarely if ever
worked for me.
I render from a bash or zsh shell and open it manually from the
Finder. It may be a bit awkward and not how it was designed to work,
but even so,
David Fedoruk írta:
I have never been able to get all the features of LilyPondTool to work
in jEdit. The advanced render and open as PDF has rarely if ever
worked for me.
So this is what disappoints me most :-) I would be happier and see more
use of my work if you didn't have problems. Could
Hi all,
I'm working on a piece for a friend of mine, and he has put a couple of
chords in it that don't reproduce in a nice fashion. I've looked through
the help resources, and wasn't able to find how to make these chords appear
as I wish.
Can anybody suggest some code that will make the
Hi Father Gordon,
Can anybody suggest some code that will make the following chords
appear as they are here?
G6(add9) -- where the 6 is a super-script, of course
Fmaj9 -- I don't want the triangle, but the maj
Noticed that you haven't gotten a response from anyone with more
ChordName(s)
Hi Father Gordon,
Sorry... should have done this first... =\
I decided to teach myself chord-name-exception coding -- attached is
your particular example, solved (I believe).
Hope this helps!
Kieren.
___
\version 2.11.37
\include english.ly
chExcMajNine =
{
c e g b
Father Gordon (et al.):
Even better!!
You can put them all in one list of exceptions -- see attached.
[Sorry... I'm just now climbing this particular learning curve.]
Kudos to the Lilypond team... AGAIN!!! =)
Cheers,
Kieren.
_
\version 2.11.37
\include english.ly
Gee thanks, Kieren!
I compiled the two snippets you gave me and they worked just fine. I
presume I can incorporate that code into the top of my \chordmode section --
I'll let you know how that works presently.
Thanks again!
Fr. Gordon+
On 21/01/2008, Kieren MacMillan [EMAIL PROTECTED] wrote:
On Mon, 21 Jan 2008 12:36:32 +0100
Mats Bengtsson [EMAIL PROTECTED] wrote:
Graham Percival wrote:
Not true; with = the d's octave is changed; with \octave the d's
octave is not changed.
No! The difference is that = modifies the pitch on the current note,
whereas the \octave changes
Whenever I code a guitar or bass piece, since they are written an octave
above their actual sound, I use the sub_8va clefs for the G and F clef.
However, in pieces I bought the clef that appears for the guitar is the
standard G clef without the 8va symbol, but I don't mind if it appears.
Daniel
On Jan 21, 2008 3:15 AM, Graham Percival [EMAIL PROTECTED] wrote:
Well, that was humbling. I honestly thought that NR 1.1 Pitches
was almost perfect, but the comments (thank you!) from last time
clearly indicated otherwise. When I tried to read the material
with a fresh mind (aided by the
On Tue, 22 Jan 2008 00:43:31 -0600
Daniel Tonda [EMAIL PROTECTED] wrote:
Whenever I code a guitar or bass piece, since they are written an
octave above their actual sound, I use the sub_8va clefs for the G
and F clef. However, in pieces I bought the clef that appears for the
guitar is the
On Tue, 22 Jan 2008 01:16:51 -0600
Trevor Ba__a [EMAIL PROTECTED] wrote:
Umm, can we check something here?
Please, that's the whole point of this.
Half-flats and half-sharps are formed by adding eh and ih; ...
... which sounds absoutely crazy to me and should instead read ...
Hi,
On Jan 17, 2008 3:30 PM, Mats Bengtsson wrote:
Below, you can find a complicated alternative solution that adds a new
bar type with this behaviour, so you could say \bar e|:.
Thanks for the tip, Mats.
I was experimenting with custom bar lines based on Mats' example. The
piece I'm working
32 matches
Mail list logo
