Jacques Boileau

I do not have the tempo view opened when I do my tests, but I have a tempo map derived from a live track so there are a lot of tempo changes. I have very little automation changes in this project, only a single track with one bypass to a plugin, IIRC. Things I have tried this morning, in this order, in light of your comments: Clear the tempo map. Set AutomationDecimatioMsec to 30, the maximum. Disabled automation read on all tracks and busses. Unfortunatly, no real changes after each of those. I can certainly make the project available to you on my Google drive. Is the .cwp all you need? I can PM you a link to it.

I did some tests this morning to see if I could quantify this a little more. I have tried it a few times betwen 2020.01 and 2020.04 EA using the rollback installer. I can now say for sure that I get a lot more dropouts with the EA. To try and show this I have increased DropoutMsec from 250 to 2500 msec so that playback wouldn't stop in EA. I then played 1m20s of my project in both 2021.01 and 2021.04 EA. Here are the results. The max engine load is not that much more in EA, but with this project it generates almost 45% more late buffers. At the default DropoutMsec of 250 msec, the project normally plays true, or at least for the most part, with crackle in 2020.01 and stops after a few seconds on EA. In case this might be seen differently: I give this as information if it could be helpful in anyway to the devs. It is not something I am complaining about. I am totally aware that this project is too complex, using plugings that are probably too cpu intensive pushing my PC to its limit. 2021.01 2021.04 EA

I may be experiencing some degardation with the EA. To try it out I decided to simply run my last project from last week. That project is a little on the heavy CPU usage on my DAW's PC. In 2020.01, it would play but it was starting to crackle a bit because of the heavy load, but it would play. Since that project was over, I was ok with that and didn't do anything to improve things. Now, to try 2020.04 EA I decided to simply open that project so I could look at the newest features (which are simply excellent btw!) and now when I press play, it barely plays for a couple of seconds and it stops on Audio Engine Dropout. I am pretty sure I haven't changed anything in the project. Is it possible, because of the new features, that the CPU load is increased somewhat even slightly and since my project was barely making it in 2020.01 it now does not have just enough CPU cycles to run? I have tried rebooting to make sure I was starting with a clean slate and it didn't help. I am of course running with a maximum buffer size of 1024 on my Scarlett 2i4. What I haven't tried yet is rollback the installation and double check that there really is a difference and didn't imagine anything. 🤥 Is it possible to have two versions of Cakewalk installed on the same machine to make this type of comparaison easier to do, instead of rolling back? Of course, we can't rule out that some Windows update creeped in an is the culprit... 🤨

I have transmitted this information and a link to this thread to Tim Shortle at SSL support. Thanks Noel!

New inserted plugins of the same type exhibit the problem too.

Thanks @Noel Borthwick. I am in contact with them and will post back results here from my inquiry when I get more feedback. I do agree that it does not seem to be Cakewalk related and I posted here mostly because this forum is so full of knowledgeable people. But the only thing that bothers me is that all instances stop working at the same time. Do different instances of a plugin share common code or memory that would explain that they would all stop working together? It would also mean that the two different plugin, channel strip, and bus compressor, would share common ressources. I am a software developer but I have no experience in VSTs. Are they a bit like DLLs and share common resources?

Thanks for the info, that helps! That probably means there is something in my installation that is causing the problem. Strange though that it is the only plugins that exhibit this behavior...

Good point! I just checked and my integrated Intel graphic driver is at the latest...

I don't use other DAWs at the moment since I am quite satisfied using Cakewalk. Thanks for the link to the SSL support desk. I couldn't find it myself. I'll send them the problem and see what they have to say.

The SSL Native 'Essentials Bundle' which includes: ChannelStrip and Bus Compressor. I have installed the latest version which is 6.5.

I use two SSL native plugins: the channel strip and bus compressor. After a while working on a project, all instances of both types of plugins' UI becomes unresponsive. The VU's do not show anything, compressor leds do not lit, etc. But I can still turn pots and hear the plugin doing its work. So it seems it's only the UI that is affected. But all instances on all tracks and buses exhibit the problem at the same time, so I guess it could be Cakewalk related. I have yet to pinpoint what maneuver I do in Cakewalk that triggers this behaviour unfortunately. For now, closing Cakewalk and reopening it solves the problem, albeit being annoying.

Worked fine for me, but it's not the first plugin I installed from them. The best way is to install their Aquarius app, login in it, open the 'Purchased' tab and you should see it there with the option to install it. Good luck! Btw, it is worth the effort...

Don't you know? Everything ancient comes back with a vengeance... I am looong due for a come back... 🤪 BTW, I am currently playing this game for the first time. My now adult son, told me I had to play this classic. After I had played it for a while and told him I was enjoy it, he said kinda proudly: "you know dad when I was skipping classes, failing school, gaming all the time and simply giving you a hard time? That's the game I was playing!" 😱 I wish he hadn't said that! 🤭

Select all the tracks you want grouped together and then hold the ctrl key while moving one of the volume slider.

Hi Robert, Great video! Always informative and well made. You talk about screensets, but not workspaces. Do you use screensets exclusively or do you use both of them for different scenarios?