183,266 users have contributed to 42,288 threads and 255,034 posts.
In the past 24 hours, we have 4 new thread(s), 16 new post(s) and 51 new user(s).
It seems its actually a Kontact 5.3 issue having spoken to Orchestral tools , because it is mainly the Berlin Exp winds that cause the crackles.( they claim v5.2 is ok ) no activiity in Kontakt Disk meter but the odd spike in cpu .
Having said that sounds like you are right about cubase and windows , goddamit . Wish I had known before buying the mac .
yeah, i'm in the same boat. but on a mac pro 2009. Demoing Cubase 7.5 now ,and i have to say, it is much more organized than logic x. Logic X makes me think that it's another facelift of the same old program, with the same old problems. Even with huge update list for 10.0.7 it seems like they're still patching the old core (like the CC7/CC10 preference setting) It's a mess. Once you use Cubase your brain takes a rest and concentrates on music instead of jumping thru the software hoops . Good luck!
+1 for cubase , I agree 100% . Apple have screwed up logic x , cant stand to even look at it after 30 years . Have started on cubase which is not a massive learning curve and will switch despite being mid series. However that doesnt help my crackle issues because I am only using the daw for midi .
Well, I see you're using a standalone via the IAC. I think that is not going to perform as well as the server without that extraneous moving part, using a low-latency audio interface on the DAW end.
I don't get why you believe that a single instance of the standalone is that much more convenient than a single instance of the decoupled server.
One expectation you have is based here, you want to have every known thing all loaded at once and low latency. "Makes life easier", evidently not, you are having issues that could be managed better. You have something in mind that doesn't seem to be working so maybe you need to adjust to your situation some. The server is what's made for low latency DAW work. It should perform a lot better than just plugging instruments into a DAW. Although I have not used it with Logic.
With the machine in my signature, Cubase 5.5.3, I don't have crackles at 512 in the buffer with 'not a lot going on'. I start projects often at 128 and latency I can do drums by, or even 64, and add latency as the project's demands grow organically, as the load grows. Horses for courses.
Cubase is definitely lower latency on windows. I bought Logic and DP behind this [Cubase/Core Audio] latency problem but for me VE Pro has obviated any need to use those hosts.
The reason I use standalone is so that I can route all the outputs via adat to another computer which runs protools . It is like having a virtual mixing desk . I can then just press record in protools and all my midi is stemmed in one pass ready for mixing . The beatuy is then I can mix a whole tv episode or movie in one protools session and the cues only have to be mixed once moreor less in terms of applying plug ins etc . ie The celeste always comes out of the same audio chanel rather than loading a seperate logic song for each cue and having to reapply settings. When you have to mix 30/40 cues per episdode evry two weeks it all helps . Mixing that anount of midi in logic can take forever.
I could work in server mode and reroute everything back to logic and then out again but its more messy ( especially the way logics mixer now works) . In terms of workflow I seemed to have found the culprit in Berlin winds exp so as long as I use them sparingly until Kontakt is fixed all is well and I can have a massive template at 256 with no issues. Having said that , seems like a pc with cubase is the way to go .
Very good news , Mac osx 10.9.3 has fixed the crackling issues . I can now play berlin WW exp on Ve pro 5 standalone without issues ar 256 in a large template .
great news! so you use cubase with ve pro ensemble standalone and iac ports? how many instances do you manage to run and what is your memory footprint?
Well, I definitely feel you on the Logic thing, it's pretty convoluted to use VE Pro and Logic. I use VE Pro to mix, Cubase is just a waystation for me mostly in terms of printing the end result. I don't know how it could be a lot worse using Cubase in OSX than that latency, although for straight plugins, one at a time Logic should be far faster (than Cubase, not than a VE Pro situation*).
Interesting that 9.3 addressed this. * I'm fairly confident your IAC->standalone is not the best use though. Yet, 256 in a large template is quite good I think, all things considered.
Actually I haven't made complete switch yet and I'm using Logic 10.0 .7 but just for MIDI so it shouldn't make any difference Cubase or not. I have 32 GB of RAM loaded so far in vepro standalone in one computer at 256 buffer with about 20 kontakts and a few Vienna instruments .
I would be interested to know if there is an alternative to IAC bus that has less latency or jitter ( apart from Ve pros own midi input which is only for server use)
I had something much larger in mind with 'large'. but that's kind of comparable more or less with me using Cubase in Snow Leopard and VE Pro servers.@molemac_824 said:
in vepro standalone in one computer at 256 buffer with about 20 kontakts and a few Vienna instruments