stryd_one,
Thanks for your post. You can send a patch to me -- I'm gearing up
to make a number of fixes to portmidi "real soon now" (and apologies for
the delays).
I have some Eclipse files set up for use with MinGw, but I think
there is no makefile for mingw without eclipse. I'd be happy to add that
to the repository.
I don't know about the thread problem -- the thread_join() was not
there originally, but was added to fix a problem of trying to exit while
the thread was still running. I don't see anything obviously wrong --
before calling pthread_join, pt_callback_proc_id is changed to tell the
timer thread to exit. With linux, even with wxWidgets, you can use
printf to look at values or set a breakpoint with gdb at Pt_Stop or even
make the timer period very long and trace its progress with printf in
the Pt_CallbackProc loop. Let me know if you figure this out.
For priority, I see that ptlinux sets priority if you are running as
root. This *used* to be the only easy way to run at high priority, but
now that the default linux kernel is more real-time-friendly, I'm not
sure what is recommended. E.g. would it be safe to always set the
priority? I suppose setpriority can fail and that's better than not even
trying. But knowing what priority to use is tricky, and high priority
can lock up the system, so maybe that should be a user option ... There
are some comments at the top of ptlinux.c (including a typo I just
noticed). In my applications, I usually have more than one real-time
thread, and I don't use PortTime. Note that you can provide your own
time functions to PortMidi, so you don't have to use PortTime, which is
intended to be a bare-minimum implementation.
-Roger
>
_______________________________________________
media_api mailing list
media_api@create.ucsb.edu
http://lists.create.ucsb.edu/mailman/listinfo/media_api
