[Denemo-devel] [bug #27004] Non-printing rests don't follow the Time Signature changes in additional voices

[Pietro Battiston]

URL:
  <http://savannah.gnu.org/bugs/?27004>

                 Summary: Non-printing rests don't follow the Time Signature
changes in additional voices
                 Project: GNU Denemo, a gtk+ frontend to GNU Lilypond
            Submitted by: toobaz
            Submitted on: ven 10 lug 2009 14:54:29 GMT
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

(denemo 0.8.6 and git)

When a new voice is created in a staff with time changes, the time changes
aren't inherited by it.

To reproduce, open the attached .denemo file and export to pdf: it will look
like the attached pdf file, while it shouldn't.


The workaround is to redefine, in the second voice, all the tempo changes,
but it's not nice, because:
1) the "official" method to insert single-staff polyphony (possibly for a
measure only!) is to add a voice, and that way it's a pain if there were many
tempo changes before
2) anyway, there is a discrepancy between Denemo's visual output and the
generated lilypond and pdf
3) moreover, if I add a tempo change in a voice, the notation of the (same)
tempo change in the other voice disappears, as if Denemo was in fact partially
aware that those tempo changes are cross-voices

Notice that clicking "Join voices" doesn't seem to have any influence on the
issue.

Probably the solution would be to establish that when a new voice is created,
it inherits all the tempo changes of the other voice of the staff. There is
obviously some arbitrariety if the voices of the staff are more than one, but
if I understood correctly denemo's logic, it's not a problem, since they will
(by induction!) have all the same tempo.

Alternatively, this inheriting could happen at the moment of creating the
lilypond file.


A cleaner solution would be to distinguish, in the internal logic, "all
staves" tempo changes from the ones regarding only one stave, and make voices
and new staves inherit only the "all staves" ones... but I think that not much
people have different tempos on different staves, so if _they_ had to manually
add some tempo changes, it would be a minor issue.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: ven 10 lug 2009 14:54:29 GMT  Name: repr.denemo  Size: 926B   By:
toobaz
A file exposing the bug and the pdf it produces.
<http://savannah.gnu.org/bugs/download.php?file_id=18404>
-------------------------------------------------------
Date: ven 10 lug 2009 14:54:29 GMT  Name: repr.pdf  Size: 21kB   By: toobaz
A file exposing the bug and the pdf it produces.
<http://savannah.gnu.org/bugs/download.php?file_id=18405>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?27004>

_______________________________________________
  Messaggio inviato con/da Savannah
  http://savannah.gnu.org/