Skip to content

drive reporting curr_frame after the range we asked it to play can confuse CDStat(). #22

Description

@cassella

In CDStat(), at "This loop finds the first track",

With this vtrackinfofile, after track 12 has finished, but before we've
started track 13, curr_frame can be 229230, almost 500 frames after it
should have stopped. The drive has stopped playing, so
CDAUDIO_NOSTATUS, but this loop leaves curr_track 13, and
UpdateDisplay() will think we've finished track 13, so it will skip to
the next track.

(b30c1b0d.vtrackinfo)

VTITLE12=Spaceman
VFRAMES12=PTRACK12-228763
VTITLE13=Bye
VFRAMES13=229214-PTRACK12

*/

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions