FiiO has released the USBDAC JA11, with an initial price of only $9 (69RMB) and support for PEQ DSD128 PCM384

[CedarX]

KTmicro tool hasn't been used to successfully extract/backup a firmware from a dongle? I just want to double check.

I don’t think the tool (the one available on the TinHifi website) has this capability.

However, it does allow you to read & write the chips registers (Hex values). So, for example, I have mapped the Gain/PEQ/Noise Gate/Limiter settings exposed by the tool to the actual register addresses & values of the KT0211L (used on several USB-C IEMs & cables, from Tanchjim, Moondrop, Simgot, etc.), KT02F20 (not very common), KT02H20 (JA11, JM12, Odo, Allegro Mini/Pro, etc.). I also did the same for the 6x PEQ of the KT0231H (KZ cable, FiiO JD10), even if that chip is theoretically not supported by the tool.

What I don’t know is whether the differences in FW behaviors end up being different register map values, then which registers would that be, and whether you can overwrite the register values with the KTmicro tool to get the desired behavior, and make it “stick”.

It also looks like the tool allows you to peek at whatever ‘register’ address value you enter: literally hundreds of addresses… Do those chips truly have that many registers? Or, beyond a certain address range, I am peeking at the memory pages, i.e the actual firmware? Don’t know…

 

[HifiWanderer16]

The seller just answered, he's gonna call the factory and see if he can get the firmware. Let's keep our fingers crossed.

 

[HissingFree]

I remember the exact same crackling with the JM12 stock firmware, although I wasn't aware of the existence of that polarity test, but it was evident when pressing the sound test button in windows, typing when searching with ctrl+f without occurrences, etc, that's another reason why I changed to JA11 firmware.

 

[multiformous]

I remember the exact same crackling with the JM12 stock firmware, although I wasn't aware of the existence of that polarity test, but it was evident when pressing the sound test button in windows, typing when searching with ctrl+f without occurrences, etc, that's another reason why I changed to JA11 firmware.

That's interesting. Just tested the JM12 with JA11 firmware and the windows audio test crackles. Like, unmistakably horrible. Then I flashed the TinHifi firmware and no crackle. Hilarious.

 

[HissingFree]

That's interesting. Just tested the JM12 with JA11 firmware and the windows audio test crackles. Like, unmistakably horrible. Then I flashed the TinHifi firmware and no crackle. Hilarious.

Yes same here but the problem is that TinHifi firmware has high background noise instead, so it's a pick your poison thing.

 

[multiformous]

The Apple dongle always appears to perform poorly in these kinds of tests, but I can't say I've ever heard any issues when listening to music with it. Not so with the JM12 with JA11 firmware... This dongle isn't really useful to me with the noise issues (sure, TinHifi doesn't crackle, but it's fuzzy and doesn't support 44.1kHz sampling rate).

 

[markanini]

The Apple dongle always appears to perform poorly in these kinds of tests, but I can't say I've ever heard any issues when listening to music with it. Not so with the JM12 with JA11 firmware... This dongle isn't really useful to me with the noise issues (sure, TinHifi doesn't crackle, but it's fuzzy and doesn't support 44.1kHz sampling rate).

Is that issue limited to a noise increase in ultrasonic frequencies only, with some periodic features? That might be below audibility thresholds.

What's the fuzzy issue with TinHifi FW exactly? Is it reproducible with measurements or by listening?

 

[multiformous]

Is that issue limited to a noise increase in ultrasonic frequencies only, with some periodic features? That might be below audibility thresholds.

I don't pretend to understand it, but there is some explanation here.

As for the fuzziness, I'm not sure I can really show it in anything I can measure. But I did record the output from the JM12 with TinHifi firmware as a test just to 'see'. To make the differences plain, I hi-passed the original polarity rumble clip and the capture of the JM12 playing the original (full bandwidth) clip and will attach them here. Play them on what you believe to be your cleanest-sounding DAC and you should hear a difference between them. I didn't amplify the clips after hi-passing them. Impossible to say how much noise is introduced by recording the output of the JM12 through my motherboard's Line In... but some of the noise in the capture is certainly representative of how I hear the rumble test when listening to the JM12. Honestly I can hear background hiss as soon as I start playing something with JM12 on TinHifi firmware.

 

