Posted by: woops
End Of Playlist - 18/10/2004 18:18
Every time i repower the empeg with "all" as the playlist (ie: 3 down button presses), i get "End of playlist". How can i fix this problem?
Quote:
This is why the empeg still beats anything on the market today!!!
Quote:
I'd use "down, down, down" more often, but having to restart it is always a bummer. It's too bad we can't make a work around.
Quote:
If you are correct in your assertion that the database limit is the cause of your problem, then if down-down-down creates a playlist with less than <limit> items, does the player remember where it got to?
Quote:
This is due to the scratch partition size correct?
Quote:
The weird thing is that metadata for the individual FIDs still seems to work. I remember this was based on specific sectors (or was it blocks...) based on the FID number.
Quote:
unless you're a big user of shuffle modes that depend on play-count or time-last-played.
Quote:
Or silly 3rd party applications that write song ratings to the skips count field... Hmm. I wonder what would happen if someone has a lot of FIDs and tries to use emphatic to write to a non-existent sector of hda3. What's after per-FID dynamic data? Running orders? Is 0x7000 the exact number that I should use to avoid writing past the end of the per-FID data?
Quote:
That would be bad.
Quote:
The final 14Mb of the 16Mb scratch partition is allocated to per-FID dynamic data, one FID per 512-byte sector. So the 0x7000th FID (i.e. FID 0x70000) is the first one which can't be written.
Quote:Quote:
the 0x7000th FID (i.e. FID 0x70000) is the first one which can't be written.
Assuming that your dynamic data partition is exactly 16Mb in size. That's only the minimum size. It could have been rounded up to a higher cylinder number.
Quote:Quote:
That would be bad.
Yeah, that's what I was thinking. But fortunately I am working with hda3 and not hda. Still, to avoid the corrolaries of Murphy's Law, I'm going to put in a check for 0x7000 in the next version.