Re: PATCHES - Countdown for December 24th
On Sun, 25 Dec 2016 22:49:12 +0100 Alexander Kobel wrote: > On 2016-12-25 19:48, Urs Liska wrote: > > Am 25.12.2016 um 14:22 schrieb Alexander Kobel: > >> Hi all, > >> > >> On 2016-12-24 17:32, James wrote: > >>> Push: > >>> [...] > >>> 5010 add choral and choral-cautionary accidental style - > >>> Alexander Kobel > >>> https://sourceforge.net/p/testlilyissues/issues/5010 > >>> http://codereview.appspot.com/311430043 > >> > >> Does this require any action from my side? I doubt that I have > >> write access to the repo... > > > > You could just try out .. > > Well, sure; let me rephrase that "question". ;-) > > [...] Bogus stuff about my anonymously made clone, not knowing how to > authenticate if my recently made Allura account comes with push > rights, etc... [...] > > Whoops, found it - CG 3.4.9. So no, I don't have a Savannah account, > even less one that is granted any rights. No reason to change that; > my activity will remain scarce. > > > But if you don't have push access the "action" required by you is > > basically stating that and asking for someone to push your patch. > > Which I would do if I could reliably say I'll manage to do so > > before I will have forgotten about the task. > > > > So I have to pass the task on to someone else. > > No worries - I sent it to Harm. Well the worst case is you attach the patch to the tracker or make an approrpiate comment in Rietveld and I (Patch Meister) will see it on the next Patch countdown and push it for you. Of course it is always possible that during those 3 or 4 days between countdowns may mean that the patch needs re-basing - in which case I just send an email directly to the developer, but that is quite rare. Regards and Merry Christmas. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Offer to help development: Convert MIDI to Lilypond
Lilypond Developers: I am offering to help with the project of converting midi2ly from C to Python, or more generally converting MIDI to Lilypond. Per attached, I understand an initial conversion attempt has been started and is awaiting completion and testing. I'm not sure if this is a good place for someone new to Lilypond internals to start, but it seems this should be a relatively independent utility so I shouldn't need a significant background in the internals. I may need a "mentor" to help get started with the nuts and bolts of Lilypond development. I've done programming for a living in C++, Java, PHP, and a few others, but not Python [too new] or C [too old], though I am somewhat familiar with both, and also somewhat familiar with the structure of MIDI. Joe Austin >> On Dec 25, 2016, at 4:05 AM, Federico Bruni wrote: >> >> Il giorno dom 25 dic 2016 alle 9:58, David Kastrup ha scritto: ImportError: dlopen (/Applications/LilyPond-2-19-45.app/Contents/Resources/lib/lilypond/current/python/midi.so, 2): no suitable image found. Did find: /Applications/LilyPond-2-19-45.app/Contents/Resources/lib/lilypond/current/python/midi.so: mach-o, but wrong architecture joemacbook:midi josephaustin$ I get a similar problem trying to do the convert from within Frescobaldi. This is my first attempt at MIDI-to-Lilypond conversion, so I may be making some elementary error. >>> This is the only file in the whole LilyPond distribution that needs a C >>> compiler to compile. It also makes for a whole lot of trouble. What it >>> does can likely be rewritten in Python without much of a performance >>> impact for the application as a whole. >>> So rewriting this module in Python proper would be very much desirable. >>> I think that somebody™ should really do this. >>> In other words: raise an issue report about this problem, and I think >>> the suggestion to solve this problem area once and for all by not using >>> a C module in the first place should be high on the list of desirable >>> solutions for the issue. >> >> I think that there's already an issue for this (and also an abandoned patch): >> https://sourceforge.net/p/testlilyissues/issues/3067/ >> > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Can I develop with Raspberry Pi 3
Is it possible/practical to run LilyDev on Raspberry Pi 3? In other words, is that a realistic alternative to setting up a virtual machine or configuring a MacBook to run native? Joe Austin ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to help development: Convert MIDI to Lilypond
Joe Austin: > I am offering to help with the project of converting midi2ly from > C to Python, or more generally converting MIDI to Lilypond. ... midi2ly is part python and part c, you can find them in git repo.: scripts/midi2ly.py python/midi.c midi2ly has been in the repository since 2001 according to logs. If external dependances are ok, you can find midi support for python below the header "MIDI Mania" in https://wiki.python.org/moin/PythonInMusic https://github.com/vishnubob/python-midi can possible be of help. /// Midi file spec. are available at: http://www.music.mcgill.ca/~ich/classes/mumt306/midiformat.pdf https://www.midi.org/specifications/item/standard-midi-files-smf The midi-file spec. and RP-017 could be of help. /// If you are interested, I'm working on a similar tool, in perl though: http://turkos.aspodata.se/git/musik/bin/miditoly.pl I'm using perls midi module https://metacpan.org/pod/MIDI, a simple midi dump program is available at http://turkos.aspodata.se/git/musik/bin/midi.pl /// I have just started writing a paper to discuss implementions and huristics in the conversion: http://turkos.aspodata.se/git/musik/bin/midi_to_lilypond.tex I'd be happy if you want to contribute to that paper and any possible developments around midi -> lilypond in any programming language. From the top of my head, on my wishful agenda is: collect midi files generated from different notation programs together with pdf outputs from same programs examine and establish huristics how to identify lyrics character encodings try to reserach and define a few conventions on how the lilypond code should be written and structured and write a output module/function for each convention e.g. relative and absolute pich output, names of music variables to match the users preferences research how polyfonic settings are written to midi file, how do you identify voices from a track with multiple voices research and define huristics to guess voice and instrument names support note scaling, i.e. duble, half note values and such among other things. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to help development: Convert MIDI to Lilypond
Hi Joseph, welcome to the LilyPond community. It is great to see someone volunteering for such a task. It is a good idea to ask for a mentor, although that person would probably be mostly a mediator between you and the developers. Personally I don't think I could be that mentor but I wanted to give you immediate feedback, in case too many devs are in holiday mode. It may be interesting for you that there are several current plans and ideas around regarding import and export to various formats. Best wishes Urs Am 26. Dezember 2016 17:44:15 MEZ, schrieb Joseph Austin : >Lilypond Developers: > >I am offering to help with the project of converting midi2ly from C to >Python, or more generally converting MIDI to Lilypond. > >Per attached, I understand an initial conversion attempt has been >started and is awaiting completion and testing. > >I'm not sure if this is a good place for someone new to Lilypond >internals to start, >but it seems this should be a relatively independent utility so I >shouldn't need a significant background in the internals. > >I may need a "mentor" to help get started with the nuts and bolts of >Lilypond development. > >I've done programming for a living in C++, Java, PHP, and a few others, >but not Python [too new] or C [too old], >though I am somewhat familiar with both, and also somewhat familiar >with the structure of MIDI. > >Joe Austin > >>> On Dec 25, 2016, at 4:05 AM, Federico Bruni >wrote: >>> >>> Il giorno dom 25 dic 2016 alle 9:58, David Kastrup ha >scritto: > ImportError: dlopen > >(/Applications/LilyPond-2-19-45.app/Contents/Resources/lib/lilypond/current/python/midi.so, > 2): no suitable image found. Did find: > >/Applications/LilyPond-2-19-45.app/Contents/Resources/lib/lilypond/current/python/midi.so: > mach-o, but wrong architecture > joemacbook:midi josephaustin$ > I get a similar problem trying to do the convert from within >Frescobaldi. > This is my first attempt at MIDI-to-Lilypond conversion, > so I may be making some elementary error. This is the only file in the whole LilyPond distribution that needs >a C compiler to compile. It also makes for a whole lot of trouble. >What it does can likely be rewritten in Python without much of a >performance impact for the application as a whole. So rewriting this module in Python proper would be very much >desirable. I think that somebody™ should really do this. In other words: raise an issue report about this problem, and I >think the suggestion to solve this problem area once and for all by not >using a C module in the first place should be high on the list of >desirable solutions for the issue. >>> >>> I think that there's already an issue for this (and also an >abandoned patch): >>> https://sourceforge.net/p/testlilyissues/issues/3067/ >>> >> > > >___ >lilypond-devel mailing list >lilypond-devel@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-devel -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Automatic LyricExtenders (issue 313240043 by perpeduumimmob...@gmail.com)
On 2016/12/25 21:53:55, akobel wrote: On 2016/12/25 15:43:05, Knut_Petersen_t-online.de wrote: > Hi everybody! > > > I'm only 90% happy about "" and \markup\null... > > For dynamic spanners and hairpins, we have \! to end them prematurely > > before a "natural" end event appears. Is this similar enough to warrant > > the use of the same token (i.e., \! would be translated to empty lyrics > > with a CompletizeExtenderEvent), and is it possible at all? Otherwise, > > should we have a special token for this (\. comes to my mind)? > > > The use of "" and \markup\null is nothing new, so it needs to be handled correctly anyway. > It's possible to move a \markup\null to the left or right, therefore it is useful for \earlyExtender. > If this property is not needed "" will be used as it is much easier to type. If \! or something similar > would be provided for the same purpose almost everybody probably still would use the faster "". Granted. Didn't think of that, probably because I can't remember having ever used either. > __ meant "add an extender event", this is meaningless with the proposed patch as > an extender event is added after every syllable. To increase compatibility I feel that it > _never_ should be reused for anything. Okay. I was considering that in case we could make \autoExtenderOff to revert to the previous behavior. But on second though, there is hardly any use for that, and it creates more confusion than it's worth. Bottom line: I withdraw both proposals. Can you then re-submit a new patch or delete the one(s) that are invalid? I don't know what has and what has not been tested for sure, as far as I can tell only patch set 1 has been tested which had a slew of warning messages during the reg test output that I don't know are expected, desirable or something else. Thanks James https://codereview.appspot.com/313240043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to help development: Convert MIDI to Lilypond
Joseph Austin writes: > Lilypond Developers: > > I am offering to help with the project of converting midi2ly from C to > Python, or more generally converting MIDI to Lilypond. > > Per attached, I understand an initial conversion attempt has been > started and is awaiting completion and testing. > > I'm not sure if this is a good place for someone new to Lilypond > internals to start, > but it seems this should be a relatively independent utility so I > shouldn't need a significant background in the internals. > > I may need a "mentor" to help get started with the nuts and bolts of > Lilypond development. > > I've done programming for a living in C++, Java, PHP, and a few > others, but not Python [too new] or C [too old], > though I am somewhat familiar with both, and also somewhat familiar > with the structure of MIDI. You'd need to look at what the midi module (in the LilyPond source tree at python/midi.c) does and redo it in Python. I haven't looked at the code or its quality, but on the surface the task would seem to be well-confined and should yield to someone with a bit of willingness to muddle through and make himself more acquainted with Python again. It is well possible that there already exist suitably licensed modules (GPLv3+ or compatible) capable of reading Midi files in Python, but matching them to the current midi.c interface might be more work than it seems worth at first glance. One challenge will be setting up a suitable developing environment for working on this problem and being able to build and test results. You'd likely want to get a suitable version of the LilyDev virtual environment for that: ask on the developer list for details and/or look up the available information in the "Contributor's Guide" to LilyPond (part of its documentation). You also might want to ask on the developer list whether or not somebody will specifically act as a mentor to get you started on the development. All the best! -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to help development: Convert MIDI to Lilypond
On Mon, Dec 26, 2016 at 11:44:15AM -0500, Joseph Austin wrote: > I am offering to help with the project of converting midi2ly > from C to Python, or more generally converting MIDI to Lilypond. Excellent! I'd be delighted to serve as your mentor. > I'm not sure if this is a good place for someone new to Lilypond > internals to start, but it seems this should be a relatively > independent utility so I shouldn't need a significant background > in the internals. That is correct; the python midi2ly conversion is quite independent of the rest of LilyPond. As a result, it is an excellent place to begin! :) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can I develop with Raspberry Pi 3
On Mon, Dec 26, 2016 at 12:47:29PM -0500, Joseph Austin wrote: > Is it possible/practical to run LilyDev on Raspberry Pi 3? Unfortuantely not; LilyDev is compiled for x86 CPUs, whereas the Pi 3 has an ARM CPU. > In other words, is that a realistic alternative to setting up a > virtual machine or configuring a MacBook to run native? Unless your MacBook is 10 years old, it would be much faster to do LilyPond development within a virtual machine on your MacBook. That said, if you are only working on midi2ly, then you don't need the full LilyPond developer infrastructure. In fact, all you need a python interpreter (and arguably git for the source code); MacOS comes with python already. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to help development: Convert MIDI to Lilypond
Hello, > On Mon, Dec 26, 2016 at 11:44:15AM -0500, Joseph Austin wrote: > > I am offering to help with the project of converting midi2ly > > from C to Python, or more generally converting MIDI to Lilypond. Joseph, did you consider using Guile Scheme instead? One can argue about the power, flexibility ... Guile is just unbeatable :), it is used by lilypond itself, so in the end you'll be better prepared to help other lily devs (which I'm not) ... my 2c I'm saying this because you mentioned earlier you do not know Python, which means you are going to learn a new programming language, so, unless you have other criteria along the line, I strongly recommend Guile (and geiser, the emacs inferior mode that we all (guilers) use, which really rocks! and makes hacking just fun! Cheers, David https://www.gnu.org/software/guile/ http://www.nongnu.org/geiser/ you can ask quiz on irc channel #guile This might be of interest as well, though I personally really don't like the 'none parens' syntax, it is worth reading, no matter wha your choice is/will be...: http://www.draketo.de/proj/py2guile/ pgp2yOum3NGqF.pgp Description: OpenPGP digital signature ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to help development: Convert MIDI to Lilypond
David Pirotte writes: > Hello, > >> On Mon, Dec 26, 2016 at 11:44:15AM -0500, Joseph Austin wrote: >> > I am offering to help with the project of converting midi2ly >> > from C to Python, or more generally converting MIDI to Lilypond. > > Joseph, did you consider using Guile Scheme instead? One can argue > about the power, > flexibility ... Guile is just unbeatable :), it is used by lilypond > itself, so in the > end you'll be better prepared to help other lily devs (which I'm not) > ... my 2c I don't think we have any utilities written in Guile/Scheme. So the likelihood of him being able to be better prepared to help other lily devs is more than dubious. For better or worse, the use of Guile in LilyPond is very much constricted to LilyPond proper (in the form of libguile) rather than general programming. I think there is not much other than lilypond-invoke-editor.scm actually written as a utility program in Guile. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Automatic LyricExtenders (issue 313240043 by perpeduumimmob...@gmail.com)
On 2016/12/26 19:14:00, pkx166h wrote: On 2016/12/25 21:53:55, akobel wrote: > Bottom line: I withdraw both proposals. Can you then re-submit a new patch or delete the one(s) that are invalid? Sorry, I'm a bit drawn up between my position as the Rietveld-proxy of Knut and my own Alexander-role as a commenter. I forwarded all patches by Knut, and I withdrew my two comments from #5 and the one from the mailing list that Knut answered in #6. The patch set is up to date. I don't know what has and what has not been tested for sure, as far as I can tell only patch set 1 has been tested which had a slew of warning messages during the reg test output that I don't know are expected, desirable or something else. W.r.t. the regtest differences, as far as I (Alexander) can tell: The warnings should be gone with Knut's parser modification in patch set 3. The image differences are expected. A few short extenders are removed (due to the different handling of collapse-length vs. the old minimum-length). The exact setting of default collapse-length could be discussed, but IMHO the setting is fine. A few extenders appear that have not been written explicitly before, but that is expected, too. I guess for page-spacing-nonstaff-lines-independent.ly, the extender should be forbidden, to have the intended effect of this regtest shown more pronounced. However, I propose that we first discuss the patch itself, and settle on syntax and choice of default parameters (collapse-length, force-length). AFAICS, once this is done, we will need a pass over the entire documentation and regtests anyway that removes all __ in lyrics - not for functionality, but to purge outdated and possibly confusing syntax. That's basically a `sed -e 's/ __//g'`, but we will have to do a quick review of at least the affected docs to check for errors. Also, a convert-ly rule still has to be written that will, e.g., also solve the difference in the page-spacing-nonstaff-lines-independent.ly regtest. Cheers, Alexander https://codereview.appspot.com/313240043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
official GNU LilyPond maintainer
With David stepping down, LilyPond is left without an official GNU maintanier. Does anybody want to do fill this role? The relevant documentation is: https://www.gnu.org/prep/standards/html_node/index.html https://www.gnu.org/prep/maintain/html_node/index.htm If nobody is interested in the position, I am willing to take it up again. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyDev 5.0 released
On Wed, Dec 14, 2016 at 01:53:06PM +0100, Federico Bruni wrote: > Eventually I managed to build the new ISO. Thanks for all this work! I get an invalid network mirror when I try to install it. Do you have a default valid set, or is it failing to connect to the generic Canadian debian server? Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to help development: Convert MIDI to Lilypond
Graham: > On Mon, Dec 26, 2016 at 11:44:15AM -0500, Joseph Austin wrote: > > I am offering to help with the project of converting midi2ly > > from C to Python, or more generally converting MIDI to Lilypond. > > Excellent! I'd be delighted to serve as your mentor. > > > I'm not sure if this is a good place for someone new to Lilypond > > internals to start, but it seems this should be a relatively > > independent utility so I shouldn't need a significant background > > in the internals. > > That is correct; the python midi2ly conversion is quite > independent of the rest of LilyPond. As a result, it is an > excellent place to begin! :) If you want it as an exercise, that's fine, but if you want a better midi to lilypond converter you better start looking at what kind of output you want since the output that midi2ly produces could be much better than what it is today. So I propose that a better course of action would be to research . what kind of lilypond code output you want to produce . the net for a suitable lowlevel midi lib . the net for alternative converters that are presently availble and let that steer your direction. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel