iRiver filename truncation

by **hmoffatt** » Wed Dec 15, 2004 7:15 am

jiri wrote:There was a new version uploaded to http://www.mediamonkey.com/beta/d_iRiverH.dll

It has on option to select whether to use ASCII or Unicode DB format. It should help in your case.

That fixes it. My files with 52 character names play fine with an ASCII format database. Must be a firmware bug. I'm using 1.63(US) which is the latest.

Thanks,

Hamish

by **jiri** » Tue Dec 14, 2004 6:04 pm

There was a new version uploaded to http://www.mediamonkey.com/beta/d_iRiverH.dll

It has on option to select whether to use ASCII or Unicode DB format. It should help in your case.

Jiri

by **hmoffatt** » Tue Dec 14, 2004 8:04 am

hmoffatt wrote: It looks like databases created with TDT are not Unicode encoded. I don't know what happens with iRiver's own software, as it crashes on almost all of my OGG files.

OK, very confused now. Found the following.

Using the filenames created by MediaMonkey (truncated to 52 characters),

Unicode Database by MM -> 5 files (52 character names) won't play
Unicode Database by iFish -> same files won't play
ISO-8859-1 database by TDT -> all files play fine
ISO-8859-1 Database by iFish -> all files play fine

Must be a firmware bug.

Hamish

by **hmoffatt** » Tue Dec 14, 2004 6:37 am

Rusty - not logged in wrote:Hamish,

Please let us know what you find re. what the problem is regarding some tracks that aren't read by the H140/H120.

btw, if you look at the db on that device that is created by default, is unicode enabled? I'm wondering if there are bugs in the device regarding handling of unicode vs. a problem in the DB format that MM is creating.

It looks like databases created with TDT are not Unicode encoded. I don't know what happens with iRiver's own software, as it crashes on almost all of my OGG files.

I do have a one whole album in the TDT database which the iRiver won't player either.

I synced a single album of 10 tracks with MM. 5 of those tracks don't play, and all of them have 52 character filenames. The 5 that do play all have shorter filenames. However, my TDT-created database contains many files with 52 character names that do play OK.

Maybe the H140 has a problem with 52 character names in Unicode format. Is it possible to make the format and/or the maximum length configurable so that I can experiment until it works?

regards
Hamish

by **Rusty - not logged in** » Mon Dec 13, 2004 9:24 pm

Hamish,

Please let us know what you find re. what the problem is regarding some tracks that aren't read by the H140/H120.

btw, if you look at the db on that device that is created by default, is unicode enabled? I'm wondering if there are bugs in the device regarding handling of unicode vs. a problem in the DB format that MM is creating.

-Rusty

by **hmoffatt** » Sun Dec 12, 2004 4:38 pm

hmoffatt wrote:I found a utility called iFish (find it on sourceforge) which allows you to view the database from the player. I read in my database created using TDT and it looked fine. Then I removed that and created a database with Media Monkey, and all the characters look trashed in iFish. Very strange.

Even with a fresh database, the player won't play some of the files from the MM-created database. Obviously I need to find a different database viewer because iFish isn't doing the trick.

OK, it turns out that your database is in UTF-16 and iFish just needed a settings change to read that correctly.

Hamish

by **hmoffatt** » Sun Dec 12, 2004 6:51 am

jiri wrote:As I wrote I don't have H140 and so I can't test it right now, but from what I reviewed the DB should be ok (i.e. the filenames there are also properly truncated to 52 characters). Maybe you could try to delete iRivNavi.iDB file from the device completely and let it MM create again (right click on the device in MM). Possibly there just something wrong remained from the incorrectly truncated files...

Do you do anything particularly special with the encoding of text in the database entries? eg use Unicode?

I found a utility called iFish (find it on sourceforge) which allows you to view the database from the player. I read in my database created using TDT and it looked fine. Then I removed that and created a database with Media Monkey, and all the characters look trashed in iFish. Very strange.

Even with a fresh database, the player won't play some of the files from the MM-created database. Obviously I need to find a different database viewer because iFish isn't doing the trick.

thanks,
Hamish

