Difference between revisions of "General advice"
From SDA Knowledge Base
Ballofsnow (Talk | contribs) (avs in mpc) |
Ballofsnow (Talk | contribs) |
||
| Line 3: | Line 3: | ||
This page is for advice / tips / tricks related to everything in the knowledge base. | This page is for advice / tips / tricks related to everything in the knowledge base. | ||
| + | <br> | ||
===Expected final results for self-encoded runs=== | ===Expected final results for self-encoded runs=== | ||
| + | <br> | ||
===Media players=== | ===Media players=== | ||
| − | === | + | <br> |
| + | ===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. | ||
| + | |||
| + | <br> | ||
===d2v file path=== | ===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 file 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. | ||
| + | |||
| + | <br> | ||
===Always keep source files backed up=== | ===Always keep source files backed up=== | ||
| + | <br> | ||
===Preview avs scripts in Media Player Classic=== | ===Preview avs scripts in Media Player Classic=== | ||
When creating your avisynth script, it is possible to preview your work by playing the avs file directly in [http://www.videohelp.com/tools?tool=Media_Player_Classic 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. | When creating your avisynth script, it is possible to preview your work by playing the avs file directly in [http://www.videohelp.com/tools?tool=Media_Player_Classic 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. | ||
| − | ===Never convert to YV12 | + | <br> |
| + | ===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. | ||
| + | |||
| + | <pre><nowiki> | ||
| + | color1=Blankclip(pixel_type="yuy2",color=$800000).assumefieldbased() | ||
| + | color2=Blankclip(pixel_type="yuy2",color=$80FFFF).assumefieldbased() | ||
| + | interleave(color1,color2).weave | ||
| + | </nowiki></pre> | ||
| + | |||
| + | <pre><nowiki> | ||
| + | color1=Blankclip(pixel_type="yuy2",color=$800000).assumefieldbased() | ||
| + | color2=Blankclip(pixel_type="yuy2",color=$80FFFF).assumefieldbased() | ||
| + | interleave(color1,color2).weave | ||
| + | ConvertToYv12() | ||
| + | </nowiki></pre> | ||
| + | Wouldn't want to deinterlace that... | ||
| + | |||
| + | <br> | ||
Revision as of 21:37, 4 November 2006
Contents
Introduction
This page is for advice / tips / tricks related to everything in the knowledge base.
Expected final results for self-encoded runs
Media players
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 file 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.
Always keep source files backed up
Preview avs 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.
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...
