Re: Drag-and-drop / copy-paste LilyPond submission web site?
Thanks Lukas! JM > Le 27 mai 2020 à 21:35, Lukas-Fabian Moser a écrit : > > Hi Jacques, > >> What is the current status regarding this, i.e. a web site where one can >> drag-and-drop a file or copy-paste LilyPond code to get the PDF or SVG >> score, ready to be downloaded? > > You mean lilybin.com ? It works, but it doesn't have the latest releases. I'm > afraid I forgot who's running it... > > Best > Lukas >
Re: Drag-and-drop / copy-paste LilyPond submission web site?
Hi Jacques, What is the current status regarding this, i.e. a web site where one can drag-and-drop a file or copy-paste LilyPond code to get the PDF or SVG score, ready to be downloaded? You mean lilybin.com ? It works, but it doesn't have the latest releases. I'm afraid I forgot who's running it... Best Lukas
Drag-and-drop / copy-paste LilyPond submission web site?
Hello folks, What is the current status regarding this, i.e. a web site where one can drag-and-drop a file or copy-paste LilyPond code to get the PDF or SVG score, ready to be downloaded? Thanks for your help! JM
Re: Adding a line break on \breve note
Ok, how about:
%%%
\version "2.20.0"
\paper {
#(set-paper-size "a4landscape")
ragged-last = ##f
}
ToninaZalmu = \key c \major
FirstMusicVerse = \relative {
\cadenzaOn
\ToninaZalmu
\once\omit Stem
\tweak duration-log #-1 g'2*3/2
e8 g a4 g \bar "|"
}
VerseOne = \lyricmode {
\set stanza = "1."
\override LyricText.self-alignment-X = #LEFT
"Lorem ipsum dolor sit amet, consectetuer adipiscing elit.+"
}
VerseOneBis = \lyricmode {
\skip 1
\once\override LyricText.self-alignment-X = #RIGHT
\once\override LyricText.extra-offset = #'(1.5 . 0)
"Etiam commodo dui eget wisi. Nunc auctor. Su" --
\override LyricText.self-alignment-X = #LEFT
spen -- di -- sse.
}
VerseTwo = \lyricmode {
\set stanza = "2."
\override LyricText.self-alignment-X = #LEFT
"Lorem ipsum dolor sit amet,+"
}
VerseTwoBis = \lyricmode {
\skip 1
\once\override LyricText.self-alignment-X = #RIGHT
\once\override LyricText.extra-offset = #'(1.5 . 0)
"consectetuer adipiscing elit. Su" --
\override LyricText.self-alignment-X = #LEFT
spen -- di -- sse.
}
\score {
\new Staff = "staff" <<
\clef "treble"
\new Voice = "first" <<
\voiceOne
\FirstMusicVerse
>>
\new Lyrics \lyricsto "first" \VerseOne
\new Lyrics \lyricsto "first" \VerseOneBis
\new Lyrics \lyricsto "first" \VerseTwo
\new Lyrics \lyricsto "first" \VerseTwoBis
>>
\layout {
\context {
\Score
proportionalNotationDuration = #(ly:make-moment 1/16)
}
}
}
%%%
Le mer. 27 mai 2020 à 16:46, Frimlik a écrit :
> Very nice, Schneidy,
>
> the only problem is that I don't want (as I wrote) constant line width,
> e.g.
> the same code without command \override #'(line-width . 66),
> and I also want whole staff to fit in the page - when I delete the
> line-width command, the staff stretches itself too much.
>
> Thanks.
>
>
>
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>
>
Re: Orchestral strings, how to organise score and parts for divisi, solos, desks etc.
On 5/27/20, Lib Lists wrote: > merge the stems so > that the final result looks like one voice. In that case, what you want clearly is \partcombine (\partCombine since 2.21). If you have more than two voices, then you can always apply another \partCombine on top of the first two voices, or use other tricks to deal with the more complex situations. > Finally, adding a \shortInstrumentName in the StaffGroup gives an > error, but the resulting pdf is otherwise correct. instrumentName and shortInstrumentName are both siple property definitions, not variables or functions so the \ is not needed; just instrumentName = "something". Cheers, -- V.
Re: GitLab access
On 5/27/20, Aaron Hill wrote: > I probably could have been (or rather should > be) submitting patches for consideration. Hear hear! But as I said, helping out on the lists is certainly not less worthy as a way of contributing. > I went ahead and linked my GitHub with GitLab, so I am @seraku24 on both > sites. OK, so now you should be able to send a membership request directly from GitLab (I’m CCing Jonas just so he knows whom it’s coming from). Welcome onboard! Cheers, -- V.
Re: Adding a line break on \breve note
Very nice, Schneidy, the only problem is that I don't want (as I wrote) constant line width, e.g. the same code without command \override #'(line-width . 66), and I also want whole staff to fit in the page - when I delete the line-width command, the staff stretches itself too much. Thanks. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
Re: Identify included files
> On 26 May, 2020, at 6:13 PM, David Wright wrote: > > Because of the inability to collate multiple MIDI files, I've always > renamed them. I tee the log into a nonce file, which I grep for their > names in a postprocessing script. (I then trash the log unless there > was an error code, in which case I leave it, renaming it foo.error.) I’m beginning to think that this may be the way to go. The article that Matt linked makes some good points about when dependency files actually need to be updated. I hadn’t considered those points before and they lead to something different from what the GNUMake manual suggests as far as building the dependency files. Implementing those ideas will require me to rework some of what I’ve been doing, but also would open up the possibility to do things like analyze the stderr from the compilation for messages which clearly identify the output. ✝✝ Fr. Samuel, OSB (R. Padraic Springuel) St. Anselm’s Abbey 4501 South Dakota Ave, NE Washington, DC, 20017 202-269-2300 (c) 202-853-7036 PAX ☧ ΧΡΙΣΤΟΣ
Re: GitLab access
On 2020-05-27 1:02 am, Valentin Villenave wrote: On 5/27/20, Aaron Hill wrote: Apologies for hijacking the thread. No apology needed. The link you provided worked for me without needing an account. What level of access are you talking about? Is it something a mere mortal like me (i.e. someone who is not currently a collaborator nor contributor) would need? Well, you most certainly *are* a contributor judging by the number of helpful replies, nifty tricks and brilliant snippets you post each week on the list :-) I guess I see mailing activity as being part of the community but not implying project membership. Granted, I have spent enough time digging about in the source that I probably could have been (or rather should be) submitting patches for consideration. The GitLab pages are publicly accessible (and I strongly hope they’ll remain so); with a GitLab account I *think* there are a few things one can do (post comments? open issues? unsure), but being referenced as a project member gives you more access, to take part in patch reviewing, to be assigned some issues and to be more easily CC-ed in various discussions. I’d be delighted to see you get involved in that sort of stuff, but that’s up to you of course! I went ahead and linked my GitHub with GitLab, so I am @seraku24 on both sites. -- Aaron Hill
Re: Orchestral strings, how to organise score and parts for divisi, solos, desks etc.
On Tue, 26 May 2020 at 20:49, Valentin Villenave wrote: > > On 5/26/20, Lib Lists wrote: > > For example, I'd start with the concertmaster's part, then duplicate > > it and edit it to generate the music the second soloist, then the > > other soloists, then desks, divisi and so on. > > Greetings, > I wouldn’t recommend to “duplicate” any code. As Xavier said, you can > easily use multiple for files to enter variables containing music for > each instrument, then \include these files in a common file to > generate the full score or the set of individual parts. Even if there > are some differences needed, you can do pretty much anything with > different tags and then \keepWithTags or \removeWithTags as needed. > > > The other option would be to create temporary staves when needed, but > > I'm not sure which one is the best strategy. > > Generally speaking, Xavier’s trick is definitely what would be best > suited to that sort of situations. If you need advice on particular > cases, you’ll need to be more specific. Hi, I attach here a modified version of the example linked by Xavier that hopefully clarifies what I mean. Let's say this is for the violin part, not for the score (although the staff names are clearly setup to be used in a score). In the first 10 bars I initially wrote the content on both voices but couldn't find a way to merge the stems so that the final result looks like one voice. My solution was to write the part only to the 'first' first violins. While that works, it's a bit confusing as both violin groups actually play those notes. Moreover, the stem is upward, even though there's no material on another voice and I thought that \skip wouldn't create any output. The second problem (related with the first) is that starting from bar 11 the voices are separated, which is correct. However, in some cases (for example if both voices have same rhythm, no other complexity of any kind, as in this case) I'd want have the voices merged in chords, and just leave 'div.' to mark it. I don't understand how to do it. Finally, adding a \shortInstrumentName in the StaffGroup gives an error, but the resulting pdf is otherwise correct. Thank you for your help! > > Cheers, > -- V. 200519_LILYPOND_Violin_Divisi_Solution_002_001.ly Description: Binary data
Re: registering a composition
On 5/27/20, Francesco Petrogalli wrote: > I am replying here in the middle of the thread, because I decided to > opt for an open source license after reading the considerations in > this email. The source is available here: > https://github.com/fpetrogalli/trr Hi Francesco, That’s excellent news! The score looks great, very groovy; the only thing that’s missing, I think, is the date somewhere (in many countries there are two things required for a copyright to be valid, regardless of which license you may add on top of it: the author’s name, and the publication year). Good work, looking forward to hearing it and reading whatever you guys come up with next! Cheers, -- V.
Re: GitLab access
Am Mittwoch, den 27.05.2020, 10:02 +0200 schrieb Valentin Villenave: > On 5/27/20, Aaron Hill wrote: > > Apologies for hijacking the thread. > > No apology needed. > > > The link you provided worked for me > > without needing an account. What level of access are you talking > > about? > > Is it something a mere mortal like me (i.e. someone who is not > > currently a collaborator nor contributor) would need? > > Well, you most certainly *are* a contributor judging by the number of > helpful replies, nifty tricks and brilliant snippets you post each > week on the list :-) > The GitLab pages are publicly accessible (and I strongly hope they’ll > remain so); with a GitLab account I *think* there are a few things > one > can do (post comments? open issues? unsure), Yes, that's what you can do as a public visitor of a repository on these platforms. but being referenced as a > project member gives you more access, to take part in patch > reviewing, > to be assigned some issues and to be more easily CC-ed in various > discussions. If as a public member (i.e. with "only" a Gitlab account) you open an issue or comment on an issue/MR you will automatically be notified about activity on that issue (if you don't disable this in your account settings) too. It's also possible to @mention any username, regardless of their status in a team. Urs > I’d be delighted to see you get involved in that sort of > stuff, but that’s up to you of course! > > Cheers, > -- V. >
Re: GitLab access
On 5/27/20, Aaron Hill wrote: > Apologies for hijacking the thread. No apology needed. > The link you provided worked for me > without needing an account. What level of access are you talking about? > Is it something a mere mortal like me (i.e. someone who is not > currently a collaborator nor contributor) would need? Well, you most certainly *are* a contributor judging by the number of helpful replies, nifty tricks and brilliant snippets you post each week on the list :-) The GitLab pages are publicly accessible (and I strongly hope they’ll remain so); with a GitLab account I *think* there are a few things one can do (post comments? open issues? unsure), but being referenced as a project member gives you more access, to take part in patch reviewing, to be assigned some issues and to be more easily CC-ed in various discussions. I’d be delighted to see you get involved in that sort of stuff, but that’s up to you of course! Cheers, -- V.
