Pd-list December 2016

pd-list@lists.iem.at

45 participants
53 discussions

problem compiling externals under Windows 10
by oscar pablo di liscia 03 Dec '16

03 Dec '16

Hi. I'm trying to compile an external for Pure Data under Windows 10 using CygWin and I got the following output: /usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: i386 architecture of input file `../lib/pd.dll' is incompatible with i386:x86-64 output I obtained pd.dll from the last Vanilla package for Windows here: http://puredata.info/downloads/pure-data I compiled the external under Windows 7 using Cygwin with no problem using exactly the same files and Makefile. Any help? Oscar Pablo Di Liscia

2 2

Re: [PD] Pd-0.47.1 on macOS 10.11.6 hangs after quitting
by jlistshit 03 Dec '16

03 Dec '16

I had the same problem on OSX 10.9.5 nut just with 47-1 also with the prior version of PD. I actually could not quit the application other than by force. If you go to your audio preferences and switch off/untick “Use callbacks” the problem might disappear, it did so here, although i don’t know exactly why. Besides that, are your Input Devices never storing their state, when you Save All Settings in audio prefs? I was wondering if the two phenomena might be releated… Hope it helps, maybe someone with more insight into the intestines can shed brighter light here. jayrope - - - www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope On 03 Dec 2016, at 12:00, pd-list-request(a)lists.iem.at wrote: > Re: Pd-0.47.1 on macOS 10.11.6 hangs after quitting

2 1

Re: [PD] Pd-0.47.1 on macOS 10.11.6 hangs after quitting
by jlistshit 03 Dec '16

03 Dec '16

1 0

Pd-0.47.1 on macOS 10.11.6 hangs after quitting
by Roman Haefeli 03 Dec '16

03 Dec '16

Hey all My colleague installed Pd-0.47.1 on his MacBook (10.11.6) and it hangs after quitting. The problem only occurs when DSP is turned on or has been turned on in the past. When DSP never has been turned on since launch of Pd, Pd quits without issues. When Pd is forcefully quit through apple menu, a 'pd' process still remains running while using 100% of a core. The only way to stop that is with a terminal command ('killall pd'). The problem is independent from chosen audio backend, it happens with 'jack', 'built-in' and other back-ends. It would already be helpful to know whether that problem is specific to his system or if it is a general problem with Pd on 10.11. How would someone proceed to track down such an issue? Thanks, Roman

3 2

[import] in Pd Vanilla
by Jeppi Jeppi 02 Dec '16

02 Dec '16

Hi all, I see the [import] object is not included in vanilla Pd-0.47, how are you supposed to load the required externals from within a patch? Thanks josep m

5 4

issues with loading FFTease and lyonpotpourri & upload this to deken please
by Alexandre Torres Porres 02 Dec '16

02 Dec '16

Hi Eric, I'll open this thread here on the pd list too so I can request that fftease/potpurri on your git https://github.com/ericlyon stuff be on deken, in the pdcon talk you didnt seem to know the procedure, maybe other people in the list can help you. Fred Jan started this link on the Pd site, maybe it helps http://puredata.info/docs/Deken . If you cant do it for some reason, would be ok for someone else to do it? But I assume you have to involved somehow. I'll also report that lyonpotpourri3.0-64bit didnt work for my 0.47-1 vanilla 64 bits in mac os 10.12.1 and that I couldn't get fftease (only 32 biuts available) in the 32 bit vanilla version (or extended) cheers

2 2

bang issue
by Alexandre Torres Porres 02 Dec '16

02 Dec '16

so, everytime I create a bang~ and conect it somewhere, it won't work right away, I have to reinstantiate the object - it also starts working if i just save the patch! Anybody ele? cheers ps. I'm on mac os 10.12.1 using vanilla 64 bits

2 2

Re: [PD] Pd-0.47.1 on macOS 10.11.6 hangs after quitting
by Dan Wilcox 01 Dec '16

01 Dec '16

