Pd-list June 2015

pd-list@lists.iem.at

75 participants
97 discussions

bsaylor pvoc~.c for 64 bits?
by geekshabeka＠riseup.net 05 Jun '15

05 Jun '15

Hello people! Anyone know any 64 bits version for bsaylor pvoc~.c or some fix for this error?: An operation on the array 'sample' in the patch 'pvoc~-help.pd' failed since it uses garray_getfloatarray while running 64-bit! Cheers bk

2 1

Gestural Interaction and Music PhD Studentship
by András Murányi 05 Jun '15

05 Jun '15

An opportunity for a fully-funded PhD studentship on Gestural Interaction and Music is currently being offered by the Department of Computer Science and Creative Technologies at UWE Bristol. http://www1.uwe.ac.uk/research/postgraduateresearchstudy/studentshipopportu… Andras

1 0

LAUNCHPAD S in Pd
by fz＠mur.at 05 Jun '15

05 Jun '15

Hi, I try to embed the Novation LAUNCHPAD S in Pd for a performance. So it would be great to access LED colors, buttons, etc. easily. I found this new library lp_util from Dan Prince: http://www.danpprince.com/engineering/lp_util/ This really looks interesting. The only problem for me is, that I can´t get it working. I am on Win8 and I use Pd-extended 43.4 - I put the lp_util folder in my C:\Program Files (x86)\Common Files\Pd and Pd seems to find it. - In Pd I declared the launchpad as Midi In and Midi Out device. If I run the patch lp_util_module_test nothing happens. So could anybody give me a hint, how to get it working? thanks! fränk ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 2

specify MIDI device with a loadbang?
by Oliver Larkin 03 Jun '15

03 Jun '15

Hi, is there a way that i can make a patch automatically choose a MIDI input device in vanilla? PD keeps loosing the chosen device if pd is launched with out that device connected. thanks oli

2 2

Fwd: Patch acting weird with Pd 0.46.6
by Pierre Massat 03 Jun '15

03 Jun '15

Hi IOhannes, Thanks for your reply. I don't understand your answer... I mean I do know that one has to use triggers to connect to multiple inlets, but I don't see where I did something wrong in my patch. Do you mean that the prints attached to two outlets should be attached to triggers ? Even then I don't understand how this could cause the entire sequence of counter values to be upside down. Have your tried it, first manually, then with the [sel 0] attached to the counter ? Do you get the same behaviour as what I described ? Cheers, Pierre. 2015-06-03 9:30 GMT+02:00 IOhannes m zmoelnig <zmoelnig(a)iem.at>: > On 2015-06-02 23:10, Pierre Massat wrote: > > > > I am probably very tired and I must be missing something obvious. But > right > > now this looks like aliens have hacked into Pd and are playing with my > > nerves. > > afaict¹, you are violating the first rule of patching: > > *never* do a fan-out without a trigger. > *always* use a trigger if you want to connect a single outlet with > multiple inlets. *always*. > > fgmasdr > IOhannes > > ¹ i was pretty sure that this would be the answer before i looked at > your patch; it usually is; but this also means that i'm very biased and > might have missed something else. > > > _______________________________________________ > Pd-list(a)lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > >

2 3

Sensing if an object is selected
by Liam Goodacre 01 Jun '15

01 Jun '15

I am looking for a way to sense if a particular subpatch object has been selected in the parent window (selected as in highlighted in blue on the screen). [iemguts/canvasselect] almost does it for me, but not quite. This object will give a list of all objects that are selected, but I am looking for something that lets out a bang or a 1 when its containing subpatch is selected and a 0 when it is deselected. Does anyone know if this is possible? Before anyone suggests it, a bang hidden under a canvas to sense the mouse click won’t do in this case. Also ineffective would be a hacked up combination of [canvasselect] and [canvasindex]. This might work, except that it would take a [metro] object to power it, and overuse of [metro] is precisely the problem that I am trying to solve.

1 0

libpd crashes with vlines~ in (libpd) clock_unset (?)
by Pascal 01 Jun '15

01 Jun '15

I have a iOS project developed with XCode that uses libpd to load a Pure Data patch. My project uses a mix of [osc~] and [phasor~] with modulated parameters (pitch, volume, etc). My app is in 64-bit as now required. I am using the latest version of Pure Data and libpd. The Pure Data patch runs fine in Pure Data but it crashes in XCode. I have an [osc~] that has its pitch modulated by an envelope. When I change the value of the length of the envelope (= modulation rate) on a device, it randomly crashes during testing but always on the same line of libpd code. I thought it had to do with how fast the parameter was changed but no, it also happens when the parameter is slowly changed. Here is below a (reduced) patch where the problem occurs. I have recently catched up with Pure Data. Any suggestions or corrections are welcome. modulatedOscillator.pd (http://forum.pdpatchrepo.info/uploads/files/upload-9c1506d8-30a2-4af3-8927-… <http://forum.pdpatchrepo.info/uploads/files/upload-9c1506d8-30a2-4af3-8927-…>) Here is a screenshot of the crash in XCode with the code sequence and the line of clock_unset that crashes. https://cloud.githubusercontent.com/assets/10989820/7903859/79938d6a-07e9-1… I have done some printing and it crashes in this function: void clock_unset(t_clock *x){ if (x->c_settime >= 0){ if (x == clock_setlist) clock_setlist = x->c_next; else{ t_clock *x2 = clock_setlist; while (x2->c_next != x) x2 = x2->c_next; x2->c_next = x->c_next; } x->c_settime = -1; } } On this line : while (x2->c_next != x) x2 = x2->c_next; With a printed value of : x2->c_next==NULL Someone replied to me about the issue on Stack Overflow: "it seems that the clock that is being unset is not found in the list of currently maintained clocks. however, this is probably one of the most often used functions in Pd and afaict you only use bog standard built-in objects, which should make the patch pretty failsafe. i'm guessing that your problem is related to the new multi-instance features of Pd and you simply hit a bug." Could it be a bug? Thanks in advance.

1 0

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 2015