Bug 7490 – Now playing time does not handle negative rate (scan backwards)

Bug 7490 - Now playing time does not handle negative rate (scan backwards)

Summary:

Now playing time does not handle negative rate (scan backwards)

Status:	RESOLVED WONTFIX

Product:	SB Controller
Classification:	Unclassified
Component:	Browser
Version:	unspecified
Platform:	PC Other

Importance:	-- minor (vote)
Target Milestone:	7.1
Assigned To:	Ben Klaas

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-03-12 00:48 UTC by Alan Young
Modified:	2008-07-01 10:20 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alan Young 2008-03-12 00:48:25 UTC

From Plauer:getTrackElapsed()

        if self.trackCorrection <= 0 then
                return tonumber(self.trackTime), tonumber(self.trackDuration)
        else
                local trackElapsed = self.trackTime + self.trackCorrection
                return tonumber(trackElapsed), tonumber(self.trackDuration)
        end

I do not understand why the test is required. Surely this correction shoudl always be applied.

(and, for some reason, the display gets completely messed up on the desktop app when rate < 0)

Comment 1 Ben Klaas 2008-03-31 09:44:24 UTC

this is a 7.1 bug

Comment 2 Ben Klaas 2008-06-06 12:53:33 UTC

Alan, is this still an issue?

Comment 3 Alan Young 2008-06-07 01:42:08 UTC

Not really, since no supplied UI with 7.1 has the ability to invoke reverse-direction audio. I plan to remove the capability entirely for 7.2.

The facility is still there (in 7.1) via the CLI and users could remap IR buttons to that functionality. Also, disabling the player-UI SongScanner plugin would expose this functionality.

Comment 4 Ben Klaas 2008-07-01 09:14:02 UTC

I think this one is a "WONTFIX". Alan, reopen and target for 7.2 if that's in error.

Comment 5 Alan Young 2008-07-01 10:20:32 UTC

No, that is fine. With 7.2 (new-streaming) there is no more 'rate'. I have left it in the status message just to keep Jive (and other UIs) happy but it is alway 1.