HydrogenAudio

Hosted Forums => foobar2000 => Support - (fb2k) => Topic started by: Nordfinn on 2011-12-18 16:19:36

Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-18 16:19:36
Old driver worked perfectly for me.  This one is not working.  I have updated components before with no problems, and can't see that I am doing anything wrong, but, get this message:

Unrecoverable playback error: Could not start the worker process - The system cannot find the file specified.

The driver is in the components folder with the rest of the drivers, however.

I read your disclaimer about ASIO, but this mode is important to me.  I switch back and forth a lot between internet radio stations, some at 48,000 some at 44.1.  If I use my card's (Asus Xonar Essence) interface, I have to switch back and forth manually.  (And definitely sounds better, despite your disclaimer.)

The old driver has apparently disappeared from my system with the update.  Can I get it, please?

Thanks much,
N.

Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: kode54 on 2011-12-18 16:27:15
Hi. If you looked at the contents of the archive properly, you would have noticed there are two executable files (.EXE) bundled with it. Those need to be unpacked wherever you placed the component. This is done for you automatically if you use the built-in component installer.

Using the built-in installer is as easy as opening the Preferences, selecting the Components section at the top if necessary, then dragging the downloaded ZIP file onto that page. Or clicking the Install... button there and selecting it manually.

An added benefit to installing that way is that if you click the Get Updates button on that page, or select "Check for updated components" from the Help menu, it will automatically poll the foobar2000 component repository for updates to listed components, then download them for you.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-18 17:01:54
Thanks very much.  I removed and then reinstalled as you suggested (dragged the whole zip to the components page).  The component is listed.  However, not working.  Get this error message:

Unrecoverable playback error: The process receiving or sending data has terminated

Strangely, the ASIO driver does not appear in the Components folder with the rest of the Foobar drivers. 

Am I yet doing something wrong?

Running XP, and the troubleshooter says I do not have any problematic components.

N.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: shakey_snake on 2011-12-18 17:14:32
Strangely, the ASIO driver does not appear in the Components folder with the rest of the Foobar drivers. 

Am I yet doing something wrong?
No.
With a standard (not-portable) install, components installed using the component installer are stored in your User configuration folder, not the foobar2000 install folder.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-18 17:38:33
Version 2.0.2 is up on the site, among other things it corrects incompatibility with Windows XP.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-18 17:54:01
New error messages: Unrecoverable playback error: Could not set sample rate to 44100 Hz; Unrecoverable playback error: Could not set sample rate to 48000 Hz

2.02 installed, but will not play, get the above error messages.
Thanks, Peter, for Foobar.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-18 18:39:41
Well, that's progress. Please try the test version I've attached to this post, it attempts to mimic behaviors of the old component.

[attachment removed - newer version up on the site]
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: mikk on 2011-12-18 19:20:47
Hi, with new 2.x asio plugins, my kx asio device is disappear. Version 1.2.7 is working.

With 2.x, output/asio tools/add new: no asio drivers found.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Mr.Grey on 2011-12-18 19:26:22
Hi, with new 2.x asio plugins, my kx asio device is disappear. Version 1.2.7 is working.

With 2.x, output/asio tools/add new: no asio drivers found.

ASIOhost32.exe & ASIOhost64.exe in component's folder?
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: kode54 on 2011-12-18 19:30:10
With 2.x, output/asio tools/add new: no asio drivers found.

Try 2.0.2, that fixes it for Windows XP.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-18 19:46:00
ASIOhost32.exe & ASIOhost64.exe in component's folder?

For one last time: do not install components manually into the "components" folder. Use the "Components" preferences page to do this properly.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: mikk on 2011-12-18 19:55:03
Hi, with new 2.x asio plugins, my kx asio device is disappear. Version 1.2.7 is working.

With 2.x, output/asio tools/add new: no asio drivers found.

ASIOhost32.exe & ASIOhost64.exe in component's folder?


Hi, yes, under ...\AppData\Roaming\foobar2000\user-components\foo_out_asio directory. Plugin version is 2.0.2.

Win7 x64
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Mr.Grey on 2011-12-18 19:56:45
I mean foo_out_asio folder
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: mikk on 2011-12-18 19:57:59
ASIOhost32.exe & ASIOhost64.exe in component's folder?

For one last time: do not install components manually into the "components" folder. Use the "Components" preferences page to do this properly.

Hi!

