Pd-list December 2019

pd-list@lists.iem.at

34 participants
39 discussions

Re: [PD] Pd double precision testing.
by Dan Wilcox 07 Dec '19

07 Dec '19

There is a double precision test build for macOS here: http://docs.danomatika.com/pdbuilds/0.51/ <http://docs.danomatika.com/pdbuilds/0.51/> As development continues, I will throw additional test builds up there. > On Dec 6, 2019, at 12:13 AM, pd-list-request(a)lists.iem.at wrote: > > Hi all, > > There is an experimental branch[1] on Pd-double-precision[2]. > > So far we know a couple of things not working yet like writing audio > files with [soundfiler] or [writesf~]. > > If anyone is willing to test and find something else not working we > welcome and appreciate it. > > Here's a Windows64 version for tests : > http://lucarda.com.ar/x/Pd-double-w64-testing.zip <http://lucarda.com.ar/x/Pd-double-w64-testing.zip> > > Tests should be done with "vanilla-only" patches. 99% of externals were > not compiled for double-precision so they don't work with this Pd. > > If you find something not working write back here to the list or issue > it to github (prepend "double-precision: " on the name of the issue). > > [1] https://github.com/pure-data/pure-data/tree/double-precision <https://github.com/pure-data/pure-data/tree/double-precision> > [2] http://www.katjaas.nl/doubleprecision/doubleprecision.html <http://www.katjaas.nl/doubleprecision/doubleprecision.html> -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

4 5

Re: [PD] store a symbol and send on bang
by Dan Wilcox 07 Dec '19

07 Dec '19

How about [value -s] instead? :) I just whipped up a [value] update which changes the backing value storage to use a t_atom and allows setting the value type based on a flag: -s makes a symbol value, otherwise a float value. There are some checks against type mismatches between the same name. This allows for sending & receiving symbols via [value -s] or [v -s] objects. Existing [value] and [v] objects are float types. The only issue I can see, other than a little more memory usage and type checking, would be possibly breaking patches which use "-s" as a value name. In this case, sending a float to the inlet is silently ignored and a default "symbol" symbol would be output on a bang which would cause a trackable error. I can put up a PR soon when I clean up this change a bit. In the meantime, macOS people can try out a test build: Pd-0.50.2-value-symbol.zip <http://docs.danomatika.com/pdbuilds/0.51/Pd-0.50.2-value-symbol.zip> > On Dec 6, 2019, at 5:50 PM, pd-list-request(a)lists.iem.at wrote: > > From: IOhannes m zmölnig <zmoelnig(a)iem.at <mailto:zmoelnig@iem.at>> > To: pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at> > Subject: Re: [PD] store a symbol and send on bang > Message-ID: <A60DFF22-1380-4C37-84AB-D66D877F4819(a)iem.at <mailto:A60DFF22-1380-4C37-84AB-D66D877F4819@iem.at>> > Content-Type: text/plain; charset=utf-8 > > Am 6. Dezember 2019 15:27:02 MEZ schrieb Christof Ressi <christof.ressi(a)gmx.at <mailto:christof.ressi@gmx.at>>: >> This would just complicate the interface. Just use [symbol] + [send] and you're done. > > > +1 > > also, [symbol -s] would make it quite complicated to create a symbol "-s"... > > > > mfg.hft.fsl > IOhannes -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

3 5

64-bit accumulator external
by Charles Z Henry 06 Dec '19

06 Dec '19

The double precision testing thread leads me to comment on an external I've been writing. I decided I needed an external (with 32-bit signals input) that would add up blocks of signals over time with an internal 64-bit accumulator to avoid losing precision during this step. But as I thought about other options for it to perform (sample-wise accumulation, sum of squares, whether the output should be normalized), it started turning into a real swiss army knife, one object with a ton of configuration choices, outputs, and control options. It could be used to read long tables with tabread4~~ for instance, or turn distributions into normalized cumulative distribution functions. There would be the option of retrieving the full 64-bit value on the output through pairs of signals/messages or truncating the precision back to 32-bits with a single output. When signals fan in to a inlet they are summed together in 32-bits, so that has to be avoided. Should I have it use a variable number of inlets or make new objects that have multiple inlets? Yikes... what am I doing? Is there a different question here? What set of 64-bit externals could do all the things a double-precision Pd *could* do? You only really lose precision when doing certain things. Is there a better way to organize the functions for usage among several objects? Which ones are essential? What set would make it complete? Yikes... In the same manner as the PdCUDA signal memory space and perform routine duplication (I designed but never published an implementation), you could control whether objects used a 32-bit signal memory space and dsp functions vs a 64-bit version of the same. You'd control the behavior through the dspcontext struct and add an object to switch it on/off in subpatches, thus using the double precision only when you need it. Array design and implementation remains problematic. This is a terrible idea. I'll go ahead and build something for my immediate usage (after my classes conclude in 2 weeks) that does just a few things, but I have to wonder if there's something better there that should be done instead. Any advice? Chuck

1 0

store a symbol and send on bang
by Csaba Láng 06 Dec '19

06 Dec '19

Dear list, is there a way to store a symbol and send it on a bang as the [value] or [float] objects do it with floats? Popesz

