Hello,
here’s a kind of pet peeve of mine: With a warning like
warning: octave check failed; expected "a", found: "a,"
I always have to look twice what the difference between the two is. It
might be easier to read as
warning: octave check failed; expected "a" and found "a,"
(or: ‘but found’)
> On 11 Nov 2017, at 12:52, Urs Liska wrote:
>
>
>
> Am 11.11.2017 um 12:30 schrieb David Kastrup:
>> I find "grouping" without "beat" fine. I could have been responsible
>> for the terminology in the code (pretty sure I wasn't, but it matches
>> the terminology I use quite better).
>>
>> N
> On 11 Nov 2017, at 12:52, Urs Liska wrote:
>
>
>
> Am 11.11.2017 um 12:30 schrieb David Kastrup:
>> I find "grouping" without "beat" fine. I could have been responsible
>> for the terminology in the code (pretty sure I wasn't, but it matches
>> the terminology I use quite better).
>>
>> N
Am 11.11.2017 um 15:07 schrieb Hans Åberg:
On 11 Nov 2017, at 12:52, Urs Liska wrote:
Am 11.11.2017 um 12:30 schrieb David Kastrup:
I find "grouping" without "beat" fine. I could have been responsible
for the terminology in the code (pretty sure I wasn't, but it matches
the terminology
Am 11.11.2017 um 21:23 schrieb David Kastrup:
Urs Liska writes:
Am 11.11.2017 um 15:30 schrieb Carl Sorensen:
When I look at http://openmusictheory.com/meter.html , the thing that we
call a beat in the c++ code is what openmusictheory calls a pulse. And
what we call a beat group is what th
> On 11 Nov 2017, at 12:52, Urs Liska wrote:
>
>
>
> Am 11.11.2017 um 12:30 schrieb David Kastrup:
>> I find "grouping" without "beat" fine. I could have been responsible
>> for the terminology in the code (pretty sure I wasn't, but it matches
>> the terminology I use quite better).
>>
>> N
Am 11.11.2017 um 13:25 schrieb Simon Albrecht:
> On 11.11.2017 12:30, David Kastrup wrote:
>
>> I have a hard time seeing a "beat" as something that can have different
>> lengths.
>>
>
> Musical notation isn’t well-defined in a mathematical or programming
> sense, so there are no such strict rules
Am 11.11.2017 um 13:25 schrieb Simon Albrecht:
On 11.11.2017 12:30, David Kastrup wrote:
I have a hard time seeing a "beat" as something that can have different
lengths.
Musical notation isn’t well-defined in a mathematical or programming
sense, so there are no such strict rules as all beat
Am 11.11.2017 um 13:15 schrieb David Kastrup:
Urs Liska writes:
Am 11.11.2017 um 12:30 schrieb David Kastrup:
I find "grouping" without "beat" fine. I could have been responsible
for the terminology in the code (pretty sure I wasn't, but it matches
the terminology I use quite better).
Now
On 11.11.2017 12:30, David Kastrup wrote:
I have a hard time seeing a "beat" as something that can have different
lengths.
Musical notation isn’t well-defined in a mathematical or programming
sense, so there are no such strict rules as all beats of a measure
having to be the same length.
If n
Urs Liska writes:
> Am 11.11.2017 um 12:30 schrieb David Kastrup:
>> I find "grouping" without "beat" fine. I could have been responsible
>> for the terminology in the code (pretty sure I wasn't, but it matches
>> the terminology I use quite better).
>>
>> Now I have certainly not gotten an Engl
Am 11.11.2017 um 12:52 schrieb Urs Liska:
"Beat" also refers to what a conductor would do. the 3+3+2 from my
example would be given as three "beats" by the conductor. Maybe your
perception of "beat" as necessarily regular comes from the fact that
in German we use "beat" too, but usually refer
Am 11.11.2017 um 12:30 schrieb David Kastrup:
I find "grouping" without "beat" fine. I could have been responsible
for the terminology in the code (pretty sure I wasn't, but it matches
the terminology I use quite better).
Now I have certainly not gotten an English music education, so can
some
Urs Liska writes:
> Am 11.11.2017 um 11:42 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> So, now the first question ...
>>>
>>> The terminology of baseMoment, beats and groups is inconsistent
>>> between the NR
>>> (http://lilypond.org/doc/v2.19/Documentation/notation/beams#setting-automati
On 2017/11/11 10:36:16, thomasmorley651 wrote:
On 2017/11/11 10:11:39, Jean-Charles wrote:
> Didn't you forget to amend the English version of changes.tely?…
I changed every changes.tely containing addLyrics in _master_
The english version is empty apart from defaults, because it was moved
to
Am 11.11.2017 um 11:42 schrieb David Kastrup:
Urs Liska writes:
So, now the first question ...
The terminology of baseMoment, beats and groups is inconsistent
between the NR
(http://lilypond.org/doc/v2.19/Documentation/notation/beams#setting-automatic-beam-behavior)
and the code. The questi
Urs Liska writes:
> So, now the first question ...
>
> The terminology of baseMoment, beats and groups is inconsistent
> between the NR
> (http://lilypond.org/doc/v2.19/Documentation/notation/beams#setting-automatic-beam-behavior)
> and the code. The question is, what are the components of the
>
Reviewers: Jean-Charles,
Message:
On 2017/11/11 10:11:39, Jean-Charles wrote:
Didn't you forget to amend the English version of changes.tely?…
I changed every changes.tely containing addLyrics in _master_
The english version is empty apart from defaults, because it was moved
to the stable 2.18
Hi all,
I'm writing an assessment how the beaming-pattern code could be redone
properly, which is pretty much necessary. Apart from some minor problems
at the surface at least the concept of (subdivide the) beaming of
tuplets it completely messed up. In fact, beam subdivision is simply
unusab
Didn't you forget to amend the English version of changes.tely?…
https://codereview.appspot.com/332110043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
20 matches
Mail list logo
