Jump to content
Morten Saether

[CLOSED] 2021.01 Early Access

Recommended Posts

5 hours ago, aidan o driscoll said:

In a sense yes. It worked last night on my laptop WHICH I HAD NOT REBOOTED then. Today I turned on both systems, driver mode set to ASIO, tried MMCSS  both enabled and disabled. Pretty much Dropout Error 0 the minute I load any file new or old. Cannot reenable the audio engine and hear a regular ticking noise over the speaker. Also the MIC Icon is flashing on and off down in the system tray if thats any help. With no audio engine, cannot play a project AND the cursor on the screen is a circle going around in circles. 

Switch to WASAPI .. all is well

 

CW_Dropouts2.jpg

Ho hum - I was optimistic there for a bit!

Share this post


Link to post
Share on other sites

The only reason it worked in WASAPI shared mode is because Windows was doing the sample rate conversion not the driver.  In his case Windows would be upsampling from 44.1 to 96K which is inefficient but would work. MMCSS is completely unrelated to this and is unlikely to cause a problem in most cases.

  • Like 1

Share this post


Link to post
Share on other sites
12 hours ago, Noel Borthwick said:

For the record the dropout issue reported by @aidan o driscoll has been resolved. I did a teamviewer session with him and found the source of his problems.
Its a driver problem with handling multiple clients at different sample rates and unrelated to Cakewalk.

In his case his Windows configuration was set to use the EVO-4 device at 24 bit 96K and Cakewalk was set to work at 24 bit 44.1K.  When I loaded his project on his system the driver appears to go into some infinite loop trying to fight Cakewalk setting the sample rate to 44.1. You can see the icons on the taskbar flashing and the driver refuses to switch to 44.1. I can't see what its doing behind the scenes but I expect its sending an infinite loop of ASIO restart notifications to Cakewalk which would explain why Cakewalk drops out immediately and then appears to hang.

I changed the Windows sound settings configuration to 16 bit, 44.1Khz for all the input and output ports for the EVO and after that everything works perfectly. We even loaded his project with the driver set to run at 16 samples and it worked perfectly.  I'm not sure why it defaulted to 96K in Windows since Aidan said that he didn't set it up that way.  I've seen many audio drivers malfunction when used at different sample rates so the first step of troubleshooting should be to either set windows to not use the audio device or make sure that its using the same sample rate/bit depth as Cakewalk. If you have an onboard soundcard, often the easiest thing to do is set Windows to use that instead.

The fix for running the device with two apps (Windows and Cakewalk) at different sample rates would have to come from the driver vendor. Aidan please start a correspondence with them.

Yeah - I've been giving this advice a lot. Seems like new users and those who feels they have more experience don't believe this.

I haven't had any dropouts of such, since I have discovered this in my Windows 7 days and still used the LE version of Sonar using only Asio4All back in 2013. 

The only time I would and still get some sort of dropout, will be with a plugin that does not support the sample rate I use with Windows 10 and the DAW. It's also extremely important to know to check if your "Favorite" plugins support these sample rates and if they have the setting to be set accordingly. 

Another important step to know: Is to never use generic drivers other than that of the devices manufacturer - including your motherboards drivers from their website. With different machines - windows intend not to have a great generic version for it. 

I think this needs to be added in the documentation too. 

Edited by Will_Kaydo
Typo's
  • Like 1

Share this post


Link to post
Share on other sites
48 minutes ago, Will_Kaydo said:

Another important step to know: To never generic drivers other than that of the devices manufacturer - including your motherboards drivers from their website. With different machines - windows intend not to have a great generic version for it. 

I think this needs to be added in the documentation too. 

Is there some kind of "Dropout troubleshooting checklist", where "check Windows samplerate" and "don't use generic drivers" could be added? So that Cakewalk users easily can check it themselves before posting or contacting support.

Great troubleshooting, Noel! 😀

Share this post


Link to post
Share on other sites
12 minutes ago, GreenLight said:

Is there some kind of "Dropout troubleshooting checklist", where "check Windows samplerate" and "don't use generic drivers" could be added? So that Cakewalk users easily can check it themselves before posting or contacting support.

Great troubleshooting, Noel! 😀

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.24.html

  • Like 1

Share this post


Link to post
Share on other sites
On 1/16/2021 at 12:30 AM, Bruno de Souza Lino said:

