Pd-list February 2006

pd-list@lists.iem.at

143 participants
216 discussions

pix_movie problem
by Item State 02 Feb '06

02 Feb '06

hi, i'm new to PD and GEM. i'm trying to write a simply movie player, starting off with the help patch of pix_movie . it seems to work basically fine, but the "texture" is only monochrome, like it would take just one pixel of the movie and paint the whole geo with that pixel's colour (i see the colour spinning as the frames progress). i'm on mac os x 10.3.9 / quicktime 7.0.4 and use the latest build from h.c. steiner . when i open the movie, the frame# and dimensions are reported correctly . i also read that there was an issue with power-of-two sizes of textures, so i tried to load a 256x256 movie as well, same problem. the patch is attached. i also tried a different geo (cube instead of rectangle), same behaviour. some other questions : - how do i determine the FPS value of the movie? - can i display movies without the open GL context ; i don't need open GL at all, i just need to render the plane movie data, like i would connect a jit.qt.movie to a jit.window object in jitter. - can i switch to fullscreen mode? thanks a lot! best, -sciss- ____________________________________________________ Do you Yahoo!? The New Yahoo! Movies: Check out the Latest Trailers, Premiere Photos and full Actor Database. http://au.movies.yahoo.com

2 1

Command line flags to Pd*.app on OS X
by Jamie Bullock 02 Feb '06

02 Feb '06

Hi, I understand that on OS X, using the recent Pd*.app bundles it is possible to modify settings and/or pass command line parameters via key/string pairs in ~/Libarary/Preferences/org.puredata.pd.plist. Is there any way to embed such settings inside the bundle? I ask this because i want to package up PD for and OS X user, and auto-launch a particular patch. I don't want them to have to 'install' anything if at all possible. I see that this has been discussed before, but I didn't really understand the answers, as I am not particularly Mac OS X savvy. Something about .command files? TIA, Jamie

2 1

Re: [PD-announce] A new version of FFTease is now available for Pd
by Eric Lyon 02 Feb '06

02 Feb '06

The MIT license is fine with me. I just put it in with the code files. So you are now welcome to modify and redistribute as you wish under that license. Eric > But in the case of FFTease, you could release it under a MIT or BSD > license, both of which let anyone do anything with it with minor > restrictions: both require that the copyright notice is always > distributed with any software that uses the code, and the BSD license > requires that you get written permission before using the name of the > software/copyright owner. Both of these are completely compatible with > the GPL. You could also put it in the public domain, then anyone could > do anything with it, regardless. >

2 2

Re: [PD-announce] A new version of FFTease is now available for Pd
by Eric Lyon 02 Feb '06

02 Feb '06

> What are the rules about distributing this? > There are no rules :) You can do whatever you like with it. > > BTW, where's the source code of that release of FFT? I don't see the > source available on the author's page. (I am blind, right?) > The main reason I did not post the source is because it is not yet unified or easy to compile, and I wanted to make the externals available before however many months it might take for me to get the code in shape. However you are welcome to get the code over here (but you have to figure out how to compile it): http://eamusic.dartmouth.edu/~eric/MAX/FFTease/code.html > link error 0 dyld: pd multiple definitions of symbol _bitrv2 > /usr/local/lib/pd/morphine~.pd_darwin definition of _bitrv2 > /usr/local/lib/pd/pvwarp~.pd_darwin definition of _bitrv2 > I encountered that problem a long time ago; the externals make calls to another library and earlier versions of Pd had a problem with this. I cannot however reproduce this problem on my current versions of Pd (0.38-3 and 0.38.4-extended-RC6). If more people encounter this conflict please let me know. > >> But it would be quite > >> nice to > >> be able to distribute FFTease built-in to Pd-extended. > > I'm happy for you to do so, but only if you are comfortable with the way the software has been released. > > the homepage states (in red!): "FFTease may be used freely for any > artistic or research purpose." > which i consider to be _not_ compatible with the GPL. > I think this is probably correct; as I understand it, the GPL places some restrictions on what you can do with the code. I think we are a bit more permissive, but if there is some way that you find our "licencette" more restrictive, I'm willing to consider relaxing it. Eric

4 5

Re: PD-list Digest, Vol 11, Issue 2
by Eric Lyon 02 Feb '06

02 Feb '06

> > > The main reason I did not post the source is because it is not yet unified > > or easy to compile, and I wanted to make the externals available before > > however many months it might take for me to get the code in shape. However > > you are welcome to get the code over here (but you have to figure out how > to > > compile it). > > Figuring out stuff like this is what some people here specialize in. ;) > I'm aware of that; for now the code is online for anyone who would like to play with it, (http://eamusic.dartmouth.edu/~eric/MAX/FFTease/code.html) but I'm not happy with its current state, so I guess I don't want to put it on the main page where someone might download it, try to compile it and it probably wouldn't work for them. There are a lot of gurus on this list, but I think it's important to have consideration for some of the people here who don't eat C code for breakfast. > > I think this is probably correct; as I understand it, the GPL places some > > restrictions on what you can do with the code. I think we are a bit > > more permissive, but if there is some way that you find our "licencette" > > more restrictive, I'm willing to consider relaxing it. > > The problem is, that any Open Source/Free Software by definition must > not pose any restrictions on how that software is used. So if FFTease > would *only* be allowed to be used for research and arts, but not for > any other uses (like making coffee), then FFTease would not be free > software as it violates "freedom 0": "The freedom to run the program, > for any purpose" - including making coffee. > Thanks for putting it that way. Technically it doesn't prohibit you from making coffee or doing anything else, but I see that explicitly stating the things that we expect most people would do with FFTease might imply that you can't do other things with it. I suppose we could say "can be freely used for any artistic or research purpose, or anything else you can think of," but that sounds kind of clunky. Note we did not use the word *only* in the licencette - we said what you *could* do, not what you couldn't do. I might consider something like Christopher's licencette for HyperUpic which states, "use freely at your own psychological risk." It's tough to cover all bases. For example, IIRC Miller states that you can use Pd "for any reasonable purpose." But I reckon that many uses of Pd might be considered unreasonable and that's what makes them interesting. If this is really a problem for people, I'll give it some thought and see if I can come up with something that doesn't offend my sense of aesthetics. Eric

3 2

Status of OSCx (for OS X)
by Mark Polishook 02 Feb '06

02 Feb '06

trying to compile OSCx as per the README instructions ./configure - works ok make - stops with the following /usr/bin/ld: can't open: ../../../pd/bin/pd (No such file or directory, errno = 2) collect2: ld returned 1 exit status make[1]: *** [sendOSC.pd_darwin] Error 1 what's the next step? .... the question really is what's the best way to add OSCx to pd? .... tia - mp

3 3

QuickTime movies (was: pix_movie problem)
by Item State 02 Feb '06

02 Feb '06

hi... i checked out PDP in the meantime which is probably more suited for what i want (quicktime movie playback). doesn't work either, however ... i open the pdp_canvas help patch. i get a couple of error messages from pdp_v41 which is probably because i don't have video live input (which is fine). however i cannot see the screen. if i add an explicit "create" message and connect to pdp_xv, i get "pdp_xv: cant open display :0" . also, pdp_yqt cannot open any of the movies, i always get "pdp_yqt: unsupported video codec" (tried with Photo-JPEG, Motion JPEG, Video, Sorenson) ... am i missing something? thanks, -sciss- ____________________________________________________ Do you Yahoo!? Stay in touch via Yahoo! Messenger with all your contacts on your 3 Mobile. http://au.mobile.yahoo.com/mweb/3-mobile.html

2 1

pix_movie problem (p.s.)
by Item State 02 Feb '06

02 Feb '06

forgot to attach the patch. ____________________________________________________ Do you Yahoo!? Take your Mail with you - get Yahoo! Mail on your mobile http://au.mobile.yahoo.com/mweb/index.html

2 1

ANN: Csound 5.00 Release
by Victor Lazzarini 02 Feb '06

02 Feb '06

