lists@lowfrequency.or

standalone-errors

I should have also said that all of the "no such file in collective" 

errors happen when javascript tries to attach any max objects, like 

the "r" (receive), and VSurface patch. And the VSurface contains one 

each of the jit.submatrix, and jit.gl.texture objects. So I see 

where the errors are coming from, but not how to solve them. Trying 

to copy the VSurface.pat file in the collective itself didn't help, 

I should have also said that all of the "no such file in collective"  
errors happen when javascript tries to attach any max objects, like  
the "r" (receive), and VSurface patch.  And the VSurface contains one  
each of the jit.submatrix, and jit.gl.texture objects.  So I see  
where the errors are coming from, but not how to solve them.  Trying  
to copy the VSurface.pat file in the collective itself didn't help,  
either.


1. patches loaded from JS are not known about from the collective 

builder, so you need to add *all* externs you need to your 

application support folder. this is because the parent patches have 

no notion of what JS does dynamically (unlike ordinary subpatchers 

whcih of course work with collective building)

2. CG.framework and all shaders need to be manually added to your 

your support folder as documented in Appendix D of the latest Jitter 

Manual (provided in the Jitter 1.5.2 download)

Your easiest solution would be just to copy the entire Cycling '74 

folder and your patches folder to your standalone support. Of course 

you can eliminate anything you don't need, but this should have at 

1. patches loaded from JS are not known about from the collective  
builder, so you need to add *all* externs you need to your  
application support folder. this is because the parent patches have  
no notion of what JS does dynamically (unlike ordinary subpatchers  
whcih of course work with collective building)

2. CG.framework and all shaders need to be manually added to your  
your support folder as documented in Appendix D of the latest Jitter  
Manual (provided in the Jitter 1.5.2 download)

Your easiest solution would be just to copy the entire Cycling '74  
folder and your patches folder to your standalone support. Of course  
you can eliminate anything you don't need, but this should have at  
least everything you require.

It helps get rid of the jit.* errors I was seeing, but not the 

"error: receive: no such file in collective". I tried adding a 

random receive object to my patch, but that doesn't fix the error. 

As far as I can tell, there isn't a receive external that I can 

Also, adding my patches to the Contents/MacOS/support folder does not 

make them visible to javascript. Even after including the patches 

via the build script, adding an instance of them to the main patch, 

and after manually copying them to the support folder, I still 

receive "error: XXX: file not found in collective" where XXX is the 

name of the patch I want to have javascript attach.

It helps get rid of the jit.* errors I was seeing, but not the  
"error: receive: no such file in collective".  I tried adding a  
random receive object to my patch, but that doesn't fix the error.   
As far as I can tell, there isn't a receive external that I can  
include, it's built in to max, right?

Also, adding my patches to the Contents/MacOS/support folder does not  
make them visible to javascript.  Even after including the patches  
via the build script, adding an instance of them to the main patch,  
and after manually copying them to the support folder, I still  
receive "error: XXX: file not found in collective" where XXX is the  
name of the patch I want to have javascript attach.

So I got my app working. Thanks for the tips, they did come in 

handy. I ran a bunch of tests of different combinations of including/ 

excluding subpatches and objects, and it seems to only work if I 

include the patch that I want javascript to attach plus all of the 

jit.* and max objects in that patch, using the collective editor. 

But it still lists a whole host of errors in the max window, which is 

what threw me off before. I can hide the max window, but having it 

generate 96 error messages (I need to attach at least 96 copies of 

the same subpatch via javascript) doesn't look good, even if the app 

So I got my app working.  Thanks for the tips, they did come in  
handy.  I ran a bunch of tests of different combinations of including/ 
excluding subpatches and objects, and it seems to only work if I  
include the patch that I want javascript to attach plus all of the  
jit.* and max objects in that patch, using the collective editor.   
But it still lists a whole host of errors in the max window, which is  
what threw me off before.  I can hide the max window, but having it  
generate 96 error messages (I need to attach at least 96 copies of  
the same subpatch via javascript) doesn't look good, even if the app  
works properly.

standalone errors