Pd-list December 2019

pd-list@lists.iem.at

34 participants
39 discussions

use case of 'isvisible' in [pdcontrol]?
by Alexandre Torres Porres 05 Dec '19

05 Dec '19

Hi, I'm curious about the use cases of the 'isvisible' message in [pdcontrol], and I also wonder how useful is it to query for the visibility state instead of just getting it when it changes. cheers

2 3

[PD-announce] Else 1.0 beta 26 and live electronics tutorial update
by Alexandre Torres Porres 05 Dec '19

05 Dec '19

ELSE 1.0 beta 26 is out! Highlight is a massive update to the [slider2d] abstraction, which now relies on updates I made to the [canvas.mouse] object and a new [savechange] object. Sadly, compatibility has been broken here. There's also a new variant object, a two dimensional circular slider called [circle] - for more details, check: https://github.com/porres/pd-else/releases/tag/v1.0-beta26 (some binaries are already available via Pd). Now for a heads up, Pd 0.51 is coming out and the next update to the ELSE library is gonna break compatibility of dozens objects! This is because [inlet~] will now allow us to send messages in the main left inlet. This also will fix some issues in objects like [else/bl.square~]. Anyway, hopefully this upcoming massive overhaul will also get me very close to a new "release candidate" phase. My tutorial has also been updated to be compatible to ELSE beta 26, see: https://github.com/porres/Live-Electronic-Music-Tutorial/releases/tag/v1.0-… Examples affected by the new [circle] object are: https://github.com/porres/Live-Electronic-Music-Tutorial/blob/master/Exampl… and https://github.com/porres/Live-Electronic-Music-Tutorial/blob/master/Exampl… _______________________________________________ Pd-announce mailing list Pd-announce(a)lists.iem.at https://lists.puredata.info/listinfo/pd-announce

1 0

Error running timbreID external on MacOS 10.14.6
by Justin Martin 04 Dec '19

04 Dec '19

When I try to create a timbre object (in this case [mean]) I get the following error: .. couldn't create /Applications/Pd-0.50-0.app/Contents/Resources/Scripts/../extra/tID/mean.pd_darwin: dlopen(/Applications/Pd-0.50-0.app/Contents/Resources/Scripts/../extra/tID/mean.pd_darwin, 10): no suitable image found. Did find: /Applications/Pd-0.50-0.app/Contents/Resources/Scripts/../extra/tID/mean.pd_darwin: no matching architecture in universal wrapper /Applications/Pd-0.50-0.app/Contents/Resources/extra/tID/mean.pd_darwin: no matching architecture in universal wrapper Does anyone know what the problem is? Thanks! Justin

7 10

Re: [PD] pd for oscilloscopes again
by Dan Wilcox 04 Dec '19

04 Dec '19

This should read: "Pd Documents directory." If you didn't create it when first starting Pd, go to Pd->Preferences->Path to (re)set it. You can also disable it completely if you choose to handle everything manually. It's only a helper. > On Dec 4, 2019, at 12:32 PM, pd-list-request(a)lists.iem.at wrote: > > Wither newer versions of Pd, you can create a "Pd Documents doctors" -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

Re: [PD] pd for oscilloscopes again
by Dan Wilcox 04 Dec '19

04 Dec '19

