I suspect this is most likely an issue with the Dragonfly itself, but thought I would post my particular problem here in case someone can assist...
I am using it on a Windows 7 PC, using J River Media Centre 18 configured to output to the dragonfly via "WASAPI - Event Style" - which is recommended on every forum I have reviewed.
1. When I play a 16 bit 41kHz flac file (2 channel), the dragonfly is green and I get sound to the headphones plugged in. Good.
2. When I play a 24 bit 48kHz flac file (6 channel downmixed to 2 channel by jriver), the dragonfly is blue and I get NO sound to the headphones plugged in. Bad
3. When I play a 24 bit 96kHz flac file (6 channel downmixed to 2 channel by jriver), the dragonfly is pink and I get NO sound to the headphones plugged in. Bad
It would appear that jriver is outputting the correct data to the dragonfly as it is changing colours depending on what kHz file is sent to it.
Any thoughts on what could be the problem?
Just purchased a DragonFly and have it set up with JRiver 18 on a Windows 7 computer using ASIO4ALL as recommended in a recent The Absolute Sound follow up article on the DragonFly. My issue is similar to San66. I've done a little more testing and have the following to add. I have tried 16/44.1kHz, 16/48kHz, 16/88.2kHz, 16/96kHz, 24/44.1kHz, 24/48kHz, 24/88.2kHz and 24/96kHz files to test the DragonFly / JRiver set up.
The DragonFly will light up correctly with each resolution fed to it. It however will ONLY pass audio when 44.1kHz or 88.2kHz files are fed to it. 48kHz and 96kHz files will not come through at all.
When I change settings in JRiver Audio Options under DSP so any file that goes in as 48kHz is down converted to 44.1kHz and any 96kHz file is down converted to 88kHz, everything plays fine.
I've changed driver selections from ASIO4ALL to everything else in JRiver (always restarting the program and the DragonFly after changes have been made) and it makes no difference. I've tested the DragonFly on two other computers with JRiver 18 and get the exact same result. I've messaged Audioquest on Dec. 12, 2012 about this and have yet to hear back.
Not sure this is a JRiver issue or Audioquest issue. Anybody else have any thoughts on this?