It's only a " wrapper" which provides an ASIO interface on top of (connected to) a native Windows audio interface (and it's driver). N.B.: the suggested " asio4all" is NOT really an ASIO driver. Though I don't know if any such driver does actually exists. That is, one which can work with any "Class Compliant" USB 2.0 audio interface. What perhaps may exists in this case is a "generic" UAC2 ASIO driver. Obviously that can be done only with a low level driver which is specific for a given hardware. It's simply impossible: the whole idea behind ASIO is to by-pass the entire windows audio subsystem, connecting directly to the hardware. The Windows driver only accepts 32 bit audio for my device which may explain why Audirvana “correctly” sends 32 bit audio when using the native Windows driver.Click to expand.There's no such thing as a “ generic ASIO driver”. ![]() Thank you.Įdit: Then perhaps this is not a Thesycon-specific issue but rather “intended” functionality within Audirvana? I would still like to propose that Audirvana always send audio to the device in the highest bit depth that is supported by that device, or have a control panel option allowing the user to choose what bit depth to use. I was hoping this further clarification may be useful. The ASIO driver only accepts 32 bit audio which explains why Audirvana works correctly and only sends 32 bit audio to it.įor reference, if I use the Thesycon driver and play audio using J River Media Center, J River always outputs 32 bit audio to the device regardless of source file bit depth or mode (WASAPI/KS/ASIO), unless you choose DirectSound which no one should be doing, LOL. ![]() I just noticed that if I play a 24 bit file that Audirvana outputs to the device using 24 bits when using the Thesycon driver - so WASAPI and Kernel Streaming (and maybe ASIO?) seem to be following the bit depth of the source file - which is ok when no additional modifications are being made to the audio, but in my case I am using a VST plugin to make changes including EQ and volume, so being able to output the modified audio stream in 32 bits is beneficial. Thank you for your consideration in fixing this Audirvana issue. It is the top file called “Singxer_USB_Audio_Class2-Driver_v5.58.0.exe” I’m not able to upload the actual device driver but I will link it here: I also wanted to use the Thesycon driver rather than the Windows driver so I can have the option of ASIO. I really wanted to see this fixed because I do use a VST plugin to apply EQ and volume change so output in at least 24 bit would be good, 32 bit would be ideal, and 32 bit is the way Origin is supposed to work. ASIO is not supported with the Windows drivers. Now if I delete the driver and just use the built-in Windows driver for the device, it will send 32 bit audio in both WASAPI and Kernel Streaming mode. Origin is supposed to output audio to the device with the highest bit depth supported, but it is not with Theyscon-based devices (I’m assuming). If I use ASIO, it sends 32 bit which is correct. When I select the device in Origin, and if I use either WASAPI or Kernel Streaming, Origin only sends 16 bit audio to the DDC device. The device supports audio in 16, 24 and 32 bit. I am assuming all devices which use Thesycon drivers would also encounter this issue. ![]() I have a DDC called “Singxer SU-2” which is connected to the PC via USB and looks just like a DAC to the OS. I have a request to fix an issue I’ve had since the beginning of my time with Audirvana.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |