Did I miss anything ? It might be true that
I ought to be more explicit about what people are allowed to do with these
scores, but I don't think I'm giving away anything serious here. The music
is copyrighted, one cannot just play it nor record it without my consent,
The score is freely
Hi,
When I have triplet, the 3 is in the same direction of the stems (eg. 3 is at
the bottom if stem are down) . However I like it at the side of the note head,
which means the opposite direction the stem are facing. (eg. I would like the 3
to be above the notes when stems are down).
If I were
Hi at all,
the following problem was a problem to me, but maybe some other
lilypond-users could have the same:
How is it possible to switch off a shiftoff at note collision?
Using version 2.2.6 the following happened:
The real good solution for prohibiting note collisions was a feature,
which I
On Fri, 17 Dec 2004 23:27:38 +0100
[EMAIL PROTECTED] wrote:
> In other word, by making the music available, I just remove the hurdle
> of having to retranscribe it by ear. I just make my music easier to find,
Thank you for doing that. I liked very much the style, the drive,
the feeling and of the
Well, since I started this argument by putting my scores online,
please let me explain my own little rationale...
- I'm no Mozart, I'm no Beatle. I don't think that the music
I write will ever be valuable enough for the score edition
business to make any sense for me.
- The only intere
On Friday 17 December 2004 21.32, David Raleigh Arnold wrote:
> On Friday 17 December 2004 02:14 pm, Erik Sandberg wrote:
> > On Friday 17 December 2004 17.49, David Raleigh Arnold wrote:
> > > On Friday 17 December 2004 05:46 am, Erik Sandberg wrote:
> > >
> > > No. So what if it did? What prote
On 17-Dec-04, at 12:53 AM, [EMAIL PROTECTED] wrote:
I see that I am supposed to use the verb "\set" and not "\override" to
"set" (obviously!)
a property.
Actually, you can use either.
Also, please keep lilypond-related questions on the mailist ("reply to
group",
instead of simply reply) ; that
> > The copyright *is* the license, which belongs exclusively
> > to the copyright holder. That's the whole idea of a copyright. Don't
> > attempt to share it with all and sundry, only with BMI/ASCAP or the like
> if
> > you want. A user license would amount to assigning it.
>
> Sorry, I didn't
On Friday 17 December 2004 17.49, David Raleigh Arnold wrote:
> On Friday 17 December 2004 05:46 am, Erik Sandberg wrote:
> > On Friday 17 December 2004 01.24, David Raleigh Arnold wrote:
> > >
> > > A license *might* protect some evildoer ripping you off but it won't
> > > protect you, You don't
On Friday 17 December 2004 11:44 am, you wrote:
> David, I was searching on 'harmonica' in the Lilypond archives, and your
> name came up. I'm also interested in harmonica notation. Can you briefly
> tell me the status of your work with Lilypond on this? Can you send me an
> example of a harmonica
On Friday 17 December 2004 17.19, David Raleigh Arnold wrote:
> On Friday 17 December 2004 09:34 am, Michael Kallas wrote:
> > Would it maybe make sense to make \version
> > numbers in the .ly files mandatory?
> > Or at least have some --Wall / --strict feature
> > that fails if it is not set?
> >
On Friday 17 December 2004 09:34 am, Michael Kallas wrote:
> Would it maybe make sense to make \version
> numbers in the .ly files mandatory?
> Or at least have some --Wall / --strict feature
> that fails if it is not set?
> That way, you would't forget to insert the version
> and have to learn the
Would it maybe make sense to make \version
numbers in the .ly files mandatory?
Or at least have some --Wall / --strict feature
that fails if it is not set?
That way, you would't forget to insert the version
and have to learn the hard way after years
that it would have been good to do so for com
On Friday 17 December 2004 01.24, David Raleigh Arnold wrote:
> On Thursday 16 December 2004 05:16 pm, Erik Sandberg wrote:
> > On Thursday 16 December 2004 22.10, [EMAIL PROTECTED] wrote:
> > > (This does not mean that the music is not copyrighted, or that it is
> > > not subject to execution righ
Mats Bengtsson wrote:
I think it's time for you to start reading the section of the manual
called "Changing Defaults". Among others, you will learn that a
\context{...} declaration specifies/changes the definition of a
single context. So, you cannot change the definition of two
different contexts i
15 matches
Mail list logo
