Thank You for your continued support and contributions!
I didn't actually realise/remember that the DB listing tells you the length of the track (is that a relatively-new feature, or has it always done that?).
Could it be something odd about your mp3 encoder?
Or the files are getting corrupted in some way?
Are they VBR? (which sometimes seem to end up with incorrect bitrates reported - I think in the file headers - which maybe can cause confusion as to the real length of a track).
When you play them in rockbox does the time played/time remaining displayed in the WPS come out consistent with the actual length of the track or the length stated in the database listing?
on my iPod all files and directories have 6-character long filenames which are created as a hex-representation of the i-node number the file/directory as stored on my NAS.
If you change even one byte in a moved file (imagine retagging your music library with respective changes of file/directory names), everything will still be transferred over network.
It’s a small Python script that will dump inodes for every file and directory within a directory tree to a text file, you then do your big changes and after you run it again, it will produce a human-readable Python (or shell) script which you can run on the remote machine to replicate the changes. If there are any remaining changes besides renaming and moving, you may finish them manually or using Unison, rsync or similar.
This makes you completely dependent on the rockbox database and seems a little nutty to me.
You might get some value out of this: https://web.archive.org/web/20240305070623/https://www.pkrc.net/detect-inode-moves.htmlQuoteIf you change even one byte in a moved file (imagine retagging your music library with respective changes of file/directory names), everything will still be transferred over network.
--no-whole-file, --no-W Disable whole-file updating when it is enabled by default for a local transfer. This usually slows rsync down, but it can be useful if you are trying to minimize the writes to the destination file (if combined with --inplace) or for testing the checksum-based update algorithm.--inplace This option changes how rsync transfers a file when its data needs to be updated: instead of the default method of creating a new copy of the file and moving it into place when it is complete, rsync instead writes the updated data directly to the destination file.
Page created in 0.054 seconds with 16 queries.