RE: Layout of a (piano) hand indicator

Hi everyone, I dig up this old topic because I need some help understanding this function. Simon has posted an interesting function which I would like to use: ... but I also would like to access some parameters in certain cases (let's say "rlineto 0 3" and "extra-offset #'(0.75 . 0)" with a sim

RE: Layout of a (piano) hand indicator

(* I forgot the function: hook = #(let ((direction? (lambda (n) (= 1 (abs n (hook-markup #{ \markup \path #0.12 #'((moveto 0 0) (rlineto -0.85 0) (rlineto 0 3)) #})) (define-event-functi

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Hello, Not sure whether this helps: removing: continue from the file, MuseScore 2.2.1 produces: Finale 2014 produces: and musicxml2ly produces: musicxml2ly: Reading MusicXML from O5beamWithoutBeamNumberContinue.xml_inter.xml ... musicxml2ly: Converting to LilyP

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Hello Urs, I’m doing tests with MusicXML, could you send me an example where MuseScore doesn’t show any beams after exporting from LilyPond? Thanks! JM > Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit : > > Hi Torsten, > > 5. Mai 2018 11:44, "Torsten Hämmerle" schrieb: > >> Hi Urs, >

Re: Layout of a (piano) hand indicator

Hello foxfanfare, I use this function from Simon a lot. Here's a way to add extra parameters to this function. As an example, this lets you specify the length of the hook. How is your Scheme coding skill? You'll notice the use of quasiquoting to get the length value where it is needed in the cas

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Hello Jacques, Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic: Hello Urs, I’m doing tests with MusicXML, could you send me an example where MuseScore doesn’t show any beams after exporting from LilyPond? Attached you'll find a simple nobeam.ly and the file nobeam.xml, which is the resu

Re: Layout of a (piano) hand indicator

I andrew, thanks for your help! Andrew Bernard wrote > How is your Scheme coding skill? Very low... but I'm learning! Your exemple was a big help, especially because the order of appearence of the elements in my function wasn't good and didn't allowed me to add a variable in the original markup

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Hello Urs, musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1 produces beams in both cases, i.e. even when there are no beams in the MusicXML data. Strange… JM > Le 6 mai 2018 à 11:09, Urs Liska a écrit : > > Hello Jacques, > > > Am 06.05.2018 um 10:11 schrieb Jacques Menu

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

On Sun, 6 May 2018, Urs Liska wrote: Attached you'll find a simple nobeam.ly and the file nobeam.xml, which is the result from exporting with the current master of python-ly. This will be opened without beams in MuseScore 2. I am getting beams in MuseScore 2.2.1, Linux Fedora 28. nobeam-wi

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

On Sun, 6 May 2018, Jacques Menu Muzhic wrote: musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1 produces beams in both cases, i.e. even when there are no beams in the MusicXML data. Strange… My guess is that MuseScore does things it isn't supposed to do. Which can some

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

The « bug » seems to have been introduced since MuseScore 2.2.x: 2.1.0 behaves as expected. JM > Le 6 mai 2018 à 11:51, Martin Tarenskeen a écrit : > > > > On Sun, 6 May 2018, Urs Liska wrote: > >> Attached you'll find a simple nobeam.ly and the file nobeam.xml, which is >> the result from

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Am 06.05.2018 um 11:43 schrieb Jacques Menu Muzhic: Hello Urs, musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1 produces beams in both cases, i.e. even when there are no beams in the MusicXML data. OK, that seems that between 2.1.0 and 2.2.1 MuseScore has added that feat

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

I’m not familiar with python.ly ’s internals: does it use LP’s internal description, shown below by \displayMusic? Starting lilypond 2.19.80 [nobeam.ly]... Processing `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-nx6e_mso/tmp2kwa263p/nobeam.ly' Parsing... Inter

Lilypond and Frescobaldi on Fedora 28

Hi, Official Fedora 28 version of lilypond 2.19.81 is currently broken. (I hope a fix will be found soon) As a workaround the install script for linux from http://lilypond.org/download/binaries/ can be used. This one works fine. If you install Frescobaldi from the official Fedora 28 repo it

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

Am 6. Mai 2018 12:08:39 MESZ schrieb Jacques Menu Muzhic : >I’m not familiar with python.ly ’s internals: does >it use LP’s internal description, shown below by \displayMusic? No, it parses the input file(s) - which points to the single most significant limitation of python-

Re: Layout of a (piano) hand indicator

On 06.05.2018 11:43, foxfanfare wrote: …… (define-event-function (direction on-line lenght offset) (direction? boolean? number? pair?) (let* ((self-al (if on-line 0 0.31)) (self-al (if (= direction 1) (- self-al) self-al)) (hook-markup #{

Re: Layout of a (piano) hand indicator

Simon Albrecht writes: > On 06.05.2018 11:43, foxfanfare wrote: > > …… >> (define-event-function (direction on-line lenght offset) >> (direction? boolean? number? pair?) >> (let* ((self-al (if on-line 0 0.31)) >> (self-al (if (= direction 1) (- self-al) self-a

Re: Layout of a (piano) hand indicator

Simon Albrecht-2 wrote > Please don’t infinitely propagate typos. It’s called ‘length’ in English. Sorry but I'm no native speacker... ...pardon my French :) -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing

\RemoveEmptyStaves removes Dynamics context

Can anybody help me with keeping the dynamics alive?  Many thanks! dynamics = {s1\p} music = {c'1} \layout {   \context {     \Score     \RemoveEmptyStaves     \override VerticalAxisGroup.remove-first = ##t   } } \score {   <<     \new Staff \music     \new Dynamics \dynamics   >> }

Re: \RemoveEmptyStaves removes Dynamics context

Am 06.05.2018 um 22:35 schrieb Thomas Weber: Can anybody help me with keeping the dynamics alive?  Many thanks! […] \layout {   \context {     \Score Replace \Score by \Staff here.     \RemoveEmptyStaves     \override VerticalAxisGroup.remove-first = ##t   } } _

Re: Layout of a (piano) hand indicator

Hi, I've read your post in the morning and some things in Simon's function were obvious to impove. But then I started testing use-cases and noticed the problem is very complex, if you try a high amount of automatism (but still with the possibility for the user to adjust values). Some points of the

Re: Layout of a (piano) hand indicator

Thomas Morley-2 wrote > Below my own attempt. > The function has an optional argument, `details', for finetuning. Ooo... Thank you very much Harm! This looks amazing :) I'll try to play with this tomorrow and tell you how it works for me :-) -- Sent from: http://lilypond.1069038.n5.nabble.com/U

Re: \RemoveEmptyStaves removes Dynamics context

On 06.05.2018 23:03, Malte Meyn wrote: Am 06.05.2018 um 22:35 schrieb Thomas Weber: Can anybody help me with keeping the dynamics alive?  Many thanks! […] \layout {    \context { \Score Replace \Score by \Staff here. \RemoveEmptyStaves \override VerticalAxisGroup.remove-first