After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 350297 - Launch the player ASAP
Launch the player ASAP
Status: RESOLVED FIXED
Product: totem
Classification: Core
Component: Browser plugin (obsolete)
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Christian Persch
totem-browser-maint
: 171873 359362 (view as bug list)
Depends on:
Blocks: 353097 361510 364020
 
 
Reported: 2006-08-07 15:42 UTC by Bastien Nocera
Modified: 2006-11-15 17:23 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
first patch, for testing and review (163.67 KB, patch)
2006-11-13 12:28 UTC, Christian Persch 		none Details | Review
updated patch (173.79 KB, patch)
2006-11-14 21:01 UTC, Christian Persch 		committed Details | Review

Description Bastien Nocera 2006-08-07 15:42:23 UTC 
When parsing a playlist, we should launch the player ASAP with the logo, and the use SetLocalFilename to set the file.

Test:

html:

<embed
src="asxplaylist.asx"
type="application/x-mplayer2" width="896" height="384" controller="true"
autoplay="true">

asxplaylist.asx:
<ASX version = "3.0">
<TITLE>Bastien's Tests</TITLE>
<Entry>
<Ref href = "http://localhost/big.mov" />
</Entry>
</ASX>
Comment 1 Bastien Nocera 2006-09-04 12:39:46 UTC 
*** Bug 171873 has been marked as a duplicate of this bug. ***
Comment 2 Christian Persch 2006-09-04 13:31:57 UTC 
I've tried to do this, by launching the viewer in New and returning 0 from WriteReady until the viewer is fully launched. The problem is that this causes mozilla to try to resume the stream every 100ms (calling WriteReady again), and causes high CPU load (~33%) until we can accept the data...
Comment 3 Bastien Nocera 2006-09-04 21:00:15 UTC 
Aren't we stuck in the main loop until the front-end is ready, when launching the viewer, or is WriteReady in that main loop?
Comment 4 Christian Persch 2006-09-04 22:11:34 UTC 
No, I modified it to launch but not wait for startup, and instead return 0 from WriteReady until the startup is complete.
Comment 5 Bastien Nocera 2006-10-05 10:16:31 UTC 
*** Bug 359362 has been marked as a duplicate of this bug. ***
Comment 6 Bastien Nocera 2006-10-05 10:21:07 UTC 
bug 359362 was about a problem with _write() being called before _set_window()
resulting in the viewer being started without a Window to plug into, and then
another time.

We should start the viewer as soon as possible (in _new()), cache data in
_write(), and start the media backend in _set_window() if not hidden.
Comment 7 Christian Persch 2006-10-16 20:26:36 UTC 
I'm working on this.
Comment 8 Christian Persch 2006-11-13 12:28:59 UTC 
Created attachment 76475 [details] [review]
first patch, for testing and review
Comment 9 Christian Persch 2006-11-14 21:01:10 UTC 
Created attachment 76593 [details] [review]
updated patch