Re: Headword for unfretted-strings
Graham, you wrote Saturday, October 11, 2008 12:41 AM
On Fri, 10 Oct 2008 22:59:43 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
Graham, you wrote Friday, October 10, 2008 7:38 PM
> On Thu, 9 Oct 2008 10:08:00 +0100
> "Trevor Daniels" <[EMAIL PROTECTED]> wrote:
>
> Err, why midi? It doesn't help anything for the docs, and as
> you've just said, it's not intended to teach anything.
TIMS - this is music, stupid, you know, stuff you
_listen_ to ;)
Not the MIDI version of string sounds, you don't. :)
Strings are so expressive they can never be properly
synthesized. I grant you that.
Seriously, there's no reason to build the .midi files in
Documentation/user/out-www/. I can appreciate that you wanted to
hear how it sounded, but there's still no point in keeping the
\midi{} in the file. OK, it only adds half a second to the build
process... but who's going to go hunting around for that .midi
files? I mean, how many people *who build the docs* are going to
want to hear it badly enough to dig out that file?
I wasn't thinking of people who build the docs; rather
people who read them. LilyPond produces printed output
and MIDI output. The inspirational headwords are supposed
to show off what Lily can do. If they include the MIDI
commands all the reader has to do is copy and paste the
score and they can both see and hear them. The headwords
are the only scores in the whole of the documentation which
are fully self-contained. OK, they're only short extracts,
but nevertheless they are a complete Lily score. Come to
think of it, they do serve as a useful teaching aid just
because of that. And as they are complete they should
include \midi{} to demonstrate that part of Lily's output.
But I'm not going to die in the ditch defending this - it
just seemed the right thing to do.
Cheers,
- Graham
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
David Your extract is now visible on the kainhofer site. Unfortunately it takes up too much space, with the result that the small amount of following text is pushed off the bottom of the first screen. I would prefer to reduce it to the first two lines, after the end of the first two triplets. These two lines already show pretty well all the notational elements contained in the remainder anyway, but I appreciate we lose a lot of the musicality, which is a pity. I'll make this change, again so we can see the result, but please let me know if you are unhappy with this. You wrote Thursday, October 09, 2008 5:38 PM I guess you would like to show how to ask lilypond to produce midi output, but if you are interested, I have a live recording by Krzysztof Wagenaar [who created the piece, July the 30th, 2007 in Mirecourt, France]. On this recording: - the all piece last 8'30" [including 30sec rapid ultimate tuning and getting the audience 'quiet and ready', until the end with a very impressive silent moment at the end [I was there :-), until applause]; - the first 'measure' last 20"; - the extract you have last 1'45" I can produce wav, ogg and/or mp3 files for the 1st 'measure', the extract I sent you and/or the entire piece [and post it somewhere on the web], let me know. I'm not sure the docs can or should link to 'real' music, but it is an interesting idea. What do you think Graham? From the type setting point of view, I wanted to add a thin line and tiny text above the 1st 'measure' saying 'approximately 20", but I couldn't find out how to do so in a nice way [done by lilypond, well automatically positioned and dimensioned, so that it would also follow future custom adaptation of measure graphical length ...]. If someone can help me, many thanks. A text spanner maybe? But there's not much room for more annotation. If the extract is to be shortened maybe this isn't relevant now. In the header, in the meter section [lentement], I also wanted to add '[approximately 8 minutes] but had other [and still have] difficulties to solve before latest tuning of these type setting little details. I'll add this, again so we can see how it looks. David Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: New doc website development
Patrick McCarty schrieb: By `text div', you mean the div with the main docs, right? If you would like the maximum line width to be 80em, what sort of page layout would you propose? I am having trouble visualizing how this would work. I was thinking about bigger screens, so they could somehow center the whole content so a fixed width, where the content has a fixed max width and the contents also. Min width should of course change according to the resolution so you don't have to scroll horizontally. I'll consider your suggestion for the blockquoted sections. I don't think it's possible to have the musical examples adjust to the page width, since the maximum widths are hardcoded when the docs are compiled. What if we set the max width in the hardcoded scripts smaller? I also discovered afterwards already mentioned issures with the appendices in NR: eg the feta font list is a picture 600px wide so it would render bad in lower resolutions. It was also mentioned that blind people don't understand the picture. The scrollbars: I think the scrollbar for the contents div should always be on, don't remember how to achive this, something like setting height to 101%? So there won't be the switch when some subsections get opened. This is a very interesting suggestion! I'll think about it. nice On my 1024x768 there is also a scrollbar on the bottom but it is useless because it is always 100% long. Does this have to be there? On this small screen it eats up a relatively big space. Are you using Firefox 2 (or a browser that uses Gecko 1.8)? Because this is a known issue for those browsers. Ok, so that's the reason, indeed under Firefox 3 it doesn't happen. Happy to switch this year, hopefully... Till ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Mutopia LY Files
I downloaded an ly file from Mutopia and I am getting many errors and I am unable to obtain the printable file. I am using the latest released version which is 2.10.33. i looked insude my LY file and it was created with version \version "1.3.117". Can this be the source of the problems I am seeing? What do I need to do to fix it? I looked for older versions of your SW to try and download the proper one but couldn't find versions prior to 2.x. Thank you, Itzik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia LY Files
Well, the link to version 1.3.117 is http://download.linuxaudio.org/lilypond/sources/v1.3/lilypond-1.3.117.tar.gz , but it's only the source, so you'd have to build it yourself. But, you're probably better off either using the pdf on mutopia, or updating the file yourself. On 08.10.2008, at 18:53, Itzik Katz wrote: I downloaded an ly file from Mutopia and I am getting many errors and I am unable to obtain the printable file. I am using the latest released version which is 2.10.33. i looked insude my LY file and it was created with version \version "1.3.117". Can this be the source of the problems I am seeing? What do I need to do to fix it? I looked for older versions of your SW to try and download the proper one but couldn't find versions prior to 2.x. Thank you, Itzik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Lilypond midi to stdout?
Hi, I'm using Lilypond to print the results of an algorithmic music program written in Python. I'm looking for a way to play the results as they are produced (i.e bar by bar), and it occurred to me that simply playing Lilypond midi files with a midi player would do the trick. However, I can't figure out how to get Lilypond's midi data sent to stdout, where it could then be read from stdin by a player. Whatever I try (including python pipes and even plain shell pipes) it just writes the file to my home directory. Is there any way around this? Regards, John O'Hagan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
Le Sat, 11 Oct 2008 09:18:51 +0100, "Trevor Daniels" <[EMAIL PROTECTED]> a écrit : > > David > > Your extract is now visible on the kainhofer site. Unfortunately it takes > up too > much space, with the result that the small amount of following text is > pushed > off the bottom of the first screen. I would prefer to reduce it to the > first two > lines, after the end of the first two triplets. These two lines already > show > pretty well all the notational elements contained in the remainder anyway, > but I appreciate we lose a lot of the musicality, which is a pity. I'll > make this > change, again so we can see the result, but please let me know if you are > unhappy with this. Hi Trevor, may i suggest: - try reduce the staff line to 16 [or lower?] - 'measure' 7, [because of paper a4 i guess], the bow just after 'ritar. ...' is not correctly positionned anymore: try suppressing the '...' of ritar, or update 'accel...' and 'ritar...' instead of 'accel. ...' and 'ritar. ...' ==> this will save a line vertically than we'll see Thanks, David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
Also, the line starting with 'measure' 5, suppress the third argument of the first 3 calls to \colmark [ the " " arg], this will also save another vertical line ... Cheers, David Le Sat, 11 Oct 2008 09:18:51 +0100, "Trevor Daniels" <[EMAIL PROTECTED]> a écrit : > David > > Your extract is now visible on the kainhofer site. Unfortunately it takes > up too > much space, with the result that the small amount of following text is > pushed > off the bottom of the first screen. I would prefer to reduce it to the > first two > lines, after the end of the first two triplets. These two lines already > show > pretty well all the notational elements contained in the remainder anyway, > but I appreciate we lose a lot of the musicality, which is a pity. I'll > make this > change, again so we can see the result, but please let me know if you are > unhappy with this. Hi Trevor, may i suggest: - try reduce the staff line to 16 [or lower?] - 'measure' 7, [because of paper a4 i guess], the bow just after 'ritar. ...' is not correctly positionned anymore: try suppressing the '...' of ritar, or update 'accel...' and 'ritar...' instead of 'accel. ...' and 'ritar. ...' ==> this will save a line vertically than we'll see Thanks, David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
forgot to mention as weel, the file I sent you was utf8 encoded, as you commented the line, could you also replace the following accented characters: David Séverin épouse Lívia ;; -- Also, the line starting with 'measure' 5, suppress the third argument of the first 3 calls to \colmark [ the " " arg], this will also save another vertical line ... Cheers, David Le Sat, 11 Oct 2008 09:18:51 +0100, "Trevor Daniels" <[EMAIL PROTECTED]> a écrit : > David > > Your extract is now visible on the kainhofer site. Unfortunately it takes > up too > much space, with the result that the small amount of following text is > pushed > off the bottom of the first screen. I would prefer to reduce it to the > first two > lines, after the end of the first two triplets. These two lines already > show > pretty well all the notational elements contained in the remainder anyway, > but I appreciate we lose a lot of the musicality, which is a pity. I'll > make this > change, again so we can see the result, but please let me know if you are > unhappy with this. Hi Trevor, may i suggest: - try reduce the staff line to 16 [or lower?] - 'measure' 7, [because of paper a4 i guess], the bow just after 'ritar. ...' is not correctly positionned anymore: try suppressing the '...' of ritar, or update 'accel...' and 'ritar...' instead of 'accel. ...' and 'ritar. ...' ==> this will save a line vertically than we'll see Thanks, David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia LY Files
Wow, that's an old version. The utility convert-ly is for updating old files but it will almost certainly *not* work on such an old file without further manual editing. I don't know why you can't get the printable version so the only option I see is to try to convert the file and then see what errors you get and try to make the appropriate changes. Maybe someone else has a better idea for you. -David Itzik Katz wrote: I downloaded an ly file from Mutopia and I am getting many errors and I am unable to obtain the printable file. I am using the latest released version which is 2.10.33. i looked insude my LY file and it was created with version \version "1.3.117". Can this be the source of the problems I am seeing? What do I need to do to fix it? I looked for older versions of your SW to try and download the proper one but couldn't find versions prior to 2.x. Thank you, Itzik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
I agree with you, Trevor. The MIDI block should go in for the sake of
the readers, not for the sake of those building docs. I'm a fairly
experienced user now, but when I was starting out it gave me fits trying
to get the MIDI block in the right place and I would definitely have
appreciated the presence of one in an example like this. I really don't
see how anyone can object to having a MIDI block in a template or a
headword.
Jon
Trevor Daniels wrote:
Graham, you wrote Saturday, October 11, 2008 12:41 AM
On Fri, 10 Oct 2008 22:59:43 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
Graham, you wrote Friday, October 10, 2008 7:38 PM
> On Thu, 9 Oct 2008 10:08:00 +0100
> "Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> > Err, why midi? It doesn't help anything for the docs, and as
> you've just said, it's not intended to teach anything.
TIMS - this is music, stupid, you know, stuff you
_listen_ to ;)
Not the MIDI version of string sounds, you don't. :)
Strings are so expressive they can never be properly
synthesized. I grant you that.
Seriously, there's no reason to build the .midi files in
Documentation/user/out-www/. I can appreciate that you wanted to
hear how it sounded, but there's still no point in keeping the
\midi{} in the file. OK, it only adds half a second to the build
process... but who's going to go hunting around for that .midi
files? I mean, how many people *who build the docs* are going to
want to hear it badly enough to dig out that file?
I wasn't thinking of people who build the docs; rather
people who read them. LilyPond produces printed output
and MIDI output. The inspirational headwords are supposed
to show off what Lily can do. If they include the MIDI
commands all the reader has to do is copy and paste the score and they
can both see and hear them. The headwords
are the only scores in the whole of the documentation which
are fully self-contained. OK, they're only short extracts, but
nevertheless they are a complete Lily score. Come to
think of it, they do serve as a useful teaching aid just because of
that. And as they are complete they should include \midi{} to
demonstrate that part of Lily's output.
But I'm not going to die in the ditch defending this - it
just seemed the right thing to do.
Cheers,
- Graham
Trevor
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: rolled chords
Am Fri, 10 Oct 2008 11:21:54 -0700 schrieb "Danny Sosa" <[EMAIL PROTECTED]>: > ... less than 8 minutes and you already solved my problem... The amazing thing is: less than 10 minutes and *3* ppl helped ! Never saw such a helpful community! (well, besides [EMAIL PROTECTED] ;-) ) Seb. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
On Sat, 11 Oct 2008 09:36:38 -0300 David S__verin <[EMAIL PROTECTED]> wrote: > - try reduce the staff line to 16 [or lower?] It's supposed to be 15, anyway. Trevor: pitches-headword.ly Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
adding rests automatically
Dear Lilypond users,
is there possibilitiy to add the rests in the below quoted example not by
hand but automatically?
\version "2.11.49"
restmusic = { d8 r d' r fis r d' r e r d' r a r cis' r }
\new Staff { \clef bass \key d \major \restmusic }
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia LY Files
2008/10/8 Itzik Katz <[EMAIL PROTECTED]>: > I downloaded an ly file from Mutopia and I am getting many errors and I am > unable to obtain the printable file. If you point us to this specific file, we'll (at least I'll) try to update it on our own and/or tell you how to do it. What operating system are you using? Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
Many thanks, David. This looks promising. In addition I've reduced the global staff size to 15, as Graham suggested. For now I've left the midi out. If it is to be used it has to go in all the headwords for consistency, and as there is opposition (as well as support) to this it will need more discussion first. I'll push it to git master and we'll see how it looks tomorrow. Trevor - Original Message - From: "David Séverin" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "Jonathan Kulp" <[EMAIL PROTECTED]>; "Graham Percival" <[EMAIL PROTECTED]>; Sent: Saturday, October 11, 2008 2:21 PM Subject: Re: Headword for unfretted-strings Finally, I did some work to get it done properly in 3 lines, here is what it looks like on my box [with lily doc parameters] What do you think ? Cheers, David ;; - Le Sat, 11 Oct 2008 09:18:51 +0100, "Trevor Daniels" <[EMAIL PROTECTED]> a écrit : David Your extract is now visible on the kainhofer site. Unfortunately it takes up too much space, with the result that the small amount of following text is pushed off the bottom of the first screen. I would prefer to reduce it to the first two lines, after the end of the first two triplets. These two lines already show pretty well all the notational elements contained in the remainder anyway, but I appreciate we lose a lot of the musicality, which is a pity. I'll make this change, again so we can see the result, but please let me know if you are unhappy with this. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: adding rests automatically
Yes; use a music function. See the docs.
Cheers,
- Graham
On Sat, 11 Oct 2008 17:51:33 +0200
"Stefan Thomas" <[EMAIL PROTECTED]> wrote:
> Dear Lilypond users,
> is there possibilitiy to add the rests in the below quoted example
> not by hand but automatically?
>
> \version "2.11.49"
> restmusic = { d8 r d' r fis r d' r e r d' r a r cis' r }
> \new Staff { \clef bass \key d \major \restmusic }
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: adding rests automatically
On 10/11/08 9:51 AM, "Stefan Thomas" <[EMAIL PROTECTED]>
wrote:
> Dear Lilypond users,
> is there possibilitiy to add the rests in the below quoted example not by hand
> but automatically?
>
> \version "2.11.49"
> restmusic = { d8 r d' r fis r d' r e r d' r a r cis' r }
> \new Staff { \clef bass \key d \major \restmusic }
This can be done through the use of a music function. You would just pass
the notes to the function, and it would return the rest of the music.
You can read about music functions in the documentation. See the notation
reference for 2.11, section 6. Music functions.
Carl
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On 2008/10/07 4:41 PM, "Alexander Kobel" <[EMAIL PROTECTED]> wrote: >> A List Apart explains how to implement this with cookies, but we would >> rather not use JavaScript: Cookies != JavaScript True, it's very easy to fiddle with them if you're using JavaScript, but they started as a server-side state-maintenance mechanism. You can set and read them without touching it at all. > And yes, I'm against JavaScript, too. This doesn't count as a real > client-side solution from my point of view. > > Simplest solution, server-sided, efficient and secure, but clearly not > nice: Keep a version of the docs for each style in a different > subdirectory, and switch accordingly. ;-) Separate versions are not necessary: just offer the user an option to set the preference in a persistent cookie, which the server creates and sends back to the client. Then, the next time the server reads it, it can parse out the preferred style sheet and send it as "the" style sheet. Best, Kurt ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: adding rests automatically
On 11.10.2008 (11:01), Carl D. Sorensen wrote:
> You can read about music functions in the documentation. See the notation
> reference for 2.11, section 6. Music functions.
The paradigm in the beginning is confusing:
function =
#(define-music-function (parser location var1 var2... )
(var1-type? var2-type?...)
#{
...music...
#})
where
argiith variable
argi-type? type of variable
It is clear what it means, of course, but a mathematician would be troubled
by a where clause which defines arguments which are not present in the
equation, and a musician may be confused by it, at least intially.
Eyolf
--
___ __ Frobtech, Inc.
/__/\ ___/_/\
\ \ \ / /\\
\ \ \_/__ / \ "If you've got the job,
_\ \ \ /\_/___ \ we've got the frob."
// \__\/ / \ /\ \
___//___/\ / _\/__
/ / \ \// //\
__/ / \ \ // // _\__
/ / / \___\// // / /\
/_/__/___/ // /___/ \
\ \ \___\ \\ \ \ /
\_\ \ / /\\ \\ \___\/
\ \/ / \\ \\ /
\_/ /\\ \\/
/__/ \\ /
\ _ \ /_\/
\ //\ \/ \ \ \
// \ \ / \ \ \
\\ /___\/ \ \ \
\\/\__\/
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Hi Kurt, On Sat, Oct 11, 2008 at 10:34 AM, Kurt Kroon <[EMAIL PROTECTED]> wrote: > > Separate versions are not necessary: just offer the user an option to set > the preference in a persistent cookie, which the server creates and sends > back to the client. Then, the next time the server reads it, it can parse > out the preferred style sheet and send it as "the" style sheet. It sounds like you know how to implement this. Would you be willing to work on it or look more into it? This would be a wonderful "feature" to have. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Review of NR 1.5
Hi Francisco I finally got around to reviewing NR 1.5 Simultaneous notes, which I believe you previously edited. The main changes I made are: - add section on Simultaneous expressions to 1.5.1 - clarify Single-staff polyphony in 1.5.2 - various miscellaneous other tweaks I've just pushed the edited version of simultaneous.itely to git master. Could you please check it out, either by looking at the .itely file on Savannah or when it appears on Reinhold's server, and let me know if you are unhappy with any of the changes. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Lyrics of a Voice above the Staff of the Voice
Hello together, I'm working on a sheet where the lyrics of the Soprano are set above its staff because the staff is shared with the Alto which has lyrics differing from those of the Soprano at some positions (which I read by using \skip). As far as I have 4 stanzas, using markups is not a usable workaround. Recently I got to: \override LyricText #'extra-offset = #'(0 . 20) But this leaves the hyphens below the Staff and only moves the text into other page items. So the question is: How do I get the lyrics above the staff of the voice they are assigned to by \lyricsto? Thanks in advance for any help. Greetings Robert Waniek ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Moving guitar fingering orientations
I'm trying to get my fingering indications below the noteheads using \set
fingeringOrientations = #'(down), but they remain resolutely above the beam.
I also tried (left) and (right) with no change either. My two bar test input
and output are attached. Can anyone tell me why this isn't working? I'm
using 2.11.61 on WinXP.
\version "2.11.61"
\paper {
#(set-paper-size "a4")
top-margin = 1.5\cm
bottom-margin = 1.5\cm
line-width = 18\cm
}
\header {
tagline = ##f
}
% Treble voice
#(define RH rightHandFinger)
up = {
\set fingeringOrientations = #'(down)
\repeat volta 2 {
a16\mf bes'-2 d''-3 g''-4 d' bes' d'' g'' a bes'-2 d''-3 f''-1 d' bes' d'' f''|
a bes'-2 d''-3 e''-0 d' bes' d'' e'' a bes' d'' e'' d' bes' d'' e''
}
}
% Bass voice
down = {
\repeat volta 2 {
a4 d' a d'|
a d' a d'
}
}
thescore = \score {
<<
\context Staff = guitar {
\clef treble
\key c \major
\time 4/4
\tempo "Moderato"
\override Staff.NoteCollision #'merge-differently-headed = ##t
<<
\context Voice = "1" { \voiceOne \up }
\context Voice = "2" { \voiceTwo \down }
>>
}
>>
\layout { }
}
\score {
\thescore
}
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
