Re: [PD] [change] bug?

2013-09-24 Thread Dan Wilcox
Ah but then if [change] used null by default, it wouldn't actually work by default ... that seems far worse then the reasonable default of 0. On Sep 23, 2013, at 10:19 PM, pd-list-requ...@iem.at wrote: From: Mario Mey mario...@gmail.com Subject: Re: [PD] [change] bug? Date: September 23

Re: [PD] [change] bug?

2013-09-24 Thread Jonathan Wilkes
...@gmail.com *Subject:**Re: [PD] [change] bug?* *Date:*September 23, 2013 6:55:36 PM CDT *Cc:*pd-list pd-list@iem.at mailto:pd-list@iem.at Well, if it is me... yes, I would like to have NULL as init value. Dan Wilcox @danomatika danomatika.com http://danomatika.com robotcowboy.com http

Re: [PD] [change] bug?

2013-09-23 Thread Alexandre Torres Porres
that's the way it works alright. If your first value sent to it is zero, just initialize it with some other value as the argument cheers 2013/9/23 Mario Mey mario...@gmail.com If i create [change] and send it a [0(, it outputs nothing. It seems like it has already the 0 value initiated. I

Re: [PD] [change] bug?

2013-09-23 Thread IOhannes m zmoelnig
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2013-09-23 17:45, Mario Mey wrote: If i create [change] and send it a [0(, it outputs nothing. yes It seems like it has already the 0 value initiated. yes. I think [change] should not work like this... i disagree. [change] *always*

Re: [PD] [change] bug?

2013-09-23 Thread i go bananas
if you want a [change] that will always output its first value, regardless of what it is, then you could set up a little thing like this attached patch On Tue, Sep 24, 2013 at 1:19 AM, IOhannes m zmoelnig zmoel...@iem.atwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2013-09-23

[PD] [change] bug?

2013-09-23 Thread Mario Mey
If i create [change] and send it a [0(, it outputs nothing. It seems like it has already the 0 value initiated. I think [change] should not work like this... ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -

Re: [PD] [change] bug?

2013-09-23 Thread Jonathan Wilkes
From: Alexandre Torres Porres por...@gmail.com To: Mario Mey mario...@gmail.com Cc: pd-list pd-list@iem.at Sent: Monday, September 23, 2013 12:13 PM Subject: Re: [PD] [change] bug? that's the way it works alright. Yes.  It's helpful to know that in Pure

Re: [PD] [change] bug?

2013-09-23 Thread Mario Mey
fix (with [* -1]). Thanks everyone. El 23/09/13 15:45, Jonathan Wilkes escribió: From: Alexandre Torres Porres por...@gmail.com To: Mario Mey mario...@gmail.com Cc: pd-list pd-list@iem.at Sent: Monday, September 23, 2013 12:13 PM Subject: Re: [PD] [change

Re: [PD] [change] bug?

2013-09-23 Thread yvan volochine
On 23/09/13 20:45, Jonathan Wilkes wrote: You can make your own version of that by first sending a copy of the incoming value through a spigot: [spigot 1] | [* -1] | [set $1( | [change] Then set the right inlet of [spigot] to zero and send the incoming value to your [change] object, and it

Re: [PD] [change] bug?

2013-09-23 Thread Mario Mey
El 23/09/13 21:22, yvan volochine escribió: On 23/09/13 20:45, Jonathan Wilkes wrote: You can make your own version of that by first sending a copy of the incoming value through a spigot: [spigot 1] | [* -1] | [set $1( | [change] Then set the right inlet of [spigot] to zero and send the

Re: [PD] [change] bug?

2013-09-23 Thread Jonathan Wilkes
-list@iem.at Sent: Monday, September 23, 2013 12:13 PM Subject: Re: [PD] [change] bug? that's the way it works alright. Yes. It's helpful to know that in Pure Data, an object that takes an optional float argument typically sets the value to zero if the user doesn't provide an argument

Re: [PD] [change] bug?

2013-09-23 Thread Jonathan Wilkes
On 09/23/2013 08:22 PM, yvan volochine wrote: On 23/09/13 20:45, Jonathan Wilkes wrote: You can make your own version of that by first sending a copy of the incoming value through a spigot: [spigot 1] | [* -1] | [set $1( | [change] Then set the right inlet of [spigot] to zero and send the