joelsquare

Has anyone else encountered really inconsistant results in being able to identify which Patcher File a bpatcher will read? I can usually build one proper bpatcher, and then have to quit and restart MAX/MSP to be able to build another. Does this make sense? I do nothing different, except retarting. Any thoughts as to what might be the problem?

What are peoples' favourite ways to save settings in complicated MAX set ups? I've found 'preset' pretty unreliable - I'm just learning 'pattr' and it's associated objects. WOndering if that's the preferred method?

Has anyone else encountered really inconsistant results in being able to identify which Patcher File a bpatcher will read?  I can usually build one proper bpatcher, and then have to quit and restart MAX/MSP to be able to build another.  Does this make sense?  I do nothing different, except retarting.  Any thoughts as to what might be the problem?

What are peoples' favourite ways to save settings in complicated MAX set ups?  I've found 'preset' pretty unreliable - I'm just learning 'pattr' and it's associated objects.  WOndering if that's the preferred method?

bpatcher-file-not-found-saving-set-ups

(Or you can really pull out the stops and save settings and data in 

an SQL database, but that's usually overkill.)

nick rothwell -- composition, systems, performance -- 

(Or you can really pull out the stops and save settings and data in  
an SQL database, but that's usually overkill.)

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


coll is my favorite external for restoring states. I tested the pattr family of objects and it seemed to restore the states of magnitudes of objects with a greater deal of latency compared to parsing out a coll accordingly, albeit the coll option requires you to build your own network and parsing mechanisms together. It is faster, though. pattr to me seems to be a short cut not worth taking.

coll is my favorite external for restoring states. I tested the pattr family of objects and it seemed to restore the states of magnitudes of objects with a greater deal of latency compared to parsing out a coll accordingly, albeit the coll option requires you to build your own network and parsing mechanisms together.  It is faster, though. pattr to me seems to be a short cut not worth taking.


> Has anyone else encountered really inconsistant results in being able

> to identify which Patcher File a bpatcher will read? I can usually

> build one proper bpatcher, and then have to quit and restart MAX/MSP

> to be able to build another. Does this make sense?

> Any thoughts as to what might be the problem?

Maybe you have several versions with the same name of the abstraction

> I'm just learning 'pattr' and it's associated objects. WOndering if

joelsquare wrote:
> Has anyone else encountered really inconsistant results in being able
>  to identify which Patcher File a bpatcher will read?  I can usually
>  build one proper bpatcher, and then have to quit and restart MAX/MSP
>  to be able to build another.  Does this make sense?

Maybe you have several versions with the same name of the abstraction
you load into bpatcher?

> I'm just learning 'pattr' and it's associated objects.  WOndering if
> that's the preferred method?

  [][]  [][][]  [][]  [][][]
[][][][][][][][][][][][][][][]

         Stefan Tiedje
         Klanggestalter
     Electronic Composition
               &
         Improvisation

            /~~~~~
     \   /|() ()|
     ))))) )|  |  |( \
     ///     _/)/ )))))
             ___/   ///

-------------------------x----
--_____-----------|-----------
--(_|_ ----|-----|-----()----
-- _|_)----|-----()-----------
----------()------------x-----

14, Av. Pr. Franklin Roosevelt,
94320 Thiais, France
Phone at CCMIX +33-1-57 42 91 09


> pattr to me seems to be a short cut not worth taking.

I do not agree, there are two speeds, speed of execution and speed of 

developement. The speed of execution of pattr compared to my MSP needs 

is a fraction of a peanut. Speed of development is the only issue that 

matters. You can't beat pattr even if you already created a coll based 

system with some man years of development time behind it.

Just my oppinion, stay happy with coll ;-)

bine~ wrote:
> pattr to me seems to be a short cut not worth taking. 

I do not agree, there are two speeds, speed of execution and speed of 
developement. The speed of execution of pattr compared to my MSP needs 
is a fraction of a peanut. Speed of development is the only issue that 
matters. You can't beat pattr even if you already created a coll based 
system with some man years of development time behind it.

Bpatcher file not found / saving set-ups