Am 27.01.2018 um 16:53 schrieb Stefano Troncaro:
Thanks guys!
Urs, your explanation is very detailed and dissipated any remaining
doubts I had left about this issue.
Glad to hear :-)
Jan-Peter, I pulled the changes and after a quick test going through
some files everything seems to be w
Thanks guys!
Urs, your explanation is very detailed and dissipated any remaining doubts
I had left about this issue.
Jan-Peter, I pulled the changes and after a quick test going through some
files everything seems to be working fine. I'll let you know if something
comes up.
About writing an expl
Thank you for your feedback Stefano!
I merged some code, which was pending quite some time. There was an
issue with the first moment inside a context that is fixed now, *but* in
your example it does not work (yet). This was quite tricky to track
down: If you create a new Voice inside a new Voi
Hi Stefano,
Am 26.01.2018 um 22:41 schrieb Stefano Troncaro:
To the openlilylib guys, since I'll be learning to use your tools,
tell me if I can be of use somehow.
One thing would be of tremendous use for us: when you have understood
how something works you could write up the explanation that
Hi Stefano,
I have now also looked at your example. I think your voicing is strange
even without considering the edition-engraver.
What you do is:
* Create a staff ("LH")
* Explicitly create a Voice ("Implied")
* Start the content of that Voice with the clef
* *Then* create two new voices
Thank you Noeck.
Your explanation makes sense and I feel it might be close to explaining the
issue, although in the log it appears as though the edition-engraver only
sees two voices, not three, thus refering to them as Voice.B and Voice.C
instead of A and B doesn't work either.
Most intriguing t
Hi Stefano,
if you write
{ \clef F <<
as in your file eetest-not-working.ly you have this in your Staff
context: \clef F and then afterwards two voices at the same time.
More explicitly, your code is interpreted as somthing like:
\new Staff {
\new Voice { \clef F
<<
\new Voice ...
Thanks for the remark! Obviouslyis a private communication thread about
a special topic not for common lilypond users. I will not interfere.
Regards
Am 26.01.2018 18:52, schrieb Urs Liska:
Am 26. Januar 2018 18:31:24 MEZ schrieb Simon Albrecht
:
On 26.01.2018 17:40, Blöchl Bernhard wrote:
Am 26. Januar 2018 18:31:24 MEZ schrieb Simon Albrecht :
>On 26.01.2018 17:40, Blöchl Bernhard wrote:
>> I tried your code with my standard lilypond without success.
>>
>> Obviously you use a package oll-core
>> https://github.com/openlilylib/oll-core
>> that is not part of standard install of li
On 26.01.2018 17:40, Blöchl Bernhard wrote:
I tried your code with my standard lilypond without success.
Obviously you use a package oll-core
https://github.com/openlilylib/oll-core
that is not part of standard install of lilypond and seems to be the
central problem of your code. May be you get
I tryed your code with my standard lilypond without success.
Obviously you use a package oll-core
https://github.com/openlilylib/oll-core
that is not part of standard install of lilypond and seems to be the
central problem of your code. May be you get competent help of the
oll-core users?
Reg
Thank you Jan-Peter, that's really useful!
In regards to the first problem, I experimented with it a little. Using the
same snippet as before, It turns out that if I write this line like this:
> \new Staff \with { \editionID LH } { \clef F <<
>
> Then the path to Piano.LH.Voice.A doesn't seem to
Hello Stefano,
I can't reproduce the misbehaviour/error you mentioned first. The
overrides are applied irrespective of the clefs placement. If the error
persists, you might send the .edition.log file.
To reduce the redundancy you mentioned you can create variables:
LH = Piano.LH
RH = Piano.R
Hello everyone! So, I'm learning to use the edition-engraver, but there are
some behaviors that I can't figure out.
Take the following snippet:
> \version "2.19.80"\language "english"
> \include "oll-core/package.ily"\loadPackage edition-engraver
> \addEdition test
> \editionMod test 1 0/4 RH.Voi
14 matches
Mail list logo
