I tried out the demo today. Maybe I was doing it wrong (although I doubt it), but all it was doing was driving up the cpu usage on both the slave machine AND my host machine. In fact CPU usage was about 3x normal on the host machine when compared to using the same effects on the same loop completely locally.

Not to mention the fact that I'd get CPU spikes every 3 bars or so, which makes for a cool effect, but wasn't something I wanted to hear.

Anyone have positive experience with it?

Did you press the button which optimizes the latency settings?

es

___________________

Don't take me too seriously.

quote:

Originally posted by Vert Did you press the button which optimizes the latency settings? es

Yep. It doesn't seem to be a network latency problem, it seems to be more of a "let's run inefficient versions of these plugins on both computers at once" kind of a problem.

quote:

Originally posted by Tranc3 Yep. It doesn't seem to be a network latency problem, it seems to be more of a "let's run inefficient versions of these plugins on both computers at once" kind of a problem.

When I did it, it didn't seem that bad, it was however slightly more buggy than using plugins normally.

es

___________________

Don't take me too seriously.

It runs best in Cubase. Has problems with FLStudio.

___________________

quote:

Originally posted by moth It runs best in Cubase. Has problems with FLStudio.

Strangely enough, that's what I use. I can't stand Fruity.

Have you thought about using V-Stack. It might be a little more stable running on Cubase considering it was made by Steinberg.

___________________
1 out of every 4 people in this country are mentally disturbed. Look at your 3 closest friends. If they seem okay, then you're the one.