Sep 26, 2016

Now Open: Music Type Foundry


The time has come, the wait is over!


The day has come to begin another chapter in my life. Before I do that, I just want to thank everyone for their support over that past few years. This has been a tremendous journey for me. I'd especially like to thank Urs Liska for his kindness, his generosity in sharing some server space and hosting fonts.openlilylib.org (which is no more) and providing so much musical expertise to myself and the music engraving community as a whole.

And now, I'm very excited to announce that I have officially made the move to a brand-new web store: Music Type Foundry, a dedicated site to serve all my alternative music notation fonts. Each product page is full of a variety of example scores so you can get a taste for what they look like in action in different styles of scores. The goal is to support users of all the major music scoring applications where possible (LilyPond, Sibelius, Finale, and Dorico). Not all fonts will be supported on all applications. The store is currently only providing fonts for LilyPond, but the others are in the works and I hope to have more support for the others by Q4 2016.

So what's new? 


All the fonts in the store have been updated and improved in one way or another. Individual glyphs have been updated. Stylesheets have been improved. Some of them are now under commercial licenses and the name has been prefixed with "MTF" so users know the difference. I haven't uploaded ALL the fonts that were there before, though I intend to eventually.

Introducing...


I am pleased to officially announce a brand-new font: MTF-Arnold!

(Image courtesy of Music Type Foundry)

(An Alban Berg excerpt, engraved by Urs Liska, lilypondblog.org)


This gorgeous 20th century revival design has all the finesse and beauty of classic Universal Edition scores. Readers of this blog can get 20% off this fantastic font all the way through October. Just enter the code LEIGHVERLAG at checkout to receive the discount.

What Am I Working On?


At the moment, I am hard at work--given the small amount of time I have each day for it--to make many of the current set of fonts available to Sibelius, Finale, and (future) Dorico users. This sure is helping me appreciate the SMuFL standard (thanks, Daniel Spreadbury!).

One thing that I've mentioned in previous posts that I am most excited about is creating Multiple Master (MM) professional fonts (i.e., optical fonts) of each of my designs so that users get more appropriately designed/weighted glyphs for printing at smaller/larger sizes. For LilyPond, these will be at the usual standard set of staff sizes: 11, 13, 14, 16, 18, 20 (default), 23, and 26pt. For other apps, there will likely be just two sizes since they don't really support more than that (and some not even that, at least not in the same score): a standard size and an "ossia" size. The SMuFL standard supports these two sizes within the same file, but I'm not sure when any of the apps will actually be able to use them like that.

I've also got some other LilyPond tips and tutorials that I hope to post here soon.

If you notice anything amiss on the site--any links that are broken or missing, any instructions that aren't clear, and especially if any fonts aren't working--please don't hesitate to let me know. You may even get a little something in return ;-)

Apr 14, 2016

A Couple of Home-grown Free PDF Utilities


So, I've been busy lately doing lots of fun things, both at home, work, and on the side. I'm working hard to get my new font site up and running, but a couple of things in particular I completed recently are two free PDF utilities that are currently being hosted by Philip Rothman of NYC Music Services: PDF-BatchScale and PDF-BatchBooklet. The are available for both Windows and Mac. I'm going to borrow some of the text/images from the download site (thanks, Philip!). If either of these sound interesting/useful to you, read on!

Dec 15, 2015

Mimicking the Real Book Look


Stop! If you have never heard of "Real Book" or "Fake Book", go look it up and then come back.

