maxxevv
Major Contributor
- Joined
- Apr 12, 2018
- Messages
- 1,873
- Likes
- 1,976
Are you talking about the old firmware or the updated one??You will notice more later, trust me
Are you talking about the old firmware or the updated one??You will notice more later, trust me
You have the updated one already?Did you actually update the firmware like I did?
Because I just did and whatever you mentioned about the clicking applies only before the firmware update, at least IME
You have the updated one already?
I only see the link on page 64...Yeah someone posted the link to the firmware update quite recently in this thread, it’s a few pages back
Thanks bro, appreciated.Yeah someone posted the link to the firmware update quite recently in this thread, it’s a few pages back
I only see the link on page 64...
'Changing' to higher bit is just padding. Lossless.Question guys. I noticed that going from 16bit to 24bit there is no click.
Is it because DX3pro changes everything to 32bits?
So, that even when using WASAPI all the native 16bit and 24bit files are automatically changed to 32bits?
'Changing' to higher bit is just padding. Lossless.
Lowered bits need dithering.
Yes, I know it is just padding. So, is that what DX3pro is doing?
No more extra clicking via USB with new firmware. And it's great.
But Bluetooth keeps clicking every play/pause. I guess it's required another one new firmware in the future
Looking at measurements of SK10, these are not making it a winner of anything.The driver (what is being called firmware but not actually so) does not control Bluetooth, only USB input - it's a Thesycon software for the XMOS chip. The clicking with Bluetooth cannot be solved with driver, it will remain unless there is some kind of actual firmware change (i.e hardware revision). In BT mode my unit clicks on and off continuously unless something is playing, and you do get a slight pop through the speaker when this happens. Very irritating, though I don't use BT it still should have been complete.
I also don't understand the 0dB level when the unit is set to fixed output. In almost every kind of device that has this volume bypass, it is accessed by a specific combination of buttons so that an accidental keypress does not result in deafness or equipment damage. A simple way to implement this would be to mute the output the moment fixed level is set, so user can bring it out of mute manually or change the mode back to where it was. The normal operating method should be both outputs active and set to variable level, and fixed level requires a little more user intervention.
There are other issues - the use of tantalum capacitors in the series signal path for one, most likely the cause of the pop as they look unterminated. Normally you would directly connect the outputs to the LPF and the summing function would automatically remove offset. That is a very basic design error, and I don't know if it's Topping or AKM that is responsible for this issue. Frankly I don't care for the bumpy implementation, the unit sounds good enough for the price and that's about it. I would really hesitate to recommend it to anyone given its numerous problems. I had purchased the SMSL SK10 and this together and the SMSL is a winner at its price, this one not so much.
I went through the 16bit / 24bit / 32bit switching test many times, but with the bit rate change, the click is not.Question guys. I noticed that going from 16bit to 24bit there is no click.
Is it because DX3pro changes everything to 32bits?
So, that even when using WASAPI all the native 16bit and 24bit files are automatically changed to 32bits?