Re: Some slur and part was forgotten with combined parts.

[James E. Bailey]

Am 08.01.2009 um 04:42 schrieb T. Kiriyama:


Hi,all,
I just find another problems with part cobination.
The slur for partone, bar number between 2 and 3 and drawing of
partone, bar number 5 to 6 were forgotten.
Is this a bug or  is there any kind of solution?
Best Regards,

%%
%% lilypond source text file
%%
%% for future compatibility
\version "2.11.65"
%%
\include "deutsch.ly"
%%
%%
partone = \relative c' {
  \clef bass
  \time 4/4
  \key c \major
  cis,4 r4 r4 cis4( |
  d4.(e8 f b d f) |
  \bar "|."
}


It looks to me like the slur isn't closed. Lilypond should complain  
about that.



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

Re: lsr having problems?

[James E. Bailey]

Am 07.01.2009 um 23:11 schrieb chip:

I just tried to register on the LSR, got to the registration page,  
entered my info, but the cursor never changes from the timer to the  
arrow. Pressing the go button does nothing. Using Firefox on Linux.  
I also tried on my XP box in both Firefox and IE7 but had the same  
problems. Also, the certificate is not correct, had to do some  
accepting an unknown certificate or something before the page would  
even begin to load.

Regards,


I don't know if this is a new problem or not, but I've never been  
able to successfully register on lsr.



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

Re: short instrument name setting

[Graham Percival]

On Wed, Jan 07, 2009 at 08:47:41AM -0500, Kieren MacMillan wrote:
> Hi Graham,
>
>> Use \tag.  It was invented for *precisely* this situation.
>> It should be somewhere in NR 3.
>
> I avoid \tag at all costs — and suggest the same to other users, and  
> warn newbies against it (or don't introduce them to it in the first  
> place) — because it FORCES THE MIXTURE OF CONTENT AND PRESENTATION,  
> which is A Bad Thing™.

WTM?!  It's like a  in HTML.  It doesn't do anything in
itself.

  \tag #'score \blah blah

doesn't force you to think about presentation in a bad way; it
just means that you only want to display something in a score.  Or
maybe in everything apart from the score.  I can't remember how
the command works.

> If there's another (non-\tag) way to do the same thing, that's The  
> Better Way™.

You want a way of indicating that something is only to be used for
particular instruments/situations, without using a command that's
designed to be used for particular instrument/situations?

Cheers,
- Graham


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

RE: Fermata over barline problem

[Nick Payne]

Thanks. Using

\override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible

Fixed the problem.

Nick

