Re: Questions From a New User
MIDI output from LilyPond is usually the way one would be able to listen to their score. While MusicXML can be converted *to* LilyPond, the reverse is not possible to my knowledge. There is an open issue [2] filed requesting a MusicXML backend to LilyPond, which would enable it to output that format. [2]: https://gitlab.com/lilypond/lilypond/-/issues/665 There have been attempts to export lilypond *to* MusicXML: https://github.com/Philomelos/lilypond-ly2musicxml But last commit was 8 years ago I think. Maybe there are more recent attempts going on elsewhere? More usabable is the MusicXML export that is provided by python-ly using the ly command, but it is still quite buggy. https://python-ly.readthedocs.io/en/latest/command.html Frescobaldi uses python-ly and has an "export as MusicXML" option, but you first have to enable experimental features in the preferences to see the option. -- MT
Re: Questions From a New User
Hi Aaron,
Having no prior knowledge of print, please excuse me for asking, but I
take it the "angle brackets" are the < and > symbols? The reason I ask
is because screen readers often read these out as "less" and "greater".
That's one of the things that confused us - the fact that sometimes you
would see braces inside the <<->> sections and vice versa.
So far, we have been using MIDI to hear our scores back, but since MIDI
is an events-only system, does that accurately reflect how the score
looks? For instance, articulations wouldn't be able to be replicated in
MIDI, nor would the tons of different barlines (still another thing that
threw us).
Cheers,
Damien.
On 30/10/2020 02:19 am, Aaron Hill wrote:
On 2020-10-29 6:25 pm, Jenny Suchan wrote:
My name is Jenny Suchan, and I just joined this list yesterday. I am a
totally blind musician seriously pursuing a career in music
composition. After looking into several different score-writing
software, I am now studying LilyPond to see how I could use it to
produce music scores. My friend Damien, another totally blind musician
who I have been working with and who made me aware of this software,
is copied on this message.
Welcome to the Pond.
The topic of LilyPond and Braille has come up before, so you are
certainly not alone. I would recommend reviewing information in the
archives [1].
[1]:
https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=braille&submit=Search%21&idxname=lilypond-user&max=20&result=normal&sort=score
We have been making our way through the Learning Manual and are
struggling with the concepts underlying the construction of chords,
multiple parts, and multiple voices. For example, it isn't clear to us
how information within less-than and greater-than signs and that
within brackets relate to each other. Also, the manual states that
tied notes share the same pitch, so how can two chords be tied
together if only one note is sustained between them? Any additional
tutorials or one-on-one help that anyone can offer would be greatly
appreciated.
Curly braces are used principally to denote sequential music, with
events following one after another. Angle brackets are generally for
simultaneous music, with events occurring at the same time. In
particular, single angle brackets are for chords; double angle brackets
are for grouping together voices or staves of music.
Ties between chords will only apply to notes that are in common.
Consider a tie between a D minor chord and a D major chord. The third
is the only thing that changes, so ties would exist between just the D's
and A's. By placing the tilde outside the chord, you will instruct
LilyPond to automatically tie any notes shared between the two chords.
If you only want to tie specific notes, you may use the tilde inside the
angle brackets after each individual note name.
The following snippet demonstrates both usage patterns. The first
measure is precisely the D minor to D major example I mentioned. The
second measure involves an G major to C major where the common G note is
tied within the chord construct.
BEGIN SNIPPET
\version "2.20.0"
\fixed d' {
| 2 ~
| 2
}
END SNIPPET
Also, is there a way-or a potential way-that LilyPond code can be
converted to MusicXML? It would be very helpful for me to be able to
translate my scores into Braille music, and we both could benefit from
audio feedback regarding our scores.
MIDI output from LilyPond is usually the way one would be able to listen
to their score.
While MusicXML can be converted *to* LilyPond, the reverse is not
possible to my knowledge. There is an open issue [2] filed requesting a
MusicXML backend to LilyPond, which would enable it to output that format.
[2]: https://gitlab.com/lilypond/lilypond/-/issues/665
-- Aaron Hill
Re: Questions From a New User
> [...] I take it the "angle brackets" are the < and > symbols? The > reason I ask is because screen readers often read these out as > "less" and "greater". Yes. The terminology is a bit unfortunate – indeed, “less than” and “greater than” are the correct names for the ASCII characters < and >, respectively. Angle brackets are actually the symbols 〈 and 〉 (Unicode characters U+2329 and U+232A), but this is not what LilyPond uses for its syntax. Werner
Re: Questions From a New User
> Am 30.10.2020 um 12:24 schrieb Damien Garwood : > > So far, we have been using MIDI to hear our scores back, but since MIDI is an > events-only system, does that accurately reflect how the score looks? For > instance, articulations wouldn't be able to be replicated in MIDI, nor would > the tons of different barlines (still another thing that threw us). Hi Damien, you can use \include "articulate.ly" in the header and \articulate in the MIDI section of your score to get *some* articulations hearable. See http://lilypond.org/doc/v2.20/Documentation/notation/the-articulate-script Since that e.g. shortens notes, don’t use it for the printed output! In case you aren’t aware: It generally makes sense to store voices or other parts of music in variables and put them together in a \score. You should use two \score sections, each including only \layout or \midi. Have fun, Hraban
WSL - Visual Studio Code - point and click
Hi I've got WSL running fine with a Debian distro, Lilypond working fine, Visual Studio Code doing it's remote thing and Sumatra picking up all the changes in pdf back on the Windows side. but no point and click. I tried to hack Aaron Hill's answer from a couple of years ago https://www.mail-archive.com/lilypond-user@gnu.org/msg129393.html but no joy (it could be me of course) Anyone out there got a method for Windows 10 64bit and current VSC/WSL2 etc? thanks Damian
Re: WSL - Visual Studio Code - point and click
On 30 October 2020 at 14:34, damianlegassick wrote: Hi I've got WSL running fine with a Debian distro, Lilypond working fine, Visual Studio Code doing it's remote thing and Sumatra picking up all the changes in pdf back on the Windows side. but no point and click. I tried to hack Aaron Hill's answer from a couple of years ago https://www.mail-archive.com/lilypond-user@gnu.org/msg129393.html but no joy (it could be me of course) Anyone out there got a method for Windows 10 64bit and current VSC/WSL2 etc? thanks Damian This is how far I've got: textedit.reg: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Classes\textedit] "URL Protocol"="" @="URL:textedit" [HKEY_CURRENT_USER\Software\Classes\textedit\shell] [HKEY_CURRENT_USER\Software\Classes\textedit\shell\open] [HKEY_CURRENT_USER\Software\Classes\textedit\shell\open\command] @="C:\\Tools\\textedit\\textedit.cmd %1" textedit.cmd: @ECHO OFF SETLOCAL SET CODE=/mnt/c/Users/damia/AppData/Local/Programs/Microsoft\ VS\ Code/bin/code SET URL=vscode://file/`/bin/wslpath -m %%(file)s`:%%(line)s:%%(column)s SET ENV=/usr/bin/env -i LYEDITOR='%CODE% --open-url %URL%' SET CMD=/usr/local/bin/lilypond-invoke-editor %* C:\Windows\System32\wsl.exe %ENV% %CMD%
Re: WSL - Visual Studio Code - point and click
Hi Damian, I know this may not be the answer you are wanting, but given that you have such a lot of heavy machinery on Windows to run LilyPond under Linux, why not simply run Debian or distro of your choice in Virtualbox, and you can even get VSC for Linux if you must. It's very easy to get point and click going in Linux. I am deeply averse to messing with the Windows 10 registry, no matter how clever the hack may be. But my feelings about the registry are not shared by all. I do all my professional work in Virtualbox Linux with Lilypond happily pointing and clicking away for years. On this list some time ago I posted a HOWTO for Ubuntu in this area, and the NR of course has some other useful info for Linux. Andrew On Sat, 31 Oct 2020 at 01:33, damianlegassick wrote: > I've got WSL running fine with a Debian distro, Lilypond working fine, Visual > Studio Code doing it's remote thing and Sumatra picking up all the changes in > pdf back on the Windows side. > > but no point and click. >
Re: WSL - Visual Studio Code - point and click
Hi Andrew I agree completely about registry changes but this one's easily undo-able. I'm just experimenting really - I've got Arch Linux working well now in Virtualbox and Lilypond/Frescobaldi also running well. Damian On 30 October 2020 at 15:15, Andrew Bernard wrote: Hi Damian, I know this may not be the answer you are wanting, but given that you have such a lot of heavy machinery on Windows to run LilyPond under Linux, why not simply run Debian or distro of your choice in Virtualbox, and you can even get VSC for Linux if you must. It's very easy to get point and click going in Linux. I am deeply averse to messing with the Windows 10 registry, no matter how clever the hack may be. But my feelings about the registry are not shared by all. I do all my professional work in Virtualbox Linux with Lilypond happily pointing and clicking away for years. On this list some time ago I posted a HOWTO for Ubuntu in this area, and the NR of course has some other useful info for Linux. Andrew On Sat, 31 Oct 2020 at 01:33, damianlegassick wrote: I've got WSL running fine with a Debian distro, Lilypond working fine, Visual Studio Code doing it's remote thing and Sumatra picking up all the changes in pdf back on the Windows side. but no point and click.
vertical positioning of text spanners and hairpins
[lilypond 2.23.0]
Folks,
how can I make the 'rit.' appear below the hairpin? Any value of
`outside-staff-priority` seems to be ignored...
\new Dynamics {
s2\tweak outside-staff-priority #1000 \<
s2\tweak outside-staff-priority #2000
\tweak bound-details.left.text "rit."
\startTextSpan |
s1\!\stopTextSpan
}
Werner
Re: vertical positioning of text spanners and hairpins
Hi Werner,
> how can I make the 'rit.' appear below the hairpin?
WARNING: HACK AHEAD! SOLUTION MAY NOT WORK BEYOND MWE!!
\new Dynamics {
s2\tweak outside-staff-priority #1000 \<
s2_\tweak outside-staff-priority #2000
\tweak bound-details.left.text "rit."
\startTextSpan |
s1\!\stopTextSpan
}
=)
Cheers,
Kieren.
Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info
Re: vertical positioning of text spanners and hairpins
>> how can I make the 'rit.' appear below the hairpin?
>
> WARNING: HACK AHEAD! SOLUTION MAY NOT WORK BEYOND MWE!!
>
> \new Dynamics {
>s2\tweak outside-staff-priority #1000 \<
>s2_\tweak outside-staff-priority #2000
> \tweak bound-details.left.text "rit."
> \startTextSpan |
>s1\!\stopTextSpan
> }
>
> =)
Pfft :-)
Werner
LSR 1119 Force clef change in alternatives
To the author (Pierre?) of lsr.di.unimi.it/LSR/Item?u=1&id=1119 Many thanks for your snippet, though, please add a description to it. ;) Thanks, Harm
Re: LSR 1119 Force clef change in alternatives
On 2020-10-30 2:19 pm, Thomas Morley wrote: To the author (Pierre?) of lsr.di.unimi.it/LSR/Item?u=1&id=1119 Many thanks for your snippet, though, please add a description to it. ;) Would this work better to avoid the hidden note showing up in MIDI? \grace s4 \once \override Staff.Clef.extra-spacing-width = #'(-1 . 0) \clef bass Seeing as the grace note affects spacing, I added a suitable spacing modifier. -- Aaron Hill
