Re: Cropped output (à la -dpreview) possiblein Finale and Sibelius

[Francisco Vila]

2013/4/9 Phil Holmes :
> I commented in an earlier message that Sibelius, IMHO, produces witheringly
> appalling graphics output.  Unaliased, with stems that attach to noteheads
> poorly.  The image I attached earlier was not scanned, but used Sibelius's
> export to PNG function at nominal 300 dpi.  This is its attempt at 1200 dpi.

It must have been downsampled at some stage. I see stairs at 100% (1:1
to screen)
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

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

Re: Cropped output (à la -dpreview) possiblein Finale and Sibelius

[Francisco Vila]

2013/4/10 Francisco Vila :
> It must have been downsampled at some stage. I see stairs at 100% (1:1
> to screen)

Hm, probably I should see stairs in either case because pixels of my
screen are bigger than cone cells of my retina, so to speak, but now I
think I see them because the image is pure b/w, i.e. not antialiased.

For inserting lilypond images in slides and the such, I find it enough
to render at 300 or 600 dpi, or around 1000px tall, antialiased, so
that the PDF viewer downsamples it for the output device, and I must
say I am very satisfied.

I used to recommend to always "render at your printer resolution,
insert at 100% size", now I'm not so sure.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

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

RE: musicxml2ly enhancements

[Curt McDowell]

How about allowing bar numbers as a letter+number, parsed similar to musical 
note+duration:
B78 a,4 ( a4 ) ( b4 ) d4 |
B79 e,4 ( f4 ) ( g4 ) a4 |
Perhaps they could also double as bar checks:
B78 a,4 ( a4 ) ( b4 ) d4
B79 e,4 ( f4 ) ( g4 ) a4
Or alternately, augment the existing bar check to allow an optional value:
a,4 ( a4 ) ( b4 ) d4 |78
e,4 ( f4 ) ( g4 ) a4 |79
Or (to taste):
|78  a,4 ( a4 ) ( b4 ) d4
|79  e,4 ( f4 ) ( g4 ) a4
The actual bar numbers might be ignored initially, but eventually 
- they might be the numbers printed
- bar checks might also verify that bar numbers match across staves, voices, 
\alternatives.

Having already entered some large pieces, I only recently discovered 
Frescobaldi. What a wonderful program. The point-and-click cursor matching 
between source and PDF nearly obviates the need for measure numbers. I wish I'd 
found it sooner!

Cheers,
-Curt

-Original Message-
From: lilypond-user-bounces+lilypond=fishlet@gnu.org 
[mailto:lilypond-user-bounces+lilypond=fishlet@gnu.org] On Behalf Of Urs 
Liska
Sent: Tuesday, April 09, 2013 4:26 AM
To: lilypond-user@gnu.org
Subject: Re: musicxml2ly enhancements

Am 09.04.2013 13:19, schrieb Janek Warchoł:
> 2013/4/9 Werner LEMBERG :
>>> Putting the bar number at the start of the line would require
>>>
>>>%{ 5 %} a,4 ( a4 ) ( b4 ) d4 |
>>>
>>> instead.
>> I like that.  It's tedious to type manually, but a computer program 
>> doesn't know that word :-)
> Indeed, but i find it unreadable, especially if it was placed at every line.
> I think that the best way to mark bar numbers in source is to make a 
> separate-line comment every 5 or so measures:
>
>>  \clef "treble" \key c \major \numericTimeSignature \time 4/4
>>  a4 ( a4) ( b4 ) d4 |
>>  \key c \major a4 ( a4 ) ( b4 ) d4 |
>>  a4 ( a4 ) ( b4 ) d4 |
>>  g1 |
>>  % m.5
>>  a,4 ( a4 ) ( b4 ) d4 |
>>  g1 |
>>  a,4 ( a4 ) ( b4 ) d4 |
>>  g1 |
>>  a,4 ( a4 ) ( b4 ) d4 |
>>  % m.10
>>  g1 |
>>  a,4 ( a4 ) ( b4 ) d4 |
> etc.
> Janek
I have come to the conclusion that it is a _very_ good idea to make a measure 
number for _every_ measure.
That way you have a measure indicator in each Git diff.
Which proves useful to map the change to the location in the file if the line 
numbers have changed considerably in the meantime.

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


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


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

