Re: musicxml2ly: import chordnames attached to empty measures or whole rests?

Much appreciated! On Wed, Oct 13, 2021 at 12:41 PM Jean Abou Samra wrote: > Le 11/10/2021 à 22:37, leonardlthomp...@gmail.com a écrit : > > Hello! > > It seems that musicxml2ly won't create a chordname if the corresponding > > harmony element in the musicxml file is attac

Re: musicxml2ly: import chordnames attached to empty measures or whole rests?

Le 11/10/2021 à 22:37, leonardlthomp...@gmail.com a écrit : Hello! It seems that musicxml2ly won't create a chordname if the corresponding harmony element in the musicxml file is attached to an empty whole rest measure. Works just fine with a chord symbol attached to a single quarter rest

musicxml2ly: import chordnames attached to empty measures or whole rests?

Hello! It seems that musicxml2ly won't create a chordname if the corresponding harmony element in the musicxml file is attached to an empty whole rest measure. Works just fine with a chord symbol attached to a single quarter rest, for example, even in a measure of only quarter rests. Would

Re: ModuleNotFoundError while doing musicxml2ly

23:04 +0200 schrieb Thomas Morley: > > > > Hi, > > > > > > > > testing a new patch locally a .xml-file popped up. > > > > > > > > While having a closer look I tried to convert it to a ly-file with > > > > ~$

Re: ModuleNotFoundError while doing musicxml2ly

.xml-file popped up. > > > > > > While having a closer look I tried to convert it to a ly-file with > > > ~$ lilypond-git/build/out/bin/musicxml2ly > > > lilypond-git/input/regression/musicxml/71d-ChordsFrets-Multistaff.xml > > > > > > --> > &g

Re: ModuleNotFoundError while doing musicxml2ly

-file with > > ~$ lilypond-git/build/out/bin/musicxml2ly > > lilypond-git/input/regression/musicxml/71d-ChordsFrets-Multistaff.xml > > > > --> > > > > Traceback (most recent call last): > > File "lilypond-git/build/out/bin/musicxml2ly", line 38,

Re: ModuleNotFoundError while doing musicxml2ly

Am Mittwoch, den 29.07.2020, 23:04 +0200 schrieb Thomas Morley: > Hi, > > testing a new patch locally a .xml-file popped up. > > While having a closer look I tried to convert it to a ly-file with > ~$ lilypond-git/build/out/bin/musicxml2ly > lilypond-git/input/regression/mus

ModuleNotFoundError while doing musicxml2ly

Hi, testing a new patch locally a .xml-file popped up. While having a closer look I tried to convert it to a ly-file with ~$ lilypond-git/build/out/bin/musicxml2ly lilypond-git/input/regression/musicxml/71d-ChordsFrets-Multistaff.xml --> Traceback (most recent call last): File "lily

Re: Doc: Minor typo (missing dash) in MusicXML2ly usage (issue 551800043 by michael.kaepp...@googlemail.com)

Am 22.04.2020 um 22:16 schrieb fedel...@gmail.com: On 2020/04/21 16:24:47, michael.kaeppler wrote: Hope this is the right way to submit translation fixes. Any advice is appreciated. I think goin' through Rietveld is overkill in this case. You'd better send a git formatted patch to

Re: Doc: Minor typo (missing dash) in MusicXML2ly usage (issue 551800043 by michael.kaepp...@googlemail.com)

On 2020/04/21 16:24:47, michael.kaeppler wrote: > Hope this is the right way to submit translation fixes. Any advice is > appreciated. I think goin' through Rietveld is overkill in this case. You'd better send a git formatted patch to lilypond-devel or translation mailing lists. Patch should be

Doc: Minor typo (missing dash) in MusicXML2ly usage (issue 551800043 by michael.kaepp...@googlemail.com)

