Pd-dev December 2012

pd-dev@lists.iem.at

14 participants
173 discussions

[ pure-data-Patches-3598097 ] add setup() function to hexname objs to guarantee loading
by SourceForge.net 23 Dec '12

23 Dec '12

Patches item #3598097, was opened at 2012-12-21 14:24 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598097&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: externals Group: bugfix Status: Open Resolution: None Priority: 5 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: IOhannes m zmölnig (zmoelnig) Summary: add setup() function to hexname objs to guarantee loading Initial Comment: When objects like ||~, &&~, etc are installed with a symlink to the 0x file name, they don't load because they can't find the setup function. They are looking for setup_0x7c0x7c_tilde(). Now that loading from setup() is included in Pd-vanilla 0.44 and Pd-extended 0.43.4, this patch adds setup() aliases to ensure that these objects load no matter what the filename is. ---------------------------------------------------------------------- >Comment By: Hans-Christoph Steiner (eighthave) Date: 2012-12-23 10:27 Message: I added #ifndef ZEXY_LIBRARY and it built and linked a zexy.pd_linux. Hope I did it right, the updated patch is attached. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2012-12-23 08:48 Message: this will never link when zexy is compiled as a a multi-object library. when providing patches, please check whether they work with the _recommended_ way of using zexy. (e.g. at least use #ifdef ZEXY_LIBRARY to protect multiple definitions of the same functions) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598097&group_…

1 0

[ pure-data-Patches-3598097 ] add setup() function to hexname objs to guarantee loading
by SourceForge.net 23 Dec '12

23 Dec '12

Patches item #3598097, was opened at 2012-12-21 14:24 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598097&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: externals Group: bugfix Status: Open Resolution: None Priority: 5 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: IOhannes m zmölnig (zmoelnig) Summary: add setup() function to hexname objs to guarantee loading Initial Comment: When objects like ||~, &&~, etc are installed with a symlink to the 0x file name, they don't load because they can't find the setup function. They are looking for setup_0x7c0x7c_tilde(). Now that loading from setup() is included in Pd-vanilla 0.44 and Pd-extended 0.43.4, this patch adds setup() aliases to ensure that these objects load no matter what the filename is. ---------------------------------------------------------------------- >Comment By: IOhannes m zmölnig (zmoelnig) Date: 2012-12-23 08:48 Message: this will never link when zexy is compiled as a a multi-object library. when providing patches, please check whether they work with the _recommended_ way of using zexy. (e.g. at least use #ifdef ZEXY_LIBRARY to protect multiple definitions of the same functions) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598097&group_…

1 0

[ pure-data-Patches-3598097 ] add setup() function to hexname objs to guarantee loading
by SourceForge.net 23 Dec '12

23 Dec '12

Patches item #3598097, was opened at 2012-12-21 14:24 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598097&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: externals Group: bugfix Status: Open Resolution: None Priority: 5 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: IOhannes m zmölnig (zmoelnig) Summary: add setup() function to hexname objs to guarantee loading Initial Comment: When objects like ||~, &&~, etc are installed with a symlink to the 0x file name, they don't load because they can't find the setup function. They are looking for setup_0x7c0x7c_tilde(). Now that loading from setup() is included in Pd-vanilla 0.44 and Pd-extended 0.43.4, this patch adds setup() aliases to ensure that these objects load no matter what the filename is. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2012-12-23 08:21 Message: make all of them red by having a yellow moose!! [url=http://www.burberryuksale.org/category/bags-burberrry]burberry handbag[/url] <a href="http://www.burberryuksale.org/category/bags-burberrry" title="burberry handbag">burberry handbag</a> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598097&group_…

1 0

Re: [PD-dev] updates to search_plugin for translation support
by Hans-Christoph Steiner 23 Dec '12

23 Dec '12

On Dec 22, 2012, at 9:34 PM, Jonathan Wilkes wrote: > ----- Original Message ----- >> From: Hans-Christoph Steiner <hans(a)at.or.at> >> To: Jonathan Wilkes <jancsika(a)yahoo.com> >> Cc: pd-dev List <pd-dev(a)iem.at> >> Sent: Saturday, December 22, 2012 8:00 PM >> Subject: Re: [PD-dev] updates to search_plugin for translation support >> >> >> On Dec 22, 2012, at 7:47 PM, Jonathan Wilkes wrote: >> >>> ----- Original Message ----- >>>> From: Hans-Christoph Steiner <hans(a)at.or.at> >>>> To: pd-dev List <pd-dev(a)iem.at> >>>> Cc: >>>> Sent: Friday, December 21, 2012 10:30 PM >>>> Subject: [PD-dev] updates to search_plugin for translation support >>>> >>>> >>>> Hey Jonathan, >>>> >>>> I just committed my updates to your search_plugin, here's what I >> did: >>>> >>>> * renamed Browser2.0 to Search >>>> >>>> * renamed "Keyword Search" title to "Search by >> Tag". The >>>> "keyword" part didn't seem to make sense once doing the >>>> translation, since the keywords won't be translated, or they >> won't >>>> work. So it seem to me they are really more "tags" than >>>> keywords". >>> >>> That will cause confusion. >>> >>> The pd META subpatch consists of various comments with the form >>> "TAG value1 value2 etc.". One of those tags happens to be >>> "KEYWORDS". All the blue links listed under the heading >> "Keyword Search" >>> are possible values that I've used after the tag "KEYWORDS" >> in help patches. >>> Therefore, it is a "Keyword Search"-- a search for values from a >> specific type of >>> tag named "KEYWORDS"-- and not a "Search by Tag", which >> implies values >>> matched from various tags like KEYWORDS, DESCRIPTION, OUTLET_1, etc. >>> >>> The fact that you can't translate the keywords is simply a limitation >> of pd's >>> implementation which has no way to sensibly translate content inside >> patches. >>> (At least none that I know of.) >> >> >> I think that the PDDP KEYWORDS are really functionally like tags in the >> blog/etc. sense, like in this sense: >> http://en.wikipedia.org/wiki/Tag_(metadata) I can't think of a common usage >> for the term 'keyword' for describing this, though its a synonym. So I >> wanted try to use the most common language possible. > > As far as pd META, I'm pretty sure "KEYWORDS" was there in a template > already. If you want to use common language go ahead and > write a script to replace "KEYWORDS" inside any [pd META] for the entire > svn, plus change the relevant part of the gui-plugin. I don't think they're used > anywhere else ATM. Its tempting to rename KEYWORDS to TAGS... but with such a big change, I'd want to be extra sure. We might just have to live with it. >> But yes, I agree, calling it "tags" one place and "keywords" >> another will cause confusion. The term "KEYWORDS" isn't wrong, >> just much less common. Maybe it could incorporate both terms: >> >> "Search by Keyword Tag" > > See my commit. seems ok, I'm happy to leave it at that. One thing I'm struggling with in my mind is the keywords/tags are in English. So if they are translated in the listing in the front page, there will be confusion when someone tries to type in the keyword in their native language to search by, it won't work. .hc

2 1

updates to search_plugin for translation support
by Hans-Christoph Steiner 23 Dec '12

23 Dec '12

Hey Jonathan, I just committed my updates to your search_plugin, here's what I did: * renamed Browser2.0 to Search * renamed "Keyword Search" title to "Search by Tag". The "keyword" part didn't seem to make sense once doing the translation, since the keywords won't be translated, or they won't work. So it seem to me they are really more "tags" than keywords". * rearranged some code to get [_ ""] everywhere, some lists needed more than trivial rearrangedments (i.e. [list foo bar] instead of {foo bar}) Hope these all work for you. .hc

2 2

[ pure-data-Bugs-3598176 ] pd~ doesn't really work in MAX
by SourceForge.net 22 Dec '12

22 Dec '12

Bugs item #3598176, was opened at 2012-12-22 11:03 Message generated for change (Tracker Item Submitted) made by porres You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3598176&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: externals Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Alexandre Porres (porres) Assigned to: Nobody/Anonymous (nobody) Summary: pd~ doesn't really work in MAX Initial Comment: Hi there, I don't knwo anyone who successfully used the pd~ external inside MAX/MSP so I just guess it's buggy and not working. Maybe some compability issue on MAX 6 is to blame, I don't know, but I think this feature is very cool, although I don't have MAX... but I'd like to play with that feature when it works fine. Thanks Alex ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3598176&group_…

1 0

