Re: 3/4 time

[jw. Verhagen]

 Sincerely thanks

Sent from my iPhone

> On Apr 12, 2020, at 8:56 AM, Noeck  wrote:
> 
> Dear Sylvia,
> 
>> Am 12.04.20 um 17:39 schrieb Sylvia Cassel:
>> f1:maj7 a1:aug7 bes1:maj7 d1:aug7
> 
> Your harmonies have a duration of 1 (whole note) but your measures are
> only 3 quarters long (time 3/4):
> 
> f2.:maj7 a2.:aug7 …
> 
> and you can write the duration only once if it is the same as previously:
> 
> f2.:maj7 a:aug7 …
> 
> 
> By the way, such questions should be asked on the users' list:
> lilypond-u...@gnu.org
> 
> 
> Cheers,
> Joram
> 
> 
> 
>> Am 12.04.20 um 17:39 schrieb Sylvia Cassel:
>> Hello out there,
>> Has anyone has a chance to look at this?  Am I doing something wrong or is
>> there a bug??  How can I get the chord notations over the right measure?
>> 
>> Sylvia Cassel 
>> Fri, Apr 3, 7:04 AM (9 days ago)
>> to bug-lilypond
>> % In doing a lead sheet in 3/4 time, the melody notation comes out correctly
>> % but the chords don't line up with the measures.  They seem to assume 4/4
>> time.
>> 
>> Example:
>> 
>> \version "2.20.0"
>> \header {
>> Title = "F - Some Day My Prince Will Come"
>> composer = "Frank Churchill"
>> }
>> melody =\relative c'
>> {
>> \clef treble
>> \key f \major
>> \time 3/4
>> 
>> c2.  f2 cis4 e2 d4 d2.
>> }
>> harmonies = \chordmode
>> {
>> f1:maj7 a1:aug7 bes1:maj7 d1:aug7
>> }
>> \score {
>> <<
>> \new ChordNames {
>> \set chordChanges = ##t
>> \harmonies
>> }
>> \new Staff \melody
>>>> 
>> \layout { }
>> }
>> Thanks for any help.
>> Sylvia
>> ___
>> bug-lilypond mailing list
>> bug-lilypond@gnu.org
>> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> 
> 

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: 3/4 time

[Noeck]

Dear Sylvia,

Am 12.04.20 um 17:39 schrieb Sylvia Cassel:
> f1:maj7 a1:aug7 bes1:maj7 d1:aug7

Your harmonies have a duration of 1 (whole note) but your measures are
only 3 quarters long (time 3/4):

f2.:maj7 a2.:aug7 …

and you can write the duration only once if it is the same as previously:

f2.:maj7 a:aug7 …


By the way, such questions should be asked on the users' list:
lilypond-u...@gnu.org


Cheers,
Joram



Am 12.04.20 um 17:39 schrieb Sylvia Cassel:
> Hello out there,
> Has anyone has a chance to look at this?  Am I doing something wrong or is
> there a bug??  How can I get the chord notations over the right measure?
>
> Sylvia Cassel 
> Fri, Apr 3, 7:04 AM (9 days ago)
> to bug-lilypond
> % In doing a lead sheet in 3/4 time, the melody notation comes out correctly
> % but the chords don't line up with the measures.  They seem to assume 4/4
> time.
>
> Example:
>
>  \version "2.20.0"
> \header {
> Title = "F - Some Day My Prince Will Come"
> composer = "Frank Churchill"
> }
> melody =\relative c'
> {
> \clef treble
> \key f \major
> \time 3/4
>
> c2.  f2 cis4 e2 d4 d2.
> }
> harmonies = \chordmode
> {
> f1:maj7 a1:aug7 bes1:maj7 d1:aug7
> }
> \score {
> <<
> \new ChordNames {
> \set chordChanges = ##t
> \harmonies
>  }
> \new Staff \melody
>>>
> \layout { }
> }
> Thanks for any help.
> Sylvia
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: 3/4 time

[David Kastrup]

Sylvia Cassel  writes:

