Re: [pygame] pygame.midi using portmidi?

[Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx>]

That patch must be for building with a makefile. It builds fine as is from the xcode project (seems to be the maintained option)

On a computer without a real midi device, it looks like both the test program and the midi.py example seem to work with the virtual keyboard. It looks like what must have been happening is that portmidi couldn't find my actual physical midi device on another computer... I'll have to look into it - the piano is only hooked up as an input (not an output), so I suppose that may be part of the problem... 

anyways, I checked in the config changes a while back, so anyone with a  /usr/local/lib/libportmidi.a and /usr/local/include/portmidi.h can build with portmidi support, and the automated builds for mac have had portmidi support built into them for a little while now

On Mon, Jan 26, 2009 at 1:21 PM, René Dudfield <renesd@xxxxxxxxx> wrote:

Hi,

this notes a patch for 10.5sdk
http://lists.create.ucsb.edu/pipermail/media_api/2009-January/000703.html

Also found a section on OSX here:
http://cratel.wichita.edu/cratel/cratel_pyportmidi

Also, have you tried the .c test programs that come with portmidi?

cheers,

On Sun, Jan 25, 2009 at 9:15 PM, Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx> wrote:
> So I got pygame building on mac with portmidi now - although I can't seem to
> get the midi.py example to do anything.
>
>  the xcode proj for portmidi seems to have the porttime sources incorporated
> into it, rather than built as a separate lib, so the porttime dependency
> doesn't exist, which was causing trouble. Also the static libportmidi.a lib
> requires linkage to the CoreMidi framework, which was also causing trouble.
>
> So I decided to kill 2 birds with one stoney-hack and made PORTTIME
> dependency be a dependency on porttime.
>
> But now when I install the pygame on a machine with a midi keyboard
> attached, and run examples/midi.py with either --output or --list, it waits
> a long time, then prints "in stat: : No such file or directory" 4 times.
>
> looking at portmidi's sources, that error seems to com from it trying to
> read the "/PortMidi/PM_RECOMMENDED_INPUT_DEVICE" setting from some prefs
> file "com.apple.java.util.prefs.plist" as part of it's initialization.
>
> It seems really bizarre and rather dumb to me that portmidi would use java
> for anything, and I'm starting to wonder if the thing even works on
> Leopard...
>
>
> On Tue, Jan 13, 2009 at 2:49 PM, René Dudfield <renesd@xxxxxxxxx> wrote:
>>
>> I think with portmidi, compiling it ourselves on mac is the way to go.
>>  Seemed easy to compile on win/linux... so hopefully it compiles ok on
>> mac too.
>>
>
>