回复： Jianpu Notation

Here's an example for key signatures. David Zhang jianpu-key-change.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Do we really offer the future?

On Thu, 2015-04-23 at 13:06 -0500, David Nalesnik wrote: > > > On Wed, Apr 22, 2015 at 4:16 PM, Thomas Morley > wrote: > 2015-04-22 22:38 GMT+02:00 tisimst > : > > All, > > > > On Wed, Apr 22, 2015 at 2:21 PM, Noeck [via Lilypond] > <[hidden email]

Re: Jianpu Notation

Hello David and Ming, > On Apr 23, 2015, at 10:44 PM, Super-User wrote: > > > I just spotted \time 3/4 or 4/4, jianpu display " 6 - ." , I think it > > should be "6 - -". > Indeed, in Jianpu, dots follow only by quarter notes and below. Yes, this is a “known issue”. I have started working on

回复： Jianpu Notation

\slurUp -- 原始邮件 -- 发件人: "Super-User";; 发送时间: 2015年4月24日(星期五) 上午10:44 收件人: "MING TSANG"; "Paul Morris"; 抄送: "lilypond-user"; 主题: 回复： Jianpu Notation > I just spotted \time 3/4 or 4/4, jianpu display " 6 - ." , I think it should > be "6 - -". Plus, I made a

回复： Jianpu Notation

> I just spotted \time 3/4 or 4/4, jianpu display " 6 - ." , I think it should > be "6 - -". Plus, I made a mistake in the original version about rests. Rests beyond one beat are displayed as repeated "0"s e.g. "0 0 0 0" for whole rest. In addition, I have noticed that in 2015-04-23_11.png

Re: Jianpu Notation

Paul, Thank you for the update to jianpu5.ly. I just spotted \time 3/4 or 4/4, jianpu display " 6 - ." , I think it should be "6 - -".   Please refer to .pngTechnically it is ok- the . represent 1/2 of "6 -" which is three beats."6 - -" also depict three beats -- I saw all jianpu use this notati

Re: Do we really offer the future?

On Fri, 24 Apr 2015 01:59:40 +0200, Urs Liska wrote: Am 24.04.2015 um 01:26 schrieb Kieren MacMillan: Hi Gilles, I have _not_ asked "the LilyPond team" to spend any resources for whatever. First of all, nobody wrote that you did. You wrote What's for the LilyPond team in spending resources

Re: Do we really offer the future?

Am 24.04.2015 um 01:26 schrieb Kieren MacMillan: Hi Gilles, I have _not_ asked "the LilyPond team" to spend any resources for whatever. First of all, nobody wrote that you did. You wrote What's for the LilyPond team in spending resources trying to work around those self-inflicted limitati

Re: Do we really offer the future?

Hi Gilles, >> I have _not_ asked "the LilyPond team" to spend any resources for whatever. > First of all, nobody wrote that you did. You wrote > What's for the LilyPond team in spending resources > trying to work around those self-inflicted limitations? That response fairly strongly implies tha

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

On 23/04/15 20:35, Calixte Faure wrote: > I learned music in French (native French) and was at the beginning a > little bit confused with 2 4 8 16 etc. because we say white, black, > "hooked", double-"hooked", triple-, etc. but after all it is logical > with the numbers. > I understood the choice

Re: How do new users feel about LilyPond's documentation?

On 23/04/15 00:00, Kieren MacMillan wrote: > Hi Wol, > Hi Kieren (NB, I've read Thomas' response) >> What I'd like to see is worked, documented examples. > > I’m happy to supply a few… But there are so many questions: > > 1. Where would they be kept? Actually, the thought just struck me, maybe

Re: Paper size survey

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Erm, the French like adopting and boasting about cutting devices. See https://en.wikipedia.org/wiki/Halifax_Gibbet for an earlier example. There is a discussion at https://en.wikipedia.org/wiki/Guillotine#Precursors about earlier designs. ;-) On 23/0

Re: Paper size survey

