I'm on pd-0.47-1 binary downloaded from UCSD [mac 64-bit].
I've created a clone of an abstraction that has the left inlet as a signal inlet.. from the docs I'd expect I can send a |vis 5 1( message to that inlet and display the patch but I can't. If I create another inlet, to the right of that inlet, which is a control inlet, I can send the vis message to that and my instance does pop up but it does seem to me that the |vis( message should always go into the left inlet to keep things consistent?
I attached an example, leftsig_test.pd is the patch to open.
BTW, this clone stuff is really making me wish we could have abstractions that take both a signal and control info on a single inlet [like dac and some other tilde objects].. I've created a wrapper around clone to play with cascading abstractions and it would be nice if I could have my wrapper operate the same as I'm assuming clone should? I know there was discussion before.. maybe [inlet~] could actually have 2 outlets, a signal outlet and a control outlet?
-Alex
Good idea ... I have to think about whether this is possible to do. If I could ake inlets that take both control and signal, then I could easily fix clone~ to take control messages like "vis" from inlets of either type.
Also that might be the way for me to fix a long-standing bug - float messages to signal subpatch inlets don't work.
cheers Miller
On Thu, Jun 23, 2016 at 09:42:18AM -0700, Alex wrote:
I'm on pd-0.47-1 binary downloaded from UCSD [mac 64-bit].
I've created a clone of an abstraction that has the left inlet as a signal inlet.. from the docs I'd expect I can send a |vis 5 1( message to that inlet and display the patch but I can't. If I create another inlet, to the right of that inlet, which is a control inlet, I can send the vis message to that and my instance does pop up but it does seem to me that the |vis( message should always go into the left inlet to keep things consistent?
I attached an example, leftsig_test.pd is the patch to open.
BTW, this clone stuff is really making me wish we could have abstractions that take both a signal and control info on a single inlet [like dac and some other tilde objects].. I've created a wrapper around clone to play with cascading abstractions and it would be nice if I could have my wrapper operate the same as I'm assuming clone should? I know there was discussion before.. maybe [inlet~] could actually have 2 outlets, a signal outlet and a control outlet?
-Alex
Either way, isn't [clone] a built in object so can't it take messages _and_ signals on its left inlet like [dac]? I guess maybe it sets up its inlets to be the same as the abstraction which doesn't allow for that.. [haven't looked at the guts].
On Thu, Jun 23, 2016 at 9:52 AM, Miller Puckette msp@ucsd.edu wrote:
Good idea ... I have to think about whether this is possible to do. If I could ake inlets that take both control and signal, then I could easily fix clone~ to take control messages like "vis" from inlets of either type.
Also that might be the way for me to fix a long-standing bug - float messages to signal subpatch inlets don't work.
cheers Miller
On Thu, Jun 23, 2016 at 09:42:18AM -0700, Alex wrote:
I'm on pd-0.47-1 binary downloaded from UCSD [mac 64-bit].
I've created a clone of an abstraction that has the left inlet as a
signal
inlet.. from the docs I'd expect I can send a |vis 5 1( message to that inlet and display the patch but I can't. If I create another inlet, to
the
right of that inlet, which is a control inlet, I can send the vis message to that and my instance does pop up but it does seem to me that the |vis( message should always go into the left inlet to keep things consistent?
I attached an example, leftsig_test.pd is the patch to open.
BTW, this clone stuff is really making me wish we could have abstractions that take both a signal and control info on a single inlet [like dac and some other tilde objects].. I've created a wrapper around clone to play with cascading abstractions and it would be nice if I could have my
wrapper
operate the same as I'm assuming clone should? I know there was
discussion
before.. maybe [inlet~] could actually have 2 outlets, a signal outlet
and
a control outlet?
-Alex
No, there's no 'main inlet' - it's suppressed (as in [pd] and a couple of others).
cheers M
On Thu, Jun 23, 2016 at 09:56:30AM -0700, Alex wrote:
Either way, isn't [clone] a built in object so can't it take messages _and_ signals on its left inlet like [dac]? I guess maybe it sets up its inlets to be the same as the abstraction which doesn't allow for that.. [haven't looked at the guts].
On Thu, Jun 23, 2016 at 9:52 AM, Miller Puckette msp@ucsd.edu wrote:
Good idea ... I have to think about whether this is possible to do. If I could ake inlets that take both control and signal, then I could easily fix clone~ to take control messages like "vis" from inlets of either type.
Also that might be the way for me to fix a long-standing bug - float messages to signal subpatch inlets don't work.
cheers Miller
On Thu, Jun 23, 2016 at 09:42:18AM -0700, Alex wrote:
I'm on pd-0.47-1 binary downloaded from UCSD [mac 64-bit].
I've created a clone of an abstraction that has the left inlet as a
signal
inlet.. from the docs I'd expect I can send a |vis 5 1( message to that inlet and display the patch but I can't. If I create another inlet, to
the
right of that inlet, which is a control inlet, I can send the vis message to that and my instance does pop up but it does seem to me that the |vis( message should always go into the left inlet to keep things consistent?
I attached an example, leftsig_test.pd is the patch to open.
BTW, this clone stuff is really making me wish we could have abstractions that take both a signal and control info on a single inlet [like dac and some other tilde objects].. I've created a wrapper around clone to play with cascading abstractions and it would be nice if I could have my
wrapper
operate the same as I'm assuming clone should? I know there was
discussion
before.. maybe [inlet~] could actually have 2 outlets, a signal outlet
and
a control outlet?
-Alex
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
I guess that makes sense as you wouldn't expect to have any inlet to your clone if your abstraction didn't have any inlets. though then you couldn't vis either.. Acknowledged!
On Thu, Jun 23, 2016 at 10:18 AM, Miller Puckette msp@ucsd.edu wrote:
No, there's no 'main inlet' - it's suppressed (as in [pd] and a couple of others).
cheers M
On Thu, Jun 23, 2016 at 09:56:30AM -0700, Alex wrote:
Either way, isn't [clone] a built in object so can't it take messages
_and_
signals on its left inlet like [dac]? I guess maybe it sets up its inlets to be the same as the abstraction which doesn't allow for that.. [haven't looked at the guts].
On Thu, Jun 23, 2016 at 9:52 AM, Miller Puckette msp@ucsd.edu wrote:
Good idea ... I have to think about whether this is possible to do. If I could ake inlets that take both control and signal, then I could
easily
fix clone~ to take control messages like "vis" from inlets of either
type.
Also that might be the way for me to fix a long-standing bug - float messages to signal subpatch inlets don't work.
cheers Miller
On Thu, Jun 23, 2016 at 09:42:18AM -0700, Alex wrote:
I'm on pd-0.47-1 binary downloaded from UCSD [mac 64-bit].
I've created a clone of an abstraction that has the left inlet as a
signal
inlet.. from the docs I'd expect I can send a |vis 5 1( message to
that
inlet and display the patch but I can't. If I create another inlet,
to
the
right of that inlet, which is a control inlet, I can send the vis
message
to that and my instance does pop up but it does seem to me that the
|vis(
message should always go into the left inlet to keep things
consistent?
I attached an example, leftsig_test.pd is the patch to open.
BTW, this clone stuff is really making me wish we could have
abstractions
that take both a signal and control info on a single inlet [like dac
and
some other tilde objects].. I've created a wrapper around clone to
play
with cascading abstractions and it would be nice if I could have my
wrapper
operate the same as I'm assuming clone should? I know there was
discussion
before.. maybe [inlet~] could actually have 2 outlets, a signal
outlet
and
a control outlet?
-Alex
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Correct... I haven't figured out how you can get messages to contol-inlet-less clone~ copies :)
On Thu, Jun 23, 2016 at 10:25:04AM -0700, Alex wrote:
I guess that makes sense as you wouldn't expect to have any inlet to your clone if your abstraction didn't have any inlets. though then you couldn't vis either.. Acknowledged!
On Thu, Jun 23, 2016 at 10:18 AM, Miller Puckette msp@ucsd.edu wrote:
No, there's no 'main inlet' - it's suppressed (as in [pd] and a couple of others).
cheers M
On Thu, Jun 23, 2016 at 09:56:30AM -0700, Alex wrote:
Either way, isn't [clone] a built in object so can't it take messages
_and_
signals on its left inlet like [dac]? I guess maybe it sets up its inlets to be the same as the abstraction which doesn't allow for that.. [haven't looked at the guts].
On Thu, Jun 23, 2016 at 9:52 AM, Miller Puckette msp@ucsd.edu wrote:
Good idea ... I have to think about whether this is possible to do. If I could ake inlets that take both control and signal, then I could
easily
fix clone~ to take control messages like "vis" from inlets of either
type.
Also that might be the way for me to fix a long-standing bug - float messages to signal subpatch inlets don't work.
cheers Miller
On Thu, Jun 23, 2016 at 09:42:18AM -0700, Alex wrote:
I'm on pd-0.47-1 binary downloaded from UCSD [mac 64-bit].
I've created a clone of an abstraction that has the left inlet as a
signal
inlet.. from the docs I'd expect I can send a |vis 5 1( message to
that
inlet and display the patch but I can't. If I create another inlet,
to
the
right of that inlet, which is a control inlet, I can send the vis
message
to that and my instance does pop up but it does seem to me that the
|vis(
message should always go into the left inlet to keep things
consistent?
I attached an example, leftsig_test.pd is the patch to open.
BTW, this clone stuff is really making me wish we could have
abstractions
that take both a signal and control info on a single inlet [like dac
and
some other tilde objects].. I've created a wrapper around clone to
play
with cascading abstractions and it would be nice if I could have my
wrapper
operate the same as I'm assuming clone should? I know there was
discussion
before.. maybe [inlet~] could actually have 2 outlets, a signal
outlet
and
a control outlet?
-Alex
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
-
Alex -
Miller Puckette