<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=gb2312"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=ZH-CN link=blue vlink=purple> <div class=WordSection1> However, I think it in another way, the way like most bittorrent tools does.<o:p></o:p> At the start of progressive downloaded, a dummy file is created on disk;<o:p></o:p> When there is seek operation requested from parser, souphttpsrc will write bunk of data to file with offset as well.<o:p></o:p> Then I will get the entire file after finish playback.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Marco Ballesio [mailto:gibrovacco@gmail.com] Sent: Monday, September 20, 2010 1:54 PM To: Discussion of the development of GStreamer Subject: Re: [gst-devel] some issues when trying to save content to disk during http progressive downloaded<o:p></o:p> </div> <o:p> </o:p> Hi,<o:p></o:p> <div> 2010/9/20 Zhao, Halley <<a href="mailto:halley.zhao@intel.com">halley.zhao@intel.com</a>><o:p></o:p> <div> <div> Your suggestion may be helpful, <o:p></o:p> But I expect a solution needn’t care about demux/mux, because all these data are passed through souphttpsrc, save the data from souphttpsrc shouldn’t care about mux/demux.<o:p></o:p> </div> </div> <div> As you wrote: "it seek to the end of the mp4 file at the beginning of playback." the seek operation is performed from the demuxer (qtdemux), which identifies essential meta-data present at the end of the file. This data will not be transferred again at the end of the playback, so *in this case* you can't consider souphttpsrc as just a mere data pipe through which you get the complete clip. Said so, you have many ways to address this: - You can (try and) use the "moov-recovery-file" transmuxing the file after having saved it. It will restore the missing meta-info. - You can re-mux on-the-file the file while you're getting it from souphttpsrc. Again, it will rebuild the lost meta-infos. - You can use only progressive-download compliant files: they will have all the meta-information stored at the beginning and no seek will be needed. Regards  <o:p></o:p> </div> <blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt; margin-left:4.8pt;margin-right:0cm'> <div> <div>  <o:p></o:p>  <o:p></o:p> <div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm; border-color:-moz-use-text-color -moz-use-text-color'> From: Marco Ballesio [mailto:<a href="mailto:gibrovacco@gmail.com" target="_blank">gibrovacco@gmail.com</a>] Sent: Sunday, September 19, 2010 12:53 AM<o:p></o:p> <div> To: Discussion of the development of GStreamer<o:p></o:p> </div> <div> <div> Subject: Re: [gst-devel] some issues when trying to save content to disk during http progressive downloaded<o:p></o:p> </div> </div> </div> <div> <div>  <o:p></o:p> Hi,<o:p></o:p> <div> 2010/9/13 Zhao, Halley <<a href="mailto:halley.zhao@intel.com" target="_blank">halley.zhao@intel.com</a>><o:p></o:p> Thanks Stefan. After add a 'queue' after 'souphttpsrc' and use 'decodebin2'; I still got same result. I think the possible solution is to enhance souphttpsrc to save content to disk after some refractor, because souphttpsrc does some seek following the command of parser. Attached mp4.log is the log of souphttpsrc, it seek to the end of the mp4 file at the beginning of playback. Finally, tail of the original mp4 file is missing in downloaded mp4 file.<o:p></o:p> <div> It looks like you're not re-muxing the content. Are you simply storing the raw mp4 data to a file or are you using a muxer before the filesink? What does mp4info tell about your output file? You may try and recover the saved files with mp4mux using the option "moov-recovery-file". What happens if you transmux the files using it? Regards  <o:p></o:p> </div> <blockquote style='border:none;border-left:solid windowtext 1.0pt;padding:0cm 0cm 0cm 6.0pt; margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt; border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204)'> halley@halley-lucid:~/swap/streaming/mp4$ ls -l total 5216 -rwxr--r-- 1 halley halley 1776915 2010-09-08 23:08 download.mp4 -rw-r--r-- 1 halley halley 1773281 2010-09-08 18:15 original.mp4<o:p></o:p> <div> -----Original Message----- From: Stefan Kost [mailto:<a href="mailto:ensonic@hora-obscura.de" target="_blank">ensonic@hora-obscura.de</a>] Sent: 2010年9月11日 1:27 To: Discussion of the development of GStreamer<o:p></o:p> </div> <div> Cc: Zhao, Halley Subject: Re: [gst-devel] some issues when trying to save content to disk during http progressive downloaded<o:p></o:p> </div> <div> <div> Am 08.09.2010 04:45, schrieb Zhao, Halley: > During playback of progressive content, I tried to save the content to disk as well. > > But the result is strange: > > Some contents are saved correctly, some contents are saved but can’t playback > again; some contents even can’t playback during progressive downloaded. > > > > ## most ogg contents work well, the saved contents can playback again > > gst-launch-0.10 souphttpsrc > location=<a href="http://10.238.37.11/share/media/video/test.ogv" target="_blank">http://10.238.37.11/share/media/video/test.ogv</a> ! tee name=t ! decodebin > ! ffmpegcolorspace ! xvimagesink t. ! queue ! filesink location=test.ogv > > > > ## some mp4 saved contents can’t playback again, the saved contents differ from > the original one; even the following test.mp4 and test2.mp4 are different > > gst-launch-0.10 souphttpsrc location=http:// > <a href="http://10.238.37.11/share/media/video/test.mp4" target="_blank">10.238.37.11/share/media/video/test.mp4</a> ! tee name=t ! decodebin ! > ffmpegcolorspace ! xvimagesink t. ! queue ! filesink location=test.mp4 > > gst-launch-0.10 souphttpsrc location=http:// > <a href="http://10.238.37.11/share/media/video/test.mp4" target="_blank">10.238.37.11/share/media/video/test.mp4</a> ! filesink > location=/home/halley/swap/streaming/test2.mp4 > At first use decodebin2! If the http source is seekable, the muxer in decodebin will do pull. You could try: gst-launch-0.10 souphttpsrc location=<a href="http://10.238.37.11/share/media/video/test.mp4" target="_blank">http://10.238.37.11/share/media/video/test.mp4</a> ! queue ! tee name=t ! decodebin2 ! ffmpegcolorspace ! xvimagesink t. ! queue ! filesink location=test.mp4 Stefan > > > ## some wmv contents even can’t playback during progressive downloaded (though > some saved wmv contents can playback again) > > gst-launch-0.10 -v -v souphttpsrc location=http:// > <a href="http://10.238.37.11/share/media/test.wmv" target="_blank">10.238.37.11/share/media/test.wmv</a> ! tee name=t ! queue ! decodebin ! > ffmpegcolorspace ! xvimagesink t. ! queue ! filesink location=test.wmv > > > > thanks in advance for your help. > > > > > > *ZHAO, Halley (Aihua)* > > Email: <a href="mailto:halley.zhao@intel.com" target="_blank">halley.zhao@intel.com</a> <blocked::mailto:<a href="mailto:aihua.zhao@intel.com" target="_blank">aihua.zhao@intel.com</a>> > > Tel: +86(21)61166476   iNet: 8821-6476 > > SSG/OTC/Moblin 3W038 Pole: F4 > > > > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > <a href="http://p.sf.net/sfu/intel-thread-sfd" target="_blank">http://p.sf.net/sfu/intel-thread-sfd</a> > > > > _______________________________________________ > gstreamer-devel mailing list > <a href="mailto:gstreamer-devel@lists.sourceforge.net" target="_blank">gstreamer-devel@lists.sourceforge.net</a> > <a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a><o:p></o:p> </div> </div> ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing <a href="http://p.sf.net/sfu/novell-sfdev2dev" target="_blank">http://p.sf.net/sfu/novell-sfdev2dev</a> _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.sourceforge.net" target="_blank">gstreamer-devel@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a><o:p></o:p> </blockquote> </div>  <o:p></o:p> </div> </div> </div> </div> ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. <a href="http://p.sf.net/sfu/novell-sfdev2dev" target="_blank">http://p.sf.net/sfu/novell-sfdev2dev</a> _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.sourceforge.net">gstreamer-devel@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a><o:p></o:p> </blockquote> </div> <o:p> </o:p> </div> </body> </html>