3.Also when in Kernel Streaming (which generally speaking I prefer) after the first playback the driver option dissapears from foobar/output settings even though the device is playing as normal. Amanero KS dissapears from the selection panel to appear again only when OS is restarted!!
Anyone else noticed something like this?
I've been seeing the same issue here - I thought it was a problem with my Foobar setup - glad it's no just me. I need to explore this some more, but it does sound like a driver bug. Hopefully this can be fixed by Amanero.
I am also glad to see its not just me either, some other friends also face the exact same issue reported here http://www.diyaudio.com/forums/digi...ro-384-kernel-streaming-wasapi-win764bit.html
I have to underline that the issue persists even after succesfully updated firmware and latest (v1.05) driver.
It definately looks to be a driver bug.
I think its about time for amanero to look into it.
I have to underline that the issue persists even after succesfully updated firmware and latest (v1.05) driver.
It definately looks to be a driver bug.
I think its about time for amanero to look into it.
I have to publicly thank Domenico from Amanero for his instant reply. We are exchanging messages and I will post when something that is of general interest comes up.
I was able to swap the DSD channels: foobar Configuration for DSD (With Amanero Interface & Buffalo DAC) H i F i D U I N O
Thanks🙂
Yep! thats the driver to address the above mentioned issue!
Domenico,
What can I say, I think that for the first time in history a vendor fixes a problem on a Sunday afternoon by issuing a new driver in less than 3 hours 🙂
F A N T A S T I C !
I strongly recommend to all users to give a try to KS.
Using Kernel Streaming in my system all streams including DSD just play straightforward with no other intervention.
Using Amanero with KS and deploying my tri-amplification the sound seems to be sooo direct that is frightening.. wish I could share this sound with you all 🙂
PS: When first play on KS @ 32bit I still got the wrong channels thing. I switched to 24bit and channels correct.. then switch back to 32bit and correction remained...
Apparently I have to do this everytime I start Foobar..
Domenico, here is your next bug 🙂
Domenico,
What can I say, I think that for the first time in history a vendor fixes a problem on a Sunday afternoon by issuing a new driver in less than 3 hours 🙂
F A N T A S T I C !
I strongly recommend to all users to give a try to KS.
Using Kernel Streaming in my system all streams including DSD just play straightforward with no other intervention.
Using Amanero with KS and deploying my tri-amplification the sound seems to be sooo direct that is frightening.. wish I could share this sound with you all 🙂
PS: When first play on KS @ 32bit I still got the wrong channels thing. I switched to 24bit and channels correct.. then switch back to 32bit and correction remained...
Apparently I have to do this everytime I start Foobar..
Domenico, here is your next bug 🙂
A new 1.054 driver has been posted at Amanero's site but no change log.
Are you sure?
Thanks to Domenico for the fix - KS seems to be solid in Foobar now.
How do you get DSD to play over KS? I had thought that ASIO was needed for this, which is what I've been trying using ASIO4All.
Using Kernel Streaming in my system all streams including DSD just play straightforward with no other intervention.
Using Amanero with KS and deploying my tri-amplification the sound seems to be sooo direct that is frightening.. wish I could share this sound with you all 🙂
How do you get DSD to play over KS? I had thought that ASIO was needed for this, which is what I've been trying using ASIO4All.
Install foo-KS and try to play any DSD file. It works as a charm!
The DSD indication should come up at the bottom left confirming the DSD playback.
At least thats what happens to my system.
The DSD indication should come up at the bottom left confirming the DSD playback.
At least thats what happens to my system.
Thanks for the response Stamatiski, but I must be missing something 😕
Do you mean "foo-out-KS" ? I have this installed, along with the foobar SACD plugin, but need to use ASIO for playback. Selecting KS results in silence from DSD files.
EDIT:
Just installed "foo input dsdiff" and removed the SCAD component and it all works lovely now - no horrible ASIO4All kludge 🙂.
Do you mean "foo-out-KS" ? I have this installed, along with the foobar SACD plugin, but need to use ASIO for playback. Selecting KS results in silence from DSD files.
EDIT:
Just installed "foo input dsdiff" and removed the SCAD component and it all works lovely now - no horrible ASIO4All kludge 🙂.
Last edited:
Spread the news!!
All we need is KS as the most simple most functional and purest method in Foobar.
May be we could push things for a foo-out-KS update (if needed) since it has not been updated for 6 years now 😉
All we need is KS as the most simple most functional and purest method in Foobar.
May be we could push things for a foo-out-KS update (if needed) since it has not been updated for 6 years now 😉
"foo input dsdiff" only outputs PCM. You can achive the same but better SQ configuring SACD plugin to output PCM.
@jackal29a
obviously we are talking about KS as an OUTPUT option. The "foo input dsdiff" as its name states is an INPUT decoder (necessary though to do the job) and NOT an OUTPUT option.
obviously we are talking about KS as an OUTPUT option. The "foo input dsdiff" as its name states is an INPUT decoder (necessary though to do the job) and NOT an OUTPUT option.
@jackal29a
obviously we are talking about KS as an OUTPUT option. The "foo input dsdiff" as its name states is an INPUT decoder (necessary though to do the job) and NOT an OUTPUT option.
I know, I was addressing dickiegeorge's comment. The only way so far to get true DSD from the combo384 in Foobar is using the "kludgy" route, using DSDIFF one only can get PCM independent of output mode used. No probs with JRiver using WASAPI or KS though.
DSD is not possible in Foobar using KS or WASAPI due to DSP and Volume stages of the player not being ready for DoP and treating the signal as regular PCM. When asked about this they said they have no intention of changing it. I guess they are not interested in DSD.
As I'm on W7 I use WASAPI Event as output.
Can someone confirm that this USB interface is async?
I'm not sure, even after searching the thread for "async"
If yes, it would be a massive upgrade for my DAC (Wyred4sound DAC-2)
Thanks!
I'm not sure, even after searching the thread for "async"
If yes, it would be a massive upgrade for my DAC (Wyred4sound DAC-2)
Thanks!
Jackal29a thanks for the info.
It makes sense that "foo input dsdiff" is converting the files into PCM which is then handled natively by the KS output. I don't have an indicator for PCM / DSD on my Buffalo DAC (only S/R) so I can't see what's going on. I need to hook up my Arduino for that.
I did feel that DSD played over KS output sounded a little different from ASIO - this would explain why.
It makes sense that "foo input dsdiff" is converting the files into PCM which is then handled natively by the KS output. I don't have an indicator for PCM / DSD on my Buffalo DAC (only S/R) so I can't see what's going on. I need to hook up my Arduino for that.
I did feel that DSD played over KS output sounded a little different from ASIO - this would explain why.
- Home
- Vendor's Bazaar
- USB to I2S 384Khz - DSD Converter