Hi all,
as i work a lot with the devel_0_37 branch of the PD cvs i always encounter problems with the Portaudio stuff when merging in changes from a new PD version. To my mind PD and Portaudio/PortMIDI should be separate things as both evolve independently from each other, so i don't like the current status of a Portaudio version being incorporated into PD. It's ok for a release package but not really for a development version. Hence, my suggestion is that the Portaudio files that are modified for PD ( pablio_pd.*, ringbuffer_pd.c ) be moved into the pd/src folder, so that one can use Portaudio from the PA cvs. In the moment there's a kind of Portaudio V19 in the devel_0_37 branch which doesn't compile with pablio_pd.c. The latter relies on the V18 API.
best greetings, Thomas
I should have thought of that... it will make my life easier too. I'll probably keep things as they are for 0.37 but quickly fix it up for 0.38. I'll look at compiling for V19 (and should go on and update my own copy since that's experimental anyway...)
cheers Miller
On Sat, Sep 13, 2003 at 01:55:12PM +0200, Thomas Grill wrote:
Hi all,
as i work a lot with the devel_0_37 branch of the PD cvs i always encounter problems with the Portaudio stuff when merging in changes from a new PD version. To my mind PD and Portaudio/PortMIDI should be separate things as both evolve independently from each other, so i don't like the current status of a Portaudio version being incorporated into PD. It's ok for a release package but not really for a development version. Hence, my suggestion is that the Portaudio files that are modified for PD ( pablio_pd.*, ringbuffer_pd.c ) be moved into the pd/src folder, so that one can use Portaudio from the PA cvs. In the moment there's a kind of Portaudio V19 in the devel_0_37 branch which doesn't compile with pablio_pd.c. The latter relies on the V18 API.
best greetings, Thomas
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
-
Miller Puckette -
Thomas Grill