cpwade wrote:No, it's pretty straight forward. PT 11 has a 30 day demo and Blue Cat does as well, crippled but the idea is there. Might do a test to see what might need to be tweaked/ how your system reacts using a clone and the demos.

Thanks cpwade: I usually do that, on a cloned system. Let's see how it goes.

Thanks for the report tass, that wouldn't bother me much.

Is the delay compensation fine with Blue Cat Patch Works inside PT? In their website they say yes, just looking for a real world experience from the Nebula community. What buffer do you guys use with Nebula in this scenario?On C7 Im used to 8192, but, since PT compensates around 16k samples for channel I'll review some setting.

I run really low buffers, like 128, keep in mind that in PT you can open Nebula in Patch Works in Audio Suite and off line process all you want with Nebula. It's my secret weapon. We had a discussion here some weeks back, and both Blue Cat and Protoolsexpert.com freaked out and posted about it, not my imagination, it's powerful used that way. Really powerful.

cpwade wrote:keep in mind that in PT you can open Nebula in Patch Works in Audio Suite and off line process all you want with Nebula. It's my secret weapon. We had a discussion here some weeks back, and both Blue Cat and Protoolsexpert.com freaked out and posted about it, not my imagination, it's powerful used that way. Really powerful.

What?!?!? That's really amazing news! Thanks a lot for letting me know that. That's a no brainer for me a this point.

Is the "print" sample accurate with Nebula inside Blue Cat with AudioSuite?

Thanks cpwade: that's very good. In Cubase, and big projects with a lot of Nebula instances and latency, the exports are not always sample accurate. I didn't found out what triggers the problem yet, but this thing is driving me crazy, so much time lost on checking bounces.