Csound 5 has finally arrived, enjoy... -Victor ================================================== After what has seemed a very long time (because it was...) we are releasing csound5.00 The binary, manuals and source files are on http://sourceforge.net/projects/csound and look for the csound5 files. The opportunity has been taken to tidy up the assembly of csound4.23 and earlier files and we are leaving the 4.23 files for a short while. Main message -- everyone should change to csound5. More robust, faster, more facilities, more fun, more music. ==John ffitch ------------------------------------------------------------------------ Release Notes for Csound 5.00 ----------------------------- The developers are very pleased to be releasing Csound5, for Linux (32 and 64 bit), Mac OSX and Windows, together with an uptodate manual. The system can be downloaded from http://sourceforge.net/projects/csound More details and further information can be found in the csound-develop mailing list at sourceforge and the main user mailing list ar csound(a)lists.bath.ac.uk The changes from version 4.23 are extensive. The internal structure of the code has been radically changed, but the language remains compatible with Csound4, and all old orchestra/scores should run unchanged. The main visible change is that we are using a plugin style of system. many of the opcodes are now loaded at start-up. This opens the way for private opcode libraries, and opcodes released under other licences than LGPL. The other major change is a move to the use of external libraries where possible. All the internal code for sound files, realtime audio etc has been replaced. We are now using libsndfile for audio file I/O, and one of ALSA, PortAudio, CoreAudio, MME or ASIO for realtime. MIDI may be handled by PortMIDI as well. The incorporation of Open Sound Control facilities uses the liblo library. A number of opcodes from csoundAV and csoundVST are now part of the main system. Another major change is that Csound5 is embeddable in other programming systems, using an API for information linkage. We are including Python, Java and other bindings for the API. Csound5 can also have multiple instances and is re-entrant. In addition there are a number of new opcodes, and of course bug fixes. We believe that csound5 is faster than csound4, and we encourage all users to move to it. NOTE: IT MAY BE NECESSARY ON SOME PLATFORMS TO HAVE EITHER ENVIRONMENT VARIABLES OPCODEDIR OR OPCODEDIR64 SET TO POINT TO DIRECTORY WHERE OPCODES LIVE. THE RELEASED FILES ARE BELIEVED TO BE SAFE AND CORRECT IN THIS RESPECT BUT BEWARE! New features: ------------ Access to multiple ALSA devices FLTK widgets reworked and synchronised with csoundAV User defined gens with names (rather than numbers) --expression-opt command option Information on time for each phase of csound if required Command line options to set ID tags in output soundfile (title/copyright etc) Jack available as output device --sched option now accepts a priority value -+rtaudio option to select output system Many new command line options Utilities to create csd files from orc/score Tcl/TK frontends (cstclsh and cswish) Can use looping structures in WAV files as well as AIFF Increased number of possible input and output audio file formats named channels #ifdef in orchestra removed limitation of only one track in MIDI input files MIDI output can also be written to a file (this is somewhat limited) MIDI-style extra time and release (xtratim, linsegr, etc.) is now also possible with score notes string variables (of type S) automatic conversion of some C-style escape sequences (\n, \r, ASCII code in octal \ooo format, etc) in string constants made internal indexes to orchestra variables 32 bit (was 16 bit in Csound 4), allowing for larger and more complex instruments replaced old PVOC format with PVOC-EX in all related opcodes SADIR SSDIR and INCDIR can now be a colon separated list of directories New Opcodes: ----------- maxk tab, tabw, and tb0()..tb15() vst4cs plugin opcodes pconvolve ftconv loris opcodes Python opcodes fluid opcodes chani and chano; chnset and chnget (string indexed) GEN43 a number of pvs (streaming phase vocoder) opcodes moogladder statevar fofilter syncgrain miditempo event_i reverbsc (Sean Costello's waveguide reverb) freeverb gentune GEN operation GEN51 GEN52 diskin2 turnoff2 a-rate int() and frac(), and round(), floor(), and ceil() << and >> operators STK (Perry Cook) instruments available from original code k() function Mixer opcodes OSCrecv, OSClisten, OSCsend loop opcodes printf, printf_i string hacking opcodes Bug Fixes: --------- Error in tablew fixed Minor fixed in dcblock Include files were confused by sections Improved reading of command line Fixes in dynamic fgen numbers gogobel and vibraphone amplitude fix Arguments to schewhen were wrong Better checking in bqrez minor checking in grain wguide2, wguide1 avoid very low frequencies wgpluck bug fix Some error messages corrected and typos fixed FLsetVal arguments were wrong outo missed out channel 6 fixed bugs and improved error reporting in ^+ and ^- code. kread, kdump and a number of other opcodes will take string arguments from the score bug fix in sinc window (gen20) Added iskip options to moogvcf, vco, bqrez, pareq, tbvcf and rezzy values rounded rather than truncated in deltap, comb, and delay removed spurious initial values from some MIDI opcodes Joystick was upside down lpshold and loopseg changed to agree with csoundAV marimba now allows zero probability of a multiple strike Added skipinit argument to diskin and soundin wave-terrain fixes for phase error accumulation (on long notes) new optional argument to delayr and all deltap opcodes, to allow delay taps to read from any of the nested delayr/delayw pairs, not just the last new optional argument to distort1 opcode (defaults to zero), to select amplitude scaling mode (0: default, compatible with original version; 1: relative to 0dBFS, same as mode 0 if 0dbfs is 32768; 2: unscaled) valpass fixed parameter overwriting Improved accuracy in some filters Improvements in bowedbar JPff -- 1 Feb 2006 Files on Sourceforge ==================== Sources: Csound5.00_src.tar.gz Csound5.00_src.zip Csound5.00_OS9_src.smi.bin Csound5.00_src_all.tar.gz (including Loris and STK code) Csound5.00_src_all.zip (including Loris and STK code) Manual Csound5.00_manual_chm.zip Csound5.00_manual_html.zip Csound5.00_manual_pdf.zip Csound5.00_manual_pdf_A4.zip Csound5.00_manual_single_file.zip OS9: Csound5.00_OS9.smi.bin OSX: Csound5.00_OSX10.3.tar.gz Csound5.00_OSX10.4.tar.gz Linux Csound5.00_i686.rpm Csound5.00_x86_64.rpm [Linux for non-root users on X86_64 Csound5.00_x86_64d.tar.gz Csound5.00_x86_64f.tar.gz ] Windows Csound5.00_win32.i686.zip Csound5.00_win32.exe (with installed) Victor Lazzarini Music Technology Laboratory Music Department National University of Ireland, Maynooth

1 0

Freeverb~ Makefile
by J_J_FUX J_J_FUX 02 Feb '06

02 Feb '06

Greetings friends of puredata In the puredata CVS there is no makefile for freeverb~ , ive tryed myself to write one but always with failure . Dose anyone have a makefile for freeverb~ ( linux ) that they could post ?. or perhaps there is one already online somewhere that i have missed and could be directed to . thanks and all the best for 2006 ! --------------------------------- Yahoo! Autos. Looking for a sweet ride? Get pricing, reviews, & more on new and used cars.

3 5

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 February 2006