Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by Will.

  1. 1 hour ago, user6808463577169165 said:



    I found the main problem

     The problem is with Output thermal.vst3

     Because when I disable it there is no crash

      I also tested vst2 version of thermal and there was no problem

    I reported it to cakewalk( send mini dump) 

    But maybe output company should solve it 

    Definitely send Output support a complaint as well. It is highly important to send CbB support one too. I had found a problem where a plugin that was working in Vst3 doesn't work with the new release only the vst2 does. So I rolled back prior to the Update1 of 2022.02 and the VST3 installation works again. 

    • Like 1

  2. 53 minutes ago, John Vere said:

    That says it all right there. My Chevy Truck 1999, My Apple Phone 2016 . Oh and did you read that Gibson guitars have been known to also catch on fire if you use Amp sims. 

     No, I don't think it does. I trade the old car in for a newer model after every 12 months payment - as soon as the insurance allows me to. 

  3. (Read with a sense of humour.)

    Stop right there young man!

    This post is illegal. 

    Here we only post bad things about CbB. Haven't you seen the forum? We only say Goodbye and we're not going to break that tradition now - even though we are still in the month of love. 

    Wait . . . are you being sarcastic perhaps? mmmm . . . Interesting! 

    • Like 1
    • Haha 2
    • Meh 1

  4. 1 hour ago, user6808463577169165 said:

    In October or november

    So 11 is out. Well, I guess the only thing to do now - its to consider both. Maybe, the two don't play well together? Or the new driver updates of your Audient? To narrow it down, try both on a simple one track project. If the issue persists - contact all 3 developers support team directly.

    Cakewalk, Icon, and Output. 

    • Like 1

  5. 4 hours ago, bitflipper said:

    Heck, most people who drive Audis or use Samsung phones don't catch on fire, 

    Dang it!

    I don't know how to feel about this. I own both. It's actually the first time I hear about a fire incident with both. Should i be worried? Its my 4th Audi in 7 years and probably 100th Samsung phone. 

  6. 39 minutes ago, user6808463577169165 said:

    I don't think these crashes related to audient

    That's what I said with the iKeystation after a having it for a year. Look at me now . . . problem free. 

    You do realize it wont hurt you to try it right? When did you update to 11? 

  7. 1 hour ago, user6808463577169165 said:

    Audio interface : audient id14

    🙆🏻‍♂️ Icons? 🙆🏻‍♂️

    A test quick: First save the project as a "copy test project" > unplug your interface and do a export without the interface. Before you export though - make sure that all the main outputs (that was set to the Audient) are going into your "Master Bus." 


    I have the 5x Pro iKeyboard that CbB don't want to be friends with. 

    Might not be your case here, but it's worth a test. Could be those plugins too, yes. 

  8. On 3/20/2022 at 10:08 PM, Gozzie said:

    Hello Lord Tim,

    Your suggestion is one of the very first things that I tried and it didn't work for me. I tried several other suggestions too and
    they didn't work for me either. I also did the aud delete, the folder delete and the reinstall.
      I suppose that it probably has to do with individual computers, versions of software etc.... because everyone seems to have various outcomes.

    i don't want to bore everybody with the whole story but maybe this can be another tool in the tool box for the next guy that has issues.

    I just bought a brand new Intel NUC Gen11i7pah computer with Windows 10 pro installed on it. My old laptop was getting pretty old and scary to rely on anymore. I installed Bandlab and then used it to install Cakewalk.  Next I installed all the plugins and everything was fine. My trouble started when I moved my songs from the laptop to the NUC. The songs loaded just fine but the midi lagged drastically behind the audio. I opened up the piano roll on the drum track midi track and watched the behavior. When the pointer hit the drum beat, it took well over a 1/4 second for the sound to play. What caught my attention was that my bass midi track was playing in time. I closed the piano roll and noticed  that I had frozen the bass track and that it was playing as an audio file and was in time with the rest of the tracks. So I unfroze the bass track it starting lagging the same as the midi drums.
    So I started my search on that issue. 

    The suggested fix was to go back to the laptop and save my songs as a CWB file (cakewalk bundle extension) because it saves all of the timing data along with everything needed to transfer a song. So I did that but the problem still remained with lagging midi. Now I tried a simple experiment. I added a new midi track and placed a few drums beats on it. To my surprise the new drum beats stayed in time with the rest of the audio tracks while the original midi tracks lagged behind. What the heck.
    So I started my search on that issue.

    It was suggested that my old laptop WASAPI audio drivers were different than my new NUC drivers and that they could through off the timing.  (that was actually right on the money)   but here's what happened next. I went back to the NUC and started changing the audio drivers in cakewalk. I went from WASAPI shared to exclusive and there was no change. When I went from exclusive to WDM/KS cakewalk instantly crashed and wouldn't boot past the splash screen.
    So I started my search on that issue.

    I tried all of the suggestions that I found from you fine folks (many thanks) but nothing worked. The common part of all of the suggestions seemed  to be that cakewalk was latching onto the audio drivers and just wouldn't let go. So I figured that if safe boot kept windows from loading the drivers just maybe something different would happen. I saw one forum article that talked about holding down the shift key when starting cakewalk to help resolve a bad plugin issue so that's what I did while in safe boot mode . Wala...  I got the popup notice and was taken to the preference screen. I changed the audio driver back to WASAPI and rebooted the computer. Now cakewalk booted normally and all was good except for original midi lag problem.

    Now that I wasn't scared  of the crashing issue anymore I went back to changing the audio drivers. I skipped over the ASIO driver because of the known ASIO4All issues and switched  to MME. That fixed the lag problem YEAH !!!  but I couldn't leave it alone at that so I tried another experiment. I opened up another old song with the MME driver and then saved it as another project. Then I changed the audio back to WASAPI shared and the song stayed in perfect timing. I loaded another old song and the timing was all off again with the midi lagging far behind the audio. So I repeated the process of changing the audio driver back to MME and saving the song. I changed the audio driver back to WASAPI and the timing was perfect again.
    So my fix for this was open old songs in MME and then save them. Now they will play right with whatever audio driver I choose at least for this computer. If I transfer to another computer this process may or may not work. I hope I dont have to find out anytime soon.

    How and why is way beyond me and I don't know if my fix will or won't help out the next person in line but hopefully it might keep someone from committing a violent act against their computer. I came all so close.  

    Many thanks to you Lord Tim and everyone else who are out there trying to help out all of us  keep up with the issues. You're a good dude.


    I had this happened recently, but haven't changed anything. I just saved the project closed Cakewalk, made a quick run, came back and that happened. My fix: Well, as you've said - it might not be a fix for everyone, but I did the Ctrl+Alt+Del thing and ended every task where I could see it was still showing up as "in use." 

  9. On 3/22/2022 at 8:50 AM, user6808463577169165 said:

    the amount of hiss that is produced in the cakewalk is        - 52db

     But in cubase and Studio One  - 56db

    This is expected seeing that when setting up Mono tracks Cakewalk it adds a gain of +3dB. There has been a multiple debates on this issue across the forum, unlike with pan setting that has the 0 balance control. When switching a stereo track/insert to mono in CbB, it takes both the L&R channels and collapse it into a mono output track that adds this +3 extra dB in gain that you're experiencing - in fact: Kudos for noticing that. So the next time you record in mono you can compensate for this, by dialling back the gain knob on your interface mic/guitar input while you're checking the levels on the meter, to keep your noise floor in check. 

  10. My studio has been treated 4 days now and before I could not hear this. When creating a SC with Aux - MEANING: Routing a synth bass output to an AUX track and sending the input to the compressor, there is a click everytime when the trigger happens in the SC channel as if the kick bleeds in to it, when it is in Solo mode. 


  11. 1 hour ago, Glenn Stanton said:

    maybe re-install it and re-scan it? or you're using a preset which has the volume off?  🙂 i haven't tried the PC version of it, but assume that is a VST2.

    I have done all of this. The Vst3 version works in Logic pro x. 

    Weird. It also have been tested on my secondary system with the same result. It seems the Vst3 does not work in this version of Cakewalk for me. It was work prior to this release. It is one of my go to EQ. This is the first time ever using the VST2 version in a project. 

  12. 32 minutes ago, Glenn Stanton said:

    i'm on build 2022.02 039. seems to be working. i have both the vst2 and vst3 installed - although override to use vst3 is set in preferences.



    Mine show too, but does not output any sound in Vst 3 only in Vst2. 

  13. Cautiously and respectfully doing a feature request for Boz Digital The Hoser VST3 to work in the current release. It was working prior to this update, but it seems only the Vst2 is working in the current release - specifically. This was the very first time I am installing it as a Vst2, upon looking into the cause. The Vst3 version install, launch, but has no output to it in the current release. Vst2 works fine. 

  • Create New...