Differences

This shows you the differences between two versions of the page.

@@ Line 1: / Line 1: @@
+====== transcode ======
+=== archives: transcode notes ===
+howto - http://www.bunkus.org/dvdripping4linux/single/
+<code>transcode -i /space/tng-biggoodbye/vob/004 -w 4357,250,100 -a 1 -b 128,0,0 -s 3.311 -V -f 25 -B 12,10,8 -R 1 -x vob,null -o /dev/null -y xvid,null</code>
+<code>transcode -i /space/tng-biggoodbye/vob/004 -w 4357,250,100 -a 1 -b 128,0,0 -s 3.311 -V -f 25 -B 12,10,8 -R 2 -x vob -o /space/tng-biggoodbye/avi/004/tng-biggoodbye-004.avi -y xvid</code>
+dvd::rip transcoding
+(pass 1)
+<code>transcode -a 0 -x vob -i MOVIE.VOB -w 6000,50 -F mpeg4 -A -N 0x2000 -f 24,1 -M 2 -Y 4,4,4,4 -B 1,11,8 -R 1 -y ffmpeg,null -o /dev/null</code>
+(pass 2)
+<code>transcode -a 0 -x vob -i MOVIE.VOB -w 6000,50 -F mpeg4 -A -N 0x2000 -f 24,1 -M 2 -Y 4,4,4,4 -B 1,11,8 -R 2 -y ffmpeg -o movie.avi</code>
+framerate.txt example for variable frame rate (updated)
+<code>transcode -i foo.vob -x vob,vob -f 0,4 -M2 -R3 -w2 --export_fps 0,1 -J ivtc -J decimate -B 3,9,16 --hard_fps --print_status 10 -J 32detect=verbose=1:force_mode=5:chromathres=2:chromadi=9 -y xvid4 -o bar.avi</code>
+*** Ripping TV Shows ***
+These are my notes from all the testing with bend on TV shows.
+Some generic conclusions:
+- Do a two-pass and force deinterlacing on a live-action show for best
+results if the show is not variable framerate.
+- Do a one-pass with hard_fps dropping on cartoons
+- If it's a variable framerate, do a one pass and force the input and
+output framerate.
+Everything else documented revolves around those three basics.
+* 2pass notes
+The two passes on cartoons seems to blur the lines in every case.  It
+could be because I'm not doing --hard_fps at all, but adding that
+usually throws the A/V out of sync.
+Without deinterlacing on a 2pass, you will see some horizontal lines as
+artifacts on *some* shows, not all.  It seems to be the minority,
+actually, as most do fine with just 2 passes.
+For deinterlacing (on 2 pass), -I 1 and -I 3 seem to work fine.  -I 3
+has consistenly delivered great results, and limited testing proves that
+-I 1 works fine.  The only problem with -I 3 is it doubles the encoding
+time, so a one-hour show will take up to 4 hours to encode on two
+passes.
+* 1pass notes
+If you are forcing the framerate, go ahead and use all the filters
+mentioned in framerate.txt.
+If not, just use 32detect.  Adding anything else throws the a/v out of
+sync.
+You can use --hard_fps on both, though.
+Generally speaking, 1pass usually will result in larger filesize.  The
+difference between one and 2 pass for filesize can be dramatic (I've
+seen from 20 megs to 200), but not consistently rational.  If a one-pass
+is working and looking really nice, go for it.  You'll probably end up
+with larger files, but save time and get good quality.
+Overall, I'd say use the one-pass method if you can afford to be very
+liberal with harddrive space.  There are some cases where using it
+actually causes jitter, so the two-pass is better because it cleans that
+up.
+# Building CVS
+Checkout the CVS
+<code>autoreconf -f -i</code>

Trace:

Differences

Navigation

Search

Toolbox