by **jiri** » Sat Dec 11, 2004 2:52 pm

As I wrote I don't have H140 and so I can't test it right now, but from what I reviewed the DB should be ok (i.e. the filenames there are also properly truncated to 52 characters). Maybe you could try to delete iRivNavi.iDB file from the device completely and let it MM create again (right click on the device in MM). Possibly there just something wrong remained from the incorrectly truncated files...

Jiri

by **hmoffatt** » Wed Dec 08, 2004 4:49 pm

jiri wrote:You were right, there was a problem in truncation. I uploaded a modified version of the device plug-in to http://www.mediamonkey.com/beta/d_iRiverH.dll , you can replace the one in Plugins folder.

As far as I know the 52 limit applies to each part of the full path. However I cannot test it because I only have H320 which doesn't have such limit at all.

Thanks, that fixes the filename extension problem.

I think you are right about the 52 characters per element. I had a file called \Tuba\Volume Three\Edward Gregson Tuba Concerto -- Allegro deciso.ogg which played ok. (The final part is < 52 characters (without truncation) but the whole path is longer.)

However I have a problem still in that filenames that were truncated during sync don't play from the DB properly. The iRiver just doesn't play them when you select them. Filenames that didn't have to be truncated are okay.

thanks,
Hamish

by **jiri** » Wed Dec 08, 2004 11:09 am

You were right, there was a problem in truncation. I uploaded a modified version of the device plug-in to http://www.mediamonkey.com/beta/d_iRiverH.dll , you can replace the one in Plugins folder.

As far as I know the 52 limit applies to each part of the full path. However I cannot test it because I only have H320 which doesn't have such limit at all.

Jiri

by **hmoffatt** » Wed Dec 08, 2004 7:18 am

hmoffatt wrote: The resulting file after sync is

\Tuba\Volume Three\Eric Ewazen Concerto for -- Wind Ensemble-Allegro ri

Also, I notice that the whole filename is ~71 characters in length, while the base filename is 52 characters. I think the H1xx requires that the entire filename (including whole path) is 52 characters?

Hamish

by **hmoffatt** » Wed Dec 08, 2004 7:16 am

jiri wrote:MM shouldn't remove the extension on synchronization. Could you check what's the original filename and what is the synchronized version (i.e. how was is truncated)?

Well I have my "Synchronize tracks to" format set to:
\<Genre>\<Album>\<Title>

I have a file
C:\mp3\Brass\DePaul University Wind Ensemble - Volume Three\06-Eric Ewazen Concerto for Bass Trombone and Wind Ensemble -- Allegro ritmico.ogg

Genre = Tuba
Album = "Volume Three"
Title = "Ralph Vaughan-Williams Concerto for Basstuba -- Rondo alla Tedesca"

The resulting file after sync is

\Tuba\Volume Three\Eric Ewazen Concerto for -- Wind Ensemble-Allegro ri

No extension. 3 out of 10 tracks got copied over without extensions.

I can supply a copy of the file if that's helpful.

thanks
Hamish

by **jiri** » Wed Dec 08, 2004 4:19 am

MM shouldn't remove the extension on synchronization. Could you check what's the original filename and what is the synchronized version (i.e. how was is truncated)?

Jiri

by **hmoffatt** » Wed Dec 08, 2004 2:18 am

ukandrewf wrote:i think you just have to ensure that your files are no longer than 48 characters +4 for the extension ie .ogg and you should be fine.

How do you propose that I do that?! Rename 4K files manually?

The latest alpha has a filename truncation option which ensures that filenames on the device are <= 52 characters long, as the H1xx requires. However it looks like it does not necessarily preserve the extension, and the H140 seems to need it.

It's the whole path name that's important, not just the base filename and extension.

Hamish

by **ukandrewf** » Tue Dec 07, 2004 8:44 pm

i think you just have to ensure that your files are no longer than 48 characters +4 for the extension ie .ogg and you should be fine.

iRiver filename truncation

Post a reply

Expand view Topic review: iRiver filename truncation

Re: Details re. problems on H120/H140

Re: Details re. problems on H120/H140

Details re. problems on H120/H140

Re: simple fix

simple fix