> Hello out there,
> Has anyone has a chance to look at this?  Am I doing something wrong or is
> there a bug??  How can I get the chord notations over the right measure?

Aaron Hill already posted a reply to the list.  These lists aren't
write-only dumps: if you post there, please also look there for
replies.  For likely user-level problems rather than genuine LilyPond
bugs, please try the lilypond-u...@gnu.org list first.

-- 
David Kastrup

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

3/4 time

[Sylvia Cassel]

Hello out there,
Has anyone has a chance to look at this?  Am I doing something wrong or is
there a bug??  How can I get the chord notations over the right measure?

Sylvia Cassel 
Fri, Apr 3, 7:04 AM (9 days ago)
to bug-lilypond
% In doing a lead sheet in 3/4 time, the melody notation comes out correctly
% but the chords don't line up with the measures.  They seem to assume 4/4
time.

Example:

 \version "2.20.0"
\header {
Title = "F - Some Day My Prince Will Come"
composer = "Frank Churchill"
}
melody =\relative c'
{
\clef treble
\key f \major
\time 3/4

c2.  f2 cis4 e2 d4 d2.
}
harmonies = \chordmode
{
f1:maj7 a1:aug7 bes1:maj7 d1:aug7
}
\score {
<<
\new ChordNames {
\set chordChanges = ##t
\harmonies
 }
\new Staff \melody
>>
\layout { }
}
Thanks for any help.
Sylvia
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: 3/4 time

[Aaron Hill]

On 2020-04-03 4:04 am, Sylvia Cassel wrote:
% In doing a lead sheet in 3/4 time, the melody notation comes out 
correctly
% but the chords don't line up with the measures.  They seem to assume 
4/4

time.

harmonies = \chordmode
{
f1:maj7 a1:aug7 bes1:maj7 d1:aug7
}


You are specifying whole note durations.  You need to use "f2.:maj7" not 
"f1:maj7".



-- Aaron Hill

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

3/4 time

[Sylvia Cassel]

% In doing a lead sheet in 3/4 time, the melody notation comes out correctly
% but the chords don't line up with the measures.  They seem to assume 4/4
time.

Example:

 \version "2.20.0"
\header {
Title = "F - Some Day My Prince Will Come"
composer = "Frank Churchill"
}
melody =\relative c'
{
\clef treble
\key f \major
\time 3/4

c2.  f2 cis4 e2 d4 d2.
}
harmonies = \chordmode
{
f1:maj7 a1:aug7 bes1:maj7 d1:aug7
}
\score {
<<
\new ChordNames {
\set chordChanges = ##t
\harmonies
 }
\new Staff \melody
>>
\layout { }
}
Thanks for any help.
Sylvia
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: "Problematic" conversion from MIDI: c4*5, c1 (in 3/4 time) etc.

[David Wright]

