Re: Swing Midi
Erik Sandberg wrote: If you want to do something more generic (something you can apply on any existing ly score), then you may want to consider using music streams. Music streams are a new concept in 2.9, and nobody has used them yet AFAIK. However, I can try to guide you if you're interested. (I would guess htat this solution can be coded entirely in Scheme) I'm very interested in this. I don't recall seeing anything about it in the manual -- maybe I missed it. Is there a description somewhere? -Dave ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Orchestral score file organization
Rick Hansen (aka RickH) wrote:
\include CommonHeader.ly% contains header block and begins a
score block and begins a nested choir staff block
\include AltoSax1.ly % generic template for alto
sax and transposes for Eb
\include AltoSax2.ly % etc
\include TenorSax1.ly % etc
\include TenorSax2.ly % etc
\include BaritoneSax.ly % etc
\include CommonTrailer.ly % ends the choir staff block,
states the layout block, and ends the score block
Yuck! I get what you're doing, especially with your second note
on the topic, but spreading a score {} block across include files
smacks of bad programming practice.
It would be better if we could create and assign Staves, Voices,
Lyrics, etc. to variables. Then we could do something like this:
myMusic_ForConcertoNo3.ly:
varViolinINotes = \relative c' { a-4 b c d }
varViolinIINotes = \relative c' { d2 f }
varClarinetNotes = \relative c' { d16 e f g d f g a d2 }
varTitle = "Concerto Number 3"
varKey = { \key c \major }
varTime = { \time 4/4 }
varStyle = "Moderato"
varComposer = "Beat-hooven"
myStructure_ViolinI.ly:
varViolinIStaff = \new Staff \with {
instrument = \markup { \sans "Violin I" }
stringNumberOrientations = #'(left)
fingeringOrientations = #'(right)
} % end with
{
#(set-accidental-style 'modern)
\clef "treble"
\once \override Score.RehearsalMark #'self-alignment-X = #left
\mark
\markup { \bold \smaller \varStyle }
\varKey
\varTime
\varViolinINotes
}
myStructure_Orchestra.ly:
myOrchestralLayout = layout { ... }
myOrchestralScore = score {
\myViolinIStaff
...
\myOrchestralLayout
}
myCompileViolinI_ForConcertoNo3.ly:
\include "myMusic_ForConcertoNo3.ly"
\include "myStructure_ViolinI.ly"
\include "myStructure_Orchestra.ly"
\myOrchestralScore
This is a more structured approach than splitting the syntax across
files. Perhaps it is already possible to do this -- I haven't tried.
Thoughts?
-Dave
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Swing Midi
Hi everyone, I searched the archives and found a few discussions about generating swing-feel MIDI from straight eighths Lily source but the most recent was from 2004. I was thinking about writing a Scheme function to carve up all of the durations into units of eighths, inserting the proper ties to maintain longer notes. Then I could imagine altering the durations as appropriate to implement the swing feel. Can anyone give me an idea of the complexity of this? I can imagine writing it in such a way that the "swing bias" can be specified (e.g. triplet, quintuplet, etc.). I know only as much Scheme as is covered in the 2.9.17 manual, which is to say, not much. What is the recommended reference? SICP? I could do this in C++ with no problem, but Scheme is a very different beast. I'm not at all sure how to do complex data structure manipulation in it. Might it be easier to do something with Perl or a similar text-processing language to alter the Lily source directly? It would be nice to have a music function that others could share. The main reason I want to do this is not to generate perfect-sounding music but to be able to give a new score and accompanying MIDI to people learning new stuff. -Dave ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing tempo marks on every part
Han-Wen Nienhuys wrote: Anything I can do to help debug this? I can produce a testcase eventually, but probably not right now due to time constraints. I'll try 2.8 and see if that works. segfaults are bugs. Please submit the offending .ly. Yep. I determined that I had a \new Staff in the quoted part, which according to the docs is a no-no. When I removed that all was well. I'll see if I can code up a short testcase tonight. -Dave ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Swing Eighths Marking
Graham Percival wrote: Sent on Aug 28: http://lists.gnu.org/archive/html/lilypond-devel/2006-08/msg00146.html If you want to volunteer, great! I'm available to discuss any portion of this. I would very happily do this, but I have to finish typesetting my current project first. I have a deadline in a couple of days. Perhaps sometime this weekend I could get started. I see there are a lot of "ask Sebastino to" items. I'm new here so I don't have all the context. Is there some reason I could not handle these items myself given proper access to the relevant repositories? It seems like a pretty straightforward Perl script should do the trick. -Dave ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Swing Eighths Marking
Markus Schneider wrote: Have you ever considered that your question has probably been already discussed, and that showing you the right keyword for searching is the quickest solution. ... indeed it has and an almost "ready-to-use" example can be found here: http://lsr.dsi.unimi.it/LSR/Item?id=204 It's good that you mention that here because I was thinking about something last night. Would it not be possible to suck out all the snippets from the LSR and format them similarly to the existing "tips and tricks" documentation? Couldn't we just generate an appendix of idioms, give them nice section headings, etc? The lily code and pdfs are already there. Slap it onto the end of the existing documentation and call it good enough for now. -Dave ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Repeat Alternatives w/o Repeat Bar
Paul Scott wrote: Manual repeat commands. Using 2.9.17. I looked at that and I think I know how to do it but I was hoping there was a way to specify this but retain the nice useage of volta and \unrollRepeats for midi output. I suppose I just have to choose one or the other since Lily doesn't seem to have built-in segno, coda, D.C. or D.S. commands that could be taken into account for midi output. Is there any sort of plan for that in the future? I can't answer that. Hopefully someone else will. I'll bet you could get a group to sponsor that. I might contribute if it got smart versions of D.C., etc. Ok, I'll throw out the question. What are we looking at in terms of cost to produce this functionality? I would be very happy to contribute. -Dave ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