> -Original Message-
> From: Dmytro O. Redchuk [mailto:brownian@gmail.com]
> Sent: Thursday, 8 January 2009 18:52
> To: Nick Payne
> Cc: Neil Thornock; lilypond-user@gnu.org
> Subject: Re: Fermata over barline problem
> 
> 2009/1/8 Nick Payne :
> > I have a fermata over a double barline, notated with
> >
> > \bar "||" \mark\markup\small {\musicglyph #"scripts.ufermata"}
> >
> > This works fine except where the barline falls at the end of a line
> on the
> > score, in which case the fermata is placed over the clef sign at the
> start
> > of the next line. Is this a bug or something I am doing wrong?
> Isn't there your situation described in Notation Reference (NR), 1.8.1
> ?
> 
> http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Writing-
> text#Text-marks
> 
> > I'm running 2.12.1 on Vista. The PNGs show the output for a couple of
> the
> > parts, one where the fermata is correctly positioned and the other
> where it
> > is being placed above the clef sign.



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

Re: Some slur and part was forgotten with combined parts.

[T. Kiriyama]

Yes, It's my mistake.
Does anyone know how to find such kind of easy mistake like gcc's -Wall option ?

2009/1/8 James E. Bailey :
>
> Am 08.01.2009 um 04:42 schrieb T. Kiriyama:
>
>> Hi,all,
>> I just find another problems with part cobination.
>> The slur for partone, bar number between 2 and 3 and drawing of
>> partone, bar number 5 to 6 were forgotten.
>> Is this a bug or  is there any kind of solution?
>> Best Regards,
>>
>> %%
>> %% lilypond source text file
>> %%
>> %% for future compatibility
>> \version "2.11.65"
>> %%
>> \include "deutsch.ly"
>> %%
>> %%
>> partone = \relative c' {
>>  \clef bass
>>  \time 4/4
>>  \key c \major
>>  cis,4 r4 r4 cis4( |
>>  d4.(e8 f b d f) |
>>  \bar "|."
>> }
>
> It looks to me like the slur isn't closed. Lilypond should complain about
> that.
>

-- 
T. Kiriyama / lilypon...@gmail.com


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

Re: Some slur and part was forgotten with combined parts.

[T. Kiriyama]

Uum... 2nd problem is my mistake, but first problem is still there.
How about this?

2009/1/8 James E. Bailey :
>
> Am 08.01.2009 um 04:42 schrieb T. Kiriyama:
>
>> Hi,all,
>> I just find another problems with part cobination.
>> The slur for partone, bar number between 2 and 3 and drawing of
>> partone, bar number 5 to 6 were forgotten.
>> Is this a bug or  is there any kind of solution?
>> Best Regards,
>>
>> %%
>> %% lilypond source text file
>> %%
>> %% for future compatibility
>> \version "2.11.65"
>> %%
>> \include "deutsch.ly"
>> %%
>> %%
>> partone = \relative c' {
>>  \clef bass
>>  \time 4/4
>>  \key c \major
>>  cis,4 r4 r4 cis4( |
>>  d4.(e8 f b d f) |
>>  \bar "|."
>> }
>
> It looks to me like the slur isn't closed. Lilypond should complain about
> that.
>



-- 
T. Kiriyama / lilypon...@gmail.com


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

Minimum width for a bar

[Nick Payne]

How can I specify that a bar containing only a single tied note be a certain
minimum width? Because the note is tied, I tried using

\once\override Slur #'minimum-length = #16

That works if the bar is in the middle of a line, but it doesn't work at the
end of a line, which is precisely where I need it to prevent text
indications from going right out to the page edge. I had a fair hunt through
the documentation without finding a solution.

Nick
<><>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Some slur and part was forgotten with combined parts.

[James E. Bailey]

Am 08.01.2009 um 12:03 schrieb T. Kiriyama:


Yes, It's my mistake.
Does anyone know how to find such kind of easy mistake like gcc's - 
Wall option ?


I don't know what editor you use, but if it has a syntax hilighting,  
you can use that to easily hilight ( and end the hilight with ). I  
use nano, and exactly that.



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

Re: Minimum width for a bar

[James E. Bailey]

Am 08.01.2009 um 12:20 schrieb Nick Payne:

How can I specify that a bar containing only a single tied note be  
a certain

minimum width? Because the note is tied, I tried using

\once\override Slur #'minimum-length = #16

That works if the bar is in the middle of a line, but it doesn't  
work at the

end of a line, which is precisely where I need it to prevent text
indications from going right out to the page edge. I had a fair  
hunt through

the documentation without finding a solution.



Section 1.8.1 on text may help. \override Score.PaperColumn #'keep- 
inside-line = ##t may do what you're looking to do.



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

Re: short instrument name setting

[Kieren MacMillan]

Graham,


You want a way of indicating that something is only to be used for
particular instruments/situations, without using a command that's
designed to be used for particular instrument/situations?


No, I want you to tell me why I should use \tag to hide/display an  
instrument name in a particular score, when it works perfectly well —  
and doesn't mix content with presentation — to do the same thing by  
manipulating the \with or \context block of the score definition.


=)

Cheers,
Kieren.

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

Re: short instrument name setting

[Kieren MacMillan]

Hi Daniel,


If, for a specific presentation feature, there's another way to turn
that feature on and off that doesn't require extra annotations in your
content definition, then certainly, that's the better way in that  
case,


That's exactly what I said — thanks for the +1!  ;-)
Kieren.

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

Re: short instrument name setting

[Valentin Villenave]

2009/1/8 Kieren MacMillan :

> That's exactly what I said — thanks for the +1!  ;-)

+another 1 for me.

\tag sucks, \context rulz.

Cheers,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Divide a note inside of music-define-function

[Michael Pozhidaev]

Hello!

Please, help me with music function creation. My function has one
argument to represent one note, how can I get the same note, but with only a 
half of its
original duration?

Of course, the following is completely wrong, but something like:
myfunc =
#(define-music-function (parser location note) (ly:music?)
#{
$note *0.5
#})

Thanks!
-- 
Michael Pozhidaev. E-mail: m...@altlinux.ru.
Tomsk State University. http://www.csd.tsu.ru
ALT Linux Team. http://www.altlinux.ru



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

Re: Divide a note inside of music-define-function

[Valentin Villenave]

2009/1/8 Michael Pozhidaev :
> Please, help me with music function creation. My function has one
> argument to represent one note, how can I get the same note, but with only a 
> half of its
> original duration?

we have exactly what you need:

http://lsr.dsi.unimi.it/LSR/Item?id=305

Cheers,
Valentin


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

Re: Giving back: LHML template

[Johan Vromans]

Johan Vromans  writes:

