I haven't quite figured out under what circumstances this does and does not work with the exact same commands, but I *think* moving tends to be more sucessful when I am working with new lists that have never been synced to the player.

The changes seem to take, but when the db on the player is refreshed with a "sync" the list reverts to its old state.

Here is an example of broken behavior.

/Tags> ls
Pos FID Type Title
#1 190 playlist moof
#2 170 playlist foo
#3 180 playlist bar
Total: 0 tunes, 3 playlists
/Tags> move 180 ^#1
/Tags> ls
Pos FID Type Title
#1 180 playlist bar <-- Note the newly desired order.
#2 190 playlist moof
#3 170 playlist foo
Total: 0 tunes, 3 playlists
/Tags> sync
Starting synchronise
--- Sychronising ---
- Checking connection
- Locking player
- Checking media
- Enabling write
- Removing old databases
- Uploading
- Upload finished
- Rebuilding player database
- Rebuild result: 00000000
- Drive 0 size: 9911314432, free: 9905983488, usage: 5330944
- Drive 1 size: 9911314432, free: 9903666176, usage: 7648256
- Write protecting
- Restarting player
- Waiting.
- Reloading database
#################################
- Done
Done synchronise
Reinitializing
Database read successfully
Checking database for faults...
No faults found
/> cd Tags
/Tags> ls
Pos FID Type Title
#1 190 playlist moof <--- but my changes are gone!
#2 170 playlist foo
#3 180 playlist bar
Total: 0 tunes, 3 playlists
/Tags>



I've had similar problems with linking playlists.

This makes doing a sorted insert of a new disc a pain, and is making interfacing with all the other crap I have for my CD collection nigh impossible. I'm more interested in dictating the track and playlist order in my perl scripts than with a magic alphbetic sorted play command.


any help?

--- Carl