I'm trying to engrave a set of tunes. It uses the Piano format with
centred dynamics, so I used the template in the Learning manual,
editing out the stuff used in the manual. However, I can't change the
tempo or key. I've edited the global variable as shown, but it still
comes out in C and common
I think you have to declare two variables:
#(define-music-function (parser location trans notes) (ly:music? ly:music?)
#{
\transpose c $trans { $notes }
#})
The problem appears to be that \transpose is expecting a notename, not
a variable, so this has the same problem, and doubled.
Thank
You've omitted the \global from your score block. It should happen
simultaneously with the music, so \global \lower
Am 01.06.2009 um 09:38 schrieb Mark Austin:
I'm trying to engrave a set of tunes. It uses the Piano format with
centred dynamics, so I used the template in the Learning manual,
Josiah Boothby schrieb:
I think you have to declare two variables:
#(define-music-function (parser location trans notes) (ly:music? ly:music?)
#{
\transpose c $trans { $notes }
#})
Sorry, I forgot to answer to the list, but as my proposal doesn't
work anyway, it doesn't matter.
The
Moin Thomas,
Error codes are created by the operating system and reported by the
application. The error code may be dependent on the context.
The context that you reported looks like a CreateFile
http://msdn.microsoft.com/en-us/library/aa363858(VS.85).aspx context.
In this case it means
2009/6/1 Carl D. Sorensen c_soren...@byu.edu:
You are welcome to pursue this, if you are interested in it. It is not my
interest.
I think it shows the impossibility of what you are trying to achieve,
at least in the completely general case, although pushing the
boundaries closer to that
\transpose c $trans { \firstNotes }
string:2:17: error: syntax error, unexpected MUSIC_IDENTIFIER,
expecting NOTENAME_PITCH or TONICNAME_PITCH
The only solution i know is to use the scheme equivalent of \transpose :
ly:music-transpose
But it is a bit harder...
Joe Neeman joenee...@gmail.com writes:
[...]
p.s. Despite [As a result of?] banging my head against this
particular wall, I think I learned a little about Scheme +
Lilypond... that's some consolation! =)
If it's any additional consolation, your approach would have been
perfectly ok were
Thanks James. Works a treat now. However, this means the error is in
the template in the Learning Manual, since I copied it straight over.
The first few lines of the first \score block should be:
\score {
\new PianoStaff = PianoStaff_pf
\new Staff = Staff_pfUpper \global \upper
\new
Mark Austin wrote:
Thanks James. Works a treat now. However, this means the error is in
the template in the Learning Manual, since I copied it straight over.
The first few lines of the first \score block should be:
\score {
\new PianoStaff = PianoStaff_pf
\new Staff = Staff_pfUpper
Mats Bengtsson wrote:
Mark Austin wrote:
Thanks James. Works a treat now. However, this means the error is in
the template in the Learning Manual, since I copied it straight over.
The first few lines of the first \score block should be:
\score {
\new PianoStaff = PianoStaff_pf
\new
On Mon, Jun 01, 2009 at 06:51:59AM -0500, Jonathan Kulp wrote:
I'm having trouble getting the LSR database to come up, and when I
opened the template in my source code it said at the top not to edit
this file.
Yes; it should only be changed in LSR.
Also I still can't pull from git:
I have the following code in my ConductorScore.ly. The first one, with
the combined parts, doesn't print the instumentName: the second one,
with just one part, does. Anybody know offhand how to fix this?
Thanks. (Files are available at
http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=1643,
On Jun 1, 2009, at 4:13 AM, Tim Rowe wrote:
2009/6/1 Carl D. Sorensen c_soren...@byu.edu:
You are welcome to pursue this, if you are interested in it. It
is not my
interest.
I think it shows the impossibility of what you are trying to achieve,
at least in the completely general case,
I don't know enough about \partcombine to tell you why, but if you
use the \new Staff \with { instrumentName = Bassoon }, you should get
what you want. At least, I got it, but I curiously got two scores
with the following code:
\score {
\new Staff \with {
printPartCombineTexts =
Grammostola Rosea rosea.grammostola at gmail.com writes:
Ik kan me niet registreren... krijg geen email...
Check even je 'spam-box', bij mij verdween hij linea-recta in de spam.
AWRog
___
lilypond-user mailing list
lilypond-user@gnu.org
Hey lilypond users,
I am compiling a file w/ many notes (on the order of 5*(3^7) 32nd notes
including spaces) that, @ the interpreting music stage, counted up to
2184. I started it last night and it has been running for upwards of 9h
using version 2.13.0 on a 1.5 GHz PowerPC running OS X
\score {
\new Staff \with {
printPartCombineTexts = ##f
midiInstrument = bassoon
instrumentName = Bassoon
shortInstrumentName = Bass.
} \partcombine \bassoonOne \bassoonTwo
}
This solution seems to work great.
I think that the
I was just brainstorming, I don`t expect anybody to implement that :-)
... I just thought, if music (as long as it's not abstract) follows some
basic principles, why this is not reflected in the chord naming sometimes.
Slash Chords are a good example ... they are a good, easily readable
The only solution i know is to use the scheme equivalent of \transpose :
ly:music-transpose
But it is a bit harder...
firstNotes = \relative c' { c4 d e f }
first = #(define-music-function (parser location trans)(ly:music?)
(let* (
(trans-note (car
Thomas schrieb:
I was just brainstorming, I don`t expect anybody to implement that :-)
... I just thought, if music (as long as it's not abstract) follows some
basic principles, why this is not reflected in the chord naming sometimes.
Slash Chords are a good example ... they are a good,
Marc Hohl wrote:
Thomas schrieb:
I was just brainstorming, I don`t expect anybody to implement that :-)
... I just thought, if music (as long as it's not abstract) follows
some basic principles, why this is not reflected in the chord naming
sometimes.
Slash Chords are a good example ...
Tim McNamara wrote:
On Jun 1, 2009, at 4:13 AM, Tim Rowe wrote:
2009/6/1 Carl D. Sorensen c_soren...@byu.edu:
You are welcome to pursue this, if you are interested in it. It is
not my
interest.
I think it shows the impossibility of what you are trying to achieve,
at least in the
On 6/1/09 12:50 PM, Grammostola Rosea rosea.grammost...@gmail.com wrote:
Tim McNamara wrote:
On Jun 1, 2009, at 4:13 AM, Tim Rowe wrote:
2009/6/1 Carl D. Sorensen c_soren...@byu.edu:
You are welcome to pursue this, if you are interested in it. It is
not my
interest.
I think it
Mats Bengtsson wrote:
Mark Austin wrote:
Thanks James. Works a treat now. However, this means the error is in
the template in the Learning Manual, since I copied it straight over.
The first few lines of the first \score block should be:
\score {
\new PianoStaff = PianoStaff_pf
\new
On 6/1/09 1:38 PM, Jonathan Kulp jonlancek...@gmail.com wrote:
Mats Bengtsson wrote:
Mark Austin wrote:
Thanks James. Works a treat now. However, this means the error is in
the template in the Learning Manual, since I copied it straight over.
The first few lines of the first \score
Hi,
Just in case it can be helpful, someone (Karl) post a pdf he wrote on
MuseScore (http://www.musescore.org) mailing list about chord name display.
Musescore is a free GPL WYSIWYG scorewriter (with lilypond export
capabilities)
Maybe it can be helpful to your current and future work on chord
Is the above code something flexible
enough that it could work with the first of those
being something other than c?
(e.g., \transpose f g \notes)
Just change
(ly:make-pitch -1 0 0) (pitch c)
by
(ly:make-pitch -1 3 0) (pitch f)
( 0 = c, 1 = d, etc ...)
If you do want 2
I have added my template to the LSR but the thumbnail image that appears
is not correct. I have tried as both Standalone Snippet and as Large
Snippet. Is there something I can do to fix this so the thumbnail
appears as it should?
Regards,
chip
___
Hi,
I've put up a page on how to get more realistic sounding MIDI output
from current LilyPond, along with the scripts and scheme code used, at
http://www.nicta.com.au/people/chubbp/articulate
It has before-and-after MIDI samples to listen to, and a full
description of what the script
On Jun 1, 2009, at 2:33 PM, Carl D. Sorensen wrote:
A chordnamemode *input* mode has been proposed a couple of times.
This mode
would take only a root (and optionally, a slash or alternate bass
note), and
everything else about the chord would be in the form of a markup. For
american jazz
On 6/1/09 8:56 PM, Tim McNamara tim...@bitstream.net wrote:
On Jun 1, 2009, at 2:33 PM, Carl D. Sorensen wrote:
A chordnamemode *input* mode has been proposed a couple of times.
This mode
would take only a root (and optionally, a slash or alternate bass
note), and
everything else
On 6/1/09 5:29 PM, Peter Chubb lily.u...@chubb.wattle.id.au wrote:
Hi,
I've put up a page on how to get more realistic sounding MIDI output
from current LilyPond, along with the scripts and scheme code used, at
http://www.nicta.com.au/people/chubbp/articulate
Peter,
I haven't
On 6/1/09 1:45 PM, lasconic lasco...@gmail.com wrote:
Hi,
Just in case it can be helpful, someone (Karl) post a pdf he wrote on
MuseScore (http://www.musescore.org) mailing list about chord name display.
Musescore is a free GPL WYSIWYG scorewriter (with lilypond export
capabilities)
is this from midi input?
if so you should be sure to apply appropriate --allow-tuplet= options.
also, funny durations like s32*231 could indicate some kind of grace notes
in the original music
see
http://lilypond.org/doc/v2.12/Documentation/user/lilypond-program/Invoking-midi2ly
Carl D. Sorensen wrote:
As far as I can see, there is very little hope for LilyPond making the right
decision about this chord entered in note mode. The first note is not the
root of the chord, so it would require substantial computation time to try
to identify the chord properly (and there's
36 matches
Mail list logo
