Tommy Byrnes

Thanks, Azlow. I don't think I"ve had any major plugin changes. A few new ones from Plugin Alliance and one from FabFilter, neither of which have caused issues in the past. The temp starts to spike as soon as I open CbB.

I don't use 3. I have to switch between 0, 1 and 2

Yes, that's what I mean. I have to go into the config and change the model. I'm on the 2020.05 EA release

Scook, I started noticing this after the March update. I'm running the May Early Release because I hoped it would fix this. Nope. As I said in the OP since then the thread scheduling needs to be changed just about every time I open CbB.

This is a new problem and has nothing to do with my rig. The computer only does this with Cakewalk. No problems in Mixbus, no abnormal temps when doing graphics work or any other program. I get a safety shutdown at 71C. Done it twice today so I'm dead in the water until I find out why only Cakewalk is doing this.

Bob, I am not overclocked, as I said, my system is liquid-cooled and my system is fine tuned. No park control, highest power plan, etc. The issue is not with the temps under normal usage. It's a problem I have with CbB. I'm pretty computer-savvy and I've troubleshot as many things as I can.

I realize 40 isn't that hot-but my CPU thermal threshold is 61 as per the AMD specs for my processor. CbB will push it well into the mid-60s. That's where it starts to get dicey. The system shuts down at 70. It scared the hell out of me this morning when it did that. Good point about the stress test, although I've never had this problem before and my rig is in good shape.

Hi folks, I'm having a weird problem with Cakewalk since the March update and I thought I would see if anyone has any ideas about why this is happening. I was hoping the latest update might have fixed my problem but no dice. I have noticed that my CPU is running crazy hot, much hotter than normal, when using CbB. There is no temp rise when I use any other program. In a typical project I am running at less than 50% usage and the audio engine never gets above 65% and no late buffers. When I kill the audio engine the temp goes dramatically down. My system is liquid-cooled and usually runs in the low 30s C under normal and even moderate to heavy usage never gets above the low 40s.. As soon as I start CbB the temp starts to go up well into the 40s with no project loaded. I also have noted that I have to keep switching between different thread scheduling modes. When I open a project I find in almost all instances the first thread maxes out which facilitates a mode switch. Afterward, the threads seem to re-balance out. The temp also seems to go up when more tracks are visible in the console view. If I hide the meters it saves a few degrees, temp-wise. All this is making mixing a real pain. I have to constantly monitor the temps and stop frequently to let the heat dissipate. It auto shut down from thermal protection this morning, which I have never had happen before. Thanks for any insight you may have. I am completely vexed by this!! Cheers, Tommy

I agree. It's very good. I picked it up when it was a freebie awhile back (Black Friday giveaway?) and it's the first DS I reach for.

I just replaced the fans in my control room rig case with Noctua fans and they are quiet!!! Their color scheme is kinda groovy

Thanks, Noel and all the Bakers!!! This was a great update.

Peter, I toggled between both phase settings and I was very precise with measuring as well. I have not worked with ARC 3 for more than an hour or so under mixing conditions so I'll definitely give it more of a test over the next couple of days. That was my initial findings. One thing I will say is taking measurements in ARC 3, while easier than it was previously is still nowhere as easy as System 4.

I installed ARC 3 this morning and ran the measurement software to set up multiple monitors. Initial (very initial) tests vs Sonarworks System 4 have me feeling the correction for ARC 3 sounds very similar to ARC 2.5. I was hoping it would tighten up the low-midrange smear I get in the control room. It doesn't do as good a job as Sonarworks. Much clearer definition in the low end. Bass sounds more articulate. My mixes have translated well with System 4 for several years now and I am more confident with my mix decisions since deciding to use it instead of ARC 2.5. I'll run some test mixes with both and see how they translate. The other thing is if you use T-Racks for mastering it won't load the new ARC 3. Only ARC 2.5. I think they need to address that.

This is a great update. I've used the arranger all morning and it's definitely got its uses. Being able to save Pro Channel presets is really helpful as well. Been hitting it hard for 5+ hours without a hiccup. Thank you Noel and all the bakers. This cake is yummy!

Wow!!

Hi all, Is there a way to take a global snapshot of multiple parameters? For example, I want to set the levels of multiple faders and take a snapshot so they all snap at the same time. I can set each one individually but it's pretty time consuming. The Quick Group does not work for this, it seems. Am I missing something? I'm trying to learn some new things about CbB after, like, 13 years of using Sonar/CbB every day in the studio. Snapshots is one I've never messed around with. Thanks a mil for the help. Stay safe, folks!! Cheers, Tommy

I love this plugin!!! I always have a Room Verb bus and this is now on it at all times. It really is quite amazing.

I got this when it first came out because the concept intrigued me and it killed my CPU and was basically unusable. Then they updated it so there was a "light" version and though better, was still too resource-hungry to find its way onto any project. It's one of the only plugins I've ever bought that truly disappointed me. Just my two cents.

Thanks, Peter, I did just that yesterday. It sounds really good!!

How is the CPU hit on this?

I got the same deal. I like version 1 so I grabbed it.

I bought the M2 a month ago for a portable interface and it's pretty amazing.

My son is the lead 3D and virtual artist for a game company and he uses Blender every day. He uses it to do all the heavy lifting.

Sorry about the delay in my response, Noel. I see the formal release is ready. My MIDI buffer size is 128. I bumped it up from 64

As soon as I installed the Early Access I immediately started having trouble with MIDI. There is a lot of stuttering and a ton of latency. It takes several seconds for the program to update MIDI information. If I move a fader on my control surface (X-Touch) of start or stop transport it takes a long while to make the corresponding move in CbB. I'm in the middle of a big client project so I uninstalled the EA version and re-installed the previous. Any ideas as to why this is happening?