Pd-list April 2003

pd-list@lists.iem.at

135 participants
217 discussions

disabling noteout object to print in the console
by Alex 29 Apr '03

29 Apr '03

Hi, I have a patch that send message midi with [noteout]. This object prints into the console message such as: put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 put 1 msg 0 0 is it possible to disable that function (other than by touching to the code) ? I am using some other objects that send feedback that I need to watch out into the console. Thanks Alex

1 0

dac~'s signal too loud?
by Nick Morrison 29 Apr '03

29 Apr '03

Hi, Please forgive me if this is a commonly answered question, but I'm new and finding my feet :-) If I create a patch with: osc~ 440 ----> *~ 0.05 ----> dac~ just the same as 01.PART1.sinewave.pd in the documentation, I get a very distorted output (as I do when I open 01.PART1.sinewave.pd.) If I reduce the *~ figure to anywhere below 0.001, I seem to get an almost artifact-free signal. However, anything above that results in a highly distorted signal. testtone.pd is painful to the ear :-) Just too much volume, somewhere along the line. Is there an overall volume control somewhere that I haven't tweaked or found yet? I'm running pd on FreeBSD 4.8, and it came out of the ports. It's version 0.35.23. I'm running it on a tiny Sony Vaio laptop, which is said to have a Yamaha DS-1E (YMF754) -based sound device. Has anyone else had (or solved!) this particular issue? Nick -- Nick Morrison : <nickm(a)internode.com.au> Internode : http://www.on.net/ # find / -user your -name base -exec chown us {} \;

3 3

Re: [PD] compression codecs
by /////++christian 28 Apr '03

28 Apr '03

>what OS are you using and what do you mean by 'good'? if good means >nice images with little compression artifacts then that suggests a >different set of codecs than small file size or fast decompression. unfortunately i am using winXP and 'good' means nice images and fast decompression ;) the picture quality of cinepak and indeo5 (lil bit better) is quite bad, but both work quite good on my machine. i was just thinking about any other codec that maybe looks better at same performance ... chr. --//--ad wolferl: geforce2, 32mb

7 9

Control Messages
by Michael McGonagle 28 Apr '03

28 Apr '03

Hello all, I have been working on creating Abstractions that allow me to group a set of line objects that are used to control various parameters via messages. I group all these things together because they all share the same line time/rate. So, I have an instrument that has many parameters that all have "message" destination points. I would like to use my line control groups to send to different parameters. Is there a way to, within an abstraction, to dynamically change the destinations of a send object? I have attached two versions of what I have. Any comments and/or suggestions would be very helpful and appreciated. Mike #N canvas 756 329 470 320 10; #X obj 53 24 inlet; #X floatatom 128 120 10 0 0 1 level1 - -; #X floatatom 128 172 10 0 0 1 level2 - -; #X obj 53 87 f 0; #X obj 53 118 pack 0 0; #X obj 135 69 tgl 15 0 empty empty spigot 0 -6 32 8 -262144 -1 -1 0 1; #X obj 53 54 spigot; #X obj 53 149 line 0 \$1; #X obj 53 180 s \$2-adj; #X obj -6 87 delay 0; #X obj -6 218 outlet; #X obj 93 24 inlet; #X obj 133 24 inlet; #X obj 173 24 inlet; #X floatatom 128 224 10 0 0 1 rate - -; #X obj 256 87 f 0; #X obj 256 118 pack 0 0; #X obj 256 149 line 0 \$1; #X obj 256 180 s \$3-adj; #X obj 235 7 loadbang; #X msg 235 26 1; #X connect 0 0 6 0; #X connect 1 0 3 1; #X connect 2 0 15 1; #X connect 3 0 4 0; #X connect 4 0 7 0; #X connect 5 0 6 1; #X connect 6 0 3 0; #X connect 6 0 9 0; #X connect 6 0 15 0; #X connect 7 0 8 0; #X connect 9 0 10 0; #X connect 11 0 1 0; #X connect 12 0 2 0; #X connect 13 0 14 0; #X connect 14 0 9 1; #X connect 14 0 4 1; #X connect 14 0 16 1; #X connect 15 0 16 0; #X connect 16 0 17 0; #X connect 17 0 18 0; #X connect 19 0 20 0; #X connect 20 0 5 0; #X coords 0 0 1 1 200 140 1; #N canvas 756 329 474 324 10; #X obj 53 24 inlet; #X floatatom 128 120 10 0 0 1 level1 - -; #X floatatom 128 172 10 0 0 1 level2 - -; #X obj 53 87 f 0; #X obj 53 118 pack 0 0; #X obj 135 69 tgl 15 0 empty empty spigot 0 -6 32 8 -262144 -1 -1 0 1; #X obj 53 54 spigot; #X obj 53 149 line 0 \$1; #X obj 53 180 s \$2-adj; #X obj -6 87 delay 0; #X obj -6 218 outlet; #X obj 93 24 inlet; #X obj 133 24 inlet; #X obj 173 24 inlet; #X obj 256 87 f 0; #X obj 256 118 pack 0 0; #X obj 256 149 line 0 \$1; #X obj 256 180 s \$3-adj; #X floatatom 128 224 10 0 0 1 level3 - -; #X floatatom 128 276 10 0 0 1 rate - -; #X obj 343 87 f 0; #X obj 343 118 pack 0 0; #X obj 343 149 line 0 \$1; #X obj 213 24 inlet; #X obj 343 180 s \$4-adj; #X obj 261 5 loadbang; #X msg 261 24 1; #X connect 0 0 6 0; #X connect 1 0 3 1; #X connect 2 0 14 1; #X connect 3 0 4 0; #X connect 4 0 7 0; #X connect 5 0 6 1; #X connect 6 0 3 0; #X connect 6 0 9 0; #X connect 6 0 14 0; #X connect 6 0 20 0; #X connect 7 0 8 0; #X connect 9 0 10 0; #X connect 11 0 1 0; #X connect 12 0 2 0; #X connect 13 0 18 0; #X connect 14 0 15 0; #X connect 15 0 16 0; #X connect 16 0 17 0; #X connect 18 0 20 1; #X connect 19 0 9 1; #X connect 19 0 4 1; #X connect 19 0 15 1; #X connect 19 0 21 1; #X connect 20 0 21 0; #X connect 21 0 22 0; #X connect 22 0 24 0; #X connect 23 0 19 0; #X connect 25 0 26 0; #X connect 26 0 5 0; #X coords 0 0 1 1 200 140 1;

