Re: Edition Engraver -- Bar 1

2018-04-07 Thread Craig Dabelstein
Here is an example of the problem. The EE overide is working in measure 3 but not measure 1. Craig On 8 April 2018 at 05:43, arnepe wrote: > good evening all, > (and hoping this post is related to the topic ...) > > I've just set up a small test-file case: > if a Score

Re: Edition Engraver -- Bar 1

2018-04-07 Thread arnepe
good evening all, (and hoping this post is related to the topic ...) I've just set up a small test-file case: if a Score starts with a \partial, the mod applied to 1 0/4 is mirrored on the upbeat as well (see MWE-bar1.ly ).

Re: Edition Engraver -- Bar 1

2018-04-07 Thread Stefano Troncaro
Hi Craig, Could you post a snippet of your code? I also had this problem before when Voices were being created automatically because of the way the code was structured. Maybe it's the same issue. 2018-04-07 4:08 GMT-03:00 Jan-Peter Voigt : > Hi Craig, > > I'll investigate that

Re: double bar number

2018-04-07 Thread bb
Thank you! That does the job! I tried something else but had no success. Now I know one first has to     \remove "Bar_number_engraver" in the \Score, than add the new one. I rdeduced the lines, obviously the code is still working? Great! Thanks! \version "2.18.2" chordsone = \chordmode { c1:7 

Re: double bar number

2018-04-07 Thread bb
Thak you! But this is not the solution. I want the bar numbers just above the note lines, separated from the chord names. Jazz players complain the bar numbers neighboring the chord names as in Jazz harmonies there sometimes are strange names of complicated chords. Regards Am 07.04.2018 um

Re: double bar number

2018-04-07 Thread Andrew Bernard
That prints the numbers high - I think the OP wants to avoid that. Have a look at this from the list, a possible answer. https://lists.gnu.org/archive/html/lilypond-user/2017-06/msg00382.html Andrew On 7 April 2018 at 23:22, Knute Snortum wrote: > Try this: > > \version

Re: double bar number

2018-04-07 Thread Knute Snortum
Try this: \version "2.19.80" chordsone = \chordmode { c1:7 f1:7 c1:7 } one = \relative c { \override Score.BarNumber.break-visibility = #all-visible \clef "bass_8" c,4 g' c, ges' | f c' f, des |c g' c, as' | } \score { << \new ChordNames { \chordsone } \new Staff

Re: Cross-staff chords question

2018-04-07 Thread Jacques Menu Muzhic
Thanks, Simon! JM > Le 7 avr. 2018 à 15:03, Simon Albrecht a écrit : > > On 07.04.2018 11:39, Jacques Menu Muzhic wrote: >> When a hand doesn’t play, is it best for the keyboard player to read rests >> or should skips be used instead? > > Definitely rests. Using skips

Re: Cross-staff chords question

2018-04-07 Thread Simon Albrecht
On 07.04.2018 11:39, Jacques Menu Muzhic wrote: When a hand doesn’t play, is it best for the keyboard player to read rests or should skips be used instead? Definitely rests. Using skips is the convention if that hand only switched to the other staff. There may be exceptions depending on

double bar number

2018-04-07 Thread bb
I want bar numbers for every bar and a low bar number position to avoid interference with the chord names. My first attempt shows two bar numbers one over the other. I do not want the second, the upper bar number. I cannot find a solution. Thanks for help. \version "2.19.80" chordsone =

Re: Cross-staff chords question

2018-04-07 Thread Jacques Menu Muzhic
Hello Andrew, When a hand doesn’t play, is it best for the keyboard player to read rests or should skips be used instead? JM > Le 7 avr. 2018 à 11:11, Andrew Bernard a écrit : > > Hi JM, > > Speaking as a keyboard player myself, it's not just a matter of presenting

Re: Cross-staff chords question

2018-04-07 Thread Jacques Menu Muzhic
Hello Rutger, Malte and Andrew, I overlooked \crossStaff and didn’t get the Span_stem_engraver should be used, sorry for that and for not removing the extraneous music in my last post. Thanks for your help, and a nice day! JM > Le 7 avr. 2018 à 11:11, Andrew Bernard

Re: Cross-staff chords question

2018-04-07 Thread Andrew Bernard
Hi JM, Speaking as a keyboard player myself, it's not just a matter of presenting the notes. Usually in contexts like this it can be an indication of which hand takes what, with the upper staff being the RH and the lower the LH. There's no hard and fast rule about that, (and some players don't

Re: Cross-staff chords question

2018-04-07 Thread Malte Meyn
Am 07.04.2018 um 10:51 schrieb Menu Jacques: I’m no pianist though: is this OK for a keyboard player, or is Finale’s output: […] better, and if so, how can I obtain the cross-staves stems this way? What is better depends on whether it should be played with one hand or two. Please always

Re: Cross-staff chords question

2018-04-07 Thread Rutger Hofman
Did you (following the manual http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-keyboards#cross_002dstaff-stems ): \layout { \context { \PianoStaff \consists #Span_stem_engraver } } to enable cross-staff stems? And did you (following the manual) specify

Re: Edition Engraver -- Bar 1

2018-04-07 Thread Jan-Peter Voigt
Hi Craig, I'll investigate that on Monday. I thought I fixed this issue a while ago, but if you are facing it now there still needs to be something to be done. Jan-Peter Am 7. April 2018 08:22:52 MESZ schrieb Craig Dabelstein : >Hi all, > >Is there something

Edition Engraver -- Bar 1

2018-04-07 Thread Craig Dabelstein
Hi all, Is there something strange about trying to reference the first beat of the first bar of a piece of music. My mods are all working except the one on the first beat of bar 1. \editionMod global 1 0/4 gossec.simphonie.clarinetII.Voice etc... Any ideas? Craig -- *Craig Dabelstein*