[nOiZepHyZiX]

I have used JRiver on Windows but first make sure you are not using direct streaming for your DSD files. The only way it will work on a Mac is using DoP (DSD over PCM). Since there are no audio drivers for Mac OS, the max DSD via DoP is 128. DSD 256 via DoP requires 706 kHz sample rate but I believe K9 only supports 384 max so DSD 256 must use direct stream with the FiiO provided driver which is only for Windows.

Thank you for your reply! I can successfully play DSD64 files using bitstreaming (observing mac os "audio devices" switching "format" to 176.4khz 32-bit, and the K9Pro switches to display a green light ring (indicating DSD playback). Playing DSD128 files also successfully play with mac os switching to 352.8Khz 32-bit setting, and K9Pro switching to green light ring. You are correct in that DSD256 files will not play (bitstreaming or not), as the max sampling rate of the K9Pro is 384Khz (JRiver errors out with a message that speaks to this). My issue comes up after hours of playtime, when all of a sudden normally-working DSD64 files will play with that noise artifact. It's as if at some point the sample rate switching failed to do so into the next song (flac-to-DSD). That issue along with frozen playback resolves once I hard power cycle the K9Pro. It seems to get "locked" after a long listening session somehow.

 

[nOiZepHyZiX]

If you have another DAC available, you can play the same playlist to see if the problem is due to jRiver/Mac or the K9 is involved.

Good call on troubleshooting with another DAC - I do have a FiiO M11 Plus LTD I could try out with this as well in DAC mode...

 

[bflat]

Thank you for your reply! I can successfully play DSD64 files using bitstreaming (observing mac os "audio devices" switching "format" to 176.4khz 32-bit, and the K9Pro switches to display a green light ring (indicating DSD playback). Playing DSD128 files also successfully play with mac os switching to 352.8Khz 32-bit setting, and K9Pro switching to green light ring. You are correct in that DSD256 files will not play (bitstreaming or not), as the max sampling rate of the K9Pro is 384Khz (JRiver errors out with a message that speaks to this). My issue comes up after hours of playtime, when all of a sudden normally-working DSD64 files will play with that noise artifact. It's as if at some point the sample rate switching failed to do so into the next song (flac-to-DSD). That issue along with frozen playback resolves once I hard power cycle the K9Pro. It seems to get "locked" after a long listening session somehow.

Something isn't right, there is no way to play direct stream DSD on Mac without specific device drivers. DoP is the only way without drivers. The light ring only tells you it's playing DSD but it does not indicate how the data was transported direct or DoP.

 

[nOiZepHyZiX]

Something isn't right, there is no way to play direct stream DSD on Mac without specific device drivers. DoP is the only way without drivers. The light ring only tells you it's playing DSD but it does not indicate how the data was transported direct or DoP.

The observable difference I can report is that when I have bitstreaming selected (as "Yes"), mac os switches to the highest available sampling rate for DSD (64/128), and K9Pro turns to the green color, indicating DSD. When I switch bitstreaming off (as "None"), mac os will still switch to the highest sampling rate available for the DSD file, and K9Pro will display the Yellow color, indicating sampling rate >48kHz. Somehow there is distinction between these two playback settings in JRiver that the K9Pro is recognizing, just not sure how.
Really these are curiosities of mine, as the K9Pro works phenomenally most of the time, it just seems to lock up occasionally after many hours of use. I still haven't come across the "abnormal alarm" state where the K9Pro light ring (according to FiiO) goes into a red-color state, with three different conditions 1) "Red indicator will stand on/pulsing/flashing when output is abnormal." 2) "Temperature too high: red indicator stand on." 3) "When the output is overloaded and the hardware is damaged: red indicator pulsing/flashing."

 

[bflat]

The observable difference I can report is that when I have bitstreaming selected (as "Yes"), mac os switches to the highest available sampling rate for DSD (64/128), and K9Pro turns to the green color, indicating DSD. When I switch bitstreaming off (as "None"), mac os will still switch to the highest sampling rate available for the DSD file, and K9Pro will display the Yellow color, indicating sampling rate >48kHz. Somehow there is distinction between these two playback settings in JRiver that the K9Pro is making, just not sure how.

JRiver must mean that "Bit Streaming On" is DoP while "Bit Streaming Off" is DSD to PCM conversion. That doesn't explain the audio issues you are having. In my experience, the few times I heard static on music simply stopped, it was due to my USB cable not being able to handle the high bit rates. Using a good quality cable solved it for me. I am not speaking about "audio quality" as I am in the camp of "digital is digital" meaning I believe USB cables work or they don't and once they work, there is no audible difference between a $10 cable and a $1000 cable.

 

[Bob Ley]

I'd like to know why, when using Bluetooth with my phone as a source, every time I pause a song and play again, the audio skips and I have to turn off Bluetooth then on again for it to play normally.

 

[FiiO Willson]

The volume drop issue is solved with system firmware beta 18. The only thing that I could not make work is bluetooth from Win7 to k9pro. (win10 / win11 /android phone worked)
I also got fiio control app 0813 for android with which I have the volume control, which was not there on my android phone with the orignal app version. Haven't looked since my last post if there is meanwhile a newer release version than 1.13 what mine had when delivered. The click problem of azertyproxy did not occur on mine. (akm version/unbalanced hp). beta 18 is stable enough for me, but I will install the new release version when it comes.

Due to some problems with APP volume adjustment, the function was cancelled.

Does the volume control move the volume knob on the k9? That would be marvelous

This requires very sophisticated mechanical and software control, which can indeed be done, but the structural design will be significantly changed

 

[FiiO Willson]

I'd like to know why, when using Bluetooth with my phone as a source, every time I pause a song and play again, the audio skips and I have to turn off Bluetooth then on again for it to play normally.

I have not encountered this problem in my use as you mentioned.
Could you please describe the phenomenon in detail, or take a video and send me separate for us to confirmation&analysis.

Thank you for your support

 

[Bob Ley]

I have not encountered this problem in my use as you mentioned.
Could you please describe the phenomenon in detail, or take a video and send me separate for us to confirmation&analysis.

Thank you for your support

I will, thanks.

 

[xLuffyzx]

Thank you for your reply! I can successfully play DSD64 files using bitstreaming (observing mac os "audio devices" switching "format" to 176.4khz 32-bit, and the K9Pro switches to display a green light ring (indicating DSD playback). Playing DSD128 files also successfully play with mac os switching to 352.8Khz 32-bit setting, and K9Pro switching to green light ring. You are correct in that DSD256 files will not play (bitstreaming or not), as the max sampling rate of the K9Pro is 384Khz (JRiver errors out with a message that speaks to this). My issue comes up after hours of playtime, when all of a sudden normally-working DSD64 files will play with that noise artifact. It's as if at some point the sample rate switching failed to do so into the next song (flac-to-DSD). That issue along with frozen playback resolves once I hard power cycle the K9Pro. It seems to get "locked" after a long listening session somehow.

Sorry, just to understand does K9 only support only up to 384khz? Cause on the 1st page they state it support up to 768khz?

"
5,USB DAC support up to 768kHz/32b decoding (DSD512 support)
"

 

[FiiO]

Sorry, just to understand does K9 only support only up to 384khz? Cause on the 1st page they state it support up to 768khz?

"
5,USB DAC support up to 768kHz/32b decoding (DSD512 support)
"

Dear friend,
For the final detailed parameters, please refer to our website: https://www.fiio.com/k9pro_parameters

Best regards

 

[xLuffyzx]

Dear friend,
For the final detailed parameters, please refer to our website: https://www.fiio.com/k9pro_parameters

Best regards

Thanks, just a question why does another devices uses the same DAC support 768khz and DSD512 but not K9 Pro? Is it the same for the ESS version as well?

 

[Moon5123]

Thanks, just a question why does another devices uses the same DAC support 768khz and DSD512 but not K9 Pro? Is it the same for the ESS version as well?

I had same thought as well, like 5 year old chord mojo support 768khz and other dacs with same AKM chips also supports it.
May be it have to do with USB chipset or something?
Well I dont have any dsd files to play so it doesn't bother me but just curious to know.

 

[ipaddy]

Can someone please explain the following situation to me?

I have the following:

1) One AK4499 K9 Pro;
2) One M11 Pro; and
3) One Focal Clear Headphones

