INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Device sync: capacity muddle  (Read 8670 times)

chrisjj

  • Citizen of the Universe
  • *****
  • Posts: 750
Device sync: capacity muddle
« on: July 03, 2013, 08:56:33 pm »

EDIT: These problems persist on 19.0.91 e.g. here sync predicts 587Mb free http://img819.imageshack.us/img819/5296/pk2q.png but result is only 254Mb free http://img819.imageshack.us/img819/9536/1p6o.png . Reported at http://yabb.jriver.com/interact/index.php?board=32.0 .

I'm finding two issues when syncing to nearly fill a MTP handheld device.

1 MC says there's sufficient capacity, but when sync is complete some of the files are missing. It is as if MC has miscomputed the space required for the files.
2 A sync that omits some files fails to warn - it says simply 'Finishes' whereas in fact apparently it has aborted the transfer on reaching capacity.

Here's an example.

Before: MC reports ready to sync 2312 .WMA files to a Creative ZEN.


One warning sign is the status bar total file size is slightly greater than the Explorer device capacity. And that doesn't include the on-device .ALB files that get created by the sync.

After: MC says Finished, but the number of "On Device" found by MC and .WMAs found by Explorer is 1962. Meaning 350 files are missing.


And if I send just those 1962 to a freshly formatted device, MC says 347Mb space will remain:



but after the sync, virtually no space remains:



A workaround of course is to leave some capacity unused. I haven't yet found out how much this needs to be.

Anyone have any input on this?
Logged

chrisjj

  • Citizen of the Universe
  • *****
  • Posts: 750
Re: Device sync: capacity muddle
« Reply #1 on: July 23, 2013, 11:30:35 am »

A workaround of course is to leave some capacity unused. I haven't yet found out how much this needs to be.

Finding out how much this needs to be seems rather difficult. The answer depends on space used by additional objects created during the sync, inc. playlist files, folders, .ALB files, and (to a lesser extent) JRiver's own files JRInfo.xml and JRState.xml.

FWIW, below are two success cases. Based on those, my proposed rule of thumb to avoid incomplete sync: For a sync list having approx. X tracks and approx X/10 playlists having approx X track references in total, ensure that JR MC device window shows an amount available which is at least 7% of the device's formatted free space figure.

Creative ZEN 8Gb model, firmware V1.21.03e name "ZEN G", no user wallpaper, newly formatted.
Before sync:
Device shows Free space: 7.62GB http://img20.imageshack.us/img20/4213/1h6.png
MC 18.0.206 with a sync list containing 1953 (track) files (7.1Gb) plus 182 playlists containing a total of 2182 track references. MC device window says 566 MB available
http://img12.imageshack.us/img12/3639/cn3v.png
After sync:
Sync success confirmed by device UI saying Track Count: 1953, Playlist Count: 182. Also: Free Space: 45MB, Album Count: 107, Photo Count: 0, Video Count: 0
Device's Explorer Properties says Used space: 7.44GB and Free space: 188.0 MB http://img849.imageshack.us/img849/6798/5kic.png

Creative ZEN 8Gb model, firmware 1.21.01e, name "ZEN A", user wallpaper, newly formatted.
Before sync:
Device shows Free space: 7.49GB http://img707.imageshack.us/img707/156/gc0j.png
MC 18.0.206 with a sync list containing 1953 (track) files (7.1Gb) http://img826.imageshack.us/img826/9711/yzyi.png plus 182 playlists containing a total of 2182 track references. MC device window says 423 MB available
After sync:
Sync success confirmed by device UI saying Track Count: 1953, Playlist Count: 182. Also: Free Space: 188Mb, Album Count: 107, Photo Count: 0, Video Count: 0
Device's Explorer Properties says Used space: 7.44GB and Free space: 45.0 MB http://img196.imageshack.us/img196/3840/3b91.png

Note: MC device window "X MB available" means X Mb remaining free after the sync.
Logged

chrisjj

  • Citizen of the Universe
  • *****
  • Posts: 750
Re: Device sync: capacity muddle
« Reply #2 on: April 10, 2014, 07:13:02 am »

FTR, these two bugs persist on 19.0.118.
Logged
Pages: [1]   Go Up