So as the topic says, using asio with my x-fi is causing issues. I know it's most likely the card, but I'm going to cover all my bases here or at least try. I know fb2k works great and is fully compatible but I'm not sure about the plugin. I try to shut it down but, it won't so I have to reboot to fix it.
I'm wondering if anyone has experienced the same thing; right now I'm just going to use KS, but I like asio better =D
Thanks.
Did you update your driver to the official, released a few days ago?
So as the topic says, using asio with my x-fi is causing issues. I know it's most likely the card, but I'm going to cover all my bases here or at least try. I know fb2k works great and is fully compatible but I'm not sure about the plugin. I try to shut it down but, it won't so I have to reboot to fix it.
I'm wondering if anyone has experienced the same thing; right now I'm just going to use KS, but I like asio better =D
Thanks.
The ASIO plugin is broke, nothing you can do.
Yay another reason not to upgrade to vista
Yay another reason not to upgrade to vista
Sucks. I really like vista over xp. So many changes that are very impressive. Now that my x-fi is working, I'm stickin with it and using ks =( Though I can't tell much of a difference between the 2, but the thing is, creatives asio driver lets me adjust asio volume seperate from the main volume. So like in WoW, I can lower my music volume so I can hear people on Teamspeak. If I try that with KS, it lowers both. Unless I'm missing something
hi, i'm runing vista with x-fi xtrem music card (latest drivers) with the basic output device and i've the runtime c++ box error.
sorry for my poor english
I'm having the same problem with ASIO, X-Fi XtremeMusic, and Vista. Here are the crash reports I get:
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 02484AA1h
Access violation, operation: write, address: 04D00888h
Call path:
This is the first crash logged by this instance.Access violation, operation: write, address: 04D00888h
Stack (04F0EE40h):
04F0EE20h: 00000000 00000000 00000000 00000000
04F0EE30h: 00000000 00000000 00000000 00000000
04F0EE40h: 00000000 00000000 04D00570 00000D20
04F0EE50h: 00000174 00000000 0000001D 85CF4370
04F0EE60h: 00000000 00000002 01A90000 00000000
04F0EE70h: 04F0FBD0 01AA519D 01A90000 03DBFBF8
04F0EE80h: 00000001 04F0FC68 04F0FC68 04F0FC68
04F0EE90h: 00000000 00000002 04F0FBD8 02538C38
04F0EEA0h: 02530000 00000002 00000000 04F0FC68
04F0EEB0h: 04F0FBEC 00000001 04F0FBF8 778AA604
04F0EEC0h: 02530000 00000001 00000000 00000001
04F0EED0h: 04F0FC68 04F0FC68 00000001 03DBFBF8
04F0EEE0h: 04F0FC98 7787AB6C 77905340 7787A9EA
04F0EEF0h: 04F0200E 7FFDB000 7FFD9000 779051F4
04F0EF00h: 00000000 00000000 00000000 00000000
04F0EF10h: 00000000 00000000 00000000 00000000
04F0EF20h: 00000000 00000024 00000001 00000000
04F0EF30h: 00000000 00000070 FFFFFFFF FFFFFFFF
04F0EF40h: 7787AB15 7787AB53 00000000 00000000
04F0EF50h: 03DBFBF8 02538BE6 7FFD9000 77905D14
Registers:
EAX: 00000000, EBX: 04D00570, ECX: 76FF7E62, EDX: 778A0F34
ESI: 04D008A8, EDI: 00000000, EBP: 04F0FF98, ESP: 04F0EE40
Crash location: "ctasio", loaded at 02480000h - 02497000h
I'm having the same problem with ASIO, X-Fi XtremeMusic, and Vista. Here are the crash reports I get:
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 02484AA1h
Access violation, operation: write, address: 04D00888h
Call path:
This is the first crash logged by this instance.Access violation, operation: write, address: 04D00888h
Stack (04F0EE40h):
04F0EE20h: 00000000 00000000 00000000 00000000
04F0EE30h: 00000000 00000000 00000000 00000000
04F0EE40h: 00000000 00000000 04D00570 00000D20
04F0EE50h: 00000174 00000000 0000001D 85CF4370
04F0EE60h: 00000000 00000002 01A90000 00000000
04F0EE70h: 04F0FBD0 01AA519D 01A90000 03DBFBF8
04F0EE80h: 00000001 04F0FC68 04F0FC68 04F0FC68
04F0EE90h: 00000000 00000002 04F0FBD8 02538C38
04F0EEA0h: 02530000 00000002 00000000 04F0FC68
04F0EEB0h: 04F0FBEC 00000001 04F0FBF8 778AA604
04F0EEC0h: 02530000 00000001 00000000 00000001
04F0EED0h: 04F0FC68 04F0FC68 00000001 03DBFBF8
04F0EEE0h: 04F0FC98 7787AB6C 77905340 7787A9EA
04F0EEF0h: 04F0200E 7FFDB000 7FFD9000 779051F4
04F0EF00h: 00000000 00000000 00000000 00000000
04F0EF10h: 00000000 00000000 00000000 00000000
04F0EF20h: 00000000 00000024 00000001 00000000
04F0EF30h: 00000000 00000070 FFFFFFFF FFFFFFFF
04F0EF40h: 7787AB15 7787AB53 00000000 00000000
04F0EF50h: 03DBFBF8 02538BE6 7FFD9000 77905D14
Registers:
EAX: 00000000, EBX: 04D00570, ECX: 76FF7E62, EDX: 778A0F34
ESI: 04D008A8, EDI: 00000000, EBP: 04F0FF98, ESP: 04F0EE40
Crash location: "ctasio", loaded at 02480000h - 02497000h
It's the ASIO plug-in itself. I think it uses direct monitoring by default, which the X-Fi only supports on creation mode. Thus it crashes in any other mode.
It's the ASIO plug-in itself. I think it uses direct monitoring by default, which the X-Fi only supports on creation mode. Thus it crashes in any other mode.
How is the problem "the ASIO plug-in itself", if the issue only affect users of Creative cards, and even the crash log says that Creative's ASIO driver (ctasio.dll) crashed? I don't know (or want to know) what "direct monitoring" and "creation mode" are. I don't remember seeing references to them in ASIO API specification. If Creative's ASIO implementation requires some Creative-specific settings changed for ASIO to work, it's simply broken.
I can't verify this issue myself, and I'm not interested in spending my money on "high-end" Creative cards just to research this issue, especially that I keep hearing horror stories about X-Fi + Vista issues on daily basis anyway.
PS. Even more proof that the driver is to blame: a process can possibly become immune to killing thru task manager etc only if a kernel/driver call is stuck, which is what apparently happens in this case.
It's the ASIO plug-in itself. I think it uses direct monitoring by default, which the X-Fi only supports on creation mode. Thus it crashes in any other mode.
How is the problem "the ASIO plug-in itself", if the issue only affect users of Creative cards, and even the crash log says that Creative's ASIO driver (ctasio.dll) crashed? I don't know (or want to know) what "direct monitoring" and "creation mode" are. I don't remember seeing references to them in ASIO API specification. If Creative's ASIO implementation requires some Creative-specific settings changed for ASIO to work, it's simply broken.
I can't verify this issue myself, and I'm not interested in spending my money on "high-end" Creative cards just to research this issue, especially that I keep hearing horror stories about X-Fi + Vista issues on daily basis anyway.
PS. Even more proof that the driver is to blame: a process can possibly become immune to killing thru task manager etc only if a kernel/driver call is stuck, which is what apparently happens in this case.
Yes the foobar2000.exe process is impossible to kill after this glitch. This is the only problem I've had with the X-Fi in Vista, but it's really annoying, because I have to use Kernel Streaming which is inconvenient.
But you're saying the problem is with the creative drivers and I'll have to wait for creative to fix it before It can be resolved?
That's exactly what he's saying, yes.
It's the ASIO plug-in itself. I think it uses direct monitoring by default, which the X-Fi only supports on creation mode. Thus it crashes in any other mode.
How is the problem "the ASIO plug-in itself", if the issue only affect users of Creative cards, and even the crash log says that Creative's ASIO driver (ctasio.dll) crashed? I don't know (or want to know) what "direct monitoring" and "creation mode" are. I don't remember seeing references to them in ASIO API specification. If Creative's ASIO implementation requires some Creative-specific settings changed for ASIO to work, it's simply broken.
I can't verify this issue myself, and I'm not interested in spending my money on "high-end" Creative cards just to research this issue, especially that I keep hearing horror stories about X-Fi + Vista issues on daily basis anyway.
PS. Even more proof that the driver is to blame: a process can possibly become immune to killing thru task manager etc only if a kernel/driver call is stuck, which is what apparently happens in this case.
Conversely foobar .9.x is the only ASIO application that crashes my X-Fi (cubase, foobar .8.3 work fine).
(http://img180.imageshack.us/img180/6145/foobarasioeg7.th.jpg) (http://img180.imageshack.us/my.php?image=foobarasioeg7.jpg)
If I enable "direct input monitoring" on foobar .8.3 it will crash the X-Fi much like foobar .9.x crashes the X-Fi. However if I leave direct input monitoring disabled, everything works perfectly (absolutely no crashes). That's why I assumed direct monitoring was the issue with foobar .9 (I guess not?). You don't have to worry about the mode switching (the X-Fi has three modes, creation, gaming, and entertainment) as that's not the problem per say, but direct input monitoring is part of ASIO (not something Creative made up).
I wouldn't normally pester you about a plug-in, but ASIO is the only way to get the X-Fi to automatically change sampling rates (44.1, 48, 96, etc), not even KS works. I was just hoping you could take a look at Otachan's ASIO builds (since they were open sources IIRC) and see what he was doing.
Hi !
Really sorry for my poor English, but I'm very interested by this topic.
WillardJuice said that maybe the direct input monitoring could be the problem.
Peter, I just want to know what do you think about that ?
Do you think is it possible to add this feature (to disable direct input monitoring) ?
Thanks a lot for this plugin, and sorry for the disturb.
I'm confused as to why you need ASIO or KS on Vista at all?
I'm confused as to why you need ASIO or KS on Vista at all?
For the same XP reasons. Why are you confused about that ?
For the same XP reasons. Why are you confused about that ?
Because Vista has an entirely new audio architecture? KMixer isn't in Vista at all.
You don't need ASIO or KS to get bit-perfect output on Vista.
Oh ! Interesting...
When I take the DS output, it's a bit perfect output ? Ok...
But, for the sampling rates, willardjuice said that just the ASIO output support to make a true 44.1 kHz without resampling, is it true ?
Yes, kmixer is not in vista anymore. But you won't get bit perfect when you use DS for sure either. The application must request "Exclusive mode" in order to get bit perfect.
Read http://en.wikipedia.org/wiki/Technical_fea...ows_Vista#Audio (http://en.wikipedia.org/wiki/Technical_features_new_to_Windows_Vista#Audio)
and
http://www.thewhippinpost.co.uk/news/vista...r-musicians.htm (http://www.thewhippinpost.co.uk/news/vista-review-for-musicians.htm)
To be honest I don't really care about those, if I can't find the difference I just use DS.
"The application must request "Exclusive mode" in order to get bit perfect."
Ah yes, that's what it is.
If it's really giving you that much trouble, I wouldn't worry about it.
Thank you thuan for the links.
Very interesting.
I didn't know that the audio part of Windows Vista was totally different from XP, and optimised a lot.
I'm confused as to why you need ASIO or KS on Vista at all?
Well X-Fi users need ASIO. (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=57917&view=findpost&p=520464)
Alright I installed the asio component simply to try and reprodruce this and I simply can't so far. Using foobar2000 0.9.5 beta, x-fi extreme music on Vista x64 with latest drivers ver. 2.15.0004 (05-11-2007) from creative homepage.
Please update to latest creative drivers and see if the problem persists.
I already have the last creative drivers installed(2.15.0004).
I've got Vista 32-bit.
I use foobar 0.9.4.5, I will try with 0.9.5
I have the crash when I stop a song and I want to start another song. I have to do that 3 or 4 times, and the program crash.
I'm happy !!!
With foobar 0.9.5, I haven't got any problems !
I tried to understand why it works now... And the only difference : I haven't installed yet the component for APE files.
So I will try, and maybe I will have crash ?
Edit : Oops ! I spoke too quick. The program crash without the component for APE files...
I was listening a track for 2 minutes, when I decided to change for a track on another format, and crash !
I found a little trick to stop the looping sound and to kill the process when foobar2000 crash.
(I will try to explain, but as you can see, my english is not really perfect, so... )
You have to launch the Creative Console Launcher.
You have to be in Creation Music Mode.
In the up-right window, you've got an option to save your config (there are already some presets like default, RMAA 1644, RMAA 2448 and RMAA 2496).
So, save and name your config ("my preset" for example)
And when you've got the continuous looping sound after the crash, go the Creative Console Launcher and choose your config ("my preset"), and the sound will stop and foobar2000 will stop too !
So, you don't need anymore te reboot your computer.
I hope it can help some of you
Please update to latest creative drivers and see if the problem persists.
It does, try switching songs really fast (the rate in which one changes songs doesn't matter, but it will produce the bug faster).
Crash reproduced. We'll probably look into this, but don't expect too much. ASIO output has very low priority development wise.
Crash reproduced. We'll probably look into this, but don't expect too much. ASIO output has very low priority development wise.
Well I have waited over a year so I think I can hold out a little bit longer.
It's ok even if you don't get around to it, I have learned there is life after ASIO. Don't get me wrong it would makes things easier if it worked, but if I really need ASIO I always have ole' faithful 8.3 to load up.
Crash reproduced. We'll probably look into this, but don't expect too much. ASIO output has very low priority development wise.
Thank you very much !
And no problem for the very low priority, I understand that very well
I can wait.