[markanini]

I don't pretend to understand it, but there is some explanation here.

As for the fuzziness, I'm not sure I can really show it in anything I can measure. But I did record the output from the JM12 with TinHifi firmware as a test just to 'see'. To make the differences plain, I hi-passed the original polarity rumble clip and the capture of the JM12 playing the original (full bandwidth) clip and will attach them here. Play them on what you believe to be your cleanest-sounding DAC and you should hear a difference between them. I didn't amplify the clips after hi-passing them. Impossible to say how much noise is introduced by recording the output of the JM12 through my motherboard's Line In... but some of the noise in the capture is certainly representative of how I hear the rumble test when listening to the JM12. Honestly I can hear background hiss as soon as I start playing something with JM12 on TinHifi firmware.

@HissingFree does it match what you are hearing? https://voca.ro/15WpWbkOXL96

I can hear the artifact in your clip, it could be RF/EMI related. Hiss is not what I would call it. Can you test again connected to a different USB port, or through a hub, without Wi-fi or 3G radios enabled? I can't reproduce it on my setup:JM12 with TinHifi FW, Samsung Dongle and CX31993 are unaffected.

BTW reports of CS43131 being more immune to RF/EMI-related noise might apply here, although FW may play a role too.

 

[HissingFree]

When I say hiss, I mean background noise, for example in this silence video one should hear nothing, but I do with Tinhifi firmware, not with JA11 firmware:

Of course, the less sensitive the headphone is, the lower this noise will be, so with ATH M50X I didn't hear any hissing with Tinhifi firmware , but then again, I also don't get crackling with JA11 firmware with these less sensitive headphones, the crackling seems to also be sensitivity related. The issues are with Salnotes Zero in my case, I also have CCA CA2 that are more sensitive and yeah the issues are amplified. But yeah I don't think Salnotes Zero are crazy sensitive headphones, there are a lot of headphones with a much higher sensitivity.

 

[multiformous]

Yeah I'm just done with this thing until there's some new firmware to test...

 

[markanini]

I now own both JM12 variants. From a quick listening test using this audio clip https://reference-audio-analyzer.pro/en/demo-cs131.php#gsc.tab=0

The stock JCally firmware produce very slight crunchy artifacts, I doubt it's audible in real listening. It exposes a multitude of sample rates from 44.1-384kHz.

The TinHifi firmware however is dead clean. So if clean output is what you want, look no further!

One general caveat is that when the cable is intermittent, like my blue JM12 is, only twisitng the cable will ensure clean playback. Without this intervention the sound will be audibly distorted with normal music. CX dongle may be more prone to cutting out fully before passing on a distorted signal, in my experience. CX31993 dongle produces light crunchiness playing back the test clip, I will need to test with a non-intermittent CX31993 to be fully certain if this is inherent to the CX31993 dongle, or a consequence of the intermittent connection.

To summarize: Under ideal conditions JM12 with TinHifi firmware will be the cleanest of all 1V dongles that I've tested.

I can't comment on durability, but I hope the silver version holds up more than three months before becoming intermittent.

 

[CedarX]

One general caveat is that when the cable is intermittent, like my blue JM12 is, only twisitng the cable will ensure clean playback.

This is interesting: there is really nothing downstream of the USB-C connector (where the SoC is located).
So, when twisting the cable… do you also “twist” (apply torque to) the USB-C connector, which could cause the problem? Or do you somehow deform the PCB inside the USB-C connector? Or, it's truly, and only the downstream cable that is causing the problem?

 

[markanini]

This is interesting: there is really nothing downstream of the USB-C connector (where the SoC is located).
So, when twisting the cable… do you also “twist” (apply torque to) the USB-C connector, which could cause the problem? Or do you somehow deform the PCB inside the USB-C connector? Or, it's truly, and only the downstream cable that is causing the problem?

I form the cable into an S-shape. The distortion comes back when i stop handing the cable in this specific way. The distortion reminds me of a dirty potentiometer.

 

[CedarX]

I form the cable into an S-shape. The distortion comes back when i stop handing the cable in this specific way. The distortion reminds me of a dirty potentiometer.

A short triggering the amp protection on & off?

 

[roZin14]

I find that, for JA11 in PC, with default microsoft driver everything works: inline mic stuff and sound.

But with Fiio usb driver installed, if inline mic is beforehand turned on for the DAC (only controllable through android app), The DAC itself isnt detected in sound settings of windows. It shows in device manager but not usable at all. fiio control panel would show no sampling rate error.

So if you want it working with fiio drivers (fiios wasapi and asio drivers), inline mic has to be turned off before connecting. and that means youll lose mic support. But then ig most people only want to hear music.

How can we post bug feedback to fiio? someone should report this or it might stay unfixed ??

 

[markanini]

I find that, for JA11 in PC, with default microsoft driver everything works: inline mic stuff and sound.

But with Fiio usb driver installed, if inline mic is beforehand turned on for the DAC (only controllable through android app), The DAC itself isnt detected in sound settings of windows. It shows in device manager but not usable at all. fiio control panel would show no sampling rate error.

So if you want it working with fiio drivers (fiios wasapi and asio drivers), inline mic has to be turned off before connecting. and that means youll lose mic support. But then ig most people only want to hear music.

How can we post bug feedback to fiio? someone should report this or it might stay unfixed ??

I enoucutnered this glitch. I was able to solve it by toggling settings back and forth, maybe re-flashing and restarting. I don't remember exactly. If nothing else helps you can always flash the TinHifi firmware. Hope this helps.

 

[roZin14]

I enoucutnered this glitch. I was able to solve it by toggling settings back and forth, maybe re-flashing and restarting. I don't remember exactly. If nothing else helps you can always flash the TinHifi firmware. Hope this helps.

Do you mean you solved it permanently? You can now use inline mic with fiio usb drivers?

 

[JanL]

I got the JCally JM12 today and played with it for a few hours. The factory setting definitely exhibited faint crackling sounds on occasion. It was not constant, but it seemed to be more prevalent at medium volumes, less so at loud volumes. That with low impedance IEMs, 64 Audio Nio, if that matters.

I took a chance on the FiiO firmware and I found and installed the V2.1 firmware. It works OK with the Fiio app on the phone, but not with the web page control. But that's on a Chromebook, so I'm not surprised. I haven't tried the web app on the Windows PC yet.
Overall it's dead quiet and quite powerful. Right now I'm driving a pair of Thieaudio Hype 4 with it and have no complaints. Plenty loud and clean at half volume. I don't really need the EQ functionality because I use Wavelet on my phone, but on the Chromebook it can come in handy with some headphones or IEMs.

 

[JanL]

I now own both JM12 variants. From a quick listening test using this audio clip https://reference-audio-analyzer.pro/en/demo-cs131.php#gsc.tab=0

The stock JCally firmware produce very slight crunchy artifacts, I doubt it's audible in real listening. It exposes a multitude of sample rates from 44.1-384kHz.

The TinHifi firmware however is dead clean. So if clean output is what you want, look no further!

One general caveat is that when the cable is intermittent, like my blue JM12 is, only twisitng the cable will ensure clean playback. Without this intervention the sound will be audibly distorted with normal music. CX dongle may be more prone to cutting out fully before passing on a distorted signal, in my experience. CX31993 dongle produces light crunchiness playing back the test clip, I will need to test with a non-intermittent CX31993 to be fully certain if this is inherent to the CX31993 dongle, or a consequence of the intermittent connection.

To summarize: Under ideal conditions JM12 with TinHifi firmware will be the cleanest of all 1V dongles that I've tested.

I can't comment on durability, but I hope the silver version holds up more than three months before becoming intermittent.

Where did you find the TinHifi firmware? I googled for it, but came up with nothing. I don't really need it because the Fiio firmware seems to be just fine, but I'm just curious.