|
|||||||
![]() |
|
|
Thread Tools |
|
|
#1 |
|
HardwareHeaven Newbie
Join Date: May 2008
Posts: 18
Rep Power: 0 ![]() |
3550 x64 crashes CT ASIO services
Windows 7 Professional x64
6 Gig Ram SB0244 as kX 3550 host card EMU 1616m also on system Problem: After installing 3550 x64, it messes up my Creative ASIO services. When starting a host such as SoundForge 10 or Sonar, I get warning popups that 'Creative ASIO devices have changed, you may need to restart this application'. Of course, restarting does nothing to help. This did not happen with the x86 version of the 3550 driver, which I tested happily alongside my 1616m in Win 7 Enterprise RC x86. I also use kx 3545 alongside the same 1616m card on a Windows XP x86 boot to the same system. No ASIO problems there. Anyone experience the same ASIO conflicts with a kX/EMU side-by-side setup? |
|
|
|
|
|
|
|
HardwareHeaven Newbie
Join Date: May 2008
Posts: 18
Rep Power: 0 ![]() |
Re: 3550 x64 crashes CT ASIO services
Update:
I tried this on my Vista x64 and exactly the same thing happened, so its not a Win 7 thing, its an issue of the 3550 x64 driver ASIO messing up Creative ASIO for the EMU card. In the meantime I've disabled the SB0244 card and I'll wait patiently for an update or repair for the x64 3550 driver. |
|
|
|
|
|
#3 |
|
Long Time ***** Friend
|
Re: 3550 x64 crashes CT ASIO services
kX is now compatible with the EMU cards, so it's no wonder you're experiencing this issue. It appears that the kX installation is also trying to install the kX driver for the EMU card, as well as the SB 0244. If I understand you correctly, you are trying to use the EMU drivers for the 1616m and the kX drivers for the other card.
If so, you should try this: Without kX installed, make sure the EMU drivers are installed and working correctly for the 1616m. Go to Device Manager and under Sound, Video, and Game Controllers rightclick on the EMU card and Disable it. Now, install the kX driver for the other card, and make sure the other card is working correctly. Once you know the other card is working correctly, go back to Device Manager and rightclick on the 1616m and Enable it. Now, check to see if both cards are working correctly? |
|
|
|
|
|
|
|
HardwareHeaven Newbie
Join Date: May 2008
Posts: 18
Rep Power: 0 ![]() |
Re: 3550 x64 crashes CT ASIO services
Thanks Thomasbarnes for the feedback. After almost two whole days of testing I've managed to make progress. Your advice is not far from what I did, but the problem seems to be the opposite - ie Creative drivers being 'Plug n Play installed' on the SB0244 card as soon as its detected. So, to make it easier for other people wanting to use an EMU card next to a kX card, I'll summarise what I did:
Of course I'd be happy if these issues are taken into account in the next release of the driver. |
|
|
|
|
|
#5 |
|
Long Time ***** Friend
|
Re: 3550 x64 crashes CT ASIO services
Is Soundforge 10 a nitive 64 Bit app? Don't know if you already know this, but the kX x64 driver is only compatible with native 64 Bit programs.
Are you saying you can't pull up the kX control panel in SONAR under Options/Audio General tab when you click on the ASIO Panel button on the General tab? Nor can you pull up the kX ASIO Control panel when SONAR is closed and you rightclick on the kX icon in the taskbar and go to Settings/ASIO Control Panel? |
|
|
|
|
|
#6 | |
|
HH's curmudgeon
|
Re: 3550 x64 crashes CT ASIO services
Many if not most DAWs will only use one ASIO client at a time if I'm not mistaken. Glad you got both running side by side though..... thanks for the write up.
__________________
Quote:
No trees were harmed in the production of this message.
However, an extremely large number of electrons were rather annoyed. |
|
|
|
|
|
|
|
|||
|
HardwareHeaven Newbie
Join Date: May 2008
Posts: 18
Rep Power: 0 ![]() |
Re: 3550 x64 crashes CT ASIO services
thomasabarnes wrote:
Quote:
One thing I can do is route SoundForge to the kX card through MS Sound Mapper, but Master Mixer is noisy as others have found. Wave Out 2/3 seems to be clean though. Quote:
Tyrsonswood wrote: Quote:
A small observation: unless I edit Windows\Run registry settings so that the kX mixer run command line falls above the CT ASIO registration line, the kX tray icon does not appear. Everything else works, but you can only access the kX root menu by right-clicking anywhere on the kX Mixer window. A final thought - contrary to the title of this thread, I now know that kX 3550 itself does not crash CT ASIO services, what crashes them is the presence of another creative card besided the 1010 card. The evidence of this is the fact that CT ASIO stops working when Windows auto installs the Audigy 2 driver on the SB0244 card when it detects it at startup. In summary, the problem is not having kX, its having two creative cards. |
|||
|
|
|
|
|
#8 |
|
Long Time ***** Friend
|
Re: 3550 x64 crashes CT ASIO services
Hi John:
Thanks for the report. In my above post when I refer to SONAR, I mean SONAR x64. So, if you install the x64 version of SONAR, you should be OK using the kX ASIO driver, but I've been experiencing some slugishness when arming/disarming tracks for recording using the kX Driver and SONAR x64 8.5.2 and 8.5.3. Your kX ASIO issue with Soundforge 10 is surely because it's not a native x64 program. I will be waiting for you to report back after you install SONAR x64. |
|
|
|
|
|
|
|
|
HardwareHeaven Newbie
Join Date: May 2008
Posts: 18
Rep Power: 0 ![]() |
Re: 3550 x64 crashes CT ASIO services
thomasbarnes wrote:
Quote:
Another interesting but minor issue: I can't access the kX ASIO panel from the kX mixer menu (despite explicit registration of the dll etc..) BUT I can access it from within Sonar after denoting kX ASIO as the audio driver mode. |
|
|
|
|
|
|
#10 |
|
Long Time ***** Friend
|
Re: 3550 x64 crashes CT ASIO services
Thanks for reporting back.
As for not being able to access the kX ASIO CP, make sure SONAR is closed when you want to access the kX ASIO CP by rightclicking the kX icon in the taskbar and navigating to Settings/ASIO Control Panel. I'm not certain, but I think it's meant to work that way (meaning when SONAR is open, a user has to access the ASIO CP from within SONAR), but if SONAR is closed, you should be able to open the ASIO CP by navigating from the kX icon in the taskbar. If SONAR is open, I cannot open the kX ASIO CP by navigating to it from the kX icon in the taskbar;I have to access the kX ASIO CP from within SONAR. |
|
|
|
![]() |
| Thread Tools | |
|
|