> After typesetting several scores for our popchoir[1] I realized that many
> things are the same each time. So I worked out a generic template to
> be used as a starting point for new scores.
> 
> The template is loosely based on the SATB template from the docs,
> enhanced with many nifty features that I would not have been able to
> implement without the great help of several lilypond-users.
> 
> How can I thank you better than by giving back the results?
> 
> Feedback is welcome. Disclaimer: it works for me. Most of the time,
> that is. It is not intended to be a 100% replacement for everything, I
> often make changes specific to each individual score. But it's a
> useful starting point. It is pretty generic and could be enhanced to
> support SATB as well.

I've been asked to contribute this to LSR but this is not a single
snippet. Instead, it's a collection of source files. 

Suggestions how to contribute this to LSR are appreciated!

-- Johan
   http://johan.vromans.org/seasons_greetings.html

[1] http://www.xploosion.nl (dutch only)


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

Re: Minimum width for a bar

[Andrew Hawryluk]

On Thu, Jan 8, 2009 at 4:57 AM, James E. Bailey
 wrote:
>
> Am 08.01.2009 um 12:20 schrieb Nick Payne:
>
>> How can I specify that a bar containing only a single tied note be a
>> certain
>> minimum width?


> Section 1.8.1 on text may help. \override Score.PaperColumn
> #'keep-inside-line = ##t may do what you're looking to do.


You might also try \textLengthOn, same section.

Andrew


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

adding to the lsr isn't working

[chip]

I have finally go registered to add my template to the LSR and have 
added all the relevant info into the form to do so. When I click on 
either the Go button or the Save button I get a pop-up box that says -


The page at https://lsr.dsi.unumi.it says:
No output from Lilypond

I have tried several times but it just won't work.

What am I doing wrong?

--
Chip


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

Re: adding to the lsr isn't working

[Valentin Villenave]

2009/1/8 chip :
> I have finally go registered to add my template to the LSR and have added
> all the relevant info into the form to do so. When I click on either the Go
> button or the Save button I get a pop-up box that says -
>
> The page at https://lsr.dsi.unumi.it says:
> No output from Lilypond

There currently are some problems with the LSR server, as you noticed
recently. Sebastiano's on it :-)

Cheers,
Valentin


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

Re: short instrument name setting

[Cameron Horsburgh]

On Thu, Jan 08, 2009 at 02:41:38PM +0100, Valentin Villenave wrote:
> 2009/1/8 Kieren MacMillan :
> 
> > That's exactly what I said — thanks for the +1!  ;-)
> 
> +another 1 for me.
> 
> \tag sucks, \context rulz.

Yeah... \context is okay, I guess, but surely my way of doing
this---using \set short.InstrumentName in the appropriate \staff block
is the more idiomatic way to go. That way the definition is
*completely* removed from the content. It just seems more LilyPondish.

-- 

Cameron Horsburgh

Blog: http://spiritcry.wordpress.com/


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

Re: short instrument name setting

[Kieren MacMillan]

Hi Cameron,


Yeah... \context is okay, I guess, but surely my way of doing
this---using \set short.InstrumentName in the appropriate \staff block
is the more idiomatic way to go. That way the definition is
*completely* removed from the content. It just seems more LilyPondish.


Agreed!
I always try to set instrument name(s) in the \score block (or a  
subcontext) instead of the content — I probably should have started  
by suggesting that to Chip.


The only place where this approach doesn't work well is with  
instrument switches, which are still unnecessarily complex and error- 
prone in Lilypond.


Cheers,
Kieren.

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

The Drummer's Gigsaw: Hip-Hop + Rap + others...

[Philippe Hezaine]

Hi all,

Some Hip-Hop, Rap and derived patterns from a contributor here:

http://philippe.hezaine.free.fr/spip.php?article31

In this release i changed the midi.scm by default.
I wanted to try a new set of dynamics for the percussions.
You'll find the results in the folder: midi+newveloc.
I also included the new midi.scm

Cheers.
--
  Phil.
Superbonus-Project (Site principal) 

