In real life it is not so easy...
I made some more tests with a scenario i would like to use on live performances. So i added about 50 plugins and made a 8 CH in and out complex routing. All tests at 24/48 and all choosen plugins show in S1 0ms latency. I wanted not to use plugins > 0ms, to avoid an impact due to latency in plugins.
GigPerfomer: After adding the 50 plugins i had to increase the block size to minimum 128 samples to avoid drop outs. Now i have a cpu load of 80 % (shown in GigPerformer, not the real CPU load, this is about 10 %) and it is running well, but with an overall roundtrip of 5 ms recorded on the other MacBook. Still some crashes, but i think, that is one of my plugin, unfortunately i could not figure out which one.
Studio One ShowPage: The same setup, also some crashes (the same Plugin, i think), but in ShowPage i could leave the buffer size to 16 samples and it worked fine. I don't know why, but i had now a roundtrip of 4ms. Perhaps i made a mistake measuring the first time. No drop outs at this very low buffer size ( how do they do this?). CPU load shown in S1 about 50 %, at Mac about 20 %. It seems, that S1 need more CPU power, but it is 1 ms faster.
I think 4 (5) ms roundtrip should be acceptable for a live scenario, but first i must find the one plugin causes the crashes. Otherwise i am afraid to go live with this. And i will try to minimize the amount of plugins, to save CPU power. Some plugins are nice to have, so i will proof the need of every one.
Hope someone find this helpful.
Is there someone out there, who really works with ShowPage and can report from real life scenarios?