Thanks for the answer Derk.<br>
Does this really apply for all kind of codecs? I thougth that this only
applies to certain kinds like AVI, and that MPEG1 for example can also
be played without a correct header. And what is than the difference to
streaming a transcoded file over HTTP, there VLC also can not go back
to the header and correct it, because the information is streamed
permanently.<br>
What makes me wonder is, that of a ~3MB large file only some 1-2 KB
seem to be different between output to STDOUT and output to a file. And
the difference is in the Header AND the Footer (last few KBs), thats
why i think some other stuff is messing it up, maybe some line-breaks
sent or something like that.<br>
Best Regards<br>
<br><div><span class="gmail_quote">On 11/16/05, <b class="gmail_sendername">Derk-Jan Hartman</b> <<a href="mailto:hartman@videolan.org">hartman@videolan.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If you used --quiet you should be fine regardless.<br>I think it's more that stdout is a stream instead of a file, so VLC<br>cannot go back in the file and update the headers with the correct<br>information and stuff.<br>
<br>DJ<br><br>On 16-nov-2005, at 11:07, Polyphem wrote:<br><br>> Hello VLC-Community,<br>><br>> I'm currently playing around with the binary Stdout option an run<br>> into a problem.<br>><br>> When I use
<br>> standard{access=file,mux=asf,url='test.mpeg'}<br>><br>> the resulting local file is healthy and plays in VLC and WMP. When<br>> I try to capture the binary output from Stdout with<br>><br>> standard{access=file,mux=asf,url=-}
<br>><br>> and than create the movie with an external program, it is<br>> corrupted. I took hex look at the binaries and it seems that 99.9%<br>> are identical. Only in the top 2-3 header rows and the bottom 2-3
<br>> footer rows the Stdout file looks sligtly different.<br>> I looked up the Stdout function here:<br>> <a href="https://trac.videolan.org/vlc/file/trunk/modules/access_output/file.c">https://trac.videolan.org/vlc/file/trunk/modules/access_output/file.c
</a><br>><br>> Is it possible that these:<br>><br>> msg_Dbg( p_access, "using stdout" );<br>> msg_Dbg( p_access, "file access output opened (`%s')", p_access-<br>> >psz_name );<br>
> msg_Dbg( p_access, "file access output closed" );<br>><br>> come in my way? Are they also parsed to the Stdout and I have to<br>> deactivate them somehow, or do those Messages need to be invoked by
<br>> a special debug option (which I did not found until now)?<br>><br>> Anyone had this problem before? Is it possible that VLC mixes other<br>> Stdout output into the stream? Invoked it with -q, --quiet, but are
<br>> there other parameters to tell VLC not to write other output to<br>> Stdout?<br>><br>> Thanks and Best Regards<br>><br>><br>><br><br>--<br>This is the streaming mailing-list, see <a href="http://www.videolan.org/streaming/">
http://www.videolan.org/streaming/</a><br>To unsubscribe, please read <a href="http://www.videolan.org/support/lists.html">http://www.videolan.org/support/lists.html</a><br><br></blockquote></div><br>