I read changelog, I already know this, I use always install function to install plugins.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Case on 2011-12-18 20:01:10
mikk, can you try deleting ASIOhost64.exe from the directory where the component is installed to and make a copy of ASIOhost32.exe with ASIOhost64.exe name. It looks like kX drivers have no 64 bit ASIO support.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-18 20:01:18
Well, that's progress. Please try the test version I've attached to this post, it attempts to mimic behaviors of the old component.

Well, it works in the sense that will play, and I don't get error messages.  But something is plainly wrong: Sound quality is extremely compromised (intermittent and underwater-sounding).  Not always, but like halt the time. 
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: mikk on 2011-12-18 20:02:29
I mean foo_out_asio folder

Directory mean folder for me.

Under c:\Users\mikk\AppData\Roaming\foobar2000\user-components\foo_out_asio folder found these files:

ASIOhost64.exe
ASIOhost32.exe
foo_out_asio.dll

But this is not component install error, because 1.2.7 version is working after installed.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: mikk on 2011-12-18 20:06:13
mikk, can you try deleting ASIOhost64.exe from the directory where the component is installed to and make a copy of ASIOhost32.exe with ASIOhost64.exe name. It looks like kX drivers have no 64 bit ASIO support.

Hi, good idea, but after foobar is started I get error message: internal error, one or more installed components have been damaged, after foobar is exited.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Mr.Grey on 2011-12-18 20:08:45
I mean foo_out_asio folder

Directory mean folder for me.

Under c:\Users\mikk\AppData\Roaming\foobar2000\user-components\foo_out_asio folder found these files:

ASIOhost64.exe
ASIOhost32.exe
foo_out_asio.dll

But this is not component install error, because 1.2.7 version is working after installed.

without ASIOhostXX.exe I have the same error
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-18 20:20:08
Well, that's progress. Please try the test version I've attached to this post, it attempts to mimic behaviors of the old component.

Well, it works in the sense that will play, and I don't get error messages.  But something is plainly wrong: Sound quality is extremely compromised (intermittent and underwater-sounding).  Not always, but like halt the time.