RE: musicxml2ly enhancements

[Martin Tarenskeen]

   %{ 5 %} a,4 ( a4 ) ( b4 ) d4 |

instead.
I like that.  It's tedious to type manually, but a computer program 
doesn't know that word :-)

Indeed, but i find it unreadable, especially if it was placed at every line.


In general I think tools like musicxml2ly and other programs that convert 
to or export .ly files (xxx2ly, mscore, denemo, rosegarden) should do 
their best to make the lilypond output look like it was handwritten by a 
"real" human lilypond user and likewise should be easily readable and 
editable by a real human. With proper formatting, indentation, and coding 
style.


I don't like the way it going for example in today's world of webdesign: 
There are advanced tools to create professional websites "without knowing 
anything about HTML and CSS". But if you want to edit the html code these 
tools produce by hand it can be a real nightmare.


Just like my lilypond scores I often still write (simple) html code using 
just Vim. Maybe I'm just getting old and old fashioned :-)


--

MT


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

Re: musicxml2ly enhancements

[Werner LEMBERG]

>%{ 5 %} a,4 ( a4 ) ( b4 ) d4 |

 I like that.  It's tedious to type manually, but a computer
 program doesn't know that word :-)
>>>
>>> Indeed, but i find it unreadable, especially if it was placed at
>>> every line.

