• SONAR
  • Conflict between ProTools and Cakewalk Sonar
2018/07/07 17:46:05
Mad_Musicologist
Hi all,
there is a strange thing going on.
when I launch a project in Cakewalk Sonar (either "old" version or "new" by Bandlab), the DAW shuts down before I can really do something.
Then I have a pop up telling me something about an unforeseen error which caused Cakewalk to shut down.
Up to here, ProTools readers might say I am wrong in this forum.
Please see the screenshot, then you'll change your mind.
I notice that the causing file is a core file for AVID applications, so I better do not mess around with it.
Strange is that I NEVER run ProTools and Cakewalk simultaneously.
But they share some plugins (which have, for ProTools, .AAX, and for Cakewalk, .VST).
I have contacted of course both Cakewalk support and AVID support, sent the mini dump file to them, but might not have an answer before Monday evening.
I saw there is a thread with complaints that ProTools Ultimate 2018.4 (which I am running without problems) was crashing upon launch. Since this does not seem to be the case with my system, the cause for the issue must be somewhere else.
Please, I'd love so much to have both DAWs on one computer.
2018/07/07 18:08:48
Anderton
The only suggestion I can think of is to change the name to CFnd.dlx before you want to use Sonar or CbB and then maybe it will be ignored. Change the name back to CFnd.dll when you want to use Pro Tools. I can't guarantee this will work but is worth a try.
 
FWIW one day, my pre-subscription version of Pro Tools was working. After a Windows update, it would no longer open. I decided I didn't need it enough to get the subscription, but I downloaded the free version so I could take some screenshots for a book. It put tons of stuff on my hard drive...I'm considering uninstalling it. I think Avid assumes that you're running a dedicated Pro Tools computer.
2018/07/07 18:43:06
tnipe
I've been running both for a while now. I used to have that error or something very similar. It doesn't happen anymore, and I don't know what fixed it. But my point is that it works to have both installed. Have you tried ending the Avid application manager process before opening Sonar? Might be worth a shot.
2018/07/07 21:29:37
Mad_Musicologist
tnipe
I've been running both for a while now. I used to have that error or something very similar. It doesn't happen anymore, and I don't know what fixed it. But my point is that it works to have both installed. Have you tried ending the Avid application manager process before opening Sonar? Might be worth a shot.

That's a fine idea, I will try. BTW, the friends in the ProTools forum suggested I should run Cakewalk as admin. That was helpful.
But it really might be that the application manager is the thing I should prevent to be in autostart. It should only be active if I either launch it directly, or I launch any AVID application.
I will try that tomorrow.
But thankx for the cool idea. 
2018/07/07 21:51:41
Noel Borthwick [Cakewalk]
Read this thread. apparently this is a recurring issue with other daws as well.
https://www.steinberg.net...viewtopic.php?t=119096

I suspect that PT is installing some audio component that is being automatically loaded by some ASIO driver on your system and crashing on startup when Cakewalk is enumerating devices.

If you share a minidump from the Cakewalk by bandlab crash I may be able to tell what operation is causing it to crash.
2018/07/08 05:08:00
Mad_Musicologist
Hi Noel, 
that article says the conflict might be caused by Quicktime for Windows, I deinstalled all Quicktime, Apple for Windows-software which I had been running on this PC.
Tried "normal" launch of my Cakewalk project, it crashed again: not directly upon launch, but after half a minute.
When the crash occurred, I had been in playback. Even 15 seconds after the crash (Cakewalk had already disappeared from the screen) I still heard some fragments of the project I had been playing back. Weird. A ghost is playing inside my PC. ;-) Do I have to call in the "Men in Black",  or preferrably the Ghostbusters?
2018/07/08 12:22:49
mettelus
Type "services" in your Windows search and look for all the PT stuff. Nothing related should be "automatic" (or loaded at boot). "Manual" is preferred for apps so that they only run when you actively launch the application. You have to right click and change that on the properties page for the service, but I highly suspect that PT is running things at boot. You can also "stop" processes there that may not show up in the task manager.
2018/07/08 14:07:22
Noel Borthwick [Cakewalk]
If you read the thread CFnd stands for Core Foundation which seems to be some cross platform abstraction layer they are using. My guess is that they are either installing a custom ASIO driver or its a shell extension or service that gets invoked during Cakewalk (and other DAW) start up.
2018/07/08 16:40:25
bitflipper
Interesting that the thread is almost a year old and no resolution was ever posted.
 
It shouldn't be that difficult to find out who's calling the DLL. It's got to be something the two DAWs have in common, most likely a driver, and it most likely says "Avid" in its file properties. Avid says the ASIO driver does not load it, but they probably determined that by looking at the source code and could have missed the reference if it's an indirect dependency.
 
My understanding is that PT installs its own ASIO driver. First place I'd look is that driver's dependencies, as well as those of other audio-related drivers (there may be many). 
 
Afterthought: try using a different driver for SONAR/CbB. The safest one for testing would be MME. If the problem goes away, that tells you it's definitely being caused by the ASIO driver.
2018/07/08 20:31:02
Mad_Musicologist
bitflipper
Interesting that the thread is almost a year old and no resolution was ever posted.

Weird. If AVID has knowledge of the issue, how come they miss solving it?
bitflipper
It shouldn't be that difficult to find out who's calling the DLL. It's got to be something the two DAWs have in common, most likely a driver, and it most likely says "Avid" in its file properties. Avid says the ASIO driver does not load it, but they probably determined that by looking at the source code and could have missed the reference if it's an indirect dependency.
 
My understanding is that PT installs its own ASIO driver. First place I'd look is that driver's dependencies, as well as those of other audio-related drivers (there may be many). 

In my config, Cakewalk uses the ASIO driver from my soundcard.
I'd have to see which one PT is using.
bitflipper 
Afterthought: try using a different driver for SONAR/CbB. The safest one for testing would be MME. If the problem goes away, that tells you it's definitely being caused by the ASIO driver. 

Didn't I once read for some reasons I do not recall anymore, MME is not optimal choice? 
But I will give that a try tomorrow.

Thankx for coming in on that issue. Maybe by tomorrow night we will know more, when I hopefully receive the analysis of the mini dump files.


12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account