no sound from bsaylor/svf~ and cyclone/svf~
by katja 22 Dec '12

22 Dec '12

So I was going to replace type punning flush-to-zero in bsaylor/svf~ with something else, but first wanted to check how it behaves in Pd-E 0.42 and in latest 0.43 autobuild. As it happens, it gives no output sound at all in latest autobuild. It's compiled with fno-strict-aliasing. By coincidence it occurred to me to check cyclone /svf~. No sound either! In dutch we say 'alsof de duvel ermee speelt'. The issues may be unrelated. cyclone/svf~ has four inlets and one outlet now, while it used to have three inlets and four outlets. This is with Pd-0.43.4-extended-20121221.app for OSX 10.5 i386 (but very unlikely that cyclone/svf~ has different number of outlets on other platforms). Weather forecasts are unfavorable for this weekend and I may spend some time on these issues. Katja

2 6

[ pure-data-Patches-3598153 ] fix type punning issue in bsaylor/svf~
by SourceForge.net 22 Dec '12

22 Dec '12

Patches item #3598153, was opened at 2012-12-22 05:59 Message generated for change (Settings changed) made by katjav You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598153&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: externals Group: bugfix Status: Open Resolution: None Priority: 5 Private: No Submitted By: Katja (katjav) Assigned to: Nobody/Anonymous (nobody) >Summary: fix type punning issue in bsaylor/svf~ Initial Comment: bsaylor/svf~.c uses a type punning method to avoid / eliminate subnormal numbers. When compiled with -ftree-vectorize, the object doesn't give signal output. Compiler warnings: svf~.c: In function 'run_svf': svf~.c:60: warning: dereferencing type-punned pointer will break strict-aliasing rules svf~.c:61: warning: dereferencing type-punned pointer will break strict-aliasing rules ... cc1: warning: -ftree-vectorize enables strict aliasing. -fno-strict-aliasing is ignored when Auto Vectorization is used. File bsaylor_svf~-type-punning-fix.patch fixes the issue by using PD_BIGORSMALL() function instead. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598153&group_…

1 0

[ pure-data-Patches-3598153 ] type punning issue in bsaylor/svf~
by SourceForge.net 22 Dec '12

22 Dec '12

Patches item #3598153, was opened at 2012-12-22 05:59 Message generated for change (Tracker Item Submitted) made by katjav You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598153&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: externals Group: bugfix Status: Open Resolution: None Priority: 5 Private: No Submitted By: Katja (katjav) Assigned to: Nobody/Anonymous (nobody) Summary: type punning issue in bsaylor/svf~ Initial Comment: bsaylor/svf~.c uses a type punning method to avoid / eliminate subnormal numbers. When compiled with -ftree-vectorize, the object doesn't give signal output. Compiler warnings: svf~.c: In function 'run_svf': svf~.c:60: warning: dereferencing type-punned pointer will break strict-aliasing rules svf~.c:61: warning: dereferencing type-punned pointer will break strict-aliasing rules ... cc1: warning: -ftree-vectorize enables strict aliasing. -fno-strict-aliasing is ignored when Auto Vectorization is used. File bsaylor_svf~-type-punning-fix.patch fixes the issue by using PD_BIGORSMALL() function instead. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3598153&group_…

1 0

Re: [PD-dev] [ pure-data-Patches-3597233 ] Win32: use binary open mode by default everywhere
by Claude Heiland-Allen 22 Dec '12

22 Dec '12

On 21/12/12 22:27, SourceForge.net wrote: > Patches item #3597233, was opened at 2012-12-18 08:43 > Message generated for change (Comment added) made by eighthave > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3597233&group_… > > Summary: Win32: use binary open mode by default everywhere > > Initial Comment: > This patch enables binary open mode on Win32 everywhere, thereby ignoring the special Win32 "text" translation mode. This makes the Win32 API more like the POSIX API, which is used by every other platform Pd supports. > > But it seems to break somethings, like the loading of some soundfiles. Attached is an example patch for the failure. Guessing here: a file saved wrongly in text mode (by old Pd, perhaps) might be corrupted in a way that text mode old Pd can read fine, but makes binary mode software (like new Pd, perhaps) fails. (sorry for not checking the example patch or using sf.net tracker) Claude -- http://mathr.co.uk

2 1

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

Pd-dev December 2012