Re: partCombine Issues Warnings When Divisi Begins Within Tied Notes

Hello Chris, sorry for the late reply. > Issuing a \partCombineApart between two tied notes results in a > warning that the tie is unterminated and omits the tie from the > printed score. Printing the top part by itself creates the tie > without issues. > > Omitting the tie from the top

\partCombine \acciaccatura slashes other flags

The slash from the acciaccatura gets deported on all subsequent 8th flags. Is this a known bug ? \version "2.25.10" \partCombine {\acciaccatura {c''16 b'16} a'1| g'8 r r4 8 r8 8 8 | 8} {\acciaccatura {f'16 g'} a'1 | e'8 r r4 8 r8 8 8 | 8} Took me quite a while to figure what was goi

Re: Changed behaviour of tag and partCombine

Timothy, I'm looking into the issue. Does adding \tagGroup #'($partCombine) early in your score work around the problem? — Dan ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Changed behaviour of tag and partCombine

On 12/10/2021 22:55, Dan Eble wrote: Timothy, I'm looking into the issue. Does adding \tagGroup #'($partCombine) early in your score work around the problem? — Dan Yes, adding the \tagGroup does bring back the missing music. -- Timothy Lanfear, Bristol, UK

Re: Changed behaviour of tag and partCombine

Le 12/10/2021 à 22:31, Timothy Lanfear a écrit : From at least 2.18 to 2.23.3, it was possible to place \tag and \keepWithTag outside of \partCombine. Version 2.23.4 requires the tagging inside \partCombine. I do have a lot of files expecting the old behaviour. \version "2

Changed behaviour of tag and partCombine

From at least 2.18 to 2.23.3, it was possible to place \tag and \keepWithTag outside of \partCombine. Version 2.23.4 requires the tagging inside \partCombine. I do have a lot of files expecting the old behaviour. \version "2.22.1" {   \keepWithTag #'t \tag #'t \partCombin

Re: partCombine returns wrongly if \tags are used

Hello, On 27/12/2020 08:52, Thomas Morley wrote: the initial example works at least since 2.8.0 (yes, I've a working 2.8.0) A long time... Tbh, I couldn't figure why it works before 2.19.21, though, if it doesn't anymore, it should be documented either as it is done for \relative already or in

Re: partCombine returns wrongly if \tags are used

''2 \tag #'score f'' \tag #'part fis'' g''1 } > > two = { e''2 d'' g'1 } > > > > \removeWithTag #'score \partCombine \one \two > > %% end > > > > it looks like tags are not > > respected for the length of `skip`, but both are counted, thus the > >

Re: partCombine returns wrongly if \tags are used

On Dec 26, 2020, at 13:29, Thomas Morley wrote: > > Hi, > > the following code gives bad output. > > %% Start > \version "2.20.0" > > one = { e''2 \tag #'score f'' \tag #'part fis'' g''1 } > two = { e''2 d'' g'1 } > > \removeWithTag #'score \par

partCombine returns wrongly if \tags are used

Hi, the following code gives bad output. %% Start \version "2.20.0" one = { e''2 \tag #'score f'' \tag #'part fis'' g''1 } two = { e''2 d'' g'1 } \removeWithTag #'score \partCombine \one \two %% end Afaict, first bad commit is commit 615571eda2393eba537c3ad0eb2d424f8dd218b0 Author

Re: Doc-snippet "Two \partcombine pairs on one staff" broken

Am So., 30. Dez. 2018 um 12:00 Uhr schrieb Thomas Morley : > > Am So., 30. Dez. 2018 um 11:06 Uhr schrieb Thomas Morley > : > > > > Hi, > > > > out of > > https://lists.gnu.org/archive/html/lilypond-devel/2018-12/msg00178.html > > > > The do

Re: Doc-snippet "Two \partcombine pairs on one staff" broken

Am So., 30. Dez. 2018 um 11:06 Uhr schrieb Thomas Morley : > > Hi, > > out of https://lists.gnu.org/archive/html/lilypond-devel/2018-12/msg00178.html > > The doc-tagged LSR-snippet "Two \partcombine pairs on one staff" > http://lsr.di.unimi.it/LSR/Item?id=958 >

Doc-snippet "Two \partcombine pairs on one staff" broken

Hi, out of https://lists.gnu.org/archive/html/lilypond-devel/2018-12/msg00178.html The doc-tagged LSR-snippet "Two \partcombine pairs on one staff" http://lsr.di.unimi.it/LSR/Item?id=958 is obviously inspired by https://sourceforge.net/p/testlilyissues/issues/1321/?page=1=25#a054 Whil

Re: Partcombine Documentation: Example Error

Hello, On Thu, 19 Jul 2018 08:44:56 +0200, Thomas Morley wrote: ... > > Hi James, > > I've no clue why it happens, so I'd go for the symptom. Something like > "partcombine warns erroneously for unterminated slur". > > Cheers, > Harm Many

Re: Partcombine Documentation: Example Error

2018-07-18 15:03 GMT+02:00 James Lowe : > Hello, > > On Wed, 18 Jul 2018 09:09:15 +0200, Thomas Morley > wrote: > >> 2018-07-17 11:55 GMT+02:00 Ben : >> > Good morning, >> > >> > I've been reading up on partcombine recently and I wanted to tr

Re: Partcombine Documentation: Example Error

Hello, On Wed, 18 Jul 2018 09:09:15 +0200, Thomas Morley wrote: > 2018-07-17 11:55 GMT+02:00 Ben : > > Good morning, > > > > I've been reading up on partcombine recently and I wanted to try out a few > > examples from the documentation to help me really understand

Re: Partcombine Documentation: Example Error

2018-07-17 11:55 GMT+02:00 Ben : > Good morning, > > I've been reading up on partcombine recently and I wanted to try out a few > examples from the documentation to help me really understand the command, > however I get this error with one example: > > From: > > ht

Re: \partcombine looses quoted parts

Thanks for your report. This is an already known issue, see: https://sourceforge.net/p/testlilyissues/issues/1823/ Cheers, Harm 2017-09-25 20:51 GMT+02:00 Peter Häring : > > -- > Peter Häring > Dürmentinger Str. 15, 88521 Ertingen > Tel. 07371/129361 > Email:

\partcombine looses quoted parts

quot; \stimmeII %Parts, where the first note is not quoted, % the second is quoted from above instrumentI = \relative b' { b1 | \quoteDuring #"stI" { s1 } } instrumentII = \relative f' { f1 | \quoteDuring #"stII" { s1 } } % \partcombine works how it should for the parts

Re: partcombine does not work with tremolo repeats

Hi, thanks for the answer, but it still fails for a slightly more complicated example: \version "2.19.59" \score { \new Staff { \set Staff.autoBeaming = ##f \partcombine \relative c' { \time 3/4 \repeat tremolo 6 { c'16 [e16] } c4 d e c4 d e }

Re: partcombine does not work with tremolo repeats

"Ulrik Serges" <ul...@serges.dk> wrote in message news:6fdb4c7d-1f9c-3dea-59dd-fc5293e1c...@serges.dk... Hello, I have problems using tremolo repeats with partcombine. The following code returns errors and doesn't produce the correct output: \version "2.19.65" \n

partcombine does not work with tremolo repeats

Hello, I have problems using tremolo repeats with partcombine. The following code returns errors and doesn't produce the correct output: \version "2.19.65" \new Staff << \partcombine \relative c' { \time 3/4 \repeat tremolo 6 {e16 g16} e2. } \relative c' {

Re: \partcombine bugs

r = { \unfoldRepeats \four \bar "|." } ufive = { \unfoldRepeats \five \bar "|." } \markup { "\partcombing already unfolded music does work ..." } \score { \new ChoirStaff << \new Staff \ufour \new Staff \ufive \new Staff \partcombine \ufour

Re: \partcombine bugs

> For choral music it is an old convention to merge dynamics if time of start, > time of end, and target are all identical. I see. But wouldn't it be preference (style) rather than a bug? I suppose you want that to be the default to merge most(all?) dynamics? I used \partcombineChords in your

Re: \partcombine bugs

Hi Pierre-Luc! Concerning "Bug1", I do not think the \< \mp should be merged. The part combine in this section is using two voices. The notes are not connected. How would you know if the hairpin is for voiceTwo *and* voiceOne? For choral music it is an old convention to merge dynamics if

Re: \partcombine bugs

Hi Knut, Concerning "Bug1", I do not think the \< \mp should be merged. The part combine in this section is using two voices. The notes are not connected. How would you know if the hairpin is for voiceTwo *and* voiceOne? -- Pierre-Luc Gauthier ___

\partcombine bugs

t volta 2 { 4 4 4 4 } } four = { a'4\p 4 4 4 2\< 2 4\mp 4 4 4 \repeat volta 2 { 4 4 4 4 } 1 4 4 4 4} five = { d'4\p 4 4 4 4\< 4 4 4 4\mp 4 4 4 \repeat volta 2 { 4 4 4 4 } 1 4 4 4 4} \markup { "\partcombine works as expected"} \score { \new Staff \partcombine \one \two \la

Re: [partcombine] partcombine can't handle simultaneous hairpins

On Thu, Jun 8, 2017 at 9:51 PM, Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > > I see this is still a problem, so I thought I'd post it to -bug. > > %%% SNIPPET BEGINS > \version "2.19.61" > > musicA = { > g'1\> R1\! > } > musicB =

[partcombine] partcombine can't handle simultaneous hairpins

Hi all, I see this is still a problem, so I thought I'd post it to -bug. Regards, Kieren. %%% SNIPPET BEGINS \version "2.19.61" musicA = { g'1\> R1\! } musicB = { b'1\> R1\! } \new Staff \partcombine \musicA \musicB %%% SNIPPET ENDS

Re: problem with \partcombine and dynamics/hairpins

can get \partcombine into really great shape. It’s a wonderful tool, to the degree that it works. Best, Kieren. On Sep 25, 2016, at 3:55 PM, Urs Liska <u...@openlilylib.org> wrote: > Hi Kieren, > no time to really look into it. But in > https://git.openlilylib.org/bfsc/das-trunkne-l

Re: problem with \partcombine and dynamics/hairpins

Harm (et al.), Right after hitting “Send”, I realized the fix: ye olde empty chord! The version below seems to work fine in both MWE and — at least, on first glance — in my RWS (real-world score). Thanks! Kieren. %%% SNIPPET BEGINS \version "2.19.48" terminateHairpin =

Re: problem with \partcombine and dynamics/hairpins

Hi Harm, > below a very bad workaround, found deep, deep in the quick n' dirty junk room. Thanks for the attempt! Works great on this MWE… But in my real-world score, Lily’s long-standing \grace-timing “feature” (read: bug) comes crashing down. =( The hint/idea is possibly a good one,

Re: problem with \partcombine and dynamics/hairpins

gt; >> SNIPPET BEGINS >> \version "2.19.46" >> >> musicA = { >> g'1\> R1\! >> } >> musicB = { >> b'1\> R1\! >> } >> >> \new Staff \partcombine \musicA \musicB >> SNIPPET ENDS > I'm no

Re: problem with \partcombine and dynamics/hairpins

.46" >> >> musicA = { >> g'1\> R1\! >> } >> musicB = { >> b'1\> R1\! >> } >> >> \new Staff \partcombine \musicA \musicB >> SNIPPET ENDS > > >Kieren MacMillan, composer >‣ websi

problem with \partcombine and dynamics/hairpins

, “viable” does NOT include pulling all dynamics out of every part and putting them in separate dynamics variables to be simultaneous-ed in post-hoc… > SNIPPET BEGINS > \version "2.19.46" > > musicA = { > g'1\> R1\! > } > musicB = { > b'1\> R1\!

partcombine problem with double explicit beams and slurs [was: Re: three small bugs]

Hello Gilberto, On 27.10.2015 13:43, Gilberto Agostinho wrote: - no. 1: when two parts contain manual beams and slurs at the same point and one uses \partcombine, some warnings are outputs in the console: "unterminated beam" and "unterminated slur". It does output the mu

Re: partcombine problem with double explicit beams and slurs [was: Re: three small bugs]

Thanks a lot. -- View this message in context: http://lilypond.1069038.n5.nabble.com/three-small-bugs-tp182794p182984.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: bug report: partcombine and multi-measure rests

Dan Eble writes: > Simon Albrecht mail.de> writes: > >> On 18.10.2015 13:25, Gilberto Agostinho wrote: >> > Hi Simon, >> > >> > Thanks for the reply. I am not sure I understand your answer, do you >> > mean that in the tiny example I created I should simply have used a >> >

Re: bug report: partcombine and multi-measure rests

Simon Albrecht mail.de> writes: > On 18.10.2015 13:25, Gilberto Agostinho wrote: > > Hi Simon, > > > > Thanks for the reply. I am not sure I understand your answer, do you > > mean that in the tiny example I created I should simply have used a > > "Solo I" indication in the fourth bar instead

Re: bug report: partcombine and multi-measure rests

I forgot to mention: You can change this indication using \layout { \context { \Voice soloText = "Solo I" } } – at least I might like that better. the output should be at least equal Agreed. \version "2.19.28" { \partcombine {R1 | \partcombineApart r2 b' |

Re: bug report: partcombine and multi-measure rests

tcombineApart command is at the same position as the R1*N: \version "2.19.28" { \partcombine {\partcombineApart r2 b'2~ | 1 | \partcombineAutomatic c''1 |} {R1*2 | f'1 |} } Which outputs this (no solos, no single voice, just two voices apart as expected, regardless of full mea

Re: bug report: partcombine and multi-measure rests

priate to change the input code of either of the voices to make > up for deficiencies of the partcombiner – at least if you should need to > print both separately, and that’s part of the point in using \partcombine. Best, Gilberto On 17/10/15 20:30, Simon Albrecht wrote: Hello Gilbert

Re: bug report: partcombine and multi-measure rests

On 18.10.2015 13:25, Gilberto Agostinho wrote: Hi Simon, Thanks for the reply. I am not sure I understand your answer, do you mean that in the tiny example I created I should simply have used a "Solo I" indication in the fourth bar instead of using rests? No, the solo indication should be

Re: bug report: partcombine and multi-measure rests

howing that the second voice is silent. Yours, Simon On 14.10.2015 21:15, Gilberto Agostinho wrote: Hello all, I get strange results when I change the type of \partcombine (for instance, using \partcombineApart) when one of the parts is in the middle of a several bars long multi-measure rest: http://li

bug report: partcombine and multi-measure rests

Hello all, I get strange results when I change the type of \partcombine (for instance, using \partcombineApart) when one of the parts is in the middle of a several bars long multi-measure rest: http://lilypond.1069038.n5.nabble.com/file/n182372/39.png code

Re: feature request: turn partcombine to partCombine (camelCase)

Malte, On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > >

\partCombine problem with spanners

2nd note should be marked Solo. Instead, both the note and the full measure rest appear.Do you think this might be related to issues 4095 and 4454? \version 2.19.25 one = \relative c' {    c1\ | f\mf  } two = \relative c' {    c1\ | R\! |  } \score {   \new Staff { \partcombine \one \two

feature request: turn partcombine to partCombine (camelCase)

Hi list, the case of the ‘c’ in partcombine is inconsistent, confusing me every time I use \partcombine(Apart|Chords|…): \partcombine, \partcombineApart, … but \partCombineTextsOnNote, \partCombineListener I would suggest to change all occurences of ‘partcombine’ to ‘partCombine’. Why

Re: \partcombine error with hairpins

I was looking into the bug again and noticed something. If we include a note before that code the problem doesn't appear mus =  \relative {   b1  b'1\  1\  1\  1\!} \score {   \new Staff \partcombine \mus \mus} However, if we write a second voice that does a different thing the problem appears

Re: \partcombine error with hairpins

the problem doesn't appear mus = \relative { b1 b'1\ 1\ 1\ 1\! } \score { \new Staff \partcombine \mus \mus } However, if we write a second voice that does a different thing the problem appears again. mus = \relative { b1 b'1\ 1\ 1\ 1\! } musTwo = \relative { b1 b'1\ 1

Re: \partcombine error with hairpins

something. If we include a note before that code the problem doesn't appear mus = \relative { b1 b'1\ 1\ 1\ 1\! } \score { \new Staff \partcombine \mus \mus } However, if we write a second voice that does a different thing the problem appears again. mus = \relative { b1 b'1

Re: \partcombine error with hairpins

Am 22.06.2015 um 13:46 schrieb Miguel Jesus: I was looking into the bug again and noticed something. If we include a note before that code the problem doesn't appear mus =  \relative {   b1 b'1\ 1\ 1\ 1\! } \score {   \new Staff \partcombine \mus \mus } However, if we write a second

Re: \partcombine error with hairpins

Thank you, Simon. Next time I'll have a little more patience before I report a bug. On Wednesday, 17 June 2015, 15:46, Simon Albrecht simon.albre...@mail.de wrote: Hello Miguel, Am 17.06.2015 um 14:14 schrieb Miguel Jesus: I'm having a problem with \partcombine (I'm sorry

\partcombine error with hairpins

I'm having a problem with \partcombine (I'm sorry for the long examples but this is the code I'm working with right now). With this code the voices aren't combined properly: \language portugues \version 2.18.0 \layout { \context { \Score skipBars = ##t }} bassoonOneFileOne = \relative re

Re: \partcombine error with hairpins

Hello Miguel, Am 17.06.2015 um 14:14 schrieb Miguel Jesus: I'm having a problem with \partcombine (I'm sorry for the long examples but this is the code I'm working with right now). With this code the voices aren't combined properly: [snip] At first I thought it had to do with the spacer

Re: \partcombine causes wrong tuplet bracket when tuplet begins with rest

On Sat, May 16, 2015 at 07:36:30AM +0100, James Lowe wrote: On 15/05/15 22:38, H. S. Teoh wrote: [...] % - Note: this is not the same as issue 913; padding the first voice % to have the same length as the second does not change the wrong % tuple bracket. [...] Is this just another

Re: \partcombine causes wrong tuplet bracket when tuplet begins with rest

James Lowe pkx at gnu.org writes: On 15/05/15 22:38, H. S. Teoh wrote: % The triplet in the first argument to \partcombine is wrongly % formatted in the output; the tuplet bracket only spans the two quarter % rests, whereas it should span both rests and the single note. % % - Note

Re: \partcombine causes wrong tuplet bracket when tuplet begins with rest

On 15/05/15 22:38, H. S. Teoh wrote: % The triplet in the first argument to \partcombine is wrongly % formatted in the output; the tuplet bracket only spans the two quarter % rests, whereas it should span both rests and the single note. % % - Note: this is not the same as issue 913; padding

\partcombine causes wrong tuplet bracket when tuplet begins with rest

% The triplet in the first argument to \partcombine is wrongly % formatted in the output; the tuplet bracket only spans the two quarter % rests, whereas it should span both rests and the single note. % % - Note: this is not the same as issue 913; padding the first voice % to have the same length

Re: \partcombine interacts badly with \tag

H. S. Teoh hsteoh at quickfur.ath.cx writes: % Arguably, using \tag with \partcombine is a bad idea, since it can % easily result in constructs that are probably not representable in a % way that would make a subsequent \removeWithTag work correctly, but % Lilypond should at least give

\partcombine interacts badly with \tag

% \partcombine should have produced a combined staff containing d'1 in % the first bar, f'1 in the second and 3rd bars, and f' d'1 chords in % the next 2 bars. However, it seems to interact badly with \tag, and % the output has a missing f1' in the second bar, a stray rest in the % 3rd bar

Re: \partcombine interacts badly with \tag

H. S. Teoh hsteoh at quickfur.ath.cx writes: \score { \removeWithTag #'midi { \partcombine \fluteIPart \fluteIIPart } } Have you tried filtering before combining? \partcombine \removeWithTag #'midi \fluteIPart \removeWithTag #'midi \fluteIIPart -- Dan

Re: partcombine: incorrect glissando attachment

On Mar 14, 2015, at 07:05 , James Lowe p...@gnu.org wrote: On 14/03/15 04:34, Dan Eble wrote: \version 2.19.16 \score { \partcombine \relative { e'' e e c' } \relative { b'~ b \glissando e, g } } Is this related to https://code.google.com/p/lilypond/issues/detail?id=1321

Re: partcombine: spurious solo text

Dan Eble d...@faithful.be writes: \version 2.19.16 \score { \partcombine \relative { c''1 | } \relative { a'2. f4 } } That's issue 100 URL:https://code.google.com/p/lilypond/issues/detail?id=100. -- David Kastrup ___ bug-lilypond

Re: partcombine: incorrect glissando attachment

On 14/03/15 04:34, Dan Eble wrote: \version 2.19.16 \score { \partcombine \relative { e'' e e c' } \relative { b'~ b \glissando e, g } } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo

partcombine: spurious solo text

\version 2.19.16 \score { \partcombine \relative { c''1 | } \relative { a'2. f4 } } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

partcombine: incorrect glissando attachment

\version 2.19.16 \score { \partcombine \relative { e'' e e c' } \relative { b'~ b \glissando e, g } } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Problem with enharmonic tie in partcombine (can let LilyPond crash)

Hi, I encountered a strange crash that is related to enharmonic ties. I'm using an engraver that is passed a grob. One particular snippet of input code lets now crash LilyPond. I can't easily produce a compiling (i.e. crashing) example because it's quite intertwined with project specific

Re: Problem with enharmonic tie in partcombine (can let LilyPond crash)

Hi Urs, On Fri, Jan 16, 2015 at 6:01 AM, Urs Liska u...@openlilylib.org wrote: Hi, I encountered a strange crash that is related to enharmonic ties. I'm using an engraver that is passed a grob. One particular snippet of input code lets now crash LilyPond. I can't easily produce a

Re: \partcombine, trill spanner and acciaccatura

Am 28.10.2014 04:33, schrieb Dan Eble: Urs Liska ul at openlilylib.org writes: Hi all, I'm experiencing an issue with \partcombine. Consider the attached snippet and image. When there is an acciaccatura in one of the voices the trill spanner doesn't stop in the \partcombine-d voice

\partcombine, trill spanner and acciaccatura

Hi all, I'm experiencing an issue with \partcombine. Consider the attached snippet and image. When there is an acciaccatura in one of the voices the trill spanner doesn't stop in the \partcombine-d voice. It doesn't matter in which voice the acciaccatura is. \appoggiatura has the same

Re: \partcombine, trill spanner and acciaccatura

Urs Liska ul at openlilylib.org writes: Hi all, I'm experiencing an issue with \partcombine. Consider the attached snippet and image. When there is an acciaccatura in one of the voices the trill spanner doesn't stop in the \partcombine-d voice. It doesn't matter in which voice

Re: [LSR v.2.18] Hymn Template for per-voice music and \partcombine does not compile.

. This is verse one It is more fun } verseTwo = \lyricmode { \set stanza = #2. This is verse two It's good for you } \score { \new ChoirStaff \new Staff { \key d \major \new NullVoice = aligner \soprano \new Voice = upper \partcombine \soprano \alto

Re: [LSR v.2.18] Hymn Template for per-voice music and \partcombine does not compile.

2014-02-28 11:54 GMT+01:00 Ed Gordijn ed.klari...@gmail.com: Hi Pierre, The scheme code is no longer needed, you can get the same result with the attached file using standard syntax. I don't no if this makes the snippet obsolete. The use of NullVoice is well documented so what remains is the

[LSR v.2.18] Hymn Template for per-voice music and \partcombine does not compile.

Dear Squad, The following snippet : http://lsr.dsi.unimi.it/LSR/Item?id=653 from Carl Sorensen (see : http://lilypond.1069038.n5.nabble.com/hymns-chords-vs-voices-td41309.html) Does not compile on v2.18 nor v2.16 Terminal says : ../all/hymn-template-for-per-voice-music-and--partcombine.ly:7:23:

partcombine rest moves up with silent second voice

Hi, Using partcombine with a silent second voice (full rests r1 or R1) and the first voice starts on the last beat. It moves the quarter rest up. \version 2.18.0 musicI = { r2 r4 c''| c''1 } musicII = { r1 | r1 } \partcombine \musicI \musicII I posted this on the user list and Karol

Re: partcombine bug - missplaced rest

hi Karol anyway - I've entered a new issue in the tracker - thanks for your report! Eluze https://code.google.com/p/lilypond/issues/detail?id=3612thanks=3612ts=1381827371 -- View this message in context: http://lilypond.1069038.n5.nabble.com/partcombine-bug-missplaced-rest-tp152312p152328

partcombine bug - missplaced rest

Missplaced rest when notes are tied. \version 2.17.28 first = { c'1 d'1~ d'1 R1*4/4 } second = { R1*4/4*4 } \score { \new Staff \partcombine \first \second } ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Re: partcombine bug - missplaced rest

Karol Majewski-2 wrote Missplaced rest when notes are tied. please reduce your example to a tiny size - eg. 4/4 = 1 … ! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/partcombine-bug-missplaced-rest-tp152312p152319.html Sent from the Bugs mailing list archive

Re: More \quoteDuring problems, with and without \partcombine

insert the command /\partcombineChords/ just before the /\quoteDuring/ in the part, the partcombine then works as intended. So in your attached example, replace the line /fluteIINotes = { r4 \quoteDuring #violin2 { s2 } r4 | }/ with the line: /fluteIINotes = { \partcombineChords r4 \quoteDuring

Re: crash with \partcombine \repeat tremolo when voices cross

On Fri, May 17, 2013 at 4:41 AM, Eluze elu...@gmail.com wrote: reported in the French community http://lilypond-french-users.1298960.n2.nabble.com/Probleme-avec-repeat-tremolo-en-partcombine-tp7579661.html I couldn't find this in the many issues about \partcombine you can circumvent

crash with \partcombine \repeat tremolo when voices cross

reported in the French community http://lilypond-french-users.1298960.n2.nabble.com/Probleme-avec-repeat-tremolo-en-partcombine-tp7579661.html I couldn't find this in the many issues about \partcombine you can circumvent this problem by adding explicit beaming in both voices for the critical

sacredHarpHeads in partcombine sections

I'm not top posting! SacredHarpHeads aren't displayed in partcombine sections when the second part is at a higher pitch than the first part. \version 2.17.7 \key a \minor \partcombine \relative a' { \sacredHarpHeadsMinor a4 c4 a4 c4 } \relative a' { \sacredHarpHeadsMinor a4 a4 c4 c4

Re: sacredHarpHeads in partcombine sections

Steve Tarr wrote SacredHarpHeads aren't displayed in partcombine sections when the second part is at a higher pitch than the first part. \version 2.17.7 \key a \minor \partcombine \relative a' { \sacredHarpHeadsMinor a4 c4 a4 c4 } \relative a' { \sacredHarpHeadsMinor a4 a4 c4

Re: sacredHarpHeads in partcombine sections

in the way that I want. Expanding the example to show the three different approaches that I've tried: \version 2.17.7 PartOne = \relative a' { \sacredHarpHeads a4 c4 a4 c4 } PartTwo = \relative a' { \sacredHarpHeads a4 a4 c4 c4 } \partcombine \PartOne \PartTwo \PartOne \\ \PartTwo \new Staff

Re: sacredHarpHeads in partcombine sections

Hello Steve, 2012/11/28 Steve Tarr stevet19...@comcast.net If I use explicit voices for each part, the stem directions are handled independently for each voice so I lose the information that the voices are crossing over each other. (And I get warning messages about note collisions when I

Re: sacredHarpHeads in partcombine sections

as in my second example using ... \\ ... (as it should, since one is just a shortcut for the other). That is, I see both up and down stems on the unison first and fourth notes; they're not merged to a single note and stem as partcombine does. My larger goal is to highlight the differences

Re: sacredHarpHeads in partcombine sections

Hello, 2012/11/28 Steve Tarr stevet19...@comcast.net SacredHarpHeads aren't displayed in partcombine sections when the second part is at a higher pitch than the first part. \version 2.17.7 \key a \minor \partcombine \relative a' { \sacredHarpHeadsMinor a4 c4 a4 c4 } \relative

Re: partcombine detects Solo II, even though I force it to use separate voices with \partcombineApart

On Sat, Aug 25, 2012 at 04:01:48PM +0200, Reinhold Kainhofer wrote: In the attached minimal example I explicitly call \partcombineApart to force two separate voice. However, the partcombiner still detects the second quarter as SoloII. The correct solution would be to use automatically forced

partcombine detects Solo II, even though I force it to use separate voices with \partcombineApart

{ \partcombine \IVDuettFagIMusic \IVDuettFagIIMusic } % WORKAROUND: Explicitly force the second quarter as Apart, too. This is cumbersome and should NOT be required: IVDuettFagIIMusicWorkaround = \relative f

Partcombine bug

Hello list, I meet a buglet in partcombine: a slur is drawn across a rest when it shouldn't. This happens with 2.15.40 on ubuntu-64bit. The bug doesn't occur with 2.14. I attach a hopefully minimal example. Rutger \version 2.15.40 obI = { \key d \major \relative c'' { g4( fis g

Re: Partcombine bug

Hi Rutger, This isn't a critical regression, there are some new \partcombine* commands Reinhold supplied for getting round these restrictions using \partcombine. Your code should have given you a warning of this sort: /home/ian/Dropbox/MusicScoresDevelopment/Testpartcombine.ly:26:10: warning

Re: Partcombine bug

Rutger Hofman rut...@cs.vu.nl writes: Hello list, I meet a buglet in partcombine: a slur is drawn across a rest when it shouldn't. This happens with 2.15.40 on ubuntu-64bit. The bug doesn't occur with 2.14. I attach a hopefully minimal example. Since 2.15.40 the following highly relevant

Re: Partcombine bug

David Kastrup d...@gnu.org writes: Rutger Hofman rut...@cs.vu.nl writes: Hello list, I meet a buglet in partcombine: a slur is drawn across a rest when it shouldn't. This happens with 2.15.40 on ubuntu-64bit. The bug doesn't occur with 2.14. I attach a hopefully minimal example. Since

Re: Partcombine bug

On Tue, Jun 19, 2012 at 01:39:39PM +0200, Rutger Hofman wrote: Hello list, I meet a buglet in partcombine: a slur is drawn across a rest when it shouldn't. This happens with 2.15.40 on ubuntu-64bit. The bug doesn't occur with 2.14. I attach a hopefully minimal example. Thanks

Re: ending simultaneous slurs from partcombine

On Fri, 01 Jun 2012 14:49:33 -0700, Keith OHara k-ohara5...@oco.net wrote: Part-combining [...] LilyPond starts two slurs and lets one continue too long. Thank you, this has been entered as http://code.google.com/p/lilypond/issues/detail?id=2584

ending simultaneous slurs from partcombine

slurs and lets one continue too long. \version 2.15.39 \partcombine {e'2( f'4 g') g'2( f')} {c'2( f'4 g') e'2( d')} % Workarounds: % Prevent the part-combiner from switching states during the slur \partcombine {\partcombineChords e'2( f'4 g') \partcombineAutomatic g'2( f')} {c'2( f'4 g') e'2

Re: Issue 1967 in lilypond: \partcombine and slurs produce misleadingwarnings (when combining into chords)

lilyp...@googlecode.com wrote in message news:8-9567054385019064696-16094765952880031725-lilypond=googlecode@googlecode.com... Comment #8 on issue 1967 by gra...@percival-music.ca: \partcombine and slurs produce misleading warnings (when combining into chords) http://code.google.com/p

Re: Issue 1967 in lilypond: \partcombine and slurs produce misleading warnings (when combining into chords)

Comment #7 on issue 1967 by d...@gnu.org: \partcombine and slurs produce misleading warnings (when combining into chords) http://code.google.com/p/lilypond/issues/detail?id=1967 I've checked with an old Ubuntu binary install. 2.12.thelatest does not have the problem. 2.14.thelatest _has_

Re: Issue 1967 in lilypond: \partcombine and slurs produce misleading warnings (when combining into chords)

Comment #8 on issue 1967 by gra...@percival-music.ca: \partcombine and slurs produce misleading warnings (when combining into chords) http://code.google.com/p/lilypond/issues/detail?id=1967 I agree that this doesn't seem to have anything to do with EventChord changes, so of course David

  1   2   3   >