[Gstreamer-bugs] [Bug 118604] Changed - Mozilla plugin is broken

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=118604

Changed by ds at schleef.org.

--- shadow/118604	Thu Sep 18 09:53:16 2003
+++ shadow/118604.tmp.26624	Fri Sep 26 18:53:29 2003
@@ -16,6 +16,86 @@
 Summary: Mozilla plugin is broken
 
 The Mozilla plugin doesn't work very well in many situations, including
 blocking the browser, hanging when it can't find an audio device, not
 reparenting correctly.  (These are from memory, so they might not actually
 be problems.)
+
+------- Additional Comments From ds at schleef.org  2003-09-26 18:53 -------
+[15:33] < dolphy> ds-work: i should try to fix the mozilla plugin
+[15:33] < ds-work> dolphy: that's a hard problem
+[15:34] < dolphy> #118604 ?
+[15:34] < ds-work> yes
+[15:34] -!- clahey is now known as cl_away
+[15:34] < dolphy> i think the reparenting can be fixed
+[15:34] < dolphy> i guess it s my mistake
+[15:34] < ds-work> basically, mozilla wants to push data to the plugin
+at a rate 
+chosen by mozilla
+[15:34] < dolphy> control hiding is also broken i can fix that
+[15:35] < dolphy> spider might not like that
+[15:35] < dolphy> but on my machine i manage to get a lot of media
+played in the 
+moz plugin
+[15:35] < ds-work> the plugin needs to either cache data before
+pushing it to 
+the pipe connecting to gst-player
+[15:35] < ds-work> or gst-player needs to cache everything coming in,
+and pull 
+as fast as possible
+[15:36] < ds-work> the latter is ideal, but very hard.  It means
+putting the 
+pipeline into PLAYING as fast as possible
+[15:36] < dolphy> hmm so moz pushes to the plugin at the download rate..
+[15:37] -!- md``` [~illuminat at pD950BDDF.dip.t-dialin.net] has joined
+#gstreamer
+[15:37] -!- md`` [~illuminat at pD950BDDF.dip.t-dialin.net] has quit IRC
+[Read 
+error: 104 (Connection reset by peer)]
+[15:37] < dolphy> we would need a specific src then
+[15:37] < ds-work> alternatively, I think mozilla can stream to a
+file, and then 
+give the filename to the plugin
+[15:37] -!- md` [illuminat at md.boerde.de] has quit IRC [No route to host]
+[15:38] < ds-work> of those options, you can pick one, and I'll work on 
+implementing it
+[15:39] < dolphy> i think having an src for that might be usefull
+[15:39] < dolphy> dunno if it's doable though
+[15:39] < dolphy> what would happen if download stalls
+[15:39] -!- LoRez  is an identified user
+[15:39] < ds-work> that means putting the src into a pipeline and
+running it, 
+independent of the play-on-startup gconf field
+[15:40] < ds-work> there are, of course, a lot more issues with 
+playing-while-downloading
+[15:40] < dolphy> downloading to a file might be very long for the user 
+experience
+[15:40] -!- docelic  is an identified user
+[15:40] < ds-work> i.e., seeking to an undownloaded segment should
+cause the 
+download to skip to that place
+[15:40] < dolphy> the media could be 20 MB 
+[15:41] < dolphy> yeah that would be nice :)
+[15:41] < ds-work> well, the download starts, the plugin gets the file 
+(unfinished), and the download continues in parallel
+[15:41] < ds-work> QT has a cool feature that shows what segments of
+the file 
+are downloaded
+[15:42] < dolphy> and does that work with gnomevfssrc ?
+[15:43] < ds-work> as a separate problem, some download media are live
+streams, 
+so you want to cache as little as possible.  pausing and playing 
+should skip portions of the stream
+[15:43] < ds-work> does what work?
+[15:43] < ds-work> playing-while-downloading?
+[15:43] < dolphy> yup
+[15:43] < ds-work> possibly not, but we can work on that
+[15:43] < dolphy> and seek to a downloadable portion
+[15:44] < ds-work> that's an easy bug :)
+[15:45] < dolphy> anyway we will need that play-while-download thing
+for the 
+video streaming server/client
+[15:45] -!- agony [~jay at AMontsouris-108-2-4-5.w193-252.abo.wanadoo.fr]
+has quit 
+IRC ["%| - Die !"]
+[15:46]  * ds-work should probably write the cache plugin
+