Guillaume Evrard

with max 4, it was possible to use an abstraction by typing the whole path

this seems not to be possible anymore with max 5...

this was useful to be sure to use the right object (and the users profiles

system of my application works on this possibility)

is there a chance to see this feature again in max 5 ?

with max 4, it was possible to use an abstraction by typing the whole path
as a symbol in the box.

this was useful to be sure to use the right object (and the users profiles
system of my application works on this possibility)

scripting-specific-objects

> with max 4, it was possible to use an abstraction by typing the 

> this seems not to be possible anymore with max 5...

> this was useful to be sure to use the right object (and the users 

> profiles system of my application works on this possibility)

> is there a chance to see this feature again in max 5 ?

It works fine here. Assuming that you're on mac, and that your hard 

script newobject newobj @text ""Macintosh HD:/Applications/Max5/ 

examples/max-tricks/random_with_no_repeat/urn-jb.maxpat""

Note the extras " because of the space in the HD name. If it doesn't 

> hi list !
>
> with max 4, it was possible to use an abstraction by typing the  
> whole path as a symbol in the box.
>
> this seems not to be possible anymore with max 5...
>
> this was useful to be sure to use the right object (and the users  
> profiles system of my application works on this possibility)
>
> is there a chance to see this feature again in max 5 ?

It works fine here. Assuming that you're on mac, and that your hard  
disk is named "Macintosh HD":

script newobject newobj @text ""Macintosh HD:/Applications/Max5/ 
examples/max-tricks/random_with_no_repeat/urn-jb.maxpat""

Note the extras " because of the space in the HD name. If it doesn't  
work, please provide an example.

thanks for reply, my hardrive is named "Data", the whole path is

Data:/MAXLIBS/2PIM/DefaultProfile/Audio/2PIM-adv.audioout.maxpat

the hard drive name MUST be "Macintosh HD" ?

> It works fine here. Assuming that you're on mac, and that your hard disk is

> script newobject newobj @text ""Macintosh

> HD:/Applications/Max5/examples/max-tricks/random_with_no_repeat/urn-jb.maxpat""

> Note the extras " because of the space in the HD name. If it doesn't work,

thanks for reply, my hardrive is named "Data", the whole path is
Data:/MAXLIBS/2PIM/DefaultProfile/Audio/2PIM-adv.audioout.maxpat
there's no spaces so no "" trick...
the hard drive name MUST be "Macintosh HD" ?

>
> It works fine here. Assuming that you're on mac, and that your hard disk is
> named "Macintosh HD":
>
> script newobject newobj @text ""Macintosh
> HD:/Applications/Max5/examples/max-tricks/random_with_no_repeat/urn-jb.maxpat""
>
> Note the extras " because of the space in the HD name. If it doesn't work,
> please provide an example.
>
> Best,
> ej
>
>

> thanks for reply, my hardrive is named "Data", the whole path is 

> Data:/MAXLIBS/2PIM/DefaultProfile/Audio/2PIM-adv.audioout.maxpat

> the hard drive name MUST be "Macintosh HD" ?

> hi emmanuel,
>
> thanks for reply, my hardrive is named "Data", the whole path is  
> Data:/MAXLIBS/2PIM/DefaultProfile/Audio/2PIM-adv.audioout.maxpat
> there's no spaces so no "" trick...
> the hard drive name MUST be "Macintosh HD" ?

i'm on it right now, doing exactly what you sent.

>> thanks for reply, my hardrive is named "Data", the whole path is

>> Data:/MAXLIBS/2PIM/DefaultProfile/Audio/2PIM-adv.audioout.maxpat

>> the hard drive name MUST be "Macintosh HD" ?

> On 2 juil. 08, at 10:04, G. wrote:
>
>  hi emmanuel,
>>
>> thanks for reply, my hardrive is named "Data", the whole path is
>> Data:/MAXLIBS/2PIM/DefaultProfile/Audio/2PIM-adv.audioout.maxpat
>> there's no spaces so no "" trick...
>> the hard drive name MUST be "Macintosh HD" ?
>>
>
>
> No it's even easier:
>
>
>
>
> ej
>
>

creating specific objects is ok, but the connection script acts weird.

