- Status Closed
- Percent Complete
- Task Type Patches
- Category Drivers
- Assigned To No-one
- Operating System All players
- Severity Low
- Priority Very Low
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#6566 - Faster drive spindown
A quick patch to allow setting the drive spin down time between 1 and 3 seconds (3 to 254 is left alone) I tried -1 (instant) and 0 (never), but instant caused all kinds of issues and the drive would actually stay powered longer (spool down the up then read then down then up then read, as opposed to down up read read down)
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
synced, also I forgot to mention that in low power (less then 10%) I do use -1. In hopes that your listening to music, and not browsing. If your browsing this might not be a good thing. Ideas?
The spindown time is only considered when a user action triggerd the disk to spin up.
If you are just listening to music and the buffer is refilled, the disk spins down
as soon as reading is done.
The low power mode will probably be removed as it is felt (at least by me) that it is
a strange idea to try to save battery whe the level is low and waste it when the level
is high. And few people like when settings are automatically changed.
This can’t be accurate, change the spin down time to -1 and watch your player. even when doing non-user action based hard drive reads you will notice it spin up and then right back down where as now you do not.
I set set spin down time to a high value using the menu and when spinning up just to read more data the spindown is immediate.
Since the spindown time only matters for user actions and it can be already set for as low as 3 seconds, I don’t think this patch is necessary.