CakeAlexS

pwalpwal
 
that shouldn't be necessary - how could installing an application affect your drivers? maybe migrating x3 settings? (if as craig says, x3 and patinum relase them differently)

Of course it shouldn't be necessary in a perfect world. However driver software (as other software) sometimes erroneously updates registry settings and file dependencies in it's update script, or the software isn't handling specific use cases correctly in peoples system configurations (the software developer just hasn't accounted for it), or there's something iffy going on in the the registry or a file/library dependency caused by another external factor. It has worked for me (several times) and others in these forums, that's not to say in this instance it will work or not, but it isn't something to be dismissed either.
 
My view is it could be a plugin issue but it's just speculation at my end (the cause right now is unknown), you need to patiently rule things out one at a time. I generally start with drivers/firmware and windows (windows update), then plugins, then Sonar (bottom upwards). Most of the time it gets to the root of the cause assuming there isn't anything listed in logs such as the Windows event viewer (should look at that as often it is a shortcut). At the end of it in the rare case of something not being resolved you end up going to support.
 
Cheers...

A couple of my projects had zero plugins...

Well, yet again, I get irritated at the phone support hours from SONAR support. They need to have later hours if they are only going to have a 5 hour window for phone support.
 
People have day jobs and need support when they get home which is usually way after 6p EST.

I also want to add that at one time I was having some issues and found I had drivers for my interface installed in multiple instances and they were hidden when I looked at Window's Device Manager.  From TC tech support they list a method to find and eliminate driver duplication(s). This method should work with any driver and I found a number of ghost duplications for other devices as well (some no longer connected -both FireWire & USB). My system has been snappier and without weird audio interface issues since...
 
Please try the following:

1. Disconnect Konnekt / Impact Twin (your audio interface) completely
2. Uninstall the whole TC Near (your device's software/drivers) software package
3. Go to System Properties->Advanced->Environment Variables and add devmgr_show_nonpresent_devices=1
4. Go to the device manager and enable View->Show hidden Devices
5. Uninstall any (your device drivers) TC Near drivers hanging around by right click on TC Near (your interface driver) select uninstall
6. Select re-scan for Hardware changes in the menu. Windows might now find an even older driver. Right-click uninstall and rescan again until all (your interface drivers) TC Near entries become unknown devices.
7. Re-install

Musicroom, that is a great tip. While the hidden devices are showing, it's also a good opportunity to get rid of the duplicate MIDI drivers that might end up bumping against the Windows MIDI port limit.

Anderton
Musicroom, that is a great tip. While the hidden devices are showing, it's also a good opportunity to get rid of the duplicate MIDI drivers that might end up bumping against the Windows MIDI port limit.

Thanks - following those steps literally changed my computer / audio experiences, not to mention my disposition. I found several instances / versions of the IT drivers along with the onboard audio driver loading, but hidden. Lot's of conflicts going on behind the scenes.
 
I learned something here, I didn't realize we had a MIDI port limit with Windows. Good call!!

I'm using the UFX with Platinum on windows 64 bit and I've not had any issues with closing projects or the application.  I also have a Fireface 400 connected to my laptop that I've not had issues with either.

musicroom
I learned something here, I didn't realize we had a MIDI port limit with Windows. Good call!!

 
Here's more info.

musicroom

Anderton
But I also wonder about FireWire and Windows 8.1. I weaned myself off FireWire a while ago, so don't have recent experience with it. IIRC there was something with Windows 8 about having to download legacy drivers or something...
 

 
FYI on this subject. I'm enjoying solid FireWire performance with Win 8.1.1 / Impact Twin.
 
 

+1 on the Impact Twin, and my MOTU Traveler (original and Mk3) with Win 8. I could be one of those lucky ones that don't need to use the legacy Firewire drivers. (In fact I've tried the legacy driver before when troubleshooting Firewire issues. The legacy driver didn't even work with the interfaces.)

CakeAlexS

pwalpwal
 
that shouldn't be necessary - how could installing an application affect your drivers? maybe migrating x3 settings? (if as craig says, x3 and patinum relase them differently)

Of course it shouldn't be necessary in a perfect world. However driver software (as other software) sometimes erroneously updates registry settings and file dependencies in it's update script, or the software isn't handling specific use cases correctly in peoples system configurations (the software developer just hasn't accounted for it), or there's something iffy going on in the the registry or a file/library dependency caused by another external factor. It has worked for me (several times) and others in these forums, that's not to say in this instance it will work or not, but it isn't something to be dismissed either.
 
My view is it could be a plugin issue but it's just speculation at my end (the cause right now is unknown), you need to patiently rule things out one at a time. I generally start with drivers/firmware and windows (windows update), then plugins, then Sonar (bottom upwards). Most of the time it gets to the root of the cause assuming there isn't anything listed in logs such as the Windows event viewer (should look at that as often it is a shortcut). At the end of it in the rare case of something not being resolved you end up going to support.
 
Cheers...

my view, were i an armchair psychologist, is that you're rationalising why it's "not sonar" but fair enough :-)

Perhaps Alex has been bitten by the "I installed an application, now SONAR doesn't work" issue because of overwriting a library that SONAR needs. That's happened to me twice and if it wasn't for this forum, I'd probably still be tearing my hair out Granted most of my hair is flesh-colored, though.