To start: Welcome back to using Pure Data. We as a community can help you make a transition if you are willing to work with our (still) ongoing transition from Pd-extended. > On Dec 4, 2019, at 9:54 AM, pd-list-request(a)lists.iem.at wrote: > > I was getting ahead of myself. Plus, my expectations were w-a-y too > high. They are not. > I expected to be able to install the whole thing, a current and > desirable version of pure data with everything I'd need. In general, you can, using deken, as most major libraries that used to be distributed with extended have new maintainers who continue development. As the last version of Pd-extended has libraries built for 32 and 64 bit on macOS and those (now old) versions were uploaded to deken, you can at the very least get those older versions. Admittedly, we probably need a more accessible overview of how to use it as well as a transition guide from Pd-extended and I think *this* is the crux of your issues. One of these is probably related to the difficultly of figuring out *which objects* belong to *which libraries* in patches made in extended. I feel your pain there as I had to go through this while migrating my own projects. > Now that I know that is not, and will never be the case, I'll be pleased > to sift thru those links from 2011 to find the good stuff. I would say this is not true and you seem to conflate your frustration with a *delibrate* attempt to make your life harder. Some backstory: Pd-extended was a successful community-driven "batteries included" version of Pure Data "vanilla" which was bundled with a large number of community-contributed libraries. That was a great thing. On the other hand, Pd-extended was heavily dependent upon the work of 1-2 people who's free time went into trying to maintain and manually merge changes from vanilla Pd. That was a bad thing and when those people had larger life issues to deal with, they could no longer maintain development. This was around 2011-2012. We as a community then asked: Who can take up work on Pd-extended? No one answered. There was a great amount of wailing and gnashing of teeth, but no one answered. In the meantime, some community members developed a simple proof-of-concept package manager for external libraries, either pre-compiled or abstraction-only. The idea behind this was to modularize external development and take away the need for a large, central development version like Pd-extended and it's maintenance overhead. This also allowed the community to focus on bringing improvements to Pd "vanilla" directly. This package manager was informally named "deken" aka Help->Find externals. Since then, we as a community have been figuring out how to handle this whole transition, from increasing community-contributed development to the Pd "vanilla" source code, to collaborative external library development and distribution. The basic idea revolves around: Pd itself comes with the core objects and "core externals" ie. [bonk~], [sigmund~], [bob~], etc. Anything else should be installed either via deken or manually to a folder. You then need to either add that folder to your general Pd path or, better yet, tell Pd about the path or name of the library using the [declare] object. After that, Pd will try to find and load it. Wither newer versions of Pd, you can create a "Pd Documents doctors" in your home documents folder which also creates a default "externals" subdirectory which is where deken will install external libraries by default and this directory is already added to your search path. This allows a simple process for most libraries: find externals, click to download, open patch, create [declare -path some lib], create object from somelib. There are currently caveats for some libs (Gem for instance), but that;'s the basic idea. One pain point is that Pd-extended did all of this automatically, however this made it hard to tell where objects came from and also lead to name clashes where the object from one library shadows that of another. With this new approach, you need to be more explicit as to which libraries you want to use, much akin to a Python import command or include in other languages. The downside, naturally, is that you need to be congnizant of which libraries you were using previously. When I was porting my old projects from Pd-extended, I basically opened the patch and made a list of objects that could not be created. Next, I did a search in the extra folder to find the helpfuls for these objects. Since the helpful would within the library subfolder, I could find the name of the library. After that, you should be able to install the library via deken, then add a [declare] to your main or abstraction patches which need to load the library. Some libraries need only to declare the path while others also need a "-lib" flag if they are pre-compiled in specific way. This is definitely confusing right now and we are working on some ways to make it work more smoothly. > I'm surprised no one has assembled a package of all the things you'd > need, libraries, GEM, everything in one single .zip file. I'd argue we do have that, although it's decentralized as outlined previously. > And instrux on what to do. Exactly. We clearly need improvement here. > The user base is very broad, with thousands of people approaching it for > different reasons, and my tiny niche application is tough to track down. It's not a niche problem, we have been dealing with it for a few years now and it could be communicated better. > Or I haven't dived deep enough to find it. No, you probably have, otherwise you would have found it. This is a very important point to make and clearly needs work. -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

data structures for display only, not interaction
by Alexandre Torres Porres 03 Dec '19

03 Dec '19

so, I have a data structure based GUI object, and say I just want it to display things and not really interact with it by clicking the data structures around, is it possible? Sorry if this is a stupid question, I just want to be sure. So, say I have some shapes (for instance, a polygon) that can be controlled by messages and change something like its size. Now, because of that, if I go over the graph on parent and click on the corner of the polygon, I can drag and change the shape. Now, what if I want to prevent that from happening? Hints for tricks and hacks? What I'm doing so far is I'm getting the values of these parameters with [get] and reset the value if they change with [set]. it seems to be doing the trick, but maybe there are other ways of doing this? And maybe, just maybe, perhaps we could include an option, a flag, that an object is only for display? hmm? what you think? cheers

4 4

Somewhat nice circles using data structures with anti-aliasing implementing Xiaolin Wu circle algorithm (vanilla)
by Ingo Stock 02 Dec '19

02 Dec '19

Hey list, i implemented the Xiaolin Wu circle algorithm to get somewhat nice circles with data structures in Pd vanilla. Patch and description are in the forum: https://forum.pdpatchrepo.info/topic/12360/somewhat-nice-circles-using-data… Have fun! :) ingo This was first posted to Pd-dev by mistake, sorry for the double post!

3 6

checking [readsf~]'s current position in wav-file
by Jakob Laue 02 Dec '19

02 Dec '19

6 6

[PD-announce] audiolab v-0.2 is on deken!
by Philipp Schmalfuß 01 Dec '19

01 Dec '19

updated my "audiolab" abstraction library there are two more objects, "pp.twisted-delays2~" and "pp.spacer~" sorry for the stupid names. all best, Philipp _______________________________________________ Pd-announce mailing list Pd-announce(a)lists.iem.at https://lists.puredata.info/listinfo/pd-announce

3 3

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 2019