(no really, go ahead... I'll wait for you...)

Done? Good. Now, hopefully you are more familiar with what a Real Book score looks like, so let's move forward.

Dec 8, 2015

A Small Holiday Gift

So, I've not been able to keep this blog as up-to-date as I'd like to. To remedy that a little, here's a small holiday gift to you. This gift was originally given by Mark Adler on the Finale Blog, but since he offered it freely, I decided to pass it along, with a little extra for all the LilyPond users out there.


Sep 10, 2015

Gorgeous Plate Engraving Pics

In a Facebook post today from Bärenreiter-Verlag, they shared some images of the good-ol'-days of real plate engraving that I think any modern computer music engraver/copyist/etc. will appreciate. I know I do. This comes from the golden-era of music publishing, folks! I share them here for long-term enjoyment just in case the above post/pictures disappear from Facebook.

Jul 6, 2015

Quick Summer 2015 Update

It seems like I've been out of the loop for too long, so I thought I'd post a quick update with info about what I've been up to.

Jun 2, 2015

New LilyPond Templates (part 2)

As promised, here is the second installment of templates. I've created templates for Rock and Pop, Jazz, and Latin style scores.

May 27, 2015

New LilyPond Templates (part 1)

Greetings, everyone!

It feels strange to (once again) not have put up a post before another month passed, but, alas, it has happened again. Let's remedy the situation!

I've decided to take it upon myself to create a small library of LilyPond 2.18.2 template files that are inspired by those found in the latest version of Sibelius (7.5). When all is said and done, I plan on replicating ALL of its templates in the following categories:
  1. No Category
  2. Solo Instruments
  3. Band
  4. Chamber Groups
  5. Choral and Song
  6. Handbells
  7. Jazz
  8. Latin
  9. Marching Band and Percussion
  10. Orchestral
  11. Orff Instruments
  12. Rock and Pop
So far, I've got #1 and 2 done, but hopefully will be able to pick up the pace and get the others cranked out. I've tried to follow Sibelius' designs as faithfully as possible in hopes that Sibelius users who are familiar with them will find the change over to LilyPond that much easier.

Apr 20, 2015

Recent Developments

Wow, over a whole month has gone by without a post. Well, I've been busy working on myriad of (mostly font-related) projects. I'm still not quite done with most of them, but here are some highlights of my latest adventures that will hopefully be released soon:

Mar 5, 2015

Different Staff Sizes

I've seen a lot of discussion as to how to deal with staves of different heights, either within the same score or elsewhere. I don't propose to have a great solution for this, but I'd like to share something I discovered (accidentally) while preparing some LilyPond tutorials.

Feb 18, 2015

Panorama Mode

Do you come from a notation program that has a "Panarama" mode for viewing your score? Well, fear not! Such a feature exists even in LilyPond to make you feel right at home, but it's not called "Panorama". It's a layout algorithm called ly:one-line-breaking.

To have your score print on a single sheet that adjusts to the length of the score, use the following code:
\paper {
  page-breaking = #ly:one-line-breaking
}
For example, here are the first two pages from a 3-page score in "normal paper" mode:


And here's how it looks when we use the one-line-breaking algorithm (cropped slightly):


That's it! Now, there are some things to remember about using this mode (from the official docs):
  1. Each score gets its own line, but everything is on a single page.
  2. All text in the \header block is NOT typeset, which is fine since this is really more of a preview mode anyway.
  3. The width of the page will be adjusted so the longest score fits on one page.
  4. Some variables in the \paper block will be ignored (like paper-width, indent, line-width) while others will be honored (like left-margin, right-margin, etc.).
  5. The height of the page is un-changed, but honored to whatever you set it to be.
Personally, I wish the height of the page automatically fit to the scores, but oh-well.

Do you miss this mode? Do you find it useful? Let me know in the comments!

Feb 7, 2015

Font Update (Improviso, Ross, Profondo)

Another set of updates have been applied and are now available on my font site: fonts.openlilylib.org. Here are the highlights:
  • Improviso (v1.1)
    • Fixed a bad contour in the clefs.C_change glyph.
    • Packaged three hand-written text fonts (one of my own creation) to compliment the font style.
  • Ross (v1.1)
    • Thickened up the scripts.tenuto articulation (which also updated the up and down portato).
    • Added information about the IM FELL text fonts.
  • Profondo (no version change)
    • Packaged my tuplet number font so the style is more consistent (the glyphs come from Bravura). The \override is now part of the default profondo.ily stylesheet.
If you haven't been over there in a while, go check them out and let me know if something is not working correctly!

Do you have a score that uses one of your favorite music fonts? Let me know so I can add it as an example on the respective font page!

Happy Engraving!

Feb 4, 2015

Engraver Spotlight: David Stephen Grant

I was recently introduced to the composer/engraver David Stephen Grant, who shared with me a very lovely score he had composed and engraved using LilyPond. The score is done with my Ross music font (and accompanying stylesheet), complimented perfectly by the IM Fell English text font.


David shared with me some background to the score:
... "Overture to Bérénice" was actually used as an Overture to a modern theatre production of Racine's "Bérénice" that I composed and contributed sound design for. The music quickly moved from this "Baroque" atmosphere into more noisy electronic sound design, ...
Great job, David, and thanks for sharing this with us!



Have you engraved something you'd like to feature here that shows off one of my music fonts? Let me know or provide a link in the comment section!

Jan 23, 2015

Update to fonts website!

I'm proud to announce a few nice updates to fonts.openlilylib.org today! I had wanted to make some changes and add a few things since the last major update and I finally got around to it. Here are the changes:
  • Updated fonts: A few fonts had "hole" artifacts from overlapping contours when using certain programs to view the glyphs (such as Inkscape, Adobe Acrobat PDF, etc.). These have now been fixed and any future use of these glyphs should result in the proper forms. Specifically, the fonts affected by this update are: Beethoven, Improviso, LilyJAZZ, Ross, and Scorlatti. If you notice any others, let me know!

  • Font stylesheets: A few minor additions to the stylesheets have been included and on each page there is now a direct link to the respective stylesheet itself for easier viewing and downloading.

  • Font viewer: I've added a convenient way to quickly look through the main glyphs in each font and compare them to others. This is what I'd wanted to do for some time and now it's finally here. Go check it out!

  • Documentation: All documentation about installation and usage that used to be on the main page has been moved to a dedicated page to keep the landing page simpler. As always, if a link is broken, I want to hear about it.
I always am trying to improve the look-and-feel of the page, so you may see some minor changes there too. Are things working on your machine/browser? Do you like the changes? Let me know in the comments!

Jan 20, 2015

Advanced Staff Grouping

Man, I love the LSR! There are so many interesting snippets there. I had to write a quick post about this one, too:

To be honest, the big orchestral brace looks a bit ugly to me (no offense to the original creators). It uses postscript code (and that's probably the point of the snippet) and requires a bunch of unnecessary \overrides. Let's clean it (and the code) up a bit!

In this snippet, a handful of useful new contexts are created to assist in grouping things together. The main contexts that already exist are: Score, GrandStaff, StaffGroup, Staff, Voice, etc. We can create new contexts by aliasing the appropriate default contexts. For example, if we want to create a "ViolinGroup", because we'd like to give a staff to the 1st and 2nd violin groups, we can do so like this:
\layout {
  \context {
    \StaffGroup
    \name ViolinGroup
    \alias StaffGroup
    systemStartDelimiter = #'SystemStartBrace
  }
}
The ViolinGroup now behaves like a StaffGroup, but with a system brace as its group indicator. The snippet goes on to similarly create a WindGroup, but uses the default system bracket as the group indicator, inheriting from StaffGroup.

Going further, we now create a StringGroup, intended for including the ViolinGroup as well as the normal Staff for the violas, cellos, and contrabasses:
\layout {
  \context {
    \StaffGroup
    \name StringGroup
    \alias StaffGroup
    \accepts ViolinGroup
    systemStartDelimiter = #'SystemStartBracket
  }
}
Since StaffGroup already \accepts the Staff context, there is no need to repeat that here, but we do need to explicitly say "\accepts ViolinGroup" since that's a custom context. The StringGroup would then need to be accepted by the context containing it (if necessary, which it is here):
\layout {
  \context {
    \StaffGroup
    \name OrchestraGroup
    \accepts WindGroup
    \accepts StringGroup
    \remove "System_start_delimiter_engraver"
  }
}
We remove the "System_start_delimiter_engraver" because we don't want it to show up right by the system itself, so we will customize this in the instrumentName variable. For this, we're going to rotate the text "Orchestra" vertically and add a large brace to show the correct grouping:
\markup { 
  \lower #0.75 \rotate #90 "Orchestra" \hspace #1
  \left-brace #175 \hspace #5
}
The extra "\hspace" commands are just to give each element a good amount of space. The last little bit of \override-ing we need to do is for the regular instrument names:
\layout {
  \context {
    \Staff
    \override InstrumentName.font-size = #-1
    \override InstrumentName.extra-offset = #'(6 . 0)
  }
}
If we didn't do these, they will show up too far-away to the system (depending on the value of "indent", of course) and to help with spacing we decrease the font-size slightly.

Those are the main building blocks we need. Here's the full updated snippet:
\version "2.18.2"
%% http://lsr.di.unimi.it/LSR/Item?id=906

% by Kieren MacMillan and P.P.Schneider.
% => http://lists.gnu.org/archive/html/lilypond-user/2013-03/msg00260.html

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% LSR workaround:
#(set! paper-alist (cons '("snippet" . (cons (* 90 mm) (* 120 mm))) paper-alist))
\paper {
  #(set-paper-size "snippet")
  tagline = ##f
}

\markup \vspace #1
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%here starts the snippet:

someMusic = { 
  \tempo "Andante."
  \time 3/4
  \key c \minor
  c'2. r8 
}

\paper { 
  indent = 40 
}

\layout {
  \context {
    \Staff
    \override InstrumentName.font-size = #-1
    \override InstrumentName.extra-offset = #'(6 . 0)
  }
  \context {
    \StaffGroup
    \name ViolinGroup
    \alias StaffGroup
    systemStartDelimiter = #'SystemStartBrace
  }
  \context {
    \StaffGroup
    \name WindGroup
    \alias StaffGroup
    systemStartDelimiter = #'SystemStartBracket
    \override SystemStartBracket.collapse-height = #1
  }
  \context {
    \StaffGroup
    \name StringGroup
    \alias StaffGroup
    \accepts ViolinGroup
    systemStartDelimiter = #'SystemStartBracket
  }
  \context {
    \StaffGroup
    \name OrchestraGroup
    \accepts WindGroup
    \accepts StringGroup
    \remove "System_start_delimiter_engraver"
    instrumentName = \markup { 
      \lower #0.75 \rotate #90 "Orchestra" \hspace #1
      \left-brace #175 \hspace #5
    }
  }
  \context {
    \GrandStaff
    \remove "System_start_delimiter_engraver"
    \accepts OrchestraGroup
    \accepts StaffGroup
    \accepts VocalGroup
  }
  \context {
    \StaffGroup
    \name VocalGroup
    \alias StaffGroup
    systemStartDelimiter = #'SystemStartBracket
  }
}

\score {
  \new GrandStaff <<
    \new OrchestraGroup <<
      \new WindGroup <<
        \new Staff \with { 
          instrumentName = "Oboe" 
        } \someMusic
      >>
      \new StringGroup <<
        \new ViolinGroup <<
          \new Staff \with { 
            instrumentName = "Violino I" 
          } \someMusic
          \new Staff \with { 
            instrumentName = "Violino II" 
          } \someMusic
        >>
        \new Staff \with { 
            instrumentName = "Viola" 
          } { \clef C \someMusic }
      >>
    >>
    \new VocalGroup <<
      \new Staff \with { 
       instrumentName = "Soprano" 
      } \someMusic
      \new Staff \with { 
       instrumentName = "Alto" 
      } { \clef C \someMusic }
    >>
  >>
}
What do you think? Let me know in the comments. What other contexts have you used/created before? How have you shown grouped instruments? I'd love to hear your experiences.

Jan 5, 2015

Increasing the horizontal size of a single measure

So, I couldn't help but make a small post about this when I saw it, since I've heard numerous people ask about it. In programs like Musescore, to increase/decrease the size of a measure, there's a keyboard shortcut for that. In LilyPond, since the horizontal spacing engine makes the whitespace "springy" and compressible, it's a less straightforward process. The documented ways of adjusting the horizontal spacing are found in the Notation Reference (NR), so I won't go over them here (well, maybe later).

As I was browsing through the LilyPond Snippet Repository (LSR), looking for something completely different, I stumbled upon this little trick for adjusting measure width. Unfortunately, it is only helpful for increasing the width. Let's start with a simple score:
\new Voice \relative c' {
  \dynamicUp
  << { c1 } { s2\f s2\p } >> | \noBreak
  f4 e d c | \noBreak
  << { c1 } { s2\f s2\p } >> | \noBreak
  d2 e | \break
}
The issue we'd like to remedy is the horizontal spacing given to the dynamics in the first measure, which we will adjust in the third measure for comparison. The real trick here is to use a parallel voice that contains basically no musical information, but allows us to override some dimensions. Using a MultiMeasureRest (MMR) gives us access to a property called "minimum-length". This is what we will use to force the measure to extend in length, thus creating more space for the second dynamic marking. To make it more useful, I wrapped the code within a music function that we can reuse.
extender = #(define-music-function (parser location length music) 
            (number? ly:music?)
            #{
               <<
                 { $music }
                 \new Voice {
                   \override MultiMeasureRest.transparent = ##t
                   \override MultiMeasureRest.minimum-length = #length
                   R1
                 }
               >>
             #})
This function takes two arguments. The first sets the value for "minimum-length". By definition, if the measure is already as long or longer than this value, then nothing changes. The second argument is the music expression that the spacing should apply to. There are two things to remember with this:
  1. The above code assumes the largest duration is a whole note, so you will need to change the duration of the MMR if you are using a different time signature ("R2." for 3/4 time, etc.).
  2. It's designed to extend the length of ONE measure only. Repeat as necessary.
Now, let's put it to use:
\version "2.18.2"

\paper {
  line-width = 9\cm
  indent = 0
}

extender = #(define-music-function (parser location length music) 
            (number? ly:music?)
            #{
               <<
                 { $music }
                 \new Voice {
                   \override MultiMeasureRest.transparent = ##t
                   \override MultiMeasureRest.minimum-length = #length
                   R1
                 }
               >>
             #})

\markup "Before"
\new Voice \relative c' {
  \dynamicUp
  << { c1 } { s2\f s2\p } >> | \noBreak
  f4 e d c | \noBreak
  << { c1 } { s2\f s2\p } >> | \noBreak
  d2 e | \break
}

