am i right in guessing you're not quite ready for sending OSC messages across a LAN using self made pluggo plugs ?
if you're using logic, then that makes your situation more difficult, but answering the question a little easier. logic is going to have to use midi to talk to the two patches in the two computers. as far as the communication goes, that's very easy, using ctlin or midin in with both patches.
however, you said tight, and here you stumble upon some problems that you don't have with the usual sequencer/softsynth programmes. the timing of Max's highest priority non-audio thread is not that good,indeed it's sometimes apalling. this, however is where your midi sync signal lives once it has entered your programme.
what do the patches on the two machines do ? if they're not doing much audio, or the midi part of the programme (and everything that is dependant on it !) is no too complex, you may find running the thread in audio interrupt (see dsp status under the options menu) helps. this seems to depend on so many things that it appears rather esoteric to me, and i've never been able to get good results that way, but it gets recommended often on this list, so i assume that some must get lucky - or know enough to make it work :-)
post a bit more information about what you are doing and what your setup needs to do.
the mxj.maxhole plugin looks interesting, so that works tighter than midi triggering? the tightness is very important to me. i can build plugins no problem if thats the right way
i dont have the second computer yet, so i obviously need to experiment, but the basic idea is to use logic to sequence chunks of audio created by 2 or more fairly large MSP patches, a synth, and a samplemangling thing. i just cant get them both to work together on the one machine, gets too complicated, and CPU gets too high. ideally, i'd have the audio from the slave computer routed back into the first computer. i believe theres a plugin called wormhole www.plasq.com/wormhole that does this, though i've heard various reports about usability.
several people have told me simple midi triggering works pretty well, though it seems a waste of space to have 2 midi boxes
well, i think network is the fastest short of triggering thru a digital audio cable at audiorate, which might be a bit overkill in most situations !
(it's still my preffered way of getting stable sync between computers, actually it's as good as just using one computer ;)
I think the OSC plugin has bigger potential than mxj, on the other hand,- it's a lot harder...
OSC is standart, so you could make a textfild to type target messages and make a plugmultiparam remember the symbols. Then you would be able to use it with more than max - i.e. Supercollider, Reaktor, Bidule, or whatever OSC ready app you might like...
[mxj net.maxhole], is a easy es eating cake, but it will only work with max, and only with stuff you built... but that might be what you wan't anyway....
i just tried some experiments with linking my powerboog g4 to a 400 Mhz imac g3. the mxj net.maxhole object gives pretty good timing if i only use max msp, but its pretty lousy if i build a plug in and use logic. its also bad timing if i use rewire to send midi to max msp on the same machine, and then relay it to the other machine.
if i use a regular midi cable the timing is pretty good and more stable than with the network connection, which tends to stutter alot if i do something like move a window around. if i have a rewire audio channel in logic playing the same thing on my powerbook as on the imac, the rewire channel is actually about 10ms behind the remote imac.
however theres some wierd mistiming over the first couple of seconds of play, where logic seems to send out the beats a bit too slow then catches up
what i am doing is playing a sequence of midi notes into mxj net.maxhole, which ive put inside a pluggo plugin. then i'm receiving them on the remote computer thru same object. i want to use the remote computer to run a synth patch. i'm not sure how plugsync would help in this case, especially becaues its so flaky.
i'm interested that some people say an ethernet connection can give better timing than a midi cable and two usb /midi interfaces. from my experiments the opposite is true, midi seems far more stable and better timing
has anyone tried synching computers using other sequencers like live or cubase? i'm getting tired of logic's strange behaviours
the communication from max msp to max msp on the other machine is good over the ethernet . its just when i use logic to throw evnts down the maxhole, the timing gets all wobbly, even though they sound like they are being sent into the maxhole with good timing.
if i use a plugin its just
i mean synching as in, i want my synth part on the second machine to be played in time with my , say, percussion part on the first machine. at the moment its sounds rather wobbly on the second machine. i want usable well timed midi type information to get to my second machine. it has to be tight, cause im doing razor editing on stuff.
the problem on my second machine sounds like the ethernet information isnt gettinbg very high priority, like its totally disrupted by moving windows around the screen...my imac is only 400mhz though
i just tried the same thing using abelton live, it seems to have almost no latency with maxhole, but the timing is wobbly. midi has a 16ms latency but the timing is much better. theres no wierd slowing down when i start the transport either, like with logic......considering switching to live
I use OSC to send events between two computers (pc and mac combinations included) to Max from a) logic and b) a custom built sequencer. This works perfect with the custom built sequencer (done in Java) with latencies under 2 ms when the computers are linked with a cross cable. Logic timing (from inside a pluggo) is very unreliable (timing can differ around 100 ms) even when working on one computer.