Reviewers: , Message: Hope this is the right way to submit translation fixes. Any advice is appreciated. Description: Doc: Minor typo (missing dash) in MusicXML2ly usage Please review this at https://codereview.appspot.com/551800043/ Affected files (+1, -1 lines): M Documentation/de/usage

Re: musicxml2ly: Emit bar checks for all voices (issue 553620043 by jonas.hahnf...@gmail.com)

uot;print bar checks between measures", thanks for the suggestion. Description: musicxml2ly: Emit bar checks for all voices The script only added them for the first voice, without explanation. As this change doesn't seem to cause any problems, it's probably fine to lift this restriction

musicxml2ly: Emit bar checks for all voices (issue 553620043 by jonas.hahnf...@gmail.com)

https://codereview.appspot.com/553620043/diff/581760043/scripts/musicxml2ly.py File scripts/musicxml2ly.py (right): https://codereview.appspot.com/553620043/diff/581760043/scripts/musicxml2ly.py#newcode2287 scripts/musicxml2ly.py:2287: if n._measure_position == Rational(0) and n !=

Re: musicxml2ly: portugues notenames and quarternotes in español (issue 571630043 by d...@gnu.org)

Pls see my comment about a patch introducing full quarter tone support for all the languages - including a complete and consistent MusicXML import language support. I've asked on dev list about introducing català and português as "official" consistent proper language names. It's already included

Re: musicxml2ly: portugues notenames and quarternotes in español (issue 571630043 by d...@gnu.org)

On 2020/02/15 16:58:45, hanwenn wrote: > https://codereview.appspot.com/571630043/diff/561450045/python/musicexp.py > File python/musicexp.py (right): > > https://codereview.appspot.com/571630043/diff/561450045/python/musicexp.py#newcode364 > python/musicexp.py:364: function_dict = { > I meant

Re: musicxml2ly: portugues notenames and quarternotes in español (issue 571630043 by d...@gnu.org)

https://codereview.appspot.com/571630043/diff/561450045/python/musicexp.py File python/musicexp.py (right): https://codereview.appspot.com/571630043/diff/561450045/python/musicexp.py#newcode364 python/musicexp.py:364: function_dict = { I meant something like # this map should be synchronized

Re: musicxml2ly: portugues notenames and quarternotes in español (issue 571630043 by d...@gnu.org)

https://codereview.appspot.com/571630043/diff/567240043/python/musicexp.py File python/musicexp.py (right): https://codereview.appspot.com/571630043/diff/567240043/python/musicexp.py#newcode375 python/musicexp.py:375: "portugues": pitch_portugues, On 2020/02/15 12:29:01, dak wrote: > On

Re: musicxml2ly: portugues notenames and quarternotes in español (issue 571630043 by d...@gnu.org)

5 12:19:54, hanwenn wrote: > português I don't think it makes sense to use anything here that doesn't match the notename language defined in scm/define-note-names.scm . There is not even an alias português there. Description: musicxml2ly: portugues notenames and quarternotes in español Giv

musicxml2ly: portugues notenames and quarternotes in español (issue 571630043 by d...@gnu.org)

https://codereview.appspot.com/571630043/diff/567240043/python/musicexp.py File python/musicexp.py (right): https://codereview.appspot.com/571630043/diff/567240043/python/musicexp.py#newcode375 python/musicexp.py:375: "portugues": pitch_portugues, português

Re: wrong note name conversion in musicxml2ly

hat as an independent vote that this might be the sanest extension into quarternote territory. > On 2/9/20 5:52 PM, David Kastrup wrote: >> mari+lilyp...@mailbox.org writes: >> >>>> On 2/9/20 1:49 PM, David Kastrup wrote: >>>>> mari+lilyp...@mailbox.org

Re: wrong note name conversion in musicxml2ly

mari+lilyp...@mailbox.org writes: >> On 2/9/20 1:49 PM, David Kastrup wrote: >>> mari+lilyp...@mailbox.org writes: >>> >>>> when converting a mxl file with "musicxml2ly --language=deutsch" the >>>> note "beses" is converted to

