Jump to content

Jacques Boileau

Members
  • Content Count

    196
  • Joined

  • Last visited

Posts posted by Jacques Boileau


  1. I don't know if that has been stated.

    Problem: If you have made a workspace of your own, when switching to it after you have have used the tempo workspace will leave the tempo track opened as big as it is in the tempo workspace.

    Solution: Saving your workspace, with the tempo track closed or at least to the size you want in 2021.04 EA fixes this. After saving, your workspace will open correctly. 


  2. 14 hours ago, Noel Borthwick said:

    Are you using the new tempo view or do you have lots of plugin automation envelopes in the project? It's hard to say more without looking at your project file so if you can share it somewhere it might show something. 

    As far as the engine goes there shouldn't be any extra load in this release. However automation rendering is at a higher resolution so it's not impossible that there could be a marginal increase if you have lots of plugin automation. There is a configuration seeing to control the resolution as well if you want to play with it. See the release notes.

    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.


  3. 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

    image.png.290014b02e96e671e1038a2eaae27ace.png

    2021.04 EA

    image.png.5b1eee8f0519e061d4f010778cdf7c4c.png


  4. 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... 🤨


  5. 23 minutes ago, Noel Borthwick said:

    @Jacques Boileau I doubt that its related to your install. If the plugin UI stops working after playing for some time it looks like an internal bug in the plugin (memory leak, or some overflow condition maybe). You should report this to the plugin vendor with any steps you remember and perhaps send them a project file for diagnosis.
    Only they can help with this issue since it is unlikely to be related to Cakewalk.

    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?

    • Like 1

  6. 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. 


  7. 3 hours ago, Sidney Earl Goodroe said:

    Totally lost on this one!! Completed the purchase, took me to Box where the downloads reside. Download the vsts, no explanation to install with this Aquarius app thingy. All I got was the Comp part of the strip. All other parts of the strip must be authorized. Wtf?????? I GIVE UP!! HELP!!!!

    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...


  8. 17 minutes ago, craigb said:

    "Box Set 4xLP?"  I know the game setting is ancient, but... 🤔

    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! 🤭

    • Like 1

  9. 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? 

    • Like 2

  10. 22 hours ago, Bruno de Souza Lino said:

    Well, the phones bundled look to be Premium Hi-Fi DJ models, which do have a Sonarworks profile. It's a bit hard to tell because there's zero information about the phones on JRR. All of the product page is Sonarworks marketing stuff.

    These are the headphones: Monoprice DJ headphones

    Expect what you pay for. I own a pair, I use them when I need close back headphones, and I have Sonarworks. They are not bad, but I have never been tempted to even try mixing on them.


  11. I just had the same problem this morning. I finally traced it down to me setting ransomware controlled folder access to 'on' without taking the time to set exceptions properly. This was suggested in Pete Brown's tweaking guide. I just didn't the full job. Amplitude could not access its preset folder and it was crashing Cakewalk. 


  12. 8 hours ago, TerraSin said:

    Is there a way to back up the .zip file? Their new installer doesn't seem to show a download location for it.

    Actually it does. In IK Product Manager, if you go to preferences (third icon on top right), you will see what the download directory is. You can even change it.

    By default you will find the downloaded file(s) under Documents\IK Multimedia\IK Product Manager. There will be a directory for the product you just downloaded with the zip in it.


  13. @Pete Brown I just went through your guide and it is excellent and thorough. Great stuff!

    One setting I haven't seen talked about in your guide, or I simply missed it, is the game mode. Since I do absolutely no gaming on my DAW's PC (I have a PS4 for gaming anyway), I turned that off. But I wonder if it has any real impact, negative or positive?

    I will put my vote in with @Craig Anderton comment: I use Edge exclusively on my DAW's PC. I did not see the benefit in installing a second browser and Edge has filled my browser need without a hitch. I started using Edge on my other, much older PC, where the fan would just run wild with Chrome opened. I was surprised how well it ran and never looked back. 

    • Like 1

  14. First, make sure you have removed all instances of a plugin. Check the path Cakewalk/Sonar scans for plugins in preference and ma,e sure you do not have duplicates. Also, you may have installed vst 2 and 3 of some plugins, if you delete only one version the other will still be found by Sonar.

    If your intention is to start fresh, as if you never where a plug-aholic, you could rename the directories where the vst are installed and Sonar is looking for them. Then you create new ones of the original name and leave them empty for now. Of course, I would suggest you leave the directory of Cakewalk/Sonar default plugin directory alone. Do a scan and your vst list should be very short. You could then cherry pick the vst from the backup dir and copy them over the new directory. It's not something I have tried, but it should work.


  15. Just got sucked into this deal too. 🥵 I also hope it will prove to be worth it! 😊 If not, I can always tell my wife you guys made me do it! 🤣

    I was gonna post that it still works, but @mibby beat me to it! Shucks!

×
×
  • Create New...