Re: accessing current file name in markup function

>> Maybe a bit less esoteric: > > Or even less esoteric: Thanks! However, Jean's statement > markups don't store location info, unfortunately. is still true, which means that you can't access the current input location within `define-markup-command`. Werner

Re: Fw: I wrote a MIDI to Lily front end; also questions about video

On Thu, 2023-12-07 at 02:43 +, Chris Korda wrote: > Doesn’t LilyPond already contain python? There’s a python.exe in the > bin folder, and it appears to run the python scripts that come with > LilyPond, can I just use that to run ly2video? I’m guessing not > because that would be too easy.

Fw: I wrote a MIDI to Lily front end; also questions about video

Hi Stefano,  I’m sure it would’ve been nicer, but life is short and I’m old, with way too many projects already (thirteen of them public, all FOSS). Thanks for the suggestions, but I’ve been programming in Windows since 1999, and wrestling with Linux is not on my bucket list. I agree that

Re: I wrote a MIDI to Lily front end; also questions about video

Yeah I figured using event-listener.ly wasn’t likely to work, because that was too easy.  This other thing that you linked is hella  complicated. It also does many things that I don’t need to do. All I need out of this is a text file just like the one that comes from event listener, except

Re: I wrote a MIDI to Lily front end; also questions about video

On Wed, 2023-12-06 at 17:21 +, Chris Korda wrote: > I spent much of the last week converting my compositions from MIDI > files to Lily format. I tried midi2ly first, but found it lacking, > and decided to roll my own in C++. I gather there are other > converters around, as I saw at least one

Re: I wrote a MIDI to Lily front end; also questions about video

> Thanks for your reply. Regarding scheme code: it seems to me that the > simplest solution would be to modify event-listener.ly so that instead of > storing point-and-click data (row and column within the lily file), it > instead stores the pixel coordinate X, Y of the note’s (or rest’s)

Re: I wrote a MIDI to Lily front end; also questions about video

Hi Jean, Thanks for your reply. Regarding scheme code: it seems to me that the simplest solution would be to modify event-listener.ly so that instead of storing point-and-click data (row and column within the lily file), it instead stores the pixel coordinate X, Y of the note’s (or rest’s)

Re: accessing current file name in markup function

Valentin Petzel writes: > Am Mittwoch, 6. Dezember 2023, 23:10:11 CET schrieb Jean Abou Samra: >> \version "2.24.2" >> >> #(define-markup-command (foo layout props loc-provider) (ly:music?) >>(display (ly:input-file-line-char-column (ly:music-property loc-provider >> 'origin)))

Re: accessing current file name in markup function

Am Mittwoch, 6. Dezember 2023, 23:10:11 CET schrieb Jean Abou Samra: > \version "2.24.2" > > #(define-markup-command (foo layout props loc-provider) (ly:music?) >(display (ly:input-file-line-char-column (ly:music-property loc-provider > 'origin))) empty-stencil) > > \markup \foo {{}} Maybe

Re: I wrote a MIDI to Lily front end; also questions about video

Hi, > I spent much of the last week converting my compositions from MIDI files to > Lily format. I tried midi2ly first, but found it lacking, and decided to roll > my own in C++. I gather there are other converters around, as I saw at least > one on GitHub. I may put mine on GitHub too, after

Re: accessing current file name in markup function

> OK, thanks.  But what about accessing the `input-file-name` variable? > Shouldn't this work within `delay-stencil-evaluation`? delay-stencil-evaluation or not, during backend processing, input-file-name is set to the filename of the main file, not the filename of the file where the markup

Re: accessing current file name in markup function

>> How can I access the current LilyPond input file name from within a >> markup command?  Or do I have to use the (undocumented) >> `delay-stencil-evaluation` functionality? > > If you mean the name of the file from which the command is called > (vs. defined), you can't — markups don't store

Re: accessing current file name in markup function

> How can I access the current LilyPond input file name from within a > markup command?  Or do I have to use the (undocumented) > `delay-stencil-evaluation` functionality? If you mean the name of the file from which the command is called (vs. defined), you can't — markups don't store location

accessing current file name in markup function

How can I access the current LilyPond input file name from within a markup command? Or do I have to use the (undocumented) `delay-stencil-evaluation` functionality? Werner

Re: Hide chords

Hi Kieren, Indeed, ‘omit' and ‘undo omit' do the trick for temporarily hiding chords you’ve written. It was actually the rest spacer that I was missing in my Lilypond vocabulary (I’m learning). Thanks ! Jan > On 5 Dec 2023, at 23:28, Kieren MacMillan wrote: > > Hi Jan, > > [p.s. Always

Re: Hide chords

Elaine, All very clear and exactly what I was looking for. Thanks a lot ! Jan > On 6 Dec 2023, at 02:59, Flaming Hakama by Elaine > wrote: > > > >> -- Forwarded message -- >> From: Jan mailto:jan.vander...@gmail.com>> >> To: lilypond-user Mailinglist >

Re: Hide chords

Hi Matthew, The spacer rest works perfectly for my purpose and I learned something new ;-). Thanks for your help! Jan . > On 5 Dec 2023, at 23:11, msk...@ansuz.sooke.bc.ca wrote: > > On Tue, 5 Dec 2023, Jan wrote: > >> What is the recommended method to “hide” chord names for a couple of >>

I wrote a MIDI to Lily front end; also questions about video

Hi all, I'm a composer and a software developer, and I started using LilyPond only a week ago. I'm very impressed with LilyPond; its functionality and documentation are outstanding. I had previously tried Sibelius and MuseScore, but had many issues with them. I spent much of the last week

Re: Lyricmode and fonts

Thanks, Aaron! Perfect! ..m. > On 6 Dec 2023, at 19:41, Aaron Hill wrote: > > On 2023-12-06 12:32 am, Henning Hraban Ramm wrote: >> You can override a whole Lyrics context with >> \override Lyrics.LyricText.font-shape = #'italic >> But that’s only suitable if you have your versions in

Re: Lyricmode and fonts

Thanks, Aaron! Perfect! ..m. > On 6 Dec 2023, at 19:41, Aaron Hill wrote: > > On 2023-12-06 12:32 am, Henning Hraban Ramm wrote: >> You can override a whole Lyrics context with >> \override Lyrics.LyricText.font-shape = #'italic >> But that’s only suitable if you have your versions in

Re: Lyricmode and fonts

On 2023-12-06 12:32 am, Henning Hraban Ramm wrote: You can override a whole Lyrics context with \override Lyrics.LyricText.font-shape = #'italic But that’s only suitable if you have your versions in different lines. Pretty sure this would work for a single Lyrics context: \lyricmode {

Re: Lyricmode and fonts

Am 06.12.23 um 08:43 schrieb Mark Probert: Hi. I’m setting a song and there are two voices, like a call and response. I want to show these two different voices by making one italic and the other regular font. I there are simple way, say using some \override, where I can change the default