Bug 14348 – Restarting paused podcast on Mediafly jumps to next podcast

Bug 14348 - Restarting paused podcast on Mediafly jumps to next podcast

Summary:

Restarting paused podcast on Mediafly jumps to next podcast

Status:	RESOLVED DUPLICATE of bug 14230

Product:	SqueezePlay
Classification:	Unclassified
Component:	App Gallery
Version:	7.4.x
Platform:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	Investigating
Assigned To:	Mickey Gee

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-27 13:50 UTC by Mickey Gee
Modified:	2009-10-02 08:45 UTC (History)
CC List:	4 users (show)

See Also:
Category:	Bug

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 Mickey Gee 2009-09-27 13:50:20 UTC

Comment 1 Mickey Gee 2009-09-27 13:52:40 UTC

If you use Baby r7784, pause a Mediafly podcast and then unpause it, it does not restart the paused podcast but jumps to the next podcast. Running with SC from Sept 27.

Comment 2 Mickey Gee 2009-09-27 13:54:02 UTC

Once it's gone to the next podcast, you can't go to and finish the one you were listening to. If you go to Mediafly and a menu of podcasts and then pick the paused one to play, it jumps to the next one again.

Comment 3 Alan Young 2009-09-27 23:09:41 UTC

player.source=info log please

Comment 4 Alan Young 2009-09-29 01:40:26 UTC

Mickey, can you seek in the track in question, before you try to pause it?

Andy, do you know if the 'canSeek' attribute of Mediafly track metadata is usually true or false. Do you know if mediafly 'knows' what track you have already listened to and auto-skips to the next if you try to listen to it again?

This may be a duplicate of bug 14017.

Comment 5 Alan Young 2009-10-01 01:48:58 UTC

Actually, perhaps this is a dup of bug 14230. Please retest with SC 7.4.1 r28696 or better.

Comment 6 Alan Young 2009-10-02 08:45:04 UTC

Mickey, in the absence of further info I'm going to assume that this is a dup of 14230 and close it as such. Please reopein it (with more info) and undup it if it reoccurs with 7.4.1 r28722 or better.

*** This bug has been marked as a duplicate of bug 14230 ***