comparison DOCS/xml/en/faq.xml @ 15981:c20bd4b50521

Remove rencently added FAQ entry because we now have a much better and detailed doc elsewhere.
author gpoirier
date Sat, 16 Jul 2005 18:04:31 +0000
parents 3eaceddfd30c
children 3bed758b6eae
comparison
equal deleted inserted replaced
15980:85fd2ee1c094 15981:c20bd4b50521
860 Newer versions of <application>MEncoder</application> can directly 860 Newer versions of <application>MEncoder</application> can directly
861 generate MPEG-2 files that can be used as a base to create a VCD or SVCD and 861 generate MPEG-2 files that can be used as a base to create a VCD or SVCD and
862 are likely to be playable out of the box on all platforms (for example, 862 are likely to be playable out of the box on all platforms (for example,
863 to share a video from a digital camcorder with your computer-illiterate 863 to share a video from a digital camcorder with your computer-illiterate
864 friends). 864 friends).
865 <screen> 865 Please read
866 mencoder -of mpeg -oac toolame -toolameopts br=224 -srate 44100 \ 866 <link linkend="menc-feat-vcd-dvd">Using MEncoder to create VCD/SVCD/DVD-compliant files</link>
867 -af-adv force=1 -ovc lavc -mpegopts format=xsvcd -vf harddup -ofps 25 \ 867 for more details.
868 -lavcopts vcodec=mpeg2video:mbd=2:keyint=25:vrc_buf_size=917:vrc_minrate=600:vbitrate=2500:vrc_maxrate=2500 \
869 <replaceable>in.avi</replaceable> -o <replaceable>xsvcd.mpg</replaceable>
870 </screen>
871 This will convert the input file <replaceable>in.avi</replaceable> into
872 the output file <replaceable>xsvcd.mpg</replaceable>, converting the
873 audio with <systemitem class="library">toolame</systemitem> at 224kbps
874 and the video with <systemitem class="library">libavcodec</systemitem>
875 at 2500kbps, making sure the bitrate never goes below 600 and never
876 exceeds 2500kbps, in order to respect the (S)VCD norm and ensure an
877 smooth playback.
878 </para><para>
879 Please note that in order to make the GOP structure SVCD compliant the
880 <option>keyint</option> option should be 15 for PAL and 18 for NTSC,
881 although very often files with much longer GOPs play correctly (25 should
882 never lead to any problem).
883 Also, even though leaving out <option>-ofps</option> should work in most
884 cases (as your source is likely to have the appropriate framerate
885 already), PAL requires <option>-ofps</option> 25 and NTSC requires
886 <option>-ofps</option> 30000/1001.
887 What's more, PAL SVCDs only support 480x576 and 352x288 resolutions,
888 whereas NTSC only supports 480x480 and 352x240.
889 If the source video has a different resolution, then you must rescale
890 with the <option>scale</option> video filter, which will make your filter
891 chain look like for example <option>-vf scale=480:480,harddup</option> for
892 an NTSC SVCD or <option>-vf scale=352:288,harddup</option> for a PAL SVCD.
893 </para><para>
894 As far as the audio is concerned, SVCD only supports MPEG-1 layer II audio,
895 therefore you have to use one of
896 <systemitem class="library">toolame</systemitem>,
897 <systemitem class="library">twolame</systemitem>, or as a last resort
898 <systemitem class="library">libavcodec</systemitem>'s MPEG-1 layer II
899 encoder (as its quality is far from being as good as the former two
900 libraries).
901 Both <systemitem class="library">toolame</systemitem> and
902 <systemitem class="library">twolame</systemitem> follow the same syntax,
903 so you depending on which one you managed to install, the example only
904 requires a small change. If you do need to use
905 <systemitem class="library">libavcodec</systemitem>'s MPEG-1 layer II
906 encoder, replace
907 <screen>
908 -oac toolame -toolameopts br=224
909 </screen>
910 if you use toolame or
911 <screen>
912 -oac twolame -twolameopts br=224
913 </screen>
914 if you use twolame by:
915 <screen>
916 -oac lavc -lavcopts acodec=mp2:abitrate=224
917 </screen>
918 </para><para>
919 The resulting <replaceable>xsvcd.mpg</replaceable> is an extended
920 SVCD (that is why it is called xsvcd), mainly because it does not contain
921 scan offsets. If you need to generate an SVCD image out of it, you
922 should pass it to
923 <ulink url="http://www.gnu.org/software/vcdimager/vcdimager.html">vcdimager</ulink>.
924 </para></answer> 868 </para></answer>
925 </qandaentry> 869 </qandaentry>
926 870
927 <qandaentry> 871 <qandaentry>
928 <question><para> 872 <question><para>