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...
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 mariomey@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 think [change] should not work like this...
______________________________**_________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/** listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
From: Alexandre Torres Porres porres@gmail.com To: Mario Mey mariomey@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 Data, an object that takes an optional float argument typically sets the value to zero if the user doesn't provide an argument.
It's not a requirement: an external author can set the default value to anything they want. It's just that doing that requires extra work (i.e., manually checking the arguments), whereas defaulting to zero happens automatically.
Anyway, I think the OP might want [change] to default to NULL-- that is, let the next incoming value pass no matter what because there isn't a previous value yet. That could be handy.
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 will be guaranteed to pass.
-Jonathan
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 mariomey@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 think [change] should not work like this...
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thanks for answering!
Who is the OP? Me? Well, if it is me... yes, I would like to have NULL as init value. But, I understand that [change] must work like it works right now. It's OK.
I use "I go bananas" patch to make it work (with [+ 1]). Then, I read Jonathan's reply... that has the same fix (with [* -1]).
Thanks everyone.
El 23/09/13 15:45, Jonathan Wilkes escribió:
From: Alexandre Torres Porres porres@gmail.com To: Mario Mey mariomey@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 Data, an object that takes an optional float argument typically sets the value to zero if the user doesn't provide an argument.
It's not a requirement: an external author can set the default value to anything they want. It's just that doing that requires extra work (i.e., manually checking the arguments), whereas defaulting to zero happens automatically.
Anyway, I think the OP might want [change] to default to NULL-- that is, let the next incoming value pass no matter what because there isn't a previous value yet. That could be handy.
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 will be guaranteed to pass.
-Jonathan
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 mariomey@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 think [change] should not work like this...
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 09/23/2013 07:55 PM, Mario Mey wrote:
Thanks for answering!
Who is the OP?
The Original Poster. :)
-Jonathan
Me? Well, if it is me... yes, I would like to have NULL as init value. But, I understand that [change] must work like it works right now. It's OK.
I use "I go bananas" patch to make it work (with [+ 1]). Then, I read Jonathan's reply... that has the same fix (with [* -1]).
Thanks everyone.
El 23/09/13 15:45, Jonathan Wilkes escribió:
From: Alexandre Torres Porres porres@gmail.com To: Mario Mey mariomey@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 Data, an object that takes an optional float argument typically sets the value to zero if the user doesn't provide an argument.
It's not a requirement: an external author can set the default value to anything they want. It's just that doing that requires extra work (i.e., manually checking the arguments), whereas defaulting to zero happens automatically.
Anyway, I think the OP might want [change] to default to NULL-- that is, let the next incoming value pass no matter what because there isn't a previous value yet.
That could be handy.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 will be guaranteed to pass.
-Jonathan
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 mariomey@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 think [change] should not work like this...
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
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 will be guaranteed to pass.
and if the incoming value is 0? =)
y
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 incoming value to your [change] object, and it will be guaranteed to pass.
and if the incoming value is 0? =)
Obviously: -0
y
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 incoming value to your [change] object, and it will be guaranteed to pass.
and if the incoming value is 0? =)
Oh yeah. So [+ 1]
-Jonathan
y
-----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* takes an argument, which is the initial value. if you fail to provide one, it will default to '0'. changing this behaviour might break patches, hence it is a no-go.
fgmadr IOhannes
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 zmoelnig@iem.atwrote:
-----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* takes an argument, which is the initial value. if you fail to provide one, it will default to '0'. changing this behaviour might break patches, hence it is a no-go.
fgmadr IOhannes
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJSQGoDAAoJELZQGcR/ejb4iO0P/iW88ih1Dn1AyvvofwWD4TFn lkg0CUrtE2ae3SyDqiRjOONnlcQdnESM3O9pEcJE2jFxpP/dVCu44xwRSkFJOzb4 9U0XvTY82jZl51uSFS/rrl2VrP1ocyRc9j3oT/LM6c6ArFZr01cKXJNJLBCKWbCA z7oL57qNmxj1Zpy3VECiHWpm+JUxo0tV2hxD1ud+Sj57aQjeAW3u8+tncRicOnAE 9Dv0q9mp5wqIJ1gNmXINi2phpZhjti/R4PpRcjfQMn7gS0N1yBQwUv8P5OWRkQ2U Mch3FvRlfV3ci6izzC3nPAkgokIk1TLem5AcMF5W+Vjvw8RpoGbAOyZU32ONko2f mmX398MGgqk9uOfm0eCv+vMzifHhk1otRfHVqLc7OG3RQgHiUZ/LBCSWx4yGDDNG KokFv1jNtQoolRgSdlYuuTOLqeLWF9OEPIrXjBJwhIOpp8Ss4YfOg9KDyNw4b61j /Tn2+/W/RB/njaBtd8/I2rVH5bHfyQ/n1JPyF5QaJeHHaOmV3OCzCdBF9zXtoTBK G4iOVNph4Oc4aOl3RZw1gopnV5Tb5cTa5on/uexGyGhMMb4F6wlGSafj+q67yKuz c5f2OLBA4mmDchAsSuPFrqZYwZVRhDGOSFNJ5h8aissdCXbJN8ndccbj5aP0Xolq Frfu/8VEvgEmMZBUlmDB =11wf -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Alexandre Torres Porres -
i go bananas -
IOhannes m zmoelnig -
Jonathan Wilkes -
Mario Mey -
yvan volochine