Pd-list September 2015

pd-list@lists.iem.at

62 participants
88 discussions

Start a nNew thread

Re: [PD] weird behavior of [vd~] in phave vocoder (overlapping subpatches)
by Christof Ressi 11 Sep '15

11 Sep '15

2 12

comport rxerrors windows 10
by rolfm＠dds.nl 11 Sep '15

11 Sep '15

on my new lenovo laptop with windows 10 trying to connect with an Arduino [comport] gives RXerror (997). with the Arduino IDE there's no problem connecting. the same patch doesn't give problems on Windows 7, XP, Mac. anyone experience with Windows 10 and [comport]? rolf

1 0

[PD-announce] Pd 0.46-7 released
by Miller Puckette 11 Sep '15

11 Sep '15

To Pd-announce: Pd version 0.46-7 is available on http://msp.ucsd.edu/software.htm or via git from sourceforge: git clone git://git.code.sf.net/p/pure-data/pure-data cd pure-data git checkout -b 0.46 This fixes a half-dozen bugs, mostly minor. cheers Miller _______________________________________________ Pd-announce mailing list Pd-announce(a)lists.iem.at http://lists.puredata.info/listinfo/pd-announce

2 1

Moving Starfield with GEM
by Pagano, Patrick 11 Sep '15

11 Sep '15

?Hey has anyone done a Star field with GEM? Do you have a patch i can look at I would prefer not to use a movie Patrick Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020

2 1

Re: [PD] Present and future of WebPd
by Robert Esler 10 Sep '15

10 Sep '15

Hi Sébastien, I’m curious, was a plugin (e.g., PPAPI) or Chrome native client ever considered? Such as how Unity encapsulates it’s projects in a NPAPI plugin. Most of these SDKs are C/C++ so it could theoretically circumvent the need for Web Audio API and also use some of Pd’s native code. Anyway, I’m quite impressed with what you’ve done with WebPd. -Rob ----------------- Robert Esler Co-Director urbanSTEW

6 14

data structure question restated as speculation
by Jonathan Wilkes 10 Sep '15

10 Sep '15

Hi list,I never got a response on my previous request for a lesson on realloc, so I'm going to rankly speculate:* people who build patches that get/set/resize ds arrays using gpointers are going to encounter (and perhaps have already encountered) rare and difficult to reproduce crashes. Why?For ds arrays, [pointer] can store a pointer to an array element. The user can retrieve the value of the array element using [get], and set it using [set]. But the user can also resize the array using [setsize], and that can move the data to a different location than what [pointer] has stored. (You can also change the ds array size with the mouse and the "Alt" key, but that's beside the point.) So what's wrong with that?When you use [setsize] to resize a ds array, Pd calls "realloc" to do the resizing. "realloc" is allowed to move the data to a new block of memory. This is more likely to happen when choosing a large size for the array, but the OS could move the data if you shrink the array, too. This is completely opaque to the user/programmer-- that is, there is no way to tell when or why realloc might relocate the data to another block. For most purposes this is no big deal because "realloc" returns a pointer to the beginning of the block which can be assigned to a variable. But recall above that we let our gpointer store a pointer to an array element which may be anywhere in the original block of memory. If realloc relocated the chunk of memory for our ds array, when we try to [get] or [set] our element, we'll be getting/setting data using a pointer that points at the _old_ memory location. In other words-- we're getting/setting values for a pointer to garbage! What about "stale pointers"?When using [setsize], the refcounts on gpointers don't change, so the relevant pointers won't be flagged as stale. But even if they were, that wouldn't do as it would be too conservative and invalidate the [setsize] object's pointer for the next size change. (E.g., if you're feeding it with a number box.) So why aren't there tons of crashes from this?OSes (well, at least Linux) apparently try extremely hard not to relocate the program's data when using realloc because it can slow things down. But "try extremely hard" != "can never happen". So what now?I don't know. Most stuff I've read would suggest storing offsets into arrays instead pointing at the elements. But... this would get extremely complex with nested ds arrays-- you'd have to create some kind offset map for navigating from the gpointer back to the data you want to get at. That seems like a lot of work, esp. for one of the most obscure parts of Pd. Are you sure this is a problem?If it isn't then there is some serious C programming voodoo going on that has zero coverage on StackExchange. But aside from Duff's Device I've seen about every kind of C voodoo in Pd so I honestly have no idea. -Jonathan

2 2

raspberry pi gpio analog/pwm
by Peter P. 10 Sep '15

10 Sep '15

Dear list, I am enjoying Miller's gpio external on a raspberry pi 2 Model B V.1.1 The help-patch kindly provided by J Oliver in his posting http://lists.puredata.info/pipermail/pd-list/2013-04/102172.html has a number box connected to gpio's inlet. Is it possible to output analogue values or PWM (on GPIO18) that way? thanks, P

1 0

Gem A/V sync?
by kubriel 09 Sep '15

09 Sep '15

i know there was something written around, and i did it few times, usually with oggread~ because it outputs time information i used to sync video. but now i have to play 6 channel audio with synchronized video. (oggplay~ has only two audio outlets) something like [readsf~ 6] will be wonderfull, if it outputs time information. i can put all audio in the tables, but it is 15minutes long, and i heard it is problem to adress precisely so long arrays with phasor audio signal. [tabplay~] also no time info. i need perfect sound quality, it goes to EBU satellite in Geneva, and some radios live also to quadro speakers in saal. only solution what i have in mind to play 6track sound with mplayer, and parse timecode from commandline, but it seems clunky to me. some ideas? thanks! kubriel -- http://kubriel.servus.at

2 1

Re: [PD] locality with new [field] object (Jonathan Wilkes)
by jamal crawford 09 Sep '15

09 Sep '15

hey list, Jonathan. > You start with a struct:[struct foo float x float y canvas a b] Then > create a scalar from this struct. The scalar will have an "x" value, a > "y" value, and a canvas "a" which gets filled with the contents of an > abstraction "b.pd" that is somewhere in Pd's search path. Now here's > the neat thing-- inside the newly instantiated "b.pd" you can do this: > [loadbang]|[field x]|[print x] > > imagine you have a drawing instruction like this:[draw rect 0 0 20 20] When you create the scalar you get a little black box on a canvas. With a canvas field like I described, you can right-click the scalar and choose "Open" to show a canvas window. while trying to create [struct foo float x float y canvas a b], i get: canvas: no such type, using pd 0.46.6 what am I missing? ~/.jc

2 7

gem advanced video keying
by hi 09 Sep '15

09 Sep '15

Dear Pd folk, I am investigating options to improve chroma keying within pd and gem to use within a theater installation. I need more advanced keying features than seemingly possible with [pix_choma_key], like border corrections and smoother edge transparencies. The best thing i found so far is this: http://forum.pdpatchrepo.info/topic/2953/neat-chroma-keying/3 very nice, but i would need more a quality like in readymade video mixers Did any of you program anything like that? Also i'm trying to find out, whether a potential setup with a computer with 4 HD-SDI inputs would be capable of keying 2 HD-live-signals at the same time and overlay that over one HD-live-background. Are there any experiences (hardware and software) from your side, you could share? I would so much love to make this happen with pd and not with an expensive video mixer i would have to buy. Any help or ideas are appreciated. Love to pd, jonny

2 5

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 September 2015