Re: Odd output

[Marco Correia]

Hi,

I didn't want to sound rude or anything. I just want to make a point that I do 
not consider this as a minor improvement since:

1. The output is not aestetically wrong, it is definitely readable differently 
from what is specified in the lilypond source.

2. I think you should not assume the user will write a musically (logicaly) 
consistent piece in order to display the notes correctly.

3. It can happen in a real world exercise, for example when displaying music 
which is obtained by a computer program.

I don't know anything about the lilypond internals. I'm just a 1 week newbie, 
who just stumbled across this problem on one of the first attempts at 
lilypond.

Lilypond is written in Scheme, is that right? For someone who doesn't know 
this language, but has a strong background on computer science in general, 
would you think that he could hack into the lilypond algorithm for displaying 
the accidentals and make something better out of it? Is there any 
documentation on the subject available?

I think the idea behind lilypond is great, and from the examples I've seen it 
looks like it works very well for most cases. I'm willing to try to help to 
correct this issue, with your help, if you think that it is feasible.

Anyway, thanks for making your effort available for free. I am also an open 
souce developer and, believe me, I do value these contributions.

Thanks!
Marco


On Friday 10 December 2010, Phil Holmes wrote:
> Please reply to the user group as well.
> 
> As is often pointed out, it's free software and the fixes depend on who is
> working for nothing on the code.
> 
> I wouldn't think it would crop up frequently.
> 
> I made a workaround with a combination of forcing the accidentals to be
> displayed, and then using force-hshift and extra-offset and a few other
> tweaks to make it work.
> 
> My example is pretty complicated, because I also autogenerate the code, but
> you're welcome to a copy if you want.
> 
> --
> Phil Holmes
> 
> 
> ----- Original Message -----
> From: "Marco Correia" <address@hidden>
> To: "Phil Holmes" <address@hidden>
> Sent: Friday, December 10, 2010 10:29 AM
> Subject: Re: Odd output
> 
> > Thanks!
> > 
> > I can't believe that this is seen as a low priority enhancement...! This
> > completely renders lilypond unusable for the task I need it, which is to
> > serve
> > as a printer for computer generated music. The output is not ugly - it is
> > plain wrong!
> > 
> > Why doesn't the accidental_engraver looks into other voices as well?
> > 
> > Maybe I can workaround it by doing an extra pass before writing the
> > lilypond
> > code to check if this kind of problem may occur... But now I wonder what
> > other
> > kind of potential problems may occur with this accidental_engraver
> > algorithm...
> > 
> > Anyway, I just wanted to say that I think this problem deserves more
> > consideration.
> > 
> > Thank you!
> > Marco
> > 
> > On Friday 10 December 2010, you wrote:
> >> ----- Original Message -----
> >> From: "Marco Correia" <address@hidden>
> >> To: <address@hidden>
> >> Sent: Friday, December 10, 2010 12:35 AM
> >> Subject: Odd output
> >> 
> >> > Hi,
> >> > 
> >> > I just started using lilypond, so it is very possible that I'm making
> >> > some mistake.
> >> > 
> >> > When compiling this example:
> >> > 
> >> > \include "english.ly"
> >> > {
> >> > \clef treble
> >> > \time 4/4
> >> > <<
> >> > { fs'4 }
> >> > \\
> >> > { f'4 }
> >> > 
> >> > }
> >> > 
> >> > I see two notes on fs (occupying the same position but with stems up
> >> > and
> >> > down). There is no indication that f is there.
> >> > 
> >> > Is this supposed to/ how do I fix it?
> >> > 
> >> > Thanks!
> >> > Marco
> >> 
> >> This was one of the first issues I raised, in June this year.  I think
> >> it was my first bug report:
> >> 
> >> http://code.google.com/p/lilypond/issues/detail?id=1134
> >> 
> >> 
> >> --
> >> Phil Holmes


-- 
Marco Correia <address@hidden>