or Connect
Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › DX50 Bug List, Wish List Fix
New Posts  All Forums:Forum Nav:

DX50 Bug List, Wish List Fix - Page 47

post #691 of 1211
Quote:
Originally Posted by Foolwolf View Post
 

How can a demand for a working UI be UI main priority?

If it were, I WOULD be still on my D2 Cowon, a Samsung device or whatnot - but I want to have better sound - but if I can't use the player due to the UI - then it is a moot point - I could as well go around using a brick - no music through either.

 

I'm sad to hear that you had troubles with UI before and it seems that many DAP's are expereincing this - so my point stands - if they go for Android - check what is already working and the Ui wouldn't become that much of a hassle.

 

I'm sorry to say that just because you fight the windmills and suffer more doesn't earn you any hero-points in my book. That isn't the question, the question and matter is to get the sort of product that you paid for and was looking for to buy. In this case, a player that was better than my D2, had a decent user interface - allowing me to play music - duh, I know picky of me eh? ;) That's about it. I could have opted for a FiiO X3 - and may still get one, but the DX50 sounded promising. regarding the AK100 and 120, I have seen a lot of bashing of that player all over media as well.

 

I share the wish for better UI... and good to know you are in for the sound.  I just think your reference to "DAP in this price range" a bit hilarious as $239 puts it squarely at the low-to-mid end for "audiophile DAPs"..... and not too surprising you get low-to-mid end UI with lo-to-mid money.... no need for any points for me kthx.

 

Just want to provide another perspective where one actually appreciate the level of completeness and finishing of a "DAP in this price range"..... we can of course agree to disagree, that's what fora are for right?  :cool: 

post #692 of 1211

Having been through all this with the DX100, I'm not particularly bothered as long as the sound justifies the bugs.

However, putting things in alphanumeric order should be fairly straightforward for any developer. Also, they really should have ironed out these minor annoying bugs before release, considering they had already seen most of them with the DX100.

post #693 of 1211
Quote:
Originally Posted by Foolwolf View Post

Well, these are tips that I have more or less already checked. I haven't checked to see if I have any filename more than 30 instances long, but I don't find that likely, and checking where scans have ended, the tags don't differ, nor do I have weird types or long filenames there. So, the pity seems to be more that there is something else that is the problem. My tags look more or less exactly like the ones you described. Even the size of jpg embedded...

I'm not familiar with "CopyInOrder" utility. nor do I believe that I should need to have so many utilities to enjoy a DAP in this price range. Still, might help.
Guess I will take another dive into MP3tag...

Thanks for the link though I appreciate that you took time to post them, that should be pinned in a post somewhere at the top on "how to".
Yep, I agree it shouldn't be this way, but believe me, filename length is the reason you are having scan issues. Once I used MP3Tag to rename the files to 30 characters long it scanned and loaded all my albums. I even tried 35 but that didn't work so there is a sweet spot there somewhere. I'll dig out my laptop tomorrow and post the script I used to auto change the filenames. It was something like [track] LENGTH$[title],30. But I should get the exact script. With that script re-naming 5,000 filenames took about a minute.

While I agree with everyone's comments about sort orders, I have been around computers for 30 years and timestamps on files have always had some influence on some pieces of software so this is no surprise to me especially with Linux based firmware. IBasso should get this right for sure, and I think they will address most if not all the issues raised with them in time going on past experience with them. Let's face it Windows and MacOS both have automatic update systems to load updates and fixes all the time. The DX50 like most modern DAPs is a micro processor device and we would be expecting unrealistic outcomes if we thought these things start life perfect and without unexpected idiosyncrasies despite our desires. Just some old fart's perspective.
post #694 of 1211
Quote:
Originally Posted by kkcc View Post
 

 

I share the wish for better UI... and good to know you are in for the sound.  I just think your reference to "DAP in this price range" a bit hilarious as $239 puts it squarely at the low-to-mid end for "audiophile DAPs"..... and not too surprising you get low-to-mid end UI with lo-to-mid money.... no need for any points for me kthx.

 

Just want to provide another perspective where one actually appreciate the level of completeness and finishing of a "DAP in this price range"..... we can of course agree to disagree, that's what fora are for right?  :cool: 

Well, not all Audiophile stuff needs to be ridiculously priced IMHO, and sure - you get what you pay for, but they also choose Android, and Android has some pretty nifty things for free to use and a community of developers to boot at that - and not using that and being a bit pricier than an average MP3 player was what I referred to.

Also, sorry for being snide - I will give you a point for coming back on my post in a very leveled way, and I mean that i a very respectful manner and shame on me for being a bit snide in the earlier remark. I blame it on all those failed scans and hours of wasted listening time - they aren't that many to begin with.

 

When it comes to UI design etc, I simply guess that it falls closer to what I know and have seen, so I had probably a higher demand knowing what is there for free and what you can do with very little effort. And as I mentioned earlier, it is fancy things, it is the basic being able to scan and get your files presented as albums, a list of all files and being able to play them in file by file, album by album, folder by folder or simply play all on repeat and shuffle - neither have worked well for me.

 

I did come home and found my first scan gone through and all albums showing for the first time. But this time - all in wav...

post #695 of 1211
Quote:
Originally Posted by kryten123 View Post

Having been through all this with the DX100, I'm not particularly bothered as long as the sound justifies the bugs.
However, putting things in alphanumeric order should be fairly straightforward for any developer. Also, they really should have ironed out these minor annoying bugs before release, considering they had already seen most of them with the DX100.
I'm quoting you only as an example of the sorting order so my reply is meant to be general not directed at your post.

While you are entirely correct that it shouldn't be hard, it isn't that simple either. In an earlier time I wrote computer code, and it was normal to set maximum string lengths and define certain constraints because there was only so much memory allocated for software to make room for data and so on. Using code sparingly also speeds up processing an responsiveness. And the more different ways the software needs to consider how the user has formatted their files adds further complexity. What might suit your files may not suit someone else's. Eg what if your files all start with the track number? Great, should be easy. But how many don't use the track number in the filename. Then the coder has to ignore the file name and look in the tag for the track number. What if that hasn't been put there? Ah... The coder uses the file timestamp. And so on. All this adds to potential conflicts and possible errors.

I remember when I got my first iPod and run in with iTunes. I had to make wholesale changes to my file naming habits, and load up tags I didn't even knew existed just to get some albums to be contiguous. Many were fragmented just like the DX50 was on FW 1.0. Even now albums on iPods list in artist order, not album title order.

So let's lighten up, make a couple concessions to accommodate its formatting (none of which has caused me an issue on my other DAPs), an enjoy the music.
Edited by Jpfe8851 - 10/3/13 at 7:48am
post #696 of 1211
Quote:
Originally Posted by Foolwolf View Post
 

Well, not all Audiophile stuff needs to be ridiculously priced IMHO, and sure - you get what you pay for, but they also choose Android, and Android has some pretty nifty things for free to use and a community of developers to boot at that - and not using that and being a bit pricier than an average MP3 player was what I referred to.

Also, sorry for being snide - I will give you a point for coming back on my post in a very leveled way, and I mean that i a very respectful manner and shame on me for being a bit snide in the earlier remark. I blame it on all those failed scans and hours of wasted listening time - they aren't that many to begin with.

 

When it comes to UI design etc, I simply guess that it falls closer to what I know and have seen, so I had probably a higher demand knowing what is there for free and what you can do with very little effort. And as I mentioned earlier, it is fancy things, it is the basic being able to scan and get your files presented as albums, a list of all files and being able to play them in file by file, album by album, folder by folder or simply play all on repeat and shuffle - neither have worked well for me.

 

I did come home and found my first scan gone through and all albums showing for the first time. But this time - all in wav...

 

Not all android devices are made equal.  Stock Android capped the audio output at 16/44.1 and any maker who wishes to "ride" on android for hi res music don't get to "free ride", they need to rewrite the whole stack.

 

FYI as far as I know only three android devices offer HD music capability - iBasso DX100 ($650), Samsung Galaxy Note 3 N900/N9002/N9005 ($750), and LG G2 ($750).   FWIW even with my N9005 the stock Music Player app didn't scan my micro SD card directly transplanted from my Note 2 n7100 initially.  And it is a quad core 2.4Ghz Krait on Snapdragon 800 chipset running the latest and greatest anrdoid jellybean 4.3.   Not to earn hero point or what not but just to point out there IS a learning curve to any new devices for a user with the possible exception of Apple and hence my suggestion for the iDevices.  Getting these music into the Database is part the device and part the user efforts.  Apple is great at helping the users and that's what made them great in the first place (iPod, and the iPhone)!

 

I also know of two upcoming ones Sony F880 ($405 for 64gb, no sd card slot), or the Sony ZX1 ($750, 128gb).  The F880 might be your best bet but no telling if it would be actually better sounding than the cowens.


Edited by kkcc - 10/3/13 at 8:00am
post #697 of 1211
Quote:
Originally Posted by Jpfe8851 View Post


I'm quoting you only as an example of the sorting order so my reply is meant to be general not directed at your post.

While you are entirely correct that it shouldn't be hard, it isn't that simple either.

I used to write (many years ago) in machine code and while the constraints may have applied back then....very unlikely to today. A modern chip should have sufficient memory to carry out basic alphanumeric functions.

I don't own apple products, but I am led to believe they can manage it.

;)

post #698 of 1211
Quote:
Originally Posted by Jpfe8851 View Post


I'm quoting you only as an example of the sorting order so my reply is meant to be general not directed at your post.

While you are entirely correct that it shouldn't be hard, it isn't that simple either. In an earlier time I wrote computer code, and it was normal to set maximum string lengths and define certain constraints because there was only so much memory allocated for software to make room for data and so on. Using code sparingly also speeds up processing an responsiveness. And the more different ways the software needs to consider how the user has formatted their files adds further complexity. What might suit your files may not suit someone else's. Eg what if your files all start with the track number? Great, should be easy. But how many don't use the track number in the filename. Then the coder has to ignore the file name and look in the tag for the track number. What if that hasn't been put there? Ah... The coder uses the file timestamp. And so on. All this adds to potential conflicts and possible errors.

I remember when I got my first iPod and run in with iTunes. I had to make wholesale changes to my file naming habits, and load up tags I didn't even knew existed just to get some albums to be contiguous. Many were fragmented just like the DX50 was on FW 1.0. Even now albums on iPods list in artist order, not album title order.

So let's lighten up, make a couple concessions to accommodate its formatting (none of which has caused me an issue on my other DAPs), an enjoy the music.

 

I think I agree with the gist of your message, and I understand you're just making a metaphor to illustrate programming constrains to non-technical persons.  I think the limitation is no longer the memory space or stacks, but just the iBasso programmers are not used to these old school programming before the days of library/function calls that handled such basic string parsing or error handling automatically.  But since they need to rewrite portion of the android OS to customize for hi res music, I'm not sure how low level they need to code at and not even sure if now-a-days the programmers are still taught to manually do these parsing or exception handling etc properly. 

 

Nonetheless, compared to other similar vendors, I am still impressed at the speed of them fixing and changing things base on customer feedback.  Much more responsive than say iriver or hifiman.


Edited by kkcc - 10/3/13 at 8:08am
post #699 of 1211
Quote:
Originally Posted by kkcc View Post
 

not even sure if now-a-days the programmers are still taught to manually do these parsing or exception handling etc properly. 

 Seems unlikely considering the inability to sort correctly.

Although I agree that they are very quick at implementing fixes, these basic bugs really should not occur....even more so as they have experience with this issue with the DX100

post #700 of 1211
Quote:
Originally Posted by Hobgoblinpie View Post
 

 

When you eject the card the DX50 resets the list, so it's not the most optimal way.

 

i have found that if you eject the card and do not turn the unit back on until you have inserted the card back in, nothing in the library list is lost. if you turn the unit back on before inserting the card then yes it is a pain :)

post #701 of 1211
Quote:
Originally Posted by Jpfe8851 View Post

Agreed. One more thing, the DX50 seems prone to mis-scans when some types of non-music files are present. I use a batch delete file to remove any orphan files remain. I accidentally left the batch file on the SD cards root folder and it stopped scanning early. Deleted the batch file and she's sweet.

 

i have a hidden .dat file located in my music folder on my sdcard. i use synctoy to keeps the sdcard updated with new music etc from my laptop. i wonder if the .dat file has any negative impact on scanning when the sdcard is put into dx50?

post #702 of 1211

Here is a strange quirk I discovered yesterday with 1.1.6.  (Gapless set to 10 seconds.)  

On a new FLAC rip from Gov't Mule album Shout!, the first song would have a skip at about 24 seconds.  I was able to reproduce it 3 times on the dx50 yesterday.  Then I checked the song on the ipod touch.  The mp3 on the ipod worked fine.  The FLAC was the original source for the mp3.  (FLAC file >> converted to mp3 320 >> itunes >> itouch).  No skipping.

Last night I upgraded to 1.2.  Today I checked the same file.  No skip after the upgrade.  So that was cool.

 

Second quirk.

I listened to a complete album.  It stopped at the end.  I let the DX50 time out and shut off.

I turned it back on.  Searched artists.  Albums.  Selected the new song i wanted.  And it started playing the last song of the album it timed out with.

Not a big deal.  But definitely not what I expected.

post #703 of 1211
Quote:
Originally Posted by kkcc View Post
 

 

I think I agree with the gist of your message, and I understand you're just making a metaphor to illustrate programming constrains to non-technical persons.  I think the limitation is no longer the memory space or stacks, but just the iBasso programmers are not used to these old school programming before the days of library/function calls that handled such basic string parsing or error handling automatically.  But since they need to rewrite portion of the android OS to customize for hi res music, I'm not sure how low level they need to code at and not even sure if now-a-days the programmers are still taught to manually do these parsing or exception handling etc properly. 

 

Nonetheless, compared to other similar vendors, I am still impressed at the speed of them fixing and changing things base on customer feedback.  Much more responsive than say iriver or hifiman.

 

Yep... exactly what I meant. Not saying iBasso shouldn't fix things. Just that someone may have not told the code to ignore longer strings... so it goes into some sort of error loop... I just found that by truncating the filename my DX50 scans fine and all my albums appear. No rescans when I restart it.

post #704 of 1211
Quote:
Originally Posted by alphabetagaga View Post
 

 

i have a hidden .dat file located in my music folder on my sdcard. i use synctoy to keeps the sdcard updated with new music etc from my laptop. i wonder if the .dat file has any negative impact on scanning when the sdcard is put into dx50?

 

Someone earlier in this or the main thread posted a little batch file to remove Mac hidden files. I've actually deleted all hidden files like thumbnails etc. as a precaution. The DX only needs the LOST.DIR and the images file on the main internal memory and of course your music files to work so try deleting the .dat file (copy to another location first).

post #705 of 1211

I still have MicroSD card scanning problem...basically, the DX50 won't scan it in an entirely.  Any solution?  I'm using top-rated Sandisk Class 1 MicroSD card with 64GB of memory.

New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Portable Source Gear
Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › DX50 Bug List, Wish List Fix