Pd-list July 2010

pd-list@lists.iem.at

124 participants
188 discussions

0.43 and GOP
by cyrille henry 31 Aug '10

31 Aug '10

hello, i give 0.43 an other try. it look like being seriously broken with GOP. by example, i try opening my lighting patch : http://www.chnry.net/ch/?092-Lighting-for-Pure-Data-lightboard&lang=en then opening "memoire_lumiere" subpatch : all GOP are not visible and i've got error in pd log. then, closing everything give lot's of errors : error: .x857a0a8: no such object and i have to quit pd. Cyrille

2 1

openpanel crash
by Alexandre Porres 30 Aug '10

30 Aug '10

hi there, I'm coming again with the same problem I brought up sometime ago. I'm experiencing some weird [openpanel] crashes, maybe is something with the new MAC OS Snow Leopard? anyway, I'm sending the patch attached as a text. Apparently, if I create first some other patch and use [openpanel] and nothing else, it doesn't crash, then I can open this patch so it works without crashing. it's crashing both in Pd Vanila 42.5 as in extended 41.4 cheers alex -------------- #N canvas 578 54 742 582 12; #X obj 514 36 loadbang; #X obj 122 230 bng 25 250 50 0 empty empty Escolher_Sample -45 -12 2 20 -4032 -1 -1; #X obj 156 273 nbx 6 19 0 100 0 0 empty sr Sample_Rate_em_KHz 1 -13 1 15 -4034 -91543 -1 44.1 256; #N canvas 302 166 923 479 sampler 0; #X obj 163 -65 cnv 15 100 60 empty empty empty 20 12 0 14 -233017 -66577 0; #X obj 314 48 /; #X obj 314 91 * 1000; #X obj 170 -26 nbx 8 14 -1e+37 1e+37 0 0 empty empty empty 0 -6 0 10 -203904 -1 -1 528552 256; #X obj 314 72 nbx 5 14 -1e+37 1e+37 0 0 empty empty empty 0 -6 0 10 -232576 -1 -1 11.9853 256; #X obj 314 115 nbx 5 14 -1e+37 1e+37 0 0 empty empty empty 0 -6 0 10 -204786 -1 -1 11985.3 256; #X text 372 67 N˙mero de Amostras dividido pelo Sample Rate do Arquivo d· o tamanho do arquivo em segundos; #X obj 261 245 line~; #X msg 261 222 0 \, \$1 \$2; #X obj 261 162 float; #X obj 170 96 metro; #X obj 170 76 tgl 15 0 empty empty empty 0 -6 0 10 -155649 -262130 -1 1 1; #X text 41 132 Sample Size; #X text 32 96 sample em Miliseg; #X text 13 78 Bangs a cada Loop do; #X msg 170 47 1; #X obj 169 -97 inlet; #X obj 261 320 outlet~; #X obj 313 -96 inlet; #X obj 345 24 * 1000; #X obj 261 188 pack 0 0; #X obj 261 271 tabread4~ \$0-sampler; #X obj 144 -94 bng 15 250 50 0 empty empty empty 0 -6 0 10 -262130 -1 -1; #X text 413 24 Sample Rate do Arquivo (entrada È em Khz \, por isso multiplicamos por 1000).; #X text 327 188 Lista (N˙mero de Amostras do Sample e sua duraÁ„o em ms); #X text 425 218 A cada Loop \, o line~ recebe duas mensagens. A primeira (Zero) leva o [line~] imediatamente ao zero. A segunda È uma lista com N˙mero de amostras e tempo em Milisegundos. Com esses dados o line~ gera um fluxo de n˙meros crescentes que serve de Ìndices para o [tabread4~]. ; #N canvas 0 22 450 300 (subpatch) 0; #X coords 0 1 100 -1 615 95 1; #X restore 242 212 graph; #X obj 265 101 f; #X obj 314 24 f; #X obj 94 -96 inlet; #X obj 313 -51 t b f; #X obj 170 -3 trigger bang float; #X obj 170 123 trigger b b; #N canvas 54 51 867 383 openpanel 0; #X obj 187 84 openpanel; #X symbolatom 187 112 80 0 0 0 - - -; #X obj 152 195 pack symbol symbol; #X text 92 83 ABRE ARQUIVO; #X text 72 169 de Arquivo e; #X text 89 185 Tabela; #X text 45 153 Cria lista com nome; #X obj 275 172 symbol \$0-sampler; #X text 330 229 Soundfile recebe a mensagem "Resize + (nome do arquivo) + (nome da tabela)" e joga o arquivo de som na tabela ao mesmo tempo em que redimensiona a tabela para o tamanho do arquivo! O Outlet d· o tamanho da tabela em n˙mero de amostras.; #X obj 187 144 t symbol bang; #X obj 188 51 inlet; #X obj 152 283 soundfiler; #X msg 152 258 read -resize \$1 \$2; #X obj 152 312 outlet; #X obj 165 52 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 -1; #X connect 0 0 1 0; #X connect 1 0 9 0; #X connect 2 0 12 0; #X connect 7 0 2 1; #X connect 9 0 2 0; #X connect 9 1 7 0; #X connect 10 0 0 0; #X connect 11 0 13 0; #X connect 12 0 11 0; #X connect 14 0 0 0; #X restore 169 -56 pd openpanel; #X obj 293 136 nbx 8 14 -1e+37 1e+37 0 0 empty empty empty 0 -6 0 10 -203904 -1 -1 528552 256; #X text 371 111 Tamanho do Sample em ms (milisegundos); #X connect 1 0 4 0; #X connect 2 0 5 0; #X connect 3 0 31 0; #X connect 4 0 2 0; #X connect 5 0 27 1; #X connect 5 0 20 1; #X connect 7 0 21 0; #X connect 8 0 7 0; #X connect 9 0 20 0; #X connect 10 0 32 0; #X connect 11 0 10 0; #X connect 15 0 11 0; #X connect 16 0 33 0; #X connect 18 0 30 0; #X connect 19 0 1 1; #X connect 20 0 8 0; #X connect 21 0 17 0; #X connect 22 0 33 0; #X connect 27 0 10 1; #X connect 28 0 1 0; #X connect 29 0 15 0; #X connect 30 0 28 0; #X connect 30 1 19 0; #X connect 31 0 15 0; #X connect 31 1 28 0; #X connect 31 1 34 0; #X connect 32 0 9 0; #X connect 32 1 27 0; #X connect 33 0 3 0; #X connect 34 0 9 1; #X restore 89 304 pd sampler; #X obj 203 350 cnv 15 397 148 empty empty empty 20 12 0 14 -233017 -66577 0; #N canvas 0 22 454 304 (subpatch) 0; #X array \$0-sampler 528552 float 0; #X coords 0 1 528551 -1 400 150 1; #X restore 202 350 graph; #X text 45 86 Esse patch È um sampler em loop \, mas tambÈm podemos mudar o pitch e o tempo do sample ao ajustar o sample rate do nosso sampler. Um sample rate menor que o do aquivo o tocar· mais lento e mais grave \, enquanto que um maior o toca mais r·pido e mais agudo. ; #X obj 81 336 dac~; #X obj 31 27 cnv 15 315 40 empty empty Sampler-Looper: 20 12 0 24 -262144 -66577 0; #X obj 89 274 bng 15 250 50 0 empty empty empty 17 7 0 10 -204800 -1 -1; #X text 59 253 restart; #X msg 514 60 \; pd dsp 1 \; sr 44.1; #X connect 0 0 11 0; #X connect 1 0 3 1; #X connect 2 0 3 2; #X connect 3 0 7 0; #X connect 3 0 7 1; #X connect 9 0 3 0;