Really?  It's like having a BASIC program which always starts with a
line number:

  %{  1 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{  2 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{  3 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{  4 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{  5 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{  6 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{  7 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{  8 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{  9 %}  a,4 ( a4 ) ( b4 ) d4 |
  %{ 10 %}  a,4 ( a4 ) ( b4 ) d4 |

As mentioned earlier, I don't like to type this, but having such a
format returned by musicxml2ly is good IMHO.  After some time you get
used to it, and line numbers are only looked at if you really need
them.

> In general I think tools like musicxml2ly and other programs that
> convert to or export .ly files (xxx2ly, mscore, denemo, rosegarden)
> should do their best to make the lilypond output look like it was
> handwritten by a "real" human lilypond user and likewise should be
> easily readable and editable by a real human.  With proper
> formatting, indentation, and coding style.

I fully agree.


Werner

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

Re: call for italian users: translation of "feathered beams" and other terms

[Davide Liessi]

Ciao Federico,

as in my previous email,
>> Unreferenced statements are my personal opinions.

>> Sources:
>> [G] = "Enciclopedia della Musica", Garzanti, Milano, 1996
[C] = Sandro Carnelos, "Gli organi della diocesi di Vittorio Veneto",
Vittorio Veneto, 2000 (a book that lists characteristics of each of
the church organs in the diocese of Vittorio Veneto, in North-Eastern
Italy)


> Common Practice Period
> well, this one has been translated before:
> http://lilypond.org/doc/v2.17/Documentation/notation/writing-pitches#note-names-in-other-languages
>
> as "Periodo di pratica comune"
> does it refer to the western classic music?
>
> better ideas?
I think "periodo di pratica comune" is a suitable translation, but
I've never seen this expression in Italian texts.

> direct
I can't understand this glossary entry, since there isn't enough context.
I don't think it is specifically a musical term, and I couldn't find
occurrences of "direct" in NR with a different meaning from the usual,
literal, common one.
Why is "direct" in the glossary? Why is it related to "custos"?

> doit
> fall
Don't know an Italian term for these; maybe you could translate them
like they did in German: "glissando indeterminato verso l'alto/il
basso" or "... verso l'acuto/il grave".

> flageolet
I would translate it as in Spanish: "armonico".
Bowed strings players call harmonic sounds "suoni flautati" (listed
also in [G]), which is etymologically related to "flageolet", so maybe
you could list both expressions: "armonico, flautato".
Regarding the other meanings (flute, organ stop), [G] leaves the
French term "flageolet" untranslated, but says that the flageolet
flute was sometimes called "flautino" or "flauto piccolo".
It seems that both it could be translated as "flagioletto" (see
http://web.archive.org/web/20090213033806/http://www.musica-antica.info/strumenti/strumenti_paragrafi/4_4.html)
and [C] lists at least four organs with a "Flagioletto" stop (all by
the same organ constructor, Giovan Battista De Lorenzi, around 1850).

> frenched score
> frenched staff
I don't know and can't find an Italian term for these.
Maybe you could translate them like they did in German: "partitura
senza i righi vuoti" and "rigo temporaneo".

> hymn meter
Maybe "metrica dell'inno" or "struttura metrica dell'inno"?

> ligature
[G] lists the untranslated Latin term "ligatura" (plural "ligaturae").
I would leave it untranslated, as it is usual with many other Latin
terms regarding ancient music.

> mensuration sign
I don't know if there is a specific Italian term for mensuration
signs: [G] talks about tempus, prolatio and the signs used to notate
them, but does not give a specific name for these signs (e.g. "tempus
imperfectum cum prolatione imperfecta, indicato dal segno C").
I think that "indicazione mensurale" or "segno mensurale" should be
understandable, and the description in the glossary is perfectly
clear.

> neighbor tones
If these are what http://en.wikipedia.org/wiki/Nonchord_tone calls
"neighbor tone" (both accented and unaccented), then it is called
"nota di volta" ([G]).
It does not translate to "toni vicini": "tono vicino/lontano" or
"tonalità vicina/lontana" means "closely/distantly related key" or
"close/distant key" (see
http://en.wikipedia.org/wiki/Closely_related_key).

Best regards.
Davide

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

Frescobaldi/LilyPond timelapse video

[Francisco Vila]

Hello,

I wanted to share this screencast with you. Duration: 1'29'' at 25x speed.

http://lilypond.es/lilypond/timelapse-screencast/timelapse-aquaplane.webm
also available as
http://lilypond.es/lilypond/timelapse-screencast/timelapse-aquaplane.mp4

It shows trial and error, browsing manuals, pauses for lunch and more.

The webm version plays directly on Firefox when drag&drop from file
manager in my system.

It is a full-screen capture at 1024x600. I used the following console
commands in an Acer Aspire One under Debian Wheezy:

#mkdir png

# save X11 screen @1fps to Ogg Theora; stop with Ctrl+C
avconv -f x11grab -r 1 -s 1024x600 -i :0.0 out.ogv

# convert to png images
ffmpeg -i out.ogv -r 1 -f image2 png/frame%05d.png

# Optionally at this point, delete unwanted png's and rename all numerically.

# convert images to video @25fps
ffmpeg -r 25 -i png/frame%05d.png -r 25 timelapse.mp4

# same for webm VP8
ffmpeg -r 25 -i png/frame%05d.png -vcodec libvpx -r 25 -b1k timelapse.webm

There is much room for improving, so suggestions are appreciated. Thanks

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

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

RE: Vocal music sheet - hyphens wrongly engraved

[Jun Wang]

Hi Phil
I tried nwc2ly, the converted lilypond file version is 2.15.26.  and It gave 
some syntax error under my  2.16.2 system.Any way to convert 2.15.26 to my 
current version or I have install a old version?
ThanksJun
From: m...@philholmes.net
To: wj1...@hotmail.com; lilypond-user@gnu.org
Subject: Re: Vocal music sheet -  hyphens  wrongly engraved
Date: Sat, 6 Apr 2013 18:01:58 +0100








Try converting direct from Noteworthy to 
Lilypond:
 
http://www.holmessoft.co.uk/homepage/Software/NWC2LY/ (advert).

--
Phil Holmes
 
 

  - Original Message - 
  From: 
  Jun Wang 
  
  To: lilypond-user@gnu.org 
  Sent: Saturday, April 06, 2013 2:45 
  PM
  Subject: Vocal music sheet - hyphens 
  wrongly engraved
  

  
  Hi 
  

  I am new to lilypond, I am helping my church to 
  generate music 
  sheet in pdf 
  in order for them to practice in choir.
  

  The original score is in nwc format, so I used 
  nwc2xml to convert it into musicxml,  then I  tried to load the 
  musicxml file into musescore and print the pdf. The pdf generated from 
  musescore is  ok, but It has limited control on the layout.  So I 
  turn to lilypond.  I used muxiscml2ly (version 2.16.2) to convert to 
  lilypond file. It works great, the quality of the final pdf definitely better 
  than the pdf generated from musescore.  but I found couple engraving 
  issue, I want to see if you can help. I attached musicxml file, lilypond file 
  and pdf file for your reference.
  

  First,  I found hyphens are engraved for 3 times. see the 3 hythons between 
  "He’ll" and "forgive" and also lyrics 
  of measure 11 and measure 12.  this seems to 
  be my major issue so far.
  

  Second, This could be muxiscml2ly 
  convertion issue, see "Duet Gently" and "Quartet" are printed for 3 
  times. I checked  the generated lilypond file, looks like extra voices 
  are added. I was able to fix this by remove following lines from lilypond 
  file.
  

  
  
  \context Voice = "PartPOneVoiceOne" { \voiceOne 
  \PartPOneVoiceOne }
  
  \new Lyrics \lyricsto "PartPOneVoiceOne" 
  \PartPOneVoiceOneLyricsOne
  
  \new Lyrics \lyricsto "PartPOneVoiceOne" 
  \PartPOneVoiceOneLyricsTwo
  
  \new Lyrics \lyricsto "PartPOneVoiceOne" 
  \PartPOneVoiceOneLyricsThree
  

  
  \context Voice = "PartPOneVoiceTwo" { \voiceThree 
  \PartPOneVoiceTwo }
  
  \context Voice = "PartPTwoVoiceTwo" { \voiceThree 
  \PartPTwoVoiceTwo }
  

  Thanks
  Jun 
  
  

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

Though Your Sins Be as Scarlet.nwctxt
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Macro not working with 2.16

[Alberto Simões]

Hello

Some time ago (years probably) somebody in this list helped me with this 
macro, for \inline that work anywhere in the music:



partialInline = #(define-music-function
 (parser location nom den mus)
 (integer? integer? ly:music?)
  #{
\set Score.measurePosition = #(ly:make-moment (- $nom) $den)
$mus
   #}
)


That worked like
   \partialInline #1 #8 { a8 }

Now I get some complains with 2.16:

../utils.ly:9:34: error: GUILE signaled an error for the expression 
beginning here

\set Score.measurePosition = #
  (ly:make-moment (- $nom) $den)
Unbound variable: $nom
melody.ly:31:32: error: error in #{ ... #}
\partialInline #1 #8 { a8 }
|
Interpreting music...
warning: type check for `measurePosition' failed; value `#' 
must be of type `moment'


Any help?
Thank you
Alberto

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

Re: Macro not working with 2.16

[Jan-Peter Voigt]

Hello Alberto,

the change was introduced in 2.13 or 2.15(?).
If you remove the dollar signs inside the scheme expression ($nom -> 
nom) (but not inside the lily code $mus), it should work:


#{
\set Score.measurePosition = #(ly:make-moment (- nom) den)
$mus
#}

HTH
Jan-Peter

Am 10.04.2013 14:50, schrieb Alberto Simões:

Hello

Some time ago (years probably) somebody in this list helped me with 
this macro, for \inline that work anywhere in the music:



partialInline = #(define-music-function
 (parser location nom den mus)
 (integer? integer? ly:music?)
  #{
\set Score.measurePosition = #(ly:make-moment (- $nom) $den)
$mus
   #}
)


That worked like
   \partialInline #1 #8 { a8 }

Now I get some complains with 2.16:

../utils.ly:9:34: error: GUILE signaled an error for the expression 
beginning here

\set Score.measurePosition = #
  (ly:make-moment (- $nom) $den)
Unbound variable: $nom
melody.ly:31:32: error: error in #{ ... #}
\partialInline #1 #8 { a8 }
|
Interpreting music...
warning: type check for `measurePosition' failed; value 
`#' must be of type `moment'


Any help?
Thank you
Alberto

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




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

Re: Macro not working with 2.16

[Alberto Simões]

Hello, Jan-Peter

On 10/04/13 14:01, Jan-Peter Voigt wrote:

Hello Alberto,

the change was introduced in 2.13 or 2.15(?).
If you remove the dollar signs inside the scheme expression ($nom ->
nom) (but not inside the lily code $mus), it should work:

#{
\set Score.measurePosition = #(ly:make-moment (- nom) den)
$mus
#}


Perfect. Thank you! :-)
Alberto



Am 10.04.2013 14:50, schrieb Alberto Simões:

Hello

Some time ago (years probably) somebody in this list helped me with
this macro, for \inline that work anywhere in the music:


partialInline = #(define-music-function
 (parser location nom den mus)
 (integer? integer? ly:music?)
  #{
\set Score.measurePosition = #(ly:make-moment (- $nom) $den)
$mus
   #}
)


That worked like
   \partialInline #1 #8 { a8 }

Now I get some complains with 2.16:

../utils.ly:9:34: error: GUILE signaled an error for the expression
beginning here
\set Score.measurePosition = #
  (ly:make-moment (- $nom) $den)
Unbound variable: $nom
melody.ly:31:32: error: error in #{ ... #}
\partialInline #1 #8 { a8 }
|
Interpreting music...
warning: type check for `measurePosition' failed; value
`#' must be of type `moment'

Any help?
Thank you
Alberto

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




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


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

Re: Cropped output (à la -dpreview) possible in Finale and Sibelius

[Carl Peterson]

On Tue, Apr 9, 2013 at 4:45 PM, David Kastrup  wrote:

> Carl Peterson  writes:
>
> > I'm not an expert on GhostScript, but in practice it is nearly always
> > best to rasterize vector graphics at the intended output resolution.
>
> Except when it isn't.  What makes you think that the PDF viewers are
> doing anything but rasterizing vector graphics at the intended output
> resolution?
>

Even though a PDF viewer is rasterizing at the output resolution, it isn't
rasterizing at the intended resolution of the PDF file. The basic Lilypond
output is intended for output at print resolution (say, 300dpi or higher).
We know this is a factor because Lilypond already uses multiple versions of
the engraving fonts so that smaller and larger scores are equally
"beautiful music."

PDF viewers cannot discern rendering intent. When a generic PDF viewer
looks at Lilypond output, it doesn't know that the stems need to be treated
as lines and not rounded rectangles below a certain resolution, or that it
needs to render all the staff lines even if one of the staff lines
"disappears" at that resolution. Lilypond knows what a stem is and what a
staff line is and if it's producing its own PNG output, it can make sure
those elements get rendered properly for the intended resolution.

Vectors can be scaled up with out limit and preserve image quality, but in
a raster environment (like a computer screen), they cannot be scaled down
without limit with the same expectation.

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

Re: Macro not working with 2.16

[David Kastrup]

Alberto Simões  writes:

> Hello
>
> Some time ago (years probably) somebody in this list helped me with
> this macro, for \inline that work anywhere in the music:
>
> Now I get some complains with 2.16:

If you had upgraded your files/macro using convert-ly, everything should
have worked fine.  convert-ly is _always_ the first thing to try
whenever something stops working in a newer version.

-- 
David Kastrup


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

Re: Cropped output (à la -dpreview) possible in Finale and Sibelius

[David Kastrup]

Carl Peterson  writes:

> On Tue, Apr 9, 2013 at 4:45 PM, David Kastrup  wrote:
>
> Carl Peterson  writes:
> 
> > I'm not an expert on GhostScript, but in practice it is nearly
> always
> > best to rasterize vector graphics at the intended output
> resolution.
> 
> 
> Except when it isn't. What makes you think that the PDF viewers
> are
> doing anything but rasterizing vector graphics at the intended
> output
> resolution?
>
> Even though a PDF viewer is rasterizing at the output resolution, it
> isn't rasterizing at the intended resolution of the PDF file. The
> basic Lilypond output is intended for output at print resolution (say,
> 300dpi or higher). We know this is a factor because Lilypond already
> uses multiple versions of the engraving fonts so that smaller and
> larger scores are equally "beautiful music."

You are confusing "scale" and "resolution".

> Lilypond knows what a stem is and what a staff line is and if it's
> producing its own PNG output, it can make sure those elements get
> rendered properly for the intended resolution.

It might make some sense getting acquainted with the involved mechanisms
before lecturing developers.  LilyPond does not differentiate _at_ _all_
between producing PNG and producing PDF.  In either case, it produces
_identical_ PostScript and lets Ghostscript convert it into _either_ PNG
_or_ PDF.  Ghostscript does a pretty good job at producing viewable PNG,
and the PDF preserves the original imprinting information in the
PostScript file, so we actually know that PDF viewers _could_ do a
reasonable job displaying LilyPond PDFs just fine.

They don't, so it turns out that the rendering decisions of typical PDF
viewers differ from that of Ghostscript when producing PNG.  The
question is how we can change the PostScript/PDF in a manner that works
better with typical PDF viewers.

Now the main problem is that typical PDF viewers don't bother much about
graphics but are centered around font display.  So one possibility would
be to create ad-hoc fonts (including hinting) representing the graphical
elements, like rounded rectangles etc, and use those instead of
graphical elements.

That's mind-numbingly stupid and complex, but it might be feasible.
Another possibility would be to do thorough experimentation running
through several previewers and implementations of graphic primitives and
take a look just what combinations work out well, and what not.

Yet another possibility is to see whether there are suitable options for
Ghostscript's PS->PDF conversion in order to produce nicer working
constructs in the PDF.  Again, that's stupid, but at least the
complexity would not be ours: we would only have to check whether
somebody already did the work for us.  But with regard to resolution
dependency, one has to take a choice between things rendering with
reasonable thickness and things lining up well.  One such parameter
expressing such a choice is "strokeadjust".

> Vectors can be scaled up with out limit and preserve image quality,
> but in a raster environment (like a computer screen), they cannot be
> scaled down without limit with the same expectation.

I might have heard about rasterization.

If you are interested in being helpful, it might make sense to stop
lecturing ex cathedra and get dirty with the actual code and
implementation.

-- 
David Kastrup

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

Re: Vocal music sheet - hyphens wrongly engraved

[Janek Warchoł]

2013/4/10 Jun Wang :
> Hi Phil
>
> I tried nwc2ly, the converted lilypond file version is 2.15.26.  and It gave
> some syntax error under my  2.16.2 system.
> Any way to convert 2.15.26 to my current version or I have install a old
> version?

sure, just use convert-ly:
http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly

hth,
Janek

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

Re: Cropped output (à la -dpreview) possiblein Finale and Sibelius

[Phil Holmes]

- Original Message - 
From: "Francisco Vila" 

To: "Phil Holmes" 
Cc: "LilyPond-User list" ; "David Kastrup" 


Sent: Wednesday, April 10, 2013 8:20 AM
Subject: Re: Cropped output (à la -dpreview) possiblein Finale and Sibelius



2013/4/9 Phil Holmes :
I commented in an earlier message that Sibelius, IMHO, produces 
witheringly
appalling graphics output.  Unaliased, with stems that attach to 
noteheads
poorly.  The image I attached earlier was not scanned, but used 
Sibelius's
export to PNG function at nominal 300 dpi.  This is its attempt at 1200 
dpi.


It must have been downsampled at some stage. I see stairs at 100% (1:1
to screen)
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com



It was exactly as produced by Sibelius.

--
Phil Holmes 



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

Re: Macro not working with 2.16

[SoundsFromSound]

Hi Alberto,

What does your macro do exactly?  Just curious, thanks!

Looks nice!


Alberto Simões-2 wrote
> Hello
> 
> Some time ago (years probably) somebody in this list helped me with this 
> macro, for \inline that work anywhere in the music:
> 
> 
> partialInline = #(define-music-function
>   (parser location nom den mus)
>   (integer? integer? ly:music?)
>#{
>  \set Score.measurePosition = #(ly:make-moment (- $nom) $den)
>  $mus
> #}
> )
> 
> 
> That worked like
> \partialInline #1 #8 { a8 }
> 
> Now I get some complains with 2.16:
> 
> ../utils.ly:9:34: error: GUILE signaled an error for the expression 
> beginning here
>  \set Score.measurePosition = #
>(ly:make-moment (- $nom) $den)
> Unbound variable: $nom
> melody.ly:31:32: error: error in #{ ... #}
>  \partialInline #1 #8 { a8 }
>  |
> Interpreting music...
> warning: type check for `measurePosition' failed; value `#
> 
> ' 
> must be of type `moment'
> 
> Any help?
> Thank you
> Alberto
> 
> ___
> 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/Macro-not-working-with-2-16-tp144278p144292.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: Macro not working with 2.16

[Thomas Morley]

2013/4/10 SoundsFromSound :
> Hi Alberto,
>
> What does your macro do exactly?  Just curious, thanks!

It's a substitution-function
(see: 
http://lilypond.org/doc/v2.16/Documentation/extending/intermediate-substitution-functions
)
for `measurePosition'
(see Nr 1.2.6: 
http://lilypond.org/doc/v2.17/Documentation/notation/special-rhythmic-concerns
)

-Harm

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

Re: Frescobaldi/LilyPond timelapse video

[Federico Bruni]

2013/4/10 Francisco Vila 

> I wanted to share this screencast with you. Duration: 1'29'' at 25x speed.
>
> http://lilypond.es/lilypond/timelapse-screencast/timelapse-aquaplane.webm
> also available as
> http://lilypond.es/lilypond/timelapse-screencast/timelapse-aquaplane.mp4
>
> It shows trial and error, browsing manuals, pauses for lunch and more.
>

Hi Francisco

nice idea
maybe too fast to be understandable
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi/LilyPond timelapse video

[Urs Liska]

Am 10.04.2013 22:18, schrieb Federico Bruni:


2013/4/10 Francisco Vila >


I wanted to share this screencast with you. Duration: 1'29'' at
25x speed.

http://lilypond.es/lilypond/timelapse-screencast/timelapse-aquaplane.webm
also available as
http://lilypond.es/lilypond/timelapse-screencast/timelapse-aquaplane.mp4

It shows trial and error, browsing manuals, pauses for lunch and more.


Hi Francisco

nice idea
maybe too fast to be understandable
That's what I'd say too. I'd suggest about half the speed. Anybody who 
will look at this at all will be patient enough to watch twice the time. 
And even if he can't really follow he will get an impression when it's 
not like a slapstick movie.


Urs




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


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

Re: Frescobaldi/LilyPond timelapse video

[Denis Bitouzé]

Le mercredi 10/04/13 à 22h18,
Federico Bruni  a écrit :

> maybe too fast to be understandable

I guess one is supposed to be replay at a lower speed if he's
interested in some point.
-- 
Denis

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

Re: call for italian users: translation of "feathered beams" and other terms

[Federico Bruni]

2013/4/10 Davide Liessi 

> > direct
> I can't understand this glossary entry, since there isn't enough context.
> I don't think it is specifically a musical term, and I couldn't find
> occurrences of "direct" in NR with a different meaning from the usual,
> literal, common one.
> Why is "direct" in the glossary? Why is it related to "custos"?
>
>
no idea, I'll leave it untranslated


> > doit
> > fall
> Don't know an Italian term for these; maybe you could translate them
> like they did in German: "glissando indeterminato verso l'alto/il
> basso" or "... verso l'acuto/il grave".
>
>
I think that it refers to "bending".
We don't have a term in italian. Maybe:
"piegatura della nota verso l'alto/basso (bending)"
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: musicxml2ly enhancements

[Wim van Dommelen]

On 10 Apr 2013, at 11:38 , Martin Tarenskeen wrote:

Just like my lilypond scores I often still write (simple) html code  
using just Vim. Maybe I'm just getting old and old fashioned :-)


+1, we're not alone..


Regards,
Wim.

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

Frescobaldi/LilyPond timelapse video

[Timothy Reeves]

Nice! I tended to pay attention to the changes in the output which kept me
from seeing what was happening on the input side...I guess I could watch
again with different focus but it might be hard... I agree slower would be
better.
Nice wallpaper, btw!

-- 
Tim Reeves
timothyrree...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user