I'm testing out FX-teleport as a way of hooking up my slave PCs (and maybe the Macs too, if/when the Mac version ever gets released), but I'm having a strange problem. I've applied the 3GB switch, and I'm using Bidule with the LAA patch by Laatido. Each machine, independently, seems fine -- I can load enough anyway to suggest that there's no problem with the 3GB switch. However, when I try to remotely load a template with 4 brass instruments and a big solo violin, it hangs Bidule on the client -- the client, not the server (where the VIs are actually being loaded). I've noticed that, when the hang happens, the latency readout in the FX-Teleport wrapper plugin in Bidule reads something crazy like 15000%. Of course, this may just be because it's hanging and trying to guage latency at the same time...
Anyway, has anybody had problems like this? I can't seem to find a way around it. The brief experience I've had with it is very impressive, but I really need to be able to maximize the RAM on all machines. Could it be too many instances? This template would be using 9 VI (LAN) plugins. Doesn't seem like a lot...
help!
J.
Anyway, has anybody had problems like this? I can't seem to find a way around it. The brief experience I've had with it is very impressive, but I really need to be able to maximize the RAM on all machines. Could it be too many instances? This template would be using 9 VI (LAN) plugins. Doesn't seem like a lot...
help!
J.