What do I with these .vob files?

[Osakaisthebomb]

OKAY

I will probably have a lot more question based on the last few post in this thread but I got one more important that those.

At 3:30 today I started virtualdub with the avi file and started saving it as an avi. 3 and a half hours later is said it was only 18% done. WHY? I mean this is only a about a hour and 29 minute video I'm using (animatrix) so i should take longer then that right? What am I doing wrong.

[Osakaisthebomb]

please excuses the horrible typos in that post.

[Kariudo]

What am I doing wrong.

You're transcoding the entire movie, that's what's wrong.

Ok, but seriously now, the slow encoding speed is most likely a result of your avisynth script.
Some filters (I'm looking at you~ vmtoon) slow the process down to a snail's pace (~4fps, this of course depends on how good your computer is)

Related to my semi-sarcastic first remark, you'll be better off just encoding the clips that you want to use rather than the entire movie (it will save space as well, since a 1.5 hour huffyuv will probably end up at around 12-15 GB)

open the video file in virtualdub mod go to video->compression->Huffyuv
then go to file->save

Ways of saving file space

use those buttons to mark the beginning and the end of the "clips" you want to use so you can save file space.

also go to streams->streams list->disable stream to disable the audio and save even more file space.

[Qyot27]

Semi-related to clip-making, it is wise to have two scripts at the ready: an LQ script, and an HQ script. The LQ script would omit things that were meant to make everything look nice, diminish noise, or slow down the script unnecessarily, and would do well to be at a lower resolution (I do mine at 320x240 or 432x240, but that's because my computer is almost a relic; feel free to use a higher res if your comp can handle it smoothly) - you can use this script to encode the full movie with MJPEG, preferably through ffdshow's VFW since that's free and produces acceptable quality.

You want to make sure the script keeps any functions that affect frame ordering or the total number of frames, but you could excise the options that are meant for higher precision. In essence, the LQ script will do a dumb inverse telecine rather than a super-tweaked one; most differences are usually not more than 1 or 2 frames and can be corrected when you open up the HQ script.

You then take this LQ MJPEG encode and track through it with VDub (you can use Alt+Arrow keys to move 50 frames at a time), making a note of your clips' starting and ending frame numbers in Notepad.

Next, you would open up your HQ script, and then use your notes to hop to the right frames of the video (easiest way to bring this up is Ctrl+G). If the frames are not quite the right ones, you can adjust the start and end frames accordingly.

[Osakaisthebomb]

Um....first I would have to now what the heck a LQ script and a HQ script was, or how to get those, to understand any of what you are talking about, Qyot27

[Kariudo]

It's pretty much all in Qyot's post (just read it over a few times)

The LQ script would omit things that were meant to make everything look nice, diminish noise, or slow down the script unnecessarily, and would do well to be at a lower resolution (I do mine at 320x240 or 432x240)...

the LQ script is just Telecide() and Decimate() (with whatever parameters you've specified for both filters) and maybe a lanczosresize().

if this was my HQ script...

Code: Select all

mpeg2Source("C:\Documents and Settings\Use\Desktop\New Folder\disk1.d2v")
TFM(order=-1,mode=5,PP=7,field=-1,slow=2)
tdecimate(mode=1)
RemoveGrain()
LimitedSharpen()
Deen("a3d", 1)
ConvertToYUY2()
FixBrokenChromaUpsampling()

the LQ script would be...

Code: Select all

mpeg2Source("C:\Documents and Settings\Use\Desktop\New Folder\disk1.d2v")
TFM(order=-1,mode=5,field=-1)
tdecimate(mode=1)

The LQ script is meant for getting decent encoding/seeking speed, no bells or whistles to make your source look really shiny. You can encode the entire movie using MJPEG (it encodes/decodes pretty fast)

You then take this LQ MJPEG encode and track through it with VDub (you can use Alt+Arrow keys to move 50 frames at a time), making a note of your clips' starting and ending frame numbers in Notepad.

self-explanatory, vdub/mod tells you the frame number of the frame you're currently on

Next, you would open up your HQ script, and then use your notes to hop to the right frames of the video (easiest way to bring this up is Ctrl+G). If the frames are not quite the right ones, you can adjust the start and end frames accordingly.

The HQ script would be whatever you were using that was taking forever to run.
You plug in the start and end frames of each clip, encode it, and then move onto the next clip (repeat ad nauseum until finished)

[Qyot27]

Yep, that's what I meant. Although I actually use BilinearResize for LQ scripts or quick-and-dirty downscaling. It doesn't have to look good or be particularly sharp, it just has to be fast and easy to encode or seek through.

[Osakaisthebomb]

GOD!!! All I want is to have good quality not spend days of hundreds of theories which always have some issue on my computer. FORGET IT!

[LittleAtari]

GOD!!! All I want is to have good quality not spend days of hundreds of theories which always have some issue on my computer. FORGET IT!

I'll make this easy on you.

Use Vfapi in the AMVapp 3.0 beta. Toss in your avisynth script and it will make you a fake avi in seconds. Just take out things that make the script go slow like VMToon (deen is okay to keep in) and you should be fine.

Some people dont want an explanation of the many different ways to do something. I know it's great to know all this information guys, but make things simple on the new guy,

[LittleAtari]

Also, I'd like to mention that you need to keep the d2v and vob files in order for the fake avi to work inside your editing program. Make sure to put them in a folder you're comfortable with. Note: Moving the d2v and vob files may require you to remake the d2v file.