Re: Offer to help development: Convert MIDI to Lilypond

[Urs Liska]

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 <address@hidden>:
>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 <address@hidden>
>wrote:
>>> 
>>> Il giorno dom 25 dic 2016 alle 9:58, David Kastrup <address@hidden> 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
>address@hidden
>https://lists.gnu.org/mailman/listinfo/lilypond-devel

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.