/
--
From: Фывапр Олджэвич tofuc...@inbox.ru
To: PD-list pd-list@iem.at
Sent: Thursday, 12 July 2012, 14:45
Subject: [PD] scale ?
Hi !
how to do simple scaling in PD ?
not via [autoscale] which is really unstable
there is a [scale] object in MAX but here
Hi !
how to do simple scaling in PD ?
not via [autoscale] which is really unstable
there is a [scale] object in MAX but here it is for GEM
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
load and use the maxlib sacale object
[maxlib/scale]
On Thu, Jul 12, 2012 at 10:45 AM, Фывапр Олджэвич tofuc...@inbox.ru wrote:
Hi !
how to do simple scaling in PD ?
not via [autoscale] which is really unstable
there is a [scale] object in MAX but here it is for GEM
On Thu, Jul 12, 2012 at 3:45 PM, Фывапр Олджэвич tofuc...@inbox.ru wrote:
Hi !
how to do simple scaling in PD ?
The simplest way is just with [* ], [/ ], [- ] and [+ ].
For example 0 -- 127 to -1 -- 1:
[/ 63.5]
|
[- 1]
--Funs
___
Pd-list@iem.at
Hallo,
nick burge hat gesagt: // nick burge wrote:
Thank you Marius. I'm using the extended version, so yes, that works.
Or use an abstraction like the attached one, probably available in
pd-extended as for example rtc/expr_scale, only does linear scaling.
Ciao
--
Frank Barknecht
Hello List, does anyone know how to resolve the name conflict between the
scale object in maxlib and Gem?
I want to open the maxlib object , but the Gem object opens instead. (I want
to make use of both libraries simultaneously).
thanks, Nick Burge.
[maxlib/scale]
.hc
On Apr 17, 2008, at 1:41 PM, nick burge wrote:
Hello List, does anyone know how to resolve the name conflict
between the
scale object in maxlib and Gem?
I want to open the maxlib object , but the Gem object opens
instead. (I want
to make use of both libraries
in theory, if you don't load gem and maxlib automatically, you should be
able to put [import gem] in one patch and [import maxlib] into another
and then you could use the gem scale in one patch and the maxlib scale
in the other. But I think this feature is broken right now.
if you're on
Thank you Marius. I'm using the extended version, so yes, that works.
Nick.
-Original Message-
From: marius schebella [mailto:[EMAIL PROTECTED]
Sent: 17 April 2008 19:58
To: nick burge
Cc: Pd List
Subject: Re: [PD] scale object name conflict between Gem and maxlib
in theory, if you
On Tue, 25 Sep 2007, Claude Heiland-Allen wrote:
--8--
Unless they arrange otherwise by defining a list method, objects
respond to the list message by distributing the arguments of the
message to their inlets, except for the first argument which is passed
as a float or symbol message to the
This is a standard feature of all obects/externals:
If the hot inlet does not accept a list, the first element is sent to
the
first inlet, the second element to the second inlet, etc...
oh, I guess I was missing something all these years
You were probably already using it with [line~]
course it's a really handy tool. but since I can't look at an object
inside it's code, there was no way for me to know about it.
That is interesting to know. I didn't know that it was a standard
behavior either but since you've brought it up, now I'd like to
know how the code allows this
Charles Henry wrote:
I will have to read some more later~
http://www-crca.ucsd.edu/~msp/Pd_documentation/x2.htm#s6.4
--8--
Unless they arrange otherwise by defining a list method, objects
respond to the list message by distributing the arguments of the
message to their inlets, except for the
Charles Henry wrote:
course it's a really handy tool. but since I can't look at an object
inside it's code, there was no way for me to know about it.
That is interesting to know. I didn't know that it was a standard
behavior either but since you've brought it up, now I'd like to
Hallo,
João Miguel Pais hat gesagt: // João Miguel Pais wrote:
This is a standard feature of all obects/externals:
If the hot inlet does not accept a list, the first element is sent to the
first inlet, the second element to the second inlet, etc...
oh, I guess I was missing something all
On Sun, 23 Sep 2007, João Miguel Pais wrote:
I just found out that if a list is sent to a |scale|, all values after the
1st substitute the parameters. The result will be the scaling of the 1st
number, but already with the new parameters.
Is this intentional, or was it a lucky effect? Maybe it
Hi,
I just found out that if a list is sent to a |scale|, all values after the
1st substitute the parameters. The result will be the scaling of the 1st
number, but already with the new parameters.
Is this intentional, or was it a lucky effect? Maybe it would be better to
update the
This is a standard feature of all obects/externals:
If the hot inlet does not accept a list, the firs
Tom
On 9/22/07, João Miguel Pais [EMAIL PROTECTED] wrote:
Hi,
I just found out that if a list is sent to a |scale|, all values after the
1st substitute the parameters. The result will be
This is a standard feature of all obects/externals:
If the hot inlet does not accept a list, the first element is sent to the
first inlet, the second element to the second inlet, etc...
Tom
On 9/22/07, João Miguel Pais [EMAIL PROTECTED] wrote:
Hi,
I just found out that if a list is
19 matches
Mail list logo
