jeffburger

I've got jit.net.send and jit.net.recv successfully communicating in two separate patchers, but there's not when I put the routine with jit.net.recv in a standalone. (Only one machine... localhost, 127.0.0.1.) I don't see an address conflict in my code or in Terminal using the net command. No errors in Max window when compiling or running standalone.

Tracking this further, I put the C74 jit.net.recv help file in a standalone and get no communication from the jit.net.send help file running native in Max either. (In doing so, I made sure try to avoid port conflicts, setting jit.net.send in that help file to 7475 and jit.net.recv in that help file to 7475 as well.)

BTW, in my full program I'm using net.tcp.send and net.tcp.recv as well as jit.net.send and jit.net.recv, but using different ports. Would this be a problem as well... and if, so how to work around? (Again, I don't think it's the only thing causing difficulties here, since the simple Max help files alone give the same results when one is made standalone.)

Max 6.1.3 on MacPro w/ OS 10.6.8, 8GB RAM

Any help is gratefully appreciated! Thanks!

Tracking this further, I put the C74 jit.net.recv help file in a standalone and get no communication from the jit.net.send help file running native in Max either. (In doing so, I made sure try to avoid port conflicts, setting jit.net.send in that help file to 7475 and jit.net.recv in that help file to 7475 as well.) 

problem-with-jit-net-send-and-jit-net-recv-in-standalone

there are extra files you need to include in the contents of the .app package when using jitter-- are you including these?

there are extra files you need to include in the contents of the .app package when using jitter-- are you including these?
(this is just a guess)


Thanks. I had that thought too, but 1) the other Jitter components seem to work without manually including any other files and 2) I've tried dragging the jitter-external folders into the standalone's support folder as well... no change.

Now the standalone gives me "corrupt data" errors for jit.net.recv. More troubleshooting test data:

To avoid the possibility of multiple jit.net.recv object conflicts, I split the jit.net.send maxhelp file into two test files... one with jit.net.send portion and one with jit.net.recv portion. These two patchers work fine together in Max. Made a Mac standalone from the stripped-down jit.net.recv. Manually copy jitter-externals folder and java folder into standalone's Contents/support folder. (Even if java may not be necessary for this, I need it anyway in my actual app.) Rebooted Max to clear. Relaunched Max and ran stripped-down jit.net.send maxhelp patcher (no recv), then launched the standalone with stripped-down jit.net.recv (no send). When ports match, standalone gives "corrupt data" errors for jit.net.recv.

Now the standalone gives me "corrupt data" errors for jit.net.recv. More troubleshooting test data: 

Problem with jit.net.send and jit.net.recv in standalone