Hello,
Please,I wanted to know when the asio support 64 bit will be available,without it, I can't see my sound card (lynx), thank you.
Best regards
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
Download foo_out_asio+dsd-0.2.0.zip and install the one that has x64 in the filename
Hello Gus,
thank you, it works again.
Hello Gus,
thank you, it works again.
Welcome! Once installed, click ASIO+DSD in Foobar preferences and select "use 64-bit ASIO drivers"
Hello,
the component asio+dsd 2.0 worked (badly) because there was a tremolo with sputterings, I sent him the report of the bug, moreover it was not possible to bypass the mixer windows, with the version 2.1, no more sound goes out.I have, I think tried all the combination but nothing to make.
On the image with the 32 bit version, no problem, so I use for the moment the asio support made by Mr.Pawlowski which works flawlessly.
When will there be a 64 bit version of asio support, I have to put it on Wishlists?thank you.
Best regards
I still get crashing when playing DSD/SACD ISO files, but this seems to be more about the DAC driver and DAC. I can play the files, but when the last song finishes or I close the player/select Stop, I get a white noise sound and I have to turn off the DAC. WASAPI Exclusive is the only way around this.
CHANGELOG:
09/14/22:
Version 0.2.2 - Channel mapping fixed.
09/12/22:
Version 0.2.1 - Dark mode support added.
09/02/22:
Version 0.2.0 - Experimental: foobar2000 v2.0 support.
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
I still get crashing when playing DSD/SACD ISO files, but this seems to be more about the DAC driver and DAC. I can play the files, but when the last song finishes or I close the player/select Stop, I get a white noise sound and I have to turn off the DAC. WASAPI Exclusive is the only way around this.
Hello,
with the sacd plugin, I don't have any problem, it works very well, only with the dst that had a variable frequency, there was a big cpu consumption and interruptions, I convert the dst to dsd and the problem is solved.
My problem is elsewhere (in 64 bit) because in 32 bit no problem for 7 years.
Your system I do not know, but for mine, I have to use the dephonica sink asio driver for the digital filter and lynx asio from the digital filter to my sound card and nothing else, and the component foo asio support has always done an excellent job.
Best regards
Hello Gus,
I just installed version 2.2 but I don't have any output.
Normally when everything works, the cpu is between 73% and 77%.
Brg
Sorry, I can't help with any issues, this is not my software, and I know basically nothing about ASIO. I'm posting the link to the component for people who may not be aware of it, but I do test if it works...
Of course my setup is vastly different:
Foobar 2.0 x64 beta 7, ASIO+DSD 0.2.2, latest Windows 10 Pro x64, Creative AE-5 sound card with latest Creative drivers running in Stereo mode, output to Stereo speakers.
Playing 24bit/96kHz live radio streams, my CPU usage for both Foobar and ASIOhost64.exe is at most 0.3% each.
ASIO settings in Foobar: "use 64-bit ASIO drivers" "run with high process priority". ASIO drivers at 50ms latency (available range is 2ms - 100ms)
High-Res radio streams, including lossless FLAC: https://www.hiresaudio.online/cd-quality-internet-radio/
Some 24/96 (mainly SuperStereo): https://www.hiresaudio.online/hires-internet-radio/
Official ASIO output component by Peter updated to version 2.2:
https://www.foobar2000.org/components/view/foo_out_asio
Current version: 2.2, released on 2022-09-19
Change log:
Added dark mode support under foobar2000 v2.0
Added 64-bit version for 64-bit foobar2000 v2.0
Supported processor architectures: x86 32-bit, x86 64-bit.
Works with foobar2000 v1.6 and newer
I checked it with Foobar 2.0 x64 beta 8, "run with realtime process priority" enabled, my CPU usage for Foobar and ASIOhost64 is negligible (almost zero).
Fantastic news!
@Peter New foo asio out 64 bit is being recognized as a virus by Avast!!!
Avast is the virus.
Avast is the virus.
Previous one (foo out asio 2.1.2) was OK. After installing foo out asio 2.2 my computer slowed down very much, even when not using foobar nor asio at all. My mouse started to live its own life (beyond my control). After removing 2.2 and manually removing files from "user components" folder, all seems to be normal again.
If this forum has rules that forbid to state that something sounds better than something else without ABX....shouldn't it also apply to such statements as "antivirus is a virus"?? Do you consider Avast a part of some global conspiracy to...to what...to steal out data or to infect our computers...with what? Which commercially available antivirus is not a virus? Are all of them bad or is there any good?
Well, did you try using the new asio component while having avast disabled? Might also solve the problems you described. And of course you can feel free to use whatever software you want, but using Avast without being forced to is beyond me, sorry. https://www.vice.com/en/article/qjdkq7/avast-antivirus-sells-user-browsing-data-investigation
And that's just the tip of the iceberg.
Thank you for this! I have been unable to send DSD files direct without eventually crashing my current and previous DACs (using foo_out_asio+dsd). This works perfectly. Much appreciated!
Well, did you try using the new asio component while having avast disabled? Might also solve the problems you described. And of course you can feel free to use whatever software you want, but using Avast without being forced to is beyond me, sorry. https://www.vice.com/en/article/qjdkq7/avast-antivirus-sells-user-browsing-data-investigation
And that's just the tip of the iceberg.
Yes. I use 3 laptops. I have Avast on 2 of them. I have installed new Asio on 2 of them (1 with avast, after ignoring the security announcement from avast and 1 without avast). The one with avast on it has become slower. It is now ok after removing asio 2.2. I noticed very strange mouse behavior on the laptop without avast, which also stopped after removing Asio 2.2.
I did not have such problems with asio 2.1.2.
It is of course wrong that avast sells our data but who doesn't? Microsoft, Facebook, Whatsup....almost every company does this. Surely most inteligence agencies of "bigger" countries spy on us...is this the reason not to use any antivirus? I suppose we have to choose "lesser evil". But this is off topic.
The topic is: this is great that Peter has updated his component to work with 64bit FB. But why is it considered as a virus (ASIOhost64.exe and ASIOhost32.exe but not foo_out_asio.dll)? If those 2 files are not infected why does avast consider the same files of 2.1.2 version as clean? I just scanned both versions of the component: 2.1.2 is clean and 2.2 has two Malware-gens.
It seems strange to me.
@wojak Anti-virus loves to freak out over .exe files it hasn't seen before or not commonly downloaded. Report a false positive.
If you can't tell Avast to ignore whatever you want ignored, dump it and get something else. That software is there to serve us...not the other way around.
If you can't tell Avast to ignore whatever you want ignored, dump it and get something else. That software is there to serve us...not the other way around.
Method 1:
1. Turn the shields off by right clicking on the Avast icon and choose under "Avast Shield Control" the desired length you want to disable them for, can be all the way up to indefinitely.
2. Go to user interface by left clicking the Avast icon.
2. Go to settings under menu.
3. Go to exceptions.
4. Choose either "add exception" or "add advanced exception".
5. Add the exceptions you want.
6. Turns the shields back on.
Method 2:
1. Right click on Avast icon and choose "Quarantine".
2. Choose the file you wish to restore by highlighting it and clicking on the 3 dots.
3. Choose "Restore and add exception".
Same here. Windows Defender flags this as virus.
Unofficial ASIO+DSD output has been updated a few times since:
CHANGELOG:
10/07/22:
Version 0.3.2 - Transport stream type changed to fp64 (64-bit floating point?)
10/03/22:
Version 0.3.1 - Trace log fixed.
09/29/22:
Version 0.3.0 - Experimental: "Run im separate process" option added.
09/14/22:
Version 0.2.2 - Channel mapping fixed.
09/12/22:
Version 0.2.1 - Dark mode support added.
09/02/22:
Version 0.2.0 - Experimental: foobar2000 v2.0 support.
Running ASIOhost in a seperate process is now an option, if not enabled, you'll only see "foobar2000" in the Windows Task Manager.
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
Minor update for ASIO+DSD:
01/11/23:
Version 0.3.3 - Separate transport streams for DSD and PCM.
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
SACD input also updated:
11/01/23:
Version 1.5.2 - DSD/PCM transition delay added.
https://sourceforge.net/projects/sacddecoder/files/foo_input_sacd/
ASIO+DSD output
01/17/23:
Version 0.3.4 - Seek fixed.
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
ASIO+DSD output
01/25/23:
Version 0.3.5 - Pause handling changed.
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
ASIO+DSD output
01/30/23:
Version 0.3.6 - DSD/PCM transition fixed.
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/