Even after the update, CbB is unusable. Type 1 audio dropouts every few seconds of playback, tweaking plugin parameters causes dropouts, sometimes pausing playback causes dropouts...In the current project I'm working, it takes me a few minutes to EQ a single track because you tweak a setting during playback, it causes a dropout, you go back play, then a random dropout occurs...I'm already running at the maximum latency I can.

The problem is on you, not on Cakewalk.  You need to put some money into your system if you are having such problems.  It works almost flawlessly for me and had for quite some time.

Share this post


Link to post
Share on other sites
1 hour ago, steve@baselines.com said:

The problem is on you, not on Cakewalk.  You need to put some money into your system if you are having such problems.  It works almost flawlessly for me and had for quite some time.

I'm gonna grab an infinite amount of money from the magical gold pot in the sky and buy a dual Epyc 128 core system with 2 TB of RAM and 2 Quadro RTX cards. That should do it.

Share this post


Link to post
Share on other sites
31 minutes ago, Bruno de Souza Lino said:

I'm gonna grab an infinite amount of money from the magical gold pot in the sky and buy a dual Epyc 128 core system with 2 TB of RAM and 2 Quadro RTX cards. That should do it.

Naw.  All you need is 2k.

Share this post


Link to post
Share on other sites
1 hour ago, Bruno de Souza Lino said:

I'm gonna grab an infinite amount of money from the magical gold pot in the sky and buy a dual Epyc 128 core system with 2 TB of RAM and 2 Quadro RTX cards. That should do it.

Or, you could spend time systematically debugging your setup. (Throw Time at the problem instead of Money)

  • Haha 1

Share this post


Link to post
Share on other sites

Um... Does "F2" not work to rename a clip when it has articulations in it? It seems to be ignored for clips with articulations, unless I go to the Select Module and un-mark "When clips are selected, select articulation within tracks too".

Steps to repro:

  • Have two midi clips. One has articulation (MIDI key switch).
  • Make sure that Select Clip + ff is enabled
  • select each clip in turn, pressing "F2" to bring up the clip rename window

Observe:

  • The clip rename window only appears for the clip without articulation.
  • If you clear the "Select Clip + ff" option, you can now rename the clip with the articulation

UPDATE

This issue is in 2020.11 as well. Please let me know if you would rather I create an official bug report instead of this post.

Edited by Colin Nicholls
  • Thanks 1

Share this post


Link to post
Share on other sites
On 1/17/2021 at 3:42 PM, lychee said:

Hello.

Again I have the same problem with the automation curves when using fast rendering of my music.

When I try to output my music as MP3, Cakewalk lowers my expression automation line to zero and messes up two other parameters making them orphan.

Orphaned.jpg.274efd11b4dc9c558acbdb0645c34a07.jpg

I have a feeling that this is going to be difficult to fix, but I send you my saved file with and without the bug, hoping that you will find the solution.

Cordially.

@lychee Your project has reason with custom modules that we dont have so we can't test it. If possible can you please send us a project that uses standard modules or uses a different synth? Its possible that something is corrupt with the project. 
Also are you certain that this problem is related to the new release?

Share this post


Link to post
Share on other sites
1 hour ago, Colin Nicholls said:

Um... Does "F2" not work to rename a clip when it has articulations in it? It seems to be ignored for clips with articulations, unless I go to the Select Module and un-mark "When clips are selected, select articulation within tracks too".

Steps to repro:

  • Have two midi clips. One has articulation (MIDI key switch).
  • Make sure that Select Clip + ff is enabled
  • select each clip in turn, pressing "F2" to bring up the clip rename window

Observe:

  • The clip rename window only appears for the clip without articulation.
  • If you clear the "Select Clip + ff" option, you can now rename the clip with the articulation

UPDATE

This issue is in 2020.11 as well. Please let me know if you would rather I create an official bug report instead of this post.

Thanks for this @Colin Nicholls - we'll get this fixed for the main release.

  • Thanks 1

Share this post


Link to post
Share on other sites
On 1/19/2021 at 10:27 AM, solarlux said:

Thank you very much issue fixed I Switched  to Tungsten Theme and restarted CbB And all is back. Big thanks

 

On 1/19/2021 at 10:20 AM, scook said:

Possibly the result of running a user theme that needs to be updated.

Either update the theme or change to Mercury or Tungsten and restart CbB.

Hi, I wonder... how do I update a user theme? - I know how to change to another theme, but not how to update. Thanks!

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×
×
  • Create New...