They load into Vegas wonderfully. Everything works super fast, scrubbing, cutting, moving. The only place I seem to have problems is with normal, simple transitions. Though I’m going to assume anything more complicated will only make the lag time worse.
My preview window is set to “Preview (auto)” though I’ve tried all the settings and haven’t noticed a noticeable change.
I’ve looked at several threads that suggest the Dynamic RAM preview as a solution and that’s been a bust as well. It either lags even worse then regular viewing or depending on how many times I’ve tried it, will speed through the first section only to come to a complete stop on the second section of the transition for a few seconds before starting again.
I’ve gone into the options and tried to up the Dynamic RAM preview max. I’ve gone up as high as it will let me and it’s still giving me fits.
My system is:
Windows XP Pro
Pentium ® 4 CPU 3.40 GHz
3.40 GHZ, 2.00 GB of RAM
Using USB2 to get from External Seagate 750 GB Hard Drive
My code is:
Code: Select all
MPEG2Source("J:\Video Projects\Animal I Have Become\AIHB.d2v", cpu=6)
Crop(8,0,-8,-0)
LanczosResize(640,480)
ConvertToRGB32()I’ve also tried turning off my anti-virus. No change.
I’ve read here that using actual lossless codecs like Huffy and Lagarith have less lag time than the vfapi/Avisynth way. Unfortunately I want to have access to all my DVDs at once rather than make buttloads of huge file size but tiny content clips. Because I can load as many vob(s) into DGIndex as I want, my goal was to have one avs script and therefore one vfapi file per video project.
If I have to switch to Huffy or Lagarith that sourcing/clipping method won’t work.
I’ve also tried the “bait and switch” technique and it works, but I’m really hesitant to use it. For one thing, since I’m using fake avi(s), the “low quality” clip is huge in comparison to my “high quality” vfapi fakes. There is just something seriously wrong with that! *lol*
Also, it took me a long time to get the vfapi/Avisynth system to work and for me to understand it, so I’d really like to use it. However, if it came down to it I’d prefer the B&S style to using Huffy or Lagarith. It works better with my clipping/sourcing style. However my concern with that is one 43 minute clip came out to 2.3 GB in size. If I start combining several episodes and/or seasons into one avs script, as I intended, these mjpegs are going to be off the charts! Which I imagine will present their own problems. I'd have to adjust, much like the note on the guide suggests of splitting up and using a few avs scripts instead of one.
One of my main reasons for using the avs/vfapi method was to keep the amount of rendering and extra huge files down. I intended to keep the vobs as the largest and only video content filled files. With B&S and/or Huffy and Lagarith this isn’t possible.
Another interesting tid-bit. When I used the PIC Mjepg 3 Codec it worked wonderfully with transitions. However, again the Dynamic Ram preview was wacky. It zoomed through the first part of the selected section and, as if the cursor needed time to catch up to the too speedy player, the player sat in a frame (the last of the selected section) until the cursor moved to it. Again, I adjusted the amount in the options to little effect.
What I’m hoping is that I just have something set wrong. Something that’s telling the Dynamic RAM preview to not work correctly. It seems to work for so many people and I have no clue why it’s not working for me. I have the RAM, I turned off everything I could think of. I’m at a loss. I would love to keep using the avs/vfapi method…as it took me forever to figure it out!
Any help would be appreciated!