2 1

Re: RE: [PD] teaching PD to newbies [WAS: Re: [GEM] GEM users request ]
by bbogart＠ryerson.ca 27 Apr '03

27 Apr '03

Fantastic idea, I will be working on a few tutorials myself soon. I suppose we should design a template for tutorials to keep things standard, anyone with documentation experience have any suggestions? an initial thought would be following Chris's format with html plus example patches... Ben ----- Original Message ----- From: Hans-Christoph Steiner <hans(a)eds.org> Date: Sunday, April 27, 2003 11:28 am Subject: RE: [PD] teaching PD to newbies [WAS: Re: [GEM] GEM users request ] > > It would be really great if we could combine all of the existing > tutorialsout there into one coherent, navigatible set of > tutorials. Just like PDDP > is becoming the central repository for docs, and the CVS is the > centralrepository for externals, there should also be a central > repository for > tutorials. > > I think that the tutorials and PDDP should ultimately be part > of the pure-data.sf.net CVS. It makes working collaboratively much > easier than if these files are spread out all over the net. > > Once this > semester is over, and I get some breathing room, I am going to > make a > "Getting Help" section for pure-data.org with links to all of the > docs and > tutorials I can find. If all of the docs and tutorials were > interconnected and easily navigatible, that would be an amazing > resource. > > .hc > > On Fri, 25 Apr 2003, David Sabine wrote: > > > Hello all, > > > > This type of idea is inline with my eventual goal for the PDDP > files.> > > I have felt that it's very important to, aside from brief and > precise> explanations of the inlets/outlets and arguments of each > object, offer at > > least one example of the object being used in a real and typical > situation.> I haven't written any complete tutorials, because I > haven't felt that it was > > part of the PDDP mandate -- however, I've been able to offer some > > 'real-world' examples of the objects in context. > > > > As tutorials are written and completed I would like to provide > web links in > > the PDDP to relevant tutorials. For example, if an online > tutorial shows a > > typical usage of [loadbang] (or anything else), then the > [loadbang].pd help > > document should provide a link to that tutorial. > > > > Obviously, [loadbang] is rather straight forward, but other help > files would > > benefit a lot from online tutorials. > > > > For those writing these wonderful tutorials - I would appreciate > if you > > contact me if you feel any of the PDDP files deserve a link to your > > tutorial. > > > > Regards, > > Dave Sabine > > > > p.s.: I like this thread a lot. There have been some good ideas > - many of > > which are possible, important, and will make PD a more valuable > and useable > > tool for all users. > > > > > > > > > > > > _______________________________________________ > > PD-list mailing list > > PD-list(a)iem.kug.ac.at > > http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list > > > > zen > \ > \ > \[D[D[D[D > > > _______________________________________________ > PD-list mailing list > PD-list(a)iem.kug.ac.at > http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list >

3 2

compression codecs
by /////++christian 27 Apr '03

27 Apr '03

hi, are there any _good_ compression codecs to produce video files pd can handle? 'cause cinepak is not really satisfactory ... thanks for suggestions... chris

2 1

pix_write
by t208898 27 Apr '03

27 Apr '03

Hi. I have a litte pd/gem patch that draws a rotating square. But when i connect to outlet of "square" to "pix_write" it seems to remember all previous rotations and adds them all to the picture. How do i clear the buffer before each write? thanks

2 1

Re: [PD] maximum of Oscillators
by pix 27 Apr '03

