Jump to content

Jacques Boileau

Members
  • Posts

    1,135
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Jacques Boileau

  1. Well, for those who where disappointed by this months Tunecore giveaway not being a plugin, this makes up for it! When I first got my interface, giveaways where once a month. Of course it was a little disappointing when they went to bi-monthly, no sleep loss of course. But if they keep this trend of 2 offers bi-monthly we are back to the equivalent of once a month. Cool! ?
  2. Yep, happens to Snark tuners, some remotes, Playstation joysticks, etc. They all use the same material that has a nice touch for a few years, than boom it gets yucky! Easy fix: a little rub with isopropyl alcohol 70% on a scott towel gets the gummy out without affecting the material too much. I have done it a few times and it works very well. I tend not to do it to often though since it has the word alcohol on the bottle. I get confused easily...
  3. One thing I don't understand though is if you look at tips & shortcuts in the settings panel of the 360 mixer, it says: "To use the SOLO system, ensure you insert Channel Strips on every DAW track. Don't forget to SOLO SAFE the Channel Strips on Busses/Auxes!" My understanding of this is that to use their SOLO system I need to add an instance of the Channel Strip on busses just for the SOLO button. I could live with that, but the numbering for busses starts back at 001 and busses get interleaved with the tracks in the 360 mixer! Not a nice layout! There may be something I don't understand here... Is there a way to specify CbB numbering of buses? For example if I could set it so that busses would start at 101, at least they would appear after all the tracks. Assuming of course I have less than 100 tracks, which for me is always the case but may not be for others though.
  4. The order follows the track order. If you reorder your tracks in CbB the tracks reorder in 360 mixer.
  5. Wow, the 360 mixer is nice! Great view if you want an SSL virtual console!
  6. Thanks @scook ! This thread is going too fast for me! ? I saw Larry's comment that 360 needed hardware, but missed yours that correct it that. My bad. ?
  7. Sounds great, but where is it!?!?! I can't find it on their site. Is having the native essential good enough to get the 360 mixer? I have bought the channel strip and bus compressor a couple of months ago, so its great to have the new version for free. Thanks for your video on the bus compressor. You rock Zo! Can't wait for your review of the channel strip.
  8. MAutoAlign is currently 59% off at Plugin Boutique, 22$. But it is listed as regular price of 54$ there and it is listed as 72$ on Melda's site. So it's actually almost 70% off Melda's list price. I don't know how often this happens, but its quite a deal.
  9. It is simply hidden. You must enable it in plugin manager. For more info, you can also watch Mike explaining you how to do it:
  10. I had to do some automation today and it was a pleasure with the upgrade that was made to it. Really nice. Makes our work easier and simply works great. Is it just me or before when you opened the automation lane it would, as now, create a volume automation lane. But before, to get rid of it we had to erase the data, the minus would only close the lane but keep the automation. Now if we do not do any editing and close it using minus, the automation is erased. If it is the case, to me its a great improvment. Countless time I would open the automation lane and change my mind and have to erase the volume automation.
  11. Hey, thats from where I live! ? I wish I hadn't miss that show... ?
  12. 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.
  13. Used 8 jampoints and got Fender 2 for 17$ and now have the entire Fender collection. ?
  14. 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.
  15. 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
  16. 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... ?
  17. I have transmitted this information and a link to this thread to Tim Shortle at SSL support. Thanks Noel!
  18. New inserted plugins of the same type exhibit the problem too.
  19. 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?
  20. 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...
  21. Good point! I just checked and my integrated Intel graphic driver is at the latest...
  22. 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.
×
×
  • Create New...