Jump to content

Mannymac

Members
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

23 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes exactly thats what I found. Sorry I dont quite understand what you are saying here in regards to your test? to make the test worthwile you would need 15 bussess, eah with a track routed to it with the delay plugin compared to 15 single tracks delay inserted directly. Did you create 15 bussess or routed 15 tracks into one buss?
  2. Tried that yes and had no sgnificant effect on engine load in my session. :)
  3. Every machine is different as you can see by the replies here so take everything I say with a grain of salt and based on my experience but: CPU load is the same...what is changing is the engine load (different thing!) My engine load is way less when running it through Audio Gridder leading me to be able to mix at lower buffer in ASIO and lower latency.
  4. Thats what I thought initially . But the bottleneck is not my machine it's the engine load in Cakewalk. As I said I can run the same plugin chains with the exact same routing in other DAW's just fine. I can even run the same chains in Cakewalk if they are on tracks not Busses. The problem is the engine load on Busses in Cakewalk. As to why that is? No idea. I found out quite a while ago that with modern CPU's the bottleneck is the CPU no longer. My session only uses 20% of my CPU but the engine load within Cakewalk is about 95-110% (past 100% is where the glitches come) at 512 Buffer. That is where Reaper outperforms Cakewalk by quite a margin in my particular case. Or in Cakewalk's own words: "The Engine Load value is a percentage of the total time the engine took to process an audio buffer. If it takes 100% or more of the allotted time, the buffer is processed too late and it will result in audio glitches/distortion." When I run my buss chain of about 6 plugins on two busses so 12 in total via Audio Gridder I have 65% engine load at 128 buffer. So it performs faster and more stable that way. I am a happy camper with that. I am using an RME ADI-2 Pro FS R as my interface, latest BIOS, no other programmes running, WIFI swiched off, latest driver for everything and an SSD. Given their excellent ASIO drivers I can say with a degree of certainty that won't be the problem either. And again, exact same plugins on stereo tracks run just fine. Whatever Cakewalk does on Busses compared to tracks seems to place a higher load on the engine. But that is beyond my paygrade. Cakewalk is the best DAW I ever used so I'm just glad I was able to solve this. I am no programmer so I have no idea if that is even possible but maybe there are ways to improve the way the engine handles Buss plugins. It seems I'm not the only one struggling with this so maybe an area for exploration for the bakers? But then again, I know bugger all about programming. As always, it might just be that certain plugins don't like being on a Cakewalk Buss at which point there is nothing they can do and it is a compatibility issue. PS: If Noel or any of the bakers want my session to check I'll happily pass it along.
  5. For professional Audio production you need an Interface with an ASIO Driver. Even a Scarlett solo will do: https://www.amazon.co.uk/Focusrite-Scarlett-Solo-Audio-Interface/dp/B07QR6Z1JB/ref=asc_df_B07QR6Z1JB/?tag=googshopuk-21&linkCode=df0&hvadid=344379515881&hvpos=&hvnetw=g&hvrand=5390826151476857481&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=1006886&hvtargid=pla-781084951088&psc=1&th=1&psc=1
  6. For anybody interested in this, I found a solution! Thanks to the new engine meter in Cakewalk (thanks for that devs!) I was able to pinpoint exactly the issue. It is that Cakewalk is really not the best (worse than Reaper and to a lesser degree Pro Tools in my tests with sessions I ported over) with longer Plugin Chains on Busses/Auxes. I dont know why that is but certain plugins place a higher load on the engine when on a buss compared to a stereo track. Zynaptiq Intensity for example added only 1,5% engine load to my session on a stereo track but a whooping 10% to the engine load when on a Buss. Similar story with other Multiband Processors or especially Acustica Audio plugins. Anyway, the solution for me is to just use Audio Gridder running as a "server" on the same machine (https://audiogridder.com/) to load chains on busses instead of inserting them directly into Cakewalk. That way I can now run a fairly heavy project at 256 Buffer with my RME ADI-2 Pro FS R without dropouts and an engine load at 50%! Fantastic! To do this install the Audo Gridder Server app and the plugin on the same machine. Start the Server App, then insert the plugin on your buss. Do a scan, load all your plugins in this wrapper et voila. Any negligible increase in latency by Audio Gridder is actually offset by me being able to have my buffer so low. So I have less engine load, and less latency! Cakewalk is my favourite DAW and I was really trying everything to be able to keep using it instead of REAPER. @Noel: Can you comment on why the engine load is different for a plugin on a buss compared to it on a track?
  7. New plugin menu is fantastic! Well done guys, a joy to use.
  8. Does anyone else have the problem that with the new NX Ocean way the headtracking app does not communicate with the VST? The other two NX versions (Regular NX and Abbey Road) work just fine.
  9. Seeing reall improvements in terms of engine session load in a heavy project with those latest improvements! Well done guys, I'm really grateful. If you were to ever add some adaptive CPU load processing like REAPER has I'd be in dream land.
  10. Now there is only Honey left if anybody wants the Harrison emulation, then please send me a PM:)
  11. Hi Noel, That would be a trade off I am happy to have in mixing Could be especially useful at higher sample rates. I am getting more and more of these sessions for blu ray audio. As an aside for further thought: Limitiing to 16 cores only brought benefits at 96khz. At 48 the performance is worse. Very interesting. My guess is there is some RAM/CPU communications going on here which Ryzen based systems seem to be very sensitive to.
  12. Indeed very interesting. Big thank you to you that you allows us to go into the engine that deep. I am afraid I dont know exactly what is going on there. I do have a lot of Scustica plugins so maybe limiting the cores forces them the to "stay in one lane"? If you want I can send my session to you if you want to analyse it. Also since you are here: Is it ever possible ti implement into Cakewalk something like a lookahead" processing liek Reaper has? For isntance my engine load is 90% but my CPU load only 20 so there are reserves if they could be adressed. Thats at 96khz with a 4096 buffer.
  13. Through experimentation I found a potential tweak for high thread count Ryzen CPUs such as my Ryzen 3950x. This tweak made a session run without crackles at 90% engine load compared to having crackles at 90% engine load. The tweak is setting the mix thread count in the config file to your actual cores in your CPU, not your logical ones. My Ryzen 3950x has 16 "real" cores/ 32 logical ones. Go into the config file under settings and set the max thread count to your real cores, in my case 16 and set the thread scheduling model to 2. Et voila! Let me know if this improves things for you.
  14. Hi folks, Acustica Audio has now enabled a license transfer feature where licenses can exchanged/sold among users. In true black Friday fashion I am selling some of my plugins listed below for 30 dollars In brackets is what they emulate. if you take more than one the others are half price, so 15 each. If you take them all you can have them for 60 USD . For an even more detailled look please check the Acustica emulations list: https://justpaste.it/AcusticaAudioAcquaMasterList Scarlett (Sontec) Aquamarine (Shadow Hills) Honey (Harrison) Lemon (Delay collection) Orange (Orban 627) If you want these get in touch
×
×
  • Create New...