On 10/29/19 11:28 PM, Solomon Foster wrote:
"Christopher R. Maden" writes:
The important part is to have files for each tune that define all
the info but which don’t actually *do* anything. That gives you
the flexibility to do different things with that info in different
contexts.
Is there
"Christopher R. Maden" writes:
>
> Message: 3
> Date: Tue, 29 Oct 2019 14:21:48 -0400
> From: "Christopher R. Maden"
> To: lilypond-user@gnu.org
> Subject: Re: Doing A Fiddle Tunebook in Lilypond
> Message-ID: <3268a110-e979-6431-9eb8-5cbe4c20b...@maden.org>
> Content-Type: text/plain;
Hi Mike,
On Tue, Oct 29, 2019 at 1:34 PM Mike Kilmer wrote:
> I did something along these lines a couple of years ago using something
> called lytex, which if I recall correctly sort of combines Tex typesetting
> with Lilypond.
>
> You can check out the main file (and entire codebase) here:
>
Hi Ralph,
On Tue, Oct 29, 2019 at 10:22 PM Ralph Palmer
wrote:
> Please take a look at the collection I've done of fiddle tunes for viola,
> and let me know if it looks like what you want. I'm on a long road trip,
> and won't have access to my computer for another month, but I think I can
>
On Tue, Oct 29, 2019, 11:16 AM Solomon Foster wrote:
> Hi all,
>
> I've been using Lilypond to render fiddle tunes for nearly a decade now,
> and I'm looking at taking the next step -- namely making a proper, large
> scale tunebook with it. While the book I'm working on right now has
> hundreds
On 10/28/19, 11:36 PM, "Federico Bruni" wrote:
Il giorno lun 28 ott 2019 alle 01:34, Carl Sorensen
ha scritto:
> I have a friend who has seen my lilypond work and would like to get
> involved with lilypond.
>
> He would like to use a MIDI keyboard, rather
> From: Karsten Reincke
> To: lilypond-user
> Cc: k.rein...@fodina.de
> Bcc:
> Date: Wed, 30 Oct 2019 00:06:32 +0100
> Subject: LilyPond, LilyPond snippets and the GPL
> By my last post, I, unfortunately, evoked a discussion concerning
> LilyPond, LilyPond snippets, and the GPL which actually
On 10/29/19, 5:46 PM, "David Kastrup" wrote:
Karsten Reincke writes:
> By my last post, I, unfortunately, evoked a discussion concerning
> LilyPond, LilyPond snippets, and the GPL which actually did not belong
> to the original topic. During this discussion Harm stated,
Karsten Reincke writes:
> On Wed, 2019-10-30 at 00:46 +0100, David Kastrup wrote:
>> [...]
>>
>> I disagree with your assessment that calling any code/function makes
>> the
>> work doing so a derivative of that code (that would concern using
>> OpenLilyLib code). [...]
>
> I agree with you,
Hi Massimiliano,
See: http://lsr.di.unimi.it/LSR/Item?id=553
E.g.:
\version "2.19.83"
\fixed c' {
\override Beam.gap-count = #3
\override Beam.gap = #1
\repeat tremolo 8 { des32 \once\omit Stem \tweak duration-log #3 g }
}
Cheers,
Pierre
Le mer. 30 oct. 2019 à 00:24, Massimiliano Viel a
On Wed, 2019-10-30 at 00:46 +0100, David Kastrup wrote:
> [...]
>
> I disagree with your assessment that calling any code/function makes
> the
> work doing so a derivative of that code (that would concern using
> OpenLilyLib code). [...]
I agree with you, that the question, when and how a piece
Hi Karsten,
first of all let me comment on your final stance: yes, I think you have
answered respectfully, appreciatively and clearly. And I have also read
your longer post. But I think there is one single flawed thought you
build your argumentation on. I'll leave most of your statements
> On 29 Oct 2019, at 22:12, Thomas Morley wrote:
>
> Am Di., 29. Okt. 2019 um 16:28 Uhr schrieb Graham King
> :
>>
>> "...and most important you want tight space between all notes as
>> though it's not allowing the space for barlines and more."
>>
>> This unanswered part of Reggie's question
Karsten Reincke writes:
> By my last post, I, unfortunately, evoked a discussion concerning
> LilyPond, LilyPond snippets, and the GPL which actually did not belong
> to the original topic. During this discussion Harm stated, that „maybe
> LSR should better use GPL 3, not this deprecated one
Hi everybody,
I wrote my first score with Lilypond and still a newbie.
I think the most efficient way to write a tremolo is the one adopted by
Stockhausen. I send an example as attachment.
The value is indicated only on the first note, while the second one is just a
back unstemmed note.
Is there
By my last post, I, unfortunately, evoked a discussion concerning
LilyPond, LilyPond snippets, and the GPL which actually did not belong
to the original topic. During this discussion Harm stated, that „maybe
LSR should better use GPL 3, not this deprecated one (Public Domain)“.
Urs asked whether
Am Di., 29. Okt. 2019 um 16:28 Uhr schrieb Graham King
:
>
> "...and most important you want tight space between all notes as
> though it's not allowing the space for barlines and more."
>
> This unanswered part of Reggie's question in [1] lead me to re-scratch an old
> itch. In manuscripts and
> Am 2019-10-29 um 20:11 schrieb ma...@masonhock.com:
>
> On 10/29, Urs Liska wrote:
>> Well, the LSR website explicitly states that it's contents is in the
>> public domain. If I read correctly your email this would have to be
>> considered illegal, especially given that many snippets there
On 10/29, Urs Liska wrote:
> Well, the LSR website explicitly states that it's contents is in the
> public domain. If I read correctly your email this would have to be
> considered illegal, especially given that many snippets there are
> uploaded not by their original authors but by someone who
> Am 2019-10-29 um 18:34 schrieb Mike Kilmer :
>
> I did something along these lines a couple of years ago using something
> called lytex, which if I recall correctly sort of combines Tex typesetting
> with Lilypond.
>
> There’s also something called lilypond-book, but I think that’s more
On 10/29/19 1:14 PM, Solomon Foster wrote:
I've been using Lilypond to render fiddle tunes for nearly a decade
now, and I'm looking at taking the next step -- namely making a
proper, large scale tunebook with it. While the book I'm working on
right now has hundreds of tunes, it's not mine to
Hi Sol.
Looks great!
I did something along these lines a couple of years ago using something called
lytex, which if I recall correctly sort of combines Tex typesetting with
Lilypond.
You can check out the main file (and entire codebase) here:
Hi all,
I've been using Lilypond to render fiddle tunes for nearly a decade now,
and I'm looking at taking the next step -- namely making a proper, large
scale tunebook with it. While the book I'm working on right now has
hundreds of tunes, it's not mine to redistribute, so I've put together a
"...and most important you want tight space between all notes as
though it's not allowing the space for barlines and more."
This unanswered part of Reggie's question in [1] lead me to re-scratch an old
itch. In manuscripts and old printed editions of mensural notation, notes and
rests are
Dick Seabrook writes:
> Perhaps we need a "graffiti law" -- that anything written in a public place
> or on
> someone else's property becomes the property of the public, or owner
> respectively.
> Otherwise what right do owners have to clean graffiti off their buildings?
You are confusing
> On 29 Oct 2019, at 13:08, Stanton Sanderson wrote:
>
> Also runs for me, except the page numbers are not images but an increasing
> number of boxed
> question marks. (Mac- OS 10.14) - Stan
I tested with MacPorts lilypond-devel on MacOS 10.16. Maybe some font missing.
Yes, ... international copyright lawyer required for even such a simple
thing. In many cases it may be better to put nothing - as the GNU lists do
- and let national law deal with problems and interpretation. Whatever you
put, some jurisdiction somewhere will find it to be in error, and that just
Perhaps we need a "graffiti law" -- that anything written in a public place
or on
someone else's property becomes the property of the public, or owner
respectively.
Otherwise what right do owners have to clean graffiti off their buildings?
Dick S.
On Tue, Oct 29, 2019 at 4:06 AM Andrew Bernard
On 10/29/2019 8:08 AM, Stanton Sanderson wrote:
Also runs for me, except the page numbers are not images but an increasing
number of boxed
question marks. (Mac- OS 10.14) - Stan
On Oct 28, 2019, at 9:36 PM, David Nalesnik wrote:
Hans,
On Mon, 28 Oct 2019, 3:21 p.m. Hans Åberg, wrote:
Also runs for me, except the page numbers are not images but an increasing
number of boxed
question marks. (Mac- OS 10.14) - Stan
> On Oct 28, 2019, at 9:36 PM, David Nalesnik wrote:
>
> Hans,
>
> On Mon, 28 Oct 2019, 3:21 p.m. Hans Åberg, wrote:
>
> > On 28 Oct 2019, at 16:02, David
though I generally loathe such usage terms, wouldn't some clause in the
list's ToS to the effect that use of the list grants some nonexclusive but
unrestricted right to copy/use that material alleviate these concerns?
Those kinds of clauses are part of every online email service, for example
You need an international copyright lawyer. This is a fraught topic.
On list email, I recently set up a big sophisticated mail server to support
GNU Mailman 3 mailing lists, and moved an archive from a previous list with
100,000 posts across. Extensive discussion with my colleagues in that
Am 29. Oktober 2019 02:57:30 MEZ schrieb ma...@masonhock.com:
>On 10/28, Klaus Blum wrote:
>> AFAIK, the public domain licence also applies to anything published
>on
>> the LY mailing list. I hope that I'm not wrong as I don't intend to
>> "steal" other people's code...
>
>I don't think that
33 matches
Mail list logo
