Trying to sync 2 macs using a power mac g5 as the slave and a powerbook g4 as the master through OSX network midi setup.
The g5 is connected to the network via ethernet, and the g4 via airport. Both machines running 10.4
g5 is running live 5.03, and the powerbook running live 4. The g5 is using an m-audio quattro with the latest drivers installed and the g4 is using internal sound.
In testing this the g5 was receiving midi from the powerbook. As soon as the powerbook started to play the g5 would follow, but experienced massive cpu spikes. The status bar stayed buried at the top on the g5, with the meter fluctuating wildly from a minimum of 175% all the way up to 1200%. This is in a completely empty ableton set.
This screenshot shows my network midi setup window and my live window with a spike in the neighborhood of 396%. The powerbook running live 4 as master was fine. Again, the spikes on the g5 started as soon as the master machine started running, and never dropped below 175%. The g5 would return to normal when sync was disabled. Re-enabling sync would bring back the spikes.
My question is, is this an osx problem, a live 5 problem or both? Or is this a problem with the way I have this setup? Has anyone else experienced this? If anyone else is using the network midi setup successfully can you tell me what I am doing wrong.
Also, on the first try live crashed on the g5, so I should be able to provide a crash log if necessary. After the second try live did not crash, but we gave up.
massive cpu spikes with OSX network midi setup
I didn't find the actual setup to be very troublesome, but the results were horrifying.hambone1 wrote:I just use two simple MIDI interfaces instead. Tried and tested, simple, and no problems at all.
For what its worth I totally agree with you hambone. But, that does not change the fact that it should work, and spikes reaching up to 1200% (I didn't think that was possible) are outlandish.