VP14 crashed frequently on pro tools 12 file "CFnd.dll"

Musicvid wrote on 12/5/2017, 4:24 PM

Have you tried reinstalling Vegas?

Slaughtertown wrote on 1/2/2018, 10:27 AM

@oskari-m I have this same problem, but in a different order. I have been a Pro-Tools user for many years, along with Sony Movie Studio. After upgrade from PT11 to PT12 I started getting crashes of SMS with an error in that CFnd.dll pro-tools extension. If it would crash immediately with opening SMS, I would have to copy a "clean" version (reserved with a different file name) into the offending PT directory and then it would work again for a while. Then SMS would start randomly crashing while editing or just sitting there during a break. Eventually it would be all the time and I copy the "clean" file again. (Somehow it gets corrupted).

@Musicvid I just upgraded to Magix Vegas Pro 15 (fresh and clean install) and still get the same exact problem. I have this same experience on two different computers which run Pro Tools and some version of Vegas (or SMS) and still when I did a full and clean rebuild of a laptop with a new SSD primary.

In the various forums for other software that crashes with this error (all seem to be audio or video editors), the suspect is ALWAYS an installation of Pro Tools is present, even if it is not running or the software in question has no dependency on any plugins or hardware which access Pro Tools. AVID dumps the problem on those developers. There is obviously something registered to PT from the PT installation which then interferes with these other programs which may be calling a modified codec, DLL or something else. If this rings a bell with anyone seeing this post, please share your thoughts. My next step may be to uninstall Pro Tools. I've had it with AVID anyway and have switched to Studio One Pro.

Musicvid wrote on 1/2/2018, 2:58 PM

This behavior was first reported with the release of protools 10, I vaguely recall.

Probably just sloppy coding, nothing more sinister.

oskari-m wrote on 1/2/2018, 4:53 PM

Hi,

I haven't been too much on the edit bench lately to be sure, but seems that i can avoid the problem simply by renaming the "CFnd.dll" to something else (like CFnd_TEMP.dll) while working with vegas. No crashes. Of course PT won't start or work then but when i need PT i just rename the file back to "CFnd.dll".

simple and stupid, but seems to be only way to get Vegas working in any reasonable way at the moment...

slaughtertown, what do you exactly mean with this: "I would have to copy a "clean" version (reserved with a different file name) into the offending PT directory and then it would work again for a while."?

NickHope wrote on 1/3/2018, 2:45 AM

I don't understand why Vegas would be looking in /Program Files/avid/protools/ at all. Anyone know?

Former user wrote on 1/3/2018, 7:58 AM

If you do a search online you will find this particular file seems to affect other programs as well.

Jam_One wrote on 1/3/2018, 8:23 AM

1. Find out which VST plugins does the "ProTools" bring with itself / installs.

2. Change the extension of CFnd.dll from "dll" to something else.

3. Launch Vegas.

4. Go to the "Options -> Preferences -> VST Effects"

5. Locate and uncheck the ProTools-inherent plugins.

6. Rename the CFnd.dll back to its normal name.

~~~~~~~~~~

One of the reasons behind the mentioned crash:
Vegas calls VST plugins at startup. Some of the plugins do respond in an "uncompatible" manner, thus preventing Vegas from starting. One of MDA plugins I used to know did this. Some of the plugins, in their turn, do activate their host/engine. An example of separated "plugin-engine architecture" being the Waves plugin system. I suppose, what we see here is an example of "uncompatible action" from the host of some VST plugin.

=======================

⚠️ The troubleshooting measures listed above are purely my theoretical supposition/assumption. I have never had any practice with "ProTools". ⚠️

Mike.Lehman wrote on 1/26/2018, 5:51 PM

I use both Pro Tools and Vegas Pro on the same machine. When I upgraded to VP15 I was hoping this would go away, but as evidenced here that is not the case. Here is what I have found...

For me the VST's have nothing to do with the problem, disabling them makes no difference. Before I start Vegas, I rename the CFnd.dll to _CFnd.dll (the underscore moves it to the top of the files list and is easier to locate later). Vegas Pro then runs fine. When I go back to Pro Tools I then rename the DLL back to its original name so Pro Tools can run properly. To help facilitate this I created a shortcut on my start menu to the CFnd.dll file location.

I should also mention, that as the date of this post, I am using the latest versions of both Pro Tools and Vegas Pro.

Former user wrote on 1/26/2018, 8:00 PM

According to what I can glean from online, Cfnd.dll is an Avid file but is part of the ASIO driver. Are you all using ASIO for your audio in Vegas? If so, this could explain something.

Mike.Lehman wrote on 1/27/2018, 2:10 AM

I do not use ASIO with Vegas Pro. I use my system's internal audio card. I do use Focusrite's ASIO driver with Pro Tools, although I keep all of that equipment turned off when using Vegas Pro.

Former user wrote on 1/27/2018, 9:07 AM

Still might be interfering with the audio driver in some way. I see problems online there is other software that has problems with it.

FPP wrote on 6/20/2018, 10:03 AM

I'm not inclined to create any negative kharma, but I fell for the sinister digital trick of, if I just upgrade to the lastest version of Vegas Pro 15, the constant crashes will cease... For about the last 18 months or so, my Sony Vegas Pro Versions 12 & 13 would crash after editing very basic files, using mostly simple cuts and transitions and so on... When I open up 12 or 13 , the new Magix offer pop-up prevails if my machine is online.

If I open program offline and run it, the program will last a little longer but eventually crashes in the middle of an edit.

I removed Versions 12 and 13, but the problem persist.

I have nothing positive to say about this so called (UPGRADE) but I feel "Ripped Off". I feel like All Magix gave me for my money is infinite instability and an impeded work-flow.

They put the software out there and expect the user to figure out what is wrong with the functionality.

I don't mind having to "tweek here" and "tweek there" but why are we the users tasked with something that should be done before release?

They got my money and I cant get a refund for registered software..

I should've exercised more discretion before my purchase, considering the history of my past experiences.

I have no choice but to go to College and study computer science, even if the teacher is 30 years younger than me.👎🤓