Re: Open Sound control?

> "D" == David Wright writes: D> If one can save OSC files like MIDI files, could you please send D> me one, and some instructions on how to play it. score-with-notes.osc Description: Binary data If you by "play it" mean getting sound from it, set up

Re: Changing basic distance between stanzas

On Tue, Aug 16, 2016 at 9:06 PM, David Nalesnik wrote: > \layout { > \context { > \Lyrics > \override VerticalAxisGroup #'nonstaff-nonstaff-spacing = > #'((basic-distance . 5)) > } > } > ​That worked very well! Thanks! Can anyone

Re: Changing basic distance between stanzas

On Tue, Aug 16, 2016 at 8:58 PM, Joshua Nichols wrote: > Thanks, I did look into this, and instead of a warning, I get no change. > > See below for what I used. > > \version "2.18.2" > > notesA = { > c' > } > > vOne = \lyricmode { > a > } > > vTwo = \lyricmode { >

Re: Changing basic distance between stanzas

Thanks, I did look into this, and instead of a warning, I get no change. See below for what I used. \version "2.18.2" notesA = { c' } vOne = \lyricmode { a } vTwo = \lyricmode { b } \score { << \new Voice = "mel" { \notesA } \new Lyrics \lyricsto "mel" { \vOne } \new

Re: Changing basic distance between stanzas

Hi Josh, On Tue, Aug 16, 2016 at 8:34 PM, Joshua Nichols wrote: > I am looking for a tweak to decrease or increase the vertical distance > between multiple stanzas. > > I found this online (not in the manual): > > \context { > \Lyrics > minimumVerticalExtent =

Changing basic distance between stanzas

I am looking for a tweak to decrease or increase the vertical distance between multiple stanzas. I found this online (not in the manual): \context { \Lyrics minimumVerticalExtent = #'(0 . 0) } ​But, when I compile (with any number in the variable) I get this message: warning: cannot

MusicXML2Ly: Problem with minor chords

Hi, In the attached XML, the minor D chord D minor is translated into d:m5 and apparently not understood -- lilypond renders it as a major D chord without warning. Dm(maj7) becomes d:maj7m5. A similar thing happens to half-diminished

Re: Custom glyph depending on the 'glyph-name

Ok I got it. Sorry for the noise. Cheers, Pierre 2016-08-16 22:06 GMT+02:00 Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com>: > Hi, > > I'd like to customize the clefs depending on their glyph-name: > > %% > \version "2.19.46" > > my-clef-G = \markup "G" > > my-clef-F = \markup "F" > >

Re: Compiling against guile-2.*

Am 16. August 2016 22:21:13 MESZ, schrieb Jacques Menu Muzhic : >Hello Andrew, > >Guile 2.x features semantic changes (in memory management IIRC) that >prevent LP from being able to use it, DK will tell you more. ... or simply search the archives for this recurring nasty

Re: Compiling against guile-2.*

Hello Andrew, Guile 2.x features semantic changes (in memory management IIRC) that prevent LP from being able to use it, DK will tell you more. JM > Le 16 août 2016 à 22:03, N. Andrew Walsh a écrit : > > Hi List, > > so I'm compiling a "live" build of Lily that

Re: Keep alive together - call for use cases

Hi David (et al.), > (The last line of the thread made me chuckle and sigh.) =) Here’s a later incarnation of the same thread/topic: Still unresolved… sigh. But I have great hopes for Mark’s work on this! Best, Kieren.

Custom glyph depending on the 'glyph-name

Hi, I'd like to customize the clefs depending on their glyph-name: %% \version "2.19.46" my-clef-G = \markup "G" my-clef-F = \markup "F" \score { \new PianoStaff << \new Staff { c' } \new Staff { \clef F c' } >> \layout { \context { \Score \override Clef.stencil

Compiling against guile-2.*

Hi List, so I'm compiling a "live" build of Lily that seems to build from git, and I got this error: WARNING: Please consider installing optional programs or files: guile < 1.9.0 (installed: 2.0.12) texi2html dblatex lh CTAN package (texlive-lang-cyrillic or texlive-texmf-fonts) ERROR: Please

Re: Keep alive together - call for use cases

On Tue 16 Aug 2016 at 15:00:05 (-0400), Kieren MacMillan wrote: > On Aug 16, 2016, at 2:50 PM, tisimst wrote: > > I'll just re-state my earlier use-case (in the devel- mailing list) for > > good measure that extends divisi staves. > > Yes. On a related note, see the

Re: Keep alive together - call for use cases

At 12:13 on 16 Aug 2016, tisimst wrote: >A great example (better and more likely to happen than mine)! Maybe >you'll be able to check this item off you wish-list soon! Thanks both for those. I probably won't do anything on this for the next couple of days, so feel free to add more thoughts if you

Re: Keep alive together - call for use cases

On Tue, Aug 16, 2016 at 1:01 PM, Kieren MacMillan [via Lilypond] < ml-node+s1069038n193727...@n5.nabble.com> wrote: > > On Aug 16, 2016, at 2:50 PM, tisimst <[hidden email] > > wrote: > > I'll just re-state my earlier use-case (in the devel- mailing

Re: Keep alive together - call for use cases

Hi Abraham, On Aug 16, 2016, at 2:50 PM, tisimst wrote: > I'll just re-state my earlier use-case (in the devel- mailing list) for good > measure that extends divisi staves. Yes. On a related note, see the thread I started a few years ago (still open, ultimately) on

Re: Keep alive together - call for use cases

On Tue, Aug 16, 2016 at 12:22 PM, Kieren MacMillan [via Lilypond] < ml-node+s1069038n193724...@n5.nabble.com> wrote: > Hi Mark, > > > I've been working on some patches to enable more flexible uses > > for the Keep_alive_together_engraver. > > Thank you! > > > if I could ask users for any

Re: Keep alive together - call for use cases

Hi Mark, > I've been working on some patches to enable more flexible uses > for the Keep_alive_together_engraver. Thank you! > if I could ask users for any situations where they can imagine this > engraver helping, that currently don't work, or don't work easily. 1a. The "frenched score with

Keep alive together - call for use cases

I've been working on some patches to enable more flexible uses for the Keep_alive_together_engraver. Whilst I've achieved my particular use case, David K is (rightly) keen that any changes might also address (or at least not rule out) other potential improvements. (If you're interested in the

Re: Open Sound control?

> "D" == David Kastrup writes: D> MusicXML export would likely be quite more useful for letting D> LilyPond interface with other applications while preserving more D> information about the original input. Obviously. I'm commenting on a misunderstanding vs.

Bay Area

Hi everyone, I'm really looking forward to attend the GSoC mentors summit on the last weekend of October in Sunnyvale. I intend to be in the Bay Area somewhat earlier, depending on how many days of leave I can negotiate with my family ;-) So I expect to be around SF ca. Oct 25-27(28) and would

Re: Open Sound control?

ander...@notam02.no writes: >> "D" == David Wright writes: > > D> I've googled around for a file format, but all I find are > D> applications and program fragments. OK, an application might be > D> able to store an OSC protocol stream in a file, but