Hello Didier, the sugested VC++ did not solve the problem..tried x86 and 64 bit versions..unfortunately. Kind regards William 16 nov. 2023 17:49:33 Didier Galardon didier22@users.sourceforge.net: Hello william, Unfortunately, I cannot test the plugin on Windows 2012 server. May be it is a problem with the VC++ runtime ? VC redistributable may be downloaded here: https://visualstudio.microsoft.com/fr/vs/older-downloads/ asio2 has been compiled with Visual Studio Express 2017. kind regards, didier...
Hello william, Unfortunately, I cannot test the plugin on Windows 2012 server. May be it is a problem with the VC++ runtime ? VC redistributable may be downloaded here: https://visualstudio.microsoft.com/fr/vs/older-downloads/ asio2 has been compiled with Visual Studio Express 2017. kind regards, didier
so for both plugins wasap2 and asio2 there is a component missing? but what and can I add this myself? according to the makers of Audiophile Optimizer, w2012 is best sounding windows version.. kind regards, william
Windos 2012 issue
I thank you for replying :) Am aware this is primarily a personal needs thing and more than obliged you take the time to share your work! So time is a non-issue, needless to say. Appreciate your looking into the 64-bit compatibility. Regarding your asking "when" (about affinities); You already know 'why' as it's something you'd introduced yourself; if you're wondering why the need to set affinity wherever we want, err, self-explanatory really. Some of us may have workloads that are themselves equally...
Hello, Thank you for you kind message and your wise remarks. I didn't knew that there was a 64 bit variant of Foobar2000. I will check this. I could change the affinity range too. But the problem is when ? I have made some changes since the last published release but the new version, albeit fitting perfectly my needs, is not yet ready for a bigger audience (e.g, I have added support for native DSD but with some limitations: no volume control, only one DSD format supported. This version is more sensible...
Futureproofing
ASIO2 and Foobar V2
Then sit back and enjoy...a rock steady cpu speed with boosts, throttles and other SQ destroying gobbledygook unable to interfere...
After much experimentation and inconsistent SQ...I can say on turbo boost etc... DO NOT touch BIOS and DO NOT use ThrottleStop... Do this instead in power plan settings...see attached pics... Then sit back and enjoy...a rock steady cpu speed with boosts, throttles and other SQ destroying gobbledygook...!
@Didier I know it sounds obsurd but: What did you change from 2.0.1 to 2.0.2/2.0.3? 2.0.2/2.0.3. suddenly sounds different in comparison. What did you change quality wise? Is it the asio driver support < 2? I changed nothing but the foo_out_asio2.dll from 2.0.1 to 2.0.2/2.0.3 in my system and notice a different sound.
@Didier I know it sounds obsurd but: What did you change from 2.0.1 to 2.0.2/2.0.3? 2.0.2/2.0.3. sudenlly sounds differnt in comparison. What did you change quality wise? Is it the asio driver support < 2? I changed nothing but the foo_out_asio2.dll from 2.0.1 to 2.0.2/2.0.3 in my system and notice a different sound.
@Didier I know it sounds obsurd but: What did you change from 2.0.1 to 2.0.2/2.0.3? 2.0.2/2.0.3. sudenlly sounds differnt in comparison. What did you change quality wise? Is it the asio driver support < 2? I changed nothing but the foo_out_asio2.dll from 2.0.2 to 2.0.2/2.0.3 in my system
@Didier I know it sounds obsurd but: What did you change from 2.0.1 to 2.0.2/2.0.3? 2.0.2/2.0.3. sudenlly sounds much better in comparison. The highs are much better. Guitars sound fantastic. What did you change quality wise? Is the asio driver support < 2? I changed nothing but the foo_out_asio2.dll from 2.0.2 to 2.0.2/2.0.3 in my system
@Didier I know it sounds obsurd but: What did you change from 2.0.1 to 2.0.2/2.0.3? 2.0.2/2.0.3. sudenlly sounds much better in comparison. The highs are much better. Guitars sound fantastic. What did you change quality wise? I changed nothing but the foo_out_asio2.dll in my system
@Didier I know it sounds obsurd but: What did you change from 2.0.1 to 2.0.2/2.0.3? 2.0.2/2.0.3. sudenlly sounds harsh in comparison. The highs sound almost distorted and clipped. I changed nothing but the foo_out_asio2.dll in my system
@Didier What did you change from 2.0.2 to 2.0.3? 2.0.3. sudenlly sounds harsh in comparison. The highs sound almost distorted and clipped. I changed nothing but the foo_out_asio2.dll in my system
Confirmed. Same error on DSD file with Asio2 2.0.3. and 2.0.1 (with Super Audio CD Decoder 1.4.3..)
Hi Didier About Asio2 ( 2.0.3 test version ) and foobar volume control, I meet a problem with SACD files: When starting a sacd ( Dop or Native ) with foobar volume at 0 ( full volume ) everything is OK except that If I change the volume , the cursor move but the volume stay full. When starting with volume decreased, the file is not read as SACD but PCM and the sound stay silent. Regards Jean-Claude
But Maxim say he was rewritten it? https://sourceforge.net/p/sacddecoder/support-requests/73/#acd4
Didier-- Ok, thanks. That file worked (I now have 2.0.3 loaded). Sorry if the mistake was on my end earlier--can't explain it. I now can use the Foobar volume control without a problem. However, if I switch output from Foobar exclusive to ASIO2 (while streaming) I get an instant crash. Also, if I switch from ASIO2 to Foobar exclusive, I don't get a crash, but I get, for a while, a double output (like an echo), I assume until the cache runs out, perhaps? At any rate, not a clean switch from one to...
David, the link is good. you have just to copy the foo_out_asio2.dll file in the component directory of your foobar instance then restart foobar. perhaps you have more than 1 foobar instance installed ? or 2 versions of foo_out_asio2.dll in your component directory with different names ? Anyway, you will fin the dll attached. Didier
Hi David I test also the patch but the version is 2.0.3 on my computer Jean-Claude Le 22/06/2022 à 17:49, Nordfinn a écrit : Didier-- Perhaps the file in the link you provided above (https://drive.google.com/file/d/1XoAp95sz6IMDvX_sRbfOiqZx8bfR9knL/view?usp=sharing) is wrong? Once I added it to components, the version comes up as 2.0.2, not 2.0.3. David [tickets:#24] https://sourceforge.net/p/foobar2000-wasap2-output/tickets/24/ Instant crash when starting playback Status: open Milestone: 1.0 Created:...
Didier-- Perhaps the file in the link you provided above (https://drive.google.com/file/d/1XoAp95sz6IMDvX_sRbfOiqZx8bfR9knL/view?usp=sharing) is wrong? Once I added it to components, the version comes up as 2.0.2, not 2.0.3. David
David, Can you check if the patch is installed correctly ? the asio2 patch version should be 2.0.3 in the component view, as shown in the attached picture. If it is not an installation mistake, could you set the trace level to 1 in asio2 advanced options, then, after the crash occurs, send me the crash report files (i.e . failure_xxxxxx.dmp and failure_xxxxxx.txt files) ? could you send me a screen copy of your asio2 advanced options, if ever you changed them ? Thanks Didier
Didier-- Tried the patch (I assume the file belongs in the Components folder with the rest of the component .dll files?). Did not fix the problem. Instant crash when using Foobar volume slider. I'm on Windows 10 Pro, and using an EVGA NU Audio card. Thanks, David
Hi Didier I confirm that I used the latest version (2.0.2) For Native DSD, I use the XMOS USB DAC Driver supplied by SMSL for the 500MK2 Dac. Without inverted phase, the result is perfect. With PCM or flac files, it's also possible to use the DSD Processor and after the transcoder. The result is also very good, slightly different from a basic PCM. Regards
Hello Jean-Claude, Thank you for your feedback. Did you use the latest version before (2.0.2) ? The only difference between the patch and 2.0.2 version is the fix for volume control . There is nothing more regarding sound quality. your config with DSD transcoder is interesting. I did'nt know that it worked with asio2. By the way, I'm working on a new asio2 version and it will support native DSD if everything goes well. best regards
Hi Didier As I met some small problems with asio2, I test this last patch. The problem I met was that with 44100 and 48000 songs, foobar crashed when I use my Presonus studio 192 . So I need to resample to 88200 or 92000 to avoid crashing. With the new patch everything is OK. It was also necessary to keep foobar volume to 0 db to avoid foobar crash. With the new patch , I can change foobar volume without problems. I was also surprised by the audio quality. It was already very good but seems improved....
may you try the patch here: https://drive.google.com/file/d/1XoAp95sz6IMDvX_sRbfOiqZx8bfR9knL/view?usp=sharing it should fix the crash when changing volume. I cannot reproduce the other crash with output change.
Tried the ASIO2 plug-in today. Sounds great, however, I get surprising crashes: If I try to use the Foobar volume slider (but no crash if I use the Windows volume control); also if I change output from another mode (e.g., default exclusive) to ASIO2 (but not if I go from ASIO 2 to default exclusive). Any idea what's going on? Thanks. N.
IT WORKS! Thank you very much.
Hi. good news ! thank you. I have uploaded the new version 2.0.2 with the fix.
Hey, Thank you very much for the patch, it works perfectly now!
Hi, may you try the patch here: https://drive.google.com/file/d/1XoAp95sz6IMDvX_sRbfOiqZx8bfR9knL/view?usp=sharing best regards
Hi, Same issue here. Tried the same, checked the same as Nemes. https://pastebin.com/TyPtDZBX
I checked my driver and firmware and both are up to date according to their website, driver is compatible with ASIO 2.3. I think the best option is the patch but I will try to reinstall the driver at least.
sorry. "Disable Asio config queries" is only in my debug version. it is not set anyway in 1.1beta2 version so I doubt it changes anything. However I see in your crash log that your asio driver is in version 1: "output_asio2_impl::open - asioVersion:2, driverVersion:1, Name:hdspfire, ErrorMessage:No ASIO Driver Error" There is some controls based on asioVersion and driverVersion in asio2 v2.0.x which didn't exist in asio2 v1.1beta2. That could be the cause of the crash. May be you could try to install...
I looked at my advanced config and there was no option to disable asio config queries. I tried setting sample cache size to 32, but it still crashed. Here is the crashlog: https://pastebin.com/5hHVmMTU I decided to revert to an older version to see if my problems persists and with the 1.1 beta2 with the patch I have zero problems and it works perfectly out of the box.
Could you try this changes in advanced config: first set the "Disable Asio config queries" checkbox then try . If it crashes again, reset the checkbox then change the following parameter: "Sample cache size (Mb") : use e.g. 32 instead of 1024, then try
Hey, Everything was on default, the standard asio plugin works perfectly with my DAC. Here is my log with trace level 1 as you requested : https://pastebin.com/51tL06gi
Hi, did you keep the default in advanced asio2 config ? just to know if it could come from your audio card, does it work with the standard asio plugin ? can you send me your log with trace level set to 1 ? (checkbox in asio2 advanced config) Best regards
Instant crash when starting playback
Hi, I have a stupid question. How to get from the level of the asio2 plug to the control panel of the given card? In the official component on the given driver, you had to double-click the left mouse, and here it does not work. Is it possible at all in this plugin? Greetings
Hi, I have a stupid question. How to get from the level of the asio2 plug to the control panel of the given card? In the official component on the given driver, you had to double-click the left mouse, and here it does not work. Is it possible at all in this plugin? Greetings
Hi, I have a stupid question. How to get from the level of the asio2 plug to the control panel of the given card? In the official component on the given driver, you had to double-click the left mouse, and here it does not work. Is it possible at all in this plugin? Greetings
Hi, I have tried to reproduce your problems (using same latency, same cache size, and forcing 24 bits asio buffers) but sorry I can't. I cannot test the Reatek asio driver itself : not compatible with my laptop. the text crash report is not very useful. Normally when foobar crashes there is a file with .dmp suffix in the "<foobar installation="">\profile\crash report" folder. this one could be useful : I can load it in VS debugger. Do you have one and may you send it ? also, could you send me the...
Here we go: I setup two versions of foobar portable 1.6.9 ASIO 2.0.0 Playing just stops but can be resumed by play button. foobar does not crash hence no report. But I was able to crash foobar by switching from my Fiio ASIO to the Realtek ASIO. Crash location: Module: KERNELBASE Offset: 12B522h Symbol: "RaiseException" (+62h) ASIO 2.0.1 foobar crashes now and then. First log is from switching ASIO drivers as described above. Crash location: Module: KERNELBASE Offset: 12B522h Symbol: "RaiseException"...
Hi May be it is a regression in 2.0.1 (there was many bugs in asio2 with this driver , due to its specific asio buffer format, but normally they have been all fixed with the help of Mo Philips). Can you check this ? i.e testing if you have a crash with both 2.0.0 and 2.0.1 or only with 2.0.1. May you also send me: the console output with asio2 trace level set to 1 the generated .dmp file if any. * a screeshot of your advanced settings (cache size,,..) and your asio driver latency settings. I will...
Hi Didier, similar to mo philips I get a crash with my Realtek ASIO driver. There are two newer different Realtek ASIO drivers around afaik : v 1.0.0.7 and v1.0.0.8. As mo philips pointed out he used an older version, I tried both versions and both crashed. Both crash locations are: Symbol: "DllUnregisterServer" (+107CEh) Could you have a quick look at the log please? Maybe it's soley the REALTEK ASIO driver to blame. FiiO driver 5.22.0 works with fantastic sound adn no errors here... Thank you very...
Hi mo philips, did you switch from 1.0.0.8 to 1.0.0.7? Which Reatek ASIO version works for you? thanks a lot
Hi Didier, similar to mo philips I get a crash with my Realtek ASIO driver. There are two newer different Realtek ASIO drivers around afaik : v 1.0.0.7 and v1.0.0.8. As mo philips pointed out he used an older version, I tried both versions and both crashed. Both crash locations are: Symbol: "DllUnregisterServer" (+107CEh) Couls you have a quick look at the log? Thank you very much, still enyoing your fantastic ASIO2 here!
Thanks for your further clarifications. I confess I should have looked at your readme. Sorry. Remember to also update your changelog in the readme :) When people begin to realize what fantastic component this is the downloads will go up and I predict that someday this will be in the official components repository where it belongs (if the developers are not too stubborn). ASIO2 is o much fun! I suggest to call it "ASIO2+Phase" to further point out its powerful features. Now with ASIO Link Pro one...
Thanks for your further clarifications. I confess I should have looked at your readme. Sorry. Remember to also update your changelog in the readme :) When people begin to realize what fantastic component this is the downloads will go up and I predict that someday this will be in the official components repository where it belongs (if the developers are not too stubborn). ASIO2 is o much fun! Now with ASIO Link Pro one could record the ASIO, ASIO+DSD 0.1.6. and ASIO2 streams to actually see if and...
Thanks for your further clarifications. I confess I should have looked at your readme. Sorry. Remember to also update your changelog in the readme :) When people begin to realize what fantastic component this is the downloads will go up and I predict that someday this will be in the official components repository where it belongs (if the developers are not too stubborn). ASIO2 is o much fun! Now with ASIO Link Pro one could record the ASIO, ASIO+DSD 0.1.6. and ASIO2 streams to actually see if and...
great ! thank you for your links and feedback. Very interesting. I think that my CPU (i5-6500) doesn't support speedshift but it is good to know. concerning the sample cache size , it depends on your constraints. Personnally, as I used one dedicated PC for my audio system, I have defined as much memory as possible. if your cache is smaller, foobar wil have to read samples from file and send them to the plugin more often (i.e, ~every minute with a 16Mb cache for a 2 channels 44,1Kz track). I am glad...
For Hanswurst ASIO : DSD Transcoder (Dop/Native ) is OK ASIO : foo_dsd_asio is ok ASIO2 : DSD Transcoder (Dop/Native ) : The sound comes out with a strong sizzle. ASIO2 : foo_dsd_asio : The sound comes out with a strong sizzle. Regards Jean-Claude
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
Hi Didier it's ok now for WMA files Thanks
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 (please update your repo :) ) Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods...
f a n t a s t i c! Can confirm this bugfix works fine with lossy codecs and foo_dsp_convolver_0.4.8 Got you on your explanation for the affinity settings. Super detailed (even avoiding core 0x01). TurboBoost can indeed affect sound quality. I was getting nearly crazy until I figured out what made my DAC crackle. You don't have to do this settings in BIOS though. You can use ThrottleStop. https://www.techpowerup.com/download/techpowerup-throttlestop/ There are two methods of switching CPU frequencies....
Hi, a fix for the WMA codec bug (and for MP3/convolver one) is available in Ticket #23. Regards Didier
The bug in ASIO2 with MP3+convolver is fixed (see attached dll) The bug with WMA codec detected by Jean-Claude (Ticket #22) is fixed too the rule concerning affinity is that the more load there is on your computer, the less this setting is relevant. I think that if you only use it for internet browsing , the affinity setting is still useful. Affinity settings are bitmask . For example , for a CPU with 4 hyperthreaded cores (i/e 8 concurrent threads) , range of the bit mask is 255, i.e 11111111 in...
You're welome. Have you tried the ASIO Proxy Install method? https://sourceforge.net/projects/sacddecoder/files/foo_dsd_asio/
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
You're welcome from my side :)
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
Thanks for the explanation of affinity settings. Do you have any further readings on this? So if I set the affinity to 160/8 this would only be useful if I do nothing than running foobar, right? As soon as I use Firefox for example these setings are pretty much useless? Is there a preferred setting for "multitasking"? Default of 10/5? I didn't see the Sample cache size in advanced options. Thx. What happens if the sample cache size is set to 512MB or 256MB? Any disadvantages? ASIO2 by default uses...
My driver has a lot of features: https://www.thesycon.de/eng/usb_audiodriver.shtml but SMSL seems to have reduced some and Dop DSD disappear in DAC Characteristics. HansWurst , thanks for your Help. Didier, I understand that it is seems very complex to take into account Native DSD in ASIO2. Thanks to have clarified all this. Regards
Hi I am not a specialist of DSD (I only listen to PCM in my system), but I think that Jean-Claude is right when he says that SACD plugin used with ASIO or ASIO2 plugin only supports DSD with DoP. Otherwise the DAC would not be able to make a difference between PCM 176Kz samples and raw DSD64 stream. When looking at the Steinberg ASIO API spec, the Asio plugin should ask for specific type of ASIO buffer when initiliazing the Asio driver, in order to use native DSD. ASIO2 plugin doesn't do this and...
With ASIO2 + SACD plugin 1.4.3 (foo_input_sacd) DSD is not converted to PCM. It is wrapped in PCM and unpacked by the chip of your DAC. There is no transcoding afaik. You can select between PCM, DSD and PCM+DSD in the SACD Tools options. If your DAC doesn't allow DoP (DSD with PCM wrapping) but only native DSD then simply select DSD here. I don't quite understand your point because foo_out_asio+dsd-0.1.6 should do exactly the same. Only the ASIO components are different Edit:Specs of your DAC https://www.akm.com/content/dam/documents/products/audio/audio-dac/ak4497eq/ak4497eq-en-datasheet.pdf...
With ASIO2 + SACD plugin 1.4.3 (foo_input_sacd) DSD is not converted to PCM. It is wrapped in PCM and unpacked by the chip of your DAC. There is no transcoding afaik. You can select between PCM, DSD and PCM+DSD in the SACD Tools options. If your DAC doesn't allow DoP (DSD with PCM wrapping) but only native DSD then simply select DSD here. I don't quite understand your point because foo_out_asio+dsd-0.1.6 should do exactly the same. Only the ASIO components are different Edit:Specs of your DAC https://www.akm.com/content/dam/documents/products/audio/audio-dac/ak4497eq/ak4497eq-en-datasheet.pdf...
With ASIO2 + SACD plugin 1.4.3 (foo_input_sacd) DSD is not converted to PCM. It is wrapped in PCM and unpacked by the chip of your DAC. There is no transcoding afaik. You can select between PCM, DSD and PCM+DSD in the SACD Tools options. If your DAC doesn't allow DoP (DSD with PCM wrapping) but only native DSD then simply select DSD here. I don't quite understand your point because foo_out_asio+dsd-0.1.6 should do exactly the same. Only the ASIO components are different Edit:Specs of your DAC https://www.akm.com/content/dam/documents/products/audio/audio-dac/ak4497eq/ak4497eq-en-datasheet.pdf...
With ASIO2 + SACD plugin 1.4.3 (foo_input_sacd) DSD is not converted to PCM. It is wrapped in PCM and unpacked by the chip of your DAC. There is no transcoding afaik. You can select between PCM, DSD and PCM+DSD in the SACD Tools options. If your DAC doesn't allow DoP (DSD with PCM wrapping) but only native DSD then simply select DSD here. I don't quite understand your point because foo_out_asio+dsd-0.1.6 should do exactly the same. Only the ASIO components are different Edit:Specs of your DAC https://www.akm.com/content/dam/documents/products/audio/audio-dac/ak4497eq/ak4497eq-en-datasheet.pdf...
With ASIO2 + SACD plugin 1.4.3 (foo_input_sacd) DSD is not converted to PCM. It is wrapped in PCM and unpacked by the chip of your DAC. There is no transcoding afaik. You can select between PCM, DSD and PCM+DSD in the SACD Tools options. If your DAC doesn't allow DoP (DSD with PCM wrapping) but only native DSD then simply select DSD here. I don't quite understand your point because foo_out_asio+dsd-0.1.6 should do exactly the same. Only the ASIO components are different Edit:Specs of your DAC https://www.akm.com/content/dam/documents/products/audio/audio-dac/ak4497eq/ak4497eq-en-datasheet.pdf...
With ASIO2 + SACD plugin 1.4.3 (foo_input_sacd) DSD is not converted to PCM. It is wrapped in PCM and unpacked by the chip of your DAC. There is no transcoding afaik. You can select between PCM, DSD and PCM+DSD in the SACD Tools options. If your DAC doesn't allow DoP (DSD with PCM wrapping) but only native DSD then simply select DSD here. I don't quite understand your point because foo_out_asio+dsd-0.1.6 should do exactly the same. Only the ASIO components are different Edit:Specs of your DAC https://www.akm.com/content/dam/documents/products/audio/audio-dac/ak4497eq/ak4497eq-en-datasheet.pdf...
Hi Affinity settings aim at avoiding mixing different plugin activities (i.e filling the sample cache vs passing samples to the driver) on the same CPU cores. Of course these parameters are relevant only if your computer is dedicated to audio (I.e if you don't use for something else at the same time) Regarding your system (4 cores/8 threads Intel i7-8550u), you could try : Asio Affinity:160 (128+32) Input Affinity:8 Concerning RAM usage, asio2 plugin uses a sample cache. By default (Sample Cache...
With ASIO2 + SACD plugin 1.4.3 (foo_input_sacd) DSD is not converted to PCM. It is wrapped in PCM and unpacked by the chip of your DAC. There is no transcoding afaik. You can select between PCM, DSD and PCM+DSD in the SACD Tools options. If your DAC doesn't allow DoP (DSD with PCM wrapping) but only native DSD then simply select DSD here. I don't quite understand your point because foo_out_asio+dsd-0.1.6 should do exactly the same. Only the ASIO components are different
With ASIO2 is + SACD plugin 1.4.3 (foo_input_sacd) DSD is not converted to PCM. It is wrapped in PCM and unpacked by the chip of your DAC. There is no transcoding. You can select between PCM, DSD and PCM+DSD in the SACD Tools options. If your DAC doesn't allow DoP (DSD with PCM wrapping) but only native DSD then simply select DSD here. I don't quite understand your point because foo_out_asio+dsd-0.1.6 should do exactly the same. Only the ASIO components are different
According to the readme of the foo_input_sacd I believe that the DSD send to the DAC is a Dop one: "If your DAC supports DoP through ASIO/WASAPI/DS driver you can set up DSD playback: 1. Open File->Preferences->Tools->SACD page. 2. Select "DSD" for "Type" in "Output (per device)"section." It is necessary to use the Transcoder, so ASIO instead of ASIO2 to get Native DSD, or the new ASIO+DSD. My DAC does'nt allow Dop DSD, so I open this ticket... If I compare SQ on my DAC with native DSD, ASIO+DSD...
I can perfectly output native DSD with ASIO2 + SACD plugin 1.4.3 on my FiiO Q1 Mark II with its DAC Driver 5.22.0 (TheSycon). If looking closely to the ASIO control panel the DSD file while playing even switches the sample rate and goes back if non DSD file is played. DSD indicator LED also lights on the FiiO. So ASIO2 and native DSD work fine here. Seems to be your ASIO driver. What does it matter if one sends DSD as DoP (wrapped as PCM)? Quote "DAC will strip this wrapper and send the native DSD...