Piano accidentals don't work in a GrandStaff

2004-04-30 Thread Yuval Harel
Hello, The Notation Manual page on Accidentals ( http://lilypond.org/doc/v2.2/Documentation/user/out-www/lilypond/Accidentals.html#Accidentals) reads: ---SNIP--- piano This rule reflects 20th century practice for piano notation. Very similar to modern but accidentals also get canceled across

Re: Piano accidentals don't work in a GrandStaff

2004-05-05 Thread Yuval Harel
On Sun, 2 May 2004 23:01:42 +0200, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: [EMAIL PROTECTED] writes: Hello, The Notation Manual page on Accidentals ( http://lilypond.org/doc/v2.2/Documentation/user/out-www/lilypond/Accidentals.html#Accidentals) reads: ---SNIP--- piano

dots astray

2004-10-10 Thread Yuval Harel
Hi, I'm typesetting a heavily-dotted piece of mine (using Lilypond 2.2.5) and came across some problems with the way Lilypond places dots. This example shows several problems: \score { \notes { \new Staff \transpose c c' { \time 3/4 << {e8. f

\oneVoice and \voiceXX commands having the wrong scope

2005-01-25 Thread Yuval Harel
Hi, I found that \oneVoice and \voiceOne sometimes have unexpected effects. Here are two examples which might be two separate bugs. When preparing the examples I also noticed that adding markup can sometimes generate programming errors in these situations. Yuval__

Re: \oneVoice and \voiceXX commands having the wrong scope

2005-01-26 Thread Yuval Harel
Sent to wrong mailing list. Sorry. On Wed, 26 Jan 2005 02:25:32 +0200, Yuval Harel <[EMAIL PROTECTED]> wrote: \oneVoice scope too short: == \version "2.4.2" \new Staff { \clef bass \context Voice="1" { \oneVoice c'2-\markup {\co

Flag-notehead collision

2005-01-29 Thread Yuval Harel
Hi, Here are flags invading the inside of half-notes: % flags.ly \version "2.4.2" { \clef bass << {b8 r4.} \\ b2 >> << {b16 r4..} \\ b2 >> << {b32 r4...} \\ b2 >> << {b64 r4} \\ b2 >> } % end Thanks, Yuval ___ bug-lilypond mailing list bug-li

Beam's 'positions' attribute confused by \change

2005-02-04 Thread Yuval Harel
Hi, It seems that a \change command after a beam makes the Beam grob's 'positions' attribute relate to the staff changed to, instead of the staff where the beamed notes actually are. Here's an example: \version "2.4.2" RH = \relative c' { \time 12/8 \stemDown \once \override Beam #

Spurious "Too many clashing notecolumns" warning

2005-02-09 Thread Yuval Harel
Lilypond does not take into account if notes are invisible when printing this warning. For example, this input produces a spurious warning: \version "2.4.2" { \clef bass << {\oneVoice g1} \\ {\hideNotes \oneVoice g1} >> } Yuval ___

Staff switch line (documentation?) bug

2005-02-09 Thread Yuval Harel
Hi, I noticed that in some situations \showStaffSwitch works where {\set PianoStaff.followVoice = ##t} produces seemingly-buggy results. Are they expected to produce the same behavior? The documentation (http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Staff-switch-lines.html)

Voice context forgotten after staff change.

2005-02-09 Thread Yuval Harel
In this example, the staff changes inside an expression assigned to voice "v". When voice "v" is used again, the staff change is forgotten, and the slur cannot be terminated, as if in a different voice context. \version "2.4.2" LH = { \clef bass \context Voice="v" { e2( \change

Re: Spurious "Too many clashing notecolumns" warning

2005-02-10 Thread Yuval Harel
On Thu, 10 Feb 2005 10:18:37 +0100, Mats Bengtsson <[EMAIL PROTECTED]> wrote: The warning is still relevant, since the position of the notes that are printed are still affected by the invisible note. I don't understand that claim. If the position was affected the notes would not have clashed, w

Re: Grace notes, ties, optimum notation

2005-02-18 Thread Yuval Harel
On Thu, 17 Feb 2005 14:04:08 +0100, Maurizio Tomasi <[EMAIL PROTECTED]> wrote: I am not sure, but perhaps this could be useful to you: http://lists.gnu.org/archive/html/lilypond-user/2004-11/msg00465.html Hi, I was glad to see this example, because there are quite a few places where I needed t

Re: Staff switch line (documentation?) bug

2005-02-22 Thread Yuval Harel
On Tue, 15 Feb 2005 02:43:26 -0800, Graham Percival <[EMAIL PROTECTED]> wrote: On 15-Feb-05, at 1:25 AM, Erik Sandberg wrote: PianoStaff.followVoice=##t changes the property for the entire piano staff, this is why the other voices are affected as well. Instead you should set Voice.followVoice

Staff change at beginning of score

2005-02-28 Thread Yuval Harel
It seems staff changes don't work at the beginning of a score. In this example, the {a} is incorrectly produced in the right-hand staff: \version "2.4.2" \score { \context PianoStaff=PS << \context Staff=RH { \change Staff=LH a } \context Staff=LH {

MIDI bug - re-attacking a note

2005-08-12 Thread Yuval Harel
Hello, When a note is attacked while it is already playing, no MIDI event is generated. This occurs often in piano notation. Here is an example: \version "2.6.3" \score { << c4 \\ {r8 c8 % <-- this note is not played

Re: MIDI bug - re-attacking a note

2005-08-14 Thread Yuval Harel
On Fri, 12 Aug 2005 18:53:13 +0200, Erik Sandberg <[EMAIL PROTECTED]> wrote: On Thursday 11 August 2005 21.45, Yuval Harel wrote: Hello, When a note is attacked while it is already playing, no MIDI event is generated. This occurs often in piano notation. Here is an example: Than

Re: MIDI bug - re-attacking a note

2005-08-14 Thread Yuval Harel
On Sat, 13 Aug 2005 16:04:16 +0200, Erik Sandberg <[EMAIL PROTECTED]> wrote: On Saturday 13 August 2005 12.58, Yuval Harel wrote: On Fri, 12 Aug 2005 18:53:13 +0200, Erik Sandberg Actually, this example works fine for me (on version 2.6.3 on Windows) - the MIDI output plays both not

Re: MIDI bug - re-attacking a note

2005-08-15 Thread Yuval Harel
c4, which delays all subsequent midi output by 1/4. New attempt: % %Yuval Harel \header { texidoc = "If notes from two polyphonic voices inside one staff overlap, midi output is delayed. If the overlapping notes are identical, the second one is not played. " reportedin = &quo

Re: MIDI bug - re-attacking a note

2005-08-15 Thread Yuval Harel
On Mon, 15 Aug 2005 01:46:26 +0200, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Yuval Harel wrote: Hello, When a note is attacked while it is already playing, no MIDI event is generated. This occurs often in piano notation. Here is an example: I think that correct MIDI behavior

Re: MIDI bug - re-attacking a note

2005-08-16 Thread Yuval Harel
On Mon, 15 Aug 2005 17:06:51 +0200, Erik Sandberg <[EMAIL PROTECTED]> wrote: On Monday 15 August 2005 17.30, Yuval Harel wrote: On Sun, 14 Aug 2005 23:53:12 +0200, Erik Sandberg <[EMAIL PROTECTED]> wrote: > You're right. I don't have working sound right now, so I re