Forums > Dev

Additions on [send] and [receive]

June 23, 2006 | 2:28 pm

Hi Cycling 74,

With the risk of sounding completely stupid: I would really like to have access to the source code of [receive] and [send] and [pv]. I believe I have some useful additions to make which will make Max even more workable as an object-oriented programming language. The new features would mainly support to make new instances of subpatchers dynamically (without the troubles of poly~) and remote-controlling their in and outputs.

Right now I use a set of abstractions that do the trick, but since every abstraction depends on loadbangs and patcherargs and adds more loadtime, and I use dozens if not hunderds of them, well.. remaking them in C would be rewarding :)

If someone from Cycling ’74 is interested I could make an example patch that illustrates what I mean. Could be like a prototype help file of the externals as I have them in mind where for now the externals are realized with abstractions.

Cheers,
Mattijs


June 23, 2006 | 2:34 pm

On Jun 23, 2006, at 9:28 AM, Mattijs Kneppers wrote:
> The new features would mainly support to make new instances of
> subpatchers dynamically (without the troubles of poly~)

and those troubles would be….?


June 23, 2006 | 2:35 pm

If you look around on your drive you will realize that not all objects
are externals – including these. These are internals – meaning their
functionality is built into Max itself. Sorry to disappoint…

-Tim


June 23, 2006 | 2:50 pm

Quote: Timothy Place wrote on Fri, 23 June 2006 16:35
—————————————————-
These are internals – meaning their
> functionality is built into Max itself. Sorry to disappoint…

It is maybe an oblique attempt to get Max’ sources ;-)

p


June 23, 2006 | 3:01 pm

Quote: Timothy Place wrote on Fri, 23 June 2006 16:35
—————————————————-
> If you look around on your drive you will realize that not all objects
> are externals – including these. These are internals – meaning their
> functionality is built into Max itself. Sorry to disappoint…
>
> -Tim
>
—————————————————-

Oops.. yeah that’s nasty. I was really looking forward to this :’/

So does that mean that there are no handles available to make such an external? Would it be possible at all to make two objects communicate with each other without a ‘physical’ connection? coll makes use of the ob_messagelist to share info, right? Is there a similar way to send events? Should I just shake off the whole idea?

A lot of questions :) If I should be able to find the answers somewhere in the sdk it would be enough to point me in that direction.

Thanks for the fast replies!
Mattijs


June 23, 2006 | 3:10 pm

On 23 Jun 2006, at 16:01, Mattijs Kneppers wrote:

> Would it be possible at all to make two objects communicate with
> each other without a ‘physical’ connection?

Yep – easy. The SDK and code examples show ways of doing this.

I don’t see why you would want the sources to send/receive: just
write new ones (prefixed by some kind of unique tag, like your name).

– N.

nick rothwell — composition, systems, performance — http://
http://www.cassiel.com


June 23, 2006 | 3:45 pm

Thanks Nick, I looked through the sdk a little closer and I found the connection methods! This looks promising! I can’t find a code example though. Did you have a particular example in mind?

Mattijs


Viewing 7 posts - 1 through 7 (of 7 total)