Re: Clef change and measure length

Malte Meyn-3 wrote > That example is the same in the german translation. But at p. 172 > (“Horizontale Ausrichtung von Pausen → Ganztaktige Pausen”, i. e. > “Horizontal positioning of rests → full measure rests”) she writes > something like “If the rest measure contains a clef, key signature or

Re: Clef change and measure length

Am 27.10.19 um 17:30 schrieb foxfanfare: Thanks for your replies. Where did you find this reference in Gould's book? I was looking for that before writing my initial post but without success. On the contrary, I found this example which suggests otherwise (see the second one): mmr.jpg

Re: Clef change and measure length

Malte Meyn-3 wrote > I think that it depends on context: In a full score where only one > instrument has a clef change, it would look weird if all the other > instruments have the rest not centered. But in solo music, I’m not so > sure which one I would prefer. > > According to Gould LilyPond’s

Re: Clef change and measure length

Am Sa., 26. Okt. 2019 um 10:30 Uhr schrieb foxfanfare : > > Hi all, > > I think this is a bug: when a clef change appears after a full measure rest, > the rest is no longer centered properly in the measure. The result looks > weird. See that example: > > \version "2.19.82" > > \new Staff > \relativ

Re: Clef change and measure length

Am 26.10.19 um 10:40 schrieb foxfanfare: Hi all, I think this is a bug: when a clef change appears after a full measure rest, the rest is no longer centered properly in the measure. The result looks weird. See that example: \version "2.19.82" \new Staff \relative c' { c1 R-"default"

Re: clef change confuses manual key signature

On Mon, Aug 13, 2012 at 11:50:34PM +0200, james wrote: > In the following: > \version "2.14.2" > \score { >\relative c' { > \time 2/4 > \set Staff.keySignature = #`(((0 . 4) . ,SHARP) ((0 . 3) . ,SHARP)) > \clef treble > c8 a c d > %%% Commenting out the following line

Re: clef change confuses manual key signature

james writes: > Honestly, what's most important to me is where the sharps/flats in the > key signature are placed. I attach the image of what I expect: That image does not make sense to me at all. Notes appear in key signature (though in a different octave) and still carry an accidental. How do

Re: clef change confuses manual key signature

On Aug 14, 2012, at 5:00 PM, David Kastrup wrote: > james writes: > > So I fail to make _any_ sense of your example. If I had to guess, I'd > say the octave specifications are there for overriding the default > octaves chosen by the key signature engraver, but without being fixed to > a certai

Re: clef change confuses manual key signature

james writes: > In the following: > \version "2.14.2" > \score { >\relative c' { > \time 2/4 > \set Staff.keySignature = #`(((0 . 4) . ,SHARP) ((0 . 3) . ,SHARP)) > \clef treble > c8 a c d > %%% Commenting out the following line solves the problem %%% > \clef bas

Re: Clef change placed outside score

On Wed, Jun 15, 2011 at 6:11 AM, Ralph Palmer wrote: > This has  been submitted as Issue 1695 : > http://code.google.com/p/lilypond/issues/detail?id=1695 Thanks. I think I found a couple workarounds: musy = \relative c' { \clef treble \override Score.NonMusicalPaperColumn #'allow-loose-spaci

Re: Clef change placed outside score

On Tue, Jun 14, 2011 at 11:55 PM, Jay Anderson wrote: > \version "2.14.1" > > %The bass clef in the lower staff is placed to the left of the staff. If > either > %the tempo mark is removed or the triplets are changed to a quarter note > the > %the clef is placed correctly. This was not an error i

Re: Clef change

This bug is fixed, or at least much improved, in 2.7.6. Michael, can you please verify that it is the way you expect? On Saturday 24 April 2004 15.09, Erik Sandberg wrote: > Hi, > > I added this to the bug cvs as 'clef-change'. > > % > % > \header { texidoc = > "The clef change in bar 1 is too f

Re: Clef change

[EMAIL PROTECTED] writes: > I agree that using cvs for uploading png may seem a bit strange. But it works > and is very simple. "cvs add -kb foo.png" is much easier than using ftp. And > the file will be downloaded automatically to . during cvs update, which is > much easier than having to open

Re: Clef change

> I agree that using cvs for uploading png may seem a bit strange. But > it works and is very simple. "cvs add -kb foo.png" is much easier > than using ftp. And the file will be downloaded automatically to . > during cvs update, which is much easier than having to open mozilla. I fully second thi

Re: Clef change

On Sunday 02 May 2004 23.00, Han-Wen Nienhuys wrote: > Couldn't we just have the entire collection rendered just like > input/test in the tips & tricks? Putting binary blobs, which are also > compiler output (by lilypond), into a source version control system > isn't the way to go I.M.O. I see the

Re: Clef change

On Sunday 02 May 2004 16.16, Werner LEMBERG wrote: > > BTW, the same goes for multivoice-rest-position2. It's not 100% > > obvious (to me at least) that it really is a bug; I can imagine that > > the coders could be more motivated to fix the problem if you've done > > some research that shows that

Re: Clef change

[EMAIL PROTECTED] writes: > On Sunday 25 April 2004 13.35, Werner LEMBERG wrote: > > > I added this to the bug cvs [...] > > > > It would be great if you can store JPG images also which show the > > problem! > > I use .png instead. I use the convention that if I submit something as > "clef-change

Re: Clef change

> BTW, the same goes for multivoice-rest-position2. It's not 100% > obvious (to me at least) that it really is a bug; I can imagine that > the coders could be more motivated to fix the problem if you've done > some research that shows that your suggestion is common practise. It's quite difficult

Re: Clef change

> This one has pretty much to do about taste. Your suggestion sounds > sensible, but do you have a hand-engraved example of this behaviour? > (this would support the claim that you have a good taste :) You > wouldn't need to provide a scan of the score; just adding a texidoc > notice telling whic

Re: Clef change

On Sunday 02 May 2004 10.36, Erik Sandberg wrote: > On Sunday 02 May 2004 07.34, Werner LEMBERG wrote: > > beam-accidental-collision.ly > > broken-small-slur.ly > > multivoice-rest-position.ly > > multivoice-rest-position2.ly > > Thanks! I marked multivoice-rest-position as

Re: Clef change

On Sunday 02 May 2004 07.34, Werner LEMBERG wrote: > I wrote: > > I ask for yet another refinement: Do a zoom at the problematic spot > > and crop the image around the buggy detail [...] > > A good example is grace-accidental-spacing.ly: The current image (as > of Apr. 28th) doesn't really show the

Re: Clef change

I wrote: > I ask for yet another refinement: Do a zoom at the problematic spot > and crop the image around the buggy detail [...] A good example is grace-accidental-spacing.ly: The current image (as of Apr. 28th) doesn't really show the problem since the relevant distances are already within sub

Re: Clef change

> BTW, is there a preferred date format & how do you extract that > easily with CVS? I just take the ChangeLog timestamp which normally is precise enough -- optimally, you should refer to the ChangeLog revision number. Werner ___ bug-lilypond ma

Re: Clef change

On Monday 26 April 2004 07.43, Werner LEMBERG wrote: > > > It would be great if you can store JPG images also which show the > > > problem! > > > > I use .png instead. > > Yes, of course. A typo of mine. > > > I use the convention that if I submit something as "clef-change.ly", > > I upload clef-c

Re: Clef change

> > It would be great if you can store JPG images also which show the > > problem! > > I use .png instead. Yes, of course. A typo of mine. > I use the convention that if I submit something as "clef-change.ly", > I upload clef-change.png demonstrating the problem, if appropriate. Thanks, I got

Re: Clef change

On Sunday 25 April 2004 23.14, Jan Nieuwenhuizen wrote: > Werner LEMBERG writes: > > But sometimes it is difficult to describe a problem with words. To > > compare newer versions of lilypond with the buggy results should be > > easier if images are already there... > > Yes, a picture showing the b

Re: Clef change

On Sunday 25 April 2004 13.35, Werner LEMBERG wrote: > > I added this to the bug cvs [...] > > It would be great if you can store JPG images also which show the > problem! I use .png instead. I use the convention that if I submit something as "clef-change.ly", I upload clef-change.png demonstrati

Re: Clef change

Werner LEMBERG writes: > But sometimes it is difficult to describe a problem with words. To > compare newer versions of lilypond with the buggy results should be > easier if images are already there... Yes, a picture showing the bug is a very good idea. That's one of the reasons why your bug re

Re: Clef change

> > It would be great if you can store JPG images also which show the > > problem! > > it's a better idea to use lilypond or lilypond-book to do this, then > we can see what happens to each bugs for every release. But sometimes it is difficult to describe a problem with words. To compare newer

Re: Clef change

[EMAIL PROTECTED] writes: > > > I added this to the bug cvs [...] > > It would be great if you can store JPG images also which show the > problem! it's a better idea to use lilypond or lilypond-book to do this, then we can see what happens to each bugs for every release. -- Han-Wen Nienhu

Re: Clef change

> I added this to the bug cvs [...] It would be great if you can store JPG images also which show the problem! Werner ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond