iBasso DX80 . . impressions and reviews. . and discussion NEW FW: 1.6.0 ** link . . 1st page . . .
May 3, 2016 at 2:49 PM Post #4,247 of 6,795
We have worked extensively on the sound issue with changing FWs. We have also conferred with other experts. There has been no definitive answer. We do not modify the sound or try to change it. We use very high quality parts and want the part choices and implementation of the collective parts to bring about the best sound possible. We continue to look into why software can impact the sound.
 
We have also seen some null issues. In getting reports from users of other brands it seems to be an issue with most all daps. We also have a report that even in iTunes there are unknown/null files. We do not use this as an excuse but to realize there are other possible issues such as tagging etc. We will continue to work on this of course.
 
iBasso Stay updated on iBasso at their sponsor profile on Head-Fi.
 
http://www.ibasso.com/ paul@ibasso.com
May 3, 2016 at 3:32 PM Post #4,248 of 6,795
Crash and failure to complete scanning my card with firmware 1.4.2 (as happened with 1.4.1). Installed the update with the "power button + volume up" method, no good. Ran a second factory reset just for kicks, no good. Tried erasing the card and putting all the music back on it, no good. Cannot use the "factory wipe tool" thing on page 1, because I have no PC.
 
The card scans fine when I revert to firmware 1.3.3, so I'm back to that one.
 
The minimum viable product concept only works if you eventually take the next steps and make the software robust. An "update" that breaks basic functionality (scanning a card) should never have seen the light of day.
 
May 3, 2016 at 3:41 PM Post #4,249 of 6,795
We have worked extensively on the sound issue with changing FWs. We have also conferred with other experts. There has been no definitive answer. We do not modify the sound or try to change it. We use very high quality parts and want the part choices and implementation of the collective parts to bring about the best sound possible. We continue to look into why software can impact the sound.

We have also seen some null issues. In getting reports from users of other brands it seems to be an issue with most all daps. We also have a report that even in iTunes there are unknown/null files. We do not use this as an excuse but to realize there are other possible issues such as tagging etc. We will continue to work on this of course.

Regardind scan issue from 1.4.0 onwards, I don't understand why with 1.3.3 I had zero problems. 1.4.2 works better than 1.4.0, but still jot perfect as 1.3.3, at least for me.
 
May 3, 2016 at 4:31 PM Post #4,250 of 6,795
  Crash and failure to complete scanning my card with firmware 1.4.2 (as happened with 1.4.1). Installed the update with the "power button + volume up" method, no good. Ran a second factory reset just for kicks, no good. Tried erasing the card and putting all the music back on it, no good. Cannot use the "factory wipe tool" thing on page 1, because I have no PC.
 
The card scans fine when I revert to firmware 1.3.3, so I'm back to that one.
 
The minimum viable product concept only works if you eventually take the next steps and make the software robust. An "update" that breaks basic functionality (scanning a card) should never have seen the light of day.

 
I was having this problem, also. It's pretty frustrating. I think it's an issue with file tagging. I'm not sure what specifically fixed it for me, but, after I cleaned up a few files that ended up showing as "(null)" after the incomplete scan, I was able to get it to scan completely without crashing.
 
I used MusicBrainz Picard to fix the problem files. Hope this helps. 
 
May 3, 2016 at 4:41 PM Post #4,251 of 6,795
  We have worked extensively on the sound issue with changing FWs. We have also conferred with other experts. There has been no definitive answer. We do not modify the sound or try to change it. We use very high quality parts and want the part choices and implementation of the collective parts to bring about the best sound possible. We continue to look into why software can impact the sound.
 
We have also seen some null issues. In getting reports from users of other brands it seems to be an issue with most all daps. We also have a report that even in iTunes there are unknown/null files. We do not use this as an excuse but to realize there are other possible issues such as tagging etc. We will continue to work on this of course.

Paul - Thanks for that clarification. I've never noticed a sound change with the various firmware versions. But based on other comments stating that they noticed a change, I always wondered if iBasso was purposely tweaking the sound image. 
 
By the way I haven't had any issues with card scanning with 1.4.2, or for that matter all the way back to 1.1.4. The latest version (1.4.2) scanned 4200 files in 8 minutes. No null titles. I'm using a Sandisk 128GB extreme.
 
May 3, 2016 at 4:44 PM Post #4,252 of 6,795
  Crash and failure to complete scanning my card with firmware 1.4.2 (as happened with 1.4.1). Installed the update with the "power button + volume up" method, no good. Ran a second factory reset just for kicks, no good. Tried erasing the card and putting all the music back on it, no good. Cannot use the "factory wipe tool" thing on page 1, because I have no PC.
 
The card scans fine when I revert to firmware 1.3.3, so I'm back to that one.
 
The minimum viable product concept only works if you eventually take the next steps and make the software robust. An "update" that breaks basic functionality (scanning a card) should never have seen the light of day.


This is exactly the behavior of my DX80.
DX80 is frustrating me a lot. But soundwise it's awesome...
 
May 3, 2016 at 4:54 PM Post #4,254 of 6,795
  .... But soundwise it's awesome...

 
Agreed. Sound is the only reason I haven't returned it. (And that it can hold two cards.) But the thought of ever upgrading to a "flagship" model from this company?... not a chance. And I've already actively advised three people--and will say the same to anyone else who expresses interest in my DX80--not to buy anything from iBasso... not unless they are prepared to muddle through barely-functional software, a lot of troubleshooting, and considerable frustration.
 
May 3, 2016 at 5:09 PM Post #4,257 of 6,795
   
I was having this problem, also. It's pretty frustrating. I think it's an issue with file tagging. I'm not sure what specifically fixed it for me, but, after I cleaned up a few files that ended up showing as "(null)" after the incomplete scan, I was able to get it to scan completely without crashing.
 
I used MusicBrainz Picard to fix the problem files. Hope this helps. 

 
My stuff is all tagged with Picard (which is a bit of an adventure in itself). I have Picard set to clear existing tags and remove ID3 tags from FLAC files before tagging. I don't think I have any APEv2 tags, so I haven't set the flag to remove them. I guess the debugger in me will have to try that next. For writing tags, I have no preferences (or specific knowledge), so I go with ID3v2 version 2.4 and UTF-16 text. Some of my files have Cyrillic--do any of the Russians on this forum have advice on text encoding for my Кирпичи и т. д.? The text shows up fine with DX80 fw 1.3.3 (lurker font), and the cards scan fine, but if ISO-8859-1 or UTF-8 are better, I'm happy to switch. 
 
May 3, 2016 at 6:33 PM Post #4,259 of 6,795
May 3, 2016 at 8:42 PM Post #4,260 of 6,795
Regardind scan issue from 1.4.0 onwards, I don't understand why with 1.3.3 I had zero problems. 1.4.2 works better than 1.4.0, but still jot perfect as 1.3.3, at least for me.

 
1.4.2 playing nice over here.  A couple of null files after scan (but they still play OK).  Thanks ibasso!  
 

Users who are viewing this thread

Back
Top