Okay, I just had what might be a really stupid idea... but maybe not.
For all you > 4GB RAM, G5 or Mac Pro guys, I wonder if it would be possible to access another whack of RAM by having another account running in the background via fast user switching? The processes should be totally independent memory-wise, and can, at least theoretically, continue to run for all users. And if a user who doen't have screen access (i.e., a "background" account) can receive email, then the network must be running, so I'm guessing you could pass midi/audio over TCP, which is generally fast enough locally. I haven't got enough RAM to really need it, but if anybody has a 6 or 8 GB RAM Mac Pro, or something similar, it might be worth a try. Bidule as the "remote" host, Wormhole2 for audio, MIDI Over Lan for midi... maybe?
J.
ps - I realize that fast user switching requires much more overhead to run, and that this isn't a very memory-efficient way of doing things. But it's a thought.
For all you > 4GB RAM, G5 or Mac Pro guys, I wonder if it would be possible to access another whack of RAM by having another account running in the background via fast user switching? The processes should be totally independent memory-wise, and can, at least theoretically, continue to run for all users. And if a user who doen't have screen access (i.e., a "background" account) can receive email, then the network must be running, so I'm guessing you could pass midi/audio over TCP, which is generally fast enough locally. I haven't got enough RAM to really need it, but if anybody has a 6 or 8 GB RAM Mac Pro, or something similar, it might be worth a try. Bidule as the "remote" host, Wormhole2 for audio, MIDI Over Lan for midi... maybe?
J.
ps - I realize that fast user switching requires much more overhead to run, and that this isn't a very memory-efficient way of doing things. But it's a thought.