We call it massicot in French, I just found out it comes from its inventor Guillaume Massiquot: seems that French people like creating cutting machines! :D 2015-04-23 14:42 GMT+02:00 Kieren MacMillan : > Hi Karl, > > > a good paper cutter (what's the right word?) > > Guillotine. =) > Yes, I’m se

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

- Original Message - > From: "Calixte Faure" > To: "Noeck" > Cc: "LilyPond Users" > Sent: Thursday, April 23, 2015 7:35:18 PM > Subject: Re: What is the problem with "\relative"? (Was: Do we really offer > the future?) > > I learned music in French (native French) and was at the be

Re: E-mail management question

Filters work perfectly. I can now review, ignore, or delete the email as it fills my new Lilypond folder on the email server. Inbox is always bypassed. No more phone blowing-up all day. :) Great suggestions from everyone. Thanks, Lance On Thu, Apr 23, 2015 at 11:35 AM, SoundsFromSound wrote

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Calixte Faure wrote: I learned music in French (native French) and was at the beginning a little bit confused with 2 4 8 16 etc. because we say white, black, "hooked", double-"hooked", triple-, etc. . At least you weren't trapped in hemi-demi-semi-quavers! - Pete ___

Re: Jianpu Notation

Hi Ming, > On Apr 23, 2015, at 7:41 AM, MING TSANG wrote: > > Good morning Paul, > > Thank you very much for you jianpu4.ly. > > I run your jianpu-test.ly and sportted one note not the same in key C and key > D. The 2nd note on third measure - a dot below the horizontal bar is missing > in

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

I learned music in French (native French) and was at the beginning a little bit confused with 2 4 8 16 etc. because we say white, black, "hooked", double-"hooked", triple-, etc. but after all it is logical with the numbers. I understood the choice of 2 4 8 16 during an exchange semester in Germany

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Hi Joram, > c' etc. is just the natural way of calling the notes in > Dutch, German and many northern and eastern European languages > So here in Germany it is an advantage when teaching LilyPond to newcomes: > You write the notes just by their name: d' fis' a' d'' – as easy as that. Interesting.

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Hi Simon, > – I think the preference one will take also depends on musical style: a piece > of renaissance vocal music uses so few leaps greater than a fourth that the > advantage of relative in typing is huge and it’s ‘error-pronity’ small. On > the other extreme, a piano piece by George Crumb

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

>> c5 d5 e5 f5 g5 f5 e5 d5 c5 > > All other things being equal, that *would* have been great. That would save typing in some cases and would follow American and other conventions. But c' etc. is just the natural way of calling the notes in Dutch, German and many northern and eastern European

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

On 23.04.2015 (19:40), Richard Shann wrote: > Well, if you set up that mapping for Denemo you could get LilyPond's > beautiful typesetting too :) The last time I tried, it wasn't possible in denemo, I think because the keyboard shortcuts were tied to specific octaves, or something like that. I've

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

On Thu, 2015-04-23 at 19:36 +0200, Eyolf Østrem wrote: > > > On 23.04.2015 (10:04), H. S. Teoh wrote: > > > Besides, only powers of 2 are valid for durations, which wastes all the > > other numbers in between. Unfortunately I don't have a good idea on how > > to write durations without using dig

Re: Do we really offer the future?

On Wed, Apr 22, 2015 at 4:16 PM, Thomas Morley wrote: > 2015-04-22 22:38 GMT+02:00 tisimst : > > All, > > > > On Wed, Apr 22, 2015 at 2:21 PM, Noeck [via Lilypond] <[hidden email]> > > wrote: > >> > >> this is a triviality for most of you and it does not solve the original > >> issue of deleting

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Two small thoughts also from me: – I think the preference one will take also depends on musical style: a piece of renaissance vocal music uses so few leaps greater than a fourth that the advantage of relative in typing is huge and it’s ‘error-pronity’ small. On the other extreme, a piano piece

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

