Re: Displaying a fake key
Hello Valentin, Thanks a lot for the solution! I thought this markup could be placed right inside the staff, but that would be more confusing that useful, so I’ll use that. A nice w-e! JM > Le 11 mars 2022 à 14:04, Valentin Petzel a écrit : > > Hello Jacques, > > I’m not exactly sure what you want, but maybe something like this? > > Cheers, > Valentin > > Am Freitag, 11. März 2022, 11:24:11 CET schrieb Jacques Menu: >> Hello folks, >> >> I’d like to display the following as though it were in C major using >> \naturalizeMusic from the LSR (https://lsr.di.unimi.it/LSR/Item?id=266), >> but still display the original key. >> >> >> Original: >> >> >> >> Naturalized, with \key commented out in the Lily code: >> >> >> >> Is there a way to display the E major key as a markup as a reminder, i.e. >> without it being taken into accout for the notes display? >> >> Thanks for your help! >> >> JM > >
Stem.note-collision-threshold
Hello everyone, I am developing a custom music notation in which distance between notes is different from the standard one. Instead of the tipical distance from C to D of 1, in mine for example this distance is 2/3. This of course causes notes in the same chord that are 1 tone away to overlap. I wanted to fix this by overriding Stem.note-collision-threshold to 1.5 (which would solve it). However, it won't allow to pass float numbers. My question is, shouldn't it allow them? Why not? In any case, does anyone know how might I approach this challenge in a different way? I tried setting a different StaffSpacing but I was unsuccessful as well. Thanks in advance, Robert
Re: DAISY Music Braille Project: Webinar invitation - Introduction to music Braille transcription using the Sao Mai Braille software
Hello Calvin, I don’t know, but you can check that with Sarah, who is in charge of the Webinar setup. I send the invitation privately. JM > Le 3 mars 2022 à 14:08, Calvin Ransom a écrit : > > Hi JM, > Will we be able to watch a recording of the webinar? I'm not able to attend > it live because that's at 3:00AM local time. > > Thanks! > > > Calvin Ransom
Re: Opposite of Laissez Vibrer?
As a repeat is not involved, I didn't look there. I searched for things like "divided tie" or "split tie" (thinking of the part of a tie after a line break, but that's automatic so nothing came up). I'm not aware that there is even a name for this item. I knew about laissez vibrer, so maybe I would have stumbled across an example or snippet in which a usage such as mine was illustrated. But I guess if I had used the index then seeing "tie, from nothing" would have caught my eye - but I didn't, because as usual I did a Google search with "lilypond", which is usually the best way in my experience because it find things in snippets and mailing lists as well. Also, in my case, it's not "from nothing" - it's just deferred for practicality. As always with searching, finding the right terms is crucial! Paul From: Jean Abou Samra To: Paul Hodges , Xavier Scheuer Cc: Lilypond-User Mailing List Sent: 11/03/2022 12:41 Subject: Re: Opposite of Laissez Vibrer? Le 11/03/2022 à 12:38, Paul Hodges a écrit : > Perfect - Thank you! I'd never have thought of looking there Where did you look? As this question comes up fairly frequently, I'd like to know if there is a better structure we can give to the manual on this topic to help people find their way. By the way, note that in the 2.23 documentation, if you look in the index at letter T ... https://lilypond.org/doc/v2.23/Documentation/notation/lilypond-index.html#lilypond-index_cp_letter-T ... you find "tie, from nothing". Thanks, Jean
Re: Bug in articulate.ly
This is a good place to start if you have patched a bug: https://lilypond.org/bug-reports.html or https://lilypond.org/help-us.html -- Knute Snortum On Fri, Mar 11, 2022 at 3:29 AM Martín Rincón Botero wrote: > > Hi all, > > I stumbled into this bug > https://marc.info/?l=lilypond-user=142300498620076=2 which I solved with > this patch https://marc.info/?l=lilypond-user=142477756707049=2 (the line > numbers seem to be different nowadays). I'm using Lilypond 2.22. Is there any > chance that this small patch gets in the standard version of articulate.ly? > That would save many users some time. > > Regards, > Martín. > > -- > www.martinrinconbotero.com
Re: Opposite of Laissez Vibrer?
Hello Paul,
a slightly different approach at this could be something like this.
Cheers,
Valentin
Am Freitag, 11. März 2022, 12:38:31 CET schrieb Paul Hodges:
> Perfect - Thank you! I'd never have thought of looking there
>
>
> I can even use it for selected notes of a chord and control the directions
> individually.
>
>
>
> Paul
>
>
>
> From: Xavier Scheuer
> To: Paul Hodges
> Cc: Lilypond-User Mailing List
> Sent: 11/03/2022 11:12
> Subject: Re: Opposite of Laissez Vibrer?
>
> On Fri, 11 Mar 2022 at 12:06, Paul Hodges wrote:
> > I need to set a passage for piano which consists of an extended melisma
> > all of whose notes tie to a chord at the end. As using actual ties would
> > become an illegible mess, the composer wrote a laissez vibrer after each
> > note, and then short "pickup" ties in front of the chord. I can't see
> > any obvious way to write these, other than writing each as a tie from the
> > original note and then shortening them all with a shape for each one -
> > which would be tedious, messy, and non-robust (as the parameters would
> > need to be adjusted every time the layout of the score was adjusted).
> >
> > Is there a better way?
>
> Hello,
>
>
> \repeatTie ?
>
>
> See NR 1.2.1 Writing rhythms > Ties
>
>
>
> Cheers,
> Xavier
% RETURN DASH DEFINITION FOR SOLID FROM 0 TO s1, DOTTED FROM s1 TO d1 AND FROM d2 TO s2
% AND SOLID FROM s2 to 1
#(define (sdds s1 d1 d2 s2)
(list
(list 0 s1 1 0)
(list s1 d1 0.1 0.3)
(list d2 s2 0.1 0.3)
(list s2 1 1 0)))
% DASH DEFINITION FOR SOLID OF LENGTH s1, DOTTED OF LENGTH d2, NOTHING, DOTTED OF LENGTH d2, SOLID OF LENGTH s2
#(define (lsdds s1 d1 d2 s2)
(sdds s1 (+ s1 d1) (- 1 (+ d2 s2)) (- 1 s2)))
{
\set tieWaitForNote = ##t
c'8\tweak dash-definition #(lsdds 0.13 0.05 0.04 0.15) ~
d'\tweak dash-definition #(lsdds 0.13 0.05 0.05 0.1) ~
e'
f'
g'
f'\tweak dash-definition #(lsdds 0.07 0.06 0.08 0.15) ~
e'\tweak dash-definition #(lsdds 0.1 0.08 0.12 0.17) ~
g'~
|
1
}
signature.asc
Description: This is a digitally signed message part.
Re: Opposite of Laissez Vibrer?
Jean Abou Samra writes: > Le 11/03/2022 à 12:38, Paul Hodges a écrit : >> Perfect - Thank you! I'd never have thought of looking there > > Where did you look? As this question comes up fairly frequently, I'd > like to know if there is a better structure we can give to the manual > on this topic to help people find their way. I am not sure this is entirely a manual problem. Left and right semities are really close relatives while \laissezVibrer and \repeatTie are completely different concepts and contexts and are essentially prime examples of the use of semities, but not really fundamentally defining what they actually are, and if you have need for both, their utterly different naming and manual location essentially doubles the search work to figure out how to use them. -- David Kastrup
Re: Displaying a fake key
Hello Jacques,
I’m not exactly sure what you want, but maybe something like this?
Cheers,
Valentin
Am Freitag, 11. März 2022, 11:24:11 CET schrieb Jacques Menu:
> Hello folks,
>
> I’d like to display the following as though it were in C major using
> \naturalizeMusic from the LSR (https://lsr.di.unimi.it/LSR/Item?id=266),
> but still display the original key.
>
>
> Original:
>
>
>
> Naturalized, with \key commented out in the Lily code:
>
>
>
> Is there a way to display the E major key as a markup as a reminder, i.e.
> without it being taken into accout for the notes display?
>
> Thanks for your help!
>
> JM
{
\mark\markup\score{
\layout {
\override Score.SpacingSpanner.shortest-duration-space = #0
\override Score.SpacingSpanner.packed-spacing = ##t
}
\new Staff \with {
\override StaffSymbol.staff-space = #0.66
fontSize = #(magnification->font-size 0.66)
\omit Clef
\omit TimeSignature
\override KeySignature.space-alist.first-note = #'(fixed-space . 0) % default 2.5
\override LeftEdge.space-alist.key-signature = #'(extra-space . 0.15) % default 0.8
%\override KeySignature.X-extent = #empty-interval
} { \key e\major \grace s }}
cis' d' e' fis'
}
signature.asc
Description: This is a digitally signed message part.
Re: Opposite of Laissez Vibrer?
Le 11/03/2022 à 12:38, Paul Hodges a écrit : Perfect - Thank you! I'd never have thought of looking there Where did you look? As this question comes up fairly frequently, I'd like to know if there is a better structure we can give to the manual on this topic to help people find their way. By the way, note that in the 2.23 documentation, if you look in the index at letter T ... https://lilypond.org/doc/v2.23/Documentation/notation/lilypond-index.html#lilypond-index_cp_letter-T ... you find "tie, from nothing". Thanks, Jean
Re: Accidental Parenthesis
On Fri, 11 Mar 2022 at 13:14, John McWilliam wrote: > > Hi, > > I wonder if anyone can help me code a cautionary accidental, as in (#). If I am working with a key signature in G and write fis no accidental is shown. Sometimes, however, I want to remind myself by forcing an accidental shown inside brackets, (#). How do I do this? Hello, fis? Cautionary accidental: add the question mark ? after the pitch Cf. NR 1.1.1 Writing pitches > Accidentals Cheers, Xavier -- Xavier Scheuer
Re: Accidental Parenthesis
I wonder if anyone can help me code a cautionary accidental, as in (#). If I am working with a key signature in G and write fis no accidental is shown. Sometimes, however, I want to remind myself by forcing an accidental shown inside brackets, (#). How do I do this? Have you even tried to look into the manual? I just searched for "cautionary" and the first sentence that I found is: A cautionary accidental (i.e., an accidental within parentheses) can be obtained by adding the question mark ? after the pitch. Kind regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver
Accidental Parenthesis
Hi, I wonder if anyone can help me code a cautionary accidental, as in (#). If I am working with a key signature in G and write fis no accidental is shown. Sometimes, however, I want to remind myself by forcing an accidental shown inside brackets, (#). How do I do this? John McWilliam Sent from Mail for Windows
Re: Opposite of Laissez Vibrer?
Perfect - Thank you! I'd never have thought of looking there I can even use it for selected notes of a chord and control the directions individually. Paul From: Xavier Scheuer To: Paul Hodges Cc: Lilypond-User Mailing List Sent: 11/03/2022 11:12 Subject: Re: Opposite of Laissez Vibrer? On Fri, 11 Mar 2022 at 12:06, Paul Hodges wrote: > > I need to set a passage for piano which consists of an extended melisma all > of whose notes tie to a chord at the end. As using actual ties would become > an illegible mess, the composer wrote a laissez vibrer after each note, and > then short "pickup" ties in front of the chord. I can't see any obvious way > to write these, other than writing each as a tie from the original note and > then shortening them all with a shape for each one - which would be tedious, > messy, and non-robust (as the parameters would need to be adjusted every time > the layout of the score was adjusted). > > Is there a better way? Hello, \repeatTie ? See NR 1.2.1 Writing rhythms > Ties Cheers, Xavier -- Xavier Scheuer
Bug in articulate.ly
Hi all, I stumbled into this bug https://marc.info/?l=lilypond-user=142300498620076=2 which I solved with this patch https://marc.info/?l=lilypond-user=142477756707049=2 (the line numbers seem to be different nowadays). I'm using Lilypond 2.22. Is there any chance that this small patch gets in the standard version of articulate.ly? That would save many users some time. Regards, Martín. -- www.martinrinconbotero.com
Re: Opposite of Laissez Vibrer?
On Fri, 11 Mar 2022 at 12:06, Paul Hodges wrote: > > I need to set a passage for piano which consists of an extended melisma all of whose notes tie to a chord at the end. As using actual ties would become an illegible mess, the composer wrote a laissez vibrer after each note, and then short "pickup" ties in front of the chord. I can't see any obvious way to write these, other than writing each as a tie from the original note and then shortening them all with a shape for each one - which would be tedious, messy, and non-robust (as the parameters would need to be adjusted every time the layout of the score was adjusted). > > Is there a better way? Hello, \repeatTie ? See NR 1.2.1 Writing rhythms > Ties Cheers, Xavier -- Xavier Scheuer
Opposite of Laissez Vibrer?
I need to set a passage for piano which consists of an extended melisma all of whose notes tie to a chord at the end. As using actual ties would become an illegible mess, the composer wrote a laissez vibrer after each note, and then short "pickup" ties in front of the chord. I can't see any obvious way to write these, other than writing each as a tie from the original note and then shortening them all with a shape for each one - which would be tedious, messy, and non-robust (as the parameters would need to be adjusted every time the layout of the score was adjusted). Is there a better way? Paul
Displaying a fake key
Hello folks, I’d like to display the following as though it were in C major using \naturalizeMusic from the LSR (https://lsr.di.unimi.it/LSR/Item?id=266), but still display the original key. Original: Naturalized, with \key commented out in the Lily code: Is there a way to display the E major key as a markup as a reminder, i.e. without it being taken into accout for the notes display? Thanks for your help! JM
Re: web page comments
Hello Rich, text-to-music toolchain : what is your use case? Creating scores with a text-based tool such as LilyPond, or converting existing texts such as MusicXML or MEI to scores? The DAISY consortium (https://daisy.org) is currently financing two projects aiming at modern, powerful music scores tools for blind users. One team is the MuseScore guys, and the other one is the Sao Mai foundation in Vietnam. The latter will present a first demo of its tool in a webinar to held next March 1 2022 at 10:00-11:30 UTC, I send you the invitation privately. A nice day! JM > Le 10 mars 2022 à 20:04, Jean Abou Samra a écrit : > > Hi Rich, > > Le 10/03/2022 à 19:01, Rich Morin a écrit : >> I just found out about LilyPond today and find it very interesting. >> However, I have a few issues to raise about the web site in general and the >> landing page in particular. >> >> Looking over the site, I ran into a large number of very pretty graphics >> that demonstrate LilyPond's input and output formats. Unfortunately, these >> would be completely inaccessible to blind users. So, I'd like there to be >> some sort of accommodation made to give these users a way to understand what >> is being shown. > > > The thing is, nobody in the current development team is blind. > Thus it is difficult to know how a blind person will perceive > the website. If you have detailed suggestions of how to improve > it, they will be welcome on the bug-lilypond mailing list > (http://lilypond.org/bug-reports.html). Even better, of course, > would be to make the changes yourself and propose them as a > source code patch (see > http://lilypond.org/doc/v2.23/Documentation/contributor/working-with-source-code). > > >> I'd also like the landing page to mention LilyPond's ability to generate >> MIDI files, etc. Looking at the page, one could easily get the impression >> that it is only useful for generating scores. However, it appears that it >> could easily be used as part of a text-to-music toolchain, which could be of >> interest to both blind and sighted users. > > > To be honest, MIDI generation is not really LilyPond's forte. > It works, but the audio rendering is not stellar, and not very > customizable at the moment. Thus I would be a bit hesitating > to put it forward on the website before it improves, as the > graphical output is what LilyPond is most good at. > > >> Finally, although I was able to find some discussion in various mailing >> lists about using braille with LilyPond, I couldn't find any official web >> pages on the topic. This seems like a deficiency that should be addressed. > > > What kind of usage do you mean? LilyPond itself has no dedicated > support for Braille, but some external tools do. CCing Jacques > who will certainly be able to tell you more about that. > > Best, > Jean >