There are two possible setups:

A) I plug the Focal Clear, with a balanced cable with a male 4.4mm jack, into the M11 Pro; or
B) I plug the Focal Clear into the K9 Pro front panel balanced 4.4mm jack. I connect the M11 Pro via balanced cable into the back panel 4.4mm line in.

Issue: In the B setup, in order to get a good volume, I need to set the 2nd switch on the front panel of the K9 Pro to "H" (which is High) and I also need to turn the large volume knob in the front of the K9 Pro to way past 12 o"clock position, such as 2 or 3 PM. That seems strange. But worse...

But where I plug the Focal Clear directly into the M11 Pro, which is setup A, starting at the M11 Pro's same volume same setting as in setting B, if I turn the M11 Pro volume up on the M11 Pro itself, I don't have to go very far before I get much louder volume than I had when going through the K9 Pro.

There is something wrong here. Where is the amplification?

Also, I tried each setup with a FIIO FH5s, and the FH5s really didn't sound any better when plugged into the K9 Pro.

Am I doing something wrong?

 

[itsnein]

Can someone please explain the following situation to me?

if you use 4.4 as input on K9 pro,
on m11 volume should be maximum - like Line output.
As far as I know, m11 pro: only 3.5 line out, not 4.4

butt in any way it is a strange setup for me.
when you use 4.4. output from m11 pro
DAC of m11 is working, and DAC from k9 not working at all. The only amp is working.

Much better IMHO connect m11 to k9 via USB.
In that case m11 works as transport, and K9 as DAC + Amp