[PD] [lanbox] and [tcpclient]
Hi list, I'm working on a multimedia/dance performance, until now we've kept the audio & video (Pd+Gem) running separately from the light. We've recently purchased a lanbox, it would be great to avoid using Midi on that project, that's wy we chose the LCX model.I've tried to have a connection setup following that thread http://elists.resynthesize.com/pd-list/2006/09/1636340/ but I cant find a working [tcpclient] for Linux (Debian sid) nor for OSX in order to communicate with the Lanbox. Any idea or link? Olivier ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [lanbox] and [tcpclient]
Oli44 wrote: > Hi list, > > but I cant find a working [tcpclient] for Linux (Debian sid) nor for OSX in > order to communicate with the Lanbox. Any idea or link? > hi. where have you looked for [tcpclient]? try http://pure-data.cvs.sourceforge.net/pure-data/externals/mrpeach/net/ mfg.asdr IOhannes ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [lanbox] and [tcpclient]
Oli44 wrote: > IOhannes m zmoelnig <[EMAIL PROTECTED]> wrote .. >> Oli44 wrote: >>> Hi list, >>> >>> but I cant find a working [tcpclient] for Linux (Debian sid) nor for >> OSX in order to communicate with the Lanbox. Any idea or link? >> hi. >> where have you looked for [tcpclient]? >> try http://pure-data.cvs.sourceforge.net/pure-data/externals/mrpeach/net/ hi. please always reply to the mailing list, unless it is something very private... >> > hallo, > > > i've downloaded it, since i'm a very average Linux user, I havent managed to > compile! well, i keep saying for years that the build system is too complicated. but whenever i do changes, i should have asked before ;-) anyhow, the most simple way to get tcpclient currently is to download the entire pd-extended binary, and extract whatever you need. if you feel like building yourself, then the "simplest" way would be to check out the entire pd-cvs, then go to externals/mrpeach and do a "make". the more sophisticated version would be to check out /externals/mrpeach/ and /externals/Makefile and /packages and do a "make" the best version would be to provide a simple makefile for people who don't want to spend days checking out or downloading binaries. but this is likely to break everything. ok, rant-mode should be turned off now... mfg.asdr IOhannes > > > trying currently to get help from a debian package maintainer via Jabber, > hope we can fix it and maybe turn it into a .deb? > > > ++ > O > > > > >> mfg.asdr >> IOhannes > ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [lanbox] and [tcpclient]
IOhannes m zmoelnig <[EMAIL PROTECTED]> wrote .. > > hi. > please always reply to the mailing list, unless it is something very > private... hello world ;-) > >>> I cant find a working [tcpclient] for Linux (Debian sid) nor for > >> OSX in order to communicate with the Lanbox. Any idea or link? > >> hi. > >> where have you looked for [tcpclient]? > >> try http://pure-data.cvs.sourceforge.net/pure-data/externals/mrpeach/net/ > > > i've downloaded it, since i'm a very average Linux user, I havent managed > to compile! Now, I managed compiling it using the most bandwidth consuming method, that is, I checked out the whole CVS, then the "Make" command in the ~/puredata/cvs/externals/mrpeach/ directory ran without a glitch. Now i've got a working [tcpclient] therefore a working [lanbox] : fiat lux! I'll work the osX version tomorrow. Thx a lot, O. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [lanbox] and [tcpclient]
On 17/01/2007, at 17.08, IOhannes m zmoelnig wrote: the best version would be to provide a simple makefile so that people can checkout a single external from cvs plus the pd section (or maybe just pd/src/m_ph.h ?), cd to the dir, run make? ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [lanbox] and [tcpclient]
Steffen wrote: > > On 17/01/2007, at 17.08, IOhannes m zmoelnig wrote: > >> the best version would be to provide a simple makefile > > so that people can checkout a single external from cvs plus the pd > section (or maybe just pd/src/m_ph.h ?), cd to the dir, run make? exactly. if you install pd differently (e.g. on debian with apt), you might get the m_pd.h file anyhow, probably as /usr/include/m_pd.h. i think no "standard" binary distribution of pd comes without this header file. (but i might be wrong). so there would be no need to checkout this file for _many_ cases (there will be problems for more in-depth externals that need access to g_canvas.h,..; however most externals should be fine with just m_pd.h) fmga-sdr IOhannes ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: Re: [PD] [lanbox] and [tcpclient]
> > IOhannes m zmoelnig <[EMAIL PROTECTED]> wrote .. > >> Oli44 wrote: > the more sophisticated version would be to check out /externals/mrpeach/ > and /externals/Makefile and /packages and do a "make" > > the best version would be to provide a simple makefile for people who > don't want to spend days checking out or downloading binaries. > but this is likely to break everything. > Even simpler: I usually use a shell script instead of a makefile if there is only one or two source files to build. Somthing like this works on linux, but probably could be extended: #! /bin/bash echo "Hello" gcc -O2 -DPD -shared -o midifile.pd_linux -I/usr/local/include/ midifile.c -L /usr/local/lib echo "done" Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
External building (was: Re: [PD] [lanbox] and [tcpclient])
On 17/01/2007, at 18.58, IOhannes m zmoelnig wrote: Steffen wrote: On 17/01/2007, at 17.08, IOhannes m zmoelnig wrote: the best version would be to provide a simple makefile so that people can checkout a single external from cvs plus the pd section (or maybe just pd/src/m_ph.h ?), cd to the dir, run make? exactly. Ok. Dare i ask, what prevents it? I'm guessing that of uniform cross- platform makefiles. Motivation: * I just tried to build arraysize. so i checked it out, with pd. But the makefile shipped in didn't support my current platform plus the include path wasn't pointing to where it "should". So i had to changed it, and by inspiration from another makefile (i chose line3) i got it working. Not too much trouble. * But passing the right path-var to make that was needed to build iemmatrix, fx, i don't think i'd worked out my self (i followed Kevins process due to curiosity on the topic). To not reinvent sliced bread, how does that idea further differ from the build-system used by (or maybe more correct: made for) pd- extended? My guess is, not much, but it currently requires the packages section of cvs too, if i'm not wrong. Im not sure where im getting at, except that i think it would be "nice" if it was "easy" to assemble/get just the settings of Pd one (the user) wants. There are a few "knobs to adjust" in this domain. To name some: millers version, pd-extended, devel, dd; pddp, or not; from none to more or all of the abstractions in cvs; from none to more or all of the externals in cvs, ... if you install pd differently (e.g. on debian with apt), you might get the m_pd.h file anyhow, probably as /usr/include/m_pd.h. i think no "standard" binary distribution of pd comes without this header file. (but i might be wrong). so there would be no need to checkout this file for _many_ cases (there will be problems for more in-depth externals that need access to g_canvas.h,..; however most externals should be fine with just m_pd.h) Ahh, i see. Thanks for the insight. Best, Stefffen ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
