Pd-list June 2006

pd-list@lists.iem.at

138 participants
210 discussions

RE: Re: [PD] a little ot: creative commons
by padawan12＠obiwannabe.co.uk 20 Jun '06

20 Jun '06

>CC addresses the production of culture, the GPL address >the production of code. They are two very different intentions, two >very different "things". I'm sure that makes a great debate. I'm not sure they are so different or if you can ever draw a line between data and code in a truly meaningful way. Pour me te differences in the licences are about simplicity and language, CC being something artists can grok right away. I'm quite happy that CC works for me for the things I want it to, granting rights for music and letting me decide what can be remixed or merely copied and what it can be used for. If you write code or patches that fall into what you believe is a grey area you're free to choose mix and match licences as you wish, GPL or BSD for code if appropriate, CC non -erivative or CC sharealike. At the end of te day never be afraid to write your own licence parts simply stating your wishes, on a per file basis if you really need to, or pulling bits from licences or supplementing them with your own stuff. Just think it through, be clear and honest about what you want to grant or restrict and try to make life as simple as possible for the end user or else they will be put off using your work. Andy > >And, despite being a FLOSS advocate and avid FLOSS programmer since many >years, >I take particular offense to this article: > > http://www.metamute.org/?q=en/Freedoms-Standard-Advanced > >Mako Hill only wishes to extend the naive tautology of the word "freedom", >and >knock CC for not having an ideology that is as simple and total as the GPL. > >best -august. > >_______________________________________________ >PD-list(a)iem.at mailing list >UNSUBSCRIBE and account-management -> >http://lists.puredata.info/listinfo/pd-list

4 5

[PD-announce] bassemu~: transistor bass emulation
by Christian Klippel 20 Jun '06

20 Jun '06

hi all, heres the first object from the jmax stuff i made, ported to pd. bassemu~ is a emulation of an analogue bass synth. it includes the obligatory filter, saw/rect/tri/sine waveform select, an extra hi-pass filter. you can also feed another signal to its left inlet, and filter that, either alone or mixed to the vco. also included is a small, messy gop abstraction to resemble a 16-step sequencer. you can find the source on http://home.mamalala.de/bassemu-0.2.tgz greets and have fun, chris _______________________________________________ PD-announce mailing list PD-announce(a)iem.at http://lists.puredata.info/listinfo/pd-announce

4 8

[announce] dorkbotswiss in züri
by moritz 20 Jun '06

20 Jun '06

friday, 16.juni, 20.00 free entry- free exit electronical offsides from: beat brogle (d/ch) presenting one word movie georg greve (d) presenting free software foundation europe net pd (ch/welt) presenting net pd --> more info http://www.dorkbotswiss.org cheers mOriTz ------------------------------------------------------------------------ ------------------------------------------------------------------------ _______________________________________________ snm mailing list snm(a)snm-hgkz.ch http://www.snm-hgkz.ch/mailman/listinfo/snm

2 1

Re: BlueTooth CUI : using [comport] or [hid]
by Hans-Christoph Steiner 20 Jun '06

20 Jun '06

