Re: How to chop a slur over a rest in a 1. volta repeat

2009-03-20 Thread Trevor Daniels


There's a way, but it's rather messy.

Here's some code to give you a start.  Essentially you draw a 
coloured box
with \markup, experiment to get the right size, move it into the 
right
position, and place it in layer 2 to put it above everything else, 
and
then make the box white.  If you add this when everything else is 
stable
it is just about do-able.  One problem is it pushes the volta marks 
too

high.  Offhand I don't know how to prevent this.

\alternative {
 { r1
   % move to right position
   -\tweak #'extra-offset #'(-2 . -1.5)
   % place in higher layer
   -\tweak #'layer #2
   ^\markup {
 % specify color
 \with-color #white  % start with a visible colour
 % specify size
 \filled-box #'(0 . 10) #'(0 . 1) #0
   }
  |
}


- Original Message - 
From: Maestraccio maestrac...@gmail.com

To: bug-lilypond@gnu.org
Sent: Friday, March 20, 2009 12:10 AM
Subject: How to chop a slur over a rest in a 1. volta repeat



I'm not top posting.




Recently I stumbled upon this problem and did not find a 
satisfying answer


in neither the Documentation segment nor in the archives:



-



\version 2.10.33

\paper{ ragged-right=##t }



\relative c'' {

\repeat volta 2 {

c,2^\markup {tacet la 1 \hspace #-1.5 \raise #1.0 {ma} volta}\p(

b a g4) g'8( f |e4 c d2) |r4 e8( c cis4 a' |

}

\alternative {

 {r1 |}

 {c,!2 b) |}

}

}



-



Please note the important tacet la 1ma volta line, which 
indicates rests


during the first occurrence of this part.



It is a fragment taken from a bigger score and printing the whole 
thing twice


(which may seem obvious here) is not a solution.



I experimented with laissezVibrer and repeatTie, but these 
commands


really end and rebegin the tie (not even a slur) al niente 
(among other


drawbacks) instead of chopping the slur in two at a thick point.



Is there a way of radically ending a slur at a predefined point at 
a certain


thickness (and beginning it likewise at the other end) or somehow

interrupting/blanking/hiding the slur over this 1. volta rest?



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond





___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: MIDI interface (feature request)

2009-03-20 Thread Hans Aberg

On 20 Mar 2009, at 02:34, Kees van den Doel wrote:

One idea is to generate some other format, perhaps Scala seq files,  
which in turn can produce MIDI files. When there is microtonal  
information present, Scala can use special algorithms to assign  
MIDI channels, and also keep track of different synth capabilities.  
I'm not sure how that format stands up with respect to LilyPond  
information in general, but such a format could be developed in a  
way directly that MIDI output cannot.


That would be very useful for other reasons too. Currently I can't  
tune my lilypond generated Persian midi
in scala because the pitchbends generated from lilypond for the  
microtones

are ignored when producing a scale .seq file.


I have discussed it with Manual Op de Coul, and he think it is a good  
idea, but the problem is finding someone that can do the hook within  
LilyPond.


The format is here
  http://www.huygens-fokker.org/scala/seq_format.html

You might check if it is rich enough for what you are doing.

  Hans




___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Point and Click on Ubuntu 8.04

2009-03-20 Thread Francisco Vila
2009/3/19 Craig Bakalian cbakal...@copper.net:
 TextEdit is its label from the ubuntu's applications menu, but it really is
 gedit.  It is called gedit from the about menu.  And, Ubuntu's Document
 Viewer is what I am using to open up pdfs with.  It is showing line number
 and column, just no click through.

The default PDF viewer in GNOME is evince. Unfortunately,
point-and-click does not work by default with the gedit/evince
combination, in part because IIRC gedit does not support placing the
cursor on both coordinates, only the line. A combination that is known
to work is Sun JRE + jEdit + LilyPondTool. There are others, please
refer to the documentation for clues on how to install the textedit
protocol etc.
-- 
Francisco Vila. Badajoz (Spain)


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: MIDI interface (feature request)

2009-03-20 Thread Mats Bengtsson



Hans Aberg wrote:

On 20 Mar 2009, at 02:34, Kees van den Doel wrote:

One idea is to generate some other format, perhaps Scala seq files, 
which in turn can produce MIDI files. When there is microtonal 
information present, Scala can use special algorithms to assign MIDI 
channels, and also keep track of different synth capabilities. I'm 
not sure how that format stands up with respect to LilyPond 
information in general, but such a format could be developed in a 
way directly that MIDI output cannot.


That would be very useful for other reasons too. Currently I can't 
tune my lilypond generated Persian midi
in scala because the pitchbends generated from lilypond for the 
microtones

are ignored when producing a scale .seq file.


I have discussed it with Manual Op de Coul, and he think it is a good 
idea, but the problem is finding someone that can do the hook within 
LilyPond.


The format is here
  http://www.huygens-fokker.org/scala/seq_format.html
One problem in LilyPond is that the part of the code currently handling 
the MIDI output, is much less flexible than the code handling ordinary 
printed output. On the other hand, this code is in general much less 
involved than the code for the printed output, so in the end it's 
perhaps not more difficult of time-consuming than to add another output 
format for the printed output, at least if you don't have the ambition 
to add the same flexibility for the sound output backend as for the 
printed output backend.


   /Mats


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: MIDI interface (feature request)

2009-03-20 Thread Hans Aberg

On 20 Mar 2009, at 09:59, Mats Bengtsson wrote:

in scala because the pitchbends generated from lilypond for the  
microtones

are ignored when producing a scale .seq file.


I have discussed it with Manual Op de Coul, and he think it is a  
good idea, but the problem is finding someone that can do the hook  
within LilyPond.


The format is here
 http://www.huygens-fokker.org/scala/seq_format.html
One problem in LilyPond is that the part of the code currently  
handling the MIDI output, is much less flexible than the code  
handling ordinary printed output. On the other hand, this code is in  
general much less involved than the code for the printed output, so  
in the end it's perhaps not more difficult of time-consuming than to  
add another output format for the printed output, at least if you  
don't have the ambition to add the same flexibility for the sound  
output backend as for the printed output backend.


The idea is to make an interface so that those interested in  
programming the printing program need not engage with those interested  
in generating sound output programs, and vice versa. There are also  
programs like

  http://people.bath.ac.uk/masjpf/CDP/csinfopg.htm
  http://chuck.cs.princeton.edu/
one might use for generating sound output.

So the format might be more general than Scala seq files. A user might  
want to add interpretations directly into the score or tweak the  
sequence file that LilyPond writes.


  Hans




___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: MIDI interface (feature request)

2009-03-20 Thread Kees van den Doel


- Original Message -
From: Hans Aberg hab...@math.su.se
Date: Wednesday, March 18, 2009 4:42 am
Subject: Re: MIDI interface (feature request)
To: Kees van den Doel kvand...@shaw.ca
Cc: bug-lilypond@gnu.org

 On 18 Mar 2009, at 02:27, Kees van den Doel wrote:
 
  Not sure I understand, I need a vibrato, not a trill.
 
 Well, how do you want realize your vibrato, MIDI-wise?

Set MIDI controller number 1 to a non-zero value on the channel.

In abc I can write:

%%MIDI controller 1 127

Kees


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: MIDI interface (feature request)

2009-03-20 Thread Kees van den Doel

 On 18 Mar 2009, at 19:26, Kees van den Doel wrote:
 
   Well, how do you want realize your vibrato, MIDI-wise?
 
  Set MIDI controller number 1 to a non-zero value on the channel.
 
 Aren't you using a synth with a vibrato channel then?

Of course. Not sure what you are thinking of with all these questions.
Point is that if I could generate MIDI messages in the score I could do what I 
want.

Kees


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: MIDI interface (feature request)

2009-03-20 Thread Kees van den Doel

 On 19 Mar 2009, at 09:57, Mats Bengtsson wrote:
 
  One technical problem of such a general feature, is that some 
 MIDI  
  commands that are intended to apply to all MIDI tracks should 
 be  
  inserted in track 0, whereas other MIDI commands (that contain 
 a  
  channel number) should be inserted in the same track as 
 the  
  corresponding music. Another complication (at least 
 conceptually) is  
  the different concepts used in LilyPond and MIDI and how they 
 are  
  mapped to each other. By default, MIDI channels correspond to 
 Staff  
  contexts in LilyPond, but this can be changed by redefining 
 the  
  context definitions in LilyPond. A final complication is the 
 lack of  
  standardization of MIDI.
 
  See http://lists.gnu.org/archive/html/bug-lilypond/2003-
 10/msg00069.html 
   for some related information.
 
 One idea is to generate some other format, perhaps Scala seq 
 files,  
 which in turn can produce MIDI files. When there is 
 microtonal  
 information present, Scala can use special algorithms to assign 
 MIDI  
 channels, and also keep track of different synth capabilities. 
 I'm not  
 sure how that format stands up with respect to LilyPond 
 information in  
 general, but such a format could be developed in a way directly 
 that  
 MIDI output cannot.

That would be very useful for other reasons too. Currently I can't tune my 
lilypond generated Persian midi
in scala because the pitchbends generated from lilypond for the microtones
are ignored when producing a scale .seq file.

Kees


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond