hi again, Another note:
Tim Thompson said we could include his patches to pyportmidi, and also include some of his other midi code... """You'll also find there a python module (nosuch.midiutil) that contains higher-level routines for MIDI things, including a MIDI file reader, simple scheduler, etc.""" cu! On Tue, Dec 23, 2008 at 6:48 PM, René Dudfield <[email protected]> wrote: > yeah, good point. > > I've used pyrex to generate a pypm.c file, and included that along > with the pypm.pyx file. This way pygame doesn't need pyrex as a > dependency. > > Might as well use the existing python binding for portmidi. There's a > few patches floating around the net... so hopefully I can find them > and pull them into the pygame version... and then they can hopefully > flow back into the pyportmidi version. > > I've emailed the author of pyportmidi to ask him if it's ok to include > it in pygame too. It should be under the python license (I think), > but I emailed him just to make sure. > > pygame.midi in svn now, and seems to build ok, and run with the latest > svn. I still have a bit of work to do on it... including docs, > finishing an output class, tests etc. Also, only tested on windows so > far. Still need to make sure it compiles, and works on Mac and linux. > > > cheers, > > > > On Mon, Dec 22, 2008 at 8:53 PM, Toni Alatalo <[email protected]> wrote: >> René Dudfield kirjoitti: >>> >>> going to try and use pyportmidi, but decided against it. since >>> pyportmidi is written in pyrex, whereas pygame uses C modules. Also >>> >> >> i don't understand the reasoning there, as Pyrex is just a way to write C. >> i.e. something written in Pyrex is a C module. >> >> otherwise: interesting stuff, thanks for info! >> >> ~Toni >>> >>> On Wed, Dec 17, 2008 at 1:12 PM, Lenard Lindstrom <[email protected]> wrote: >>> >>>> >>>> That looks good. test.exe works for me too, except when it is killed >>>> prematurely. It still quits, but gives me an error message as well. >>>> Anyway, >>>> I will look at adding portmidi to the Windows dependency build process. I >>>> just need to make sure it is optional. >>>> >>>> Lenard >>>> >>>> René Dudfield wrote: >>>> >>>>> >>>>> cool, I'll try out the midi tests some more on the weekend. test.exe >>>>> with option 6 seems to work for me. >>>>> >>>>> yeah, I've used pyportmidi :) I think a few things need to be redone >>>>> though, but maybe I should just use that, and send them patches (or >>>>> point them to the pygame svn). >>>>> >>>>> I've already got code to convert midi events into pygame events... >>>>> which is useful if you want to handle midi events in the same way as >>>>> keyboard/mouse/joystick events. Also did some code to run the midi >>>>> stuff as a background thread, which I think will make it easier for >>>>> people - so they don't need to manage the midi streams themselves. >>>>> >>>>> >>>>> >>>> >>>> -- >>>> Lenard Lindstrom >>>> <[email protected]> >>>> >>>> >>>> >> >> >
