i'm interested in running two different pd-patches on one machine. is it better to load both patches to the same program, or is it better to start pd twice?
Tim mailto:TimBlechmann@gmx.net ICQ: 96771783 http://www.nyds-exp-discogs.tk -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Tim Blechmann wrote:
i'm interested in running two different pd-patches on one machine. is it better to load both patches to the same program, or is it better to start pd twice?
Tim mailto:TimBlechmann@gmx.net
I can't see any advantage to loading them into seperate instances of PD.
Don't start PD twice.
ICQ: 96771783 http://www.nyds-exp-discogs.tk-- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Yeah, I would like to be like that, but don't these people tend to burn out young and die young?
It sure would be nice to have energy to spare like that, though.
Larry
On Wed, 1 Jan 2003, Larry Troxler wrote:
Tim Blechmann wrote:
i'm interested in running two different pd-patches on one machine. is it better to load both patches to the same program, or is it better to start pd twice? Tim mailto:TimBlechmann@gmx.net
I can't see any advantage to loading them into seperate instances of PD. Don't start PD twice.
The way I'm guessing things out:
If you start PD twice then the second one does not have accesss to sound devices.
If you start PD twice then the two processes can do things more independently. For example, if video is causing the audio to make clicks and pauses and such, then you should run the video patch in another process.
But then, audio has to be in the _first_ process you start because the sound driver is first come first served.
Mathieu Bouchard http://artengine.ca/matju
Quoting Mathieu Bouchard matju@sympatico.ca:
On Wed, 1 Jan 2003, Larry Troxler wrote:
Don't start PD twice.
why ?
The way I'm guessing things out:
If you start PD twice then the second one does not have accesss to sound devices.
this is, of course, not true. You should be able to start the first process with "-nosound" and get the sound on the second instance. However, it is correct (with "normal" drivers) that only one pd-process will have access to the soundcard. With virtual audio cables like "jack" (i guess) you could even produce sound on both processes.
If you have several soundcards in your pc, this shouldn't be a problem at all (one or more cards exclusively for each pd)
If you start PD twice then the two processes can do things more independently. For example, if video is causing the audio to make clicks and pauses and such, then you should run the video patch in another process.
right
But then, audio has to be in the _first_ process you start because the sound driver is first come first served.
see above.
it really depends on what you are doing with your two patches. If they are driven by the same pd, you have to take care about nameclashes in send/receive's and tables and elsewhere. If they are driven by 2 pd's you don't have this problem but others (like the audio-output). additionally GUI-control of several pd's might be not as simple as with one interface. me, for instance, i use 2 pd's most of the time (esp. when under heavy load): 1 audio-engine~ (that does all the signal-processing) with realtime-priority and 1 GUI (that does no signal processing) with bad priority. These are connected via netsend/netreceive, but this might not be what you need.
mfg.a.dsr IOhannes
Hi all,
Has anyone compiled externals/footils/flext-iiwu for OSX? Or are all footils just linux?
d
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
Hi, david casal hat gesagt: // david casal wrote:
Has anyone compiled externals/footils/flext-iiwu for OSX? Or are all footils just linux?
No, they should be able to compile on OS-X, as well, maybe even on OS-9 for Max/MSP. But I have no Apple system, so I cannot build or test them... But you should be able to just take a makefile.darwin from the flext-tutorials and adapt it for my externals. I could not test this, so I don't supply makefiles or binaries for Mac or Windows.
ciao
Frank Barknecht _ ______footils.org__
David, Frank,
The flext-iiwu part was very easy. However, getting iiwu to compile and tracking down MidiShare was much more difficult. It was far from my cleanest compile, but Pd-MacOSX now seems to have a soundfont synth, downloadable from: http://homepage.mac.com/atl/sw/
have fun... :) adam
I believe Frank Barknecht said this around Mon, 6 Jan 2003:
Hi, david casal hat gesagt: // david casal wrote:
Has anyone compiled externals/footils/flext-iiwu for OSX? Or are all footils just linux?
No, they should be able to compile on OS-X, as well, maybe even on OS-9 for Max/MSP. But I have no Apple system, so I cannot build or test them... But you should be able to just take a makefile.darwin from the flext-tutorials and adapt it for my externals. I could not test this, so I don't supply makefiles or binaries for Mac or Windows.
ciao
Frank Barknecht _ ______footils.org__
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list
--
Adam Lindsay +44(0)1524 594 537 atl@comp.lancs.ac.uk http://www.comp.lancs.ac.uk/computing/users/atl/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Tue, 7 Jan 2003, Adam Lindsay wrote:
HIya Adam,
However, getting iiwu to compile and tracking down MidiShare was much more difficult. It was far from my cleanest compile, but Pd-MacOSX now seems to have a soundfont synth, downloadable from: http://homepage.mac.com/atl/sw/
WOw. You didn't even give me time to find MIdiShare, etc. (Got as far as complaints about readline.h and so on)
Thank you!
d
I believe Frank Barknecht said this around Mon, 6 Jan 2003:
Hi, david casal hat gesagt: // david casal wrote:
Has anyone compiled externals/footils/flext-iiwu for OSX? Or are all footils just linux?
No, they should be able to compile on OS-X, as well, maybe even on OS-9 for Max/MSP. But I have no Apple system, so I cannot build or test them... But you should be able to just take a makefile.darwin from the flext-tutorials and adapt it for my externals. I could not test this, so I don't supply makefiles or binaries for Mac or Windows.
ciao
Frank Barknecht _ ______footils.org__
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list
--
Adam Lindsay +44(0)1524 594 537 atl@comp.lancs.ac.uk http://www.comp.lancs.ac.uk/computing/users/atl/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
Hi, Adam Lindsay hat gesagt: // Adam Lindsay wrote:
The flext-iiwu part was very easy. However, getting iiwu to compile and tracking down MidiShare was much more difficult. It was far from my cleanest compile, but Pd-MacOSX now seems to have a soundfont synth, downloadable from: http://homepage.mac.com/atl/sw/
Thanks a lot, Adam. I checked the new files into the CVS, supposing you don't mind ;)
ciao
Frank Barknecht _ ______footils.org__
On Tue, 7 Jan 2003, Adam Lindsay wrote:
Hello all,
However, getting iiwu to compile and tracking down MidiShare was much more difficult.
Well, turns out I spoke too soon. If I'm correct here, flext-iiwu wants iiwusynth compiled, which wants midishare? I downloaded the OSX packages from GRAME's website and installed, but I can't see a libmidishare.so anywwhere, and the only midishare.h (which 'configure' in iiwusynth-0.2.2 seems to look for) is in the MidiShare Development tools package, in C/C++/include folder. Even when I put that in system paths like /usr/include or /usr/local, it iiwusynth won't configure with midishare enabled.
Hints? Which version of iiwusynth did you compile? (or am I missing something here, and I don't really need to do any of this)
(now missing debian-world)
d
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
Oops. *I* may have spoke too soon, and ignored a dynamic library. David, just to be sure, you *have* tried it with the binary tucked away in the pd-darwin directory?
adam
I believe david casal said this around Tue, 7 Jan 2003:
On Tue, 7 Jan 2003, Adam Lindsay wrote:
Hello all,
However, getting iiwu to compile and tracking down MidiShare was much more difficult.
Well, turns out I spoke too soon. If I'm correct here, flext-iiwu wants iiwusynth compiled, which wants midishare? I downloaded the OSX packages from GRAME's website and installed, but I can't see a libmidishare.so anywwhere, and the only midishare.h (which 'configure' in iiwusynth-0.2.2 seems to look for) is in the MidiShare Development tools package, in C/C++/include folder. Even when I put that in system paths like /usr/include or /usr/local, it iiwusynth won't configure with midishare enabled.
Hints? Which version of iiwusynth did you compile? (or am I missing something here, and I don't really need to do any of this)
(now missing debian-world)
d
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
--
Adam Lindsay +44(0)1524 594 537 atl@comp.lancs.ac.uk http://www.comp.lancs.ac.uk/computing/users/atl/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
I was able to experiment on a clean machine. The tarball has everything you need. Run pd (from the directory where you unpacked it) with: pd -path flext-iiwu/pd-darwin flext-iiwu/pd/fiiwu~.pd
And load your sound font. Thanks for pointing out a nifty external, and thanks to Frank for providing it.
To everyone else, sorry about the extra traffic. It was mostly from being unclear in last night's knackered post. Cheers, adam
Adam Lindsay said this at Tue, 7 Jan 2003 13:17:55 +0000:
Oops. *I* may have spoke too soon, and ignored a dynamic library. David, just to be sure, you *have* tried it with the binary tucked away in the pd-darwin directory?
adam
I believe david casal said this around Tue, 7 Jan 2003:
On Tue, 7 Jan 2003, Adam Lindsay wrote:
Hello all,
However, getting iiwu to compile and tracking down MidiShare was much more difficult.
Well, turns out I spoke too soon. If I'm correct here, flext-iiwu wants iiwusynth compiled, which wants midishare? I downloaded the OSX packages from GRAME's website and installed, but I can't see a libmidishare.so anywwhere, and the only midishare.h (which 'configure' in iiwusynth-0.2.2 seems to look for) is in the MidiShare Development tools package, in C/C++/include folder. Even when I put that in system paths like /usr/include or /usr/local, it iiwusynth won't configure with midishare enabled.
Hints? Which version of iiwusynth did you compile? (or am I missing something here, and I don't really need to do any of this)
(now missing debian-world)
d
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
--
Adam Lindsay +44(0)1524 594 537 atl@comp.lancs.ac.uk http://www.comp.lancs.ac.uk/computing/users/atl/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list
On Tue, 7 Jan 2003, Adam Lindsay wrote:
I was able to experiment on a clean machine. The tarball has everything you need. Run pd (from the directory where you unpacked it) with: pd -path flext-iiwu/pd-darwin flext-iiwu/pd/fiiwu~.pd
And load your sound font. Thanks for pointing out a nifty external, and thanks to Frank for providing it.
Thanks Adam, I'll try that (later when I get home), and report back.
d
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
On Tue, 7 Jan 2003, Adam Lindsay wrote:
Hiya
Oops. *I* may have spoke too soon, and ignored a dynamic library. David, just to be sure, you *have* tried it with the binary tucked away in the pd-darwin directory?
If by tried you mean tried to -lib load it on ps startup, yes I did.
-lib /usr/local/lib/pd/extra/flext-iiwu/pd-darwin/fiiwu
and several other things, like -path and other locations, just to be sure.
Then I tried make clean, (make -f [proper makefile] clean), and after tweaking the config, make again. THen, it complained about not finding iiwusynth.h
Hope that helps
d
adam
I believe david casal said this around Tue, 7 Jan 2003:
On Tue, 7 Jan 2003, Adam Lindsay wrote:
Hello all,
However, getting iiwu to compile and tracking down MidiShare was much more difficult.
Well, turns out I spoke too soon. If I'm correct here, flext-iiwu wants iiwusynth compiled, which wants midishare? I downloaded the OSX packages from GRAME's website and installed, but I can't see a libmidishare.so anywwhere, and the only midishare.h (which 'configure' in iiwusynth-0.2.2 seems to look for) is in the MidiShare Development tools package, in C/C++/include folder. Even when I put that in system paths like /usr/include or /usr/local, it iiwusynth won't configure with midishare enabled.
Hints? Which version of iiwusynth did you compile? (or am I missing something here, and I don't really need to do any of this)
(now missing debian-world)
d
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
--
Adam Lindsay +44(0)1524 594 537 atl@comp.lancs.ac.uk http://www.comp.lancs.ac.uk/computing/users/atl/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
Compiling was pretty annoying, partially because of what you cite.
The specific step you need might be to remove the config.cache file... configure caches the fact that it didn't find MidiShare.h on the first go. I think once I got that step, it configured okay.
The iiwusynth-0.2.2 compile presents its own problems, cos the MacOSX headers it needs are a mix between the MACINTOSH and (default) linux builds. I just commented stuff out as I went along, (make, edit, repeat) and then moved the src/.libs/libiiwusynth.a file to /usr/local/lib/, and ran ranlib.
Anyway, it was much easier to provide a binary than describe the ad-hoc hackery that went on last night.
Hope that helps you rolling your own, adam
david casal said this at Tue, 7 Jan 2003 12:34:08 +0000:
On Tue, 7 Jan 2003, Adam Lindsay wrote:
Hello all,
However, getting iiwu to compile and tracking down MidiShare was much more difficult.
Well, turns out I spoke too soon. If I'm correct here, flext-iiwu wants iiwusynth compiled, which wants midishare? I downloaded the OSX packages from GRAME's website and installed, but I can't see a libmidishare.so anywwhere, and the only midishare.h (which 'configure' in iiwusynth-0.2.2 seems to look for) is in the MidiShare Development tools package, in C/C++/include folder. Even when I put that in system paths like /usr/include or /usr/local, it iiwusynth won't configure with midishare enabled.
Hints? Which version of iiwusynth did you compile? (or am I missing something here, and I don't really need to do any of this)
(now missing debian-world)
d
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+
-
Adam Lindsay -
david casal -
Frank Barknecht -
Larry Troxler -
Mathieu Bouchard -
Tim Blechmann -
zmoelnig＠iem.at