\markup "After"
\new Voice \relative c' {
  \dynamicUp
  << { c1 } { s2\f s2\p } >> | \noBreak
  f4 e d c | \noBreak
  \extender #12 << { c1 } { s2\f s2\p } >> | \noBreak
  d2 e | \break
}


That looks better (focus is on the third measure, of course) and certainly could be adjusted further, but we'll stop there for now, having accomplished our goal.

I'm still on the lookout for a more convenient solution for "shrinking" a measure, but some of the methods in the NR (above) can help with this.

Got any other great ideas for shrinking or expanding measures to make the page look better? Share them in the comments!

Dec 23, 2014

Merry Christmas!

To everyone out there, firstly, I want to wish the happiest of holidays, in whatever form you choose to celebrate. I truly hope these holidays are wonderful for each of you. It's a time to remember those that we love and the friendships we cherish. Hope the new year brings lots of great opportunities to each of you.

Last Sunday I performed my own arrangement of Oh, Come, All Ye Faithful for my local congregation. It turned out wonderfully and I certainly felt the spirit of Christmas as I sang it. My little brother, a very talented pianist, composer, arranger, improvisor, etc., accompanied me on the piano, though I wish we could have done it with the organ. If you're interested, here's the sheet music for your enjoyment. Feel free to download and use!