On Fri 29 Jul 2016 at 23:02:22 (+0200), Mojca Miklavec wrote:
> On 29 July 2016 at 21:55, David Wright wrote:
> > On Fri 29 Jul 2016 at 14:29:57 (+0200), Mojca Miklavec wrote:
> >> I have a midi file that I wanted to convert into scores, but the
> >> scores simply don't look right.
> >>
> >> While I have a real (relatively long) song in the MIDI, I believe that
> >> I can fully reproduce the problem with the following simple example:
> >>
> >> \score {
> >>   \new Voice = "melody" {
> >> \set Staff.midiInstrument = "accordion"
> >> \time 3/4
> >> \relative c' {
> >>   c4 c c |
> >>   c1 d4 e |
> >>   f4*5 g4 |
> >>   f2.~ | % becomes f4*5
> >>   f2 e4 |
> >>   d4*3 | % becomes d2.
> >>   c4 c2~ | % becomes c1
> >>   c2
> >> }
> >>   }
> >>   \midi { \tempo 4 = 160 }
> >>   \layout {}
> >> }
> >>
> >> (I picked accordion because one doesn't hear the duration with piano.)
> >>
> >> The idea is to make midi from the above example first (lilypond
> >> test.ly), then convert midi to scores (midi2ly test.midi -o test2.ly)
> >> and typeset again (lilypond test2.ly).
> >>
> >>
> >> The resulting MIDI file sounds right, but the typesetting of it is
> >> very strange. I get just a single quarter note printed out rather than
> >> something that takes the duration of five times a quarter.
> >>
> >> OK, that's probably expected when I consciously enter the above
> >> syntax, but not after conversion from a MIDI file.
> >>
> >> I noticed that the whole idea of the asterisk operator is to print a
> >> single unit, but to prolong it in MIDI (or for other purposes). But
> >> there's a lot of inconsistency:
> >> - if I properly enter c2.~ c2, I get c4*5 from the midi conversion
> >> - if I properly enter c2~ c2, I get c1 which is "forbidden" inside 3/4
> >> - if I sloppily enter c4*3 which would typset in a very weird way, it
> >> comes out OK after the conversion as c2.
> >>
> >> None of that makes any sense to me.
> >>
> >> Sure I can manually fix the resulting plain text file, but I was
> >> wondering if there was really no better way to get this done properly
> >> and automatically.
> >
> > In the absence of any output examples, I've attached what my system
> > produces from your source. Let us know what's incorrect.
> 
> Oh wait!
> 
> The "answer" to my question has always been there in the generated ly
> file. These are the important settings that make all the difference:
> 
> \remove "Note_heads_engraver"
> \consists "Completion_heads_engraver"
> 
> (plus of course those for rests).
> 
> The main problem is that what I do is:
> - run midi2ly (outputting absolute pitches & durations) to get the melody out
> - copy just the melody to a different file template to get exactly the
> staff arrangement I want (the default output is semi-useless for my
> particular use case)
> 
> In fact I didn't realize that I would get correct PDF if I kept those
> two settings.
> 
> This approach of copying just the melody avoids many useless settings like
> \set Staff.instrumentName = "\new:melody"
> but the two/four necessary lines were accidentally omitted.
> 
> > It looks to
> > me as if the original score is just what you (idiosyncratically) asked
> > for and the subsequent score has been "conventionalised" as one might
> > expect, because the midi performer has no way of representing your
> > odd notation.
> 
> I don't think so. I didn't try to manually inspect the dump of the
> midi file (maybe I should), but I strongly suspect that there will be
> absolutely no difference in midi irrespective of whether I enter
> c2.~c2 or c4*5.

That's what I said: the midi performer has no way of representing your
odd notation. The MIDI file has note pitches, starting times, and
durations, expressed in beats. Your "odd notation", whether it's
c2.~c2 or c4*5, and whether the former's tie is conventionally placed,
makes no difference to the starting time and duration.

> It must be midi2ly that eventually decides what to do
> with pitches that last for some "weird durations".

There are no weird durations in the MIDI; there are just durations. A
note lasts as long as the composer writes into the score. AFAICT all
midi2ly does is to perform some mechanical arithmetical reductions
corresponding to a schoolchild learning cancellation in fractions¹.
IOW c4*4 can be written as c1, c4*10 as c2*5, and so on. What it never
appears to do is to create two notes and a tie.

> midi2ly already provides options for outputting absolute or relative
> pitches, to always include the timing (or only when necessary), ...
> There could potentially be another parameter to determine whether
> midi2ly should produce "c1" or "c2.~c4". Or perhaps some way to fix
> this with python-ly that I have to run anyway. Maybe that exists
> already.

This just complicates midi2ly without adding any functionality lacking
elsewhere. If it worries you, 

Re: "Problematic" conversion from MIDI: c4*5, c1 (in 3/4 time) etc.

[David Wright]

On Fri 29 Jul 2016 at 14:29:57 (+0200), Mojca Miklavec wrote:
> I have a midi file that I wanted to convert into scores, but the
> scores simply don't look right.
> 
> While I have a real (relatively long) song in the MIDI, I believe that
> I can fully reproduce the problem with the following simple example:
> 
> \score {
>   \new Voice = "melody" {
> \set Staff.midiInstrument = "accordion"
> \time 3/4
> \relative c' {
>   c4 c c |
>   c1 d4 e |
>   f4*5 g4 |
>   f2.~ | % becomes f4*5
>   f2 e4 |
>   d4*3 | % becomes d2.
>   c4 c2~ | % becomes c1
>   c2
> }
>   }
>   \midi { \tempo 4 = 160 }
>   \layout {}
> }
> 
> (I picked accordion because one doesn't hear the duration with piano.)
> 
> The idea is to make midi from the above example first (lilypond
> test.ly), then convert midi to scores (midi2ly test.midi -o test2.ly)
> and typeset again (lilypond test2.ly).
> 
> 
> The resulting MIDI file sounds right, but the typesetting of it is
> very strange. I get just a single quarter note printed out rather than
> something that takes the duration of five times a quarter.
> 
> OK, that's probably expected when I consciously enter the above
> syntax, but not after conversion from a MIDI file.
> 
> I noticed that the whole idea of the asterisk operator is to print a
> single unit, but to prolong it in MIDI (or for other purposes). But
> there's a lot of inconsistency:
> - if I properly enter c2.~ c2, I get c4*5 from the midi conversion
> - if I properly enter c2~ c2, I get c1 which is "forbidden" inside 3/4
> - if I sloppily enter c4*3 which would typset in a very weird way, it
> comes out OK after the conversion as c2.
> 
> None of that makes any sense to me.
> 
> Sure I can manually fix the resulting plain text file, but I was
> wondering if there was really no better way to get this done properly
> and automatically.

In the absence of any output examples, I've attached what my system
produces from your source. Let us know what's incorrect. It looks to
me as if the original score is just what you (idiosyncratically) asked
for and the subsequent score has been "conventionalised" as one might
expect, because the midi performer has no way of representing your
odd notation.

(Ignore the addition of 00 to the midi filename; my lilypond command
postprocesses midi filenames to make them sort in the correct order.)

> (PS: please CC me in reply.)

This will happen automatically if you coerce you mail client into
including the header line:

 Reply-To: Mojca Miklavec , 
lilypond-u...@gnu.org

Cheers,
David.
\score {
  \new Voice = "melody" {
\set Staff.midiInstrument = "accordion"
\time 3/4
\relative c' {
  c4 c c |
  c1 d4 e |
  f4*5 g4 |
  f2.~ | % becomes f4*5
  f2 e4 |
  d4*3 | % becomes d2.
  c4 c2~ | % becomes c1
  c2
}
  }
  \midi { \tempo 4 = 160 }
  \layout {}
}