To get bits, use the standard bitwise operators, just like C or many other languages. Pd has the whole suite: & | >> << To get the value of a bit, AND it by that bit's value, i.e. the 4th bit would be [& 16] .hc On Jun 16, 2006, at 2:00 PM, Dan Overholt wrote: > Hi All, > > I've put up an example of using the Bluetooth CUI with PD here: > http://www.create.ucsb.edu/~dano/CUI/CUIBTPDtest.pd > > The only question is how to get at the individual bits within the > last 2 > received bytes to decode the digital inputs from the CUI. In Max/MSP, > there is an 3rd party external called [bit] that does this... any > suggestions? > > All the best, > -Dan > > -- > Dan Overholt -- http://www.create.ucsb.edu/~dano > Center for Research in Electronic Art Technology, UCSB > > > On Fri, 16 Jun 2006, Alexandre Quessy wrote: > >> Hello Pure Data friends, >> >> >> We are currently trying to make the Bluetooth CUI work with PD. >> >> >> The Bluetooth Create Usb Interface is the wireless version of the USB >> CUI, a 13 analog/10 bits and 12 digital I/O interface for sensors. >> The >> BTCUI is perfect for embbeded applications like dance, >> performance, music etc. It's one of the cheapest and smallest >> wireless >> interface on the market, and it is Open Hardware ! >> >> The USB CUI works all right with PD, with HID tools. We use the [hid] >> external from PD-Extended 0.39.RC4 (on Mac). >> >> Unfortunately, we didn't succeeded to make the BluetoothCUI working >> with PD. We have tried [comport] and [hid]. The BTCUI works perfectly >> on Max/MSP (demo version), as announced by Dan Overholt, its creator. >> His patch is downloadable at >> http://www.create.ucsb.edu/~dano/CUI/BlueCUItestRev2.zip and uses the >> [serial] object of Max/MSP. >> >> The protocol of the CUI is probably similar to the one used by >> joysticks and such. It consists in a serie of integers with >> delimiters, the several remaining integers beings the values that the >> device sends to the computer. See the attached PD patches. Below are >> out two PD patches. The first one uses [hid] and works with the USB >> CUI, but not over BlueTooth. (Apple does serial port emulation) The >> second uses [comport] and almost work. The CUI LED lights up, so it >> means that it is sending data, but most often, dumping the data from >> [comport]'s outlet give us nothing. >> >> >> Would you have any idea of what is missing to imitate, and make even >> better than the [serial] Max/MSP object ? Otherwise, would it be >> easier on >> Linux ? >> >> >> JN and >> ------------------------------------------------------------------------ Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams

3 3

Re: BlueTooth CUI : using [comport] or [hid]
by Hans-Christoph Steiner 20 Jun '06

20 Jun '06

Hey Dan, How is the [&] object ineffecient? I think its just a straight pass- thru to the C & operator, should it should use little CPU. It would be easy enough to write something like [bit] for Pd based on [&] which would make the patching easier. .hc On Jun 16, 2006, at 9:03 PM, Dan Overholt wrote: > all right, there's an updated version of the PD patch for the > Bluetooth > CUI on the website now, including the digital inputs: > http://www.create.ucsb.edu/~dano/CUI/CUIBTPDtest.pd > > using the AND operator in PD seems to be _very_ inneffecient > though, if > anyone has a better idea, let me know! > > -Dan > > On Fri, 16 Jun 2006, Hans-Christoph Steiner wrote: > >> >> To get bits, use the standard bitwise operators, just like C or many >> other languages. Pd has the whole suite: & | >> << >> >> To get the value of a bit, AND it by that bit's value, i.e. the 4th >> bit would be [& 16] >> >> .hc >> >> On Jun 16, 2006, at 2:00 PM, Dan Overholt wrote: >> >>> Hi All, >>> >>> I've put up an example of using the Bluetooth CUI with PD here: >>> http://www.create.ucsb.edu/~dano/CUI/CUIBTPDtest.pd >>> >>> The only question is how to get at the individual bits within the >>> last 2 >>> received bytes to decode the digital inputs from the CUI. In Max/ >>> MSP, >>> there is an 3rd party external called [bit] that does this... any >>> suggestions? >>> >>> All the best, >>> -Dan >>> >>> -- >>> Dan Overholt -- http://www.create.ucsb.edu/~dano >>> Center for Research in Electronic Art Technology, UCSB >>> >>> >>> On Fri, 16 Jun 2006, Alexandre Quessy wrote: >>> >>>> Hello Pure Data friends, >>>> >>>> >>>> We are currently trying to make the Bluetooth CUI work with PD. >>>> >>>> >>>> The Bluetooth Create Usb Interface is the wireless version of >>>> the USB >>>> CUI, a 13 analog/10 bits and 12 digital I/O interface for sensors. >>>> The >>>> BTCUI is perfect for embbeded applications like dance, >>>> performance, music etc. It's one of the cheapest and smallest >>>> wireless >>>> interface on the market, and it is Open Hardware ! >>>> >>>> The USB CUI works all right with PD, with HID tools. We use the >>>> [hid] >>>> external from PD-Extended 0.39.RC4 (on Mac). >>>> >>>> Unfortunately, we didn't succeeded to make the BluetoothCUI working >>>> with PD. We have tried [comport] and [hid]. The BTCUI works >>>> perfectly >>>> on Max/MSP (demo version), as announced by Dan Overholt, its >>>> creator. >>>> His patch is downloadable at >>>> http://www.create.ucsb.edu/~dano/CUI/BlueCUItestRev2.zip and >>>> uses the >>>> [serial] object of Max/MSP. >>>> >>>> The protocol of the CUI is probably similar to the one used by >>>> joysticks and such. It consists in a serie of integers with >>>> delimiters, the several remaining integers beings the values >>>> that the >>>> device sends to the computer. See the attached PD patches. Below >>>> are >>>> out two PD patches. The first one uses [hid] and works with the USB >>>> CUI, but not over BlueTooth. (Apple does serial port emulation) The >>>> second uses [comport] and almost work. The CUI LED lights up, so it >>>> means that it is sending data, but most often, dumping the data >>>> from >>>> [comport]'s outlet give us nothing. >>>> >>>> >>>> Would you have any idea of what is missing to imitate, and make >>>> even >>>> better than the [serial] Max/MSP object ? Otherwise, would it be >>>> easier on >>>> Linux ? >>>> >>>> >>>> JN and >>>> >> >> >> --------------------------------------------------------------------- >> --- >> >> Man has survived hitherto because he was too ignorant to know how to >> realize his wishes. Now that he can realize them, he must either >> change them, or perish. -William Carlos Williams >> >> > > -- > Dan Overholt -- http://www.create.ucsb.edu/~dano > Center for Research in Electronic Art Technology, UCSB ------------------------------------------------------------------------ If you are not part of the solution, you are part of the problem. - Eldridge Cleaver

