date:20150708

Re: Switching on/off instrument staff

2015-07-08 Thread Víctor



Also, I don't know if it makes a difference to you (it appears the 
output doesn't change), but I'd move your Dynamic section more 
explicitly in-between the two piano staves. I think it just makes the 
code a little cleaner. Like this:


\new PianoStaff <<
\new Staff ...
\new Dynamics ...
\new Staff ...
>>

Oh, and you don't need to explicitly create a \new Voice anymore in 
the upper piano Staff if you do that. Just a small suggestion.


- Abraham


Thanks for the suggestion, it is indeed a cleaner way. Now that I'll 
redefine the \score, I'll do it this way. Thanks again.

Víctor
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching on/off instrument staff

2015-07-08 Thread tisimst

On Wed, Jul 8, 2015 at 11:26 AM, Víctor [via Lilypond] <
ml-node+s1069038n17851...@n5.nabble.com> wrote:

> Abraham:
>
> You just gave me a wonderful solution, I'll explain myself:
>
> My current file layout is like this:
>
>
> *formato.ly *
>
> \version "2.19.15"
>
> \include "snippets.ly"% file with lots of snippets (really)
> \include "tipografia.ly"  % typographies
>
> \layout {
> % some overrides here
> }
>
> % some format snippets here:
> formatoPerc = { \stemDown }
>
>
>
> *voice_with_piano_example.ly *
>
> \include "formato.ly"
>
> control { } % this normaly stays empty, but can be used to add code to the
> voice without "polluting" it
>
> voz = { a4 b c }
> verso = \lyricmode { la la la }
>
> pianoDer = { a4 b c }
> pianoIzq = {a4 b c }
>
> dinamicas = { s4\pp s4 s4\f } % some dynamics here
>
> \score {
>   <<
> \new Staff \with { instrumentName = \vozSolo } << % this variable is
> defined in *formato.ly *
>   \new Voice \voz
>   \addlyrics \verso
>   \new Voice \control
> >>
> \new PianoStaff \with { instrumentName = \pianoIns } <<
>   \new Staff = "MD" <<
> \new Voice \pianoDer
> \new Dynamics \dinamicas
>   >>
>   \new Staff = "MI" {
> \clef bass
> \pianoIzq
>   }
> >>
>   >>
> }
>
> But now I've realized that \score should be declared in a separate file,
> something like* voz_y_piano.ly *, and there I can
> easely comment out the piano staff for all my files at once, avoiding both
> pain and human mistakes.
>
> Thanks again to all of you for your support. Best regards,
> Víctor.
>


Glad I could offer some help! Yes, if the \score block is the same for each
song, then putting it in its own file and \include-ing it after the
variable definitions is a handy way to solve this problem, for reasons
you've already discovered.

Also, I don't know if it makes a difference to you (it appears the output
doesn't change), but I'd move your Dynamic section more explicitly
in-between the two piano staves. I think it just makes the code a little
cleaner. Like this:

\new PianoStaff <<
  \new Staff ...
  \new Dynamics ...
  \new Staff ...
>>

Oh, and you don't need to explicitly create a \new Voice anymore in the
upper piano Staff if you do that. Just a small suggestion.

- Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Switching-on-off-instrument-staff-tp178484p178517.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching on/off instrument staff

2015-07-08 Thread Víctor

Abraham:

You just gave me a wonderful solution, I'll explain myself:

My current file layout is like this:

*formato.ly*

   \version "2.19.15"

   \include "snippets.ly"% file with lots of snippets (really)
   \include "tipografia.ly"  % typographies

   \layout {
% some overrides here
   }

   % some format snippets here:
   formatoPerc = { \stemDown }

*voice_with_piano_example.ly*

   \include "formato.ly"

   control { } % this normaly stays empty, but can be used to add code
   to the voice without "polluting" it

   voz = { a4 b c }
   verso = \lyricmode { la la la }

   pianoDer = { a4 b c }
   pianoIzq = {a4 b c }

   dinamicas = { s4\pp s4 s4\f } % some dynamics here

   \score {
  <<
\new Staff \with { instrumentName = \vozSolo } << % this
   variable is defined in /formato.ly/
  \new Voice \voz
  \addlyrics \verso
  \new Voice \control
>>
\new PianoStaff \with { instrumentName = \pianoIns } <<
  \new Staff = "MD" <<
\new Voice \pianoDer
\new Dynamics \dinamicas
  >>
  \new Staff = "MI" {
\clef bass
\pianoIzq
  }
>>
  >>
   }

But now I've realized that \score should be declared in a separate file, 
something like*/voz_y_piano.ly/*, and there I can easely comment out the 
piano staff for all my files at once, avoiding both pain and human mistakes.

Thanks again to all of you for your support. Best regards,
Víctor.

El 08/07/15 a las 11:33, tisimst escribió:

Victor,

You have gotten some great advice. Sorry they don't work for you. As 
I've been thinking about your dilemma I wondered if you could just do 
something like

\layout {
\context {
\Score
\denies "PianoStaff"
  }
}

on the top-level to remove the PianoStaff altogether (assuming this is 
how you built the piano part), but that doesn't do it either. This 
would be the kind of solution you would be looking for. Sorry it 
doesn't work like I postulated. I think I have a solution, but seeing 
a tiny example of a couple of files the exemplify your work-flow may 
help us out. Just put them in the body of an email like this:

%%% file1.ly 

voicePart = { c1 }
pianoRH = { c1 }
pianoLH = { c1 }

\include "formato.ly "

%%% file2.ly 

voicePart = { b1 }
pianoRH = { b1 }
pianoLH = { b1 }

\include "formato.ly "

%%% formato.ly 

\paper {
  indent = 0
}

\layout {
\override SomeThing.property = 1.5
\override SomeThingElse.property = 0
}

\score {
<<
\new Staff \voicePart
\new PianoStaff <<
\new Staff \pianoRH
\new Staff \pianoLH
>>
>>
  \layout {}
}

%%% masterfile.ly 

\include "file1.ly "
\include "file2.ly "

%%%

I just made that up, of course. Thank you in advance for clarifying 
things so that we may help you better.

- Abraham

On Wed, Jul 8, 2015 at 9:44 AM, Víctor [via Lilypond] <[hidden email] 
> wrote:

Wow, so many answers. I think Rob's solution will be the most
close to what I need, however I fear Abraham already answered my
question.

I'll explain my problem further: I'm working in a three volume
anthology for a singers school, each volume will come in two
versions, one for the professor and the other for the student. The
professor's version must have all voice piano parts, while the
student's should only have the voice part. Now, because this is a
very large project that includes gregorian scores, a lot of text
and some didactics, I've decide to assemble the book in LuaLaTeX
using lyluatex  package (a
recent replacement for lilypond-book). So all lilypond files
(about 80 right now, but they will be something like 200 in the
end) are configured from a single style sheet named /formato.ly
/, wich contains all snippets, formats, etc. So
what I am looking for, is a snippet that can disable all piano
parts across the project from a single line in such /formato.ly
/. To replace the \score block in all of the
files could be both painful and dangerous, but I prefer to do it
right now than later, when there will be much more of them; and
since all files are generated from a template, I can just replace
it with any text editor.

Anyway, if somebody has an idea of how to make this, I'll really
apreciate.
Thanks to all for your answers, best regards.
Víctor

El 08/07/15 a las 07:00, Robert Schmaus escribió:

Hi Chris,

The tag method is a fantastic tool in many cases, so it's great
to be aware of it. Just in this particular case it's maybe not
the easiest way to go.

Yeah, that's how I mostly use variables as well - placing just
the music in variables and then, in the score block, build up a

\new StaffGroup <<
  \new S

Re: Switching on/off instrument staff

2015-07-08 Thread tisimst

Victor,

You have gotten some great advice. Sorry they don't work for you. As I've
been thinking about your dilemma I wondered if you could just do something
like

\layout {
  \context {
\Score
\denies "PianoStaff"
  }
}

on the top-level to remove the PianoStaff altogether (assuming this is how
you built the piano part), but that doesn't do it either. This would be the
kind of solution you would be looking for. Sorry it doesn't work like I
postulated. I think I have a solution, but seeing a tiny example of a
couple of files the exemplify your work-flow may help us out. Just put them
in the body of an email like this:

%%% file1.ly

voicePart = { c1 }
pianoRH = { c1 }
pianoLH = { c1 }

\include "formato.ly"

%%% file2.ly

voicePart = { b1 }
pianoRH = { b1 }
pianoLH = { b1 }

\include "formato.ly"

%%% formato.ly

\paper {
  indent = 0
}

\layout {
  \override SomeThing.property = 1.5
  \override SomeThingElse.property = 0
}

\score {
  <<
\new Staff \voicePart
\new PianoStaff <<
  \new Staff \pianoRH
  \new Staff \pianoLH
>>
  >>
  \layout {}
}

%%% masterfile.ly

\include "file1.ly"
\include "file2.ly"

%%%

I just made that up, of course. Thank you in advance for clarifying things
so that we may help you better.
- Abraham

On Wed, Jul 8, 2015 at 9:44 AM, Víctor [via Lilypond] <
ml-node+s1069038n178514...@n5.nabble.com> wrote:

> Wow, so many answers. I think Rob's solution will be the most close to
> what I need, however I fear Abraham already answered my question.
>
> I'll explain my problem further: I'm working in a three volume anthology
> for a singers school, each volume will come in two versions, one for the
> professor and the other for the student. The professor's version must have
> all voice piano parts, while the student's should only have the voice part.
> Now, because this is a very large project that includes gregorian scores, a
> lot of text and some didactics, I've decide to assemble the book in
> LuaLaTeX using lyluatex  package (a
> recent replacement for lilypond-book). So all lilypond files (about 80
> right now, but they will be something like 200 in the end) are configured
> from a single style sheet named *formato.ly *, wich
> contains all snippets, formats, etc. So what I am looking for, is a snippet
> that can disable all piano parts across the project from a single line in
> such *formato.ly *. To replace the \score block in all
> of the files could be both painful and dangerous, but I prefer to do it
> right now than later, when there will be much more of them; and since all
> files are generated from a template, I can just replace it with any text
> editor.
>
> Anyway, if somebody has an idea of how to make this, I'll really apreciate.
> Thanks to all for your answers, best regards.
> Víctor
>
> El 08/07/15 a las 07:00, Robert Schmaus escribió:
>
>  Hi Chris,
>
>  The tag method is a fantastic tool in many cases, so it's great to be
> aware of it. Just in this particular case it's maybe not the easiest way to
> go.
>
>  Yeah, that's how I mostly use variables as well - placing just the music
> in variables and then, in the score block, build up a
>
>  \new StaffGroup <<
>   \new Staff \new Voice \someMusic
>   \new Staff <<
>  \new Voice { \voiceOne \moreMusic }
> \new Voice { \voiceTwo \yetMoreMusic }
>   >>
> >>
>
>  I find this a very clear structure ... and it allows me to have a
> "complete" template where you just comment out  all \Staffs you don't need
> in a particular case.
>
>  Cheers, Rob
>
> __
>
>  Truth does not change according to our ability to stomach it.
> -- *Flannery O'Connor*
>
> On 8 Jul 2015, at 13:11, Chris Yate <[hidden email]
> > wrote:
>
>   Hi Rob,
>
>  Wow, thanks, that's a much neater way. I think I should probably look at
> refactoring my band template.
>
> I agree, my method is a bit complicated -- but it's bothering me a bit,
> because I think there was a reason I did it like this in the first place!
> Could well be an insufficient understanding at the time, of how variables
> work :-)
>
>  I do already use variables as:
>
>  violinMusic = { a b c d }
>
>  violinVoice = \new Voice {
>  % voice setup stuff %
>  \violinMusic
> }
>
>  Chris
>
> On 8 July 2015 at 09:58, Robert Schmaus <[hidden email]
> > wrote:
>
>> In addition to the suggested way with tags (which surely works, but
>> which I find overly complicated), a simpler way would be to simply place
>> the Staffs in variables and comment out the ones you don't want to have
>> in the next engraving. Like this:
>>
>> violinStaff = \new Staff \with { instrumentName = "Violin" }{
>> \relative c'' { c4 d e f }
>> }
>>
>> celloStaff = \new Staff \with { instrumentName = "Cello" }{
>> \relative c { c4 d e f }
>> }
>>
>> \score{
>> <<
>>

Re: Switching on/off instrument staff

2015-07-08 Thread Víctor

Wow, so many answers. I think Rob's solution will be the most close to 
what I need, however I fear Abraham already answered my question.

I'll explain my problem further: I'm working in a three volume anthology 
for a singers school, each volume will come in two versions, one for the 
professor and the other for the student. The professor's version must 
have all voice piano parts, while the student's should only have the 
voice part. Now, because this is a very large project that includes 
gregorian scores, a lot of text and some didactics, I've decide to 
assemble the book in LuaLaTeX using lyluatex 
 package (a recent replacement for 
lilypond-book). So all lilypond files (about 80 right now, but they will 
be something like 200 in the end) are configured from a single style 
sheet named /formato.ly/, wich contains all snippets, formats, etc. So 
what I am looking for, is a snippet that can disable all piano parts 
across the project from a single line in such /formato.ly/. To replace 
the \score block in all of the files could be both painful and 
dangerous, but I prefer to do it right now than later, when there will 
be much more of them; and since all files are generated from a template, 
I can just replace it with any text editor.

Anyway, if somebody has an idea of how to make this, I'll really apreciate.
Thanks to all for your answers, best regards.
Víctor

El 08/07/15 a las 07:00, Robert Schmaus escribió:

Hi Chris,

The tag method is a fantastic tool in many cases, so it's great to be 
aware of it. Just in this particular case it's maybe not the easiest 
way to go.

Yeah, that's how I mostly use variables as well - placing just the 
music in variables and then, in the score block, build up a

\new StaffGroup <<
  \new Staff \new Voice \someMusic
  \new Staff <<
 \new Voice { \voiceOne \moreMusic }
\new Voice { \voiceTwo \yetMoreMusic }
  >>
>>

I find this a very clear structure ... and it allows me to have a 
"complete" template where you just comment out  all \Staffs you don't 
need in a particular case.

Cheers, Rob

__

Truth does not change according to our ability to stomach it.
-- /Flannery O'Connor/

On 8 Jul 2015, at 13:11, Chris Yate > wrote:

Hi Rob,

Wow, thanks, that's a much neater way. I think I should probably look 
at refactoring my band template.

I agree, my method is a bit complicated -- but it's bothering me a 
bit, because I think there was a reason I did it like this in the 
first place! Could well be an insufficient understanding at the time, 
of how variables work :-)

I do already use variables as:

violinMusic = { a b c d }

violinVoice = \new Voice {
 % voice setup stuff %
 \violinMusic
}

Chris

On 8 July 2015 at 09:58, Robert Schmaus > wrote:

In addition to the suggested way with tags (which surely works, but
which I find overly complicated), a simpler way would be to
simply place
the Staffs in variables and comment out the ones you don't want
to have
in the next engraving. Like this:

violinStaff = \new Staff \with { instrumentName = "Violin" }{
\relative c'' { c4 d e f }
}

celloStaff = \new Staff \with { instrumentName = "Cello" }{
\relative c { c4 d e f }
}

\score{
<<
  \violinStaff
  \celloStaff
>>
}

IMO there's no need for a complicated tag structure, just go for a
simple approach. You will want to use a variable structure for any
non-trivial score anyway ...

Best, Rob

Am 07/07/15 um 17:42 schrieb Víctor:
> Hello Lilyponders:
>
> Is there a way to place a switch in some instrument part so it
is not
> rendered when such switch is off? Something like:
>
> \score{
> <<
> \new Staff \with { instrumentName = "Violin" }{
> \relative c'' { c4 d e f }
> }
> \new Staff \with { instrumentName = "Cello" }{
> \relative c { c4 d e f }
> }
> >>
> }
>
> \layout{
> \disableCello
> }
>
> Thanks,
> Víctor.
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org 
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org 
https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond snippet web page

2015-07-08 Thread MING TSANG

Chris, 
Thank you. I guess we have to wait.  I will try every day.
Immanuel,Ming. 


 On Wednesday, July 8, 2015 8:53 AM, Chris Yate  wrote:
   

 http://downforeveryoneorjustme.com/lsr.di.unimi.it
 :-)
Down here too
On 8 July 2015 at 13:47, MING TSANG  wrote:

I am trying to access snippets since Sunday.  Web apge down?  All I get is :

This webpage is not available
ERR_CONNECTION_TIMED_OUT

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user





  ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond snippet web page

2015-07-08 Thread Chris Yate

http://downforeveryoneorjustme.com/lsr.di.unimi.it
 :-)

Down here too

On 8 July 2015 at 13:47, MING TSANG  wrote:

> I am trying to access snippets since Sunday.  Web apge down?
> All I get is :
>
> This webpage is not available
> ERR_CONNECTION_TIMED_OUT
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

lilypond snippet web page

2015-07-08 Thread MING TSANG

I am trying to access snippets since Sunday.  Web apge down?  All I get is :

This webpage is not available
ERR_CONNECTION_TIMED_OUT
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Forwarding LilyPond issue

2015-07-08 Thread Andrew Bernard

Hi,

Yes, as Martin said, it's fixed by installing this version of fontconfig on
Fedora 22:

fontconfig.x86_642.11.94-1.fc22

It's not a lilypond or Frescobaldi issue as such. Therefore, it ouht ot be
taken of the Frescobaldi bug list.

Andrew


On 8 July 2015 at 17:56, Peter Bjuhr  wrote:

>  Reported on the Frescobaldi issue tracker:
>
>  I'm a Fedora 22 user with Frescobaldi 2.18.1 and Lilypond 2.19. I'm
> having an issue when i try to engrave a score. It seems to fail when it
> tries to generate a pdf.
>
> Layout output to duba.ps'... Converting to./duba.pdf'...
> warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28
> -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
> -r1200 -sDEVICE=pdfwrite -sOutputFile=./duba.pdf -c.setpdfwrite -fduba.ps)'
> failed (256)
>
> fatal error: failed files: "/home/marsan/Documentos/Partituras/Coral/Duba/
> duba.ly"
>
> What is wrong?
>
> Thanks.
>
>
> I'm not familiar with this (but Urs responded that it's a known issue). Is
> it a Fedora specific problem? Any workarounds?
>
> Best
> Peter
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching on/off instrument staff

2015-07-08 Thread Robert Schmaus

Hi Chris, 

The tag method is a fantastic tool in many cases, so it's great to be aware of 
it. Just in this particular case it's maybe not the easiest way to go. 

Yeah, that's how I mostly use variables as well - placing just the music in 
variables and then, in the score block, build up a 

\new StaffGroup <<
  \new Staff \new Voice \someMusic 
  \new Staff <<
 \new Voice { \voiceOne \moreMusic }
\new Voice { \voiceTwo \yetMoreMusic }
  >>
>>

I find this a very clear structure ... and it allows me to have a "complete" 
template where you just comment out  all \Staffs you don't need in a particular 
case. 

Cheers, Rob

__

Truth does not change according to our ability to stomach it.
-- Flannery O'Connor

> On 8 Jul 2015, at 13:11, Chris Yate  wrote:
> 
> Hi Rob,
> 
> Wow, thanks, that's a much neater way. I think I should probably look at 
> refactoring my band template.
> 
> I agree, my method is a bit complicated -- but it's bothering me a bit, 
> because I think there was a reason I did it like this in the first place! 
> Could well be an insufficient understanding at the time, of how variables 
> work :-)
> 
> I do already use variables as:
> 
> violinMusic = { a b c d }
> 
> violinVoice = \new Voice {
>  % voice setup stuff %
>  \violinMusic 
> }
> 
> Chris
> 
>> On 8 July 2015 at 09:58, Robert Schmaus  wrote:
>> In addition to the suggested way with tags (which surely works, but
>> which I find overly complicated), a simpler way would be to simply place
>> the Staffs in variables and comment out the ones you don't want to have
>> in the next engraving. Like this:
>> 
>> violinStaff = \new Staff \with { instrumentName = "Violin" }{
>> \relative c'' { c4 d e f }
>> }
>> 
>> celloStaff = \new Staff \with { instrumentName = "Cello" }{
>> \relative c { c4 d e f }
>> }
>> 
>> \score{
>> <<
>>   \violinStaff
>>   \celloStaff
>> >>
>> }
>> 
>> IMO there's no need for a complicated tag structure, just go for a
>> simple approach. You will want to use a variable structure for any
>> non-trivial score anyway ...
>> 
>> Best, Rob
>> 
>> 
>> Am 07/07/15 um 17:42 schrieb Víctor:
>> > Hello Lilyponders:
>> >
>> > Is there a way to place a switch in some instrument part so it is not
>> > rendered when such switch is off? Something like:
>> >
>> > \score{
>> > <<
>> > \new Staff \with { instrumentName = "Violin" }{
>> > \relative c'' { c4 d e f }
>> > }
>> > \new Staff \with { instrumentName = "Cello" }{
>> > \relative c { c4 d e f }
>> > }
>> > >>
>> > }
>> >
>> > \layout{
>> > \disableCello
>> > }
>> >
>> > Thanks,
>> > Víctor.
>> >
>> > ___
>> > lilypond-user mailing list
>> > lilypond-user@gnu.org
>> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>> 
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Printing movement titles in page header

2015-07-08 Thread Mark Knoop

I'm trying to include the title of the current movement in the page
header. This works if I use bookparts to seperate the movements, but
not by setting header:piece in a score block. I don't want to use
bookparts as I don't want pagebreaks between movements.

Any ideas on how to achieve this? 

\version "2.19.22"

\header {
  title = "My Piece"
  composer = "Me"
  tagline = ##f
  % piece only prints in header if set here or in bookpart header
  piece = "Global Piece"
}

\paper {
  oddHeaderMarkup = \markup
  \fill-line {
\on-the-fly #not-part-first-page \fromproperty #'header:piece
\on-the-fly #not-part-first-page \fromproperty #'header:title
\on-the-fly #print-page-number-check-first 
  \fromproperty #'page:page-number-string 
  }
  evenHeaderMarkup = \oddHeaderMarkup
}

\book {
  \bookpart {
% piece only prints in header if set here or in top-level header
\header { piece = "Part 1" }
\score {
  % setting piece here has no effect
  \header { piece = "Movement 1" }
  \repeat unfold 400 c'1
}
\score {
  % setting piece here has no effect
  \header { piece = "Movement 2" }
  \repeat unfold 400 d'1
}
  }
  \bookpart {
\score {
  % setting piece here has no effect, 
  % even without a bookpart level header 
  \header { piece = "Movement 3" } 
  \repeat unfold 400 e'1
}
  }
}

-- 
Mark Knoop

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching on/off instrument staff

2015-07-08 Thread Chris Yate

Hi Rob,

Wow, thanks, that's a much neater way. I think I should probably look at
refactoring my band template.

I agree, my method is a bit complicated -- but it's bothering me a bit,
because I think there was a reason I did it like this in the first place!
Could well be an insufficient understanding at the time, of how variables
work :-)

I do already use variables as:

violinMusic = { a b c d }

violinVoice = \new Voice {
 % voice setup stuff %
 \violinMusic
}

Chris

On 8 July 2015 at 09:58, Robert Schmaus  wrote:

> In addition to the suggested way with tags (which surely works, but
> which I find overly complicated), a simpler way would be to simply place
> the Staffs in variables and comment out the ones you don't want to have
> in the next engraving. Like this:
>
> violinStaff = \new Staff \with { instrumentName = "Violin" }{
> \relative c'' { c4 d e f }
> }
>
> celloStaff = \new Staff \with { instrumentName = "Cello" }{
> \relative c { c4 d e f }
> }
>
> \score{
> <<
>   \violinStaff
>   \celloStaff
> >>
> }
>
> IMO there's no need for a complicated tag structure, just go for a
> simple approach. You will want to use a variable structure for any
> non-trivial score anyway ...
>
> Best, Rob
>
>
> Am 07/07/15 um 17:42 schrieb Víctor:
> > Hello Lilyponders:
> >
> > Is there a way to place a switch in some instrument part so it is not
> > rendered when such switch is off? Something like:
> >
> > \score{
> > <<
> > \new Staff \with { instrumentName = "Violin" }{
> > \relative c'' { c4 d e f }
> > }
> > \new Staff \with { instrumentName = "Cello" }{
> > \relative c { c4 d e f }
> > }
> > >>
> > }
> >
> > \layout{
> > \disableCello
> > }
> >
> > Thanks,
> > Víctor.
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Forwarding LilyPond issue

2015-07-08 Thread Urs Liska



Am 08.07.2015 um 11:06 schrieb Federico Bruni:
> Hi Andrew
> 
> It's this issue?
> https://code.google.com/p/lilypond/issues/detail?id=4449#c17

No, it seems to be something different.
The issue currently reported is about a wrong GhostScript version being
called. And I *think* it is a Frescobaldi issue (now). See
https://github.com/wbsoft/frescobaldi/issues/705#event-350595291

Urs

> 
> Did you get notifications from google code?
> 
> Il giorno mer 8 lug 2015 alle 10:17, Andrew Bernard
>  ha scritto:
>> Hi Peter,
>>
>> I reported this some time ago for Fedora 22. The issue has been dealt
>> with and fixed and is now working in 2.19.22. Previous versions fail
>> with the error you show, but 2.19.22 is now good. It’s not a
>> Frescobaldi error.
>>
>> Andrew
>>
>>
>>
>> From: lilypond-user-bounces+andrew.bernard=gmail@gnu.org
>> [mailto:lilypond-user-bounces+andrew.bernard=gmail@gnu.org] On
>> Behalf Of Peter Bjuhr
>> Sent: Wednesday, 8 July 2015 5:56 PM
>> To: LilyPond Users
>> Subject: Forwarding LilyPond issue
>>
>> Reported on the Frescobaldi issue tracker:
>>
>>
>>> I'm a Fedora 22 user with Frescobaldi 2.18.1 and Lilypond 2.19. I'm
>>> having an issue when i try to engrave a score. It seems to fail when
>>> it tries to generate a pdf.
>>>
>>> Layout output to duba.ps'... Converting to./duba.pdf'...
>>> warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28
>>> -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE
>>> -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./duba.pdf
>>> -c.setpdfwrite -fduba.ps)' failed (256)
>>> fatal error: failed files:
>>> "/home/marsan/Documentos/Partituras/Coral/Duba/duba.ly"
>>>
>>> What is wrong?
>>>
>>> Thanks.
>>>
>>
>> I'm not familiar with this (but Urs responded that it's a known
>> issue). Is it a Fedora specific problem? Any workarounds?
>>
>> Best
>> Peter
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Forwarding LilyPond issue

2015-07-08 Thread Martin Tarenskeen



On Wed, 8 Jul 2015, Peter Bjuhr wrote:


 On 2015-07-08 10:17, Andrew Bernard wrote:
   I reported this some time ago for Fedora 22. The issue has been dealt
   with and fixed and is now working in 2.19.22. Previous versions
   fail with the error you show, but 2.19.22 is now good. It’s not a
   Frescobaldi error.



 Thanks! Good to know that it has been fixed!


After a long search for the cause of the problem, it was fixed thanks to the 
updated fontconfig package in Fedora. I don't think it was anything in LilyPond 
2.19.22 that made the bug disappear:


https://bugzilla.redhat.com/show_bug.cgi?id=1216312

--

MT___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Forwarding LilyPond issue

2015-07-08 Thread Federico Bruni


Hi Andrew

It's this issue?
https://code.google.com/p/lilypond/issues/detail?id=4449#c17

Did you get notifications from google code?

Il giorno mer 8 lug 2015 alle 10:17, Andrew Bernard 
 ha scritto:

Hi Peter,

I reported this some time ago for Fedora 22. The issue has been dealt 
with and fixed and is now working in 2.19.22. Previous versions fail 
with the error you show, but 2.19.22 is now good. It’s not a 
Frescobaldi error.


Andrew



From: lilypond-user-bounces+andrew.bernard=gmail@gnu.org 
[mailto:lilypond-user-bounces+andrew.bernard=gmail@gnu.org] On 
Behalf Of Peter Bjuhr

Sent: Wednesday, 8 July 2015 5:56 PM
To: LilyPond Users
Subject: Forwarding LilyPond issue

Reported on the Frescobaldi issue tracker:


I'm a Fedora 22 user with Frescobaldi 2.18.1 and Lilypond 2.19. I'm 
having an issue when i try to engrave a score. It seems to fail when 
it tries to generate a pdf.


Layout output to duba.ps'... Converting to./duba.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 
-dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE 
-dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./duba.pdf 
-c.setpdfwrite -fduba.ps)' failed (256)
fatal error: failed files: 
"/home/marsan/Documentos/Partituras/Coral/Duba/duba.ly"


What is wrong?

Thanks.



I'm not familiar with this (but Urs responded that it's a known 
issue). Is it a Fedora specific problem? Any workarounds?


Best
Peter



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching on/off instrument staff

2015-07-08 Thread Robert Schmaus

In addition to the suggested way with tags (which surely works, but
which I find overly complicated), a simpler way would be to simply place
the Staffs in variables and comment out the ones you don't want to have
in the next engraving. Like this:

violinStaff = \new Staff \with { instrumentName = "Violin" }{
\relative c'' { c4 d e f }
}

celloStaff = \new Staff \with { instrumentName = "Cello" }{
\relative c { c4 d e f }
}

\score{
<<
  \violinStaff
  \celloStaff
>>
}

IMO there's no need for a complicated tag structure, just go for a
simple approach. You will want to use a variable structure for any
non-trivial score anyway ...

Best, Rob


Am 07/07/15 um 17:42 schrieb Víctor:
> Hello Lilyponders:
> 
> Is there a way to place a switch in some instrument part so it is not
> rendered when such switch is off? Something like:
> 
> \score{
> <<
> \new Staff \with { instrumentName = "Violin" }{
> \relative c'' { c4 d e f }
> }
> \new Staff \with { instrumentName = "Cello" }{
> \relative c { c4 d e f }
> }
> >>
> }
> 
> \layout{
> \disableCello
> }
> 
> Thanks,
> Víctor.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Forwarding LilyPond issue

2015-07-08 Thread Peter Bjuhr




On 2015-07-08 10:17, Andrew Bernard wrote:


Hi Peter,

I reported this some time ago for Fedora 22. The issue has been dealt 
with and fixed and is now working in 2.19.22. Previous versions fail 
with the error you show, but 2.19.22 is now good. It’s not a 
Frescobaldi error.


Andrew



Thanks! Good to know that it has been fixed!

Best
Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Forwarding LilyPond issue

2015-07-08 Thread Andrew Bernard

Hi Peter,

 

I reported this some time ago for Fedora 22. The issue has been dealt with and 
fixed and is now working in 2.19.22. Previous versions fail with the error you 
show, but 2.19.22 is now good. It’s not a Frescobaldi error.

 

Andrew

 

 

 

From: lilypond-user-bounces+andrew.bernard=gmail@gnu.org 
[mailto:lilypond-user-bounces+andrew.bernard=gmail@gnu.org] On Behalf Of 
Peter Bjuhr
Sent: Wednesday, 8 July 2015 5:56 PM
To: LilyPond Users
Subject: Forwarding LilyPond issue

 

Reported on the Frescobaldi issue tracker:




I'm a Fedora 22 user with Frescobaldi 2.18.1 and Lilypond 2.19. I'm having an 
issue when i try to engrave a score. It seems to fail when it tries to generate 
a pdf.

Layout output to duba.ps'... Converting to./duba.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 
-dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite 
-sOutputFile=./duba.pdf -c.setpdfwrite -fduba.ps)' failed (256)

fatal error: failed files: 
"/home/marsan/Documentos/Partituras/Coral/Duba/duba.ly"

What is wrong?

Thanks.


I'm not familiar with this (but Urs responded that it's a known issue). Is it a 
Fedora specific problem? Any workarounds?

Best
Peter

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Forwarding LilyPond issue

2015-07-08 Thread Peter Bjuhr


(I've never seen this in Ubuntu.)



On 2015-07-08 10:11, Urs Liska wrote:

[...] it only affects
binary releases and not my self-built LPs [...]




That could explain why I haven't encountered it.

Best
Peter

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Forwarding LilyPond issue

2015-07-08 Thread Urs Liska



Am 08.07.2015 um 10:08 schrieb Peter Bjuhr:
> 
> 
> On 2015-07-08 09:57, Urs Liska wrote:
 fatal error: failed files:
 >>"/home/marsan/Documentos/Partituras/Coral/Duba/duba.ly"
 >>
 >>What is wrong?
 >>
 >>Thanks.
 >>
>>> >
>>> >I'm not familiar with this (but Urs responded that it's a known issue).
>>> >Is it a Fedora specific problem? Any workarounds?
>> It's not necessarily Fedora related as others have similar problems too.
>> I encounter this on Debian also sometimes.
> 
> Do you mean that it is just a matter of keep on trying and LilyPond will
> eventually succeed?
> 

Not really. I've stopped following the issue because it only affects
binary releases and not my self-built LPs (which seems to be due to the
different way bundled or system libraries are called) and hope that
eventually it will be fixed. But as said I don't know about the current
state.

Urs

> (I've never seen this in Ubuntu.)
> 
>> It seems to have been
>> introduced by some changes to the Ghostscript/Pango systems.
> 
> 
> Best
> Peter
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Forwarding LilyPond issue

2015-07-08 Thread Peter Bjuhr

On 2015-07-08 09:57, Urs Liska wrote:

fatal error: failed files:
>>"/home/marsan/Documentos/Partituras/Coral/Duba/duba.ly"
>>
>>What is wrong?
>>
>>Thanks.
>>

>
>I'm not familiar with this (but Urs responded that it's a known issue).
>Is it a Fedora specific problem? Any workarounds?

It's not necessarily Fedora related as others have similar problems too.
I encounter this on Debian also sometimes.

Do you mean that it is just a matter of keep on trying and LilyPond will 
eventually succeed?

(I've never seen this in Ubuntu.)

It seems to have been
introduced by some changes to the Ghostscript/Pango systems.

Best
Peter

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Forwarding LilyPond issue

2015-07-08 Thread Urs Liska


>>
>> fatal error: failed files:
>> "/home/marsan/Documentos/Partituras/Coral/Duba/duba.ly"
>>
>> What is wrong?
>>
>> Thanks.
>>
> 
> I'm not familiar with this (but Urs responded that it's a known issue).
> Is it a Fedora specific problem? Any workarounds?

It's not necessarily Fedora related as others have similar problems too.
I encounter this on Debian also sometimes. It seems to have been
introduced by some changes to the Ghostscript/Pango systems.

Urs

> 
> Best
> Peter
> 
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Forwarding LilyPond issue

2015-07-08 Thread Peter Bjuhr


Reported on the Frescobaldi issue tracker:

I'm a Fedora 22 user with Frescobaldi 2.18.1 and Lilypond 2.19. I'm 
having an issue when i try to engrave a score. It seems to fail when 
it tries to generate a pdf.


Layout output to|duba.ps'...Converting to|./duba.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 
-dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH 
-r1200 -sDEVICE=pdfwrite -sOutputFile=./duba.pdf -c.setpdfwrite 
-fduba.ps)' failed (256)


fatal error: failed files: 
"/home/marsan/Documentos/Partituras/Coral/Duba/duba.ly"


What is wrong?

Thanks.



I'm not familiar with this (but Urs responded that it's a known issue). 
Is it a Fedora specific problem? Any workarounds?


Best
Peter

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Switching on/off instrument staff

Re: Switching on/off instrument staff

Re: Switching on/off instrument staff

Re: Switching on/off instrument staff

Re: Switching on/off instrument staff

Re: lilypond snippet web page

Re: lilypond snippet web page

lilypond snippet web page

Re: Forwarding LilyPond issue

Re: Switching on/off instrument staff

Printing movement titles in page header

Re: Switching on/off instrument staff

Re: Forwarding LilyPond issue

Re: Forwarding LilyPond issue

RE: Forwarding LilyPond issue

Re: Switching on/off instrument staff

Re: Forwarding LilyPond issue

RE: Forwarding LilyPond issue

Re: Forwarding LilyPond issue

Re: Forwarding LilyPond issue

Re: Forwarding LilyPond issue

Re: Forwarding LilyPond issue

Forwarding LilyPond issue

23 matches

Site Navigation

Mail list logo

Footer information