Re: Issue 316 in lilypond: ancient \ictus not centered
Updates: Owner: percival.music.ca Comment #2 on issue 316 by paconet.org: ancient \ictus not centered http://code.google.com/p/lilypond/issues/detail?id=316 It should be \include gregorian.ly nowadays. Owner changed because otherwise unable to comment: Issue owner must be a project member -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 316 in lilypond: ancient \ictus not centered
Updates: Owner: --- Comment #3 on issue 316 by percival.music.ca: ancient \ictus not centered http://code.google.com/p/lilypond/issues/detail?id=316 owner now means the person fixing the issue. I'm not touching ancient stuff. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Room to improvement for polyphonic rests
Rests are not centered with noteheads in other voices.
\relative c''
{ c2 c4 c c1 r4 r r r r1 }
\\
{ r4 r r r r1 c2 c4 c c1 }
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
attachment: 4th-rest-center.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #9 on issue 665 by brownian.box: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 I'll happily make it 300, by the way. Here in Kyiv, Ukraine is preferable option though, but others are possible, i hope. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #10 on issue 665 by reinhold.kainhofer: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 There have been some discussions on lilypond-devel and lilypond-user. Here is a short excerpt from one of my mails, outlining how such a MusicXML backend could/would be implemented: The only problem is that the lilypond structure is not ideally suited for full MusicXML 2.0 export: All other graphical output formats (eps, ps, pdf, png, svg) simply export some graphical objects with a fixed position on a page, so at that stage the musical information is no longer available, so MusicXML export has to hook in earlier. The pure musical structure can probably be easily extracted from the music stream (e.g. by an engraver, listening to all kinds of events), but at that stage the page layout has not been done, so the great layout of lilypond scores could not be exported directly. On the other hand, the final graphical objects don't have any link to the music object that caused them, so one would also have to add such a link to the grobs. The MusicXML export would then work in two stages in a lilypond run: 1) In an engraver create the xml tree for the pure musical content 2) at the same time, also listen to created graphical objects and add a pointer to the corresponding xml node 3) After the layout is done, a MusicXML backend goes through the graphical object and exports all positioning information (most of which is new in MusicXML 2.0) to their linked xml nodes. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Updates: Owner: --- Labels: -Priority-Postponed Priority-Low musicxml Comment #11 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 What about implementing the pure-music-stream export as a first step? Can't be (much) worse than our current MIDI export, can it? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Room to improvement for polyphonic rests
On Thu, Feb 18, 2010 at 7:20 AM, Francisco Vila paconet@gmail.com wrote: Rests are not centered with noteheads in other voices. This is intentional; only whole-measure rests should be centered. (Please provide scans of publications if you think otherwise) -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Room to improvement for polyphonic rests
Han-Wen Nienhuys hanw...@gmail.com writes: On Thu, Feb 18, 2010 at 7:20 AM, Francisco Vila paconet@gmail.com wrote: Rests are not centered with noteheads in other voices. This is intentional; only whole-measure rests should be centered. (Please provide scans of publications if you think otherwise) Whole-measure rests are centered in the _bar_, not with other noteheads. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Room to improvement for polyphonic rests
2010/2/18 Han-Wen Nienhuys hanw...@gmail.com: On Thu, Feb 18, 2010 at 7:20 AM, Francisco Vila paconet@gmail.com wrote: Rests are not centered with noteheads in other voices. This is intentional; only whole-measure rests should be centered. (Please provide scans of publications if you think otherwise) To be fair, this is similar to LilyPond: Schott/Universal Wiener Urtext http://paconet.org/lilypond/Schott.jpg LilyPond output http://paconet.org/lilypond/Peters.jpg But this looks more balanced: Peters http://paconet.org/lilypond/lilypond.png -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Room to improvement for polyphonic rests
2010/2/18 Francisco Vila paconet@gmail.com: 2010/2/18 Han-Wen Nienhuys hanw...@gmail.com: On Thu, Feb 18, 2010 at 7:20 AM, Francisco Vila paconet@gmail.com wrote: Rests are not centered with noteheads in other voices. This is intentional; only whole-measure rests should be centered. (Please provide scans of publications if you think otherwise) To be fair, this is similar to LilyPond: Schott/Universal Wiener Urtext http://paconet.org/lilypond/Schott.jpg LilyPond output http://paconet.org/lilypond/Peters.jpg But this looks more balanced: Peters http://paconet.org/lilypond/lilypond.png Oops, sorry for the link dance. Peters http://paconet.org/lilypond/Peters.jpg lilypond http://paconet.org/lilypond/lilypond.png -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 978 in lilypond: docs for lily-git.tcl
Updates: Status: Fixed Comment #1 on issue 978 by markpolesky: docs for lily-git.tcl http://code.google.com/p/lilypond/issues/detail?id=978 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 978 in lilypond: docs for lily-git.tcl
Updates: Owner: markpolesky Comment #2 on issue 978 by markpolesky: docs for lily-git.tcl http://code.google.com/p/lilypond/issues/detail?id=978 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 641 in lilypond: error: script direction not yet known when using implicit Voice contexts
Comment #2 on issue 641 by horndude77: error: script direction not yet
known when using implicit Voice contexts
http://code.google.com/p/lilypond/issues/detail?id=641
% This example has the same fix/workaround as issue 641.
% There is no warning in this case. Instead the hairpins
% end at the end of the markup instead of at the correct
% location.
\version 2.13.13
\score
{
\new Staff
%\new Voice
{
%\key c \major
{\repeat unfold 16 c''16}
{s4\ s2.\!^\markup{Hello Hello Hello!}}
{\repeat unfold 16 c''16}
{s4\ s2.\!^\markup{Hi!}}
}
}
Attachments:
dynamic_error.preview.png 4.0 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 641 in lilypond: error: script direction not yet known when using implicit Voice contexts
On Thu, Feb 18, 2010 at 9:50 PM, lilyp...@googlecode.com wrote:
% This example has the same fix/workaround as issue 641.
% There is no warning in this case. Instead the hairpins
% end at the end of the markup instead of at the correct
% location.
I spoke too soon. I can't figure out how to work around the issue in
piano centered dynamics:
\version 2.13.13
left = {\repeat unfold 16 c''16}
dyn = {s4\ s2.\!^\markup{Hello Hello Hello!}}
right = {\clef bass \repeat unfold 16 c16}
\score
{
\new PianoStaff
\new Staff \left
\new Dynamics \dyn
\new Staff \right
}
Adding either the key or the new voice don't seem to do the trick.
Thanks for the help.
-Jay
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