it works fine when the patcher is in edit mode (and #0 stays #0 in the

but when i use my object as an abstraction, the connection doesn't work

the only difference is that #0 becomes a number...

> i'm on it right now, doing exactly what you sent.

>>> thanks for reply, my hardrive is named "Data", the whole path is

>>> Data:/MAXLIBS/2PIM/DefaultProfile/Audio/2PIM-adv.audioout.maxpat

>>> the hard drive name MUST be "Macintosh HD" ?

ok i have now a new problem
creating specific objects is ok, but the connection script acts weird.

it works fine when the patcher is in edit mode (and #0 stays #0 in the
objects names)
but when i use my object as an abstraction, the connection doesn't work
anymore (jpatchline_new: can't find box)

> hi emmanuel,
>
> i'm on it right now, doing exactly what you sent.
>
> thanks for your help !
>
>
> 2008/7/2 Emmanuel Jourdan :
>
>> On 2 juil. 08, at 10:04, G. wrote:
>>
>>
>>  hi emmanuel,
>>>
>>> thanks for reply, my hardrive is named "Data", the whole path is
>>> Data:/MAXLIBS/2PIM/DefaultProfile/Audio/2PIM-adv.audioout.maxpat
>>> there's no spaces so no "" trick...
>>> the hard drive name MUST be "Macintosh HD" ?
>>>
>>
>>
>> No it's even easier:
>>
>>
>>
>>
>> ej
>>
>>
>
>

> creating specific objects is ok, but the connection script acts weird.

> it works fine when the patcher is in edit mode (and #0 stays #0 in 

> but when i use my object as an abstraction, the connection doesn't 

> work anymore (jpatchline_new: can't find box)

> the only difference is that #0 becomes a number...

> re-hello !
>
> ok i have now a new problem
> creating specific objects is ok, but the connection script acts weird.
>
> it works fine when the patcher is in edit mode (and #0 stays #0 in  
> the objects names)
> but when i use my object as an abstraction, the connection doesn't  
> work anymore (jpatchline_new: can't find box)
>
> the only difference is that #0 becomes a number...

the first is the one where the abstraction is created and connected,

the second is the abstraction (tobescripted.maxpat), it is a simple 16x16

here is the first patch where the script is executed :

of course, here are the 2 patches,
the first is the one where the abstraction is created and connected,
the second is the abstraction (tobescripted.maxpat), it is a simple 16x16
thru.

> the first is the one where the abstraction is created and connected,

> the second is the abstraction (tobescripted.maxpat), it is a simple 

Here is something which seems to work ;-) Using the [combine] object 

to generate the string. Note that you probably don't really need the 

> of course, here are the 2 patches,
> the first is the one where the abstraction is created and connected,
> the second is the abstraction (tobescripted.maxpat), it is a simple  
> 16x16 thru.

Here is something which seems to work ;-) Using the [combine] object  
to generate the string. Note that you probably don't really need the  
#0 because the varname are local.

i get exactly the same behavior with your patch...

the combine object doesn't seem to make it.

>> the first is the one where the abstraction is created and connected,

>> the second is the abstraction (tobescripted.maxpat), it is a simple 16x16

> Here is something which seems to work ;-) Using the [combine] object to

> generate the string. Note that you probably don't really need the #0 because

i get exactly the same behavior with your patch...
the combine object doesn't seem to make it.
g

> On 2 juil. 08, at 15:07, G. wrote:
>
>  of course, here are the 2 patches,
>> the first is the one where the abstraction is created and connected,
>> the second is the abstraction (tobescripted.maxpat), it is a simple 16x16
>> thru.
>>
>
> Here is something which seems to work ;-) Using the [combine] object to
> generate the string. Note that you probably don't really need the #0 because
> the varname are local.
>
> ej
>
>
>
>
>

well the combine object simplify the patch for the creation, but the

connection with matrix~ and outlets still doesn't work if abstraction.

> i get exactly the same behavior with your patch...

> the combine object doesn't seem to make it.

>>> the first is the one where the abstraction is created and connected,

>>> the second is the abstraction (tobescripted.maxpat), it is a simple 16x16

>> Here is something which seems to work ;-) Using the [combine] object to

>> generate the string. Note that you probably don't really need the #0 because

well the combine object simplify the patch for the creation, but the
connection with matrix~ and outlets still doesn't work if abstraction.

> i get exactly the same behavior with your patch...
> the combine object doesn't seem to make it.
> g
>
> 2008/7/2 Emmanuel Jourdan :
>
>> On 2 juil. 08, at 15:07, G. wrote:
>>
>>
>>  of course, here are the 2 patches,
>>> the first is the one where the abstraction is created and connected,
>>> the second is the abstraction (tobescripted.maxpat), it is a simple 16x16
>>> thru.
>>>
>>
>> Here is something which seems to work ;-) Using the [combine] object to
>> generate the string. Note that you probably don't really need the #0 because
>> the varname are local.
>>
>> ej
>>
>>
>>
>>
>>
>
>

Weird it works here with different cases:

- patch outside of the search path by providing an absolute path (with 

> i get exactly the same behavior with your patch...
> the combine object doesn't seem to make it.

Weird it works here with different cases:
- patch in the search path
- patch outside of the search path by providing an absolute path (with  
or without spaces).

but still no connection between the scripted abstraction and the matrix~ object when the whole patch is an abstraction...

On 2 juil. 08, at 17:13, guillaume wrote:

> but still no connection between the scripted abstraction and the 

> matrix~ object when the whole patch is an abstraction...

the abstraction is properly created? what happens if you connect with 

> yes i'm running 5.0.3
>
> but still no connection between the scripted abstraction and the  
> matrix~ object when the whole patch is an abstraction...

the abstraction is properly created? what happens if you connect with  
the manual mechanism at the right?

the abstraction is properly created since it's connected to outlets...

i get the same behavior on another mac intel :

no connection between the matrix~ object and the scripted abstraction, if the whole patch is an abstraction.

scripting specific objects