Difference between revisions of "General advice"
From SDA Knowledge Base
Ballofsnow (Talk | contribs) (Save time with uncle Bob.) |
Ballofsnow (Talk | contribs) (Vdub in low priority mode, will fill out later.) |
||
| Line 8: | Line 8: | ||
<br> | <br> | ||
===Media players=== | ===Media players=== | ||
| + | |||
| + | <br> | ||
| + | ===Running VirtualDub(Mod) in low priority mode=== | ||
<br> | <br> | ||
Revision as of 09:16, 6 November 2006
Contents
- 1 Introduction
- 1.1 Expected final results for self-encoded runs
- 1.2 Media players
- 1.3 Running VirtualDub(Mod) in low priority mode
- 1.4 Finding frame numbers for the Trim command
- 1.5 d2v file path
- 1.6 Keep your source files
- 1.7 Never convert to YV12 colorspace before deinterlacing
- 1.8 Preview avisynth scripts in Media Player Classic
- 1.9 Save time with MvBob
Introduction
This page is for advice / tips / tricks related to everything in the knowledge base.
Expected final results for self-encoded runs
Media players
Running VirtualDub(Mod) in low priority mode
Finding frame numbers for the Trim command
VirtualDub(Mod) beats Avisynth in this aspect. To find the range of frames for your cut, open your avs file in VirtualDub(Mod) and look at the frame numbers at the bottom of the screen. Plug those into the Trim() command.
d2v file path
If you're working with DVD source material and have created your DGIndex project file (the d2v), you may get problems if you move your source files around. This is because the d2v file is using an absolute file path. There are two ways to solve this problem.
1. Open DGIndex, go to the Options menu and deselect Use Full Paths. Future d2v files will use relative paths.
2. Open the d2v file in Notepad or any text editor. The third line should have the path to the source file, change it to your liking.
Keep your source files
This rule should be followed especially by people new to encoding. Chances are you will mess up, not following SDA's strict standards and be asked to redo your encodes. Try as hard as possible to backup your source files somewhere, even if you've encoded your run properly and it's already up on SDA. Burning your data to DVD discs is a good idea. Use lossless compression if needed. At the very least, encode your run with a very high bitrate in Xvid/H.264, but beware that these codecs use the YV12 colorspace and could mess up your interlaced source material. The next section explains why.
Never convert to YV12 colorspace before deinterlacing
Compare the following two avisynth scripts in VirtualDub(Mod) to see why. No actual deinterlacing is done, but you can see how the color is messed up in the second script.
color1=Blankclip(pixel_type="yuy2",color=$800000).assumefieldbased() color2=Blankclip(pixel_type="yuy2",color=$80FFFF).assumefieldbased() interleave(color1,color2).weave
color1=Blankclip(pixel_type="yuy2",color=$800000).assumefieldbased() color2=Blankclip(pixel_type="yuy2",color=$80FFFF).assumefieldbased() interleave(color1,color2).weave ConvertToYv12()
Wouldn't want to deinterlace that...
Preview avisynth scripts in Media Player Classic
When creating your avisynth script, it is possible to preview your work by playing the avs file directly in Media Player Classic, instead of encoding it first and then playing it. Of course, whether or not you can play it live without lag depends on how fast your computer is. Don't expect smooth playback if you're deinterlacing your video with mvbob. Though for the purpose of previewing you can try replacing mvbob with the faster leakkernelbob.
Save time with MvBob
MvBob is a very slow deinterlacer. When encoding the HQ and IQ versions, you typically do two-pass encodes for each. This means you'll be mvbob'ing your video four times! It only needs to be done once! You can save time by encoding a new mvbob'ed source file to lossless format (HuffYuV, Lagarith) and loading that into a new script.
