Re: strange error message

On Tue, Mar 11, 2025 at 2:57 AM Stefan Thomas wrote: > Dear Knute, > so far I have not been able to reproduce the error message, but I'll keep > at it. > In what contexts does the “cyclic dependency” message occur? > I've seen them when using a \change Staff command, but that doesn't seem to be

Re: strange error message

Dear Knute, so far I have not been able to reproduce the error message, but I'll keep at it. In what contexts does the “cyclic dependency” message occur? Am Fr., 7. März 2025 um 01:07 Uhr schrieb Knute Snortum : > On Thu, Mar 6, 2025 at 5:02 AM Stefan Thomas > wrote: > >> Dear community, >> whi

Re: strange error message

On Thu, Mar 6, 2025 at 5:02 AM Stefan Thomas wrote: > Dear community, > while compiling a certain file after upgrading to version 2.24.4 I get > strange two error messages: > The first one is: > >> ~/partituren/vorlagen/rhythmen.ly:233:9: programming error: cyclic >> dependency: calculation-in-pr

Re: Strange pdf render

One workaround you might try is to print your PDF as PDF. I do not know if it works, but it is simple to try... Maybe the new PDF output would stop displaying your strange decolorations I have done that for another unrelated problem I had on PDF's... Silvain Le 14.11.24 à 17:46, Mats Bengtsson a

Re: Strange pdf render

On 2024-11-14 13:35, Mats-Olof Liljegren wrote: Hello! I have a strange issue that’s a bit off-topic, perhaps. When I render to PDF, everything looks fine on my computer and in printouts. But when I import the PDF into ForScore on iPad, I get strange discolorations. See the attached image. H

Re: Strange pdf render

Thank’s for all answers. Obvious now.. Med vänlig hälsning / Kind regards Mats-Olof Liljegren e-pro Sturegatan 14 702 14 Örebro Tel 070 360 19 19 e-post m...@e-pro.se web: http://e-pro.se > 14 nov. 2024 kl. 14:19 skrev Xavier Scheuer : > > On Thu, 14 Nov 2024 at 13:37, Mats-Olof Liljegren

Re: Strange pdf render

It looks to me like ForScore hyperlinks. You can disable these in ForScore by going to Settings -> PDF Annotations, and then disable Hyperlinks. You might also try \pointAndClickOff in your score file and recreate the PDF. -- Bret Whissel https://bretwhissel.net b...@bretwhissel.net -Origin

Re: Strange pdf render

On Thu, 14 Nov 2024 at 13:37, Mats-Olof Liljegren wrote: > > Hello! I have a strange issue that’s a bit off-topic, perhaps. When I render to PDF, everything looks fine on my computer and in printouts. But when I import the PDF into ForScore on iPad, I get strange discolorations. See the attached i

Re: Strange pdf render

At 13:35 14/11/2024 +0100, Mats-Olof Liljegren wrote: But when I import the PDF into ForScore on iPad, I get strange discolorations. See the attached image. See http://forscore.co/kb/why-are-there-blue-rectangles-on-certain-pages/ . I trust this helps. Brian Barker

Re: Strange behavior with repeat immediately before alternate endings

On Thu, 10 Oct 2024 10:06:03 -0700 Knute Snortum wrote: > On Thu, Oct 10, 2024 at 9:27 AM Lucas Cavalcanti > wrote: > > > Put brackets before and after the "repeat unfold 3". Don't know what > > causes this bug, but it still happens in version 2.25.19. > > > > %% > > \fixed c'' { > > \repeat

Re: Strange behavior with repeat immediately before alternate endings

On Fri, 11 Oct 2024, Peter Chubb wrote: > The syntax of repeat is: >\repeat TYPE MUSIC ALTERNATIVES > So when you have: >\repeat volta 2 { > \repeat unfold {} > \alternative { > } >} > The alternatives are attached to the unfolded repeat, and get unfolded. That's the

Re: Strange behavior with repeat immediately before alternate endings

> "Cameron" == Cameron Hall writes: Cameron> I've run into a strange problem that I think may be a bug. In Cameron> this MWE, I have a repeat with alternate endings. However, Cameron> the "\repeat unfold 3 { c1 }" is causing the volta brackets Cameron> to disappear for some reason. If I inste

Re: Strange behavior with repeat immediately before alternate endings

On Thu, Oct 10, 2024 at 9:27 AM Lucas Cavalcanti wrote: > Put brackets before and after the "repeat unfold 3". Don't know what > causes this bug, but it still happens in version 2.25.19. > > %% > \fixed c'' { > \repeat volta 2 { > {\repeat unfold 3 { c1 }} > \alternative { \volta 1 { d

Re: Strange behavior with repeat immediately before alternate endings

Put brackets before and after the "repeat unfold 3". Don't know what causes this bug, but it still happens in version 2.25.19. %% \fixed c'' { \repeat volta 2 { {\repeat unfold 3 { c1 }} \alternative { \volta 1 { d } \volta 2 { e } } } c4 r r2} %% Em qui., 10 de out. de 2024 às 13:21,

Re: strange chord

> I mean… technically, it’s correct… Thanks. > but yuck. :-) > If I were customizing the name, I would probably have it say > Em(addb4). At the very least it should say Emsusb4. As chord names noob I have no opinion to that. I just wanted to ensure that MR !2335 produces correct results, e

Re: strange chord

Hi Werner, I mean… technically, it’s correct… but yuck. If I were customizing the name, I would probably have it say Em(addb4). At the very least it should say Emsusb4. — Kieren __ My work day may look different than your work day. Please do not feel

Re: strange chord

> I tried the following > > ``` > \version "2.25.16" > > chord = \chordmode { c4:6-^1 } > > << > \new ChordNames \chord > \chordmode { \chord } > >> > ``` > > and got the attached result. The displayed chord name looks weird > to me, but I'm no expert for Jazz chords... Is it correct? If no

Re: Strange behavior of repeat unfold inside a repeat volta with alternatives.

Thanks for the explanation! I was not aware of the previous behavior and that was very confusing. And I guess I was not expecting alternatives to work with /unfold/ either but that makes sense. On 2023-09-26 23:53, David Kastrup wrote: Stéphane SOPPERA writes: I observed a strange behavior

Re: Strange behavior of repeat unfold inside a repeat volta with alternatives.

