minminmusic

Thank you...that did the trick!!! And I guess the first option takes care of the fact that (drove me nuts) that if I hid a track in the Track View that I'd have to go over and hide it in the Console View?

So...I have 3 Icon P1 Units. I recently when through Track Manager and hid a bunch of tracks of archived/not being used tracks in both Track View and Console View. They are still showing up within my controllers through. Is this a bug or a limitation of the MMC protocol? It's doing this in both CbB and Sonar. :(

I think you may have hit one issue on the head that I've noticed with my system. I have Process Lasso enabled on with an update it looks like it turned on Pro Balanced Enabled (which I think should be off for audio machines?) and I also noticed that core parking was on. I disabled both and the machine seems to be doing better and less fan throttling as well. Still haven't tried to re-enable MCompressor thought yet...been busy today.

Yeah...Safe Mode needs an overhall. It should ask you those questions in some kind of order that makes sense or provide additional info in a specific order. Such as Track 1 - Kick Drum: EQ, Track 1 - Kick Drum: UA 1176, Track 2 - Snare: Sonitus Gate etc. That would be much more meaningful. Right now...it appears random though I think it's based somewhat on the historical order the plug-ins were loaded.

RME Fireface 800. Has worked like a beast for well over 15 years. Also have an Apollo 8p but not as my main interface. System drivers are the ASIO RME drivers...again beasts. Running 24bit and 44.1. This Cakewalk project has been a little glitchy as I've been working on it over the last year (with both my old system and new one...band members live internationally so it's a little slow getting work done.) Now...the only thing I can think of off hand I'm running the graphics off of the CPU. As I'm in deep in the UA waters, there's not a lot of motherboards with ample PCIe slots anymore. I went with the ASUS Tuf Gaming z790. Now...if I got rid of one of my Quad UA cards and upgraded that to a Octo it would free up a slot and I wouldn't loose any UA power...but as I'm not a gamer, would prefer something that is solid enough for an audio system, maybe put less stress on the CPU but not generate enough heat to add to the 14900k woes. Just wish it was easier to debug who's the culprit plugin wise as I could try and find alternatives.

I suspect it might be MCompressor as I was using it in sidechain mode on the master buss (to get a little pump in the junk). Looks like once I turned it off it calmed down a little. Have CbB open right now which I don't think has the "hover" option. I'll check in Sonar in a sec. Thanks for the suggestion!!!

So...recent i9-14900k build. Overall been running great however I'm working on one project where I'm getting crackling in CbB. Most recent Sonar is less so but still intermittently there as well. Was not having this issue on the previous machine but also multiple new plug-ins were added after the machine transition. Is there any way to determine where/who the bottleneck culprit is without removing everything and starting over. I know sometimes it can be one specific plugin that's not playing nicely. Other times it could be the order of plugins. One project with double the amount of files plays fine...one with less and I'm getting crackles. Any thoughts/approaches?

Can now log into Bandlab both in the forum and within the App. Still getting the spinning ball and if I click on the screen it goes white and with no responsiveness so will have to get that sorted.

Also couldn't get into the forum...with Firefox I was getting that 406 error. Installed Chrome and got an error message that they were updating their API(?). Can't be 100% sure as I uninstalled Chrome once I saw both were having issues.

Same here. Just did a system cloning to a new system. Everything worked for the first two days and today it's all gone to the toiler with the above error, not being able to get into Sonar. I can kinda get into CbB but having issues there as well. Again...first two days after cloning it was working pretty smoothly.

Let's say for Waves...they offer all those options. If I was trying to clean up and declutter my menus...which would be the preferred versions to Enable or Disable? If I just stayed with the Stereo versions...what would happen if I placed that on a mono track? I'm trying to declutter my life...

Paid for v3 (after owning v2 a number of years ago) and have gotten no response from the creator. Any one else had any luck?

The attached setup seemed to fix the lagginess and all tracks on all three units are showing up correctly. Not totally sure if this is the correct way OR that there's benefits/differences between the Mackie Control driver or the MMcL. Regardless with both, unless Cakewalk has no way of sending this data, I wish some of the limited tweakability of the "DrivenByMoss" Reaper and Bitwig driver could be added to Cakewalk. Realize their limits in the MCU protocol but squeezing the little but extra out of what's available is always nice.

For reference on how it's currently set up.

This is a follow-up to my earlier post on the iCON P1 controllers. I thought I got things fixed but, while the 3 iCON controllers are displaying the the track order correctly and are banking...something about adding this 3rd controller and having to fiddle with things has made the display timecode counter on the P1-M extremely laggy. Previously, I had the P1-M (main unit) on MMcL Mackie Control #1 and the P1-X extender on MMcL Mackie Control XT #1. Everything worked well. Adding the additional P1-X, I thought it would be routed to the MMcL Mackie Control XT #2 but could not get it to pick up. Now...I have all 3 routed with MMcL Mackie Control #1 (using the correct midi routing). LIke I said, as far as I can tell this setup is working except for the extreme lagginess on the timecode bar. I also have the P1 series mapped to LUNA and Reaper and the timecode is working fine there. If it's a 24 track project and I want the P1-X1 to be assigned to tracks 1-8, P1-X2 to 9-16 and the P1-M to 17 through 24...which is the nest configuration to use within the Control Surfaces menu? I've generally set it up in the order in the Control Surfaces menu...not because I think it's needed that way (if it's routed correctly) but from an organizational standpoint it makes more sense to my lizard brain.