Superbonus-Project (Plate-forme d'échange):




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

Re: short instrument name setting

[chip]

Kieren MacMillan wrote:

Hi Cameron,


Yeah... \context is okay, I guess, but surely my way of doing
this---using \set short.InstrumentName in the appropriate \staff block
is the more idiomatic way to go. That way the definition is
*completely* removed from the content. It just seems more LilyPondish.


Agreed!
I always try to set instrument name(s) in the \score block (or a 
subcontext) instead of the content — I probably should have started by 
suggesting that to Chip.


The only place where this approach doesn't work well is with 
instrument switches, which are still unnecessarily complex and 
error-prone in Lilypond.


Cheers,
Kieren.
I've been reading all the messages in this thread and haven't quite 
understood all of it, but I believe you are referring to the content 
section as the section where all the notes are. That being the wrong 
place to put
\set short.instrumentname. I finally settled on putting the instrument 
names in this section of my score, which is how I have it now, using the 
header item 'piece'. This works well and looks good on the printed sheet.


\book { \score { << \new Staff = "trumpeta" \with { \remove 
Instrument_name_engraver } \trumpeta >> \header {piece="Trumpet 1"} 
\layout { indent = 0\mm} } }


Whether or not this is the 'correct' way I don't know, but it does the job.
Regards,
Chip



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

Re: adding to the lsr isn't working

[Valentin Villenave]

2009/1/8 chip :
> The page at https://lsr.dsi.unumi.it says:
> No output from Lilypond

Can you post your snippet here?

Cheers,
Valentin


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

Re: short instrument name setting

[James E. Bailey]

Am 08.01.2009 um 23:15 schrieb chip:
I've been reading all the messages in this thread and haven't quite  
understood all of it, but I believe you are referring to the  
content section as the section where all the notes are. That being  
the wrong place to put
\set short.instrumentname. I finally settled on putting the  
instrument names in this section of my score, which is how I have  
it now, using the header item 'piece'. This works well and looks  
good on the printed sheet.


That's exactly it. The idea is that there are two aspects to data  
entry in lilypond, what is displayed and how it is displayed. The  
musical notes being the what (content) and what is actually put on  
the page being the how (presentation). If you think about it, if you  
have your music in a variable, you've already started separating things.


I think of it kinda like database normalization. Keep everything  
separate and reference it where you need to.


So, the \set Staff.instrumentName and \set Staff.shortInstrumentName,  
not being actual notes, and only being necessary for presentation,  
should be kept outside of any definition of notes that occur with the  
instrument. You could define a context for instrument names, which is  
probably way more work than is necessary for most situations, or, do  
as you said, and modify your Staff definition to have the appropriate  
instrumentName and shortInstrumentName and everything else. The goal  
is to be able to easily generate score and parts in whatever format  
that may be desired as easily as possible.



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

Re: lsr having problems?

[Valentin Villenave]

2009/1/8 James E. Bailey :
> I don't know if this is a new problem or not, but I've never been able to
> successfully register on lsr.

Have you tried going on http://lsr.dsi.unimi.it/list.php?type=usr and
clicking on "New"?

Cheers,
Valentin


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

Re: lsr having problems?

[Valentin Villenave]

2009/1/9 Valentin Villenave :

> Have you tried going on http://lsr.dsi.unimi.it/list.php?type=usr and
> clicking on "New"?

Sorry, the correct link is https://lsr.dsi.unimi.it/list.php?type=usr

Cheers,
Valentin


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

Re: adding to the lsr isn't working

[chip]

Valentin Villenave wrote:

2009/1/8 chip :
  

The page at https://lsr.dsi.unumi.it says:
No output from Lilypond



Can you post your snippet here?

Cheers,
Valentin


  

Absolutely. Here it is -
~~~

% LilyPond
%{
This is a template that works well for a horn section for a band. It has 
a score which includes trumpets 1,2, Alto Sax 1,2, Tenor Sax, Bari Sax, 
Trombone 1 Bass Clef and Trombone 2 Treble Clef. It prints the score and 
creates the separate horn parts files. It also has overrides for bar 
numbering, auto-beaming, zigzag glissando, multi-measure rests and 
numeric time sig. The score prints the instrument name and the 
shortinstrumentnames on each successive page. On the individual parts 
the instrument name is above the top staff on the left in the 'piece' 
header position. And the first staff indentation in the individual 
printed parts is set to zero.


Tweaking the template to suit your own band is quite easy. The variable 
names can be changed to adjust the template to any horns. Then just 
change the same names in the \book \score section at the bottom of the 
template. Adjust the key signature, tempo and time signature, and the 
\transpose syntax, and you're good to go. For my own use I remove all 
the \transpose syntaxes so I can view the complete score in concert key. 
then after I see that all the parts are correct I add the \transpose 
syntax before printing the parts.

%}

%\include "english.ly"
%\version "2.12.1"
\header{
   title = "Title"
   composer = "Composer-RecordingArtistName"
   arranger = "Arranger-TranscriberName"
}
% Just change the \time, \key \tempo to meet your needs
global = { \time 4/4  \key c \major \tempo 4=107
 #(override-auto-beam-setting '(end 1 8 * *) 1 4 'Staff)
 #(override-auto-beam-setting '(end 1 8 * *) 2 4 'Staff)
 #(override-auto-beam-setting '(end 1 8 * *) 3 4 'Staff)
 \override Score.BarNumber #'break-visibility = #'#(#t #t #t)
 \override Score.BarNumber #'break-visibility = #end-of-line-invisible
 \override Score.BarNumber #'self-alignment-X = #-1
 \override Glissando #'thickness = #3
 \override Glissando #'style = #'zigzag
 \override Glissando #'minimum-length = #6
 \override Glissando #'springs-and-rods = #ly:spanner::set-spacing-rods
 \override MultiMeasureRest #'expand-limit = 1
 \set Score.skipBars = ##t
 \numericTimeSignature
}
\paper {
top-margin = 0.1\cm
page-top-space = 0.1\cm
ragged-bottom = ##t
left-margin = 20\mm
line-width = 175\mm
}

% -- Trumpet 1--
trpta = {
% Notes here -
a b c d
}
% Change the \transpose keys to meet your needs
trumpeta = \transpose c d \relative c'' {
 \global
 \set Staff.instrumentName = #"Trumpet 1"
 \set Staff.shortInstrumentName = #"Trpt 1"
 \clef treble
 << \trpta >>
 }

% -- Trumpet 2--
trptb = {
% Notes here -
a b c d
}
% Change the \transpose keys to meet your needs
trumpetb = \transpose c d \relative c'' {
 \global
 \set Staff.instrumentName = #"Trumpet 2"
 \set Staff.shortInstrumentName = #"Trpt 2"
 \clef treble
 << \trptb >>
}

% -- Alto Sax 1 --
altoa = {
% Notes here -
a b c d
}
% Change the \transpose keys to meet your needs
altosaxa = \transpose c a \relative c'' {
 \global
 \set Staff.instrumentName = #"Alto Sax 1"
 \set Staff.shortInstrumentName = #"Alto 1"
 \clef treble
 << \altoa >>
}

% -- Alto Sax 2 -
altob = {
% Notes here -
a b c d
}
% Change the \transpose keys to meet your needs
altosaxb = \transpose c a \relative c'' {
 \global
 \set Staff.instrumentName = #"Alto Sax 2"
 \set Staff.shortInstrumentName = #"Alto 2"
 \clef treble
 << \altob >>
}

% -- Tenor--
tenor = {
% Notes here -
a b c d
}
% Change the \transpose keys to meet your needs
tenorsax = \transpose c d \relative c'' {
 \global
 \set Staff.instrumentName = #"Tenor Sax"
 \set Staff.shortInstrumentName = #"Tnr Sax"
 \clef treble
 << \tenor >>
}

% -- Bari--
bari = {
% Notes here -
a b c d
}
% Change the \transpose keys to meet your needs
barisax =  \transpose c a \relative c''{
 \global
 \set Staff.instrumentName = #"Bari Sax"
 \set Staff.shortInstrumentName = #"Btn Sax"
 \clef treble
 << \bari >>
}

% -- Trombone Bass Clef--
tbonea = {
% Notes here -
a b c d
}
% Change the \transpose keys to meet your needs
trombonea = \relative c {
 \global
 \set Staff.instrumentName = #"Trombone 1"
 \set Staff.shortInstrumentName = #"Tbn 1"
 \clef bass
 << \tbonea >>
}

% -- Trombone Treble Clef--
tboneb= {
% Notes here -
a b c d
}
% Change the \transpose keys to meet your needs
tromboneb = \transpose c d \relative c' {
 \global
 \set Staff.instrumentName = #"Trombone 2"
 \set Staff.shortInstrumentName = #"Tbn Bb"
 \clef treble
 << \tboneb >>
}

\book { \score {
 <<
   \new StaffGroup = "trumpets" <<
\new Staff = "trpta" \trumpeta
\new Staff = "trptb" \trumpetb >>
   \new StaffGroup = "saxes" <<
\new Staff = "altoa" \altosaxa
\new Staff = "altob" \altosaxb
\new S

Re: lsr having problems?

[chip]

Valentin Villenave wrote:

2009/1/9 Valentin Villenave :

  

Have you tried going on http://lsr.dsi.unimi.it/list.php?type=usr and
clicking on "New"?



Sorry, the correct link is https://lsr.dsi.unimi.it/list.php?type=usr

Cheers,
Valentin
  
When I go there, highlight my name in the Users window, and click on New 
Element I get the Account Data page.
I have this page - https://lsr.dsi.unimi.it/update.php - open and all 
the info input, click on Ok or Save, the page appears to  load fine but 
finally that error box pops up.

--
Chip



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