8 16

[PD-announce] GridFlow 9.9
by Mathieu Bouchard 16 Aug '10

16 Aug '10

GridFlow 9.9 available now !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | `---> at http://gridflow.ca/ ChangeLog version 9.9 (2010.05.05): * added class [gridflow] for reporting version number of gridflow * [print]: pointer: write "0x" and not "0x0x" * added examples supercycloid.pd, simple_mask.pd, tictactoe.pd * renamed example blob.pd to shadebob.pd * reviewed and updated a lot of examples. * support GEM 91, 92 and 93 all at once, with runtime autodetection (NOT compile-time!) * fixed bug about [#to_pix] when created after [gemwin] was last activated * [#to_pix] and [#from_pix]: when in colorspace rgba, preserve alpha instead of setting to 0 * [#to_pix]: when in colorspace rgb, alpha defaults to 255 instead of 0 * [#to_pix]: correct GL_RGBA vs GL_BGRA on OSX * added [gf/string_length] [doc_link] [doc_accolade] [#lop_space] * added even more missing helpfiles... * [#io.quicktimecamera]: added brightness, contrast, hue and colour (saturation) control * [#io.x11]: setcursor: support 77 cursors instead of 64; and reject out-of-range values * [#color]: runs faster * [#io.videodev]: added colorspace rgba, with alpha=255. * [#io.videodev]: added conversion from RGB to colorspace "magic" * [#camera]: added colorspace rgba * [#io.quartz]: added support for keypress and keyrelease * [#io.quartz]: added 'menubar' method (show/hide system menubar on OSX) * [#io.quartz]: added hidecursor and setcursor * [#io.quicktimecamera]: colorspace rgba's alpha=255 now. * [#io.quicktimecamera] [#io.quicktimeapple]: added colorspaces y, yuv, rgb, and added method "cast". * [#io.videodev] and [#camera]: removed attribute 'transfer' * fixed bug in nested-list processing (which affected [print] and [display] and use of symbols that look like floats) * [#io.videodev]: add support for libv4l1 * [#camera]: added method "api", added autodetection of camera modules * [#io.quicktimehw]: show real error messages * added class [#to~], for converting grids to signals. * [gf/canvas_...] and [gf/find_file]: add default arg * [args]: fixed crash when using comma when there is no [inlet] at all. * [#out quartz]: major speedup ! * [#store]: put_at: fixed two crashing bugs * [#in grid]: handle end-of-file and other errors properly (when reading) * quicktimeapple, quicktimecamera and gem pix : refixed colorspace on PPC * [#io.ppm]: rewritten without using libnetpbm (so that errors are handled properly); support reading P2 P3 P5 P6 and writing P5 P6 * added alias [pd/print] for pd's [print] * added alias [gf/range] for gf's [range] * [#mouse]: added method "/" to automatically scale coordinates * [#draw_rect]: fix outline mode * removed polygon_editor.pd and [#edit_polygon] * added [#out png] (in 1, 2, 3, 4 channels) * added 'cast' method to [#cast] (for changing number type) * [#for] supports floats such as [#for (f #) (f # 10) (f # 1)] * [#out sdl]: fixed mouse button support so that [#mouse] is useful * added class [gemdead], for using pix-objects without a [gemwin]. * OSX: show proper camera error messages * added [#out quartz 0]: make a borderless OSX window * OSX package: enable OpenCV support * Ubuntu package: enable libv4l1 support _ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801 _______________________________________________ Pd-announce mailing list Pd-announce(a)iem.at http://lists.puredata.info/listinfo/pd-announce

10 21

abstraction setting its own arguments
by Mathieu Bouchard 08 Aug '10

08 Aug '10

Is there any class that allows abstractions to set their own arguments ? It's important for making properties dialogues that can save args the same way that numbox (Ctrl+3) and IEMGUIs do. Well, I just made one. http://gridflow.ca/help/setargs-help.png Does it seem like it's designed the right way ? _ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801

3 26

Re: [PD] change list order according to their first element
by patko 08 Aug '10

08 Aug '10

Hello, I've been in need of such trick lately you might be interested about it. The following mail exposes a method using gridflow http://lists.puredata.info/pipermail/pd-list/2010-06/080330.html hascinna -- Patrice Colet ----- "Libero Mureddu" <libero.mureddu(a)gmail.com> a écrit : > Hello, > I'm trying to realize something like that: I have different lists > that > I have to sort in ascending order according to their first element, > but I cannot find a solution. > > In other words I'd like to have the lists > (1 a b c) (5 d e f) (3 g h i) > > ordered in this way: > (1 a b c) (3 g h i) (5 d e f) > > thanks a lot, > > Libero > > -- > Libero Mureddu > http://www.myspace.com/liberomureddu > http://www.resonatorhelsinki.com/ > > _______________________________________________ > Pd-list(a)iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list

3 3

resonator: Making resonances with Pure Data
by hghoyer 07 Aug '10

07 Aug '10

Hi, I am looking for a way to simulate resonances in a tube. So a kind of resonator, or something. Maybe someone there already a patch to generate resonances? .hg

6 6

Re: [PD] squeakyshoecore
by Kim Cascone 07 Aug '10

07 Aug '10

nice work Chris! I'd love to peek at your patches when and if you make them available :))

2 1

Re: [PD] software license for pd general patch?
by patko 06 Aug '10

06 Aug '10

----- "Mathieu Bouchard" <matju(a)artengine.ca> a écrit : > On Tue, 6 Jul 2010, João Pais wrote: > > that's the same thing. then you'll be loosing time by typing a score > > > which has always the same rhythm/tempo. better put a metro with a > mod, > > and you have it. the music for which the program is made is more > like: > > Ah yeah, that's a good example score-wise. > > But then, the problems with such scores are things like the flirting > too > close to the "uncertainty principle" (tempo is used for a time too > short > to be really felt) and the "consonance" of tempos (13:10 can be quite > hard > to distinguish from 4:3 in many circumstances, just like such ratios > of > frequencies can). But you picked extreme scores, and I can see very > well > how pieces of much lesser complexity than that can be a lot more > followable by the ear _while_ at the same time having much of a use > for a > complex programmable super-metronome. > This uncertainty principle would only apply to uncertain styles of music, main differences between rythms are about how you interpret them If the rythm is played like every step with no accent, no one would make a difference between 11:8 , 4:4, 7:16 ... that's why we use some patterns where it's easier to recognize differents ratios, and those patterns are things that defines the style of the music. If we compare both the music of Ministry and the music of a Taraf de Haïdouks we would have for the same complex bars but different kinds of musics, because they use different kinds of patterns. In fact even in a simple 4:4 bar, the need for a variable metronome is quite necessary for orchestras. Different sections don't play their parts at the same tempo, if you pay attention to it, technicaly a section would play better if the tempo is slower or higher for different parts, that's why there is conductor. pryvitannie -- Patrice Colet

3 3

Layered Signal Processing and Transport Architecture
by errordeveloper＠gmail.com 05 Aug '10

05 Aug '10

Sorry for being a little bit off-topic, but I would like here from everyone on this list as well as Miller himself, because MAX used to run on a DSP core (according to Wikipedia) This the message that i have posted to alsa-devel list yesturday: I have a proposal for this Layered Model, which would allow implementation of new audio interfaces with DSP cores, with cross-platform compatibility and audio networking in mind. it would be a sort of OSI for signal processing, but with some extra stuff to it, such as a common language (library) for hardware programming. it's not to replace ALSA, but just to bring a different approach for design engineers of professional audio applications. we all know that these days a lot manufactuares chose Linux for their Mixing Consoles (such as Midas, Lawo, Calrec and others), also other products use Linux, but there might be only a few who use ALSA (as far as i could find out there rather NONE in pro-audio Linux devices). Linux runs on devices such as Blackfin and OMAP, which have DSP cores, but the interface is device-specific, hence low-level. ALSA had been designed for conventional sound-cards (largely) also there drivers for RME, DigiGram and other pro-interfaces, but the hardware is still proprietary and it isn't quite flexible. The idea is to bring new concepts to the world, well not 100% new, but new in a way. One of these would be to implement an "open-source" audio processor interface of a kind. It would have configurable channel strips with (multi-band EQ and dynamics). Another motivating factor is upcomming completition of AVB ethernet standard from IETF/IEEE, there had been no publicaly avaliable code for this, nor i could find any discussions of how it could be implemented in Linux. However i have contact with a professor Richard Foss from Rhodes University, and there they have implemented a library and packet generator for AVB, though they haven't yet published this code. There also hasn't heppend any wide adoption of OSC, and may be OSC is not that great? I am currently working on "Control and Monitoring Protocol" which could take part in this architercture on it's TOP Layer. The fallowing are the ABSTRACTION layers that i have thought being most general: ~>> Control, Monitoring and Information (CMI) ACMP (above mentioned above, it's kind of OSC-based) or AES-x170 (both can fit together) also OSC ..or even MIDI but ACMP is more general, it should be good for lighting and other controll applications .. here is the place for GUI interfaces, hardware controllers, control surfaces ...etc ~>> Signal Processing Subsystem (SPS) ~>> Core Signal Bus (CSB) : our inter-connect it has one common clock one or more control ports and one or more signal ports (a port can be input, output, or both) the control ports are exposed to CMI layer the signal prorts can be: bridged (over Ethernet (i.e. AVB), USB or FireWire) interfaced (to say I2S, AES/EBU, AES-50 ..MADI, ADAT) or streamed to a codec or uncompressed file dumping Let's call it an Port Exposure Layer ~>> Core Signal Elements (CSE) the main abstraction for this is library (our cross-platform API) compiler (to produce platform dependent code) interpreter (to configure and glue the blocks) ~>> General Purpose Operating System Of course it is still there ..it could be on a remote machine or anything ..and it could be everywhere around, even General Purpose CPU could be a fall-back option ..well, this is all about abstraction after all :) This is with parallel audio clustering applications and distributed chain processing in mind. Looking forward to here some discussion, I would like to set up a wiki and discusion list for this! Regards, -- Ilya Dmitrichenko Илья Дмитриченко email: errordeveloper at gmail.com

2 2

[announce] Integra Live 1.0.0 (beta)
by Jamie Bullock 04 Aug '10

04 Aug '10

Dear Pd list, I am pleased to announce the first public beta release of Integra Live, a new application for the composition and performance of live electronic music. Integra Live uses Pure Data as its signal processing engine and provides a new user interface written in Adobe Flex. The software can be downloaded from the project website: http://www.integralive.org The Adobe AIR runtime is required and can be downloaded from: http://get.adobe.com/air/ Integra Live aims to provide an intuitive and humane interface to advanced signal processing and interaction capabilities. It is currently being developed by the research centres of the Integra project, and will be used by Integra commissioned composers and performers in a series of concerts across Europe in 2011. Please take time to try the software and give us your feedback via the online forum: http://integralive.uservoice.com All best wishes! Jamie -- Dr. James Bullock Senior Researcher, Interactive Technology in Music Performance Software Development Manager, Integra Project Birmingham Conservatoire Birmingham City University UK -- http://www.jamiebullock.com

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 July 2010