Re: Boxed Markup as a Whole?
Hi Ben,
SoundsFromSound wrote
> I can't figure out how to box marked-up notes as one unit.
you can use a whole score as markup, so as a point to start, how about:
%---
\version "2.19.81"
\header {
title = "Example"
}
\relative c'
{
c1 c1^\markup \box {
\score {
{
\stopStaff
d'4 d'8 d'
}
\layout {
\context {
\Staff
\remove "Clef_engraver"
\remove "Time_signature_engraver"
}
}
}
} c1 c c c c c
}
%---
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Boxed Markup as a Whole?
Hello,
I am stumped on how to enclose these markup noteheads in one box around
them all? I can only seem to get them individually boxed. In the past, I
have only had to box text markup before, and that's about it. So I can't
figure out how to box marked-up notes as one unit. (see attached)
Also, how can I beam these eighth notes together in the markup? Is this
possible?
Thank you!
(http://lilypond.org/doc/v2.19/Documentation/notation/music)
%%
\version "2.19.81"
\header {
title = "Example"
}
\relative c'
{ c1 c^\markup {
% how can I beam these 8th notes as well as box them as a unit?
\note #"4" #1
\hspace #0.75
\note #"8" #1
\note #"8" #1
} c c c c c c }
\paper {
markup-system-spacing.minimum-distance = 10
markup-system-spacing.basic-distance = 15
ragged-right = ##f
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Some openLilyLib packages/modules open for testing
Hi Urs, I've been looking at the Latex integration (lycritrprt) but I'm afraid it's a bit over my head. I'd need a couple of pointers into making it work before I could play with it and test it. Craig On Sat, 14 Jul 2018 at 09:00, Craig Dabelstein wrote: > Hi Urs, > > Just confirming, as you've discovered, that compiling is lots slower. > > Craig > > > On Sat, 14 Jul 2018 at 08:04, Craig Dabelstein > wrote: > >> Hi Urs, >> >> I've been converting one of my old projects to the new versions to test >> for you and so far it has all worked perfectly. You are a genius! >> >> I haven't got to the Latex integration yet (so please don't delete the >> temp-print-message branch of scholarly just yet!) >> >> All the best, >> >> Craig >> >> >> On Sat, 14 Jul 2018 at 01:59, Urs Liska wrote: >> >>> As suspected the post below wasn't delivered (at least not yet) due to >>> the large attachments. >>> >>> The two files mentioned in the text can temporarily be downloaded from >>> >>> https://cloud.ursliska.de/s/bhN8Kd5MxdgjAea and >>> https://cloud.ursliska.de/s/0LRvGdvL4azL4Za >>> >>> Am 13.07.2018 um 17:31 schrieb Urs Liska: >>> >>> Hi, >>> >>> I noticed that over time openLilyLib pops up more and more on the lists, >>> but mostly as a sort of dubious secret toolkit which only a few illuminati >>> know about and whose purpose and potential isn't obvious to everyone else. >>> >>> In recent weeks (as you'll have noticed) I had the wonderful opportunity >>> to work on it on a partially paid basis: I had to implement some >>> functionality and was in essence paid to work on that for 7x8 hours. What >>> had to be created amounted to "half" an openLilyLib package, so I decided >>> to aim at the whole thing, working of course more than these seven full >>> days but also achieving substantially more. But maybe most important is >>> that I managed to write comprehensive manuals along the way. They are >>> authored in Markdown (which is good) but so far only work in a >>> Markdown=>Pandoc=>LuaLaTeX=>PDF chain (which is less good because it should >>> also be possible to produce HTML sites). But they do exist, and if the list >>> rules allow you will see them attached to this post. >>> >>> I would like to take this as an opportunity to "announce" openLilyLib >>> and open it up for a more broad testing. Jan-Peter's comment made me >>> realize that it's high time to do so since as far as I know anybody who has >>> plunged into using it wouldn't want to live without anymore, and so it >>> should finally become somewhat more public - also hoping to get some more >>> contributions back in return with the goal of moving towards something that >>> can actually be "released". >>> >>> >>> What "is" openLilyLib? >>> >>> openLilyLib serves two independent goals: On the one hand it is a >>> platform for providing "packages" that extend LilyPond's functionality by >>> specific purposes (e.g. "managing breaks", "grid-based approach to managing >>> music", "comtemporary wind notation" (fictional) or similar). On the other >>> hand it provides numerous little building-blocks that can be used to >>> modularize the development of advanced functionality. Which is basically a >>> side-effect of the first goal. >>> >>> How is it structured? >>> >>> openLilyLib is a collection of repositories maintained on Github, but >>> anyone could also keep private repositories as openLilyLib packages. The >>> core package is oll-core (https://github.com/openlilylib/oll-core) that >>> provides the technical infrastructure. Some information on how to install >>> oll-core and other packages can be found temporarily on the Wiki page >>> https://github.com/openlilylib/oll-core/wiki. One of the next tasks >>> will be to also write an oll-core manual, but I had to decide to do other >>> things first. >>> >>> What new stuff is now available? >>> >>> I have worked on four modules (a package may contain modules with more >>> specific functionality): >>> >>>- stylesheets.span >>>\tagSpan, a function to tag music "as something" and providing an >>>interface to styling the music >>>- scholarly.editorial-markup >>>\editorialMarkup, a wrapper around \tagSpan, specifically designed >>>for use in scholarly editions, modeled after parts of MEI >>>- scholarly.choice >>>\choice, giving the possibility to encode alternative versions of >>>some music, annotating it and choosing the music to be engraved >>>- scholarly.annotate >>>This has been around for some years now and can be used for >>>maintaining a critical commentary directly within and musically linked to >>>the score document. The code has been thoroughly reviewed and integrated >>>with the above three modules. >>>I have also newly created a (Lua)LaTeX package that is fine-tuned to >>>typeset critical reports from annotate's output. But this is *completely* >>>undocumented so far and wouldn't lend itself to being reviewed right now. >>>But anyone
Re: Some openLilyLib packages/modules open for testing
Hi Urs, Just confirming, as you've discovered, that compiling is lots slower. Craig On Sat, 14 Jul 2018 at 08:04, Craig Dabelstein wrote: > Hi Urs, > > I've been converting one of my old projects to the new versions to test > for you and so far it has all worked perfectly. You are a genius! > > I haven't got to the Latex integration yet (so please don't delete the > temp-print-message branch of scholarly just yet!) > > All the best, > > Craig > > > On Sat, 14 Jul 2018 at 01:59, Urs Liska wrote: > >> As suspected the post below wasn't delivered (at least not yet) due to >> the large attachments. >> >> The two files mentioned in the text can temporarily be downloaded from >> >> https://cloud.ursliska.de/s/bhN8Kd5MxdgjAea and >> https://cloud.ursliska.de/s/0LRvGdvL4azL4Za >> >> Am 13.07.2018 um 17:31 schrieb Urs Liska: >> >> Hi, >> >> I noticed that over time openLilyLib pops up more and more on the lists, >> but mostly as a sort of dubious secret toolkit which only a few illuminati >> know about and whose purpose and potential isn't obvious to everyone else. >> >> In recent weeks (as you'll have noticed) I had the wonderful opportunity >> to work on it on a partially paid basis: I had to implement some >> functionality and was in essence paid to work on that for 7x8 hours. What >> had to be created amounted to "half" an openLilyLib package, so I decided >> to aim at the whole thing, working of course more than these seven full >> days but also achieving substantially more. But maybe most important is >> that I managed to write comprehensive manuals along the way. They are >> authored in Markdown (which is good) but so far only work in a >> Markdown=>Pandoc=>LuaLaTeX=>PDF chain (which is less good because it should >> also be possible to produce HTML sites). But they do exist, and if the list >> rules allow you will see them attached to this post. >> >> I would like to take this as an opportunity to "announce" openLilyLib and >> open it up for a more broad testing. Jan-Peter's comment made me realize >> that it's high time to do so since as far as I know anybody who has plunged >> into using it wouldn't want to live without anymore, and so it should >> finally become somewhat more public - also hoping to get some more >> contributions back in return with the goal of moving towards something that >> can actually be "released". >> >> >> What "is" openLilyLib? >> >> openLilyLib serves two independent goals: On the one hand it is a >> platform for providing "packages" that extend LilyPond's functionality by >> specific purposes (e.g. "managing breaks", "grid-based approach to managing >> music", "comtemporary wind notation" (fictional) or similar). On the other >> hand it provides numerous little building-blocks that can be used to >> modularize the development of advanced functionality. Which is basically a >> side-effect of the first goal. >> >> How is it structured? >> >> openLilyLib is a collection of repositories maintained on Github, but >> anyone could also keep private repositories as openLilyLib packages. The >> core package is oll-core (https://github.com/openlilylib/oll-core) that >> provides the technical infrastructure. Some information on how to install >> oll-core and other packages can be found temporarily on the Wiki page >> https://github.com/openlilylib/oll-core/wiki. One of the next tasks will >> be to also write an oll-core manual, but I had to decide to do other things >> first. >> >> What new stuff is now available? >> >> I have worked on four modules (a package may contain modules with more >> specific functionality): >> >>- stylesheets.span >>\tagSpan, a function to tag music "as something" and providing an >>interface to styling the music >>- scholarly.editorial-markup >>\editorialMarkup, a wrapper around \tagSpan, specifically designed >>for use in scholarly editions, modeled after parts of MEI >>- scholarly.choice >>\choice, giving the possibility to encode alternative versions of >>some music, annotating it and choosing the music to be engraved >>- scholarly.annotate >>This has been around for some years now and can be used for >>maintaining a critical commentary directly within and musically linked to >>the score document. The code has been thoroughly reviewed and integrated >>with the above three modules. >>I have also newly created a (Lua)LaTeX package that is fine-tuned to >>typeset critical reports from annotate's output. But this is *completely* >>undocumented so far and wouldn't lend itself to being reviewed right now. >>But anyone interested may have a look at >>https://github.com/uliska/lycritrprt as well. >> >> I would love to get some feedback based on the manuals and on the code. >> All the examples in the manuals are directly linked from example files in >> the repositories. >> >> How to get them? As described on the Wiki page one needs the repositories >> of oll-core, stylesheets and
Re: Some openLilyLib packages/modules open for testing
Hi Urs, I've been converting one of my old projects to the new versions to test for you and so far it has all worked perfectly. You are a genius! I haven't got to the Latex integration yet (so please don't delete the temp-print-message branch of scholarly just yet!) All the best, Craig On Sat, 14 Jul 2018 at 01:59, Urs Liska wrote: > As suspected the post below wasn't delivered (at least not yet) due to the > large attachments. > > The two files mentioned in the text can temporarily be downloaded from > > https://cloud.ursliska.de/s/bhN8Kd5MxdgjAea and > https://cloud.ursliska.de/s/0LRvGdvL4azL4Za > > Am 13.07.2018 um 17:31 schrieb Urs Liska: > > Hi, > > I noticed that over time openLilyLib pops up more and more on the lists, > but mostly as a sort of dubious secret toolkit which only a few illuminati > know about and whose purpose and potential isn't obvious to everyone else. > > In recent weeks (as you'll have noticed) I had the wonderful opportunity > to work on it on a partially paid basis: I had to implement some > functionality and was in essence paid to work on that for 7x8 hours. What > had to be created amounted to "half" an openLilyLib package, so I decided > to aim at the whole thing, working of course more than these seven full > days but also achieving substantially more. But maybe most important is > that I managed to write comprehensive manuals along the way. They are > authored in Markdown (which is good) but so far only work in a > Markdown=>Pandoc=>LuaLaTeX=>PDF chain (which is less good because it should > also be possible to produce HTML sites). But they do exist, and if the list > rules allow you will see them attached to this post. > > I would like to take this as an opportunity to "announce" openLilyLib and > open it up for a more broad testing. Jan-Peter's comment made me realize > that it's high time to do so since as far as I know anybody who has plunged > into using it wouldn't want to live without anymore, and so it should > finally become somewhat more public - also hoping to get some more > contributions back in return with the goal of moving towards something that > can actually be "released". > > > What "is" openLilyLib? > > openLilyLib serves two independent goals: On the one hand it is a platform > for providing "packages" that extend LilyPond's functionality by specific > purposes (e.g. "managing breaks", "grid-based approach to managing music", > "comtemporary wind notation" (fictional) or similar). On the other hand it > provides numerous little building-blocks that can be used to modularize the > development of advanced functionality. Which is basically a side-effect of > the first goal. > > How is it structured? > > openLilyLib is a collection of repositories maintained on Github, but > anyone could also keep private repositories as openLilyLib packages. The > core package is oll-core (https://github.com/openlilylib/oll-core) that > provides the technical infrastructure. Some information on how to install > oll-core and other packages can be found temporarily on the Wiki page > https://github.com/openlilylib/oll-core/wiki. One of the next tasks will > be to also write an oll-core manual, but I had to decide to do other things > first. > > What new stuff is now available? > > I have worked on four modules (a package may contain modules with more > specific functionality): > >- stylesheets.span >\tagSpan, a function to tag music "as something" and providing an >interface to styling the music >- scholarly.editorial-markup >\editorialMarkup, a wrapper around \tagSpan, specifically designed for >use in scholarly editions, modeled after parts of MEI >- scholarly.choice >\choice, giving the possibility to encode alternative versions of some >music, annotating it and choosing the music to be engraved >- scholarly.annotate >This has been around for some years now and can be used for >maintaining a critical commentary directly within and musically linked to >the score document. The code has been thoroughly reviewed and integrated >with the above three modules. >I have also newly created a (Lua)LaTeX package that is fine-tuned to >typeset critical reports from annotate's output. But this is *completely* >undocumented so far and wouldn't lend itself to being reviewed right now. >But anyone interested may have a look at >https://github.com/uliska/lycritrprt as well. > > I would love to get some feedback based on the manuals and on the code. > All the examples in the manuals are directly linked from example files in > the repositories. > > How to get them? As described on the Wiki page one needs the repositories > of oll-core, stylesheets and scholarly within a common root directory and > add that to LilyPond's include path. > > The repositories are at https://github.com/openlilylib/oll-core, > https://github.com/openlilylib/scholarly and > https://github.com/openlilylib/stylesheets. People who can
Re: Partcombine not working for orchestral parts?
Hi Ben, > I probably confused you with my wording, sorry! I just meant it's above the > staff when it's supposed to be (in rare situations where dynamics are > technically different between the same instrument parts)...and then it's > below for the part 'extraction' single staff file. ;) Right? Correct! In the score: dynamics unique to Flute 1 appear above the staff, dynamics unique to Flute 2 appear below the staff, and shared dynamics appear [once only] below the score; in the parts: dynamics appear below the staff. Magic. =) K. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Software playing lilypond's music sheets
Hi Richard and Martin
@Richard:
the reason it failed to compile for you is because I messed up the
Makefile. It is fixed now. Lilydumper compiles just fine with g++-6
and g++-7. You can try again if you want.
@Martin:
Sadly since I use debian and didn't get much time for the packaging,
this was kind of something I was expecting to be honest. Looking at
the error message your sent, there are two issues. One is that
QT_HOST_DATA and QMAKE_SPEC are not found. The "build system" uses
qmake to determine where those libraries are installed and
automatically configure things for you. Can you check what does `qmake
-query` prints on your machine? Maybe you simply don't even need that
on fedora. You can try to edit the script in
https://github.com/s-d-m/lilyplayer/blob/master/src/configure and
comment line 56 (the one which prints
${QT_HOST_DATA}/mkspecs/${QMAKE_SPEC} and see if that works?
The other issue is that it seems some options I were using when
compiling are only available for release build, and ... I'm left
wondering how come on debian it compiled just fine for debug builds.
For that second issue you can try compiling using `make BUILD=release`
or simply update your clone from github as I just fixed that
I wanted to install Fedora on a virtualbox to see what would be the
proper fix, but sadly I got hit virtualbox not launching as described
http://linux.debian.bugs.rc.narkive.com/uLBOQlPv/processed-re-virtualbox-fails-to-start-vm-verr-ldrelf-relocation-not-supported
If some of you wants to help on the packaging side of things (someone
even asked me about windows binaries), or take over the project,
please let me know as I don't plan to spend much more time on it.
Kindest regards
On 13/07/2018, Richard Shann wrote:
> On Fri, 2018-07-13 at 09:39 +0200, Samuel DA MOTA wrote:
>> Hi Martin,
>>
>> Thanks for the feedback.
>>
>> Unfortunately since it always was a side project I didn't get much
>> time to polish it like I wanted. In any case, feel free to clone it
>> and improve upon.
>>
>> I kept the build system simple on purpose so that fixing these issues
>> shouldn't be too hard. Had I more time I would have used Meson.
>>
>> Out of curiosity, what is the error you get?
>
> I, too, couldn't make lilydumper on Debian 9.3 (stretch) with
> make
> make -C ./src "lilydumper"
> make[1]: Entering directory '/home/rshann/lilydumper/src'
> make[1]: *** No rule to make target 'lilydumper'. Stop.
>
> but then g++-8 is not available in Debian Stretch it seems ...
>
> Richard Shann
>
>> Cheers
>>
>> On 13/07/2018, Martin Tarenskeen wrote:
>> >
>> >
>> > On Thu, 12 Jul 2018, Samuel DA MOTA wrote:
>> >
>> > > Hi everyone!
>> > >
>> > > I wrote a software a while ago that would play a music sheet
>> > > generated
>> > > by lilypond. It shows the music sheet and follows it with a
>> > > cursor. I
>> > > made a video to demo the end-result. You can watch it at
>> > > https://s-d-m.github.io/lilydumper/intro_assets/lilyplayer-demo.w
>> > > ebm
>> >
>> > Wow. I'm impressed. This is something that I could use!
>> > I downloaded the sources from GitHub but was not able to compile
>> > succesfully (yet). I'm on Linux Fedora 28.
>> >
>> > I hope a userfriendly distribution of the tools will be available
>> > one day.
>> > Or a Makefile that works on my system.
>> >
>> > If anyone has succesfully compiled these tools on a Fedora system
>> > please
>> > share what additional libraries, steps or patches were required.
>> >
>> > --
>> >
>> > MT
>> >
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
On 7/13/2018 1:37 PM, Kieren MacMillan wrote:
Hi Ben,
You're absolutely right. Wow. I just tried it with the example I gave earlier
w/ the two flutes. Sure enough, the pp dynamic is above the staff for the
full score but both pp are below for Flute 1 and Flute 2 separately.
Hmmm… It should appear below the staff in all cases, no? The only "magic"
should be that it only appears once in the score (but still below the staff). Please post
MWE so we can double-check.
I probably confused you with my wording, sorry! I just meant it's above
the staff when it's /supposed/ to be (in rare situations where dynamics
are technically different between the same instrument parts)...and then
it's below for the part 'extraction' single staff file. ;) Right?
(see attached)
\version "2.19.81"
fluteone =
\relative { e'4\ff( f g a) | \once \partcombineApart r4 f4 g f | c'2~\pp
c2 | f8 f e e f r f f |r1 | f4 g g g | c c c }
flutetwo =
\relative { c'2\p( d) e f r4 e r g c2 c2 c,4 c c c r1 c''4 c c }
\new Staff \with {
instrumentName = #"Flute 1.2"
shortInstrumentName = #"Fl. "
soloText = "1."
soloIIText = "2."
}
\partcombine \fluteone \flutetwo
\new Staff
\fluteone
\new Staff
\flutetwo
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
Hi Ben, > You're absolutely right. Wow. I just tried it with the example I gave earlier > w/ the two flutes. Sure enough, the pp dynamic is above the staff for the > full score but both pp are below for Flute 1 and Flute 2 separately. Hmmm… It should appear below the staff in all cases, no? The only "magic" should be that it only appears once in the score (but still below the staff). Please post MWE so we can double-check. > I keep finding these ways that LilyPond is just so powerful So true! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
On 7/13/2018 1:00 PM, Kieren MacMillan wrote: Hi Ben, If you have a full orchestra score, with Flutes 1 & 2 on one staff in the score and also separated out parts via partcombine, where/how do you place a dynamic then so that it applies to both locations without redundant markings? The part-combiner actually does a great job of merging identical dynamics — no need (usually!) to do any extra work. Specifically: I'm confused how to relocate the Flute 2's above-the-staff-dynamic in the full score to the normal under-the-staff location for Flute 2's part, single staff page. Do I need to input each dynamic mark twice? No. The part-combiner *should* do that correctly (as I recall, from my rather heavy work with it several years ago). You're absolutely right. Wow. I just tried it with the example I gave earlier w/ the two flutes. Sure enough, the pp dynamic is above the staff for the full score but both pp are below for Flute 1 and Flute 2 separately. I keep finding these ways that LilyPond is just so powerful - my mind can only explode so many times haha thanks so much for this! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
Hi Ben, > If you have a full orchestra score, with Flutes 1 & 2 on one staff in the > score and also separated out parts via partcombine, where/how do you place a > dynamic then so that it applies to both locations without redundant markings? The part-combiner actually does a great job of merging identical dynamics — no need (usually!) to do any extra work. > Specifically: I'm confused how to relocate the Flute 2's > above-the-staff-dynamic in the full score to the normal under-the-staff > location for Flute 2's part, single staff page. Do I need to input each > dynamic mark twice? No. The part-combiner *should* do that correctly (as I recall, from my rather heavy work with it several years ago). Hope that helps! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
On 7/13/2018 10:52 AM, Kieren MacMillan wrote: So what's the best way to do this in your opinion? Should every instance of brief rests like this in one part but not the other be prefaced with "once...apart" If I recall correctly, I settled on the fact that part combinations (and the related visuals/texts) are PRESENTATION layer, and not CONTENT layer… so I used the edition-engraver to "inject" commands and markups as desired. (I’ve set aside some time in late August to deal with some long-standing Lilypond-related initiatives; I’ll tack the part-combiner on to that list and get back to you when I’ve put together a "best practices" demo. I know that doesn’t help you now… sorry!) Best, Kieren. I see. That makes me think though, about this injection stuff, vs tags or something... Question then: If you have a full orchestra score, with Flutes 1 & 2 on one staff in the score and also separated out parts via partcombine, where/how do you place a dynamic then so that it applies to both locations without *redundant* markings? I'm not speaking about the obvious dynamic marking above the staff for Flute 2, and the 'normal' location under the staff for Flute 1, that's a given - I mean in the full score there "usually" is just one dynamic marking /under/ the flute staff which implies the flutes (plural) take that mark. So do you use the edition engrave to "hide" these duplicate above the staff dynamics in the full score but then somehow re-locate them to under the staff in the part (under the staff, of course since there is only one voice/instrument on the part) :) Specifically: I'm confused how to relocate the Flute 2's above-the-staff-dynamic in the full score to the normal under-the-staff location for Flute 2's part, single staff page. Do I need to input each dynamic mark twice? I hope you follow what I mean. Sorry long week for me! Thank you so much! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Some openLilyLib packages/modules open for testing
As suspected the post below wasn't delivered (at least not yet) due to the large attachments. The two files mentioned in the text can temporarily be downloaded from https://cloud.ursliska.de/s/bhN8Kd5MxdgjAea and https://cloud.ursliska.de/s/0LRvGdvL4azL4Za Am 13.07.2018 um 17:31 schrieb Urs Liska: Hi, I noticed that over time openLilyLib pops up more and more on the lists, but mostly as a sort of dubious secret toolkit which only a few illuminati know about and whose purpose and potential isn't obvious to everyone else. In recent weeks (as you'll have noticed) I had the wonderful opportunity to work on it on a partially paid basis: I had to implement some functionality and was in essence paid to work on that for 7x8 hours. What had to be created amounted to "half" an openLilyLib package, so I decided to aim at the whole thing, working of course more than these seven full days but also achieving substantially more. But maybe most important is that I managed to write comprehensive manuals along the way. They are authored in Markdown (which is good) but so far only work in a Markdown=>Pandoc=>LuaLaTeX=>PDF chain (which is less good because it should also be possible to produce HTML sites). But they do exist, and if the list rules allow you will see them attached to this post. I would like to take this as an opportunity to "announce" openLilyLib and open it up for a more broad testing. Jan-Peter's comment made me realize that it's high time to do so since as far as I know anybody who has plunged into using it wouldn't want to live without anymore, and so it should finally become somewhat more public - also hoping to get some more contributions back in return with the goal of moving towards something that can actually be "released". What "is" openLilyLib? openLilyLib serves two independent goals: On the one hand it is a platform for providing "packages" that extend LilyPond's functionality by specific purposes (e.g. "managing breaks", "grid-based approach to managing music", "comtemporary wind notation" (fictional) or similar). On the other hand it provides numerous little building-blocks that can be used to modularize the development of advanced functionality. Which is basically a side-effect of the first goal. How is it structured? openLilyLib is a collection of repositories maintained on Github, but anyone could also keep private repositories as openLilyLib packages. The core package is oll-core (https://github.com/openlilylib/oll-core) that provides the technical infrastructure. Some information on how to install oll-core and other packages can be found temporarily on the Wiki page https://github.com/openlilylib/oll-core/wiki. One of the next tasks will be to also write an oll-core manual, but I had to decide to do other things first. What new stuff is now available? I have worked on four modules (a package may contain modules with more specific functionality): * stylesheets.span \tagSpan, a function to tag music "as something" and providing an interface to styling the music * scholarly.editorial-markup \editorialMarkup, a wrapper around \tagSpan, specifically designed for use in scholarly editions, modeled after parts of MEI * scholarly.choice \choice, giving the possibility to encode alternative versions of some music, annotating it and choosing the music to be engraved * scholarly.annotate This has been around for some years now and can be used for maintaining a critical commentary directly within and musically linked to the score document. The code has been thoroughly reviewed and integrated with the above three modules. I have also newly created a (Lua)LaTeX package that is fine-tuned to typeset critical reports from annotate's output. But this is *completely* undocumented so far and wouldn't lend itself to being reviewed right now. But anyone interested may have a look at https://github.com/uliska/lycritrprt as well. I would love to get some feedback based on the manuals and on the code. All the examples in the manuals are directly linked from example files in the repositories. How to get them? As described on the Wiki page one needs the repositories of oll-core, stylesheets and scholarly within a common root directory and add that to LilyPond's include path. The repositories are at https://github.com/openlilylib/oll-core, https://github.com/openlilylib/scholarly and https://github.com/openlilylib/stylesheets. People who can clone these with Git should checkout the v0.6.0 branch for scholarly, people who want to *download* should do so from exactly this page: https://github.com/openlilylib/scholarly/tree/v0.6.0 (the gree button in the upper right area of the screen). Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hacker Warning
On 7/13/2018 10:27 AM, Michael Hendry wrote: I have taken steps to improve the security of my passwords. I'd be lost without a password manager. Quite a few to choose from, I can think of 1Password, Dashlane, Encryptr, KeePass, LastPass... various architectures and business models among them. Managing many hundreds of unique random passwords used from various locations and devices gets pretty impractical any other way. -- Karlin High Missouri, USA ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hacker Warning
On 13/07/18 11:40, Michael Hendry wrote: I’ve recently received a message from a hacker who told me he knew my password (and quoted it correctly) Michael, Your e-mail address is listed on https://haveibeenpwned.com/ so it's possible they have obtained your details from one of these breaches. Joshua. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hacker Warning
> On 13 Jul 2018, at 12:12, Simon Albrecht wrote: > >> On 13.07.2018 - 12:42, Michael Hendry wrote: >> >> >> I’ve recently received a message from a hacker who told me he knew my >> password (and quoted it correctly), demanding money in bitcoin for not >> forwarding details of my recent visit to a porn website to all my contacts. >>> >>> I had been using nabble to access the list - I've never accessed a porn >>> website. >>> >>> Firefox had warned me that the nabble site wasn’t secure when I logged in. >>> >>> I’ve deleted my nabble account, hence a couple of my messages to the group >>> have been deleted. > > They may have been deleted from Nabble, but there are two other independent > archives of all posts to the list. One can be found via the link below. > > Also, this isn't the only reason not to use Nabble: for example, it has an > idiosyncratic handling of attachments that simply don't appear to many > recipients etc. > > Best, Simon > > >>> lilypond-user mailing list >>> lilypond-user@gnu.org >>> https://lists.gnu.org/mailman/listinfo/lilypond-user >> Thanks. I don’t think my contributions will be greatly missed! Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hacker Warning
> On 13 Jul 2018, at 12:34, David Kastrup wrote: > > Michael Hendry writes: > >> I’ve recently received a message from a hacker who told me he knew my >> password (and quoted it correctly), demanding money in bitcoin for not >> forwarding details of my recent visit to a porn website to all my >> contacts. > > You make it sound like you use only one password for everything. That was the way the hacker put it - without specifying what site the password related to, but I worked backwards from the quoted password. > A bad > idea. Indeed. I don’t think I had used nabble since 2015, and I did have one other website on which I had used the same password - by coincidence, I had accessed both on the same afternoon, but the first appeared secure (https:) > >> I had been using nabble to access the list - I've never accessed a >> porn website. >> >> Firefox had warned me that the rabble site wasn’t secure when I logged >> in. > > That sounds like spoofing: not actually connecting to the site you think > you are connecting to. Misspelled names (i.e., rabble instead of > nabble) can set oneself up with typo squatters. Could be. But I used a copied-and-pasted URL to access the nabble site - http://lilypond.1069038.n5.nabble.com/Four-Bars-per-Line-System-again-td45952.html I had copied this URL into a Lilypond file along with David Nalesnik’s excellent way of getting a four-bars-to-a-line layout for leadsheets, with sufficient flexibility to get (e.g.) the bridge section starting at the beginning of a line when the number of bars in the A section wasn’t divisible by 4. I have checked my browser’s history for misspellings and have found none. > >> I’ve deleted my nabble account, hence a couple of my messages to the >> group have been deleted. > > Deleting your nabble account sounds like pulling off the tractor > ignition key after the mule has bolted. Nice image!, but I decided I didn’t need to use nabble any more. > > It doesn't sound like it will do much to address password > vulnerabilities or spoofing. I have taken steps to improve the security of my passwords. Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
On 7/13/2018 9:29 AM, Ben wrote:
Is there a way to input the notes in a better way to anticipate this
'bug' in partcombine?
I won't claim a "better way," but I'm used to considering each
appearance of a partcombine text (like "Solo" or "a2") as suspicious and
calling for closer inspection to see if the part combiner met
expectations or not. My audiences aren't used to seeing such texts, so I
want them gone regardless. I pretty much do what Kieren MacMillan
explained about \partcombineApart. Here's how my style would have it:
% CODE
\version "2.19.80"
fluteone = \relative {
e'4( f g a) |
% Only need one note de-combined; use \once
\once \partcombineApart r4 f4 g f |
c'2~ c2 |
f8 f e e f r f f |
% Several notes to de-combine, no \once...
\partcombineApart r1 |
f4 g g g |
% ...done. Set combining back to default.
\partcombineAutomatic c4 c c
}
flutetwo = \relative {
c'2( d) |
e2 f |
r4 e r g |
c2 c2 |
c,4 c c c |
r1 |
c''4 c c
}
\new Staff \with {
instrumentName = #"Flute 1.2"
shortInstrumentName = #"Fl. "
}
% During the version 2.19 series,
% \partcombine gained the ability to specify which intervals
% get combined. From 2 to 9 notes apart works well for my SATB/TTBB
% hymnal music, other kinds of music may have different preferences.
{ \partcombine #'(2 . 9) \fluteone \flutetwo }
% END CODE
--
Karlin High
Missouri, USA
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
Hi Ben, > it does seem rather difficult to be able to predict when you'll need the > "once partcombineapart" in the music until you go to actually *combine* the > parts in a staff, and see the missing rest(s), correct? That’s what I’ve found. (Disclaimer: The part combiner has been improved — is constantly improving? — of late, and I’ve not needed to use it in a production score for two or three years, so I can’t say what the current state is exactly without doing some tests, which I have no time to do right now!) > What I mean is, when you're inputting notes into flute 1, you input the notes > and rests normally As you should. > So what's the best way to do this in your opinion? Should every instance of > brief rests like this in one part but not the other be prefaced with > "once...apart" If I recall correctly, I settled on the fact that part combinations (and the related visuals/texts) are PRESENTATION layer, and not CONTENT layer… so I used the edition-engraver to "inject" commands and markups as desired. (I’ve set aside some time in late August to deal with some long-standing Lilypond-related initiatives; I’ll tack the part-combiner on to that list and get back to you when I’ve put together a "best practices" demo. I know that doesn’t help you now… sorry!) Best, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
On 7/13/2018 9:59 AM, Torsten Hämmerle wrote:
Hi Ben,
Combining two parts is not a trivial task and, sometimes, automatic
\partcombine will not produce optimal results.
*What has happened in your example?*
In measure 2, Flute 1 rests, and therefore, the e' is marked "Solo II", has
neutral stem direction and there is no rest symbol for Flute 1 (see above,
case 1).
Directly after that, Flute 1 kicks in again and \partcombine automatically
switches to polyphonic notation (case 3).
All in all, this is a rather unfortunate solution because of the missing
rest, it is very obscure where Flute 1 actually comes in and it is hard to
distinguish Flute 1 from Flute 2.
*Solution*
In cases like this, \partcombine can be directed by using \partcombineApart
(polyphonic notation as in case 3), \partcombineChords for case 2 and
\partcombineAutomatic to switch back to automatic behaviour.
I follow you.
Please bear with me...
Taking Kieren's workaround into account, and seeing as how you can
certainly work around this 'bug', it does seem rather difficult to be
able to predict when you'll need the "once partcombineapart" in the
music until you go to actually *combine* the parts in a staff, and see
the missing rest(s), correct?
What I mean is, when you're inputting notes into flute 1, you input the
notes and rests normally - not really thinking about down the road that
some rest here and there might not appear, depending on what the other
flute part is doing, so I better put "once...apart" in the code to
handle it. Follow?
So what's the best way to do this in your opinion? Should every instance
of brief rests like this in one part but not the other be prefaced with
"once...apart" just to be sure, or is that overkill? Thanks for helping
me understand this powerful utility!
On 7/13/2018 9:48 AM, Kieren MacMillan wrote:
Hi Ben,
Currently I'm struggling to understand why partcombine won't work as I expected
it to...for orchestral works, it's common to have, say 2 flutes, on the same
staff in the full score but for the parts, only print flute 1 and 2 on separate
parts without the other music included.
(http://lilypond.org/doc/v2.19/Documentation/notation/multiple-voices)
However, I followed along in the documentation and can't figure out why my
quarter note rests won't appear in voice 1, but other duration rests do appear.
To me, that looks like a bug in \partcombine.
Workaround:
\relative { e'4( f g a) |*\once \partcombineApart* r4 f4 g f | c'2~ c2 |
f8 f e e f r f f |r1 | f4 g g g | c c c }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
On 7/13/2018 9:48 AM, Kieren MacMillan wrote:
Hi Ben,
Currently I'm struggling to understand why partcombine won't work as I expected
it to...for orchestral works, it's common to have, say 2 flutes, on the same
staff in the full score but for the parts, only print flute 1 and 2 on separate
parts without the other music included.
(http://lilypond.org/doc/v2.19/Documentation/notation/multiple-voices)
However, I followed along in the documentation and can't figure out why my
quarter note rests won't appear in voice 1, but other duration rests do appear.
To me, that looks like a bug in \partcombine.
Workaround:
\relative { e'4( f g a) | \once \partcombineApart r4 f4 g f | c'2~ c2 |
f8 f e e f r f f |r1 | f4 g g g | c c c }
Is there a way to input the notes in a better way to anticipate this
'bug' in partcombine? Or did I organize things in a clear way?
What I mean is, semantically, is there anything 'wrong' with my input
for this example, with respect to the goal being at some point wanting
to separate orchestral parts?
What am I doing wrong? I'm getting concerned with having to print out parts for
several projects in the near future but these a2/solo markings are not
functioning as I had hoped they would with partcombine.
In what way do you want the markings different from what’s printed?
I just wanted the rests themselves to appear correctly in the two
voices, which I had understood that partcombine was used for :) I'm OK
with the solo / a2 markings appearing, when correct, along with the
rests. I was scared that since one rest somehow flat out didn't appear
in the part, I thought - oh no, all of my parts won't be combined
correctly and rests will not show for all other parts too...
Thanks!
Cheers,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
Hi Ben, Combining two parts is not a trivial task and, sometimes, automatic \partcombine will not produce optimal results. There are different cases when combining two parts in one stave: *1. only one part plays, the other rests* Write the active part only and mark it "Solo" or "Solo II" (these texts can be changed) *2. both parts have the same rhythm* In this case, both parts may even be written as "chords", i.e. sharing the same stem. *3. polyphonic passages* When both parts are rhythmically different, standard polyphonic notation will be used (opposite stem directions). *What has happened in your example?* In measure 2, Flute 1 rests, and therefore, the e' is marked "Solo II", has neutral stem direction and there is no rest symbol for Flute 1 (see above, case 1). Directly after that, Flute 1 kicks in again and \partcombine automatically switches to polyphonic notation (case 3). All in all, this is a rather unfortunate solution because of the missing rest, it is very obscure where Flute 1 actually comes in and it is hard to distinguish Flute 1 from Flute 2. *Solution* In cases like this, \partcombine can be directed by using \partcombineApart (polyphonic notation as in case 3), \partcombineChords for case 2 and \partcombineAutomatic to switch back to automatic behaviour. All the best, Torsten -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partcombine not working for orchestral parts?
Hi Ben,
> Currently I'm struggling to understand why partcombine won't work as I
> expected it to...for orchestral works, it's common to have, say 2 flutes, on
> the same staff in the full score but for the parts, only print flute 1 and 2
> on separate parts without the other music included.
> (http://lilypond.org/doc/v2.19/Documentation/notation/multiple-voices)
> However, I followed along in the documentation and can't figure out why my
> quarter note rests won't appear in voice 1, but other duration rests do
> appear.
To me, that looks like a bug in \partcombine.
Workaround:
\relative { e'4( f g a) | \once \partcombineApart r4 f4 g f | c'2~ c2 | f8
f e e f r f f |r1 | f4 g g g | c c c }
> What am I doing wrong? I'm getting concerned with having to print out parts
> for several projects in the near future but these a2/solo markings are not
> functioning as I had hoped they would with partcombine.
In what way do you want the markings different from what’s printed?
Cheers,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Partcombine not working for orchestral parts?
Good morning,
I wanted to create a new thread which was inspired by my previous email
about voices-staves.
I figured a new thread could help more people this way.
Currently I'm struggling to understand why partcombine won't work as I
expected it to...for orchestral works, it's common to have, say 2
flutes, on the same staff in the full score but for the parts, only
print flute 1 and 2 on separate parts without the other music included.
(http://lilypond.org/doc/v2.19/Documentation/notation/multiple-voices)
However, I followed along in the documentation and can't figure out why
my quarter note rests won't appear in voice 1, but other duration rests
do appear. I thought maybe it was the location of the pitches being too
close, but I tried other octaves and no change occurred.
What am I doing wrong? I'm getting concerned with having to print out
parts for several projects in the near future but these *a2/solo*
markings are not functioning as I had hoped they would with partcombine.
Thank you for setting me straight :)
Example
The rests are not consistently displayed in voice 1, but voice 2 seems
to be correct.
(see attached)
Here is the code:
\version "2.19.81"
fluteone =
% the r4 in measure two simply won't display, yet the 1/8th rest in
measure 4 DOES display?
\relative { e'4( f g a) | r4 f4 g f | c'2~ c2 | f8 f e e f r f f |r1 |
f4 g g g | c c c }
flutetwo =
% however the rests in this voice display correctly?
\relative { c'2( d) e f r4 e r g c2 c2 c,4 c c c r1 c''4 c c }
\new Staff \with {
instrumentName = #"Flute 1.2"
shortInstrumentName = #"Fl. "
}
\partcombine \fluteone \flutetwo
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hacker Warning
Michael Hendry writes: > I’ve recently received a message from a hacker who told me he knew my > password (and quoted it correctly), demanding money in bitcoin for not > forwarding details of my recent visit to a porn website to all my > contacts. You make it sound like you use only one password for everything. A bad idea. > I had been using nabble to access the list - I've never accessed a > porn website. > > Firefox had warned me that the rabble site wasn’t secure when I logged > in. That sounds like spoofing: not actually connecting to the site you think you are connecting to. Misspelled names (i.e., rabble instead of nabble) can set oneself up with typo squatters. > I’ve deleted my nabble account, hence a couple of my messages to the > group have been deleted. Deleting your nabble account sounds like pulling off the tractor ignition key after the mule has bolted. It doesn't sound like it will do much to address password vulnerabilities or spoofing. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hacker Warning
> On 13.07.2018 - 12:42, Michael Hendry wrote: > > > I’ve recently received a message from a hacker who told me he knew my > password (and quoted it correctly), demanding money in bitcoin for not > forwarding details of my recent visit to a porn website to all my contacts. >> >> I had been using nabble to access the list - I've never accessed a porn >> website. >> >> Firefox had warned me that the nabble site wasn’t secure when I logged in. >> >> I’ve deleted my nabble account, hence a couple of my messages to the group >> have been deleted. They may have been deleted from Nabble, but there are two other independent archives of all posts to the list. One can be found via the link below. Also, this isn't the only reason not to use Nabble: for example, it has an idiosyncratic handling of attachments that simply don't appear to many recipients etc. Best, Simon >> lilypond-user mailing list >> lilypond-user@gnu.org >> https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Hacker Warning
I’ve recently received a message from a hacker who told me he knew my password (and quoted it correctly), demanding money in bitcoin for not forwarding details of my recent visit to a porn website to all my contacts. I had been using nabble to access the list - I've never accessed a porn website. Firefox had warned me that the rabble site wasn’t secure when I logged in. I’ve deleted my nabble account, hence a couple of my messages to the group have been deleted. Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Software playing lilypond's music sheets
On Fri, 13 Jul 2018, Samuel DA MOTA wrote: Hi Martin, Thanks for the feedback. Unfortunately since it always was a side project I didn't get much time to polish it like I wanted. In any case, feel free to clone it and improve upon. I kept the build system simple on purpose so that fixing these issues shouldn't be too hard. Had I more time I would have used Meson. Out of curiosity, what is the error you get? When trying to compile lilydumper: make -C ./src "lilydumper" make[1]: Entering directory '/home/m.tarenskeen/rpmbuild/SOURCES/GIT/lilydumper/src' make[1]: *** No rule to make target 'lilydumper'. Stop. make[1]: Leaving directory '/home/m.tarenskeen/rpmbuild/SOURCES/GIT/lilydumper/src' make: *** [Makefile:4: lilydumper] Error 2 When trying to compile lilyplayer: make -C ./src "all" make[1]: Entering directory '/home/m.tarenskeen/rpmbuild/SOURCES/GIT/lilyplayer/src' "/usr/lib64/qt4/bin/uic" -o "ui_mainwindow.hh" "mainwindow.ui" && \ sed -i '1i // Avoid warnings on generated headers\n#if !defined(__clang__)\n #pragma GCC system_header\n#endif\n' "ui_mainwindow.hh" g++ -std=c++1z -Werror -fno-rtti -fstrict-enums -fstack-protector-all --param ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fPIC -fcf-protection=full -fstack-clash-protection -Werror -Wno-pedantic -Wpointer-arith -Wall -Wextra -Wformat=2 -Wnonnull -Winit-self -Wmissing-include-dirs -Wswitch-default -Wswitch-enum -Wuninitialized -fstrict-aliasing -Wstrict-overflow=5 -Warray-bounds -Wfloat-equal -Wundef -Wshadow -Wcast-qual -Wcast-align -Wwrite-strings -Wconversion -Wsign-conversion -Wmissing-declarations -Wpacked -Wredundant-decls -Winvalid-pch -Wlong-long -Wvarargs -Wvla -funsafe-loop-optimizations -Wunsafe-loop-optimizations -Wdouble-promotion -Wsuggest-attribute=pure -Wsuggest-attribute=const -Wsuggest-attribute=noreturn -Wsuggest-attribute=format -Wtrampolines -Wzero-as-null-pointer-constant -Wuseless-cast -Wlogical-op -Wvector-operation-performance -Wabi=11 -Wctor-dtor-privacy -Wnoexcept -Weffc++ -Wstrict-null-sentinel -Wold-style-cast -Woverloaded-virtual -Wsign-promo -Wswitch-bool -Wlogical-not-parentheses -Wsizeof-array-argument -Wbool-compare -Wodr -Wsuggest-final-types -Wsuggest-final-methods -Wsuggest-override -Wnull-dereference -fdelete-null-pointer-checks -Wduplicated-cond -Wplacement-new=2 -Wconditionally-supported -fsized-deallocation -Wsized-deallocation -Wduplicated-branches -Wrestrict -Wregister -Wdangling-else -Walloc-size-larger-than=1073741824 -Walloc-zero -Walloca -Wformat-overflow=2 -Wformat-truncation=2 -Wstringop-overflow=4 -Waligned-new -Wmultistatement-macros -Wcast-align=strict -fsanitize=address -fsanitize=undefined -fbounds-check -DQT_NO_DEBUG -D_REENTRANT -DQT_WIDGETS_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_SVG_LIB -O0 -ggdb3-isystem "/usr/include" -isystem "/usr/include/QtWidgets" -isystem "/usr/include/QtCore" -isystem "/usr/include/QtGui" -isystem "/usr/include/QtSvg" -isystem "**Unknown**/mkspecs/**Unknown**" -I ./ -MD -c -o "main.o" "main.cc" cc1plus: error: /usr/include/QtWidgets: No such file or directory [-Werror=missing-include-dirs] cc1plus: error: **Unknown**/mkspecs/**Unknown**: No such file or directory [-Werror=missing-include-dirs] In file included from /usr/include/c++/8/x86_64-redhat-linux/bits/os_defines.h:39, from /usr/include/c++/8/x86_64-redhat-linux/bits/c++config.h:2450, from /usr/include/c++/8/iosfwd:38, from /usr/include/c++/8/ios:38, from /usr/include/c++/8/ostream:38, from main.cc:1: /usr/include/features.h:381:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp] # warning _FORTIFY_SOURCE requires compiling with optimization (-O) ^~~ In file included from /usr/include/c++/8/ext/string_conversions.h:41, from /usr/include/c++/8/bits/basic_string.h:6361, from /usr/include/c++/8/string:52, from /usr/include/c++/8/bits/locale_classes.h:40, from /usr/include/c++/8/bits/ios_base.h:41, from /usr/include/c++/8/ios:42, from /usr/include/c++/8/ostream:38, from main.cc:1: /usr/include/c++/8/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next ^~ cc1plus: all warnings being treated as errors compilation terminated. make[1]: *** [Makefile:429: main.o] Error 1 rm ui_mainwindow.hh make[1]: Leaving directory '/home/m.tarenskeen/rpmbuild/SOURCES/GIT/lilyplayer/src' make: *** [Makefile:5: all] Error 2 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Software playing lilypond's music sheets
On Fri, 2018-07-13 at 09:39 +0200, Samuel DA MOTA wrote: > Hi Martin, > > Thanks for the feedback. > > Unfortunately since it always was a side project I didn't get much > time to polish it like I wanted. In any case, feel free to clone it > and improve upon. > > I kept the build system simple on purpose so that fixing these issues > shouldn't be too hard. Had I more time I would have used Meson. > > Out of curiosity, what is the error you get? I, too, couldn't make lilydumper on Debian 9.3 (stretch) with make make -C ./src "lilydumper" make[1]: Entering directory '/home/rshann/lilydumper/src' make[1]: *** No rule to make target 'lilydumper'. Stop. but then g++-8 is not available in Debian Stretch it seems ... Richard Shann > Cheers > > On 13/07/2018, Martin Tarenskeen wrote: > > > > > > On Thu, 12 Jul 2018, Samuel DA MOTA wrote: > > > > > Hi everyone! > > > > > > I wrote a software a while ago that would play a music sheet > > > generated > > > by lilypond. It shows the music sheet and follows it with a > > > cursor. I > > > made a video to demo the end-result. You can watch it at > > > https://s-d-m.github.io/lilydumper/intro_assets/lilyplayer-demo.w > > > ebm > > > > Wow. I'm impressed. This is something that I could use! > > I downloaded the sources from GitHub but was not able to compile > > succesfully (yet). I'm on Linux Fedora 28. > > > > I hope a userfriendly distribution of the tools will be available > > one day. > > Or a Makefile that works on my system. > > > > If anyone has succesfully compiled these tools on a Fedora system > > please > > share what additional libraries, steps or patches were required. > > > > -- > > > > MT > > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Four Bars per Line/System, again :)
Michael,
thanks for drawing attention to this /superb/ tool! (It's quite old now
but works flawlessly with current Lilypond versions).
...but with additional "\book"s for Bb and Eb instruments. I'd like to be
able to avoid the potential for error in dealing with the odd line which
needs to be other than 4 bars long by defining the "4 4 4 4 3 4 ..." as a
variable and then passing the variable to custom-line-breaks-engraver but I
can't work out how to do this.
That's easy if you know the Lilypond syntax for incorporating Scheme
elements:
myList = #'(4 4 4 4 3 4)
\layout {
\context {
\Score
\consists #(custom-line-breaks-engraver myList)
}
}
Best
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Software playing lilypond's music sheets
Hi Martin, Thanks for the feedback. Unfortunately since it always was a side project I didn't get much time to polish it like I wanted. In any case, feel free to clone it and improve upon. I kept the build system simple on purpose so that fixing these issues shouldn't be too hard. Had I more time I would have used Meson. Out of curiosity, what is the error you get? Cheers On 13/07/2018, Martin Tarenskeen wrote: > > > On Thu, 12 Jul 2018, Samuel DA MOTA wrote: > >> Hi everyone! >> >> I wrote a software a while ago that would play a music sheet generated >> by lilypond. It shows the music sheet and follows it with a cursor. I >> made a video to demo the end-result. You can watch it at >> https://s-d-m.github.io/lilydumper/intro_assets/lilyplayer-demo.webm > > Wow. I'm impressed. This is something that I could use! > I downloaded the sources from GitHub but was not able to compile > succesfully (yet). I'm on Linux Fedora 28. > > I hope a userfriendly distribution of the tools will be available one day. > Or a Makefile that works on my system. > > If anyone has succesfully compiled these tools on a Fedora system please > share what additional libraries, steps or patches were required. > > -- > > MT > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Software playing lilypond's music sheets
On Thu, 12 Jul 2018, Samuel DA MOTA wrote: Hi everyone! I wrote a software a while ago that would play a music sheet generated by lilypond. It shows the music sheet and follows it with a cursor. I made a video to demo the end-result. You can watch it at https://s-d-m.github.io/lilydumper/intro_assets/lilyplayer-demo.webm Wow. I'm impressed. This is something that I could use! I downloaded the sources from GitHub but was not able to compile succesfully (yet). I'm on Linux Fedora 28. I hope a userfriendly distribution of the tools will be available one day. Or a Makefile that works on my system. If anyone has succesfully compiled these tools on a Fedora system please share what additional libraries, steps or patches were required. -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Software playing lilypond's music sheets
Hi Sam, thanks a lot for sharing this! Best Jan-Peter Am 12.07.2018 um 23:48 schrieb Samuel DA MOTA: > Hi everyone! > > I wrote a software a while ago that would play a music sheet generated > by lilypond. It shows the music sheet and follows it with a cursor. I > made a video to demo the end-result. You can watch it at > https://s-d-m.github.io/lilydumper/intro_assets/lilyplayer-demo.webm > > The soft is mainly based on the event listener. If you are interested > in knowing how I extracted pieces of information from lilypond to know > e.g. where on the music sheet the cursor is and at which time, you can > read the documentation at https://s-d-m.github.io/lilydumper/ > > The tool to extract the data and generate a "playable" music sheet is > lilydumper: https://github.com/s-d-m/lilydumper and the one that > actually plays it is lilyplayer: https://github.com/s-d-m/lilyplayer > > If you think adding a new output to lilypond for that use case would > be nice and have questions, let me know. > > Kindest regards > > Sam > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Software playing lilypond's music sheets
Wow! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