On 23.04.2015 (10:04), H. S. Teoh wrote: > Besides, only powers of 2 are valid for durations, which wastes all the > other numbers in between. Unfortunately I don't have a good idea on how > to write durations without using digits either. I started on a vim script to remap the keyboard as foll

Re: Standard LilyPond score structure (Was: How do new users feel about LilyPond's documentation?)

Am 23.04.2015 um 09:38 schrieb Urs Liska: Am 23. April 2015 09:32:56 MESZ, schrieb Simon Albrecht : Am 23.04.2015 um 04:39 schrieb H. S. Teoh: I even apply this structure to long rests -- instead of R1*50 (or however many bars it is), I break it up into groups under passage labels, and within

how apt are comparisons to TeX/LaTeX?

In the context of the long discussions of what does lilypond need to do, I'm predisposed to try to think about it in terms of what (I think I) know about TeX/LaTeX. So the first question is: how much of lilypond's goals and design are based on TeX/LaTeX? Along these lines comes a series of o

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Hi, > It makes me think that it was a wrong design decision in lilypond to use > ' and , for octave indications and digits 1, 2, 4, 8, ... for durations. > If we had used digits for octave designations instead, absolute mode > would be much less painful to write, e.g.: > > c5 d5 e5 f5 g5 f5

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

On Thu, Apr 23, 2015 at 03:35:59PM +0200, Federico Bruni wrote: > Hi Kieren > > 2015-04-23 14:40 GMT+02:00 Kieren MacMillan : > > > > personally I find lilypond code in \relative mode easier to read. > > > > Really? I look at > > > > \relative c,, { c4 g' a b e f' g' a, b,, c’ } > > > > and I

Re: E-mail management question

> On 23 Apr 2015, at 16:59, SonusProj . wrote: > Subscribing to this e-mail list is overwhelming me with e-mail posts that are > beyond me and outside of my scope of interest. Is it possible to throttle > the e-mail so I don't receive 70 e-mails a day? One option is a daily digest, good if y

Re: How do new users feel about LilyPond's documentation?

Hi, a bit late, but my memories from when starting with LilyPond: > 1. What is the thing you (especially new users) like the least about > LilyPond's documentation structure? - documentation The sheer amount of pages to read was daunting. But I wanted to understand it (not being a programme

Re: Jianpu Notation

On Thu, Apr 23, 2015 at 11:09 AM, David Nalesnik wrote: > > > On Thu, Apr 23, 2015 at 11:07 AM, Carl Sorensen > wrote: > >> >> >> On 4/23/15 7:55 AM, "H. S. Teoh" wrote: >> >> >On Thu, Apr 23, 2015 at 12:34:32PM +, Carl Sorensen wrote: >> >> >> >> >> >> On 4/22/15 10:57 PM, "Super-User" wr

Re: What is a voice context?

Am 23.04.2015 um 18:37 schrieb Carl Sorensen: On 4/23/15 12:02 AM, "Urs Liska" wrote: Am 23.04.2015 um 06:07 schrieb Carl Sorensen: So now I'm going to jump in on what I think a Voice context is. A Voice context is a context, which means it can contain engravers, performers, and music ex

B Series paper

B4 paper is readily available in Japan (Japan has an amazing riches of paper!). You can purchase it online through Rakuten Global Market: http://global.rakuten.com/en/category/303151 It's not cheap per sheet, but its certainly cheaper than buying 19 tonnes. HTH, Carl ___

Re: What is a voice context?

On 4/23/15 12:02 AM, "Urs Liska" wrote: > > >Am 23.04.2015 um 06:07 schrieb Carl Sorensen: >> So now I'm going to jump in on what I think a Voice context is. >> >> A Voice context is a context, which means it can contain engravers, >> performers, and music expressions. >> ... >> >> I'd be happy

Re: E-mail management question

SonusProj . wrote > I am a new user and really have no big plans on being a developer or power > user. I just want to get my projects, analysis, practice lessons, etc to > paper with some modicum of control. > > I have Notion and it works well and quick but the limitations prevent me > from getti

Re: Jianpu Notation

On Thu, Apr 23, 2015 at 11:07 AM, Carl Sorensen wrote: > > > On 4/23/15 7:55 AM, "H. S. Teoh" wrote: > > >On Thu, Apr 23, 2015 at 12:34:32PM +, Carl Sorensen wrote: > >> > >> > >> On 4/22/15 10:57 PM, "Super-User" wrote: > >> > >> >Seheme, as a dialect of Lisp, can be annotated with ;; so t

Re: Jianpu Notation

On 4/23/15 7:55 AM, "H. S. Teoh" wrote: >On Thu, Apr 23, 2015 at 12:34:32PM +, Carl Sorensen wrote: >> >> >> On 4/22/15 10:57 PM, "Super-User" wrote: >> >> >Seheme, as a dialect of Lisp, can be annotated with ;; so that our >> >Scheme codes implementing Jianpu can be documented as well.

Re: E-mail management question

On 2015-04-23 16:59, SonusProj . wrote: Subscribing to this e-mail list is overwhelming me with e-mail posts that are beyond me and outside of my scope of interest. Is it possible to throttle the e-mail so I don't receive 70 e-mails a day? I guess I am seeing if there is a forum type format

Re: E-mail management question

2015-04-23 17:37 GMT+02:00 SonusProj . : > I see a method, though cumbersome, to post to this e-mail group without > being a subscriber. How does one stop being a subscriber if I choose that > path? You must be subscribed to the list to be able to post a mesage from your email client. I suggest

Re: E-mail management question

Nabble does have its own account login, so you'd need to create that with them in order to *write* a post on their site. Reading is always open without an account. Your mailing list subscription is managed here: https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: E-mail management question

Thanks Abraham and also thanks Werner. I try both suggestions. I see a method, though cumbersome, to post to this e-mail group without being a subscriber. How does one stop being a subscriber if I choose that path? Also, I see nabble has a login. Does this site allow replies to the posts it co

Re: Jianpu Notation

On Thu, Apr 23, 2015 at 9:55 AM, H. S. Teoh wrote: > On Thu, Apr 23, 2015 at 12:34:32PM +, Carl Sorensen wrote: > > > > > > On 4/22/15 10:57 PM, "Super-User" wrote: > > > > >Seheme, as a dialect of Lisp, can be annotated with ;; so that our > > >Scheme codes implementing Jianpu can be docume

Re: E-mail management question

Lance, On the other hand, all correspondence is archived according to these threads using the free Nabble service. You can find it here: lilypond.1069038.n5.nabble.com It keeps the conversations in a more familiar "forum"-like format, so you can go whenever you need without feeling like you have

Re: How do new users feel about LilyPond's documentation?

On Thu, Apr 23, 2015 at 07:11:27AM -0700, Knute Snortum wrote: > LilyPond has a great glossary, but I'd like to see cross-references > back to the Notation manual. For instance, I might lookup "grace > note" which gives me acciaccatura >

Re: E-mail management question

> Subscribing to this e-mail list is overwhelming me with e-mail posts > that are beyond me and outside of my scope of interest. Is it > possible to throttle the e-mail so I don't receive 70 e-mails a day? You should activate `thread view' in your e-mail reader. Then you can simply ignore all e

Re: Standard LilyPond score structure (Was: How do new users feel about LilyPond's documentation?)

On Thu, Apr 23, 2015 at 01:55:57PM +0200, Gilles wrote: [...] > Of course, if you are used to it, nobody forces you to change. The > suggestion was certainly that LilyPond should forbid all input other > than the "standard" ("best practice") layout. > > [Yet I want to stress that what you seem to

Fwd: Re: Problem RemoveEmptyStaves

Message transféré Sujet : Re: Problem RemoveEmptyStaves Date : Thu, 23 Apr 2015 17:05:00 +0200 De :Les Éditions Valmajour - pg Pour : tisimst Hello, thanks for your answer, I actually just found out a few minutes ago : I added a \StaffGroup context with a

Re: Do we really offer the future?

Hello. On Thu, 23 Apr 2015 12:09:29 +0200, Urs Liska wrote: Hi all, I had to leave this alone for a while, otherwise I wouldn't have been able to reply calmly to a number of the first responses on this thread. It's only lately that the discussion has reached a level of constructivity that may b

Re: Do we really offer the future?

+ I do think that your efforts are important for the future of LilyPond. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Standard LilyPond score structure (Was: How do new users feel about LilyPond's documentation?)

On Thu, Apr 23, 2015 at 09:32:56AM +0200, Simon Albrecht wrote: > Am 23.04.2015 um 04:39 schrieb H. S. Teoh: > >I even apply this structure to long rests -- instead of R1*50 (or > >however many bars it is), I break it up into groups under passage > >labels, and within each passage label groups of R

Re: Do we really offer the future?

Hi Urs, thanks a lot for all your efforts. I think you see the situation very clearly and I hope you continue this way. I can't see what I could contribute to that but in general you have my support for what you do. Best, Joram ___ lilypond-user maili

Re: Problem RemoveEmptyStaves

This is curious, but it can be taken care of. If the solo part is *always* visible, then you can do: \new Dynamics \with { \override VerticalAxisGroup.remove-empty = ##f } { ... } in _just_ the solo staff. This, of course, will not be effective if there are times when it is appropriate for it to

Re: Do we really offer the future?

Depends on how you type your files and read music, I guess. As a singer I learned reading music relatively so it is more natural for me and i exclusively use \relative mode. But I agree there are limitation like Kieren second example with split voices: I always expect the note before the split to b

Re: Jianpu Notation

On Thu, Apr 23, 2015 at 12:34:32PM +, Carl Sorensen wrote: > > > On 4/22/15 10:57 PM, "Super-User" wrote: > > >Seheme, as a dialect of Lisp, can be annotated with ;; so that our > >Scheme codes implementing Jianpu can be documented as well. > > Comments in the code are not the documentatio

E-mail management question

I am a new user and really have no big plans on being a developer or power user. I just want to get my projects, analysis, practice lessons, etc to paper with some modicum of control. I have Notion and it works well and quick but the limitations prevent me from getting what I want onto the printe

Re: Creating LilyPond Object Models

On the piano I can play/think in voices or not. Sorry, I've lost track as to who wrote that. But just in case -- one might consider the (single-musician) pianist accompanying a (4-voiced) sunday school hymn. Pete ___ lilypond-user mailing list lilypon

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Am 23.04.2015 um 16:13 schrieb ArnoldTheresius: Federico Bruni wrote ... personally I find lilypond code in \relative mode easier to read. Perhaps, it's only a problem because the editors we use are not able to translate automatically between relative and absolute octave notation. Well, bac

回复： Jianpu Notation

Ming Tsang: I also expected it for long, and went for collage for a CS degree, and work in startups for two years, and try to write my own implementation. >Note that I don't say that the output of a1soft program is optimal >compared to manually printed jianpu scores. But lilypond's output is >s

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Hi Federico, > I see the first as less cluttered than the second (and another example of > music can appear much more cluttered than above example). I see the second as containing more information encoded directly in the input, and requiring less to be added by the user. > I don't like trying

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Federico Bruni wrote > ... >> > personally I find lilypond code in \relative mode easier to read. Perhaps, it's only a problem because the editors we use are not able to translate automatically between relative and absolute octave notation. Well, back to the original question, what may profession

Re: Creating LilyPond Object Models

Hi Urs, > If, as a musician, I get confused by "thinking of a voice context" I can't > use any technology of notating, including pen and paper. > But if I can abstract my instrument - the piano - away and realize it uses > multiple voices, I can use that concept for all notation programs. I thin

Re: How do new users feel about LilyPond's documentation?

LilyPond has a great glossary, but I'd like to see cross-references back to the Notation manual. For instance, I might lookup "grace note" which gives me acciaccatura , but there is no link to the Notation manual. Knute

Re: "Instrument" as first-class citizen

Hi Carl, > I never use the word "music object" for LilyPond entities. That’s wise. As I said, I think we shouldn’t let new and potentially confusing nomenclature creep in. > If we are missing structures needed to capture music the way musicians and > composers think about it, it may be desirabl

Problem RemoveEmptyStaves

Hello, Hello everyone, I have a contextproblem; in the attached file, I need to have the dynamics(placed in a context Dynamics) in all parts. But when I use "\ RemoveEmptyStaves" in the context \PianoStaff, dynamics disappear from the solo part. I do not see what it comes from. Does anyone have

Re: Do we really offer the future?

2015-04-23 14:45 GMT+02:00 Kieren MacMillan : > > It is far faster to input > > I disagree: I find absolute mode far faster for input, and the benefit in > favour of absolute *increases* the moment I have to do any > cutting-and-pasting. I must say that I've never tried absolute mode in any real

Re: Do we really offer the future?

On Wed, 2015-04-22 at 14:01 +0100, Richard Shann wrote: > On Wed, 2015-04-22 at 08:31 -0400, Kieren MacMillan wrote: > > Hi Richard, > > > > > Interesting, I didn't realize that this was a reason to use a front-end > > > to generate the LilyPond. With the Denemo front end it is Del,M to > > > dele

Re: Creating LilyPond Object Models

On Thu, Apr 23, 2015 at 8:22 AM, David Nalesnik wrote: > > The list at > > > > lists the various sorts of stream events which are input for translators. > Simply renaming this section "Stream Events" with an introductory blurb

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Hi Kieren 2015-04-23 14:40 GMT+02:00 Kieren MacMillan : > > personally I find lilypond code in \relative mode easier to read. > > Really? I look at > > \relative c,, { c4 g' a b e f' g' a, b,, c’ } > > and I can’t immediately tell which octave the last c is in. Looking at > > c,,4 g,, a,,

Re: How do new users feel about LilyPond's documentation?

Abraham Lee gmail.com> writes: > > All, > I've been thinking about this a lot lately, even going so far as to create my own "Quick Start" tutorials for new users, but I can only go so far in my own head. I really have two questions that I keep wondering about: > > What is the thing you (especia

Re: Creating LilyPond Object Models

Am 23.04.2015 um 15:13 schrieb Kieren MacMillan: Hi Urs, Hence “musician” != “voice”, and to try to conflate the two ideas (as one of the replies did) is potentially confusing. Yes, but that's a confusion that is not related to LilyPond at all. That confusion immediately becomes related to

Re: Creating LilyPond Object Models

On Thu, Apr 23, 2015 at 3:25 AM, Johannes Rohrer wrote: > * 2015-04-23 01:29 +0200: > > Translators are program elements that convert music expressions to > output. > > Engravers are translators that create printed output. Performers are > > translators that create midi output. > > > > Translat

Re: Creating LilyPond Object Models

Hi Urs, >> Hence “musician” != “voice”, and to try to conflate the two ideas (as one of >> the replies did) is potentially confusing. > > Yes, but that's a confusion that is not related to LilyPond at all. That confusion immediately becomes related to Lilypond if, as was suggested/implied, her

Re: "Instrument" as first class citizen (Was: ...)

Hi Xavier, > Actually there is the \addInstrumentDefinition command (used in > combination with \instrumentSwitch) which does *part* of that. > See NR 1.6.3 Writing parts > Instrument names > http://lilypond.org/doc/v2.18/Documentation/notation/writing-parts#instrument-names Yes… But if we’re [fi

Re: Creating LilyPond Object Models

On 4/23/15 1:25 AM, "Johannes Rohrer" wrote: >* 2015-04-23 01:29 +0200: >> Translators are program elements that convert music expressions to >>output. >> Engravers are translators that create printed output. Performers are >> translators that create midi output. >> >> Translators examine the

Re: How do new users feel about LilyPond's documentation?

Hi Thomas (et al.), > I wanted to make a score for Guitar with tab but I do not find > an example in the documentation that is for an newbie readable […] > one file so that people can copy and past it, press engrave button and it > works Sounds to me like you’re asking for a well-commented templ

Re: How do new users feel about LilyPond's documentation?

Hi Carl, > I'd be happy to have a Best Practices guide as part of the LilyPond > documentation. I'd be happy to review your proposals for appearance, > organization, and content. Alright! I’ll put together a proposal and forward it to you off-list. Thanks, Kieren. __

Re: Creating LilyPond Object Models

Am 23.04.2015 um 14:50 schrieb Kieren MacMillan: Hi Urs, On the piano I can play/think in voices or not. But that’s exactly my point: you’re a single “musician”. (I think everyone would agree on that semantic.) But you can play multiple “voices”. Hence “musician” != “voice”, and to try to c

Re: Standard LilyPond score structure (Was: How do new users feel about LilyPond's documentation?)

Hi Carl, > Flexibility is also a Good Thing. And standardization and flexibility are > always at odds with one another. > > Similarly, brevity is a Good Thing. And obviousness is a good thing. And > brevity and obviousness are often at odds with one another. > > The tradeoffs between these co

Re: Do we really offer the future?

Hi Urs, Thank you again for your excellent efforts in this regard. > So finally I'm back at the beginning, namely my original post's question, > preparing a convincing set of facts, arguments and "promises" that help to > overcome the reservations with regard to b) and c) of the above list. I h

Re: Creating LilyPond Object Models

On 4/23/15 3:26 AM, "Urs Liska" wrote: > >I think this is an excellent approach. Actually this is exactly one kind >of information that is lacking in the documentation (or at least not >accessible to the user). If one has the chance to get such a model it is >much more easy to guess where to fi

Re: Creating LilyPond Object Models

Hi Urs, > On the piano I can play/think in voices or not. But that’s exactly my point: you’re a single “musician”. (I think everyone would agree on that semantic.) But you can play multiple “voices”. Hence “musician” != “voice”, and to try to conflate the two ideas (as one of the replies did) i

Re: "Instrument" as first-class citizen

On 4/23/15 6:32 AM, "Kieren MacMillan" wrote: >Hi Carl (et al.), > >>> It doesn't help that many things are implicit and based on contexts >>>which >>> are invisible and undocumented > >> Hmm. I have a bit more trouble understanding this. > >I infer that he (correctly) means how > >\version

Re: Jianpu Notation

On 4/22/15 10:55 PM, "Werner LEMBERG" wrote: > >>>Ok, the problem was that your music file was for LilyPond 2.19 and >>>jianpu3.ly only works with 2.18. >> >> Have you proposed adding this to LilyPond? It seems like this would >> be a promising thing to add to the core, since it's another stand

Re: Do we really offer the future?

Hi Shane, > For God's sake don't deprecate \relative Okay, “deprecation” is a bit strong. =) But I don’t even tell newbies about it when I’m introducing them to Lilypond — I tried that for a while, and found that overcoming the confusion not worth the effort. > It is far faster to input I d

Re: Paper size survey

Hi Karl, > a good paper cutter (what's the right word?) Guillotine. =) Yes, I’m serious. Cheers, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Hi Martin, > personally I find lilypond code in \relative mode easier to read. Really? I look at \relative c,, { c4 g' a b e f' g' a, b,, c’ } and I can’t immediately tell which octave the last c is in. Looking at c,,4 g,, a,, b,, e, f g' a b,, c it’s perfectly clear right away. Chee

Re: Jianpu Notation

On 4/22/15 10:57 PM, "Super-User" wrote: >Seheme, as a dialect of Lisp, can be annotated with ;; so that our Scheme >codes implementing Jianpu can be documented as well. Comments in the code are not the documentation I am talking about. The JianpuStaff should be added to the Internals Referen

Re: What is the problem with "\relative"? (Was: Do we really offer the future?)

Hi Federico, > If you structure your files in a way that causes relative mode to produce > side-effects, you can still enter in relative mode and then convert in > absolute mode when you've finished (Frescobaldi can do it). I find it just as easy to enter code in absolute mode, so why should I

Re: "Instrument" as first-class citizen

Hi Carl (et al.), >> It doesn't help that many things are implicit and based on contexts which >> are invisible and undocumented > Hmm. I have a bit more trouble understanding this. I infer that he (correctly) means how \version "2.19.18" \score { \new Voice c' } \score { \new Staf

Re: "Instrument" as first class citizen

On Thu, 23 Apr 2015 09:50:05 +0200, Xavier Scheuer wrote: On 23 April 2015 at 04:28, Gilles wrote: On Wed, 22 Apr 2015 19:17:53 -0700, Flaming Hakama by Elaine wrote: [...] Without getting too technical, objects are things that you can create, have properties and relationships with other

Re: Jianpu Notation

David:   Thank you for started the jianpu notation.  I also love it to call "JianpuStaff".Paul:  Thank you for the time and patience and effort that make jianpu notation possible.Carl: Thank you suggestion to add to lilypond core. Thank you for pointing out a1soft software program. I will have a

Re: Standard LilyPond score structure (Was: How do new users feel about LilyPond's documentation?)

On Wed, 22 Apr 2015 19:39:25 -0700, H. S. Teoh wrote: On Thu, Apr 23, 2015 at 04:19:08AM +0200, Gilles wrote: On Wed, 22 Apr 2015 21:53:42 -0400, Kieren MacMillan wrote: [...] >So, to output a simple 16-bar lead sheet, a user should always [be >forced to] create 3 files (voice.ily, chords.ily,

Re: Jianpu Notation

Good morning Paul, Thank you very much for you jianpu4.ly. I run your jianpu-test.ly and sportted one note not the same in key C and key D.  The 2nd note on third measure - a dot below the horizontal bar is missing in key D. I appreciate very much that you to take time and patient working out jia

Re: Cross staff beaming warning

Pierre, Completely brilliant my good man! Andrew On 23 April 2015 at 20:48:39, Pierre Perol-Schneider (pierre.schneider.pa...@gmail.com) wrote: Hi Andrew, If it happens only once, simply add: %% suppress warning : #(ly:set-option 'warning-as-error #f) #(ly:expect-warning (_ "weird stem size

Re: Do we really offer the future?

Calixte: ... > Or have a script/feature/tool that automatically counts measures : it would > be able to put bar numbers in comment, ... You can try: http://turkos.aspodata.se/git/musik/bin/addnum.pl it works for me... You're welcome to suggest changes. Regards, /Karl Hammar ---

Re: Introducing LV GoldenAge!

Hi Abraham, Thank you very much for your work. I'll take a closer look to the new font tonight. Cheers, Pierre 2015-04-22 23:02 GMT+02:00 tisimst : > On Wed, Apr 22, 2015 at 2:46 PM, David Bellows [via Lilypond] <[hidden > email] > wrote: >

Re: Cross staff beaming warning

Hi Andrew, If it happens only once, simply add: %% suppress warning : #(ly:set-option 'warning-as-error #f) #(ly:expect-warning (_ "weird stem size, check for narrow beams")) before the score bloc. Hope I understood you well, HTH too, Cheers, Pierre 2015-04-23 6:41 GMT+02:00 Andrew Bernard : >

Re: Paper size survey

Reinhold: > Am 2015-04-23 um 12:05 schrieb k...@aspodata.se: > > I staple the A3's in the middle with an ordinary stapler (without > > using it's anvil(?)) on a medium soft board (so the staples gets > > through) and fold the staple? pins on the inside flat, > > For this, I can really recommend

  1   2   >