Re: chord.ly to extract notes from chords breaks with new Guile
Le 2023-05-27 22:31, msk...@ansuz.sooke.bc.ca a écrit : Back in 2015 people on the list helped me with extracting notes from chords, in this thread: https://lists.gnu.org/archive/html/lilypond-user/2015-09/msg00394.html chord.ly has been renamed to chordsAndVoices.ly (it deals also now with Voices) You can donwload it here : http://gillesth.free.fr/Lilypond/chordsAndVoices/ Note you have also to download checkPitch.ly to make it work. There is a small help http://gillesth.free.fr/Lilypond/chordsAndVoices/chordsAndVoices-doc.pdf I use chordsAndVoices.ly a lot, as it is part of the project arranger.ly http://gillesth.free.fr/Lilypond/arranger.ly/ My Lilypond version is 2.24.1 Please, tell me if there is something wrong with a more recent version. -- Gilles
Re: chord.ly to extract notes from chords breaks with new Guile
On Mon, 29 May 2023, Gilles Thibault wrote:
> chord.ly has been renamed to chordsAndVoices.ly (it deals also now with
> Voices)
> You can donwload it here :
Thanks a lot!
As far as I know, the new version works fine. The problem in the old
version was just because of the non-breaking spaces in the lines I
modified according to instructions from the mailing list. That was a
problem I encountered back in 2015 too, and thought I had fixed then. My
version of the file is unmodified since 2015; evidently some non-breaking
spaces survived the earlier fix, and earlier versions of Lilypond ignored
them. I don't know why the latest version had a problem with these
characters given that earlier versions didn't, but I also don't know why
earlier versions *didn't* have a problem with these particular
non-breaking spaces when others in the same file caused a lot of trouble.
I will say again, as I said in 2015, that I wish people would stop trying
to use HTML for email. That's where the non-breaking spaces came from.
Anyway, even the old version of chord.ly contained support for separating
voices, which I hadn't previously touched but I investigated just recently
in the hope of separating MIDI notes that don't have identical timing.
That is, if my input is
<< { a1 } \\ { b2 2 } >>
it would be nice to be able to separate it out into three separate outputs
for separate MIDI channels, like:
{ a1 }
{ b2 c2 }
{ r2 d2 }
Unfortunately, both the old chord.ly and new chordsAndVoices.ly code have
the same problem with respect to voices that I encountered in 2015 with
respect to notes within a chord: requesting a non-existent voice index
returns the last voice instead of silence. That seems to be the intended
behaviour of the code in your application, so it's not exactly a bug, but
it isn't what I need.
I think the really right answer for me is to not use Lilypond to do this
note-separation at all, but to do postprocessing with other tools on the
MIDI files generated by Lilypond instead. I'm more confident of really
getting correct results from that in all the different cases of
simultaneous notes, than I would be by trying to do the separation inside
Lilypond.
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before tribes.
https://ansuz.sooke.bc.ca/
Frescobaldi issue 16: .ly is missing by saving
Hi all I'm wondering if we can close this old Frescobaldi issue: https://github.com/frescobaldi/frescobaldi/issues/16 In some desktops (like GNOME) Frescobaldi used to save a new file without the .ly file extension. This is no longer the case today, at least on Windows 10 and GNOME Linux. Can you please report what happens in other OSes and desktop environments? We are missing feedback from MacOS and KDE Linux in particular, but any comment is helpful. Thanks Federico
Re: Frescobaldi issue 16: .ly is missing by saving
Just checked on macOS Ventura 13.4 and Frescobaldi adds the .ly extension automatically. Cheers, Lib On Mon, 29 May 2023 at 22:52, Federico Bruni wrote: > > Hi all > > I'm wondering if we can close this old Frescobaldi issue: > https://github.com/frescobaldi/frescobaldi/issues/16 > > In some desktops (like GNOME) Frescobaldi used to save a new file > without the .ly file extension. This is no longer the case today, at > least on Windows 10 and GNOME Linux. > Can you please report what happens in other OSes and desktop > environments? > > We are missing feedback from MacOS and KDE Linux in particular, but any > comment is helpful. > > Thanks > Federico > > >
Markup with text or text in dynamics font
Hi - I appreciate all the help this list provides. I seem to be helping less than I used to; not sure why. I've tried a few times recently to figure out how to make what would effectively be a markup in dynamic script, with no success. I've looked pretty extensively on the LilyPond site, as well as in the LSR and the email archives. I'm currently running LilyPond 2.24.0 and Frescobaldi 3.2 (still having problems figuring out how to install 3.3) under Linux/Ubuntu 22.04.2 LTS. I currently would like to add sempre ff e ben marcato in dynamic font. I can do a markup using \bold and \italic, but it's not quite the same as the dynamic font. Am I missing a simple way to accomplish this? I appreciate any help on this. All the best, Ralph __ Ralph Palmer Seattle USA (he, him, his) palmer.r.vio...@gmail.com
Re: Lilypond v 2.24.1, segno repeat question where segno and coda sign are adjacent
Oh, darn :-) I forgot to attach my Lilypond source code. Thanks, Ken On Mon, May 29, 2023 at 3:16 PM Kenneth Wolcott wrote: > > HI; > > Lilypond v 2.24.1, segno repeat question where segno and coda sign > are adjacent in the original. > > How to engrave this (screenshot attached)? The only segno sign is > at this location and the only coda sign is also at this location. I'd > like to engrave the music so that the midi output represents the segno > in action. What I don't understand in this case is where my \volta 1 > and \volta 2 are to be placed when the segno and coda signs are > adjacent. > > Thanks, > Ken Wolcott Raindrops_Keep_Fallin_on_my_Head_before_introducing_segno_repeat.ly Description: Binary data Raindrops_Keep_Fallin_on_my_Head.ly Description: Binary data
Re: Markup with text or text in dynamics font
In markup, you can use \dynamic to use the dynamics characters. However, only a small part of the alphabet is provided, as it is normally only used for actual dynamics; what you want is not normal practice, and would come out looking like the attached image. Paul From: Ralph Palmer To: lilypond-user Mailinglist Sent: 29/05/2023 23:00 Subject: Markup with text or text in dynamics font Hi - I appreciate all the help this list provides. I seem to be helping less than I used to; not sure why. I've tried a few times recently to figure out how to make what would effectively be a markup in dynamic script, with no success. I've looked pretty extensively on the LilyPond site, as well as in the LSR and the email archives. I'm currently running LilyPond 2.24.0 and Frescobaldi 3.2 (still having problems figuring out how to install 3.3) under Linux/Ubuntu 22.04.2 LTS. I currently would like to add sempre ff e ben marcato in dynamic font. I can do a markup using \bold and \italic, but it's not quite the same as the dynamic font. Am I missing a simple way to accomplish this? I appreciate any help on this. All the best, Ralph __ Ralph Palmer Seattle USA (he, him, his) palmer.r.vio...@gmail.com
Re: Frescobaldi issue 16: .ly is missing by saving
Fedora 38 .ly is appended automatically just fine. Andrew
Re: Frescobaldi issue 16: .ly is missing by saving
Mint 21.1 Cinnamon desktop .ly is appended automatically just fine. Andrew
Library to embed LilyPond in other programs
Hello everyone. I'd like to know if there is any way of embedding a LilyPond interpreter in a C/C++ program (For example: A library that provides the functionality to the regular downloaded executable). Thanks in advance
Re: Frescobaldi issue 16: .ly is missing by saving
On UbuntuStudio, Kubuntu 23.04, the .ly extension was automatic. Cheers, Colin On 2023-05-29 14:47, Federico Bruni wrote: Hi all I'm wondering if we can close this old Frescobaldi issue: https://github.com/frescobaldi/frescobaldi/issues/16 In some desktops (like GNOME) Frescobaldi used to save a new file without the .ly file extension. This is no longer the case today, at least on Windows 10 and GNOME Linux. Can you please report what happens in other OSes and desktop environments? We are missing feedback from MacOS and KDE Linux in particular, but any comment is helpful. Thanks Federico
Re: Library to embed LilyPond in other programs
> Le 30 mai 2023 à 07:22, Lucas Monteiro a écrit : > > > Hello everyone. > > I'd like to know if there is any way of embedding a LilyPond interpreter in a > C/C++ program (For example: A library that provides the functionality to the > regular downloaded executable). Welcome. For your information, I had to approve your post manually as a moderator because you aren't subscribed to the list. I suggest that you subscribe on https://lists.gnu.org/mailman/listinfo/lilypond-user; you may then opt out of receiving posts to the list in your member preferences if you wish. There is no liblilypond, but it is naturally possible, and common, to spawn LilyPond in a subprocess. Best, Jean
Re: Lilypond 2.24.1 repeat sego with DC : music found after \fine
> On 30 May 2023, at 02:00, Kenneth Wolcott wrote: > > Hi; > > Warning message from Lilypond 2.24.1 regarding a repeat segno > attempt with a DC: > > When_You_and_I_Were_Young_Maggie.ly:50:12: warning: found music after \fine > \volta 2 > \fine > > I have two screenshots (one that looks a little dirty is a png from a > pdf from a photo), the other is from my engraving. > > My engraving "almost" looks correct but the "DC" is missing. > > Thanks, > Ken Wolcott > 16.54.42.png> According to https://lilypond.org/doc/v2.24/Documentation/notation/long-repeats#al_002dfine-repeats The \volta1 and \volta2 sections should be within the curly braces of the repeat block. If you then change your repeats from volta to segno you get a ‘D.C. al Fine’ at the end and no errors (volta gets you the repeat bar at the end). Not sure whether that text would be easy to customise (could not find a reference for it on a quick search, only for an alternative Fine text, not for an alternative D.C. al Fine text) Kind regards Hans
