- Status Closed
- Percent Complete
- Task Type Bugs
- Category Music playback
- Assigned To No-one
- Operating System
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#1557 - Possible fade out bug
JBR20-CVS-030720
When listening to a long file (1500min+), after pressing
stop, I get a what appears to be a normal fade out, but
it end in an abrupt rise in volume (to the normal level)
for what I think is about 100ms.
I don’t think the problem is related to the file length, but
I didn’t try other files. The file is usually played based on
the resume feature.
Closed by amiconn
2005-05-13 00:17
Reason for closing: Fixed
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
2005-05-13 00:17
Reason for closing: Fixed
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
Logged In: YES
user_id=988982
Fixed in cvs
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
It is definetly unrelated to the resume feature, it seems that
the volume is cranked back up before an audio buffer is
completely empty.
Fixed in cvs
I thought we left fixed issues as "open/fixed" status, until the
next full release comes along, rather than "closed/fixed"???
Björn told me that this policy is no longer applicable. Bugs
should now be closed immediately after fixing them. So I did.
The reason for that is simply that the amount of open
entries that we otherwise need to walk through and close at
a later time becomes quite overwhelming (I've done it
several times, it takes hours of manual clicking).
It is better if we all take care of whatever we can now and
make sure to get them out of our face when they're fixed.
One by one.