I set the output of Hi-Max (latest fw v0.1) to +6dB in its webapp using DAC Playback Volume slider and that's the only gain setting I'm aware of. Similarly, I set the output of KT02H20 to +3dB using KT USB app. The later was roughly 2dB louder.
-
Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!
FiiO has released the USBDAC JA11, with an initial price of only $9 (69RMB) and support for PEQ DSD128 PCM384
I found that +4 to +6dB gain on Hi-Max on its WalkPlay app is no different from +3dB gain. So, it's actual max gain setting is +3dB.
Also, there is a language issue. As I said earlier, KT02H20 has higher gain than Hi-Max when they are set to the same gain value on each app. This does not necessarily mean there is a "power difference" or a difference in their max output power. Normally, when we use the term "power" in the context of comparing devices, we usually don't mean their default gain difference. We almost always mean a difference in their maximum output power. Again, at 16 ohm, Hi-Max's max/unclipping output power is slightly higher than JM12's, meaning Hi-Max can go slightly louder than JM12 without clipping.
Nope, see my post I made in your thread:
VE Odo is good or bad for use in Windows PC
VE Odo is good or bad for use in Windows PC? actually i use chip audio motherboard ASRock B75M-DGS R2.0 (Realtek ALC662 Audio Codec iems kz edc pro
www.audiosciencereview.com
It's fine IMHO, no rush to upgrade if you already have it. Some graph distortion is reported but its unclear if they exceed audibilty thresholds. You may listen to the dune soundtrack clip, and cmaj clips if you are concerned with audible crackling artefacts, which are solved with a firmware flash.
How to update VE Odo firmware?
Do a listening test first.
1. https://reference-audio-analyzer.pro/en/demo-cs131.php
2. https://www.audiosciencereview.com/...31xx-based-devices-a-comparative-review.63038 the bottom of the original post.
If you can't identify audible crackling, you can skip and further steps. Otherwise, here is the firmware flashing packing including everything https://www.tinhifi.com/pages/eq
The audio is working, except when Windows plays a sound, there's a hissing sound similar to rain. Some YouTube videos have a sound delay, but overall it's good.
Will this update improve the audio on my Venture Electronics Odo + KZ EDC Pro set?
Will this update improve the audio on my Venture Electronics Odo + KZ EDC Pro set?
It's not very likely to reduce any real hissing. The hissing of windows stock sounds is likely due to their limited quality. Make sure to uncheck "listen to this device" in Windows settings.
In my case, the JM12 stock firmware is the only firmware that produces hiss when playing songs using the FiiO Music Player app.
At first, I was hesitant to change the firmware because I read that every firmware has problems.
But I was relieved after flashing the FiiO or TinHifi firmware, which fixed the hiss problem on the FiiO Music Player app.
However, the FiiO or TinHifi firmware did not pass the rumble test or the dun soundtrack clip test using sensitive IEMs.
It did pass the test when using headphones.
Why not? It’s not like you’re throwing a lot of money at it, but it’ll be limited: you have only 5 PEQ filters to play with, it’s not exactly the highest quality DAC, you may experience some pops and clicks…
amburegul26
New Member
- Joined
- Nov 23, 2025
- Messages
- 1
- Likes
- 1
Using the FiiO app on Android, when I set the device volume to 40, I can hear extreme crackling in the Dune soundtrack test and the rumble test from Audiocheck.
But when I set the volume to 60 (maximum) and apply –12 dB gain through the PEQ in the app, the overall volume is about the same for my sensitive IEMs (CCA CRA+), and I don’t hear any crackling anymore.
But when I set the volume to 60 (maximum) and apply –12 dB gain through the PEQ in the app, the overall volume is about the same for my sensitive IEMs (CCA CRA+), and I don’t hear any crackling anymore.
At 0dB gain, these test tracks may trip one of the KTmicro “DRC” features. For example, the noise limiter is set at -3dB by default, with the “smooth transition” off.
If you check the "PS" in a previous post, I experience the same on mine (usually connected to a PC, after setting it up on Android).
At anything other than max 60/60 in the main volume, it'll noticeably fuzz/distort in certain tracks with instruments against silent backgrounds (previously mentioned the first 17s of this song), so something like 30/60 isn't usable for sensitive IEMS (regardless of PEQ settings). OTH, as you've also found, leaving it maxed at 60/60 while enabling PEQ at -12db gain seems to only way to limit max volume without the fuzz issue.
TL;DR Either main 60/60 vol + PEQ Off (too loud), or 60/60 with PEQ On at 0db or -12db gain still plays fine (haven't checked PEQ at +12db gain, but that'd be same volume as PEQ Off). The problem appears when main FiiO app volume isn't left maxed at 60/60, fuzzing out at 40/60, 30/60, etc.
Last edited:
dr.strange
New Member
- Joined
- Nov 28, 2025
- Messages
- 4
- Likes
- 0
I recently purchased the kz type c cable , but mine came with the new mic (like m2 version) , But i wasn't able to read what eq is on it with kt tools (It uses ktmicro chip also) I Don't know what seems to be the issue , if you know a better way to try and mod the eq value.
Although I don’t recall how I got it.. I believe the M2 uses a CX31993 SoC, which would explain why you can’t read the EQ presets with the KTmicro tool—unlike e.g. the Kiwi Ears Allegro Pro dongle, which also has 3x presets but is based on KT02H20 (+dual-ES9603).
KZ has a cheaper USB-C cable (no preset) that uses a KT0231H. The PEQ on that one (6x filters) can be set with the KTmicro tool by writing directly into the register slots (different addresses as compared to the KT02H20/KT0211L).
dr.strange
New Member
- Joined
- Nov 28, 2025
- Messages
- 4
- Likes
- 0
It is this cable , it is supposed to be the old usb c cable but has the new mic , and it shows in hwinfo as ktmicro device with VID 31b2 , PID 1132
But when i tried to use kt micro tools it didn't read any stored settings on the cable like it did in your case,
so if you know how i could read the settings already on it or how to adjust the eq that would be helpful
Ok, so it’s not the “M2”, but the other KZ cable using a KT0231H chip (the “M2” USB-C connector is slightly larger, with a little glass window and a button for the presets).
The version of the KTmicro tool from the TinHifi website (I assume that’s what you use) is for the KT02H20 & KT0211L. But the tool registry R/W feature works and can be used with the KT0231H.
Let me look in my stuff for the DAC PEQ registry addresses & settings for the KT0231H…
EDIT: here you go...
KT0231H DAC PEQ Register Addresses:
| Addr. Dec. | Addr. Hex. | Default Dec. | Default Hex. | Description |
|---|---|---|---|---|
53 | 0x35 | 3997696 | 0x003D0000 | DAC #0 Freq & Gain |
54 | 0x36 | 700 | 0x000002BC | DAC #0 Type & Q |
55 | 0x37 | 7995392 | 0x007A0000 | DAC #1 Freq & Gain |
56 | 0x38 | 700 | 0x000002BC | DAC #1 Type & Q |
57 | 0x39 | 12058624 | 0x00B80000 | DAC #2 Freq & Gain |
58 | 0x3A | 700 | 0x000002BC | DAC #2 Type & Q |
59 | 0x3B | 16252928 | 0x00F80000 | DAC #3 Freq & Gain |
60 | 0x3C | 700 | 0x000002BC | DAC #3 Type & Q |
61 | 0x3D | 20709376 | 0x013C0000 | DAC #4 Freq & Gain |
62 | 0x3E | 700 | 0x000002BC | DAC #4 Type & Q |
63 | 0x3F | 25690112 | 0x01880000 | DAC #5 Freq & Gain |
64 | 0x40 | 700 | 0x000002BC | DAC #5 Type & Q |
How it works...Register 0x35 default value is 0x003D0000: 0x003D means 61Hz; 0x0000 means 0dB Gain.
Register 0x36 default value is 0x000002BC: 0x0000 is for type "0" (Peak); 0x02BC is for "700" or Q=0.700.
The five main types of filters are: 0x0000 (Peak), 0x0001 (Low-Pass), 0x0002 (High-Pass), 0x0003 (Low-Shelf), 0x0004 (High-Shelf). There may be more filter type (I haven't looked).
So let say, you want to set Filter #0 with a 200Hz / 6dB / Q=0.7 low-shelf, you'll write 0x00C8003C in register 0x35 (or, if you use the decimal notation also supported by the KTmicro tool, 13107260 in register 53) and 0x000302BC in register 0x36 (or, in decimal, 197308 in register54). 0x00C8 is 200Hz, 0x003C is "60" or 6.0dB, 0x0003 is for low-shelf, 0x02BC is "700" or Q=0.700.
Another example, let say, you want to set Filter #4 with a 3,000Hz / -3.5dB / Q=4 peak filter, you'll write 0x0BB8FFDD in register 0x3D (or, if you use the decimal notation, 196673501 in register 61) and 0x00000FA0 in register 0x3E (or, in decimal, 4000 in register 62). 0x0BB8 is 3,000Hz, 0xFFDD is "-35" or -3.5dB, 0x0000 is for peak, 0x0FA0 is "4000" or Q=4.000.
It's a little cumbersome to calculate & enter, but 1/ that's why these tools exist... and 2/ nothing an Excel spreadsheet or a small script couldn't solve (I hope my above examples are correct!). I personally use these PEQ-enabled dongles or cables permanently attached to an IEM, or easy to drive HP. I "explore" PEQ on a more user-friendly device (e.g. Qudelix 5K), and it's only when I'm happy that I enter the PEQs in these devices—or KZ cable in our case.
The KT02H20 & KT0211L are similar, but with 5x DAC PEQ filters in registers 0x26 to 0x2F. The ADC PEQ filters are in registers 0x1A to 0x23, the PGA ADC vol. is in register 0x3A, the PGA DAC L&R vol. is in register 0x3B, etc.
Last edited:
