Re: Installing Frescobaldi 3.1.3 on Mac with MacOS 12.1
On 2 Sep 2022, at 17:29, Knute Snortum wrote: > > On Fri, Sep 2, 2022 at 12:30 AM Michael Hendry > wrote: >> >> Thanks to Omer and Jean for getting me back on the Frescobaldi road again. >> >> I’m now able to open, edit and compile lilypond source documents again, but >> I’m getting a lot of warnings about deprecated code which I’d like to get >> rid of. >> >> When I attempt to use ‘convert.ly’ (via Frescobaldi’s Tools menu) to update >> an affected file, the original lilypond version comes up in the “From >> version” box, but the “To version” box is blank. >> >> If I type 2.23.12 in the "To version” box I get the following... >> >> Traceback (most recent call last): >> File >> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/convert_ly.py", >> line 217, in run >> AttributeError: 'NoneType' object has no attribute ‘toolcommand' >> >> …which means nothing to me. >> >> Any suggestions? > > Just a guess, but do you have LilyPond 2.23.12 set up in Frescobaldi? > That is, is it in the preferences? Yes, it’s the only version I have set up, as... /Users/michaelhendry/lilypond-2.23.12/bin/lilypond …in the “Lilypond versions to use” section. Michael
Re: Alternative to Frescobaldi
Le 02/09/2022 à 22:43, J Martin Rushton a écrit : I've just spent another couple of hours clearing out previous attempts to get Frescobaldi running and attempting to sort out its dependency hell. [...] I'm running AlmaLinux 8.6 if that helps. Would it work for you to us the Frescobaldi Flatpak package? https://flathub.org/apps/details/org.frescobaldi.Frescobaldi
Re: Alternative to Frescobaldi
Well well. Alma Linux is indeed a fine distro, but now I agree with you about dependencies on this linux. Part of the process to install PyQt4 is to install enough of Qt4 to get qmake and that's a nightmare. It's absurdly complicated. And Qt4 has been obsoleted anyway, making this all that much harder. How committed are you to Alma Linux? At this point I would recommend a distro that you don't have to fight with, such as Ubuntu, which has frescobaldi in the repo anyway. If you cannot or will not change from Alma Linux I can push on. Do let me know. Andrew On 3/09/2022 9:37 am, Andrew Bernard wrote: I've come late to this thread, but if you are on Alma Linux I'll run a VM up and figure this for you. Don''t despair. I'm not aware of any 'dependency hell' on several other Linux distros, so let me sort this out and post a set of instructions how to install it.
Re: Alternative to Frescobaldi
On Fri 02 Sep 2022 at 22:46:01 (+0100), J Martin Rushton wrote: > On Fri, 2022-09-02 at 16:17 -0500, David Wright wrote: > > On Fri 02 Sep 2022 at 21:43:25 (+0100), J Martin Rushton wrote: > > > I've just spent another couple of hours clearing out previous > > > attempts > > > to get Frescobaldi running and attempting to sort out its > > > dependency > > > hell. > > > > > > Is there any alternative to Frescobaldi? > > > > An editor (emacs) + LilyPond + PDF viewer (xpdf). > > (My choices in parentheses.) > > > > > I'm running AlmaLinux 8.6 if that helps. > > > > Not a great deal; does it mean that F~ isn't part of the > > distribution? > > > My preference is for vi, but yes, that's what I've been using for the > last couple of years since F~ stopped working. What I miss though is > the back link from the score to the source, and the MIDI playback. 0. Which PDF viewer, and which version of LP? 1. Does the PDF have the textedit URLs? $ grep -a textedit foo.pdf /URI(textedit:///tmp/restpos.ly:4:16:17)>> ……… 2. Does the PDF viewer see them? Look for cursor to change as you move over a notehead. 3. Run the PDF viewer from the commandline. Click on an active notehead. What appears on the console? Anything like: lilypond-invoke-editor (GNU LilyPond) 2.22.0 4. Is lilypond-invoke-editor defined? $ which lilypond-invoke-editor /usr/bin/lilypond-invoke-editor 5. Can lilypond-invoke-editor open a file in an editor, preferably the one you want? $ lilypond-invoke-editor textedit:///tmp/foo.txt:2:4:6 /tmp/foo.txt is the full path to any old text file with more than a couple of lines in it. The cursor should land on the second line, four chars along. How many of those steps work? And at the other end of the process, are you starting vi as a server, with something like: $ gvim $ vim --servername GVIM $ vi --servername gvim (letter-case unimportant), else you might see: E247: no registered server named "GVIM": Send failed. Cheers, David.
Re: Alternative to Frescobaldi
I've come late to this thread, but if you are on Alma Linux I'll run a VM up and figure this for you. Don''t despair. I'm not aware of any 'dependency hell' on several other Linux distros, so let me sort this out and post a set of instructions how to install it. Andrew On 3/09/2022 6:43 am, J Martin Rushton wrote: I've just spent another couple of hours clearing out previous attempts to get Frescobaldi running and attempting to sort out its dependency hell. Is there any alternative to Frescobaldi? I'm running AlmaLinux 8.6 if that helps.
Re: docs about Rest vertical position
Hi Martín, > how do you think that this feature is more useful than \tweaking the y-offset? I don't, personally. =) > If the documentation explains how to move a rest, the officially recommended > way should be using \tweak in my opinion. I agree. I was simply offering a less… um… nuclear doc-revision option. > It's unclear to me what's the use case of the option of adding a note to a > \rest (which in itself sounds like a contradiction). Much like a few other “seems like a great idea when you're a newbie” (which I will refrain from explicitly mentioning here), I believe the main use case is to make it really easy for new users to fix collisions or “hard-code” the rest position, without introducing them to \override-ing and \tweak-ing. > If we follow the WSIWYM paradigm, you can't possibly mean to put a > "note-rest" somewhere. Perhaps not pointing that out or removing the feature > altogether is better in the long run? I agree. Cheers, Kieren
Re: Create 16th-century microtonal accidental
... perfect, exactly what I was looking for, thank you, very much
appreciated! ...
Werner LEMBERG writes:
>> A modern half note, sorry for the unclear terminology. The original
>> notation puts the dot above the (centered) minim stem, but in a modern
>> transcription I would prefer to have the dot above the notehead.
>
> OK.
>
> ```
> {
> \override Script.add-stem-support = ##f
> \override Script.toward-stem-shift = 0
> \override Script.skyline-horizontal-padding = 0
> d'2^.
> }
> ```
>
>
> Werner
Re: Alternative to Frescobaldi
Hello folks, > Le 2 sept. 2022 à 23:46, J Martin Rushton a > écrit : > > On Fri, 2022-09-02 at 16:17 -0500, David Wright wrote: >> On Fri 02 Sep 2022 at 21:43:25 (+0100), J Martin Rushton wrote: >>> I've just spent another couple of hours clearing out previous >>> attempts >>> to get Frescobaldi running and attempting to sort out its >>> dependency >>> hell. >>> >>> Is there any alternative to Frescobaldi? >> >> An editor (emacs) + LilyPond + PDF viewer (xpdf). >> (My choices in parentheses.) >> >>> I'm running AlmaLinux 8.6 if that helps. >> >> Not a great deal; does it mean that F~ isn't part of the >> distribution? >> >> Cheers, >> David. > My preference is for vi, but yes, that's what I've been using for the > last couple of years since F~ stopped working. What I miss though is > the back link from the score to the source, and the MIDI playback. Is it known why F~ stopped working and wasn’t fixed? JM
Re: Alternative to Frescobaldi
On Fri, 2022-09-02 at 16:17 -0500, David Wright wrote: > On Fri 02 Sep 2022 at 21:43:25 (+0100), J Martin Rushton wrote: > > I've just spent another couple of hours clearing out previous > > attempts > > to get Frescobaldi running and attempting to sort out its > > dependency > > hell. > > > > Is there any alternative to Frescobaldi? > > An editor (emacs) + LilyPond + PDF viewer (xpdf). > (My choices in parentheses.) > > > I'm running AlmaLinux 8.6 if that helps. > > Not a great deal; does it mean that F~ isn't part of the > distribution? > > Cheers, > David. My preference is for vi, but yes, that's what I've been using for the last couple of years since F~ stopped working. What I miss though is the back link from the score to the source, and the MIDI playback. -- J Martin Rushton MBCS
Re: docs about Rest vertical position
Am Fr., 2. Sept. 2022 um 21:44 Uhr schrieb Jean Abou Samra : > [...] moving \rest to a footnote or undocumenting it altogether. > Whether its outright removal is desirable is another question. > > This is veering into lilypond-devel territory, maybe we should continue the > discussion there? Alternatively, I'll be happy to continue on a patch > on GitLab :-) > > Cheers, > Jean I never understood why we don't allow \glissando \rest !? Cheers, Harm
Re: Alternative to Frescobaldi
On Fri 02 Sep 2022 at 21:43:25 (+0100), J Martin Rushton wrote: > I've just spent another couple of hours clearing out previous attempts > to get Frescobaldi running and attempting to sort out its dependency > hell. > > Is there any alternative to Frescobaldi? An editor (emacs) + LilyPond + PDF viewer (xpdf). (My choices in parentheses.) > I'm running AlmaLinux 8.6 if that helps. Not a great deal; does it mean that F~ isn't part of the distribution? Cheers, David.
Re: Alternative to Frescobaldi
Hi Martin, that depends on what you consider an alternative to Frescobaldi. Lilypond can be used with any text editor. There is a quite powerful Lilypond module for VSCode, maybe that is something along the lines of what you are looking for? Cheers, Valentin Am Freitag, 2. September 2022, 22:43:25 CEST schrieb J Martin Rushton: > I've just spent another couple of hours clearing out previous attempts > to get Frescobaldi running and attempting to sort out its dependency > hell. > > Is there any alternative to Frescobaldi? > > I'm running AlmaLinux 8.6 if that helps. signature.asc Description: This is a digitally signed message part.
Alternative to Frescobaldi
I've just spent another couple of hours clearing out previous attempts to get Frescobaldi running and attempting to sort out its dependency hell. Is there any alternative to Frescobaldi? I'm running AlmaLinux 8.6 if that helps. -- J Martin Rushton MBCS
Re: docs about Rest vertical position
Well, we're mostly agreeing ;-). I wouldn't support pointing out the downsides
of note+rest as suggested by Kieren nor I'm sure that I agree it's useful to
know about note+rest: if \tweak is the proper way to do it, let's document that
instead.
>
> On Sep 2, 2022 at 9:44 PM, mailto:j...@abou-samra.fr)>
> wrote:
>
>
>
> Le 02/09/2022 à 21:31, Martín Rincón Botero a écrit : > Hi Kieren, > >
> how do you think that this feature is more useful than \tweaking the >
> y-offset? If the documentation explains how to move a rest, the >
> officially recommended way should be using \tweak in my opinion. It's >
> unclear to me what's the use case of the option of adding a note to a >
> \rest (which in itself sounds like a contradiction). If we follow the >
> WSIWYM paradigm, you can't possibly mean to put a "note-rest" > somewhere.
> Perhaps not pointing that out or removing the feature > altogether is
> better in the long run? Reread Kieren's original message; I think you are
> exactly agreeing with him :-) The transposition problem can be worked around
> using \version "2.23.12" untransposable = \withMusicProperty untransposable
> ##t \etc \transpose c f \voices 1,2 << { \untransposable c''8\rest b e' d'
> } \\ { g16^1 f^2 g a } >> but of course, for this sort of use case, \tweak
> Y-offset is better in the first place. I can't think of use cases where \rest
> is really what you want, as opposed to \tweak Y-offset. Unless someone comes
> up with an argument for it, I'd support a patch showing \tweak Y-offset in
> the documentation and moving \rest to a footnote or undocumenting it
> altogether. Whether its outright removal is desirable is another question.
> This is veering into lilypond-devel territory, maybe we should continue the
> discussion there? Alternatively, I'll be happy to continue on a patch on
> GitLab :-) Cheers, Jean
>
>
Re: docs about Rest vertical position
My two cents: Tweaking the position is fine to avoid a collision or to keep a rest about the same “viewing” line then the notes of a phrase But, or better And: When composing; arranging it happens often that a note is skipped (read: turned into a ‘rest’). Think about note patterns what repeat, with small variations. Then the note/rest does the job perfectly. The pattern is kept. The rest is exactly on the place the note would have been. In fact a very well musical solution. Met vriendelijke groet, Eef H.E. Weenink MBA Op 2 sep. 2022 om 21:33 heeft Martín Rincón Botero het volgende geschreven: Hi Kieren, how do you think that this feature is more useful than \tweaking the y-offset? If the documentation explains how to move a rest, the officially recommended way should be using \tweak in my opinion. It's unclear to me what's the use case of the option of adding a note to a \rest (which in itself sounds like a contradiction). If we follow the WSIWYM paradigm, you can't possibly mean to put a "note-rest" somewhere. Perhaps not pointing that out or removing the feature altogether is better in the long run? Martín. On Sep 2, 2022 at 4:27 PM, mailto:kie...@kierenmacmillan.info>> wrote: Hi all, I was answering a user's question on the FB group, and noted that in the docs, we suggest “To explicitly specify a rest’s vertical position, write a note followed by \rest.” While this is a useful thing to know about, I don't personally believe it's a best practice: it mixes content with presentation, it doesn't play well with \transpose, etc. I'm not necessarily suggesting that we avoid pointing out this feature. I'm just wondering if anyone else agrees that we should point out the downsides, and give alternative ways of accomplishing the same task? If so, I can put together some draft verbiage for a discussion starting point. Cheers, Kieren.
Re: docs about Rest vertical position
Le 02/09/2022 à 21:31, Martín Rincón Botero a écrit :
Hi Kieren,
how do you think that this feature is more useful than \tweaking the
y-offset? If the documentation explains how to move a rest, the
officially recommended way should be using \tweak in my opinion. It's
unclear to me what's the use case of the option of adding a note to a
\rest (which in itself sounds like a contradiction). If we follow the
WSIWYM paradigm, you can't possibly mean to put a "note-rest"
somewhere. Perhaps not pointing that out or removing the feature
altogether is better in the long run?
Reread Kieren's original message; I think you are exactly agreeing
with him :-)
The transposition problem can be worked around using
\version "2.23.12"
untransposable = \withMusicProperty untransposable ##t \etc
\transpose c f \voices 1,2 <<
{ \untransposable c''8\rest b e' d' }
\\
{ g16^1 f^2 g a }
>>
but of course, for this sort of use case, \tweak Y-offset is better in
the first place. I can't think of use cases where \rest is really what
you want, as opposed to \tweak Y-offset. Unless someone comes up with
an argument for it, I'd support a patch showing \tweak Y-offset in the
documentation and moving \rest to a footnote or undocumenting it altogether.
Whether its outright removal is desirable is another question.
This is veering into lilypond-devel territory, maybe we should continue the
discussion there? Alternatively, I'll be happy to continue on a patch
on GitLab :-)
Cheers,
Jean
Re: docs about Rest vertical position
Hi Kieren, how do you think that this feature is more useful than \tweaking the y-offset? If the documentation explains how to move a rest, the officially recommended way should be using \tweak in my opinion. It's unclear to me what's the use case of the option of adding a note to a \rest (which in itself sounds like a contradiction). If we follow the WSIWYM paradigm, you can't possibly mean to put a "note-rest" somewhere. Perhaps not pointing that out or removing the feature altogether is better in the long run? Martín. > > On Sep 2, 2022 at 4:27 PM, (mailto:kie...@kierenmacmillan.info)> wrote: > > > > Hi all, I was answering a user's question on the FB group, and noted that in > the docs, we suggest “To explicitly specify a rest’s vertical position, write > a note followed by \rest.” While this is a useful thing to know about, I > don't personally believe it's a best practice: it mixes content with > presentation, it doesn't play well with \transpose, etc. I'm not necessarily > suggesting that we avoid pointing out this feature. I'm just wondering if > anyone else agrees that we should point out the downsides, and give > alternative ways of accomplishing the same task? If so, I can put together > some draft verbiage for a discussion starting point. Cheers, Kieren. > >
Re: Create 16th-century microtonal accidental
> A modern half note, sorry for the unclear terminology. The original
> notation puts the dot above the (centered) minim stem, but in a modern
> transcription I would prefer to have the dot above the notehead.
OK.
```
{
\override Script.add-stem-support = ##f
\override Script.toward-stem-shift = 0
\override Script.skyline-horizontal-padding = 0
d'2^.
}
```
Werner
Re: Create 16th-century microtonal accidental
A modern half note, sorry for the unclear terminology. The original notation puts the dot above the (centered) minim stem, but in a modern transcription I would prefer to have the dot above the notehead. Werner LEMBERG writes: >> Thank you! Is there a way to keep the staccato dot just above the >> notehead also when there is a stem (on a minima for example)? > > A minima? Really? How shall this look like? Contrary to modern > notation, the stems of minimae and friends are horizontally > centered... > > > Werner
Re: Installing Frescobaldi 3.1.3 on Mac with MacOS 12.1
On Fri, Sep 2, 2022 at 12:30 AM Michael Hendry wrote: > > Thanks to Omer and Jean for getting me back on the Frescobaldi road again. > > I’m now able to open, edit and compile lilypond source documents again, but > I’m getting a lot of warnings about deprecated code which I’d like to get rid > of. > > When I attempt to use ‘convert.ly’ (via Frescobaldi’s Tools menu) to update > an affected file, the original lilypond version comes up in the “From > version” box, but the “To version” box is blank. > > If I type 2.23.12 in the "To version” box I get the following... > > Traceback (most recent call last): > File > "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/convert_ly.py", > line 217, in run > AttributeError: 'NoneType' object has no attribute ‘toolcommand' > > …which means nothing to me. > > Any suggestions? Just a guess, but do you have LilyPond 2.23.12 set up in Frescobaldi? That is, is it in the preferences? -- Knute Snortum
Re: docs about Rest vertical position
A little more context:
>“To explicitly specify a rest’s vertical position, write a note followed
> by \rest.”
> While this is a useful thing to know about, I don't personally believe it's a
> best practice: it mixes content with presentation, it doesn't play well with
> \transpose, etc.
Consider, for example, the following two snippets:
\transpose c f \voices 1,2 <<
{ \tweak Y-offset 1 r8 b e' d' }
\\
{ g16^1 f^2 g a }
>>
\transpose c f \voices 1,2 <<
{ c''8\rest b e' d' }
\\
{ g16^1 f^2 g a }
>>
Cheers,
Kieren.
docs about Rest vertical position
Hi all, I was answering a user's question on the FB group, and noted that in the docs, we suggest “To explicitly specify a rest’s vertical position, write a note followed by \rest.” While this is a useful thing to know about, I don't personally believe it's a best practice: it mixes content with presentation, it doesn't play well with \transpose, etc. I'm not necessarily suggesting that we avoid pointing out this feature. I'm just wondering if anyone else agrees that we should point out the downsides, and give alternative ways of accomplishing the same task? If so, I can put together some draft verbiage for a discussion starting point. Cheers, Kieren.
Re: Create 16th-century microtonal accidental
> Thank you! Is there a way to keep the staccato dot just above the > notehead also when there is a stem (on a minima for example)? A minima? Really? How shall this look like? Contrary to modern notation, the stems of minimae and friends are horizontally centered... Werner
Re: Create 16th-century microtonal accidental
Thank you! Is there a way to keep the staccato dot just above the notehead also when there is a stem (on a minima for example)? ``` g2^. ``` Best! Johannes Werner LEMBERG writes: >> To mimic the appearance of this sign I need to place a dot centered >> above the notehead in the next available space (not above the staff >> like articulations, not on staff lines). > > What about a normal staccato point? You can force its direction by > using `^`, for example > > ``` > g\breve^. > ``` > > > Werner
Re: Create 16th-century microtonal accidental
> To mimic the appearance of this sign I need to place a dot centered > above the notehead in the next available space (not above the staff > like articulations, not on staff lines). What about a normal staccato point? You can force its direction by using `^`, for example ``` g\breve^. ``` Werner
Create 16th-century microtonal accidental
Hello! I would like to use Lilypond for a critical edition of Nicola Vicentino's treatise "L'antica musica" (Rome 1555). The original notation uses an unconventional accidental to indicate a pitch modification of a "Diesis" (ca. 1/5 of a whole tone). To mimic the appearance of this sign I need to place a dot centered above the notehead in the next available space (not above the staff like articulations, not on staff lines). I couldn't find a feature that detects the next available space. Do you have recommendations how to implement such a behaviour? Collisions with other noteheads (in chords), fingerings or articulations wont' be an issue since the original notation never uses such things. Examples of the original notation can be found here, see for example fol. 12v (PDF p. 24): http://vmirror.imslp.org/files/imglnks/usimg/9/94/IMSLP114662-PMLP210243-lantica_musica.pdf Thank you! Johannes
Re: Installing Frescobaldi 3.1.3 on Mac with MacOS 12.1
Thanks to Omer and Jean for getting me back on the Frescobaldi road again. I’m now able to open, edit and compile lilypond source documents again, but I’m getting a lot of warnings about deprecated code which I’d like to get rid of. When I attempt to use ‘convert.ly’ (via Frescobaldi’s Tools menu) to update an affected file, the original lilypond version comes up in the “From version” box, but the “To version” box is blank. If I type 2.23.12 in the "To version” box I get the following... Traceback (most recent call last): File "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/convert_ly.py", line 217, in run AttributeError: 'NoneType' object has no attribute ‘toolcommand' …which means nothing to me. Any suggestions? Regards, Michael