Stéphane SOPPERA writes: > I observed a strange behavior with a /repeat unfold/ inside a /repeat > volta/ with /alternatives/. See the attached /bug_repeat__ok.ly/ for > full source. > > Using Lilypond 2.24.1: > >     \repeat volta 2 { >   %% Here we repeat three times the same music. > *

Re: strange detached beam issue

Thanks, you were right. There was an unterminated Slur.outside-staff-priority override that was causing the problem. This snippet displays the flying beam: \version "2.24.1" top = { \change Staff = "upper" \voiceTwo } bottom = { \change Staff = "lower" \voiceOne } upper = \relative c'' { \ove

Re: strange detached beam issue

I note some other differences between your image and what the code sample generates, in the slur and dynamic positions. I can't suggest what in particular is happening, but if this happened to me, I'd be looking for an earlier tweak or override which hadn't been cancelled. Paul From: Ji

Re: strange detached beam issue

Yes, I noted that the problem doesn’t occur in my snippet. I will try to add things to it until I can get it to happen. In my full text, I have just had it happen again, in a similar passage where both parts leave the upper stave. Forcing a voice to “hold open” the staff again fixes it for me.

Re: strange detached beam issue

It should be noted that on 2.25.7 this doesn't happen on my machine, and the beam renders correctly (after running convert-ly on your snippet, it didn't change anything). -William On 8/15/23 18:11, Jin Choi wrote: I have a section of piano music where two voices start in the treble clef and

Re: strange detached beam issue

I solved the issue, but still don’t understand why it happened. Apparently, when both voices leave the top staff, the staff or some context or something just goes away at that point, even though it’s in use later? I just added a third parallel voice that sits in the top staff and s1*4 to hold it

Re: Strange behaviour of multiple \include’d documents

On 30/01/2023 22:26, Immanuel Asmus wrote: > Hello Jean, > > actually, I /did/ subscribe. I wonder why my subscription was unsuccessful. I > just tried again. It didn't work this time either. I approved your message again. Did you receive the confirmation email after filling the subscription for

Re: Strange behaviour of multiple \include’d documents

Hello Jean, actually, I /did/ subscribe. I wonder why my subscription was unsuccessful. I just tried again. I finally found the cause of this error: It seems I checked only the paper variables of my main document and Wetterlied.ly, whereas I didn’t llok carefully into the other tqo source fi

Re: Strange behaviour of multiple \include’d documents

On Mon, Jan 30, 2023 at 9:34 AM Jean Abou Samra wrote: > Hello Immanuel, > > Welcome to this list. For your information, I had to approve your message > manually as a list administrator because you are not subscribed to the list > yet. Please fix this by subscribing on > https://lists.gnu.org/mai

Re: Strange behaviour of multiple \include’d documents

Dear Immanuel, Sorry, I’m having trouble finding what would be the problem from the provided snippets. Could you please reduce the files to a minimum working example that we can compile that reproduces the problem? This might help find what is the problem. In my experience when this kind of t

Re: Strange behaviour of multiple \include’d documents

Hello Immanuel, Welcome to this list. For your information, I had to approve your message manually as a list administrator because you are not subscribed to the list yet. Please fix this by subscribing on https://lists.gnu.org/mailman/listinfo/lilypond-user (note that once subscribed, you can

Re: Strange font problem in 2.24.0

>> It was diagnosed as a bug in the font (!), not in LilyPond. > > Yes, I saw the issue. That's extraordinarily weird. It's not. > It is one of the fonts installed with Microsoft Office so maybe this > should be reported to Microsoft. Newer versions of this font have it fixed. For example, 'Ti

Re: Strange font problem in 2.24.0

On Mon, 2 Jan 2023 at 16:11, Jean Abou Samra wrote: > Le 02/01/2023 à 14:31, Jean Abou Samra a écrit : > > Le 31/12/2022 à 18:23, Sven Axelsson a écrit : > >> I sent the font file to you privately. > > > > Thanks, I opened > > > > https://gitlab.com/lilypond/lilypond/-/issues/6508 > > > It was di

Re: Strange font problem in 2.24.0

Le 02/01/2023 à 14:31, Jean Abou Samra a écrit : Le 31/12/2022 à 18:23, Sven Axelsson a écrit : I sent the font file to you privately. Thanks, I opened https://gitlab.com/lilypond/lilypond/-/issues/6508 It was diagnosed as a bug in the font (!), not in LilyPond. OpenPGP_signature Descri

Re: Strange font problem in 2.24.0

Le 31/12/2022 à 18:23, Sven Axelsson a écrit : I sent the font file to you privately. Thanks, I opened https://gitlab.com/lilypond/lilypond/-/issues/6508 OpenPGP_signature Description: OpenPGP digital signature

Re: Strange font problem in 2.24.0

On Sat, 31 Dec 2022 at 17:39, Jean Abou Samra wrote: > > > Le 31/12/2022 à 17:11, Sven Axelsson a écrit : > > On Sat, 31 Dec 2022 at 16:33, Jean Abou Samra > wrote: > > > > Le 31/12/2022 à 14:56, Sven Axelsson a écrit : > > > Hi list, > > > > > > I have just updated my sheet musi

Re: Strange font problem in 2.24.0

Le 31/12/2022 à 17:11, Sven Axelsson a écrit : On Sat, 31 Dec 2022 at 16:33, Jean Abou Samra wrote: Le 31/12/2022 à 14:56, Sven Axelsson a écrit : > Hi list, > > I have just updated my sheet music archive to LilyPond 2.24.0. It went > well, but I am seeing a strange fo

Re: Strange font problem in 2.24.0

On Sat, 31 Dec 2022 at 16:33, Jean Abou Samra wrote: > Le 31/12/2022 à 14:56, Sven Axelsson a écrit : > > Hi list, > > > > I have just updated my sheet music archive to LilyPond 2.24.0. It went > > well, but I am seeing a strange font encoding problem. > > > > I have installed LilyPond on a Mac M

Re: Strange font problem in 2.24.0

Le 31/12/2022 à 14:56, Sven Axelsson a écrit : Hi list, I have just updated my sheet music archive to LilyPond 2.24.0. It went well, but I am seeing a strange font encoding problem. I have installed LilyPond on a Mac M1 running MacOS 13.1 with Homebrew which builds from source using Guile 3.

Re: Strange issue where lilypond runs a line off the page

Moving things to the staff context fixed both issues. Thanks a lot! --Galen On Mon, Aug 29, 2022 at 5:10 PM Aaron Hill wrote: > On 2022-08-29 4:03 pm, Galen Hazelwood wrote: > > I don't see what other event it could be talking about. I don't know if > > this is an actual problem, or my understa

Re: Strange issue where lilypond runs a line off the page

On 2022-08-29 4:03 pm, Galen Hazelwood wrote: I don't see what other event it could be talking about. I don't know if this is an actual problem, or my understanding of lilypond isn't good enough yet. It is an unbreakable beam that is blocking things. Your \override for Beam.breakable applies

Re: Strange Page Break Error

> On 17 Nov 2021, at 13:42, Robert Schmaus wrote: > > Dear Ponderers, > > I was just about to quickly write down a sheet of music, nothing fancy at > all, when all of a sudden I got an exception. This is the full ly code (and I > can’t make it any shorter for the reasons explained below): >

Re: Strange Page Break Error

Quick Update: The exception did indeed disappear after entering some more music. Header is also no problem anymore … I just hope, it stays like this when I get to the end of the music … > On 17. Nov 2021, at 13:37, Robert Schmaus wrote: > > Dear Ponderers, > > I was just about to quickly wr

Re: Strange Page Break Error

This compiled fine for me on lilypond 2.23.3, except for the warning about the empty ChordNames. On lilypond 2.20 I got an error message similar to yours (without the filename weirdness), but it compiled fine if I commented out the ChordNames line or typed something into its music expression. I

Re: Strange text distribution

See melismaBusyProperties in http://lilypond.org/doc/v2.23/Documentation/notation/common-notation-for-vocal-music#multiple-notes-to-one-syllable On 13/11/2021 13:54, Bernhard Kleine wrote: Hi, I feel lost. The text should go to every note in the example. However the brackets behave as slurs /t

Re: Strange text distribution

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

Re: Strange text distribution

Hello Bernhard, I think you’re tackling the wrong problem. First of all you can use manual beaming without \autoBeamOff. But then your manual beams appear to be only nescessary because 3/4 time sets a so called beaming exception for eigth notes, so instead of 8[ 8] 8[ 8] 8[ 8] you have 8[ 8 8 8

Re: Strange text distribution

Add a line \set melismaBusyProperties = #'() to the global variable. Thanks a lot Bernhard Am 13.11.2021 um 15:09 schrieb Phil Holmes: See melismaBusyProperties in http://lilypond.org/doc/v2.23/Documentation/notation/common-notation-for-vocal-music#multiple-notes-to-one-syllable On 13/11/

Re: Strange text distribution

I found the solution: add a line Am 13.11.2021 um 15:09 schrieb Phil Holmes: See melismaBusyProperties in http://lilypond.org/doc/v2.23/Documentation/notation/common-notation-for-vocal-music#multiple-notes-to-one-syllable On 13/11/2021 13:54, Bernhard Kleine wrote: Hi, I feel lost. The text

Re: Strange text distribution

Bernhard Kleine writes: > Hi, I feel lost. The text should go to every note in the > example. However the brackets behave as slurs /ties. This is > unexpected. Where is the error? > > Kind regards Bernhard > > \version "2.21.1" > \language "deutsch" > \header { >   title = "Im Haslachtal" >   tag

Re: Strange beams on cross-staff tremolos

On Wed, Nov 3, 2021 at 11:03 AM Paolo Prete wrote: > > Instead of suppressing the warning, given that LilyPond adds an invisible > "auxiliary" stem to the whole notes, for creating the tremolo beam, > I think it should be better to explicitly set the stems on both notes, > according to the beam'

Re: Strange beams on cross-staff tremolos

Instead of suppressing the warning, given that LilyPond adds an invisible "auxiliary" stem to the whole notes, for creating the tremolo beam, I think it should be better to explicitly set the stems on both notes, according to the beam's position: %%% \version "2.22.0" upper = { s1 } lower = {

Re: Strange beams on cross-staff tremolos

Thanks for your reply, but unfortunately the value of Beam.gap depends on how long is the measure, then it requires to be set only after a definitive score and with a trial and error procedure... BTW, I wonder if these issues are reported as known bugs in the ML On Wed, Nov 3, 2021 at 4:17 PM Masa

Re: Strange beams on cross-staff tremolos

When tremolo beams between whole notes don't work good, try to specify directions of implicit stems of whole notes. \version "2.22.0" upper = { s1 s } lower = { \clef treble \override Beam.gap = 3 % a way to fix 2) \repeat tremolo 8 { \stemUp c16 \change Staff = "upper"

Re: Strange beams on cross-staff tremolos

On Wed, Nov 3, 2021 at 5:44 AM Paolo Prete wrote: > > Hello, > > I'm experiencing strange beams on cross-staff tremolos on whole notes. > The beam in the below snippet: 1) is not placed at the middle of the two > notes and 2) it is too close to the ledger lines. > > Is this expected? > Is there a

Re: Strange staff/system spacing

Hello Jean and Lukas, I resolved the problem by adding one more \allowPageTurn to the music. I guess that is still a sort of bug related to ly:page-turn-breaking but my own problem has been resolved by having reasonable number of \allowPageTurn in the music. Thanks for your help and best regard

Re: Strange staff/system spacing

Hello Jean and Lukas, I’ve just realized that my problem might be due to inappropriate use of: page-breaking = #ly:page-turn-breaking If I comment out the above line in the \paper block, the problem goes away. I will investigate further. Cheers, Jun > 2021/07/27 1:09、田村淳 のメール: > > Hello Luk

Re: Strange staff/system spacing

Hello Lukas and Jean, Thanks for your offer. Here is a zip archive containing all the source files to generate the harpsichord part. “BWV_1044_hpd.ly” should be compiled. If you uncomment the last line of “BWV_1044_header.ily” to make \edition an empty string, the result would be fine. Note th

Re: Strange staff/system spacing

Le 26/07/2021 à 15:58, 田村淳 a écrit : Hello! I’m about to finish one project but I’ve encountered a very strange problem. I have no idea where to start looking into. And I don’t think I can produce a tiny example easily. This is the first 2 pages of 25-page harpsichord part: [attachment 1] Ev

Re: Strange behaviour of chord names?

Ah, that explains it. Thank you very much, Aaron! Am Sa., 13. März 2021 um 16:02 Uhr schrieb Aaron Hill < lilyp...@hillvisions.com>: > On 2021-03-13 6:11 am, Christian Masser wrote: > > [...] > > mySoloChordsA = \chords { > > c1 f g c > > } > > [...] > > I think you want \chordmode, not \chords

Re: Strange behaviour of chord names?

On 2021-03-13 6:11 am, Christian Masser wrote: [...] mySoloChordsA = \chords { c1 f g c } [...] I think you want \chordmode, not \chords, when defining the variables. \chords { ... } is shorthand for \new ChordNames \chordmode { ... } if I recall. -- Aaron Hill

RE: Strange behavior with grace notes

John, This is a known issue. To compensate place a spacer grace in each of the other voices/staves. Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of John Burt Sent: Friday, July 24, 2020 11:31 AM To: lilypond-user Subject: Strange beha

Re: Strange behavior with grace notes

Please check the known issues in the notation reference: https://lilypond.org/doc/v2.20/Documentation/notation/special-rhythmic-concerns You must put grace skips in all staves when a grace note is at the start of a piece. HTH, Carl From: lilypond-user on behalf of John Burt Date: Friday,

Re: Strange error from define-syntax

"John Schlomann" writes: > define-macro works perfectly for me, even though the Guile manual seems to > somewhat disparage its use. Well, it's not the modern Scheme way but at the current point of time LilyPond works best with Guile 1.8. -- David Kastrup

RE: Strange error from define-syntax

nd-User Mailing List' > Subject: Re: Strange error from define-syntax > > "John Schlomann" writes: > > > Thank you, David, for your quick response. I'm not sure what you mean by > > "stick to macros". I thought define-syntax was the way to define

Re: Strange error from define-syntax

"John Schlomann" writes: > Thank you, David, for your quick response. I'm not sure what you mean by > "stick to macros". I thought define-syntax was the way to define a macro. > What am I missing? define-macro and defmacro apparently. -- David Kastrup

Re: Strange error from define-syntax

On 5/28/20, John Schlomann wrote: > Thank you, David, for your quick response. I'm not sure what you mean by > "stick to macros". I thought define-syntax was the way to define a macro. > What am I missing? I think David may have been referring to LilyPond macros; have a look at that for example:

RE: Strange error from define-syntax

2020 11:54 AM > To: John Schlomann > Cc: 'Lilypond-User Mailing List' > Subject: Re: Strange error from define-syntax > > "John Schlomann" writes: > > > Dear Ponders & Schemers, > > > > > > > > I wanted to try creating a simple

Re: Strange error from define-syntax

"John Schlomann" writes: > Dear Ponders & Schemers, > > > > I wanted to try creating a simple Scheme macro. I've never done this before, > so I may well be going about it all wrong, but the error I get doesn't make > sense. > > > > Here is a minimal non-working example: > > > > \version "2.

Re: Strange error from \new Voice

On Fri 10 Apr 2020 at 09:58:57 (+0200), Michael Gerdau wrote: > > When working with addlyrics it was outside the \new staff construct like > > here: > > > > tenorVoicePart = \new Staff \with { > >   instrumentName = "Tenor" > >   midiInstrument = "choir aahs" > > } { \clef "treble_8" \tenorVoice }

Re: Strange error from \new Voice

On Thu 09 Apr 2020 at 18:41:40 (+0200), Noeck wrote: > Am 09.04.20 um 18:18 schrieb Bernhard Kleine: > > This would be worth mentioning in the manual! > > glad it works. What exactly would you mention in the manual? > > 1) How to use the \lyricsto construct? It is explained here: > > https://lil

Re: Strange error from \new Voice

> When working with addlyrics it was outside the \new staff construct like > here: > > tenorVoicePart = \new Staff \with { >   instrumentName = "Tenor" >   midiInstrument = "choir aahs" > } { \clef "treble_8" \tenorVoice } > \addlyrics { \verseVoice } > > Now, it is within > > Soprano = \new Sta

Re: Strange error from \new Voice

When working with addlyrics it was outside the \new staff construct like here: tenorVoicePart = \new Staff \with {   instrumentName = "Tenor"   midiInstrument = "choir aahs" } { \clef "treble_8" \tenorVoice } \addlyrics { \verseVoice } Now, it is within Soprano = \new Staff \with {   instrumentN

Re: Strange error from \new Voice

Am 09.04.20 um 18:18 schrieb Bernhard Kleine: > This would be worth mentioning in the manual! Hi Bernhard, glad it works. What exactly would you mention in the manual? 1) How to use the \lyricsto construct? It is explained here: https://lilypond.org/doc/v2.20/Documentation/notation/common-no

Re: Strange error from \new Voice

Am 09.04.2020 um 17:18 schrieb Noeck: > > Am 09.04.20 um 17:04 schrieb Bernhard Kleine: >> \new Lyrics \lyricsto „SI“ > Did you copy that verbatim or use the correct "normal quotes": > > \new Lyrics \lyricsto "SI" > > Just to rule out that simple problem. > > Joram This is what is there : Sopran

Re: Strange error from \new Voice

Am 09.04.20 um 17:04 schrieb Bernhard Kleine: > \new Lyrics \lyricsto „SI“ Did you copy that verbatim or use the correct "normal quotes": \new Lyrics \lyricsto "SI" Just to rule out that simple problem. Joram

Re: Strange error from \new Voice

this results in an error: the output is in the appendix. Preprocessing graphical objects... programming error: No spring between column 0 and next one continuing, cross fingers programming error: No spring between column 0 and next one continuing, cross fingers programming error: didn't find

Re: Strange error from \new Voice

Replace \addlyrics... by \new Lyrics \lyricsto „SI“... Kind regards, Michael Mobil gesendet > Am 09.04.2020 um 15:03 schrieb Bernhard Kleine : > > I have the following extract from Mendelssohn Bartholdy. I noticed that > the parentheses in measure seven were not respected and the text was > w

Re: Re: strange time changes - req help

On 2020-03-30 16:10, Eby Mani wrote: Thank you Aaron. Malte, can you explain why you have mentioned \partial 8*7 is not needed ?. Probably since Malte uses the latest stable version, 2.20, which handles these things much better than what was done in version 2.18. Try it out and you should

Re: strange time changes - req help

On 2020-03-28 7:57 am, Malte Meyn wrote: You don’t need this \partial 8*7. In fact it’s better to omit it for correct autobeaming and bar checks. (Your code gives a bar check warning.) Odd, there should not be any bar check failures. But I did not have access to my local LilyPond installation,

Re: strange time changes - req help

Am 28.03.20 um 15:30 schrieb Aaron Hill: Would something like this work? \version "2.20.0" {   \time 4/4   \partial 8*7 | b'2 4. \bar "||" You don’t need this \partial 8*7. In fact it’s better to omit it for correct autobeaming and bar checks. (Your code gives a bar check warning.

Re: strange time changes - req help

On 2020-03-28 6:27 am, Eby Mani wrote: I'm trying to typeset some Victorian choral music with some strange time changes that switch between. Attached samples. e.g. eg1, 4.5th beat of 4/4 time it goes to pickup bar (\partial 8) of 6/8 time. eg2, On the 5th beat of 6/8 time it goes to pickup bar(

Re: Strange gap-behaviour with whole-note tremolo Beams

Am Fr., 27. März 2020 um 14:51 Uhr schrieb Torsten Hämmerle : > > Thomas Morley-2 wrote > > I have no clue why this happens and where those added values came from. > > > > Any insights? > > > Hi Harm, > > > Believe it or not, this strange (and certainly unintended) effect is caused > by the thickne

Re: Strange gap-behaviour with whole-note tremolo Beams

Thomas Morley-2 wrote > I have no clue why this happens and where those added values came from. > > Any insights? Hi Harm, Believe it or not, this strange (and certainly unintended) effect is caused by the thickness of the invisible stems! The beam shortening will actually depend on the beam

Re: Strange gap-behaviour with whole-note tremolo Beams

Am Fr., 27. März 2020 um 13:48 Uhr schrieb Malte Meyn : > > > > Am 27.03.20 um 12:23 schrieb Thomas Morley: > > I have no clue why this happens and where those added values came from. > > > > Any insights? > > Wild guess, to be tested: ll. 558 ff. of beam.cc. > Hi Malte, I had a look, alas, with

Re: Strange gap-behaviour with whole-note tremolo Beams

Am 27.03.20 um 12:23 schrieb Thomas Morley: I have no clue why this happens and where those added values came from. Any insights? Wild guess, to be tested: ll. 558 ff. of beam.cc.

Re: Strange results from simultaneous RehearsalMarks

> Your code is based on a LSR-snippet, you may try some of the others dealing > with simultaneous RehearsalMarks. In particular: http://lsr.di.unimi.it/LSR/Item?id=735 http://lsr.di.unimi.it/LSR/Item?id=736 to prin

Re: Strange results from simultaneous RehearsalMarks

Am Sa., 27. Juli 2019 um 18:29 Uhr schrieb Patrick Karl : > I'm running LIlyPond 2.19.81 on a Mac desktop running OSX 10.11.6. > > I'm confused about the warnings generated by the following snippet: > > \version "2.19.81" \score { \new GrandStaff << \new Staff { > c'1\bar

Re: Strange space between beam and slur

Lukas-Fabian Moser writes: > Hi Andrew, > > Am 25.06.19 um 10:56 schrieb Andrew Bernard: >> What is it about 19? Is it some magic borderline number in some unit >> system in lilypond? Do we know? > > I'd rather suspect there's some kind of "anthropic principle" at work > here: The bugs (at least

Re: Strange space between beam and slur

Hi Andrew, Am 25.06.19 um 10:56 schrieb Andrew Bernard: What is it about 19? Is it some magic borderline number in some unit system in lilypond? Do we know? I'd rather suspect there's some kind of "anthropic principle" at work here: The bugs (at least the one I reported) should probably occur

Re: Strange space between beam and slur

What is it about 19? Is it some magic borderline number in some unit system in lilypond? Do we know? Andrew On Tue, 25 Jun 2019 at 15:49, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> wrote: > So possible workarounds: > #(set-global-staff-size 19.01) > or using: > \layo

Re: Strange space between beam and slur

So possible workarounds: #(set-global-staff-size 19.01) or using: \layout { #(layout-set-staff-size 19) } instead. Cheers, Pierre Le mar. 25 juin 2019 à 01:01, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> a écrit : > Hum, this staff-size 19 reminds me: > http://lilypond.

Re: Strange space between beam and slur

Hum, this staff-size 19 reminds me: http://lilypond.1069038.n5.nabble.com/misplacement-note-head-version-2-19-td211629.html Any posible relationship? Cheers, Pierre Le mar. 25 juin 2019 à 00:11, Thomas Morley a écrit : > Am So., 23. Juni 2019 um 11:59 Uhr schrieb Thomas Morley > : > [...] > Just

Re: Strange space between beam and slur

Am So., 23. Juni 2019 um 11:59 Uhr schrieb Thomas Morley : [...] Just reported in the german forum https://lilypondforum.de/index.php/topic,501.0.html \version "2.19.82" % problem occurs at staff-size 19, but does not occur at staff-size 18 or 20 #(set-global-staff-size 19) \new TabStaff \with {

Re: Strange space between beam and slur

Am So., 23. Juni 2019 um 10:54 Uhr schrieb Andrew Bernard : > > Hi Lukas, > > May be a bug, but I always use explicit voices, not '//' constructs. I > find it is just better but. > > You play with the rests, but this works: > > > \new Staff > << >{ > \voiceOne > R1 > a''8( b'' b'

Re: Strange space between beam and slur

Hi Lukas, May be a bug, but I always use explicit voices, not '//' constructs. I find it is just better but. You play with the rests, but this works: \new Staff <<   {     \voiceOne     R1     a''8( b'' b'' a'')   }   \new Voice {     \voiceTwo     R1     r2   } >> I'm aware this does not

Re: Strange space between beam and slur

Hi Carl, thanks for trying this (and forgive me for explicitly CC'ng you as the author of the commit that, on my system, triggered the problem)! On 6/22/19, 3:48 PM, "Lukas-Fabian Moser" wrote: That's about as much as I can contribute, I guess. Does anybody have an idea wh

Re: Strange space between beam and slur

On 6/22/19, 3:48 PM, "Lukas-Fabian Moser" wrote: That's about as much as I can contribute, I guess. Does anybody have an idea what precisely is causing the problem? Hmm, this works for me on 2.19.82 running on OSX under Frescobaldi. No extra space. What is your system conf

Re: Strange GS failure

On Mon, Jan 07, 2019 at 11:49:42AM +, Peter Toye wrote: > Brian, > > Thanks - that was it! Not a very helpful error message, is it? You get a slightly better one if you add the -V flag (verbose): Converting to `./test.pdf'... Invoking `gs -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPO

Re: Strange GS failure

Brian, Thanks - that was it! Not a very helpful error message, is it? Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Monday, January 7, 2019, 11:38:50 AM, Brian Barker wrote: > At 11:28 07/01/2019 +, you wrote: >>I've got two almost identical files, o

Re: Strange dotted slur which are not slurs or ties

Am 13.09.2018 um 15:29 schrieb Torsten Hämmerle: > > Phrasing slurs can be made dotted by \phrasingSlurDotted and they can be > made dashed by \phrasingSlurDashed. > > Thank you both,  Simon and Torsten Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kle...@gmx.net www.b-kleine.com, www.urse

Re: Strange dotted slur which are not slurs or ties

Bernhard Kleine wrote > But how make them dotted? Phrasing slurs can be made dotted by \phrasingSlurDotted and they can be made dashed by \phrasingSlurDashed. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing

  1   2   3   4   5   6   >