Trying to figure out what is going on.  Problem seems worst on the Vorbis streams.
Can I get the old driver?
Thanks.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Case on 2011-12-18 20:50:10
Sticking to old version is not a solution. The new component is supposed to be superior in any way. It already includes several workarounds for known issues in various drivers that old version didn't have but there are some bugs that need to be sorted.
Are you using some very small output buffer size in ASIO driver's preferences or in foobar2000 output preferences? That could explain the glitching you hear. You can access driver's options in Asio tools if you Click Add. There's a button to configure driver.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Case on 2011-12-18 21:10:50
Version 2.0.3 (http://www.foobar2000.org/components/view/foo_out_asio) was just uploaded. It fixes issues in 32-bit ASIO host and won't use 64 bit version unless user manually selects it. kX drivers should output sound with this one now.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: kraut on 2011-12-18 21:26:36
I have tried twice to install new version. I use m-audio 1010LT sound card.
In the asio virtual device editor the version 2.02 sees the sound card channels.
Trying to use the version i still get error message.

I tried again upgrade, version is now 2.03. Seems to be working fine.

Thanks.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-19 01:01:15
Problems with 2.0.3: Almost working, but some streams I have to start twice before they sound right.  First time: intermittent, chugging, and wrong speed.  Second time: sounds great.  Can't see a pattern as to which kind of stream (AAC, MP3, Vorbis) affected.  I am using a plenty big buffer (same as with previous driver).
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: keijo on 2011-12-19 01:12:03
I have tried twice to install new version. I use m-audio 1010LT sound card.
In the asio virtual device editor the version 2.02 sees the sound card channels.
Trying to use the version i still get error message.

I tried again upgrade, version is now 2.03. Seems to be working fine.

Thanks.


I have also M-Audio sound card, Delta Audiophile 2496 and my OS is Server 2008 R2. Foobar2000 is version 1.1.10.

ASIO output doesn't work here yet with this 2.03 version either. After installing it Foobar asks if it is ok to restart program, and when it does it gives just error message "Internal error - one or more of the installed components have been damaged".
Then it is needed to start Foobar in safemode and remove ASIO output driver.

Why i don't use Wasapi then? It gives me crackling noise. Not as much as Direct Sound does. Wasapi worked quite well without any crackling for awhile but suddenly it started to act badly as well.

Main problem with WASAPI is that if i have any web browser open when i use foobar2000, audio from that browser wont work anymore after that.
Like if i have youtube video open and i watch half of it and then pause for awhile, listen some music with foobar and when i want to continue watching that video i have to close browser, restart audio service, reopen browser, restore session to get all tabs back, choose right tab and find a spot where i was left.
I did that procedure at least couple hundred times before i decided that it's too time consuming to do constantly.

I tried to find other audio programs that i would like as much as foobar2000 but there weren't any.
Then i found out that ASIO output driver. Too bad that it didn't help in my situation here.

Instead i installed KS output driver which seems to work just fine. Now i have used it just about one hour so i'm not 100% sure but looks promising.
Even though it was said to be unstable and experimental. And was made 5 years ago.

Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: A_Man_Eating_Duck on 2011-12-19 01:28:25
@keijo

Have you upgraded to the very latest drivers m-audio drivers from THIS (http://forums.m-audio.com/showthread.php?24052-**-Official-Update-Announcements-**-Delta-Series-Drivers-Updated-6-1) thread?
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-19 07:41:06
ASIO output doesn't work here yet with this 2.03 version either. After installing it Foobar asks if it is ok to restart program, and when it does it gives just error message "Internal error - one or more of the installed components have been damaged".
Then it is needed to start Foobar in safemode and remove ASIO output driver.

Open the components preferences page and install the whole zip you downloaded, not just the DLL alone.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: kraut on 2011-12-19 08:21:56
I just went to preferences, components page, and selected: get updates, then apply and restart.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: mikk on 2011-12-19 09:24:03
Version 2.0.3 (http://www.foobar2000.org/components/view/foo_out_asio) was just uploaded. It fixes issues in 32-bit ASIO host and won't use 64 bit version unless user manually selects it. kX drivers should output sound with this one now.

Hi, this version is working again, thanks.

+ Info:
My kx driver version is 3551, this is latest (beta) driver with win7 support.
My system is Win7x64. I use kxmixer x86 version, because many kx plugins is only x86 compatible. When windows is starting, kxmixer x86 version is started automatically, instead of kxmixer x64 version.
Now I thinking, and after I try start kxmixer x64 version. Well, ver 2.0.2 Asio plugin is working. lol.
After windows is started, and kxmixer x86 version is loaded, ver 2.0.2 Asio plugin is working... Certainly 2.0.3 is working (32 or 64 bit).
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-19 09:54:01
Problems with 2.0.3: Almost working, but some streams I have to start twice before they sound right.  First time: intermittent, chugging, and wrong speed.  Second time: sounds great.  Can't see a pattern as to which kind of stream (AAC, MP3, Vorbis) affected.  I am using a plenty big buffer (same as with previous driver).

Would be very nice if you could provide a recording of this.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Seeking_Lossless on 2011-12-19 10:00:27
I'm using Lexicon Lambda with Foobar version 1.1.10. Works fine here via automatic update (ASIO 2.0.3). Anyway, thanks Peter for still developing this plug-in.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-19 11:50:26
Problems with 2.0.3: Almost working, but some streams I have to start twice before they sound right.  First time: intermittent, chugging, and wrong speed.  Second time: sounds great.  Can't see a pattern as to which kind of stream (AAC, MP3, Vorbis) affected.  I am using a plenty big buffer (same as with previous driver).

Would be very nice if you could provide a recording of this.

Will give it a try.  Will have to teach myself how.  Thanks.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: a3aan on 2011-12-19 12:54:07
The new asio driver (up to 2.0.3) sometimes causes some sort of sync issue. This results in a lot of added noise. After hitting pause and play all is fine again. I think the old driver had the same or similar issue, but *much* more rarely. I'm using Win7/64 and a Emu 0404usb with latest beta drivers.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-19 13:24:27
Would be very nice if you could provide a recording of this.
Sorry, Peter.  Cannot find a way to do so (can't find a way to point Audacity to the ASIO driver as source; will only record Asus driver).  However, see last post by a3aan.  Sounds like the same problem.  Thanks.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Case on 2011-12-19 16:25:35
If you have a loopback cable to connect the speaker output to line-in you could make an analog recording. That should be good enough.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-19 17:48:38
Problems with 2.0.3: Almost working, but some streams I have to start twice before they sound right.  First time: intermittent, chugging, and wrong speed.  Second time: sounds great.  Can't see a pattern as to which kind of stream (AAC, MP3, Vorbis) affected.  I am using a plenty big buffer (same as with previous driver).

Would be very nice if you could provide a recording of this.

Ok.  Managed to record a sample.  Thanks Case. If someone could please let me know how to attach the file to one of these posts, or where to post the file elsewhere, would be appreciated.  (I do not see an attachment option here.)
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: db1989 on 2011-12-19 18:05:24
http://www.hydrogenaudio.org/forums/index.php?showforum=35 (http://www.hydrogenaudio.org/forums/index.php?showforum=35)
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-19 18:32:16
http://www.hydrogenaudio.org/forums/index.php?showforum=35 (http://www.hydrogenaudio.org/forums/index.php?showforum=35)

Thanks.  Posted to Uploads thread.  Topic "Problem sample for new ASIO driver (http://www.hydrogenaudio.org/forums/index.php?showtopic=92465)"
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-19 20:43:00
New update attached - may or may not help.
There have been fixes specific to bugs found on machines with X-Fi cards (last Xonar "fix" broke X-Fi instead).
Please report if it makes things better/worse on Xonars. I've not yet done anything to specifically address the issue Nordfinn is having, but I've changed initialization function call order to more closely mimic the old component, so maybe certain oddball issues that didn't happen with foo_out_asio 1.x will now go away.

Attachment removed - newer version up on the site
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-19 21:05:03
This is working for me.  Problem solved: everything opening cleanly.
Thanks, Peter.
Nordfinn
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-20 08:19:03
Version 2.0.4 released.

For anyone else writing ASIO software, here's the apparent standard for ASIO initialization call order (do it differently and Asus/Creative drivers will explode in your face):

canSampleRate(); // Not sure if needed
getChannels(); // Necessary before getChannelInfo() even if you already know the channel count or else Creative will hate you.
setSampleRate(); // Necessary before createBuffers() or else Asus will hate you. Doing it before getChannels() isn't good either.
getChannelInfo();
getBufferSize();
createBuffers();


I'd like to mention that Asus Xonar drivers are responsible for 50% of all ASIO related crash reports that I've received for the old ASIO plug-in. The new plug-in is now capable of surviving these without taking foobar2000 down, but audio playback will still be interrupted. For this reason I do not recommend using ASIO for playback as despite of my best efforts it's likely still buggier than regular DirectSound, at least with cards such as Xonar.


Addendum - on device control panels:
Some drivers (M-Audio) fail to call InitCommonControls() before spawning their dialogs and their dialogs don't work if your app hasn't done InitCommonControls() before.
Idiot award goes to ASIO4ALL which spawns a modeless dialog without giving the calling context a sane way to know whether the dialog is still running. Also hangs in CoUninitialize() - AFTER closing the dialog - on my WinXP VM.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: helohe on 2011-12-20 13:46:28
with the old plugin, I used to get a BSOD when playing music in a playlist and some files have different sampling rate and bitrate. for example
I play 16 /44.1 files and then the next file is 24/192 or 24/176.4. when the switching occours I got bsod. I have a "buggy" asus xonar essence st card, with newest asus drivers. the bsod message with the old plugin was some error in cmudaxp.sys :

Source
Windows

Summary
Shut down unexpectedly

Date
‎28.‎10.‎2011 01:52

Status
Report sent

Problem signature
Problem Event Name:    BlueScreen
OS Version:    6.1.7601.2.1.0.256.1
Locale ID:    2055

Extra information about the problem
BCCode:    d1
BCP1:    0000000000000798
BCP2:    0000000000000002
BCP3:    0000000000000001
BCP4:    FFFFF880044532AD
OS Version:    6_1_7601
Service Pack:    1_0
Product:    256_1
Bucket ID:    X64_0xD1_cmudaxp+272ad
Server information:    4c7d45a6-8171-48da-a430-6633e3c34bee

I haven't tested your new plugin yet, because I prefer to avoid bsod again
I switched to WASAPI because of that problem. but wasapi doesn't automatically set the sampling rate, I have to set it for each (different) file manually in the asus controll panel. also even though WASAPI in exclusive mode mutes other sounds well, each time there is another sound playing, like a beep in windows or whatever, there is a short interruption of playback. also wasapi exclusive mode doesn't work for 16/44.1 files.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-20 13:58:53
I'm having trouble understanding why Xonar is so popular - it comes with ridiculously buggy drivers, it has already wasted countless hours of my development time, and it sounds like it's more trouble than it's worth for its users.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Nordfinn on 2011-12-20 14:10:41
Helohe--Just to say that I have exactly the same card and drivers (running XP), and have never experienced any of these problems, and I switch sample rates often (but note that the card does not support 176).  Possible you have bad hardware?  I have found Asus responsive, when I've dinged them.

2.0.4 driver working great so far.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Kurtegikov on 2011-12-20 15:12:48
Hello, I have a question about ASIO behavior: I understand that it is supposed to block other system sounds and sounds from other sources like other players, browsers etc. But i noticed this strange behaviour: when i play music with foobar2000 using ASIO output other programms like for example Firefox browser having troubles opening html documents, i have saved html document and when i try to open it with firefox, it will be opening for like 50 seconds instead of 1-2 seconfs if i use any other output, or for example if i press open containing folder in foobar2000 it would freeze foobar2000 interface and will be opening it for like 40 seconds to 1 minute instead of doing it instanly, or if i use Foo_run script to open a link in firefox from foobar2000 it would again freeze foobar2000 interface ( music would continue playing OK) and will be opening the link for a minute or so.


Is there any way to fix it, anyone know what the problem is or is it a normal behaviour for this protocol?

System is 32 bit XP SP 3 and soundcard:ASUS XONAR Essence ST with latest drivers.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: helohe on 2011-12-20 15:13:51
I only had the problem with asio. I'm using win7 64bit. I think the driver is buggy, maybe it has a problem with 64bit windows.

24/176.4 works fine using asio, I think it is getting upsampled to 192 or downsampled to 96. 176.4 is usually used when playing back dsd materials (using the sacd decoder plugin, the plugin unfortunately doensn't allow setting a sample rate of 192 or 96)
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Seeking_Lossless on 2011-12-21 09:56:45
I'm having trouble understanding why Xonar is so popular - it comes with ridiculously buggy drivers, it has already wasted countless hours of my development time, and it sounds like it's more trouble than it's worth for its users.

I agree. Xonar user, can you all please settle with DirectSound or Wasapi in the mean time? Please understand Peter, he do this probably by himself and without any incentive. Honestly, most complaint that i read came from Xonar user. I'm using Lexicon Lambda which is 3- 4 years ago came with very buggy driver, BSOD was no stranger. But a year later they begin releasing much more stable driver with each releases. So maybe you guys should push Asus for stable driver instead.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-21 10:47:56
Xonar DirectSound was buggy too until I came up with a solution to dodge their lame dsound.dll hook recently. Oh wait, don't tell Asus that I dodge their hooks or they might "fix" my "fix" with the next update.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Seeking_Lossless on 2011-12-21 11:48:57
Is that true? Even with DirectSound? I think people should slow down when recommending the product, until they fix the buggy driver. This remind me of Audiotrak Prodigy and ESI Juli@ couple years ago, from what i read it's not doubt a great card and always recommended by most audio sites and magazine, but shipped with very buggy driver. So, the cards not quite reach it's full potential using modern OS with those buggy driver. I'm glad that i chose Lexicon Lambda for my desktop recording. At least their driver is stable since 2 years ago.

Okay, this is going off-topic and i will stop now. But for the last, please Xonar user, let Peter solve the problem at his pace.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: MaceDD on 2011-12-22 16:50:31
Ola,

I'm the new guy.

The New Plugin is working fine. First I had some problems to get the plugin to work and foobar said that the plugin is broken. But I just forgot to copy both EXE-files into the component folder.

Furthermore the new plugin found the build-in ASIO of my UNI Xonar driver (modded Asus driver) and it works wonderfully. Don't need WASAPI and ASIO4All anymore. Thanks a lot Peter.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: NEMO7538 on 2011-12-22 19:42:50
Version 2.0.4 does not work here (Win XP Pro SP3 32 bits, USB Soundblaster HD, Thinkpad T60 laptop).
I used the built-in component updater.
The soundcard does not appear in playback/output/asio
Tried ASIO4ALL but the entry does not provide the mapping to the Soundblaster. (It did with version 1.2.7)
DS works fine however
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: MaceDD on 2011-12-23 02:59:38
Version 2.0.4 does not work here (Win XP Pro SP3 32 bits, USB Soundblaster HD, Thinkpad T60 laptop).
I used the built-in component updater.
The soundcard does not appear in playback/output/asio
Tried ASIO4ALL but the entry does not provide the mapping to the Soundblaster. (It did with version 1.2.7)
DS works fine however


Try to install that plugin manually. That should work. Don't forget to update your sound-driver of course.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Kohlrabi on 2011-12-23 07:34:20
Try to install that plugin manually.

Since at least two "bug" reports in here were based on wrong installation of the plugin, please do not recommend or encourage this behaviour.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Oery on 2011-12-23 08:23:02
v2.0.4 work fine, on my both system:
1. X-FI XtremeMusic, Creative Sound Blaster X-Fi series driver 2.18.0015 - Windows7 x86-SP1
2. Prodigy Audiotrak HD2, ESI Driver v1.08 - WindowsXP Pro SP3

Thx Peter
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Peter on 2011-12-23 13:06:52
Version 2.0.4 does not work here (Win XP Pro SP3 32 bits, USB Soundblaster HD, Thinkpad T60 laptop).
I used the built-in component updater.
The soundcard does not appear in playback/output/asio
If no matching entry shows in the output device list, your soundcard does not support ASIO. Quick google search reveals that USB SoundBlaster cards do not support ASIO.
Quote
Tried ASIO4ALL but the entry does not provide the mapping to the Soundblaster. (It did with version 1.2.7)
DS works fine however
Tested ASIO4ALL on a Windows XP virtual machine, playback works correctly. Their configuration dialog doesn't quite work correctly, I'll see if this can be worked around.


Note that as for 2.0.4, botched manual installs block foobar2000 startup entirely to prevent nonsensical bug reports.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Jackal29a on 2011-12-23 20:15:55
Installed 2.0.4 on my 2 PCs (both Foobar 1.1.10 running onW7 Pro SP1 x86, one with Musiland 02, the other Xonar D2X) and not only works in both, it does so beautifully. Thx Peter, you are a star mate.

Cheers
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: exa065 on 2012-01-10 12:23:17
I am unable to debug an ASIO driver in VisualStudio2008 against the new foo_out_asio 2.1 component.  Visual Studio would not stop at any breakpoints in my code. I can debug fine when using the old foo_out_asio.dll.  I am not sure if I am doing something wrong. Are there any special configuration  requirements for debugging?

OK, I found the answer. I have to attach to ASIOhost32.exe.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Gainless on 2012-01-13 08:57:43
Just wanted to mention that I get several timeouts at playback since I use the new version 2.1, everything else (except for a little reaction delay) is fine.
I'm using the NI Audio 2 DJ, which is already known for troublesome ASIO drivers.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Dexter_prog on 2012-01-13 19:45:37
I think the delay is gone for me, but it is still very sensible to CPU load and usually it going over 80-85 produces pops and crackles.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Dandruff on 2012-01-16 11:28:23
Cool, ASIO support version 2.1 doesn't even need the "Convert mono to stereo" DSP anymore. Thanks! Mono files now play fine to stereo outputs (Left+Right) by default.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: exa065 on 2012-01-16 17:33:15
Cool, ASIO support version 2.1 doesn't even need the "Convert mono to stereo" DSP anymore. Thanks! Mono files now play fine to stereo outputs (Left+Right) by default.


Is there any other processing performed by the driver, besides sensing mono to L and R channels? Is the new ASIO driver bit-perfect under all usage scenarios? 

Thanks,

George
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Dexter_prog on 2012-02-04 17:24:28
I think the delay is gone for me, but it is still very sensible to CPU load and usually it going over 80-85 produces pops and crackles.


New version (2.1.1) is supposed to address this:
Quote
Version 2.1.1 highlights:
* New "high process priority" option for dodgy drivers that stutter under high CPU load.

http://www.foobar2000.org/components/view/foo_out_asio (http://www.foobar2000.org/components/view/foo_out_asio)

Even though I laughed at "dodgy drivers" (Focusrite drivers being dodgy, yeah, right), I am trying it now. I'll post back.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Dexter_prog on 2012-02-04 19:59:32
Well, still skippy at >90% of cpu usage.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Dandruff on 2012-02-07 08:41:30
Not skippy here under high CPU load (RME HDSP 9632, WinXP SP3).
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: takoyaki on 2012-03-24 13:31:37
I have audiophilleo1 which can bit-perfect test.

foo_out_asio 2.1.1 didn't pass the bit-perfect test.   
but foo_out_asio 1.2.7 was okay...
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: Sandrine on 2012-03-24 13:40:15
What was your DSP chain? Replaygain on or off?
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: takoyaki on 2012-03-24 15:41:55
What was your DSP chain? Replaygain on or off?


no DSPs.
no Replaygain.
Title: New ASIO driver: issues, bug/problem reports, etc.
Post by: ekzotic on 2012-08-18 11:15:36
in win8 i should have set win7 compatibility on asiohost.exe