On 10/30/19, 5:13 PM, "Hans Åberg" wrote:
> On 30 Oct 2019, at 22:14, Carl Sorensen wrote:
>
>The snippets should be LGPL for being includable under other licenses,
I believe, because the processed part remains in the output, and thus
copyrightable. Thus, they play
I believe these are called Scaled Degrees in English.
https://en.wikipedia.org/wiki/Degree_(music)
I'm not sure how they correspond with the Reimannian names, but here they
are:
1 - Tonic
2 - Supertonic
3 - Mediant
4 - Subdominant
5 - Dominant
6 - Submediant
b7 - Subtonic
7 - Leading tone
Urs:
...
> One of the main issues we have at play here (and that has been discussed
> by others in this thread) is that tools like LilyPond and LaTeX blur the
> lines between source, program, and document.
>
> The arguments that are expressed *for* a requirement to license the PDF
> (etc.)
> On 30 Oct 2019, at 21:41, Thomas Morley wrote:
>
> Am Mi., 30. Okt. 2019 um 19:44 Uhr schrieb Graham King
> :
>
>> Harm, I'm afraid I'm struggling with "#(ly:make-moment -3)"
>>
>> The NR[2] shows four arguments to ly:make-moment, describes two of them, and
>> then speaks a little
Since I was off for nearly a day there may well be aspects I missed when
trying to read through the whole thread, but I have the feeling that
some thoughts still haven't been expressed.
Am 30.10.19 um 12:27 schrieb Urs Liska:
Sorry for being short: what you say is very much hiw I meant it but
> On 30 Oct 2019, at 22:14, Carl Sorensen wrote:
>
>The snippets should be LGPL for being includable under other licenses, I
> believe, because the processed part remains in the output, and thus
> copyrightable. Thus, they play the same role as the Bison skeleton file and
> GCC
> On 30 Oct 2019, at 23:36, David Kastrup wrote:
>
> Hans Åberg writes:
>
>>> On 30 Oct 2019, at 23:05, David Kastrup wrote:
>>>
>>> Hans Åberg writes:
>>>
The snippets should be LGPL for being includable under other licenses,
I believe, because the processed part remains in
Dear Sam
I an looking for the Riemannian approach. Can you help me?
On Wed, 2019-10-30 at 18:30 -0400, Sam Bivens wrote:
> Hi Karsten,
> The Riemannian system isn't as widely used among English-speaking circles as
> it
> is in German-speaking circles. Are you looking for the non-Riemannian
>
ptoye wrote
> What I want is the first quaver sf and the hairpin to finish before the
> next quaver, so that the 3rd quaver is at the same dynamic as the 2nd
> one.
>
> Here's a better MWV
>
> \version "2.19.52"
> \language "english"
> {
> <<
> \new Staff {
> \time 2/4
> \clef
Hans Åberg writes:
>> On 30 Oct 2019, at 23:05, David Kastrup wrote:
>>
>> Hans Åberg writes:
>>
>>> The snippets should be LGPL for being includable under other licenses,
>>> I believe, because the processed part remains in the output, and thus
>>> copyrightable. Thus, they play the same
Hans Åberg writes:
>> On 30 Oct 2019, at 18:48, Carl Sorensen wrote:
>>
>> This says to me that you can consider LSR snippets as part of the
>> code used to create music (any music, not just your specific music).
>> You can then put your specific music in a separate file, with
>> separate
On 10/30/19, 3:17 PM, "Hans Åberg" wrote:
> On 30 Oct 2019, at 22:14, Carl Sorensen wrote:
>
>>The snippets should be LGPL for being includable under other
licenses, I believe, because the processed part remains in the output, and thus
copyrightable. Thus, they play
On 10/30/19, 3:10 PM, "Hans Åberg" wrote:
> On 30 Oct 2019, at 18:48, Carl Sorensen wrote:
>
>> In general this is legally impossible; copyright law does not give you
any say in the use of the output people make from their data using your
program. If the user uses your
Hi Carl,
Carl Sorensen-3 wrote
> The two big issues I saw were font embedding and clipping the bounding
> box. It seems like we ought to be able to adjust both of those in the svg
> output.
> Would it be possible to modify the effects of lilypond-book-preamble.ly on
> .svg files?
LilyPond
Hi Karsten,
The Riemannian system isn't as widely used among English-speaking circles
as it is in German-speaking circles. Are you looking for the non-Riemannian
translations for these terms (we tend to use Roman numerals), or would you
prefer to keep the Riemannian approach?
Sam
On Wed, Oct 30,
Hi Carl,
Am 30.10.2019 um 18:34 schrieb Carl Sorensen:
The two big issues I saw were font embedding and clipping the bounding box. It
seems like we ought to be able to adjust both of those in the svg output.
Would it be possible to modify the effects of lilypond-book-preamble.ly on .svg
> On 30 Oct 2019, at 23:05, David Kastrup wrote:
>
> Hans Åberg writes:
>
>> The snippets should be LGPL for being includable under other licenses,
>> I believe, because the processed part remains in the output, and thus
>> copyrightable. Thus, they play the same role as the Bison skeleton
Am Mi., 30. Okt. 2019 um 19:44 Uhr schrieb Graham King
:
> Harm, I'm afraid I'm struggling with "#(ly:make-moment -3)"
>
> The NR[2] shows four arguments to ly:make-moment, describes two of them, and
> then speaks a little obtusely of the _second_ argument to ly:make-moment
> being possibly
> On 30 Oct 2019, at 22:28, Carl Sorensen wrote:
>
>> On 10/30/19, 3:17 PM, "Hans Åberg" wrote:
>>
>>> On 30 Oct 2019, at 22:14, Carl Sorensen wrote:
>>>
The snippets should be LGPL for being includable under other licenses, I
believe, because the processed part remains in
> On 30 Oct 2019, at 22:14, Carl Sorensen wrote:
>
>>The snippets should be LGPL for being includable under other licenses, I
>> believe, because the processed part remains in the output, and thus
>> copyrightable. Thus, they play the same role as the Bison skeleton file and
>> GCC
> On 30 Oct 2019, at 18:48, Carl Sorensen wrote:
>
>> In general this is legally impossible; copyright law does not give you any
>> say in the use of the output people make from their data using your program.
>> If the user uses your program to enter or convert her own data, the
>>
Hi Henning,
thanks for your hints.
Henning Hraban Ramm-3 wrote
> You can also use Inkscape on the command line. The call is like
> inkscape -z -f input.pdf -A output.svg
On my PC, this creates a SVG file that even Inkscape cannot read.
I already experimented with
inkscape -z -f input.pdf -l
On 10/30, Karsten Reincke wrote:
> 1) I did not refer to the libstdc or anything else for which indeed
> the gcc runtime exception can be used. I am talking about the a bit
> abstract case of using a GPL licensed library or module or snippet as
> base of ones work compiled by the GCC to complere
From: Karsten Reincke
Date: Wednesday, October 30, 2019 at 9:02 AM
To: Henning Hraban Ramm , lilypond-user
Cc:
Subject: Re: LilyPond, LilyPond snippets and the GPL
On Wed, 2019-10-30 at 15:08 +0100, Henning Hraban Ramm wrote:
[...]
It’s the same if you publish a book using TeX:
No, it isn't.
> Am 2019-10-30 um 16:35 schrieb Klaus Blum :
>
> For Mac, I don't have any idea. My knowledge about Macs is exactly zero.
As Nick stated, pfd2svg is available via HomeBrew, but also via MacPorts.
Mac users that are able to use LilyPond should be able to use one of those or
even compile it on
> On 30 Oct 2019, at 00:05, Graham King wrote:
>
>>
>> On 29 Oct 2019, at 22:12, Thomas Morley wrote:
>>
>> Am Di., 29. Okt. 2019 um 16:28 Uhr schrieb Graham King
>> :
>>>
>>>
>>> This unanswered part of Reggie's question in [1] lead me to re-scratch an
>>> old itch. In manuscripts and
Casey Driessen and Oriole Saña have developed some new symbols for notating
the violin/fiddle technique called chopping.
You can see .png images of these symbols here:
https://drive.google.com/drive/folders/15b2tNfqkp9jkpd1T3r1lcgulSbNfwWQ7
More background on the technique is available at:
On 10/30/19, 11:48 AM, "Karsten Reincke" wrote:
2) Your polemic attack is wrong and unfair. If you had read my posts
carefully,
you would know [and probably you know it, but withhold this aspect], that I
offered URS already the opportunity to integrate my coming lib -
On Wed, 2019-10-30 at 09:41 -0700, ma...@masonhock.com wrote:
> On 10/30, Karsten Reincke wrote:
> > Here, the analogy of gcc and Lilypond matches perfectly: As we are
> > must distribute binaries which are compiled by the gcc on the base a
> > GPL licensed source code, we must also distribute the
On 10/30/19, 9:35 AM, "Klaus Blum" wrote:
Dear OOoLilyPond users,
I'm planning to add a new option to OOoLilyPond.
At the moment, we only have the choice between three file formats:
- PNG is a bitmap format with the obvious quality drawbacks.
- EPS can only
On 10/30, Karsten Reincke wrote:
> Here, the analogy of gcc and Lilypond matches perfectly: As we are
> must distribute binaries which are compiled by the gcc on the base a
> GPL licensed source code, we must also distribute the binaries (png)
> which are compiled by LilyPond on the base of a GPL
On Wednesday, 30 October 2019 15:35:34 GMT Klaus Blum wrote:
> For Mac, I don't have any idea. My knowledge about Macs is exactly zero.
>
>
> Am I still missing something? Do you have any more thoughts, ideas,
> recommendations, experiences, ... ?
I don't know either, but the thing about MacOS
Re: Hairpin.minimum-length gives wrong output
Try s8\sf\> s8-\hide\p s4 | s2 2 2 2 2 2 2 2 2 2 2 2
--
Phil Holmes
- Original Message -
From: Peter Toye
To: Phil Holmes ; lilypond-user@gnu.org
Sent: Wednesday, October 30, 2019 3:51 PM
Subject: Re: Hairpin.minimum-length
Sorry, a typo. Both lines should have \! rather than \p. What I want is the
first quaver sf and the hairpin to finish before the next quaver, so that the
3rd quaver is at the same dynamic as the 2nd one.
Here's a better MWV
\version "2.19.52"
\language "english"
{
<<
\new Staff {
Dear Friends;
as perhaps known, I try to refactor the LilyPond snippet
http://lsr.di.unimi.it/LSR/Snippet?id=967 originally written by Klaus Blum. It
is
already in a good shape, but it is still not a 'library. If you want to follow
the
development steps, check out
Hairpin.minimum-length gives wrong output
Not quite sure of the output you want here. Your 2 lines of your example
aren't the same since the top line has a piano dynamic on it and the lower line
doesn't. Is the first quaver supposed to have the sf immediately below it? If
so, where do you
Dear OOoLilyPond users,
I'm planning to add a new option to OOoLilyPond.
At the moment, we only have the choice between three file formats:
- PNG is a bitmap format with the obvious quality drawbacks.
- EPS can only be used with OpenOffice (not LibreOffice) and cannot be
displayed on screen.
Dear Robin,
Thanks - I see from the bug reports that it's fixed in LP 2.21 but I don't know
the release date for that.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Wednesday, October 30, 2019, 2:58:25 PM, Robin Bannister wrote:
> Peter Toye wrote:
>>
On Wed, 2019-10-30 at 15:08 +0100, Henning Hraban Ramm wrote:
> [...]
> It’s the same if you publish a book using TeX:
No, it isn't.
> While original TeX is PD and some other parts have their own licenses, those
> never apply to the contents of your book or the PDF or printed version of it,
This minimal criminal seems to give wrong output. I want to make sure that the
hairpin lasts for exactly one quaver (1/8 note). The first line gives a warning
message that the hairpin is too short. The second line adjusts the length of
the hairpin but it's now too long.
To try it out you may
Peter Toye wrote:
Any ideas on how to get just the tied note showing a repeat
https://lists.gnu.org/archive/html/lilypond-user/2017-03/msg00226.html
Cheers,
Robin
Am 2019-10-30 um 13:06 schrieb David Kastrup :
>
> You are correct that you cannot license the source under any license
> other than the GPL if you are going to distribute it containing GPL
> licensed snippets (the LSR snippets are PD, the Notation Reference
> contents GFDL). But the PDF
> On 30 Oct 2019, at 02:15, Carl Sorensen wrote:
>
>Frescobaldi 3 (without Rumor) also supports MIDI input.
>
> Yes, but it only gets the notes. Rumor will also capture durations.
For what it is worth, one can record it in GarageBand, select the track and
copy, which produces a textual
Il giorno mer 30 ott 2019 alle 01:15, Carl Sorensen
ha scritto:
Frescobaldi 3 (without Rumor) also supports MIDI input.
Yes, but it only gets the notes. Rumor will also capture durations.
From reading the Frescobaldi docs, there used to be a Rumor plugin.
Now it appears we no longer
I'm trying to engrave some music where there is an alternative repeat end, and
a single note within a chord is tied over. The tie works for the 1st
alternative, but not for the 2nd. But adding \repeatTie in the alternative
produces ties for all notes in the chord, and not just the tied one.
I'm trying to engrave some piano music where the composer (or probably the
original 19th century engraver) has saved time by putting accents midway
between the staves (see attached snip). I've tried to do this in a dynamic
staff with LP code like
s4->
but this gives warning messages, although
Am 30. Oktober 2019 12:45:06 MEZ schrieb Karsten Reincke :
>Dear Elaine
>
>On Tue, 2019-10-29 at 18:13 -0700, Flaming Hakama by Elaine wrote:
>> [...]
>> It seems you think that, if you use code from the LSR as part of your
>input
>> files, that you are obligated to distribute both the input
Karsten Reincke writes:
> Many thanks for your comment. It contains an important hint. BUt it is a bit
> apart
> from my crucial point:
>
> I am not arguing that my LilyPond work (or a snippet) is covered by
>the GPL because it is 'executed' by LilyPond. I argue that my code is
>covered by the
Karsten Reincke writes:
> On Wed, 2019-10-30 at 01:36 +0100, David Kastrup wrote:
>> Karsten Reincke writes:
>>
>> > [...]
>> >
>> > Hence, if I use a piece of software as library, snippet, or module,
>> > then I am using the advantage that I do not have to program that code
>> > by myself. I
Dear Elaine
On Tue, 2019-10-29 at 18:13 -0700, Flaming Hakama by Elaine wrote:
> [...]
> It seems you think that, if you use code from the LSR as part of your input
> files, that you are obligated to distribute both the input files and the
> resulting PDF/MIDI files under the GPL.
YES, if the
Sorry for being short: what you say is very much hiw I meant it but not all.
I'll clarify later but am currently on the road. Maybe tonight of tomorrow.
Am 30. Oktober 2019 12:09:37 MEZ schrieb Karsten Reincke :
>Dear Urs;
>
>many thanks for your clever thoughts! You brought up a very seductive
Dear Urs;
many thanks for your clever thoughts! You brought up a very seductive argument,
which I therefore will only summarize here for being sure that I've understood
you
correctly. May I condense your line of argumentation in the following way?
You point out that there could be a function in
On Wed, 2019-10-30 at 01:36 +0100, David Kastrup wrote:
> Karsten Reincke writes:
>
> > [...]
> >
> > Hence, if I use a piece of software as library, snippet, or module,
> > then I am using the advantage that I do not have to program that code
> > by myself. I am saving costs and time. A very
On Wed, 2019-10-30 at 00:55 +, Carl Sorensen wrote:
>
> On 10/29/19, 5:46 PM, "David Kastrup" wrote:
>
> Karsten Reincke wrotes:
>
>[...]
> >
> > [4] But if a GPL licensed LilyPond snippet is used by another LilyPond
> > code (either by a functional call into the
54 matches
Mail list logo
