Re: Variable length bars

2014-06-27 Thread Phil Holmes
- Original Message - From: Patrick or Cynthia Karl pck...@mac.com To: lilypond-user@gnu.org Sent: Thursday, June 26, 2014 10:53 PM Subject: Variable length bars I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which has a single initial time signature of 4/2

Re: Variable length bars

2014-06-27 Thread Matthew Collett
On 27/06/2014, at 9:53 am, Patrick or Cynthia Karl pck...@mac.com wrote: I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which has a single initial time signature of 4/2 2/2 followed by measures that are either 4 half-note beats or 2 half-note beats long, in

Re: Variable length bars

2014-06-27 Thread Urs Liska
Am 26.06.2014 23:53, schrieb Patrick or Cynthia Karl: I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which has a single initial time signature of 4/2 2/2 followed by measures that are either 4 half-note beats or 2 half-note beats long, in quasi-random fashion. It's

Re: Variable length bars

2014-06-27 Thread Urs Liska
Am 27.06.2014 10:05, schrieb Urs Liska: Am 26.06.2014 23:53, schrieb Patrick or Cynthia Karl: I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which has a single initial time signature of 4/2 2/2 followed by measures that are either 4 half-note beats or 2 half-note beats

Fwd: Re: Variable length bars

2014-06-27 Thread Malte Meyn
Forgot CC … Original Message Subject: Re: Variable length bars Date: Fri, 27 Jun 2014 08:10:52 +0200 From: Malte Meyn lilyp...@maltemeyn.de To: Patrick or Cynthia Karl pck...@mac.com You don’t even need the \set Timing.measureLength, a \time command will do the same when you

Re: Double key signature

2014-06-27 Thread James
On 25/06/14 04:14, Keith OHara wrote: Pierre Perol-Schneider pierre.schneider.paris at gmail.com writes: On the french list we are working on a Merulo score with an 8 lines staff, 2 clefs and 2 key signature As you can notice, I still have to manually set the distance between the key

Building documentation: bad PNG output

2014-06-27 Thread Aymeric
Hello, I’m tring to build the LilyPond documentation since quite some time, and whereas the PDF and HTLM output is great, the PNG are… well… here is a sample. Where do you think it’s coming from, and can you help me solve this, please? Thanks in advance, Aymeric

Re: Building documentation: bad PNG output

2014-06-27 Thread Federico Bruni
2014-06-27 12:19 GMT+02:00 Aymeric ejisn...@gmail.com: I’m tring to build the LilyPond documentation since quite some time, and whereas the PDF and HTLM output is great, the PNG are… well… here is a sample. Where do you think it’s coming from, and can you help me solve this, please? You

Re: Building documentation: bad PNG output

2014-06-27 Thread Aymeric
lilypond-2.18.2/Documentation/out-www/00 But all the PNG images look the same. I tried to export some PNG myself with LilyPond from my own .ly files, and I don’t have this error. On 06/27/2014 12:31 PM, Federico Bruni wrote: 2014-06-27 12:19 GMT+02:00 Aymeric ejisn...@gmail.com

Re: Building documentation: bad PNG output

2014-06-27 Thread Federico Bruni
Don't look there, it's different from what we have. Also, why caring for images in the directories? I'm asking: have you seen that image on the html manual? If so, where? (manual, section, parapraph) 2014-06-27 12:39 GMT+02:00 Aymeric ejisn...@gmail.com:

Re: Building documentation: bad PNG output

2014-06-27 Thread Aymeric
For example, in the HTML documentation: file:///usr/doc/lilypond-doc-2.18.2/html/Documentation/notation/pitches.html file:///usr/doc/lilypond-doc-2.18.2/html/Documentation/eb/lily-bd76d922.png looks the same as the image I sent before. On 06/27/2014 12:50 PM, Federico Bruni wrote: Don't look

Re: Building documentation: bad PNG output

2014-06-27 Thread Federico Bruni
Those files names are randomly generated. We don't have them! Can you see the same issue on the lilypond website? http://lilypond.org/doc/v2.18/Documentation/notation/pitches Or send us a screenshot of your web page. 2014-06-27 12:58 GMT+02:00 Aymeric ejisn...@gmail.com: For example, in the

Re: Building documentation: bad PNG output

2014-06-27 Thread Federico Bruni
Ok, finally I see what's the problem. I never had such a problem and I cannot make a guess. You got no error when running make doc? You should check the log files in Documentation: ./Documentation/notation.texi2pdf.log ./Documentation/notation.bigtexi.log ./Documentation/notation.splittexi.log

Re: Building documentation: bad PNG output

2014-06-27 Thread Federico Bruni
BTW, what's the purpose of building the current stable doc (2.18.2)? Which source are you using? 2014-06-27 13:16 GMT+02:00 Federico Bruni fedel...@gmail.com: Ok, finally I see what's the problem. I never had such a problem and I cannot make a guess. You got no error when running make doc?

Re: Building documentation: bad PNG output

2014-06-27 Thread Federico Bruni
Helping you is a hard job and I've just run out of time. You are not telling us which source you are using. From a linux distro repository? From lilypond git repository? You should use git and checkout the 2.18.2 branch, otherwise you won't get much help from this list probably. And the logs of

Re: Building documentation: bad PNG output

2014-06-27 Thread Phil Holmes
The key thing to note is that 'make doc' is not designed to produce PNG output: these are at best intermediate files and at worst built as a by-product. The only thing it is designed to create is PDF and HTML output: so the question is, as before: what does that look like? -- Phil Holmes

Re:Variable length bars (Phil Holmes)

2014-06-27 Thread Andrew A. Cashner
-- Forwarded message -- From: Phil Holmes m...@philholmes.net To: Patrick or Cynthia Karl pck...@mac.com, lilypond-user@gnu.org Cc: Date: Fri, 27 Jun 2014 08:45:46 +0100 Subject: Re: Variable length bars - Original Message - From: Patrick or Cynthia Karl

Re: Building documentation: bad PNG output

2014-06-27 Thread James
Aymeric, On 27/06/14 13:06, Federico Bruni wrote: Helping you is a hard job and I've just run out of time. You are not telling us which source you are using. From a linux distro repository? From lilypond git repository? You should use git and checkout the 2.18.2 branch, otherwise you won't

Re: Building documentation: bad PNG output

2014-06-27 Thread Aymeric
Thank you. I will do what you say later, and give you as much details as I can. Now I know it could be an environment problem, so I’ll dig further. On 06/27/2014 02:47 PM, James wrote: Aymeric, On 27/06/14 13:06, Federico Bruni wrote: Helping you is a hard job and I've just run out of

Re: Variable length bars (Phil Holmes)

2014-06-27 Thread Knute Snortum
I am working on Mussorgsky's *Pictures at an Exhibition* and in the last movement he specifically changes from cut time to 2/2. I am not sure of the significance of this, but there it is. (The 2/2 section has a lot of half note triplets.) Knute Snortum (via Gmail) On Fri, Jun 27, 2014 at

Re: Re:Variable length bars (Phil Holmes)

2014-06-27 Thread Andrew A. Cashner
Phil, You're absolutely right (and I apologize if I suggested you didn't know that)---as you say, my terms weren't precise either. In medieval and Renaissance theory, C is tempus imperfectum cum prolatione minore, cut C is tempus imperfectum cum prolatione maiore; in other words, both are duple

Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line

2014-06-27 Thread Patrick or Cynthia Karl
Message: 6 Date: Thu, 26 Jun 2014 20:20:16 +0200 From: Marc Hohl m...@hohlart.de Subject: Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line [...] Sorry, that doesn't work for me, result is the same. I assume you're saying to replace the \bar || with

Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line

2014-06-27 Thread David Kastrup
Patrick or Cynthia Karl pck...@mac.com writes: Message: 6 Date: Thu, 26 Jun 2014 20:20:16 +0200 From: Marc Hohl m...@hohlart.de Subject: Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line [...] Sorry, that doesn't work for me, result is the same. I assume

Crescendos, sforzandos, and impossible MIDI volumes

2014-06-27 Thread Knute Snortum
I want to start a discussion about this and maybe get a change into LilyPond. Currently, you can get an impossible (de)crescendo error in LilyPond if your crescendo has a \sf in the middle [1]. It stops the crescendo and if you restart it, ending in any dynamic mark, you get an error. This is

Re: Crescendos, sforzandos, and impossible MIDI volumes

2014-06-27 Thread Simon Albrecht
Am 27.06.2014 20:42, schrieb Knute Snortum: I want to start a discussion about this and maybe get a change into LilyPond. Currently, you can get an impossible (de)crescendo error in LilyPond if your crescendo has a \sf in the middle [1]. It stops the crescendo and if you restart it, ending