accord.pdf
Description: Adobe PDF document


accord-00.midi
Description: MIDI audio
% Lily was here -- automatically converted by 
/home/david/lilypond-2.19.44-1/lilypond/usr/bin/midi2ly from /tmp/accord-00.midi
\version "2.14.0"

\layout {
  \context {
\Voice
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
\remove "Rest_engraver"
\consists "Completion_rest_engraver"
  }
}

trackAchannelA = {
  
  % [TEXT_EVENT] creator: 
  
  % [TEXT_EVENT] GNU LilyPond 2.19.44  
  
  \time 3/4 
  
  \tempo 4 = 160 
  
}

trackA = <<
  \context Voice = voiceA \trackAchannelA
>>


trackBchannelA = {
  
  % [INSTRUMENT_NAME] accordion
  
  \set Staff.instrumentName = "\new:melody"
  
}

trackBchannelB = \relative c {
  c'4 c c 
  | % 2
  c1 d4 e 
  | % 4
  f4*5 g4 
  | % 6
  f4*5 e4 
  | % 8
  d2. 
  | % 9
  c4 c1 
}

trackB = <<
  \context Voice = voiceA \trackBchannelA
  \context Voice = voiceB \trackBchannelB
>>


\score {
  <<
\context Staff=trackB \trackA
\context Staff=trackB \trackB
  >>
  \layout {}
  \midi {}
}


accord-00-midi.pdf
Description: Adobe PDF document
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: "Problematic" conversion from MIDI: c4*5, c1 (in 3/4 time) etc.

[David Kastrup]

Mojca Miklavec  writes:

> I have a midi file that I wanted to convert into scores, but the
> scores simply don't look right.
>
> While I have a real (relatively long) song in the MIDI, I believe that
> I can fully reproduce the problem with the following simple example:
>
> \score {
>   \new Voice = "melody" {
> \set Staff.midiInstrument = "accordion"
> \time 3/4
> \relative c' {
>   c4 c c |
>   c1 d4 e |
>   f4*5 g4 |
>   f2.~ | % becomes f4*5
>   f2 e4 |
>   d4*3 | % becomes d2.
>   c4 c2~ | % becomes c1
>   c2
> }
>   }
>   \midi { \tempo 4 = 160 }
>   \layout {}
> }
>
> (I picked accordion because one doesn't hear the duration with piano.)
>
> The idea is to make midi from the above example first (lilypond
> test.ly), then convert midi to scores (midi2ly test.midi -o test2.ly)
> and typeset again (lilypond test2.ly).
>
>
> The resulting MIDI file sounds right, but the typesetting of it is
> very strange. I get just a single quarter note printed out rather than
> something that takes the duration of five times a quarter.

Yes, this sucks.  The salient point is that the durations are not
necessarily detected correctly, and more importantly, that their
relation to the bar lines (which a single timing mistake will move who
knows where) is not really known to be correct.  So midi2ly does not try
meddling with ~ and such stuff but converts every note to a single
recognizable entity.

You can partly fix this up using the Completion_heads_engraver like
follows:

\score {
  \new Voice = "melody"
  \with {
\remove "Note_heads_engraver"
\remove "Rest_engraver"
\consists "Completion_heads_engraver"
\consists "Completion_rest_engraver"
completionUnit = #(ly:make-moment 3/4)
completionFactor = 1
  }
  {
\set Staff.midiInstrument = "accordion"
\time 3/4
\relative c' {
  c4 c c |
  c1 d4 e |
  f4*5 g4 |
  f2.~ | % becomes f4*5
  f2 e4 |
  d4*3 | % becomes d2.
  c4 c2~ | % becomes c1
  c2
}
  }
  \midi { \tempo 4 = 160 }
  \layout {}
}

But you'll notice that this still does not deliver perfect results.  You
won't get around reediting, really.

> I noticed that the whole idea of the asterisk operator is to print a
> single unit, but to prolong it in MIDI (or for other purposes). But
> there's a lot of inconsistency:
> - if I properly enter c2.~ c2, I get c4*5 from the midi conversion
> - if I properly enter c2~ c2, I get c1 which is "forbidden" inside 3/4
> - if I sloppily enter c4*3 which would typset in a very weird way, it
> comes out OK after the conversion as c2.
>
> None of that makes any sense to me.

midi2ly produces a single note/note-length and a maximum of one dot.
The rest it does by scaling.

I'm not going to defend it.  midi2ly is an old utility and it suffers
from being a batch tool.  An interactive tool that would correct
bar-lines as the user corrects recognized durations and then can
re-split durations after correction would have a lot more sanity going
for it.

> Sure I can manually fix the resulting plain text file, but I was
> wondering if there was really no better way to get this done properly
> and automatically.

Completion_* engravers fix a bit of the typeset result but not
necessarily enough, and the input stays ugly.

-- 
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

"Problematic" conversion from MIDI: c4*5, c1 (in 3/4 time) etc.

[Mojca Miklavec]

Hello,

I have a midi file that I wanted to convert into scores, but the
scores simply don't look right.

While I have a real (relatively long) song in the MIDI, I believe that
I can fully reproduce the problem with the following simple example:

\score {
  \new Voice = "melody" {
\set Staff.midiInstrument = "accordion"
\time 3/4
\relative c' {
  c4 c c |
  c1 d4 e |
  f4*5 g4 |
  f2.~ | % becomes f4*5
  f2 e4 |
  d4*3 | % becomes d2.
  c4 c2~ | % becomes c1
  c2
}
  }
  \midi { \tempo 4 = 160 }
  \layout {}
}

(I picked accordion because one doesn't hear the duration with piano.)

The idea is to make midi from the above example first (lilypond
test.ly), then convert midi to scores (midi2ly test.midi -o test2.ly)
and typeset again (lilypond test2.ly).


The resulting MIDI file sounds right, but the typesetting of it is
very strange. I get just a single quarter note printed out rather than
something that takes the duration of five times a quarter.

OK, that's probably expected when I consciously enter the above
syntax, but not after conversion from a MIDI file.

I noticed that the whole idea of the asterisk operator is to print a
single unit, but to prolong it in MIDI (or for other purposes). But
there's a lot of inconsistency:
- if I properly enter c2.~ c2, I get c4*5 from the midi conversion
- if I properly enter c2~ c2, I get c1 which is "forbidden" inside 3/4
- if I sloppily enter c4*3 which would typset in a very weird way, it
comes out OK after the conversion as c2.

None of that makes any sense to me.

Sure I can manually fix the resulting plain text file, but I was
wondering if there was really no better way to get this done properly
and automatically.

Thank you,
Mojca

(PS: please CC me in reply.)

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1524 in lilypond: Beaming eighth notes in threes in 3/4 time

[lilypond]

Updates:
Status: Verified

Comment #5 on issue 1524 by brownian.box: Beaming eighth notes in threes in  
3/4 time

http://code.google.com/p/lilypond/issues/detail?id=1524

:-) Thank you for expected behavior part.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1524 in lilypond: Beaming eighth notes in threes in 3/4 time

[lilypond]

Updates:
Status: Fixed

Comment #4 on issue 1524 by carl.d.s...@gmail.com: Beaming eighth notes in  
threes in 3/4 time

http://code.google.com/p/lilypond/issues/detail?id=1524

Binary version not yet released


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1524 in lilypond: Beaming eighth notes in threes in 3/4 time

[lilypond]

Status: Accepted
Owner: 
Labels: Type-Defect Priority-Critical

New issue 1524 by colinpkc...@gmail.com: Beaming eighth notes in threes in  
3/4 time

http://code.google.com/p/lilypond/issues/detail?id=1524

Because of special rules regarding 3/4 time, grouping eighth notes in  
threes is producing wrong results.

Reported by Nick Payne:
Shouldn't this example have the notes in the second bar beamed three
together and three together? What I'm getting is three, then one, then two:

\version 2.13.50

\relative c' {
\time 3/4
c8 c c c c c
\set beamExceptions = #'((end . (((1 . 8) . (3 3)
c c c c c c
}


Attachments:
test.preview.png  2.1 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1524 in lilypond: Beaming eighth notes in threes in 3/4 time

[lilypond]

Comment #1 on issue 1524 by k-ohara5...@oco.net: Beaming eighth notes in  
threes in 3/4 time

http://code.google.com/p/lilypond/issues/detail?id=1524

The built-in rule to end beams a beat seems to be active for the end of the  
second beat (even though it shouldn't be).  Workaround is to say 'please  
let beams go across all three beats' :


\relative c' {
\time 3/4
c8 c c c c c
\set beatStructure = #'(3)  % - workaround
\set beamExceptions = #'((end . (((1 . 8) . (3 3)
c c c c c c
}

Attachments:
1524.png  1.3 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1524 in lilypond: Beaming eighth notes in threes in 3/4 time

[lilypond]

Updates:
Status: Fixed
Owner: Carl.D.Sorensen
Labels: fixed_2_13_51

Comment #2 on issue 1524 by carl.d.s...@gmail.com: Beaming eighth notes in  
threes in 3/4 time

http://code.google.com/p/lilypond/issues/detail?id=1524

Fixed in commit c1695321ac192515a7ddbcd10e259accfc333dc5

A regtest is also included.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1524 in lilypond: Beaming eighth notes in threes in 3/4 time

[lilypond]

Updates:
Status: Verified

Comment #3 on issue 1524 by colinpkc...@gmail.com: Beaming eighth notes in  
threes in 3/4 time

http://code.google.com/p/lilypond/issues/detail?id=1524

(No comment was entered for this change.)


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond