Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Guy Stalnaker]

All,

Being the stupid can't-let-it-go idiot I am :-)

I have a working frescobaldi. I had to  download the latest popplerqt4 from
the poppler source. I did the bad thing and installed it over the old, but
I have a working frescobaldi and that's the important thing.

Thanks to all three of you for taking the time to look through my problem.
I *greatly* appreciate it.

Guy Stalnaker
jimmyg...@gmail.com


On Tue, Sep 17, 2013 at 12:26 AM, Philippe Massart  wrote:

> I had the same error a few weeks ago, before trying the frescobaldi port
> file. But, it occurred with the "manually installed" version of frescobaldi
> (more precisely: the "manually installed" version of python-poppler-qt4).
>
> The python-poppler-qt4 I had manually installed had been compiled a long
> time ago and didn't recognize the new versions of the Sip API (installed by
> macport). The solution was tho rebuild and re-install the "manually
> installed" python-poppler-qt4, but since your python-poppler-qt4 was
> successfully installed by macport, I guess the problem lies elsewhere.
>
> I'll continue to look at it.
>
> Philippe
>
> Le 17 sept. 2013 à 07:04, Guy Stalnaker  a écrit :
>
> Well, this is certainly been an adventure. Sorry for the delay in
> acknowledging your and Davide's replies, but I've had to jettison using
> FileVault to regain space on the local harddrive. Somehow FileVault was
> holding 30Gb of space and refusing to release it, causing me no end of
> grief in downloading MacPort source and then compiling.
>
> So, finally, I have had to restart this from scratch. I'm afraid I was a
> bit rash in trying to troubleshoot the situation so your proffered solution
> cannot help (but you do describe what I did a year ago when I first
> installed Frescobaldi "python setup.py install"). What I've now done:
>
> 1. remove all traces (port uninstall/rm -rf) of poppler and frescobaldi
> 2. run "sudo port clean" to remove temp files, etc.
> 3. run "sudo port selfupdate" to get things up to date after the clean and
> FileVault issues (this took well over SIX hours -- good gawd)
> 4. run "sudo port install poppler +qt4 +quartz" which completed
> successfully
> 5. run "sudo port install frescobaldi-devel +app" which completed
> succefully
>
> But ...
>
> Frescobaldi crashes on startup:
>
> 
> [Lots of traceback calls]
> import popplerqt4
> RuntimeError: the sip module implements API v10.0 to v10.1 but the
> popplerqt4 module requires API v9.1
> 
>
> "port installed" shows:
>
> 
> Anorien% sudo port installed | grep sip
>   py27-sip @4.13.3_0
>   py27-sip @4.14.2_0
>   py27-sip @4.15.1_0 (active)
> Anorien [sudo port installed | grep sip] ~
>  13-09-16 10:45PM
> Anorien% sudo port installed | grep poppler
>   poppler @0.20.5_0+qt4+quartz
>   poppler @0.22.0_0+qt4+quartz
>   poppler @0.24.1_0+qt4+quartz (active)
>   poppler-data @0.4.6_0 (active)
>   py27-python-poppler-qt4 @0.16.3_1 (active)
> 
>
> I cannot deactivate the active py27-sip or poppler. I get a dependency
> errors.
>
> 
> Anorien% sudo port deactivate py27-sip @4.15.1_0
> Password:
> --->  Deactivating py27-sip @4.15.1_0
> --->  Unable to deactivate py27-sip @4.15.1_0, the following ports depend
> on it:
> --->py27-pyqt4 @4.10.3_1
> --->py27-python-poppler-qt4 @0.16.3_1
> ...
> Anorien% sudo port deactivate poppler @0.24.1_0+qt4+quartz
> --->  Deactivating poppler @0.24.1_0+qt4+quartz
> --->  Unable to deactivate poppler @0.24.1_0+qt4+quartz, the following
> ports depend on it:
> --->py27-python-poppler-qt4 @0.16.3_1
> --->texlive-bin @2013_2+x11
> 
>
> I installed the non-devel frescobaldi and get the exact same error on
> running from terminal.
>
> I "port uninstalled" all old sip/poppler ports and both frescobaldi ports
> and reinstalled, but the API error persists. So I cannot remove it due to
> dependencies (the texlive dependency is especially weighty - there are
> *many* that arise if I try to remove texlive as well).
>
> Any ideas?
>
> 
>
> It's always frustrating when folks post at how it just works for them LOL
> This stuff never just works for me.
>
> Guy Stalnaker
> jimmyg...@gmail.com
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Problem with hemiola notation

[Jim Long]

On Tue, Sep 17, 2013 at 07:31:15AM +0200, David Kastrup wrote:
> 
> I have not yet
> seen the trivial ugly correction for that yet

Hey, hey -- I resemble that remark!  Nice catch on using \skip,
though, instead of scaling s1 by the number of bars times the
time signature.

I should have included an elaboration in my previous post.  Try
the example using this definition of barLines:

barLines = {
s1 * 1 * 3/4 % skip 1 measure of 3/4 time
\repeat volta 2 {
s1 * 1 * 3/4 % skip 1 measure of 3/4 time
\bar ""  % then blank out the ensuing barline
s1 * 1 * 3/4 % skip 1 measure of 3/4 time
}
s1 * 1 * 3/4 % skip 1 measure of 3/4 time
\bar "|."% and set a final barline
}


Jim

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

Re: Problem with hemiola notation

[David Kastrup]

David Kastrup  writes:

> Alan McConnell  writes:
>
>> On Tue, Sep 17, 2013 at 12:50:54AM +0200, Janek Warchoł wrote:
>>> 2013/9/17 Alan McConnell :
>>> > On Mon, Sep 16, 2013 at 11:21:43PM +0200, Janek Warchoł wrote:
>>> >>
>>> >> Please send us a short and compilable example and we'll try to tell
>>> >> you what exactly needs to be done.  Without an example, i have no idea
>>> >> why Phil's solution wouldn't work for you.
>>> >
>>> >   Nothing easier!  Here it is [...]
>>> 
>>> Nothing easier!  Here the second barline disappears (tested with
>>> 2.16.2 and 2.17.26)
>> You are absolutely right!  However:  try this
>
>>
>> d4. e8 d c | b4 g g4. \bar ""  a8 d,4 d | b' g g \bar "|."
>
> Bad timing.  You are too late for overriding the bar.  I have not yet
> seen the trivial ugly correction for that yet, namely
>
> d4. e8 d c | b4 g << g4. { \skip 4 \bar "" } >>  a8 d,4 d | b' g g \bar "|."
>
> which lets the \bar "" command fall at the right time.

Oh, at any rate: have you considered Renaissance barlines?  They are
pretty much intended for dealing gracefully with that kind of music.

http://lilypond.org/doc/v2.16/Documentation/notation/working-with-ancient-music_002d_002dscenarios-and-solutions#mensurstriche-layout>

-- 
David Kastrup


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

Re: Problem with hemiola notation

[David Kastrup]

Alan McConnell  writes:

> On Tue, Sep 17, 2013 at 12:50:54AM +0200, Janek Warchoł wrote:
>> 2013/9/17 Alan McConnell :
>> > On Mon, Sep 16, 2013 at 11:21:43PM +0200, Janek Warchoł wrote:
>> >>
>> >> Please send us a short and compilable example and we'll try to tell
>> >> you what exactly needs to be done.  Without an example, i have no idea
>> >> why Phil's solution wouldn't work for you.
>> >
>> >   Nothing easier!  Here it is [...]
>> 
>> Nothing easier!  Here the second barline disappears (tested with
>> 2.16.2 and 2.17.26)
>  You are absolutely right!  However:  try this

>
> d4. e8 d c | b4 g g4. \bar ""  a8 d,4 d | b' g g \bar "|."

Bad timing.  You are too late for overriding the bar.  I have not yet
seen the trivial ugly correction for that yet, namely

d4. e8 d c | b4 g << g4. { \skip 4 \bar "" } >>  a8 d,4 d | b' g g \bar "|."

which lets the \bar "" command fall at the right time.

-- 
David Kastrup


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

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Philippe Massart]

I had the same error a few weeks ago, before trying the frescobaldi port file. 
But, it occurred with the "manually installed" version of frescobaldi (more 
precisely: the "manually installed" version of python-poppler-qt4). 

The python-poppler-qt4 I had manually installed had been compiled a long time 
ago and didn't recognize the new versions of the Sip API (installed by 
macport). The solution was tho rebuild and re-install the "manually installed" 
python-poppler-qt4, but since your python-poppler-qt4 was successfully 
installed by macport, I guess the problem lies elsewhere.

I'll continue to look at it.

Philippe

Le 17 sept. 2013 à 07:04, Guy Stalnaker  a écrit :

> Well, this is certainly been an adventure. Sorry for the delay in 
> acknowledging your and Davide's replies, but I've had to jettison using 
> FileVault to regain space on the local harddrive. Somehow FileVault was 
> holding 30Gb of space and refusing to release it, causing me no end of grief 
> in downloading MacPort source and then compiling.
> 
> So, finally, I have had to restart this from scratch. I'm afraid I was a bit 
> rash in trying to troubleshoot the situation so your proffered solution 
> cannot help (but you do describe what I did a year ago when I first installed 
> Frescobaldi "python setup.py install"). What I've now done:
> 
> 1. remove all traces (port uninstall/rm -rf) of poppler and frescobaldi
> 2. run "sudo port clean" to remove temp files, etc.
> 3. run "sudo port selfupdate" to get things up to date after the clean and 
> FileVault issues (this took well over SIX hours -- good gawd)
> 4. run "sudo port install poppler +qt4 +quartz" which completed successfully
> 5. run "sudo port install frescobaldi-devel +app" which completed succefully
>  
> But ...
> 
> Frescobaldi crashes on startup:
> 
> 
> [Lots of traceback calls]
> import popplerqt4
> RuntimeError: the sip module implements API v10.0 to v10.1 but the popplerqt4 
> module requires API v9.1
> 
> 
> "port installed" shows:
> 
> 
> Anorien% sudo port installed | grep sip  
>   py27-sip @4.13.3_0
>   py27-sip @4.14.2_0
>   py27-sip @4.15.1_0 (active)
> Anorien [sudo port installed | grep sip] ~
>   13-09-16 10:45PM
> Anorien% sudo port installed | grep poppler
>   poppler @0.20.5_0+qt4+quartz
>   poppler @0.22.0_0+qt4+quartz
>   poppler @0.24.1_0+qt4+quartz (active)
>   poppler-data @0.4.6_0 (active)
>   py27-python-poppler-qt4 @0.16.3_1 (active)
> 
> 
> I cannot deactivate the active py27-sip or poppler. I get a dependency 
> errors. 
> 
> 
> Anorien% sudo port deactivate py27-sip @4.15.1_0
> Password:
> --->  Deactivating py27-sip @4.15.1_0
> --->  Unable to deactivate py27-sip @4.15.1_0, the following ports depend on 
> it:
> --->py27-pyqt4 @4.10.3_1
> --->py27-python-poppler-qt4 @0.16.3_1
> ...
> Anorien% sudo port deactivate poppler @0.24.1_0+qt4+quartz 
> --->  Deactivating poppler @0.24.1_0+qt4+quartz
> --->  Unable to deactivate poppler @0.24.1_0+qt4+quartz, the following ports 
> depend on it:
> --->py27-python-poppler-qt4 @0.16.3_1
> --->texlive-bin @2013_2+x11
> 
> 
> I installed the non-devel frescobaldi and get the exact same error on running 
> from terminal.
> 
> I "port uninstalled" all old sip/poppler ports and both frescobaldi ports and 
> reinstalled, but the API error persists. So I cannot remove it due to 
> dependencies (the texlive dependency is especially weighty - there are *many* 
> that arise if I try to remove texlive as well).
> 
> Any ideas?
> 
> 
> 
> It's always frustrating when folks post at how it just works for them LOL 
> This stuff never just works for me.
> 
> Guy Stalnaker
> jimmyg...@gmail.com

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

Re: Problem with hemiola notation

[Jim Long]

On Mon, Sep 16, 2013 at 07:17:08PM -0400, Alan McConnell wrote:
> \version "2.16.0"
> 
> \header {
>   title = "A Jazzy 3/4 Tune!"
> }
> 
> %  Put some vertical space here!
> \markup { \vspace #1 }
> 
> global =  {
>   \key g \major 
>   \time 3/4
> }
> 
> 
> violinOne = \new Voice \relative c'' {
>   \set Staff.instrumentName = #"Violin 1 "
> 
> d4. e8 d c | b4 g g4. \bar ""  a8 d,4 d | b' g g \bar "|."
> 
> }
> 
> %  Challenge:  to get rid of the barline between  g g4. and a8 d,  !
> 
> 
> \score {
>   \new Staff
>   << \global \violinOne
>   >>
> }
> 
> \layout { }

I have two solutions for you.  The "ugly" one uses note scaling and a spacer
rest to achieve the desired engraved notation, at the expenses of slightly
inaccurate MIDI playback (if that is a concern to you).

violinOne = \new Voice \relative c'' {
  \set Staff.instrumentName = #"Violin 1 "

d4. e8 d c | b4 g g4. * 2/3 \bar "" s8 a8 d,4 d | b' g g \bar "|."

}

As Harm pointed out, the \bar command *must* come at a bar boundary
to be effective.  If you haven't encountered note duration
scaling yet,  "g4. * 2/3" *engraves a dotted quarter* -- the
literal duration -- in the output, but in Lilyponds internal
rhythmic counting, the duration is computed as 2/3 of the dotted
quarter, which of course is just a regular quarter note.  So the
\bar command now does indeed fall at a bar boundary.  The "s8"
after the \bar command is a spacer rest with an eighth-note
duration, because the engraved output for that bar appears to
have only 2 and a half beats.  The s8 adds one eighth note to the
duration of the measure following the \bar command.

The less ugly method, and one that achieves correct MIDI output,
is to create another music variable.  This variable can hold all
sorts of editorial notations, volta repeats, double bar lines,
dashed bar lines, invisible bar lines, tempo changes, etc.  Then
by placing that music into the simultaneous music (<< ... >>)
structure of the violin staff, those bar line properties get set
for the violin part.  In this solution, I also moved the final
bar '\bar "|."' out of the violin part and into the barLines
variable to illustrate.

violinOne = \new Voice \relative c'' {
\set Staff.instrumentName = #"Violin 1 "
d4. e8 d c | b4 g g4. a8 d,4 d | b' g g
}

%  Challenge:  to get rid of the barline between  g g4. and a8 d,  !

barLines = {
s1 * 2 * 3/4 % skip 2 measures of 3/4 time
\bar ""  % then blank out the ensuing barline
s1 * 2 * 3/4 % skip 2 more measures of 3/4 time
\bar "|."% and set a final barline
}

\score {
\new Staff
<< \global \violinOne \barLines
>>
}

\layout { }




HTH,

Jim

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

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Guy Stalnaker]

Well, this is certainly been an adventure. Sorry for the delay in
acknowledging your and Davide's replies, but I've had to jettison using
FileVault to regain space on the local harddrive. Somehow FileVault was
holding 30Gb of space and refusing to release it, causing me no end of
grief in downloading MacPort source and then compiling.

So, finally, I have had to restart this from scratch. I'm afraid I was a
bit rash in trying to troubleshoot the situation so your proffered solution
cannot help (but you do describe what I did a year ago when I first
installed Frescobaldi "python setup.py install"). What I've now done:

1. remove all traces (port uninstall/rm -rf) of poppler and frescobaldi
2. run "sudo port clean" to remove temp files, etc.
3. run "sudo port selfupdate" to get things up to date after the clean and
FileVault issues (this took well over SIX hours -- good gawd)
4. run "sudo port install poppler +qt4 +quartz" which completed successfully
5. run "sudo port install frescobaldi-devel +app" which completed succefully

But ...

Frescobaldi crashes on startup:


[Lots of traceback calls]
import popplerqt4
RuntimeError: the sip module implements API v10.0 to v10.1 but the
popplerqt4 module requires API v9.1


"port installed" shows:


Anorien% sudo port installed | grep sip
  py27-sip @4.13.3_0
  py27-sip @4.14.2_0
  py27-sip @4.15.1_0 (active)
Anorien [sudo port installed | grep sip] ~
 13-09-16 10:45PM
Anorien% sudo port installed | grep poppler
  poppler @0.20.5_0+qt4+quartz
  poppler @0.22.0_0+qt4+quartz
  poppler @0.24.1_0+qt4+quartz (active)
  poppler-data @0.4.6_0 (active)
  py27-python-poppler-qt4 @0.16.3_1 (active)


I cannot deactivate the active py27-sip or poppler. I get a dependency
errors.


Anorien% sudo port deactivate py27-sip @4.15.1_0
Password:
--->  Deactivating py27-sip @4.15.1_0
--->  Unable to deactivate py27-sip @4.15.1_0, the following ports depend
on it:
--->py27-pyqt4 @4.10.3_1
--->py27-python-poppler-qt4 @0.16.3_1
...
Anorien% sudo port deactivate poppler @0.24.1_0+qt4+quartz
--->  Deactivating poppler @0.24.1_0+qt4+quartz
--->  Unable to deactivate poppler @0.24.1_0+qt4+quartz, the following
ports depend on it:
--->py27-python-poppler-qt4 @0.16.3_1
--->texlive-bin @2013_2+x11


I installed the non-devel frescobaldi and get the exact same error on
running from terminal.

I "port uninstalled" all old sip/poppler ports and both frescobaldi ports
and reinstalled, but the API error persists. So I cannot remove it due to
dependencies (the texlive dependency is especially weighty - there are
*many* that arise if I try to remove texlive as well).

Any ideas?



It's always frustrating when folks post at how it just works for them LOL
This stuff never just works for me.

Guy Stalnaker
jimmyg...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Formatting long footnotes

[Gilberto Agostinho]

Yep, that simple and it works perfectly. Thanks a lot Thomas :)

Take care,
Gilberto


On Tue, Sep 17, 2013 at 4:02 AM, Thomas Morley wrote:

> 2013/9/17 Gilberto Agostinho :
> > Hi all,
> >
> > I have yet one more question: when writing a long footnote, the text is
> not
> > breaking into several lines or respecting the margin limits. I would
> love to
> > have it set to justified alignment as well, if that is possible.
> >
> > Here is a tiny example:
> >
> > \version "2.17.25"
> >
> > {
> >
> >   \footnote #'(-1 . 1)
> >
> > \markup{Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut
> eget
> > ante venenatis mi consectetur ornare. Cras facilisis dictum venenatis.
> > Donec.}
> >
> >   a'4 b' c'' d''
> >
> > }
> >
> >
> > Thanks a lot!
> > Gilberto Agostinho
>
>
> Hi,
>
> I'd use
> \markup \justify { ... }
> or
> \markup \wordwrap { ... }
>
> Cheers,
>   Harm
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Formatting long footnotes

[Rachael Thomas Carlson]

Hello Gilberto:

 
> {
> 
>   \footnote #'(-1 . 1)
> 
> \markup{Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut
> eget ante venenatis mi consectetur ornare. Cras facilisis dictum venenatis.
> Donec.}
> 
>   a'4 b' c'' d''
> 
> }
\justify-string will do the trick.

\markup { \justfiy-string #"Lorem ipsum dor sit amet,..."
}

Rachael Thomas Carlson

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

Re: Formatting long footnotes

[Thomas Morley]

2013/9/17 Gilberto Agostinho :
> Hi all,
>
> I have yet one more question: when writing a long footnote, the text is not
> breaking into several lines or respecting the margin limits. I would love to
> have it set to justified alignment as well, if that is possible.
>
> Here is a tiny example:
>
> \version "2.17.25"
>
> {
>
>   \footnote #'(-1 . 1)
>
> \markup{Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut eget
> ante venenatis mi consectetur ornare. Cras facilisis dictum venenatis.
> Donec.}
>
>   a'4 b' c'' d''
>
> }
>
>
> Thanks a lot!
> Gilberto Agostinho


Hi,

I'd use
\markup \justify { ... }
or
\markup \wordwrap { ... }

Cheers,
  Harm

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

Re: Problem with hemiola notation

[Thomas Morley]

2013/9/17 Alan McConnell :
> On Tue, Sep 17, 2013 at 12:50:54AM +0200, Janek Warchoł wrote:
>> 2013/9/17 Alan McConnell :
>> > On Mon, Sep 16, 2013 at 11:21:43PM +0200, Janek Warchoł wrote:
>> >>
>> >> Please send us a short and compilable example and we'll try to tell
>> >> you what exactly needs to be done.  Without an example, i have no idea
>> >> why Phil's solution wouldn't work for you.
>> >
>> >   Nothing easier!  Here it is [...]
>>
>> Nothing easier!  Here the second barline disappears (tested with
>> 2.16.2 and 2.17.26)
>You are absolutely right!  However:  try this
>  "extract"
>
> (start)--
> % experiment-3.ly  --  This file is about bar lines
> %  and will be posted to the lilypond list
> \version "2.16.0"
>
> \header {
>   title = "A Jazzy 3/4 Tune!"
> }
>
> %  Put some vertical space here!
> \markup { \vspace #1 }
>
> global =  {
>   \key g \major
>   \time 3/4
> }
>
>
> violinOne = \new Voice \relative c'' {
>   \set Staff.instrumentName = #"Violin 1 "
>
> d4. e8 d c | b4 g g4. \bar ""  a8 d,4 d | b' g g \bar "|."
>
> }
>
> %  Challenge:  to get rid of the barline between  g g4. and a8 d,  !
>
>
> \score {
> \new Staff
> << \global \violinOne
> >>
> }
>
> \layout { }
>
>
>  (finish)
>
> There is something Weird and Strange going on here

Not really.
The Problem is that the BarLine happens while the note continues.
Every command initiated after said note will come too late. And every
command before the note, preceeded with \once, will not affect the
BarLine. It is set too early.
To circumvent it, all I can think of is to use some \override -
\revert before and after the note.

Below I use a function to apply these commands to the note, showing a
drastically simplified example.

\version "2.16.0"

noBarLineAfterNote =
#(define-music-function (parser location m)(ly:music?)
#{
  \override Staff.BarLine #'stencil = ##f
  #m
  \revert Staff.BarLine #'stencil
#})

\relative c'' {
  c2
  \noBarLineAfterNote
  c1
  c2
}

> (For Thomas
> Morley: "Sea Nymphs hourly ring his knell ... ding(dotted) dong bell!)

:)

"When shall we three (quavers) meet again?"

>
> Alan
>
> --
> Alan McConnell :  http://globaltap.com/~alan/
> An idea is not responsible for the people who believe in it.
> If you only have a hammer, you tend to see every problem as a nail.


Cheers,
  Harm

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

Formatting long footnotes

[Gilberto Agostinho]

Hi all,

I have yet one more question: when writing a long footnote, the text is not
breaking into several lines or respecting the margin limits. I would love
to have it set to justified alignment as well, if that is possible.

Here is a tiny example:

\version "2.17.25"

{

  \footnote #'(-1 . 1)

\markup{Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut
eget ante venenatis mi consectetur ornare. Cras facilisis dictum venenatis.
Donec.}

  a'4 b' c'' d''

}


Thanks a lot!
Gilberto Agostinho
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Problem with hemiola notation

[Alan McConnell]

On Tue, Sep 17, 2013 at 12:50:54AM +0200, Janek Warchoł wrote:
> 2013/9/17 Alan McConnell :
> > On Mon, Sep 16, 2013 at 11:21:43PM +0200, Janek Warchoł wrote:
> >>
> >> Please send us a short and compilable example and we'll try to tell
> >> you what exactly needs to be done.  Without an example, i have no idea
> >> why Phil's solution wouldn't work for you.
> >
> >   Nothing easier!  Here it is [...]
> 
> Nothing easier!  Here the second barline disappears (tested with
> 2.16.2 and 2.17.26)
   You are absolutely right!  However:  try this
 "extract"

(start)--
% experiment-3.ly  --  This file is about bar lines
%  and will be posted to the lilypond list
\version "2.16.0"

\header {
  title = "A Jazzy 3/4 Tune!"
}

%  Put some vertical space here!
\markup { \vspace #1 }

global =  {
  \key g \major 
  \time 3/4
}


violinOne = \new Voice \relative c'' {
  \set Staff.instrumentName = #"Violin 1 "

d4. e8 d c | b4 g g4. \bar ""  a8 d,4 d | b' g g \bar "|."

}

%  Challenge:  to get rid of the barline between  g g4. and a8 d,  !


\score {
\new Staff
<< \global \violinOne
>>
}

\layout { }


 (finish)

There is something Weird and Strange going on here(For Thomas
Morley: "Sea Nymphs hourly ring his knell ... ding(dotted) dong bell!)

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
An idea is not responsible for the people who believe in it.
If you only have a hammer, you tend to see every problem as a nail.

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

Re: Problem with hemiola notation

[Nick Payne]

Here's a nasty hack that (without taking the lyrics into account) 
achieves the desired appearance:


\version "2.17.25"

move = #(define-music-function (parser location type move) (string? 
pair?) #{

  \once \override $type #'extra-offset = #move
  #})

barspace = #(define-music-function (parser location width) (pair?) #{
  \once \override Staff.BarLine.extra-spacing-width = #width
  #})

\relative f'' {
  \time 3/4
  g4. a8 \move "Dots" #'(3 . 0) f4.*2/3 |
  \barspace #'(0 . 2) ges8*2 e4.( d8) |
}
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Problem with hemiola notation

[Janek Warchoł]

2013/9/17 Alan McConnell :
> On Mon, Sep 16, 2013 at 11:21:43PM +0200, Janek Warchoł wrote:
>>
>> Please send us a short and compilable example and we'll try to tell
>> you what exactly needs to be done.  Without an example, i have no idea
>> why Phil's solution wouldn't work for you.
>
>   Nothing easier!  Here it is [...]

Nothing easier!  Here the second barline disappears (tested with
2.16.2 and 2.17.26)

\version "2.16.0"

\header {
  title = "A Simple 3/4 Tune"
}

%  Put some vertical space here!
\markup { \vspace #1 }

global =  {
  \key g \major
  \time 3/4
}


violinOne = \new Voice \relative c'' {
  \set Staff.instrumentName = #"Violin 1 "

d4. e8 d c | b4 g g \bar "" | a d, d | b' g g \bar "|."

}

%  Challenge:  to get rid of the barline between  g g and a d,  !


\score {
\new Staff
<< \global \violinOne
>>
}

\layout { }

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

Re: Problem with hemiola notation

[Alan McConnell]

On Mon, Sep 16, 2013 at 11:21:43PM +0200, Janek Warchoł wrote:
>
> Please send us a short and compilable example and we'll try to tell
> you what exactly needs to be done.  Without an example, i have no idea
> why Phil's solution wouldn't work for you.

  Nothing easier!  Here it is:
(start)--
% experiment-3.ly  --  This file is about bar lines
%  and will be posted to the lilypond list
\version "2.16.0"

\header {
  title = "A Simple 3/4 Tune"
}

%  Put some vertical space here!
\markup { \vspace #1 }

global =  {
  \key g \major 
  \time 3/4
}


violinOne = \new Voice \relative c'' {
  \set Staff.instrumentName = #"Violin 1 "

d4. e8 d c | b4 g g | a d, d | b' g g \bar "|."

}

%  Challenge:  to get rid of the barline between  g g and a d,  !


\score {
\new Staff
<< \global \violinOne
>>
}

\layout { }

(finish)

Make the second barline Go Away!

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
An idea is not responsible for the people who believe in it.
If you only have a hammer, you tend to see every problem as a nail.

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

Re: Problem with hemiola notation

[Thomas Morley]

2013/9/16 Alan McConnell :
> On Mon, Sep 16, 2013 at 12:32:25AM +0200, Thomas Morley wrote:
>> 2013/9/15 Thomas Morley :
>>
>> > Hi Alan,
>> >
>> > I've got the image, thanks.
>> > Now it's clear what you deserve.
> "What I deserve"?  Whipping?  Methinks thou art getting
> Shakespearian, as befits your nom de plume.

:)))
Well, I'm not a native english speaker.
My mistakes may be funny sometimes.
All I hope is that they are not misleading, offending, injurious ...


>> > I know no way to let LilyPond checking bars without complain for code like:
>> > \relative c' { \time 3/4 c4. d8 bes4. | a8 a4. g8 | }
>> > Even if you use the "Completion_heads_engraver".
>  It is very possible that the compiler issued some warnings.
>  I didn't pay attention; I looked for the "successfully
>  completed" message, and then refreshed the .ps,
>
>  I have let my eye run over your two solutions, and I am
>  totally awed and bowled over.  I notice your tons of guile,
>  which is very impressive.  Although I am somewhat familiar
>  with LISP, I have only used guile in a couple of spots
>  in my sorties into LIlypond.   So I shall do some more
>  reading and experimenting.
>
>  I have already remarked: the string players who have
>  played my parts as I set them -- bad bar checking and
>  all -- didn't seem to have difficulty; they were more
>  startled than anything else.  Which leads me to another
>  thought:  is it possible to delete _one_ bar line?
>  My thought(please excuse again the rough code indication,
>  for which I have been chastised several times!):  what
>  about
>|ees4 d c | c4. d8 bes4. \delete{|} a8 a4. g8 | g2 r4 | ?
>  This would be extremely unkosher -- I know nowhere where
>  this is done -- but I think it would be readable.  I
>  would like to try it on my LA friends and on my own 4tet.
>
>  Is it easy to implement such a \delete function, as
>  implemented above?  I would want the spacing to be
>  just as if the barline were there . . .
>
> All thoughts/ideas/implementations welcome!

As others remarked already
|
prints no BarLine, it is a check whether the measure is "full".

Do I understand correctly that you ask about empty/invisible/no
BarLine at some point of time?
And not about deleting a barcheck by hindsight?

If yes, easiest might be to use \bar "", (was said already).
Regard:

\relative c' {
c1
\bar ""
|
d
}

Cheers,
  Harm

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

Re: Problem with hemiola notation

[Alan McConnell]

On Mon, Sep 16, 2013 at 04:33:39PM +0100, Phil Holmes wrote:
>

> >My thought(please excuse again the rough code indication,
> >for which I have been chastised several times!):  what
> >about
> >   |ees4 d c | c4. d8 bes4. \delete{|} a8 a4. g8 | g2 r4 | ?
> >This would be extremely unkosher -- I know nowhere where
> >this is done -- but I think it would be readable.  I
> >would like to try it on my LA friends and on my own 4tet.
> >
> >Is it easy to implement such a \delete function, as
> >implemented above?  I would want the spacing to be
> >just as if the barline were there . . .
> >
> >All thoughts/ideas/implementations welcome!
> 
> Remember that | is _not_ a bar line, it's a bar check.  Does the
> following illustrate how you could do this?
> 
> \relative c'' { c1 | c \bar "" c c | c }
Alas, no.  I played with the \bar command and put in
some fancy stuff.  But, peculiarly enough, the original
bar line, mandated I guess by my 3/4 key signature, is
not replaced.  It is still implacably there!

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
An idea is not responsible for the people who believe in it.
If you only have a hammer, you tend to see every problem as a nail.

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

Re: Problem with hemiola notation

[Janek Warchoł]

2013/9/16 Alan McConnell :
> On Mon, Sep 16, 2013 at 10:01:42PM +0100, Phil Holmes wrote:
>>
>> >bar line, mandated I guess by my 3/4 key signature, is
>> >not replaced.  It is still implacably there!
>> >
>> >Alan
>>
>>
>> No fancy stuff needed. \bar "" puts in a blank bar line.
>I guess it does, although I can't see it.  But, as I
>said, I want/need the original barline not to be there.
>But it still is.  

Please send us a short and compilable example and we'll try to tell
you what exactly needs to be done.  Without an example, i have no idea
why Phil's solution wouldn't work for you.

Janek

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

Re: Problem with hemiola notation

[Phil Holmes]

- Original Message - 
From: "Alan McConnell" 

To: "Phil Holmes" 
Cc: "lilypond-user" 
Sent: Monday, September 16, 2013 9:45 PM
Subject: Re: Problem with hemiola notation



Remember that | is _not_ a bar line, it's a bar check.  Does the
following illustrate how you could do this?

\relative c'' { c1 | c \bar "" c c | c }

 Alas, no.  I played with the \bar command and put in
some fancy stuff.  But, peculiarly enough, the original
bar line, mandated I guess by my 3/4 key signature, is
not replaced.  It is still implacably there!

Alan



No fancy stuff needed. \bar "" puts in a blank bar line.

--
Phil Holmes

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

Re: Handicapped barcheck message in Lilypond version 2.17.26-1

[Phil Holmes]

Correct output with Windows on 2.17.26.  Let's stop reporting good output 
until the OP tells us where the bad output comes from.


warning: barcheck failed at: 1/2
   c'4
   d | e f g a b c

--
Phil Holmes 



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

Re: Problem with hemiola notation

[Alan McConnell]

On Mon, Sep 16, 2013 at 10:01:42PM +0100, Phil Holmes wrote:
>
> >bar line, mandated I guess by my 3/4 key signature, is
> >not replaced.  It is still implacably there!
> >
> >Alan
> 
> 
> No fancy stuff needed. \bar "" puts in a blank bar line.
   I guess it does, although I can't see it.  But, as I
   said, I want/need the original barline not to be there.
   But it still is.  

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
An idea is not responsible for the people who believe in it.
If you only have a hammer, you tend to see every problem as a nail.

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

Re: Handicapped barcheck message in Lilypond version 2.17.26-1

[Thomas Morley]

2013/9/16 Wim van Dommelen :
> I downloaded the newest version (2.17.26) today and saw a strange message
> converning barcheck. It lost the
>
> This sample code:
>
> \version "2.17.26"
>
> \relative f {
> c'4 d | e f g a b c
> }
>
> produces this error:
>
> GNU LilyPond 2.17.26
> Processing `test-barcheck.ly'
> Parsing...
> Interpreting music...
> test-barcheck.ly:4:13: warning: barcheck failed at: 0/0
> c'4
> d | e f g a b c
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `test-barcheck.ps'...
> Converting to `./test-barcheck.pdf'...
> Success: compilation successfully completed
>
> The ouput looks OK, but in the last stable the message will refer to "1/2"
> instead of "0/0" as it used to be.
>
> An entry for the bug-list?
>
> Regards,
> Wim.

Can't confirm on
Ubuntu 10.04 64-bit
LilyPond 2.17.26 via installer

Terminal shows:

GNU LilyPond 2.17.26
Processing `atest-22.ly'
Parsing...
Interpreting music...[8][16][24]
Preprocessing graphical objects...
Interpreting music...[8][16][24]
Preprocessing graphical objects...
Interpreting music...
atest-22.ly:3452:13: warning: barcheck failed at: 1/2
c'4
d | e f g a b c
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `atest-22.ps'...
Converting to `./atest-22.pdf'...
Success: compilation successfully completed


Cheers,
  Harm

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

Re: Handicapped barcheck message in Lilypond version 2.17.26-1

[SoundsFromSound]

Concerning the error message, I too see 1/2 in my log here. If that
helps...no 0/0 here.


David Kastrup wrote
> Wim van Dommelen <

> mail@

> > writes:
> 
>> I downloaded the newest version (2.17.26) today and saw a strange
>> message converning barcheck. It lost the
>>
>> This sample code:
>>
>>  \version "2.17.26"
>>
>>  \relative f {
>>  c'4 d | e f g a b c
>>  }
>>
>> produces this error:
>>
>>  GNU LilyPond 2.17.26
>>  Processing `test-barcheck.ly'
>>  Parsing...
>>  Interpreting music...
>>  test-barcheck.ly:4:13: warning: barcheck failed at: 0/0
>>  c'4
>>  d | e f g a b c
>>  Preprocessing graphical objects...
>>  Finding the ideal number of pages...
>>  Fitting music on 1 page...
>>  Drawing systems...
>>  Layout output to `test-barcheck.ps'...
>>  Converting to `./test-barcheck.pdf'...
>>  Success: compilation successfully completed
>>
>> The ouput looks OK, but in the last stable the message will refer to
>> "1/2" instead of "0/0" as it used to be.
>>
>> An entry for the bug-list?
> 
> Not before we get more data.  I don't see 0/0 in current master but
> rather 1/2 as before.  So we need to get more data (which platform
> exactly, which binary etc).  Since I can't reproduce this on current
> master and there has not really been any relevant change I can remember,
> this points to a bad compilation and/or a platform-specific problem.  Or
> something related to garbage collection.  We need to see whether we can
> reproduce this on another system.
> 
> -- 
> David Kastrup
> 
> 
> ___
> lilypond-user mailing list

> lilypond-user@

> https://lists.gnu.org/mailman/listinfo/lilypond-user





-
composer | sound designer
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Handicapped-barcheck-message-in-Lilypond-version-2-17-26-1-tp150887p150890.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: Handicapped barcheck message in Lilypond version 2.17.26-1

[David Kastrup]

Wim van Dommelen  writes:

> I downloaded the newest version (2.17.26) today and saw a strange
> message converning barcheck. It lost the
>
> This sample code:
>
>   \version "2.17.26"
>
>   \relative f {
>   c'4 d | e f g a b c
>   }
>
> produces this error:
>
>   GNU LilyPond 2.17.26
>   Processing `test-barcheck.ly'
>   Parsing...
>   Interpreting music...
>   test-barcheck.ly:4:13: warning: barcheck failed at: 0/0
>   c'4
>   d | e f g a b c
>   Preprocessing graphical objects...
>   Finding the ideal number of pages...
>   Fitting music on 1 page...
>   Drawing systems...
>   Layout output to `test-barcheck.ps'...
>   Converting to `./test-barcheck.pdf'...
>   Success: compilation successfully completed
>
> The ouput looks OK, but in the last stable the message will refer to
> "1/2" instead of "0/0" as it used to be.
>
> An entry for the bug-list?

Not before we get more data.  I don't see 0/0 in current master but
rather 1/2 as before.  So we need to get more data (which platform
exactly, which binary etc).  Since I can't reproduce this on current
master and there has not really been any relevant change I can remember,
this points to a bad compilation and/or a platform-specific problem.  Or
something related to garbage collection.  We need to see whether we can
reproduce this on another system.

-- 
David Kastrup


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

Re: Handicapped barcheck message in Lilypond version 2.17.26-1

[SoundsFromSound]

Hello,

I don't quite understand. The bar check failed because it's in the wrong
place, isn't it? 

Since LilyPond assumes 4/4 time by default (and since you didn't include any
meter manually), the bar should be between the F and G, right? That would be
4/4 time.

LilyPond is expecting 4/4 common time, and so that bar symbol is causing the
problem in the log I believe.

I'm a bit confused. Can you clarify the issue a bit more? Am I missing
something else?

I believe the bar check log message is correct because the "|" was not
placed in the correct spot in the code.

Thanks,
Ben



Wim van Dommelen-4 wrote
> I downloaded the newest version (2.17.26) today and saw a strange  
> message converning barcheck. It lost the
> 
> This sample code:
> 
>   \version "2.17.26"
> 
>   \relative f {
>   c'4 d | e f g a b c
>   }
> 
> produces this error:
> 
>   GNU LilyPond 2.17.26
>   Processing `test-barcheck.ly'
>   Parsing...
>   Interpreting music...
>   test-barcheck.ly:4:13: warning: barcheck failed at: 0/0
>   c'4
>   d | e f g a b c
>   Preprocessing graphical objects...
>   Finding the ideal number of pages...
>   Fitting music on 1 page...
>   Drawing systems...
>   Layout output to `test-barcheck.ps'...
>   Converting to `./test-barcheck.pdf'...
>   Success: compilation successfully completed
> 
> The ouput looks OK, but in the last stable the message will refer to  
> "1/2" instead of "0/0" as it used to be.
> 
> An entry for the bug-list?
> 
> Regards,
> Wim.
> 
> 
> 
> 
> 
> ___
> lilypond-user mailing list

> lilypond-user@

> https://lists.gnu.org/mailman/listinfo/lilypond-user





-
composer | sound designer
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Handicapped-barcheck-message-in-Lilypond-version-2-17-26-1-tp150887p150888.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

Handicapped barcheck message in Lilypond version 2.17.26-1

[Wim van Dommelen]

I downloaded the newest version (2.17.26) today and saw a strange  
message converning barcheck. It lost the


This sample code:

\version "2.17.26"

\relative f {
c'4 d | e f g a b c
}

produces this error:

GNU LilyPond 2.17.26
Processing `test-barcheck.ly'
Parsing...
Interpreting music...
test-barcheck.ly:4:13: warning: barcheck failed at: 0/0
c'4
d | e f g a b c
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test-barcheck.ps'...
Converting to `./test-barcheck.pdf'...
Success: compilation successfully completed

The ouput looks OK, but in the last stable the message will refer to  
"1/2" instead of "0/0" as it used to be.


An entry for the bug-list?

Regards,
Wim.




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

Re: Zigzag slurs

[Jayaratna]

Dear Urs,

i don't know how to say it in English: on a flute it should be a kind of
staccato made with no tongue, using the diaphragm, almost like a rithmical
vibrato. I hope it makes sense.

A



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Zigzag-slurs-tp150880p150885.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: Zigzag slurs

[Jayaratna]

Dear Pierre,

thank you, this is exactly what I needed. I still have to decide if I want
the thicker or the thinner one.

A



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Zigzag-slurs-tp150880p150886.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: Zigzag slurs

[Pierre Perol-Schneider]

2013/9/16 Jayaratna 

> Dear subscribers,
>

Hi,


>
> I need to make something similar to this. Any clues?


>

Here's some options :

\version "2.16.2" %??

\score {

  \new Staff

  \relative g'

   {

  \set Timing.beamExceptions = #'()

  \set Timing.baseMoment = #(ly:make-moment 1 8)

  \set Timing.beatStructure = #'(1 1 1 1 1 1 1 1)

  \override TimeSignature #' stencil = ##f

  \override TextSpanner #'style = #'zigzag

  \stemDown

  g16*2/3 b-.\startTextSpan b-. \stopTextSpan

  b-.\startTextSpan b-. b-. \stopTextSpan

  c-.\startTextSpan c-. c-. \stopTextSpan

  d-.\startTextSpan d-. d-. \stopTextSpan

%%% here's another option :

  \override TextSpanner #'style = #'trill

 d-.\startTextSpan d-. d-. \stopTextSpan

 c-.\startTextSpan c-. c-. \stopTextSpan

 c-.\startTextSpan c-. c-. \stopTextSpan

 c-.\startTextSpan c-. c-. \stopTextSpan

   }

}


Cheers,

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

Re: Zigzag slurs

[Urs Liska]

How would you describe the meaning of this?



Jayaratna  schrieb:
>Dear subscribers,
>
>I need to make something similar to this. Any clues?
>
>Thanks for your help,
>A
>
> 
>
>
>
>--
>View this message in context:
>http://lilypond.1069038.n5.nabble.com/Zigzag-slurs-tp150880.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

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Zigzag slurs

[Jayaratna]

Dear subscribers,

I need to make something similar to this. Any clues?

Thanks for your help,
A

 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Zigzag-slurs-tp150880.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: Problem with hemiola notation

[Phil Holmes]

- Original Message - 
From: "Alan McConnell" 

To: "Thomas Morley" 
Cc: "David Kastrup" ; "lilypond-user" 
Sent: Monday, September 16, 2013 4:20 PM
Subject: Re: Problem with hemiola notation



On Mon, Sep 16, 2013 at 12:32:25AM +0200, Thomas Morley wrote:

I have already remarked: the string players who have
played my parts as I set them -- bad bar checking and
all -- didn't seem to have difficulty; they were more
startled than anything else.  Which leads me to another
thought:  is it possible to delete _one_ bar line?
My thought(please excuse again the rough code indication,
for which I have been chastised several times!):  what
about
   |ees4 d c | c4. d8 bes4. \delete{|} a8 a4. g8 | g2 r4 | ?
This would be extremely unkosher -- I know nowhere where
this is done -- but I think it would be readable.  I
would like to try it on my LA friends and on my own 4tet.

Is it easy to implement such a \delete function, as
implemented above?  I would want the spacing to be
just as if the barline were there . . .

All thoughts/ideas/implementations welcome!


Remember that | is _not_ a bar line, it's a bar check.  Does the following 
illustrate how you could do this?


\relative c'' { c1 | c \bar "" c c | c }


--
Phil Holmes 



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

Re: Problem with hemiola notation

[Alan McConnell]

On Mon, Sep 16, 2013 at 12:32:25AM +0200, Thomas Morley wrote:
> 2013/9/15 Thomas Morley :
>
> > Hi Alan,
> >
> > I've got the image, thanks.
> > Now it's clear what you deserve.
"What I deserve"?  Whipping?  Methinks thou art getting
Shakespearian, as befits your nom de plume.


> > I know no way to let LilyPond checking bars without complain for code like:
> > \relative c' { \time 3/4 c4. d8 bes4. | a8 a4. g8 | }
> > Even if you use the "Completion_heads_engraver".
 It is very possible that the compiler issued some warnings.
 I didn't pay attention; I looked for the "successfully
 completed" message, and then refreshed the .ps,

 I have let my eye run over your two solutions, and I am
 totally awed and bowled over.  I notice your tons of guile,
 which is very impressive.  Although I am somewhat familiar
 with LISP, I have only used guile in a couple of spots
 in my sorties into LIlypond.   So I shall do some more
 reading and experimenting.

 I have already remarked: the string players who have
 played my parts as I set them -- bad bar checking and
 all -- didn't seem to have difficulty; they were more
 startled than anything else.  Which leads me to another
 thought:  is it possible to delete _one_ bar line?
 My thought(please excuse again the rough code indication,
 for which I have been chastised several times!):  what
 about 
   |ees4 d c | c4. d8 bes4. \delete{|} a8 a4. g8 | g2 r4 | ?
 This would be extremely unkosher -- I know nowhere where
 this is done -- but I think it would be readable.  I
 would like to try it on my LA friends and on my own 4tet.
 
 Is it easy to implement such a \delete function, as
 implemented above?  I would want the spacing to be
 just as if the barline were there . . .

All thoughts/ideas/implementations welcome!

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
An idea is not responsible for the people who believe in it.
If you only have a hammer, you tend to see every problem as a nail.

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

Re: some original LP scores

[Dave Phillips]

On 09/16/2013 10:18 AM, Janek Warchoł wrote:

Hi,

a somewhat late answer...



Hi Janek,

Thanks for your comments and suggestions, I agree with your judgements. 
Umeko needs a complete code rewrite, the Sonatina somewhat less. The 
trios are the most ambitious things I've done in LP, I've a lot to fix 
there.


Btw, Rachael asked if the guitar pieces had been recorded. They have 
not, though the Sonatina is available in a recorded MIDI version at

http://archive.org/details/SonatinaForAnImaginaryGuitarist.

Unfortunately time is in short supply these days, but I'll try to do a 
major clean-up over the next two weeks. I'll announce the refreshed 
scores when they're ready.


Best,

dp


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

Re: some original LP scores

[Janek Warchoł]

Hi,

a somewhat late answer...

2013/9/8 Dave Phillips :
> I've revised some pieces and added some new things here :
>
> http://linux-sound.org/dlp-music-lilypond/
>
> Comments and suggestions are most welcome, particularly regarding part
> writing and instrument-specific matters. This work was done primarily in
> response to an on-going article project, I'd like it to be presented as well
> as possible.

Sonatina Prelude
---

* i recommend upgrading to newest development version (there's almost
nothing to change in syntax, actually).  Current dev version produces
consistent spacing on both pages (in your rendering, systems on 2nd
page are much closer than on the first page), and also accents don't
touch slurs.

* the "proper" way to indicate guitar positions is using text
spanners: 
http://www.lilypond.org/doc/v2.16/Documentation/notation/guitar#indicating-position-and-barring
(they automatically adjust their length when the spacing changes).

* in my opinion it would be clearer to define two voices and combine
them instead of creating "splits" on a per-measure basis.  But that's
a matter of personal preference.

Umeko
-

* I find the voicing in m.61-64 a bit strange.

* accent in m.73 collides with the notes.

* placement of whole noteheads in last measure looks strange.

I believe these problems would have a smaller chance of appearing if
there were full-length voices, i.e. if you had used

melodyI = { 104 bars of music }
melodyII = { 104 bars of music }
melodyIII = { 104 bars of music }

<<
  \melodyI
  \melodyII
  \melodyIII
>>

rather than << { } \\ { } \\ { } >> construct.


Trios
---

* it would be good to increase the distance between systems, either by
reducing font-size or by spreading the piece onto more pages.

Can i save these scores as a material for analyzing LilyPond
performance in the future?

best,
Janek

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

Re: Reminder: LilyPond meeting in Waltrop, Germany, 2013-09-20 to 2013-09-24

[Jan-Peter Voigt]

Hello out there,
I am not able to take the journey, though I'd like to.
But are there possibilities to join in via skype, google or some webrtc 
link?


Cheers, Jan-Peter

Am 14.09.13 13:36, schrieb David Kastrup:

This is a reminder that next weekend, Sept 20th to 24th, there will be a
LilyPond developer and user meeting in Waltrop, Germany.  After the
first attempt to schedule the meeting in August, we rescheduled in order
to better meet people's calendars.



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

Re: Reminder: LilyPond meeting in Waltrop, Germany, 2013-09-20 to 2013-09-24

[Pierre Perol-Schneider]

2013/9/15 Janek Warchoł 

> Hi,
>
> 2013/9/14 David Kastrup :
> > This is a reminder that next weekend, Sept 20th to 24th, there will be a
> > LilyPond developer and user meeting in Waltrop, Germany.  After the
> > first attempt to schedule the meeting in August, we rescheduled in order
> > to better meet people's calendars.
>
> I'd like to come, but that would only make sense if there were several
> other participants.  So, please declare yourself!
> Janek
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

I'd love to come but for the moment I'm a little short money wise.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 350 "\relative"s on all parts - is it possible to simply the code?

[Wim van Dommelen]

On 16 Sep 2013, at 11:28 , Richard Sabey wrote:

   . , that using absolute mode is better, and one reason is  
that it makes it easier to make the Lilypond notation for later bits  
of a musical work, using the Lilypond notation you have already  
written for earlier bits. You can copy and paste without having to  
recheck the octave of the first pitch you paste.


To avoid the copy-and-paste problem and finding yourself in the wrong  
octave too much, I have the habit of starting each part (or section or  
page) with a reference to the absolute pitch I am at that point. That  
corrects the code at least at that point and more, it tells you with  
an error-message that the flow of relative coded music doesn't add up  
correctly.


Regards,
Wim.

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

Re: Markup spacing issue

[Janek Warchoł]

2013/9/16 Thomas Morley :
> I didn't look at Janek's link, though you might be interested in the
> markup-command 'compensate-indent' I wrote some time ago.
> Shouldn't be too hard to adept it, though it works even right now.
>
> [lily snippet]

I'm not sure if i fully understand what this code does, but it appears
to me that together with my snippet it may provide an ultimate
solution for aligning stanzas (?).  In particular, maybe it would
solve a bug that is mentioned in line 38 of my snippet.

Suggestions for improving my snippet are welcome!

best,
Janek

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

Re: Markup spacing issue

[Thomas Morley]

2013/9/16 Noeck :
>
>> You most probably want to use \null instead of \hspace.  And you
>> probably will be interested in this snippet:
>> http://github.com/openlilylib/snippets/blob/master/templates/adjustable-centered-stanzas.ily
>>
>> best,
>> Janek
>
> That is a very useful snippet. Thanks!
>
> Cheers,
> Joram
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

Hi Joram,

I didn't look at Janek's link, though you might be interested in the
markup-command 'compensate-indent' I wrote some time ago.
Shouldn't be too hard to adept it, though it works even right now.

\version "2.17.26" %"2.16.0"

#(define-markup-command (compensate-indent layout props arg)(markup?)
#:properties ((add-space  0)
  (stack-dir RIGHT))
  (let* ((amount (+ add-space (ly:output-def-lookup layout 'indent)))
 (lst (if (= stack-dir RIGHT)
  (list (make-hspace-markup amount) arg)
  (reverse (list (make-hspace-markup amount) arg
 (mrkp (make-concat-markup lst)))
  (interpret-markup layout props mrkp)))


\markup
  \override #'(add-space . -5 )
  \box
\fill-line {
\box
  \compensate-indent
 \column {
   "Trägt die schönsten bunten Schleifen,"
 }
\box
\override #'(stack-dir . -1)
  \compensate-indent
\column {
  "Hat das Jahr genug vom Tanzen,"
}
}

Delete the \box-command, only inserted for better viewing what happens.


HTH,
  Harm

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

Re: 350 "\relative"s on all parts - is it possible to simply the code?

[Richard Sabey]

> Date: Fri, 13 Sep 2013 14:31:47 -0700 (PDT)
> From: MING TSANG 
> To: Urs Liska , Kieren MacMillan
>   
> Cc: David Nalesnik ,"lilypond-user@gnu.org"
>   
> Subject: Re: 350 "\relative"s on all parts - is it possible to simply
>   the code?
> Message-ID:
>   <1379107907.22293.yahoomail...@web142601.mail.bf1.yahoo.com>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Urs, Jieren & David:
> 
> Thank you for the suggestion. I will code parts with "\relative" and then use 
> frecobaldi to convert it to absolute. ?This will save time to code 350 
> "\relative"s. ?The code is much cleaner.

Glad you found a solution you like, Ming.

I would steer clear of \relative completely. When I started using Lilypond, I 
used \relative because Lilypond's documentation seemed to me to say "\relative 
is recommended because it makes data entry easier". I found, from bitter 
experience, that using absolute mode is better, and one reason is that it makes 
it easier to make the Lilypond notation for later bits of a musical work, using 
the Lilypond notation you have already written for earlier bits. You can copy 
and paste without having to recheck the octave of the first pitch you paste.
  ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Markup spacing issue

[Noeck]

> You most probably want to use \null instead of \hspace.  And you
> probably will be interested in this snippet:
> http://github.com/openlilylib/snippets/blob/master/templates/adjustable-centered-stanzas.ily
> 
> best,
> Janek

That is a very useful snippet. Thanks!

Cheers,
Joram

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

Re: Problem with hemiola notation

[David Kastrup]

"Phil Holmes"  writes:

> From: "David Kastrup" 
>> Actually, I think it's about time to move the LSR to 2.16.
>
>
> We have had problems contacting the maintainer, otherwise would have
> tackled this.

Sigh.  We have a bunch of ailing infrastructure projects.  The LSR is
not in as bad a shape as Mutopia yet, but then it's closer associated
with LilyPond.  If we had a flood of LilyPond volunteers hammering at
our gates not knowing how to help the project, it would be worth
thinking of setting up new projects/websites taking off where the
previous volunteers managed to get them.

But it's not like the core project itself has enough people filling in,
like, on translations of the documentation.

-- 
David Kastrup

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

Re: Markup spacing issue

[David Kastrup]

Noeck  writes:

> Hi,
>
> is this a bug or intended: The following code worked nicely in 2.16 but
> with the latest version, the two columns do not fill the whole page
> width (what I would expect from fill-line). The 2.17 docs have a similar
> example - I found no syntax change.
>
> \version "2.17.26" %"2.16.0"
>
> \markup \fill-line {
>   \hspace #0.1% shows no visible effect
>   \column {
> "Trägt die schönsten bunten Schleifen,"
>   }
>   \hspace #0.1% does not push the next column to the right
>   \column {
> "Hat das Jahr genug vom Tanzen,"
>   }
>   \hspace #0.1
> }
>
> Is this a bug?

Well, partly it's a documentation problem, partly new behavior, partly
it may also be a bug.  The problem is that previously, \hspace was
implemented as going forward by the stated amount minus a space width.
In combination with the following interword space (_iff_ there was an
interword space following, otherwise \hspace would go wrong), this
resulted in 0.1 amounts of space.

\fill-line stretches the interword space.

Now \hspace has been changed to only actually take the required space
and it is _not_ getting surrounded by word space.  So there is less
opportunity for stretching.  Now \fill-line is not yet doing everything
right anyway, and that's
http://code.google.com/p/lilypond/issues/detail?id=3504>.  So there
will still be changes how the above works out.  But it's not clear that
it will, or that it indeed should work exactly as before.

-- 
David Kastrup


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

Re: Markup spacing issue

[Janek Warchoł]

2013/9/16 Noeck :
>
>> The way hspace works has been changed (corrected).  In your example,
>> omitting the hspace makes the text fill the line.
>
> A follow-up question: How can I push the columns a bit from the margins?
> (Like I could with the \hspace commands before.)

You most probably want to use \null instead of \hspace.  And you
probably will be interested in this snippet:
http://github.com/openlilylib/snippets/blob/master/templates/adjustable-centered-stanzas.ily

best,
Janek

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

Re: Markup spacing issue

[Noeck]

> 
> The way hspace works has been changed (corrected).  In your example,
> omitting the hspace makes the text fill the line.
> 
> -- 
> Phil Holmes
> 

Cool, that's even better (easier). In that case, the docs should be updated:
http://www.lilypond.org/doc/v2.17/Documentation/notation/stanzas#printing-stanzas-at-the-end-in-multiple-columns

A follow-up question: How can I push the columns a bit from the margins?
(Like I could with the \hspace commands before.)

Joram

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

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Davide Liessi]

Dear Guy,

2013/9/16 Guy Stalnaker :
> Tonight I tried to use your new port. The port compiles with no errors. The
> macport install process failed when attempting to activate your
> Frescobaldi+devel saying that previous files exist.

I'm sorry I didn't notice this problem on my machine before the
publication of my Portfiles.
I had manually installed Frescobaldi and python-poppler-qt4 but not
with Philippe's guide: I had installed them explicitly setting the
prefix to something different from /opt/local, so they didn't interact
with MacPorts' directory hierarchy.

This problem occurs because when you do "python setup.py install" for
python-poppler-qt4 and Frescobaldi, they are installed inside the
directory tree of the Python version you used (in this case the
MacPorts' one).
So their files are copied inside MacPorts' tree.

When you then install them with my Portfiles, MacPorts tries to copy
the same files in the same locations, but it finds the manually
installed files and refuses to continue.
This is because manually installed files can be user data files (e.g.
databases) or user settings files (like the ones in /opt/local/etc),
so by default MacPorts cannot overwrite files that weren't written by
itself.

Philippe is right when he says that
2013/9/16 Philippe Massart :
> The idea is to really avoid touching manually the macport tree.

The solution, that Philippe mentions, should be simply to force the
activation with '-f' option.
This allows MacPorts to overwrite existing files.

2013/9/16 Guy Stalnaker :
> I did a check by
> attempting to deactivate Frescobaldi, but macports said there was not an
> activated Frescobaldi port.

MacPorts was right: there wasn't an active Frescobaldi or
python-poppler-qt4 port, but it couldn't activate them because there
were already files in place.

2013/9/16 Philippe Massart :
> Now, the errors you have when trying to open files come probably from the
> folders you moved.

Probably.
The best thing to do, in my opinion, is to uninstall
frescobaldi(-devel) and py27-python-poppler-qt4 ports, move back the
folders and files in their original location and then force install
frescobaldi(-devel).
This way all other ports should work correctly and the force install
should take care of overwriting the manually installed files.

2013/9/16 Philippe Massart :
> Like you, I had a manually installed frescobaldi version; since "forcing"
> the activation of the portfile, my both frescobaldi install are now working:
> the one from macport, the other manually installed (and sync via github).

As long as you don't "python setup.py install" Frescobaldi (with the
default prefix) there shouldn't be interaction problems between
MacPorts and manually installed versions.
My advice is to avoid "python setup.py install" for Frescobaldi at all
and run it from its directory.
You can rely on MacPorts for all dependencies (including
python-poppler-qt4) and then have MacPorts' Frescobaldi and, e.g. in
your home directory, multiple directories each with a different
version of Frescobaldi (or a Git repository in which you can switch
versions).

Dear Guy, let us know if you need further assistance and if the "undo
move / force install" solution works for you.
I think I should put a notice on my repository's home page about this
problem, but I'll wait and see if the proposed solution works for you.

Best wishes.
Davide

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

Re: Markup spacing issue

[Phil Holmes]

- Original Message - 
From: "Noeck" 

To: "lilypond-user" 
Sent: Monday, September 16, 2013 9:57 AM
Subject: Markup spacing issue



Hi,

is this a bug or intended: The following code worked nicely in 2.16 but
with the latest version, the two columns do not fill the whole page
width (what I would expect from fill-line). The 2.17 docs have a similar
example - I found no syntax change.

\version "2.17.26" %"2.16.0"

\markup \fill-line {
 \hspace #0.1 % shows no visible effect
 \column {
   "Trägt die schönsten bunten Schleifen,"
 }
 \hspace #0.1 % does not push the next column to the right
 \column {
   "Hat das Jahr genug vom Tanzen,"
 }
 \hspace #0.1
}

Is this a bug?

Cheers,
Joram



The way hspace works has been changed (corrected).  In your example, 
omitting the hspace makes the text fill the line.


--
Phil Holmes 



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

Re: Problem with hemiola notation

[Phil Holmes]

- Original Message - 
From: "David Kastrup" 

To: "Janek Warchoł" 
Cc: "Thomas Morley" ; "lilypond-user" 


Sent: Monday, September 16, 2013 10:01 AM
Subject: Re: Problem with hemiola notation



Janek Warchoł  writes:


Hi Harm,

2013/9/16 Thomas Morley :

Hi again,

I now come up with a (hopefully) improved version.
It is a function which takes a dotted(!) note as argument replacing it
with the main note and a dot (instead of a tied note)


Looks nice!


\version "2.16.2"
% Does not work with 2.14.2 !
[...]


If i understand correctly this cannot be added to LSR,


Actually, I think it's about time to move the LSR to 2.16.

--
David Kastrup



We have had problems contacting the maintainer, otherwise would have tackled 
this.


--
Phil Holmes 



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

Re: Problem with hemiola notation

[David Kastrup]

Janek Warchoł  writes:

> Hi Harm,
>
> 2013/9/16 Thomas Morley :
>> Hi again,
>>
>> I now come up with a (hopefully) improved version.
>> It is a function which takes a dotted(!) note as argument replacing it
>> with the main note and a dot (instead of a tied note)
>
> Looks nice!
>
>> \version "2.16.2"
>> % Does not work with 2.14.2 !
>> [...]
>
> If i understand correctly this cannot be added to LSR,

Actually, I think it's about time to move the LSR to 2.16.

-- 
David Kastrup

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

Re: Problem with hemiola notation

[Janek Warchoł]

Hi Harm,

2013/9/16 Thomas Morley :
> Hi again,
>
> I now come up with a (hopefully) improved version.
> It is a function which takes a dotted(!) note as argument replacing it
> with the main note and a dot (instead of a tied note)

Looks nice!

> \version "2.16.2"
> % Does not work with 2.14.2 !
> [...]

If i understand correctly this cannot be added to LSR, so maybe you
could add it here http://github.com/openlilylib/snippets ? (scroll
down to see description)

I believe that it won't take you more that 10-15 minutes to submit the
snippet even if you're not familiar with GitHub at all (and of course
the next time will probably be under 2 minutes).

best,
Janek

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

Markup spacing issue

[Noeck]

Hi,

is this a bug or intended: The following code worked nicely in 2.16 but
with the latest version, the two columns do not fill the whole page
width (what I would expect from fill-line). The 2.17 docs have a similar
example - I found no syntax change.

\version "2.17.26" %"2.16.0"

\markup \fill-line {
  \hspace #0.1  % shows no visible effect
  \column {
"Trägt die schönsten bunten Schleifen,"
  }
  \hspace #0.1  % does not push the next column to the right
  \column {
"Hat das Jahr genug vom Tanzen,"
  }
  \hspace #0.1
}

Is this a bug?

Cheers,
Joram

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