[noobandroid]

Which music file format do you use? If a lossy one (e.g. MP3), which bitrate?

all are flac albums

 

[Lurker0]

all are flac albums

If you revert back to 2.3.0, does the problem disappear? In more common words, do you experience the problem only on 2.4.0?

 

[noobandroid]

If you revert back to 2.3.0, does the problem disappear? In more common words, do you experience the problem only on 2.4.0?

only at 2.4.0, not in previous versions

 

[Lurker0]

 

If you revert back to 2.3.0, does the problem disappear? In more common words, do you experience the problem only on 2.4.0?

only at 2.4.0, not in previous versions

OK, but did you try to flash 2.3.0 back and check if the problem disappeared? You see, there is a chance that the problem is caused not by the firmware, it just happened that it appeared the first time after the firmware update...
 
Also, if nobody else experience it, it must be something special with your device or your use...

 

[Paul - iBasso]

songs ending 4 seconds ahead of what it should be, tried on a whole lot of songs and they appear so, used the batch tool and same results still

Does this happen with all songs or random?

 

[noobandroid]

Does this happen with all songs or random?

it happened to quite a few albums i listened to

 

[noobandroid]

no such problems in 2.3 firmware

 

[Guppy_]

is there anyway to run the batch tool in windows 10 64 bit?

 

[Paul - iBasso]

  is there anyway to run the batch tool in windows 10 64 bit?

We just tried it on our Windows 10 and it doesn't work. We had reports it worked fine from users so we will look into this for a remedy.

 

[Guppy_]

 
We just tried it on our Windows 10 and it doesn't work. We had reports it worked fine from users so we will look into this for a remedy.

I found some google pages where some "experts" modified the .inf from the windows 8 driver and got it to work using unsigned drivers, I tried disabling unsigned and got "windows disabled this drive because of known issues".   If its any good to you  I tried both windows 10 pro 64 bit and home 64bit, got same result.  Corrupt hash   and after enabled unisigned drivers "blocked by windows". In any case, thanks for the quick response and hope you find a workaround!

 

[UNOE]

I had no issues with Windows 10. Disable user account control. Boot with disabled driver signature. Install the driver and when you receive the prompts click install any way or what ever the option is called you have to click install anyway I think 2 or 3 times. Then when driver is done installing you should be able to boot normally without driver sign enforcement disabled. The fiio drivers work same way under Windows 10.

 

[Guppy_]

I had no issues with Windows 10. Disable user account control. Boot with disabled driver signature. Install the driver and when you receive the prompts click install any way or what ever the option is called you have to click install anyway I think 2 or 3 times. Then when driver is done installing you should be able to boot normally without driver sign enforcement disabled. The fiio drivers work same way under Windows 10.

tried this and got:
 
The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)

 

[jackiecanev2]

I'm also experiencing the strange popping and clicking using USB/DAC on Mac (Macbook Pro 15" Mid-2014); there's no popping when no music is playing, and strangely, the popping isn't always bilateral - that is, the placement is different between pops. I've managed to get about 15 seconds or thereabout after a restart until the popping starts up again, but once the unit has been on for longer than that, the popping begins. I've tried MP3 and FLAC files, to the same result, but even when the unit is warm I can get through those first 15 seconds without any issue... so, I would assume its happening at the CPU. Reverting back to 2.3.0 FW resolves the popping issue, but I much prefer the sound signature of the 2.4.0 firmware - it is by far my favorite release. Pretty bummed about having to choose between the sound sig or the ability to use as a DAC... 
 
TL/DR; random experimental observations
- Rebooting gives about 15-20seconds of clear playback immediately upon reboot.
- Popping out the SD card clears the popping noise for >15 seconds, but less than 30 seconds.
- Popping the SD card back in does nothing.
- Scanning the SD card during playback clears the popping during scanning.
- Pops are consistent in timing frequency, but inconsistent in L/R placement.
- Happens to FLAC, MP3, AIFF, + Spotify.
- No issue with 2.3.0 firmware.
- Have done factory reset.
- Have used batch tool.
- Changing USB cable/port etc has no effect.

 

[Paul - iBasso]

  I'm also experiencing the strange popping and clicking using USB/DAC on Mac (Macbook Pro 15" Mid-2014); there's no popping when no music is playing, and strangely, the popping isn't always bilateral - that is, the placement is different between pops. I've managed to get about 15 seconds or thereabout after a restart until the popping starts up again, but once the unit has been on for longer than that, the popping begins. I've tried MP3 and FLAC files, to the same result, but even when the unit is warm I can get through those first 15 seconds without any issue... so, I would assume its happening at the CPU. Reverting back to 2.3.0 FW resolves the popping issue, but I much prefer the sound signature of the 2.4.0 firmware - it is by far my favorite release. Pretty bummed about having to choose between the sound sig or the ability to use as a DAC... 
 
TL/DR; random experimental observations
- Rebooting gives about 15-20seconds of clear playback immediately upon reboot.
- Popping out the SD card clears the popping noise for >15 seconds, but less than 30 seconds.
- Popping the SD card back in does nothing.
- Scanning the SD card during playback clears the popping during scanning.
- Pops are consistent in timing frequency, but inconsistent in L/R placement.
- Happens to FLAC, MP3, AIFF, + Spotify.
- No issue with 2.3.0 firmware.
- Have done factory reset.
- Have used batch tool.
- Changing USB cable/port etc has no effect.

I have passed this on to our software team. Thank you.

 

[pietro77]

I bought recently Leef Access microSD Card Reader with Micro USB 2.0 and it is not working properly on dx90, but working flawless on dx50 so I considering it as a bug in dx90.