Pd-dev December 2015

pd-dev@lists.iem.at

14 participants
16 discussions

Re: [PD-dev] Pd-extended EOL?
by Dan Wilcox 11 Jan '16

11 Jan '16

Yeah, that’s what I mean. Basically so people will stop downloading an out of date extended if there is an easy way to get the same/similar functionality from a much newer version of vanilla+externals. Judging from the continued extended bug reports of things which are generally fixed in vanilla, I’m thinking it would be a good idea to see what’s needed for a transition and start that more formal conversation. -------- Dan Wilcox @danomatika <https://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/> > On Oct 1, 2015, at 4:00 AM, pd-dev-request(a)lists.iem.at wrote: > > If by 'relative parity' you mean availability of all the externals the > last version of Pd-extended came with, this might have been reached > already. Search for 'extended' in deken. It shows a lot of (all?) > externals directly packaged from Pd-extended. Many thanks to IOhannes > for uploading all those.

8 18

[pure-data:patches] #568 Update INSTALL.txt and tcl/Makefile.am
by Antoine Rousseau 28 Dec '15

28 Dec '15

--- ** [patches:#568] Update INSTALL.txt and tcl/Makefile.am** **Status:** open **Group:** bugfix **Created:** Mon Dec 28, 2015 02:33 PM UTC by Antoine Rousseau **Last Updated:** Mon Dec 28, 2015 02:33 PM UTC **Owner:** Miller Puckette **Attachments:** - [0002-Update-tcl-Makefile.am-to-include-pd_deken.tcl.patch](https://sourcefo… (1.7 kB; text/x-patch) - [0001-Update-some-linux-parts-of-INSTALL.txt.patch](https://sourceforge.net/… (1.3 kB; text/x-patch) Update tcl/Makefile.am to include pd_deken.tcl (which was not properly installed) and Update some linux parts of INSTALL.txt --- Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to https://sourceforge.net/p/pure-data/patches/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pure-data/admin/patches/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

1 0

[pure-data:bugs] #1224 should number2 clip values?
by danomatika 28 Dec '15

28 Dec '15

--- ** [bugs:#1224] should number2 clip values?** **Status:** open **Group:** v0.46 **Created:** Mon Dec 28, 2015 01:36 AM UTC by danomatika **Last Updated:** Mon Dec 28, 2015 01:36 AM UTC **Owner:** nobody sliders, radios, etc no longer clip incoming values as of Pd 0.46-7. number2 (nbox) still does however. Should it be updated as well to match the behavior of floatatom? --- Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to https://sourceforge.net/p/pure-data/bugs/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pure-data/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

1 0

[pure-data:bugs] #1223 [declare -stdlib] crashes libpd
by Ticket 1223 25 Dec '15

25 Dec '15

--- ** [bugs:#1223] [declare -stdlib] crashes libpd** **Status:** open **Group:** v0.46 **Created:** Fri Dec 25, 2015 03:24 AM UTC by Anonymous **Last Updated:** Fri Dec 25, 2015 03:24 AM UTC **Owner:** nobody libpd crashes on a [declare -stdlib] in g_canvas.c canvas_completepath() line 1294 as sys_libdir is NULL, probably because libpd doesn't set the extra libdir? --- Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to http://sourceforge.net/p/pure-data/bugs/ To unsubscribe from further messages, a project admin can change settings at http://sourceforge.net/p/pure-data/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

1 0

[pure-data:bugs] #1222 oscformat can't send messages starting with symbols
by danomatika 23 Dec '15

23 Dec '15

--- ** [bugs:#1222] oscformat can't send messages starting with symbols** **Status:** open **Group:** v0.46 **Created:** Wed Dec 23, 2015 07:01 PM UTC by danomatika **Last Updated:** Wed Dec 23, 2015 07:01 PM UTC **Owner:** nobody Sending messages with start with a float works fine ie. in the example: [4 5 weasel 6 7 rat < However, sending a message starting with a symbol does not: [weasel 4 5 6 7 rat < results in an error: oscformat: no method for 'weasel' Prepending list fixes this, but there isn't a mentin of it in the help patch. Since messages starting with floats are regarded as implciit lists, I'd think that messages starting with symbols would as well. --- Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to https://sourceforge.net/p/pure-data/bugs/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pure-data/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

1 0

overview of upstream sources?
by katja 23 Dec '15

23 Dec '15

With the decentralization of Pd lib version control it is hard to locate / identify upstream source repositories. Would it be feasible and useful to generate (and regularly update) an overview of forks based on http://git.puredata.info/cgit/, to be referenced from http://puredata.info/docs/developer/GettingPdSource? Katja

7 7

Please move bug tracking OFF Sourceforge
by William Huston 21 Dec '15

21 Dec '15

Please move bug tracking OFF Sourceforge. It is a well known fact that SF has joined the Dark Side, inserts malware into installers, and is blocked by many browsers. Dan Wilcox has suggested I not complain, but offer to help. OK-- I am happy to. I will begin by searching the archives for the history on this, or if anyone else has ideas/guidance, I'd be grateful. Thanks, BH -- -- May you, and all beings be happy and free from suffering :) -- ancient Buddhist Prayer (Metta)

1 0

[pure-data:bugs] #1221 add [midirealtimein] & [midiclkin] documentation
by Alexandre Porres 18 Dec '15

18 Dec '15

--- ** [bugs:#1221] add [midirealtimein] & [midiclkin] documentation** **Status:** open **Group:** v0.46 **Created:** Fri Dec 18, 2015 10:55 PM UTC by Alexandre Porres **Last Updated:** Fri Dec 18, 2015 10:55 PM UTC **Owner:** Miller Puckette There are these 2 midi objects in vanilla ([midirealtimein] & [midiclkin]) that have no help file and are not mentioned in the midi-help.pd file, neither are present in the "MIDI and OSC" section of help-intro.pd If there's nothing wrong with them, please add them to the documentation. --- Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to https://sourceforge.net/p/pure-data/bugs/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pure-data/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

1 0

Re: [PD-dev] building on OS X
by Roman Haefeli 18 Dec '15

18 Dec '15

I hope you'll be o.k. with me bringing this back to the list... On Thu, 2015-12-17 at 23:57 +0100, katja wrote: > On Wed, Dec 16, 2015 at 5:57 PM, Roman Haefeli <reduzent(a)gmail.com> wrote: > ... > >> ifeq ($(uname), MINGW) > >> ldlibs = -lwsock32 > >> endif > ... > > > > Without that clause, building fails on mingw-w64. Without the > > conditional, it breaks other platforms. I can't tell you why, but it > > works. > > I wonder what makes it work because variable 'uname' should be empty > at the point where you test it. You're right (and I seem to have already forgotten what I actually did). Sorry for the confusion. Here is the full story. I was looking for a way to cross-compile for Windows on Linux using the pd-lib-builder Makefile. So I checked how the Makefile detects the platform and I forced the platform in order to be able to cross-compile by naively setting the desired destination platform like this: $ make uname=MINGW CC=i686-w64-mingw32-gcc And later when I encountered linking issues, I added a conditional that checks for a value that I set myself. Actually, it's not uname that is set later in the Makefile (line 438), but uname is used to set the system variable to 'Windows'. It seems to me that using the same platform detection mechanism as the Makefile would be a proper(er) way to add platform specific flags. Do you think it is a good idea to do something like that: ifeq ($(findstring MINGW, $(uname)), MINGW) ldlibs = -lwsock32 endif > Can you run 'make vars' and check > values of variables 'uname' and 'ldlibs'? ~/pd-src/mrpeach/osc$ make uname=MINGW CC=i686-w64-mingw32-gcc vars [...] variable ldlibs = -lwsock32 [...] variable system = Windows [...] There is no variable 'uname', only 'system'. > I invite you to join the > discussion on this particular topic here: > https://github.com/pure-data/pd-lib-builder/issues/7. Thanks for the hint. I'll do. Roman

1 0

Re: [PD-dev] building on OS X
by Dan Wilcox 17 Dec '15

17 Dec '15

-------- Dan Wilcox @danomatika <https://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/> > On Dec 14, 2015, at 4:00 AM, pd-dev-request(a)lists.iem.at wrote: > > From: Roman Haefeli <reduzent(a)gmail.com <mailto:reduzent@gmail.com>> > Subject: [PD-dev] building on OS X > Date: December 14, 2015 at 1:53:10 AM MST > To: pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at> > > * Do I need XCode? (and thus an Apple-ID?) Yes, you need Xcode. It has the compiler & build chain you need. Open source projects generally compile just fine from the commandline. You do not need to use Xcode itself for building Pd. You also don’t need to install Xcode form the App Store. If you have an Apple ID (or can borrow someone’s) you can download the current & beta versions of Xcode from the Apple Developer site <https://developer.apple.com/> and just install it yourself. > * How do I install all other necessary tools (git, etc.)? I heard about > homebrew, fink, macports… Use Homebrew. It’s great: http://brew.sh <http://brew.sh/> > * Once things are set up, is it feasible to have completely CLI based > workflow? Yes.

4 9

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 2015