Mats Bengtsson-4 wrote:
>
>
> Well, if you manage to describe how that should work. If you imagine
> yourself in the role of the autochanger, how would you react if somebody
> else did some extra staff changes every now and then. When should you
> start doing your ordinary job after such a
On 01.03.2010, at 06:03, George_ wrote:
I disagree. Once again citing my hypothetical 500-bar fugue, it seems
incomprehensible to me that there should not be a compromise
between the
autochange function and manual staff changes. It just blows my mind
that
something so feature-rich as Lilypon
George_ wrote:
I could try that. But would it be possible to request a feature that allows
manual and automatic staff changes at the same time?
Well, if you manage to describe how that should work. If you imagine
yourself in the role of the autochanger, how would you react if somebody
else
James Bailey-4 wrote:
>
> I'm still not convinced that the autochanger was ever meant to be
> mixed with the manual changer. It seems that, if anything, the bug is
> that it's possible to have manual staff changes whilst using the
> autochanger.
>
I disagree. Once again citing my hypo
I could try that. But would it be possible to request a feature that allows
manual and automatic staff changes at the same time?
Thanks
George
James Bailey-4 wrote:
>
> The only problem I have with this is that I don't think that manual
> staff changes are supposed to work with autochange.
On 28.02.2010, at 10:56, Xavier Scheuer wrote:
2010/2/28 James Bailey :
The only problem I have with this is that I don't think that manual
staff changes are supposed to work with autochange.
…
So, according to the doc, it should be possible to mix automatic and
manual staff changes.
Or thi
On 28.02.2010, at 10:56, Xavier Scheuer wrote:
2010/2/28 James Bailey :
The only problem I have with this is that I don't think that manual
staff changes are supposed to work with autochange.
…
So, according to the doc, it should be possible to mix automatic and
manual staff changes.
Or thi
2010/2/28 James Bailey :
> The only problem I have with this is that I don't think that manual
> staff changes are supposed to work with autochange.
That's what I thought too.
But with a further look at the doc one can see, under "Changing staff
automatically" (autochange):
If additional contr
The only problem I have with this is that I don't think that manual
staff changes are supposed to work with autochange. I could force
things to work, but the known issues and warnings says that if you
want high quality output, staff switches should be specified
manually. And yeah, I realize
Okay, I've put the snippet in the quote. Basically the first change shows the
\change not working; the second one shows the \change working. Regardless,
both produce errors in the log.
> \version "2.13.7"
>
> \new PianoStaff {
> <<
> \new Staff = "up" {
>
Again, I don't know what the expected behavior of autochange is, it
seems to be a pretty simple tool, however you may be able to achieve
the desired result with a spacer rest.
<<
\new PianoStaff {
<<
\new Staff = "up" {
\new Voice = "melOne" {
\key
I can add the bug to the tracker, but can you make a short snippet
(http://lilypond.org/doc/v2.13/Documentation/web/tiny-examples#Tiny-
examples) that demonstrates the problem. and then a sentence or two
that explains what the behavior should be. Then I'll know what to
add, 'cause I don't ev
On Sat, Feb 27, 2010 at 12:32 PM, George_ wrote:
>
> Is there any particular format I need to conform to for bug reports, or do I
> just write 'freestyle'?
Yes, see this page for some hints:
http://lilypond.org/doc/v2.13/Documentation/web/bug-reports
Thanks,
Patrick
__
Is there any particular format I need to conform to for bug reports, or do I
just write 'freestyle'?
Patrick McCarty-3 wrote:
>
> On 2010-02-27, George_ wrote:
>>
>> So where can I report this?
>
> If you run LilyPond without arguments, you'll see the bug report URL
> listed at the very bottom
On 2010-02-27, George_ wrote:
>
> So where can I report this?
If you run LilyPond without arguments, you'll see the bug report URL
listed at the very bottom:
http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs
-Patrick
___
lilypond-u
>Actually I'm not a pianist, nor some kind of "LilyPond-genius", so my
>answer was only based on my knowledge of LilyPond (little with
>keyboard-related stuffs) and also based on your minimal code, which had
>only one (zero) staff change...
>
>Pardon my bloody stupid answer.
I'm sorry.
>Indeed,
On 27 February 2010 06:09, George_ wrote:
> So say I have a piece that is five hundred bars long. Say I use
> autochange to get Lilypond to automatically change staff for the
> music. Say that there are 50 staff changes that are particularly
> awkward. You are telling me that the only alternative
>Why are you using *both* \autochange (i.e. _automatic_ staff changing)
>and \change Staff = "up" (i.e. _manual_ staff changing) ?
>
>To my opinion either you let LilyPond change automatically at a certain
>note, either you decide yourself when to change, and you say LilyPond
>when (using the \cha
On 26 February 2010 20:46, George_ wrote:
> Hey, guys, could I please get some help for this? I really need to get this
> music transcribed for a competition in April, help would be greatly
> appreciated. Thanks!
Hi,
I don't understand what you are trying to achieve...
On 23 February 2010 22:
Hey, guys, could I please get some help for this? I really need to get this
music transcribed for a competition in April, help would be greatly
appreciated. Thanks!
--
View this message in context:
http://old.nabble.com/Strange-message-with-autochange-tp27710824p27722612.html
Sent from the Gnu -
Update: if I put \change Staff = "up" after the rest, the b goes onto the
right staff. However, the rest still stays on the bottom staff, and I get
this in the log:
D:/Music Work/Sheet Music/BWV 533/BWV533.ly:24:52: warning: cannot find
context to switch to
21 matches
Mail list logo