2 1

23bit t_float vs. 20bit display in Pd's integer representation
by Hans-Christoph Steiner 20 Jun '06

20 Jun '06

First I off, I forgot one thing in my analysis of the bitness of Pd's integers: the sign. So its 20 bits, I forgot the bit for the sign ( -999999 to 999999). So this leads me to the question which Matju brought up: the internal representation (t_float) should be able to store 23 bits of integer information. Why does Pd only display up to 20bits on integer data? If Pd displayed 7 digits plus sign, it would cover the 23 bits... .hc ------------------------------------------------------------------------ News is what people want to keep hidden and everything else is publicity. - Bill Moyers

2 3

gigs in europe in july / august - live PD
by hard off 19 Jun '06

19 Jun '06

I am coming to europe this summer, from july 20th to the start of september. I will bring a laptop with 6 gigabytes of sampled loops from pretty much every genre of music that i could find in the last 3 years or so. All mixed up live in front of your eyes via PD. If anyone knows of any gigs that might suit, please let me know. it's good fun. no gig too big or too small - anywhere in europe is ok. thanks! matt hard.off(a)gmail.com

2 2

Gem : problems loading films on Linux
by Alexandre Quessy 19 Jun '06

19 Jun '06

Hi all, I have to set up a machine for our lab. Everything was working fine before the dist-upgrade from Ubuntu Breezy to Dapper... Now, no more film loading. I lost several hours on this already, so I thought I could share this problem with you guys. :) The next step, if no good idea appears (as I have probably forgot a stupid but important detail somewhere), is to compile everything and not use unconsistant deb packages + pd-exended linux + hand-compiled libraries. Below are the output of the PD window, Gem's ldd output (the list of dynamic loaded libraries used by Gem.pd_linux) and the ./configure output. -- Alexandre Quessy http://alexandre.quessy.net For debugging : =================== PD loading Gem =================== tried /home/azer/aalex/gem/Gem/src/Gem.pd_linux and succeeded GEM: Graphics Environment for Multimedia GEM: ver: 0.90 GEM: compiled: Jun 16 2006 GEM: maintained by IOhannes m zmoelnig GEM: Authors : Mark Danks (original version on irix/windows) GEM: Chris Clepper (macOS-X) GEM: Daniel Heckenberg (windows) GEM: James Tittle (macOS-X) GEM: IOhannes m zmoelnig (linux/windows) GEM: using SSE2 optimization ======================= Gem's PD Errors ================= pix_film:: quicktime support pix_film:: libmpeg3 support pix_film:: libaviplay support pix_film:: libmpeg support Direct Rendering enabled! GEM: Start rendering ... ... quicktime failed ... MPEG3 failed ... aviplay failed ... ... ... ... ... giving up! error: GEM: pix_film: Unable to open file: ../data/anim-1.mov ... ... quicktime failed ... MPEG3 failed ... aviplay failed ... ... ... ... ... giving up! error: GEM: pix_film: Unable to open file: ../data/alea.mpg ... ... quicktime failed ... MPEG3 failed ... aviplay failed ... ... ... ... ... giving up! error: GEM: pix_film: Unable to open file: ../data/homer.avi ======== Gem.pd_linux's ldd (a shell command) output ===== linux-gate.so.1 => (0xffffe000) libdv.so.4 => /usr/lib/libdv.so.4 (0xb7c24000) libmpeg.so.1 => /usr/lib/libmpeg.so.1 (0xb7b36000) libmpeg3.so.1 => /usr/lib/libmpeg3.so.1 (0xb7afb000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb7adc000) libtiff.so.4 => /usr/lib/libtiff.so.4 (0xb7a8c000) libGLU.so.1 => /usr/lib/libGLU.so.1 (0xb7a16000) libGL.so.1 => /usr/lib/libGL.so.1 (0xb79b0000) libXext.so.6 => /usr/lib/libXext.so.6 (0xb79a2000) libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0xb799d000) libX11.so.6 => /usr/lib/libX11.so.6 (0xb78b7000) libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb78b4000) libz.so.1 => /usr/lib/libz.so.1 (0xb78a0000) libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb788e000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb7824000) libaviplay-0.7.so.0 => /usr/lib/libaviplay-0.7.so.0 (0xb778b000) libquicktime.so.0 => /usr/lib/libquicktime.so.0 (0xb76e9000) libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb76c7000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb75f2000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb75e8000) libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb74b8000) liba52-0.7.4.so => /usr/lib/liba52-0.7.4.so (0xb74ad000) libdrm.so.2 => /usr/lib/libdrm.so.2 (0xb74a6000) libXau.so.6 => /usr/lib/libXau.so.6 (0xb74a3000) /lib/ld-linux.so.2 (0x80000000) libaviplayavformat-0.7.so.0 => /usr/lib/libaviplayavformat-0.7.so.0(0xb7444000) libaviplayavcodec-0.7.so.0 => /usr/lib/libaviplayavcodec-0.7.so.0(0xb7170000) libaviplayavutil-0.7.so.0 => /usr/lib/libaviplayavutil-0.7.so.0(0xb716b000) libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0xb70e3000) libasound.so.2 => /usr/lib/libasound.so.2 (0xb702e000) libartsc.so.0 => /usr/lib/libartsc.so.0 (0xb7028000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7025000) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb7020000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb6f9c000) libesd.so.0 => /usr/lib/libesd.so.0 (0xb6f92000) libaudiofile.so.0 => /usr/lib/libaudiofile.so.0 (0xb6f72000) libaudio.so.2 => /usr/lib/libaudio.so.2 (0xb6f5e000) libXt.so.6 => /usr/lib/libXt.so.6 (0xb6f10000) libaa.so.1 => /usr/lib/libaa.so.1 (0xb6ef5000) libncurses.so.5 => /lib/libncurses.so.5 (0xb6eb4000) libslang.so.2 => /lib/libslang.so.2 (0xb6df9000) libSM.so.6 => /usr/lib/libSM.so.6 (0xb6df1000) libICE.so.6 => /usr/lib/libICE.so.6 (0xb6dd9000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb6dd6000) libXi.so.6 => /usr/lib/libXi.so.6 (0xb6dcd000) libXft.so.2 => /usr/lib/libXft.so.2 (0xb6dbb000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb6d8d000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb6d85000) libaviplayvidix-0.7.so.0 => /usr/lib/libaviplayvidix-0.7.so.0(0xb6d81000) libaviplaydha-0.7.so.0 => /usr/lib/libaviplaydha-0.7.so.0 (0xb6d4c000) libnsl.so.1 => /lib/tls/i686/cmov/libnsl.so.1 (0xb6d36000) libgpm.so.1 => /usr/lib/libgpm.so.1 (0xb6d30000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb6d11000) ==================== ./configure 's output ======================== checking for Base/configLinux.h.in... yes checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for sin in -lm... yes checking for main in -lz... yes checking for dlopen in -ldl... yes checking how to run the C preprocessor... gcc -E checking for X... libraries /usr/X11R6/lib, headers in standard search path checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for main in -lX11... yes checking for main in -lXext... yes checking for XF86VidModeGetAllModeLines in -lXxf86vm... yes checking for main in -lXext... (cached) yes checking for glInitNames in -lGL... yes checking for gluLookAt in -lGLU... yes checking for "OpenGL"-framework... no checking for "AGL"-framework... no checking for "Carbon"-framework... no checking for "QuickTime"-framework... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for PKG_IMAGEMAGICK___CFLAGS... checking for PKG_IMAGEMAGICK___LIBS... checking for ImageMagick++-config... no checking for main in -lMagick++... no checking for PKG_TIFF_CFLAGS... checking for PKG_TIFF_LIBS... checking for tiff-config... no checking for TIFFOpen in -ltiff... yes checking for PKG_JPEG_CFLAGS... checking for PKG_JPEG_LIBS... checking for jpeg-config... no checking for jpeg_read_header in -ljpeg... yes checking for PKG_LIBQUICKTIME_CFLAGS... -I/usr/include/lqt checking for PKG_LIBQUICKTIME_LIBS... -lquicktime -lpthread -lm -lz -ldl checking for PKG_LQT_CFLAGS... checking for PKG_LQT_LIBS... checking for lqt-config... yes checking for PKG_MPEG3_CFLAGS... checking for PKG_MPEG3_LIBS... checking for mpeg3-config... no checking for mpeg3_check_sig in -lmpeg3... yes checking for PKG_MPEG_CFLAGS... checking for PKG_MPEG_LIBS... checking for mpeg-config... no checking for OpenMPEG in -lmpeg... yes checking for PKG_AVIFILE_CFLAGS... -I/usr/include/avifile-0.7 checking for PKG_AVIFILE_LIBS... -laviplay checking for PKG_FFMPEG_CFLAGS... checking for PKG_FFMPEG_LIBS... checking for ffmpeg-config... no checking for av_open_input_file in -lavformat... no checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking linux/videodev.h usability... yes checking linux/videodev.h presence... yes checking for linux/videodev.h... yes checking for PKG_IEEE1394_CFLAGS... checking for PKG_IEEE1394_LIBS... checking for ieee1394-config... no checking for main in -ldv... yes checking for PKG_FTGL_CFLAGS... -I/usr/include/freetype2 checking for PKG_FTGL_LIBS... -lGLU -lGL -lfreetype -lz -lftgl checking for PKG_GLTT_CFLAGS... checking for PKG_GLTT_LIBS... checking for gltt-config... no checking for GLTTFont in -lgltt... no checking for pthread_create in -lpthread... yes checking for X... libraries /usr/X11R6/lib, headers in standard search path checking for ANSI C header files... (cached) yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking float.h usability... yes checking float.h presence... yes checking for float.h... yes checking for memory.h... (cached) yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for strings.h... (cached) yes checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking termios.h usability... yes checking termios.h presence... yes checking for termios.h... yes checking for unistd.h... (cached) yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking for GLsizeiptrARB... yes checking for unsigned int... yes checking size of unsigned int... 4 checking for void *... yes checking size of void *... 4 checking for error_at_line... yes checking for pid_t... yes checking for unistd.h... (cached) yes checking vfork.h usability... no checking vfork.h presence... no checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes checking whether gcc needs -traditional... no checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... yes checking for bzero... yes checking for floor... yes checking for gettimeofday... yes checking for memset... yes checking for munmap... yes checking for pow... yes checking for sqrt... yes checking for strchr... yes checking for strdup... yes checking for strrchr... yes checking for strstr... yes checking for lqt_add_video_track... yes checking for glBindProgramARB... yes checking for glBindProgramNV... yes checking m_pd.h usability... yes checking m_pd.h presence... yes checking for m_pd.h... yes checking whether compiler accepts "-freg-struct-return"... yes enabling "register struct return" allows to make use of FreeFrame-effects without recompiling them might break things, if you are using several different compilers checking whether compiler accepts "-O3"... yes checking whether compiler accepts "-fno-builtin"... yes checking whether compiler accepts "-falign-loops=16 -funroll-loops"... yes checking whether compiler accepts "-ffast-math"... yes AltiVec: ...... AltiVec: ...no... checking whether compiler accepts "-mmmx"... yes checking whether compiler accepts "-msse2"... yes checking whether linker accepts "-shared -Wl,-export-dynamic"... yes checking whether linker accepts "-bundle -bundle_loader /usr/local/bin/pd"... no checking for strip... strip checking if strip is GNU strip... yes checking for dos2unix... true configure: creating ./config.status config.status: creating Make.config config.status: creating Base/configLinux.h config.status: Base/configLinux.h is unchanged Result: Target : Gem.pd_linux Objects : Base Controls Geos Manips MarkEx Nongeos Particles Pixes openGL Configuration: Compiler : g++ CXXFLAGS : -g -O2 -freg-struct-return -O3 -fno-builtin -falign-loops=16 -funroll-loops -ffast-math -mmmx -msse2 : -I/usr/include/lqt -I/usr/include/lqt -I/usr/include/avifile-0.7 -I/usr/include/freetype2 INCLUDES : -I/usr/include/FTGL -I/usr/include/freetype2 DEFINES : LIBS : -ldv -lmpeg -lmpeg3 -ljpeg -ltiff -lGLU -lGL -lXext -lXxf86vm -lXext -lX11 -ldl -lz -lm -L/usr/X11R6/lib -lpthread : -lGLU -lGL -lfreetype -lz -lftgl -laviplay -L/usr/lib -lquicktime -lpthread -lm -lz -ldl -lquicktime -lpthread -lm -lz -ldl LDFLAGS : -shared -Wl,-export-dynamic : -L/usr/X11R6/lib Strip : strip --strip-unneeded Install path : /usr/local pure-data: version : 0.39 used optional libraries: font-rendering : FTGL image-support use ImageMagick : no use TIFF : yes use JPEG : yes video-support use mpeg : yes use mpeg-3 : yes use QuickTime : yes use aviplay : yes use ffmpeg : no input-support use v4l : yes use ieee1394 : yes misc using ARB-extensions : yes using NV-extensions : yes using reg-struct-ret : yes Now run make ...

2 1

GEM: tassellation patterns and persistence of data?
by alberto.zin＠poste.it 19 Jun '06

19 Jun '06

Hi all, I have two questions/curiosities about GEM: 1) is it possible/technically feasible to make tassellation patterns (regular division of the plane, eg. like Escher works) in GEM ? anybody did something similar ? 2) is it possible to have a (I don't know how to call it) "persistence of vision" effect in GEM ? I mean, suppose for example I want to use a "translateXYZ" for a rectangle; the effect I've in mind is something like a "trace" of the movement on the screen with configurable persistence of the trace.. I'm also thinking to oscilloscope-like effects in GEM ... Thanks in advance Alberto Zin

4 3

Re: [PD] how to trigger bang's with a period less than 1 milisecond
by Frank Barknecht 19 Jun '06

19 Jun '06

Hallo, Tim Blechmann hat gesagt: // Tim Blechmann wrote: > On Sun, 2006-06-18 at 21:50 +0200, Frank Barknecht wrote: > > I'm not sure what exactly you mean with "granularity" here, but if you > > could only generate messages in steps of ~1.5 msec or 64 samples at > > 44.1kHz you could forget about using Pd to do techno music someone > > would actually dance to. > > sorry, but how can you generate messages, that are _not_ aligned to a 64 > sample grid ... Every "clock-delayed message" (metro, del, pipe, qlist, ...) is not aligned to 64 samples, GUI generated messages like clicking on a [bng] are aligned. However to actually make use of this in signal externals, you need to do some extra work. vline~ does. See attached patch and doc/3.audio.examples/C04.control.to.signal.pd > well, a |metro 100.2| will create delays of 100.13ms and 101.59ms ... > (logical time, 64@44100Hz) Nope, it won't. ;) Ciao -- Frank Barknecht _ ______footils.org_ __goto10.org__

5 7

← Newer
1
...
7
8
9
10
11
12
13
...
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list June 2006