27 Apr '03

*advertises* nqpoly is available at http://pix.test.at/pd/nqpoly/ it's an abstraction that helps instantiating lots of copies of other abstractions. clone is an external that does a similar thing, and is available at http://www.akustische-kunst.de/puredata/clone/ pix. On Fri, 03 Jan 2003 13:32:43 +0100 thomas gorbach <blackinch(a)t0.or.at> wrote: > pix wrote: > > >oh, you mean a test to see how many osc~ objects pd can run > >simultaneously? > > > >depends on your cpu. you could build an nqpoly (or clone) compatible > >object, so you could easily create many osc~'s and see what the cpu > >usage is like. > > > What you mean with nqpoly or clone. > Are there existing objects like that ? > In witch Lib ? > > greetns > > > > >a note, with nqpoly, you should turn off audio computation while > >modifying parameters like the number of instances, as it speeds up the > >garbage collection (?) and recreation of the objects. > > > >pix. > > > >On Fri, 03 Jan 2003 10:23:34 +0100 > >thomas gorbach <blackinch(a)t0.or.at> wrote: > > > >>David Sabine wrote: > >> > >>>Hello, > >>> > >>>It appears that oscillators can perform frequencies to 999999 hz and > >>>then above 1000000 hz - but the accuracy of the wave forms at that > >>>frequency are questionable as PD converts the numbers to 1.0000+e6 > >etc.>>Certainly, the > >>>resolution of waves above 999999 hz will be diminished? > >>> > >>>This is obviously far beyond the human ear's audio range. > >>> > >>>Also, depending on your sample rate, your audio hardware might be > >>>incapable of producing frequencies above a certain range. For > >example,>>the highest frequency that a 44.100 khz sample rate can > >achieve is>>22.05 khz. Frequencies higher than that are either snipped > >entirely by>>your audio hardware or appear as very low frequency > >artefacts.>> > >>>Hardware that is capable of sampling audio at 192 khz have a maximum > >>>frequency output of 96000 hz. > >>> > >>>Regards, > >>>Dave Sabine > >>> > >>> > >>> > >>>-----Original Message----- > >>>From: pd-list-admin(a)iem.kug.ac.at > >[mailto:pd-list-admin@iem.kug.ac.at]>>On Behalf Of thomas gorbach > >>>Sent: January 3, 2003 2:35 AM > >>>To: PD-list(a)iem.kug.ac.at > >>>Subject: [PD] maximum of Oscillators > >>> > >>>hello List > >>> > >>>1. question > >>>is there someone who tried the maximum of oscillators pd can perform > >?>> > >>>2. question: > >>>if i open a patch with an oscil i get this text. > >>> > >>>#N canvas 16 64 314 182 10; > >>>#X obj 66 54 osc~; > >>>#X obj 109 54 osc~; > >>>#X obj 66 86 *~ 0.1; > >>>#X obj 66 121 dac~; > >>>#X floatatom 66 19 5 0 0 0 - - -; > >>>#X obj 109 33 + 5; > >>>#X connect 0 0 2 0; > >>>#X connect 1 0 2 0; > >>>#X connect 2 0 3 0; > >>>#X connect 2 0 3 1; > >>>#X connect 4 0 0 0; > >>>#X connect 4 0 5 1; > >>>#X connect 5 0 1 0; > >>> > >>>is there any systematic in the numbering of the boxes ? > >>> > >>>Greetns > >>>TOM > >>> > >>> > >>> > >>>_______________________________________________ > >>>PD-list mailing list > >>>PD-list(a)iem.kug.ac.at > >>>http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list > >>> > >>> > >>> > >>Yes this i know. > >>But i'm looking for the amount of oscil pd can produce. > >> > >>greetns > >>TOM > >> > >

1 0

maximum of Oscillators
by thomas gorbach 27 Apr '03

27 Apr '03

hello List 1. question is there someone who tried the maximum of oscillators pd can perform ? 2. question: if i open a patch with an oscil i get this text. #N canvas 16 64 314 182 10; #X obj 66 54 osc~; #X obj 109 54 osc~; #X obj 66 86 *~ 0.1; #X obj 66 121 dac~; #X floatatom 66 19 5 0 0 0 - - -; #X obj 109 33 + 5; #X connect 0 0 2 0; #X connect 1 0 2 0; #X connect 2 0 3 0; #X connect 2 0 3 1; #X connect 4 0 0 0; #X connect 4 0 5 1; #X connect 5 0 1 0; is there any systematic in the numbering of the boxes ? Greetns TOM

3 5

Re: [PD] readanysf~ beta
by t.barrass＠pgrad.unimelb.edu.au 27 Apr '03

27 Apr '03

hi august, > about the crashes? did you compile it yourself? yes > if so, can you send me a backtrace from gdb? after loading libs as usual, this: (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2224)] 0x401838fe in pthread_mutex_lock () from /lib/libpthread.so.0 (gdb) tim

1 0

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 April 2003