Dec 14, 2014

New Music Font: Sebastiano

So, I've actually had this done for a little while, but just hadn't released it yet. This new font is a OFL derivative of a (basically) non-public OFL-licensed font designed by engraver/composer Florian Kretlow (github source). It follows what I call the "inky" look, where internal corners (at least some of them) get "rounded" by what would have been caused by the capillary action of the liquid ink. Here's a sample (click to see a full-size PDF).



I think the font itself is quite nice. It has some inconsistencies that bother me a little, though. For example, the default flat symbol is thicker in the stem than inside the eyelet. The second f in the "sffz" ligature is different from the first. Having these inconsistencies doesn't make the font BAD, per se, just not to my taste.



Fortunately, in the source files, there were a bunch of other variants in his source files that were more to my liking. Here's the same score as above, but with my selected variants, as done in LilyPond.


The new font is available at fonts.openlilylib.org. Go get it! Here's a more extensive example: Grieg's Piano Concerto in A-minor, Second Movement.

Nov 12, 2014

Piano RH/LH Brackets

Sometimes when I'm playing the piano or organ (especially the organ, since I'm not that great with the pedals yet), I need to mark that a high note in the lower stave should be played with the right hand. Here's an example of this situation:
For me, the indicated note is easily reachable with the right hand. So, how do I mark it that way? Well, in the Notation Reference, in the Fingering Instructions section, I found an example of a custom fingering markup. Normally, if you want to indicate that a note be played with a particular finger you use the "-N" syntax where N=1, 2, etc., and you'd get something like this:

\relative c'' { 
  c4-1 d-2 f-4 e-3 
}
Pretty simple. If you need a more complex instruction (like a finger-substitution), we can use the built-in "\finger" macro that allows us to put in a "\markup" object:

\relative c'' {
  c4-1 d-2 f\finger \markup \tied-lyric #"4~3" c\finger "2 - 3"
}
Nice! Now, we take this a step further. I decided to create a bracket (or half-bracket, really) using some simple post-script commands within a "\markup" object:
lhMark = \markup { 
  \path #0.1 #'((moveto -1 0)(rlineto 0 1.5)(rlineto 0.5 0))
}
rhMark = \markup { 
  \path #0.1 #'((moveto -1 0)(rlineto 0 -1.5)(rlineto 0.5 0))
}
This is in the shape of an "L" and is designed to go on the LEFT side of the notehead. However, the default position is ABOVE the notehead (or chord, if it's part of one). So, in order to place it NEXT to the note, I need to change the "fingeringOrientations" property, like so:
\set fingeringOrientations = #'(left)
Putting these together, we get something like this:
\relative c {
  \clef bass
  \set fingeringOrientations = #'(left)
  <f, a'\finger \rhMark>4
}

Let's take this a step further. Suppose I now want to indicate "R.H." next to the bracket. This can be done pretty easily by using the "\concat" function within the "\markup" object, which concatenates two expressions, like this:
lhMarkText = \markup { 
  \concat {
    \override #'(font-encoding . latin1) \italic "L.H. " 
    \path #0.1 #'((moveto 0 -0.5)(rlineto 0 1.5)(rlineto 0.5 0))
  }
}
rhMarkText = \markup { 
  \concat {
    \override #'(font-encoding . latin1) \italic "R.H. " 
    \path #0.1 #'((moveto 0 1)(rlineto 0 -1.5)(rlineto 0.5 0))
  }
}

\relative c {
  \clef bass
  \set fingeringOrientations = #'(left)
  <f, a'\finger \rhMarkText>4
}
This can get even more involved if we need to actually bracket a section of a chord, but following the snippets above, we can do crazy things like this:
rhBracket = \markup { 
  \concat {
    \path #0.1 #'((moveto 0 -1.75)(rlineto 0.5 0)(rlineto 0 4.25)(rlineto -0.5 0))
    \override #'(font-encoding . latin1) \italic " RH" 
  }
}

lhBracket = \markup { 
  \concat {
    \path #0.1 #'((moveto 0 0.75)(rlineto 0.5 0)(rlineto 0 -3.25)(rlineto -0.5 0))
    \override #'(font-encoding . latin1) \lower #1.25 \italic " LH" 
  }
}

\new Staff \relative c, {
  \clef bass
  \set fingeringOrientations = #'(right)
  <e f bes\finger \lhBracket e\finger \rhBracket g b! dis>1\arpeggio 
}
There you go, all you piano/organ players! You may have to play around with the numbers (since there isn't a dedicated function to do this yet), but without too much effort, you should be able to get the job done.

If you are trying to do this and can't figure it out for your situation, send me an email.

Nov 6, 2014

Long, Broken (De-)Crescendo Text

Have you ever wondered how to create a dynamic marking like this:



I know I have, and as I was looking through the Chopin score above, I noticed this marking again, and having never tried to do it in LilyPond, I thought I'd figure it out.

In the LilyPond Notation Reference, under the Dynamics Section there's a subsection called "Changing text and spanner styles for text dynamics". In the example, it shows how you can customize the crescendo markings to be text instead of a hairpin and use your own markup text.

\relative c'' {
  \set crescendoText = \markup { \italic { cresc. poco } }
  \set crescendoSpanner = #'text
  \override DynamicTextSpanner.style = #'dotted-line
  a2\< a
  a2 a
  a2 a
  a2 a\mf
}

We can extend this further by using successive "\<" marks, which allows us to have as many bits of text as I want in the chain, except for the last one. To end the chain, it must end on a stand-alone dynamic. This can be created with:
do = \markup { \normal-text \italic do }
do = #(make-dynamic-script do)
or these operations can be combined:
do = #(make-dynamic-script (markup #:normal-text #:italic "do"))

Now, to create the broken-up crescendo (I'll leave the default dashed-line), we can do something like this:
\relative c'' {
  \set crescendoSpanner = #'text
  \set crescendoText = \markup \italic "cre"
  a2\< a 
  \set crescendoText = \markup \italic "scen"
  a2 a\<
  a2 a
  a2 a\do
}
So, all we need to do is put \set crescendoText = \markup \italic "some text" before the note or chord we want to attach it to and \< after it like we would normally do.