Did Pd save it’s window state in the old version? IE. starting Pd automatically starts windows that were open when it was last closed? It might be an old state that gets loaded by the OS and this can cause weird issues like this some times. This should be fixed in 0.47 as I added clearing & locking the state as well as telling the OS not to save state automatically … or at least I think that work in the in the master branch but it could be in one of my side branches. -------- Dan Wilcox @danomatika <https://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/> > On Dec 1, 2016, at 9:21 PM, pd-list-request(a)lists.iem.at wrote: > > From: Roman Haefeli <reduzent(a)gmail.com <mailto:reduzent@gmail.com>> > Subject: [PD] Pd-0.47.1 on macOS 10.11.6 hangs after quitting > Date: December 1, 2016 at 6:04:02 PM GMT+1 > To: pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at> > > > Hey all > > My colleague installed Pd-0.47.1 on his MacBook (10.11.6) and it hangs > after quitting. The problem only occurs when DSP is turned on or has > been turned on in the past. When DSP never has been turned on since > launch of Pd, Pd quits without issues. > > When Pd is forcefully quit through apple menu, a 'pd' process still > remains running while using 100% of a core. The only way to stop that > is with a terminal command ('killall pd'). > > The problem is independent from chosen audio backend, it happens with > 'jack', 'built-in' and other back-ends. > > It would already be helpful to know whether that problem is specific to > his system or if it is a general problem with Pd on 10.11. > > How would someone proceed to track down such an issue? > > Thanks, > Roman

1 0

Control external command from Pd
by Roman Haefeli 01 Dec '16

01 Dec '16

Hey all I would like to use Pd to start and stop several instances of a certain command. I need to catch the stdout of the commands in Pd, so I can monitor their status. Also, I want to be able to kill them individually. I tried to achieve that with [ggee/shell], but there are some culprits. When I launch the command directly in [shell] like this: [command ( | [shell] I get the command's stdout on the left outlet of [shell], but I don't know of a reliable way to send a SIGHUP signal to command. On the other, I can launch a wrapper script that sends command to the background and returns its PID: #!/bin/sh command & echo $! and in Pd, I do: [./wrapper.sh ( | [shell] and the left outlet of [shell] gives me the PID of the command which allows me to reliably kill that instance later. However, this way [shell] doesn't output the command's stdout. Is there a way to have my cake and eat it, too? Roman

3 8

matching queries with text in [text search]
by Liam Goodacre 01 Dec '16

01 Dec '16

When [text search] searches through a text file, it seems to evaluate the query against a line of text term by term. If one of the query terms is found to mismatch the corresponding term in the text line, it comes out as negative. I am looking for a search algorithm that does the opposite. I want it to match the searchable text against the query term by term, and reject it the moment it finds a mismatch. This would mean that extra terms in the query are allowed to pass, while queries that are shorter than the text are rejected, even if they match. This should be clearer with examples: -- Searching "cats 1 2 3" into "cats" returns negative. I want it to return positive. --Searching "dogs" into "dogs a b c" returns positive. I want it to return negative. At first glance, it seems like you can achieve this using [text search]'s numbered arguments. For example, [text search my-text 0] will return positive for the "cats" example, because it is only searching the first term. But I don't think that this can lead to a general solution, as the number of searchable terms is very inflexible. For instance, if the same text file contained the line "giraffe 86", then I would want the query "giraffe" to come up negative, because "giraffe 86" has not been met. But if you're using the 0 argument, it will come up positive, because it's only searching the first term. I've made an abstraction that solves this problem by dividing the text file according to line length, and then making multiple passes with the query. It works well enough, but I'm wondering if there's a more efficient way. In the context I need it, it will be used fast and frequently, so I want to make sure that it works as quickly as possible. I'm attaching the abstraction, for anyone who wants to take a look. Can you think of a better way of making this search, perhaps using the numbered arguments after all, or using lists instead of [text]? I assume that lists will be much slower, but perhaps there's a way. If what I've written here is unclear, please take a look at the examples in the attachment--they should straighten things up.

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 December 2016