I am showing a part of the completed score. The problem was not the
beaming but the text distribution in the original example.
AutobeamingOff was correct for the First line , the line with the
beamExceptions took care of the eigths and the corresponding text in the
second line.
Kind regards
Hello folks,
I’m at a loss regarding that : \compressMMRests, compressEmptyMeasures are
present in LPNR 2.23, but Frescobaldi 3.1.3 knows only \compressFullBarRests.
I remember there’s been a name change at some point in time.
Sp which command should one use?
Thanks for your help!
JM
Am Fr., 12. Nov. 2021 um 13:44 Uhr schrieb Leo Correia de Verdier
:
>
> Dear Harm and list!
>
> The chords were not that hard to implement. What I did was:
>
> 1) Removing the overrides for NoteHead.transparency and NoteHead.Y-offset
> from glissandoStemsOn and glissandoStemsOff. Transparency is s
Hello Jacques,
Frescobaldi does not always know the latest Lilypond language. As far as I see
\compressMMRests and \comressEmptyMeasures do the same, but
\compressEmptyMeasures works like a toggle that needs to be unset by
\expandEmptyMeasures (it’s basically just a shorthand for \set Score.ski
Am So., 14. Nov. 2021 um 14:15 Uhr schrieb Valentin Petzel :
>
> Hello Jacques,
>
> Frescobaldi does not always know the latest Lilypond language. As far as I see
> \compressMMRests and \comressEmptyMeasures do the same, but
> \compressEmptyMeasures works like a toggle that needs to be unset by
> \
Hello Thomas,
Yes, you’re right, I missed that there is an music-map in there. So basically
it just sets Score.skipBars once each time it encounters a MM rest in the
argument music.
Valentin
Am Sonntag, 14. November 2021, 14:58:18 CET schrieb Thomas Morley:
> Am So., 14. Nov. 2021 um 14:15 Uhr
Harm wrote:
Well, not exactly.
\compressMMRests compresses MMRs in the following music-espression,
which may be some longer sequential music. It is _limited_ to MMRs.
\compressEmptyMeasures compresses MMRs and other long durations until reverted:
m = {
\override Score.BarNumber.break-visibili
Am Mi., 27. Okt. 2021 um 16:29 Uhr schrieb Dimitris Marinakis <
dtsmari...@gmail.com>:
> Thomas fantastic work as always. I found a potential limitation. Can you
> confirm if this is possible with the current code?
> I'd like a bit more control on the stem attachment of the splited stems
> ideally
Le 13/11/2021 à 20:41, David Sumbler a écrit :
I have just started on a new Lilypond project, having had little
interaction with Lilypond for several months. I installed v.2.23.4.
Although I have so far only set 3 lines of music on 2 staves, the
message "programming error: cyclic dependency:
It's easy as pie to convert in Frescobaldi (which uses convert-ly).
--
Knute Snortum
On Sat, Nov 13, 2021 at 10:44 PM m.tarensk...@kpnmail.nl
wrote:
>
> Have tried convert-ly?
>
> MT
>
> Verzonden vanaf mijn Huawei mobiele telefoon
>
>
> Oorspronkelijk bericht
> Onderwerp: unk
Le 14/11/2021 à 13:49, Thomas Morley a écrit :
Am Fr., 12. Nov. 2021 um 13:44 Uhr schrieb Leo Correia de Verdier
:
Dear Harm and list!
The chords were not that hard to implement. What I did was:
1) Removing the overrides for NoteHead.transparency and NoteHead.Y-offset from
glissandoStemsOn
On Sun, Nov 14, 2021 at 4:10 AM Jacques Menu wrote:
>
> Hello folks,
>
> I’m at a loss regarding that : \compressMMRests, compressEmptyMeasures are
> present in LPNR 2.23, but Frescobaldi 3.1.3 knows only \compressFullBarRests.
You can use \compressMMRests in Frescobaldi without a problem, it ju
Thank you for your help in this matter.
I added the line "\consists Staff_collecting_engraver" as suggested,
and read the somewhat cryptic paragraph under Mark_engraver in the IR,
as indicated in the link you provided.
Unfortunately I still got the same error messages as before.
However, re-read
13 matches
Mail list logo