5 8

writing to cyclone/coll takes a long time
by Jakob Laue 06 Dec '19

06 Dec '19

Dear list, For a university project we are building a melody generator based on markov chains. This includes generating a big matrix of probabilities for playing a certain note. The number of rows in the matrix depends on the markov order and the pitch range that our patch works with. We have a pitch range of 9, hence markov order 3 means writing 9^3 rows = 729. We want to work with the fifth order which means writing 9^5 = 59049 rows into the matrix. We use the coll object from the cyclone library to generate our matrix because it has the handy gui for looking at your matrix after you generated it. Our problem is that it takes more than 3 minutes to write 60000 rows into the coll object and we don't understand why. Attached we have a test patch that simulates our matrix generation. Writing 700 rows into coll takes less than a second, writing 6000 rows takes round about 1.5 seconds (simulating fourth order/9^4), writing 60000 rows takes 3 minutes and 45 seconds. Do you have any hint why it takes that long to write 60000 rows into coll? Maybe we do something wrong or have missed some smarter way to write our rows into the coll matrix. We are on: MacBook Pro 13" early 2011, macOS Sierra 10.12.6 Pd 0.48-0 Thanks, Hajar and Jakob

5 7

Knowing if Pd is in Edit mode when instantiating an object (was Query if Pd is in Edit mode for a GUI)
by Alexandre Torres Porres 06 Dec '19

06 Dec '19

> > Em ter, 26 de fev de 2019 às 04:28, Liam Goodacre <liamg_uw(a)hotmail.com> > escreveu: > >> My guess is that the message stream that [receivecanvas] taps into would >> let you listen to the edit-mode state changes, but not query its state. >> > Hi, earlier this year I was asking about querying edit status and Liam told me about [receivecanvas], the problem is that it only tells you about when the status changes. Now, if I create an object when I'm in edit mode, it won't know, and when I open a patch not in edit mode, it won't know either. So how can I know about it? thanks

3 7

Re: [PD] Pd double precision testing.
by Lucas Cordiviola 06 Dec '19

06 Dec '19

On 12/5/2019 7:41 PM, Edwin van der Heide wrote: > Is there also a macOS version or should I compile it myself? I'm not a macOS user but you can compile it. Sources are here : https://github.com/pure-data/pure-data/tree/double-precision If you have xcode installed do: ~~ cd path/to/pd ./autogen.sh ./configure CPPFLAGS=-DPD_FLOATSIZE=64 make make app ~~ If you have never compiled lets wait until someone brings one to this thread. :) Mensaje telepatico asistido por maquinas.

1 0

Get the info error info from console and end it to port
by Csaba Láng 05 Dec '19

05 Dec '19

Dear list, I need to send to an application if there is an error in the console, which does not appear anywhere in the patch itself. How can I get the error, let's say the file does not exist? Thanks for any hints. Best, Popesz

2 3

send a multiatom control message via netreceive
by Csaba Láng 05 Dec '19

05 Dec '19

Dear list, I need to send a control message back to the sender on the network if the message has arrived to Pd. this part works fine: [list /LOGIN 6( | [send /OK $1 $2( | [netreceive] Or the first message can be [list /BEGIN CODE50( I need to make in the first message after list 2 or 3 variables [list $1 $2 $3( where the variable sometime a float, or a symbol. With [pack s s s] does not work, as even I change the float to symbol, it won't accept it. It should not be so difficult, but I am stuck totally. Thanks, Popesz

2 1

FUDI protocol and interfacing external programs with netreceive
by afleck＠inventati.org 05 Dec '19

05 Dec '19

Hello, I have been looking into writing some external programs to send messages to pd via netreceive. With netreceive in udp mode (-u), sending bytes not terminated by a newline does not generate anything at the outlet. By "sending bytes" I do not mean that I have netreceive in -b mode, just that I am not automatically terminating the message with a newline, as would happen with "echo foo; | pdsend 9999 localhost udp." In -b mode no newline is necessary. As soon as a newline is added, the message is at the outlet. Furthermore, it's actually not even necessary to include a semicolon in the datagram. If i send the bytes \102\111\111\10 ("foo\n") to a netreceive connected to print, i see "print: foo" in the console. This is not at all clear from either the help patches on netsend and netreceive or the little information available online about FUDI, all of which mention that a message is just atoms, numbers, and whitespace terminated by a semicolon. The Wikipedia page on FUDI even says "A newline is just treated as whitespace and not needed for message termination." as far as I can tell this was sourced from a (now offline but archived) pure data wiki page, the genesis of which can be found at: https://lists.puredata.info/pipermail/pd-list/2009-01/067238.html. There's a good lead at https://lists.puredata.info/pipermail/pd-list/2013-01/100183.html, mentioning the required newline, but it also says a semicolon is required, which I have found to not be the case. Can anyone clear this up for me? Is there any official specification of FUDI available? I think having this information easily available would be nice, and after I get to the bottom of it I'll correct the Wikipedia page! I would also like to know how to send multiple messages in one datagram. Sending "foo;bar;\n" to a netreceive connected to print only gives me "print: foo" at the console, and trying to [route foo bar] doesn't work. Cheers

2 1

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