Fw: Errors with midi2ly and musicxml2ly

Verzonden vanaf mijn Huawei mobiele telefoon Oorspronkelijk bericht Onderwerp: Re: Errors with midi2ly and musicxml2ly Van: m.tarensk...@zonnet.nl Aan: Aaron Hill Cc: There are more python2 vs python3 issues in those scripts than just that one. You

Re: musicxml2ly: handle hidden time signatures; support text+bpm \tempo marks. (issue 344000043 by a.mylt...@gmail.com)

On 2018/06/13 14:38:23, lilypond-pkx wrote: On 2018/06/04 10:51:25, a.myltsev wrote: > Removed the 'test' commits, leaving only changes to Python files. Patch counted down - please push. Alex if you do not have commit access can you attach a git-formatted patch (re-based against current

Re: musicxml2ly: handle hidden time signatures; support text+bpm \tempo marks. (issue 344000043 by a.mylt...@gmail.com)

On 2018/06/04 10:51:25, a.myltsev wrote: Removed the 'test' commits, leaving only changes to Python files. Patch counted down - please push. Alex if you do not have commit access can you attach a git-formatted patch (re-based against current master) and I can push it for you - attach it to the

Re: musicxml2ly: handle hidden time signatures; support text+bpm \tempo marks. (issue 344000043 by a.mylt...@gmail.com)

On 2018/06/01 20:12:25, a.myltsev wrote: > What are the scripts these 'test' dirs? Those are actual tests for the added functionality, runnable with `pytest`. > Was this a mistake? No, I believe that these tests are individually useful, even though not yet integrated into the Lilypond

Re: musicxml2ly: handle hidden time signatures; support text+bpm \tempo marks. (issue 344000043 by a.mylt...@gmail.com)

What are the scripts these 'test' dirs? Those are actual tests for the added functionality, runnable with `pytest`. Was this a mistake? No, I believe that these tests are individually useful, even though not yet integrated into the Lilypond testing system. If you prefer, though, I can leave

Re: musicxml2ly: handle hidden time signatures; support text+bpm \tempo marks. (issue 344000043 by a.mylt...@gmail.com)

On 2018/06/01 11:50:31, a.myltsev wrote: musicxml2ly: hidden timesigs and tempo marks with text. What are the scripts these 'test' dirs? Was this a mistake? If so can you re-submit the patch please? thanks James https://codereview.appspot.com/34443

RE: crash during musicxml2ly

Hello, Thanks Regards, GOHIER Frédéric De : James Lowe <james.l...@runbox.com> Envoyé : lundi 7 mai 2018 10:13 À : James Lowe Cc : Frédéric Gohier; lilypond-devel Objet : Re: crash during musicxml2ly Frederic On Wed, 02 May 2018 12:09:37 +0100 (BST),

Re: crash during musicxml2ly

Frederic On Wed, 02 May 2018 12:09:37 +0100 (BST), "James Lowe" wrote: > Hello Frederic, > > On Tue, 1 May 2018 16:47:24 +, Frédéric Gohier > wrote: > > > hello, > > > > I just push the patch on rietveld : > >

Re: crash during musicxml2ly

Hello Frederic, On Tue, 1 May 2018 16:47:24 +, Frédéric Gohier wrote: > hello, > > I just push the patch on rietveld : https://codereview.appspot.com/339560043/ > > Thank you, I have created https://sourceforge.net/p/testlilyissues/issues/5317/ for this issue. I

Re: [PATCH] musicxml2ly fix for lyrics when chord is present (fixes 61e)

Vincent, On 29/11/16 09:50, Vincent Le Ligeour wrote: > As commented in the patch I did not find any documentation if a chord > element can contain multiple lyrics, so I just assumed that the first note > of the chord contained the lyrics (consistant with Finale and Muscore > exports). Thanks,

[PATCH] musicxml2ly fix for lyrics when chord is present (fixes 61e)

Hello, This patch should fix the musicxml regression tests that have both lyrics and chords (for example 61e). As commented in the patch I did not find any documentation if a chord element can contain multiple lyrics, so I just assumed that the first note of the chord contained the lyrics

Re: Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

David Nalesnik writes: > On Wed, Oct 12, 2016 at 5:52 AM, David Kastrup wrote: > >> Bonus points for recognizing the fragment... > > Toccata and Fugue in D minor, BWV 565? Ah, I should have removed the treble staff altogether so that you'd have been

Re: Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

On Wed, Oct 12, 2016 at 5:52 AM, David Kastrup wrote: > Bonus points for recognizing the fragment... Toccata and Fugue in D minor, BWV 565? DN P.S. Sorry, nothing apropos the main topic! ___ lilypond-devel mailing list

Re: Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

Johan Vromans writes: >> > The bottom line is: What is required in chord c:blah so that .NN can >> > be added as a pure addition. It is unfortunate that c:.13 is invalid >> > syntax. > > Since MusicXML additions are pure additions, would it be safe to turn these > into

Re: Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

> > The bottom line is: What is required in chord c:blah so that .NN can > > be added as a pure addition. It is unfortunate that c:.13 is invalid > > syntax. Since MusicXML additions are pure additions, would it be safe to turn these into (addNN)? E.g. C + 13 => c:(add13) Even though that

Re: Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

On 2016/10/07 17:31:40, jvromans_squirrel.nl wrote: While we're at it: A couple of lines later (line 1617): if self.bass: value += "/+%s" % self.bass.ly_expression () AFAIK, a bass note is written as /c, not /+c. An inversion is written as /c but an additional bass

Re: Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

On 2016/10/07 17:31:40, jvromans_squirrel.nl wrote: On Fri, 07 Oct 2016 07:45:53 -0700 mailto:d...@gnu.org wrote: > https://codereview.appspot.com/305700043/diff/1/python/musicexp.py > File python/musicexp.py (right): > >

Re: Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

On Fri, 07 Oct 2016 07:45:53 -0700 d...@gnu.org wrote: > https://codereview.appspot.com/305700043/diff/1/python/musicexp.py > File python/musicexp.py (right): > > https://codereview.appspot.com/305700043/diff/1/python/musicexp.py#newcode1608 > python/musicexp.py:1608: # digit. If none, omit the

Re: Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

https://codereview.appspot.com/305700043/diff/1/python/musicexp.py File python/musicexp.py (right): https://codereview.appspot.com/305700043/diff/1/python/musicexp.py#newcode1608 python/musicexp.py:1608: # digit. If none, omit the ".". I think this behavior is wrong since the first digit is

Musicxml2ly: Fix incorrect conversion of Minor Chords (issue 305700043 by pkx1...@gmail.com)

Reviewers: , Message: Patch on countdown for October 11th Description: Musicxml2ly: Fix incorrect conversion of Minor Chords Issue 4980 The solutions for the invalid combinations are provided in python/musicexp.py. A colon is added if a colon-less chord (i.e., major) has modifications. Adding

Reimplement issue 4781 for musicxml2ly more literally. (issue 302050043 by j...@weathervanefarm.net)

Reviewers: , Message: Issue 4781 is reimplemented as requested by David Kastrup. Description: Reimplement issue 4781 for musicxml2ly more literally. Reimplementation was necessary as part of the implementation of issue 4751, but some of the code changes for 4781 were omitted. This reproduces

Possible errors reimplementing musicxml2ly fix for issue 4581

of changes into musicxml2ly that were made over several years separately from LilyPond in the Philomelos project. Not fully understanding the Philomelos changes, I opted to preserve the Philomelos code when it seemed to work rather than recreating the latest LilyPond code. The effect

Make additional changes to the new version of musicxml2ly (issue 297370043 by j...@weathervanefarm.net)

Reviewers: , Message: A few days a go I uploaded a new patch for issue 4751, "Import Philolelos enhancements to musicxml2ly", the first patch for which had been flagged as needing work. I hope this version works better. Description: Make additional changes to the new version of m

Re: [PATCH] musicxml2ly: Make sure movement_title exists before using it

Hello, On 13/12/15 21:32, Thomas Weber wrote: > fixed problem and was generated by Sibelius' internal MusicXML export > functionality (not Dolet). Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4699/ Thanks James ___

Re: [PATCH] musicxml2ly: Avoid duplicate "tr" if both and, are present

Am 15.12.2015 um 09:06 schrieb James: > Ticket created at: > https://sourceforge.net/rest/p/testlilyissues/issues/4698/ http://sourceforge.net/p/testlilyissues/issues/4698/ ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: [PATCH] musicxml2ly: Avoid duplicate "tr" if both and, are present

Hello, On 13/12/15 21:48, Thomas Weber wrote: > In situations like this: > > > > > this will be created: > > \trill \startTrillSpan > > It should only be \startTrillSpan Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4698/ Thanks James

Re: [PATCH] musicxml2ly: Avoid duplicate "tr" if both and, are present

Thomas, On 13/12/15 21:48, Thomas Weber wrote: > Another patch for musicxml2ly: In situations like this: > > > > > this will be created: > > \trill \startTrillSpan > > It should only be \startTrillSpan. > > (My changes can also be found on Githu

[PATCH] musicxml2ly: Make sure movement_title exists before using it

Here's a little trivial patch to musicxml2ly. The attached MusicXML file triggers the fixed problem and was generated by Sibelius' internal MusicXML export functionality (not Dolet). Best, Thomas Weber >From 12576c27e26693832659602bf883a3d08b04fa78 Mon Sep 17 00:00:00 2001 From: Thomas We

[PATCH] musicxml2ly: Avoid duplicate "tr" if both and, are present

Another patch for musicxml2ly: In situations like this: this will be created: \trill \startTrillSpan It should only be \startTrillSpan. (My changes can also be found on Github: https://github.com/th-we/lilypond.) Greets, Thomas Weber >F

Re: musicxml2ly tremolo tag on notes shorter than quarter

On Tue, 12 May 2015, pls wrote: For example what happened with the Philomenos musixcml2ly-dev fork? Yes, Philomelos is still alive and I’m about to update the musicxml2ly-dev Github repo.  Over at least three years I have written almost 100 bug reports  and many test cases

Re: merging philomelos musicxml2ly-dev

becoming so far apart in terms of codebase that nothing gets fixed or that LilyPond's musicxml2ly becomes so far behind philomelos to be worse than useless and we might as well remove musicxml2ly from the code and just point to Philomelos. Would it be an idea to freeze development of musicxml2ly

Re: musicxml2ly output indentation style

On Sat, 16 Nov 2013, Peter Bjuhr wrote: On 11/14/2013 09:16 AM, Martin Tarenskeen wrote: Hi, The lilypond output that is produced from musicxml2ly uses another indentation style than I see in my own scores when using for example Vim or Frescobaldi, or in all examples in the Lilypond

Re: musicxml2ly output indentation style

On 11/17/2013 07:02 PM, Martin Tarenskeen wrote: I did a short try with the dev version from Github (downloaded zip there) but I see no difference. Still had to use Tools-Format manually. Sorry for a stupid question, but did you install after download? But even if it works, it would

Re: musicxml2ly output indentation style

Peter Bjuhr peterbj...@gmail.com schrieb: On 11/14/2013 09:16 AM, Martin Tarenskeen wrote: Hi, The lilypond output that is produced from musicxml2ly uses another indentation style than I see in my own scores when using for example Vim or Frescobaldi, or in all examples in the Lilypond

Re: musicxml2ly output indentation style

On 11/14/2013 09:16 AM, Martin Tarenskeen wrote: Hi, The lilypond output that is produced from musicxml2ly uses another indentation style than I see in my own scores when using for example Vim or Frescobaldi, or in all examples in the Lilypond documentation. for example: %commonly used

musicxml2ly output indentation style

Hi, The lilypond output that is produced from musicxml2ly uses another indentation style than I see in my own scores when using for example Vim or Frescobaldi, or in all examples in the Lilypond documentation. for example: %commonly used style music = \relative c' { a b c d

Fwd: New Feature: musicxml2ly should consider colors of noteheads and stems

Forwarding to devel list - this is more patch proposal than bug report. Please comment if we need tracker issue for this... -- Forwarded message -- From: DaLa d.la...@gmx.de Date: 2013/7/20 Subject: New Feature: musicxml2ly should consider colors of noteheads and stems To: bug

musicxml2ly

Hey all,we have been working on solutions for old musicxml2ly-bugs and some new functions. We have published our efforts onhttps://github.com/Philomelos/lilypond-musicxml2ly-dev. We will continue working on musicxml2ly but there are far more bugs than we could ever handle on our own. So if no one

Re: Fix for several musicxml2ly bugs. (issue 5697059)

Hey Julien, thanks a million! Cheers, patrick http://codereview.appspot.com/5697059/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Fix for several musicxml2ly bugs. (issue 5697059)

Hi Patrick, A cleaned up version of this patch has been committed (and credited to you), so you may close this Rietveld issue. You will see the fix in version 2.15.41, the next development release. Cheers, Julien http://codereview.appspot.com/5697059/

musicxml2ly: Fix title, chord symbol and midi bugs. (issue 6330046)

LGTM http://codereview.appspot.com/6330046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: musicxml2ly

the staff. I remember this had been fixed in one of the previous lilypond 2.15.x versions, but with musicxml2ly from Lilypond 2.15.37 I am still (again?) having this problem. Same with 2.15.38 Hi, I did not see a reaction to this question, so I try again. What happened with this musicxml2ly bug

Re: musicxml2ly

On Wed, May 16, 2012 at 09:33:09AM +0200, Martin Tarenskeen wrote: I did not see a reaction to this question, so I try again. What happened with this musicxml2ly bug ? First chords were printed below the staff, then I think it was fixed, and now the chords are below the staff again

Re: musicxml2ly

of above the staff. I remember this had been fixed in one of the previous lilypond 2.15.x versions, but with musicxml2ly from Lilypond 2.15.37 I am still (again?) having this problem. Same with 2.15.38 I did not see a reaction to this question, so I try again. What happened

Re: musicxml2ly

It's not a regression. It has never been officially fixed. A while ago I posted a bug report and a minimal example: http://old.nabble.com/musicxml2ly%3A-chordnames-placement-bug-td33309393.html. Here is a solution for the chord symbol bug: http://codereview.appspot.com/5697059/. I still

Re: musicxml2ly

On Wed, May 16, 2012 at 10:42:09AM +0200, pls wrote: It's not a regression. It has never been officially fixed. A while ago I posted a bug report and a minimal example: http://old.nabble.com/musicxml2ly%3A-chordnames-placement-bug-td33309393.html. Here is a solution for the chord symbol bug

Re: musicxml2ly

. I remember this had been fixed in one of the previous lilypond 2.15.x versions, but with musicxml2ly from Lilypond 2.15.37 I am still (again?) having this problem. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org

musicxml2ly

Hi, There have been many requests from several people for Lilypond-to-MusicXML conversion. I am not going to repeat that question. We do have a musicxml2ly script. I have tried it with many example xml and mxl files from here: http://www.makemusic.com/musicxml/music/example-set and here

Re: musicxml2ly

Hello, On 8 April 2012 17:47, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: ... Or are many problems already known? http://code.google.com/p/lilypond/issues/list?can=2q=musicxmlsort=prioritycolspec=IDx=typey=prioritymode=gridcells=tiles There is also this recent - seemingly unfinished patch

Re: musicxml2ly

Hi Martin, yes, we are currently working on the musicxml2ly scripts and we have solved e.g. the issue concerning the chord symbols you mentioned. I haven't had time to work on the patch James pointed to but it works as it is. We use it on www.philomelos.net. Philomelos is a new community site

Re: musicxml2ly

On 2012-04-08 20:15, pls wrote: yes, we are currently working on the musicxml2ly scripts and we have solved e.g. the issue concerning the chord symbols you mentioned. I haven't had time to work on the patch James pointed to but it works as it is. We use it on www.philomelos.net http

Re: Fix for several musicxml2ly bugs. (issue 5697059)

://code.google.com/p/lilypond/issues/detail?id=1983 -) http://old.nabble.com/musicxml2ly%3A-chordnames-placement-bug-td33309393.html -) http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg00519.html I also added 2 lines to Usage as the new command line options -m and --midi hadn't been added yet. Beyond

Re: Fix for several musicxml2ly bugs. (issue 5697059)

://code.google.com/p/lilypond/issues/detail?id=1983 This sounds very straightforward; can you cook up a small patch restricted to this item alone -) http://old.nabble.com/musicxml2ly%3A-chordnames-placement-bug-td33309393.html This one sounds like issue 1969, and could probably be added as a comment

Re: Fix for several musicxml2ly bugs. (issue 5697059)

This patch is not associated with any issue in the bug tracker. It will not get a proper review until it is added there, and the automatic testing shows that it does not cause any unexpected problems. Should it be added to issue 1983, or is it sufficiently different that we should open a new

Re: Fix for several musicxml2ly bugs. (issue 5697059)

On 2012/02/29 22:33:45, Julien Rioux wrote: So please revert the changes to musicxml.py I mean musicxml2ly.py http://codereview.appspot.com/5697059/ ___ lilypond-devel mailing list lilypond-devel@gnu.org

Fix for several musicxml2ly bugs. (issue 5697059)

Reviewers: , Description: Fix for several musicxml2ly bugs. musicxml2ly: title, chord symbol and midi bug Titles and headers can now contain single words followed by a punctuation mark (.,!:). See issue 1983. Chord symbols are now placed above staffs instead of below. musicxml2ly now

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

2012/1/16 pls p.l.schm...@gmx.de: BTW: http://codereview.appspot.com/5303063/ is still open and hasn't been pushed. Oops! Looks like this patch slipped through the cracks because it wasn't mentioned in tracker issue 1985. I'm adding it now, it should be checked soon. thanks, Janek

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

Hi Janek, done! Thanks patrick BTW: http://codereview.appspot.com/5303063/ is still open and hasn't been pushed. Am 16.01.2012 um 00:07 schrieb Janek Warchoł: Hi Patrick, your patch was pushed when i was absent; now i see that Rietveld issue is still opened. Could you close it please?

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

Hi Patrick, your patch was pushed when i was absent; now i see that Rietveld issue is still opened. Could you close it please? http://codereview.appspot.com/5096050/ Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

On 2011/09/25 18:30:51, janek wrote: 2011/9/25 ptrcklsch...@googlemail.com: Hi Janek, I was talking about uploading some changes of this patch to rietveld. I forgot to add some bits and pieces I had announced in the description of this patch to the reworked version. I would have had to

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

LGTM. Thanks! http://codereview.appspot.com/5096050/diff/20001/python/musicexp.py File python/musicexp.py (right): http://codereview.appspot.com/5096050/diff/20001/python/musicexp.py#newcode1510 python/musicexp.py:1510: # Print out the style if we have ome, but the '() should only be The typo

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

This also passes a completely fresh make ; make doc. http://codereview.appspot.com/5096050/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

Hi Patrick, 2011/9/24 ptrcklsch...@googlemail.com: I just discovered that I forgot to add the changes related to conversion-info and \center-column. Do I have to make a completely new patch containing all 3 files (musicxml2ly.py, musicxml.py and musicexp.py) or is it ok to upload only the

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

On 2011/09/25 10:31:14, janek wrote: Hi Patrick, 2011/9/24 ptrcklsch...@googlemail.com: I just discovered that I forgot to add the changes related to conversion-info and \center-column. Do I have to make a completely new patch containing all 3 files (musicxml2ly.py, musicxml.py and

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

2011/9/25 ptrcklsch...@googlemail.com: Hi Janek, I was talking about uploading some changes of this patch to rietveld. I forgot to add some bits and pieces I had announced in the description of this patch to the reworked version. I would have had to adjust only 2 of the 3 files in the

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

On 2011/09/23 15:36:15, p-l-s wrote: Hi Reinhold and Janek, I hope I got it right this time. I didn't include the bit about miscellaneous. This will be part of a seperate patch. BTW: I noticed that the midi-block is not always inserted in every .ly file (this is not related to my

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

passes make and reg tests http://codereview.appspot.com/5096050/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

the installed musicxml2ly file and copy it over to the source tree! In particular, the source code contains identifiers like @TOPLEVEL_VERSION@, which will be replaced by the build system with proper values, so that we don't have to hardcode things like version or python path! So, -) Modify only

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

Hm, I didn't understand all of this. What do I have to change in musicxml2ly? My idea was to use the description misc field for a custom header variable named 'miscellaneous' by default. I was thinking about implementing a cmd line option ('-t' and '--texinfo') to be able to use

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

Hi Reinhold and Janek, I hope I got it right this time. I didn't include the bit about miscellaneous. This will be part of a seperate patch. BTW: I noticed that the midi-block is not always inserted in every .ly file (this is not related to my patch). I will do some testing... Thanks for your

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

Some concerns and a handful of questions (as usual in my case). http://codereview.appspot.com/5096050/diff/1/python/musicexp.py File python/musicexp.py (right): http://codereview.appspot.com/5096050/diff/1/python/musicexp.py#newcode63 python/musicexp.py:63: self.print_verbatim ('\\version

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

Welcome to the wonderful world of LilyPond development! Most changes look fine, but there are some things that can't be submitted yet. See my comments. Most important: Please edit the source file in scripts/musicxml2ly.py and don't modify the installed musicxml2ly file and copy it over

musicxml2ly: use either work-title or movement-title as title

Hey Reinhold, here is a small patch for the title issue. hth patrick 0001-musicxml2ly-use-either-work-title-or-movement-title-.patch Description: Binary data ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman

musicxml2ly: proposals concerning tagline, conversion info, source-element and midi-output

Hey all, I'd like to change (and add) some minor things in musicxml2ly, but before I make a patch I wanted to make sure that no-one objects: 1) tagline: musicxml2ly currently uses the contents of the software-element for the LilyPond-tagline. So the tagline at the end of a piece engraved

Re: musicxml2ly: proposals concerning tagline, conversion info, source-element and midi-output

Am Saturday, 17. September 2011, 16:50:33 schrieben Sie: I'd like to change (and add) some minor things in musicxml2ly, but before I make a patch I wanted to make sure that no-one objects: 1) tagline: musicxml2ly currently uses the contents of the software-element for the LilyPond-tagline

Re: musicxml2ly: proposals concerning tagline, conversion info, source-element and midi-output

Am 17.09.2011 um 17:01 schrieb Reinhold Kainhofer: Am Saturday, 17. September 2011, 16:50:33 schrieben Sie: I'd like to change (and add) some minor things in musicxml2ly, but before I make a patch I wanted to make sure that no-one objects: 1) tagline: musicxml2ly currently uses

Re: Isue 1868: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly) (issue 4908041)

I was able to do a full make doc with no errors. James http://codereview.appspot.com/4908041/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Isue 1868: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly) (issue 4908041)

passes make and reg tests http://codereview.appspot.com/4908041/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly) (issue 4908041)

Patch no longer applies to current tree http://codereview.appspot.com/4908041/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

  1   2   >