Noel Borthwick

Thanks David, What version of the Generic ASIO driver do you have currently? I’d like to report this to Steinberg for investigation as well.

The Realtek ASIO driver is the culprit here. You can use WASAPI mode (exclusive or shared) if you dont have a different audio interface. WASAPI works well with Realtek devices.

@David GovettThis is not a focusrite issue. Most likely your issue is the "Generic Low Latency" ASIO driver that is installed on your system. If you freeze frame your video you will see that the pop ups are emanating from that driver. Look for this driver on your PC and uninstall it. I know some old versions of Cubase or their plugins installed that. Let us know what the manufacturer of that driver is by looking at the file properties when you find it. I'm pretty sure that once you remove it you wont have this issue. Cakewalk doesnt need this driver since WASAPI mode is sufficient and preferred for accessing soundcards that don't have ASIO drivers. If you can't easily find the driver and uninstall it you can do this: Go to this registry key in regedit and look for "Generic Low Latency ASIO Driver" HKEY_LOCAL_MACHINE\SOFTWARE\ASIO Then copy the CLSID value search for it. You should find it embedded under the CLSID key below HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\ For me it looks like this HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{52EBAE30-47E4-483F-B87B-770314306005} Then under that key's InprocServer32 value you will see the path to the ASIO dll. Go to that path and rename the all dlls in that path with a .bak extension or something else. Restart your PC and now that ASIO driver should no longer be loaded by Cakewalk.

@Anders Madsen if you can reproduce it could you send us a crash dump?

What device and driver mode were you using when you had the issue? You can post screen shots if you aren’t sure.

There are no specific changes to the engine that would affect the core behavior, if anything CbB is a lot more efficient. You are probably running into Windows 7 legacy stuff. Cakewalk is compiled with the latest Microsoft tools compared to SONAR and perhaps that may account for some minor differences. More likely you have tweaked your system for SONAR in some ways and CbB is configured differently. Re crashes please submit any crashes you encounter for investigation. There are details in my sig about crash dumps. We've fixed hundreds of crashes that occurred in SONAR so CbB is more stable for most people by a long shot.

Ive seen some plugins take long irrespective of available CPU. They may be artifically throttling the processing speed. You can try bypassing the plugins to find which ones slow down. Render is also gated by disk access. Also you can speed up by setting the bounce buffer size high in the audio configuration settings.

@Cecelius2 thanks for following up. Please keep us posted on the status of this issue.

@sreams please report this to the Video card vendor and also to Microsoft via the feedback channel. @Pete Brown may be able to follow up after you log a feedback report on Microsoft. This is likely on the driver vendor to fix it however.

@eric chevrier The crash is in the UI for the prochannel EQ. However I cannot determine what led to that crash. All I can see from the dump is that the crash happened on an instrument track strip. Something odd is that I do not see any EQ loaded by your project. Questions: Can you verify whether any of your instrument tracks have the EQ enabled? Can you remember specifically what operations you did leading to the crash. Also more importantly, is it reproducible? Did you get any prior error messages pertaining to the EQ when loading the project. Does the error happen with only one project or all, How many tracks have the EQ enabled?

Hi folks, this is the FAQ channel so please don't post specific problem reports here. @eric chevrier I've replied in your other thread.

The issue quoted has already been solved for the next release as reported in the thread scook linked. The resolution for now is to use BandLab assistant to activate. If you are running Windows 7, this is a reminder that Windows 7 is not actively supported or tested by Cakewalk (or Microsoft) so you use it at your own risk since issues like this can crop up.

The only reason a Wav64 is created is if the wave file exceeds 2GB. Make sure you select exactly the length you want to export on the timeline. The duration will show in the export audio title bar. You can also use the new Export toolbar and set it to export a selection. Other factors that can lead to a wave 64 exporting is if you are exporting at high sample rates or at 64 bit resolution which will create bigger files. Additionally in the export dialog ensure you are selecting the file type of WAV and not Wav64.

Please post questions like this in the techniques forum which is more appropriate.

Hi @sreams there is nothing especially expensive cakewalk is doing when moving the mouse over track names. I suspect something video driver related since the cursor does change.

What audio interface and driver mode? Do you have Cakewalk set to share the audio device with other applications?

Let me know if you can get a reproducible case with a project and we can follow up with NI.

Unfreezing reloads the synth into memory. If he app spontaneously shuts down it could be memory corruption from the synth.

Glad you could solve it. In asio mode you must deselect both inputs and outputs before picking a different device. This could be more intuitive.

The problem is something on your system blocking writing files to your audio folder as the message indicated. Check that you don't have an antivirus program blocking writing to the project audio folder. Also if you are using one drive don't use the same folder that one drive is scanning.

BandLab assistant is not developed by Cakewalk. Were working on a standalone bootstrap installer that will install Cakewalk independently. Since Cakewalk can now activate itself BandLab assistant is no longer required for this.

The CmdArgs registry string is used to specify the arguments to the external tool. Its definitely used in CbB and and its how we pass command line arguments to the Plugin Manager exe. Note that this is only used for the generic tool type. Look in the registry and you will see how Plugin Manager is set up. For plugin manager its set up like this: CmdArgs --- "/ParentWnd$ /VSTInventoryRegKey$" When Cakewalk launches plugin manager it expands the /ParentWnd$ variable to the window handle of Cakewalk and /VSTInventoryRegKey$ to the appropriate registry key. Other flags present in CmdArgs are passed through unmodified to the external process. Its easy to test this. Make a batch file that echo's its arguments and set up a tool that executes the batch file.

Thats impressive with just 8GB RAM

@Bob Greaves which version did you install when you ran into this problem? 24.4 is obsolete. We’ll contact you tomorrow with more instructions,

I have the multiple accounts wired to my NAS not pc. It allows me to have a hybrid storage solution.