CCE 2.5 SP DVD frameserving with Avisynth

[scissors]

btw, if anyone is curios why i letterbox to 432 width - i noticed on all the 16:9 tvs i've seen when you do 16:9 zooms the edges dissappear off screen.

why encode what you won't see? Save on space.

Also, the crop measurement are for 2.35:1 ratio.

[LoneTango]

When I go through this whole process and after the Pulldown, my video file size exceeds the normal VCD size of <800MB. It's usually around 1.7GB and there is no way I can fit it on a CDR. Is there a process missing somewhere in the VCD conversion that shrinks the file size to VCD standard?

The process of using this method is extremely fast, but I'm stuck with the file size being twice the size of a normal VCD.

Please help.

[Shabubu]

[quote="scissors"]

I'm just curious as to why you wouldn't just use DVD2SVCD - it does almost exactly what you outline in your guide, but the entire process is automated once you choose your settings...

answer = entire film on one svcd cdr in less than 7 hours.

Firstly for avi_io caps why don't you just use the segmentedAVIsource command, it does what you said earlier without all the typing

Please try software before using sarcasm. I have been using AVISynth for going on 1.5 years (if not more), so I'd consider what I know what I'm on about, DVD2SVCD uses exactly this method, in fact it does it better as it uses BeSweet for the audio and vstrip for the ripping, both of which are significantly better than the methods used in this guide (besweet, azid downmix engine, ssrc and tooLame without intermediate files). Thus if this method takes you 7 hours, then DVD2SVCD will take seven hours. Also DVD2SVCD will rip and mux the subtitles, multiple audio streams and make the disk images using vcdimager (with chaptering ripped from the DVD). Also you can set up your bitrates to allow however many minutes you want per CD, from 1 to whatever.

Don't get me wrong, I love setting up avisynth scripts, I find nothing better than going thru all the little foibles (incidentally, load the script into virtualdub without the trim comment, then step thru to the frame you want to cut at, then put that number into the script, it allows frame by frame cutting and is easier to use). But DVD2SVCD is far more efficient than I am, automates what can be a relatively arduous process and is just damn sweet.

Please please please give it a go, then join there fan club.

[ASHY]

Seems like a lot of messing about frame serving with Avisynth to CCE.
Why not try this simpler method using TMPGenc.

Load up your AVI or D2v file into TMPG.
Set it up as if you were gonna encode then save as a project.

Convert the project file to avi with VFAPI convertor. ( I recommend converting the Video only and doing the audio separately with TMPG or another program and then multiplexing)

Load the AVI into CCE, set up the parameters in CCE and encode.

CCE will now use all the settings ands filters you set up in TMPG to encode your movie, but at a faster rate than TMPG.

ASHY

[Kdiddy]

ASHY:
Because the AVIsynth is a faster ENCODING process than what you just described. Due to mainly that VFAPI only works in RGB thus u have a lot of colorspace conversion going on that slows the encoding process. Using Avisynth is not that hard once you have a set pattern.

[scissors]

ASHY:
Because the AVIsynth is a faster ENCODING process than what you just described. Due to mainly that VFAPI only works in RGB thus u have a lot of colorspace conversion going on that slows the encoding process. Using Avisynth is not that hard once you have a set pattern.

okay, this is a new one on me. i thought it was just a wrapper for avisynth.

[Kdiddy]

Thought what was a "wrapper"..VFAPI?...no VFAPI is a tool that allows you to create a pseudo AVI file for programs that normally dont support most commonly the D2V files that DVD2AVI creates. AVIsynth is framserving tool like Vdub or Premiere.

[scissors]

ho hum.

with getting into some protracted arguement - then yes it's a wrapper

[Kdiddy]

what is AVIsynth or VFAPI??...VFAPI, yes...AVIsynth no..do you need VFAPI to wrap a file for AVIsynth, no.

[mediamonk]

to all who have crashes when frameserving from avisynth to CCE.

1.do your audio seperatly.CCE has many troubles with audio.

2.put "ResampleAudio(44100)"without the quotes at the bottom of your avs script,or use GKNOT to generate your avs.

CCE will crash no more.

[alienworkshop]

hi, i was wonderting how to do the pulldown part of the guide. i know it sounds stupid, but i just don't get it. i had copied it to the same directory and everything and everything else seemed go just fine. it's when it says open the command prompt i just don't get. i tried opening the pull.exe, but a dos screen just pops up for a second. any help would be appreciated. thanks!

[fantomlord]

pulldown is a command line based program.
either you need to go into a dos prompt and enter the command manually, or get the GUI.

[alienworkshop]

fantomlord, i think i'll give that a try. and thanks a lot for the help!

[alienworkshop]

hi, i was wondering why when i replay the video i made with cinema craft encoder i get this cinema craft logo on the bottom right of the finished video, and if someone could please tell me how to get rid of this thing, it would be much appreciated.

[fantomlord]

you're using a demo version
to get rid of the logo...
buy the program

[alienworkshop]

alright, thanks again.

[sammie]

Hey folks, Finally got AviSynth working with CCE. But when I did it seemed really slow. Did some time runs with Virtual Dub frame server then simply doing separate VDub processing then CCE encode. The AviSynth came out slowest by a lot on a 90 minute movie. Roughly 1.5 days Vdub to CCE, 2 days separate and almost 3 days AviSynth

The only guess I have is that I am transcoding some old VHS tapes and using a combo spatial/temporal cleaner. I know that slows things down with Vdub. With Vdub I am using fLaxen and with AviSynth I am using Convolution3D. Straight encodes CCE are obviously faster so I know it isn't that. Is it likely to be the cleaner slowing things down? I like the fLaxen results, would it be faster to use the LoadVirtuaDubPlugin and fLaxen even though I'd have to convert to RGB? Is there a better (same quality but faster) native AviSynth combo filter than Convolution3d?

[Truman]

AFAIK flaxen is an author of plugins, not a filter. Which plugin do you mean?
Well, it is hard to compare Vdub vs. Avisynth if you use different filters.
Generally you can use all external Vdub plugins with Avisynth. Tell me the exact filter name and a download link if necessary. Then I will try to write the Avisynth script if you like.

[sammie]

Yep, I know it's hard. Guessing that it is the filters causing the slowness. Was presuming that the native AviSynth filter might be faster. Plus, I didn't want to do the RGB conversion to use the VDub filter if I didn't have to.

I think it's called flaxenVHS. It's a combo temporal and spatial smoother (has sharpening and a couple of other things too, but I think other tools give better results there).

Presume the script is:
ConvertToRGB32
LoadVirtualDubPlugin("flaxenVHS.dll","myname",preroll)
Then:
myname(param, param,parm,etc.)

If you know the filter and have a guess at the preroll that would be a great help. Plus any syntax errors you see, all help would be appreciated !!!?!?!

[sammie]

The download link is: http://flaxen.dynip.com/vdf/fxvhs/

Looks like the name is fxvhs

[Truman]

I just had a look at the vdub_filters.avs and found this:

########################
# VHS Filter by flaXen #
########################

function VD_VHS(clip clip, bool "stabilize", int "luma_threshold", int "chroma_threshold",
  \  int "temporal_error", int "temporal_bias", int "noise_threshold",
  \  int "pixel_radius", bool "prefilter", bool "postfilter", bool "sharpen",
  \  int "sharpen_amount", bool "eight_direction", int "chroma_shift_x",
  \  int "chroma_shift_y", bool "shift_i", bool "shift_q")
{
  LoadVirtualdubPlugin(VirtualDub_plugin_directory+"\fxvhs.vdf", "_VD_VHS")
  return clip._VD_VHS(default(stabilize,true)?1:0, default(luma_threshold,5),
    \  default(chroma_threshold,30), default(temporal_error,15), default(temporal_bias,5),
    \  default(noise_threshold,10), default(pixel_radius,1), default(prefilter,false)?1:0,
    \  default(postfilter,false)?1:0, default(sharpen,false)?1:0, default(sharpen_amount,15),
    \  default(eight_direction,false)?1:0, default(chroma_shift_x,-1), default(chroma_shift_y,0),
    \  default(shift_i,false)?1:0, default(shift_q,false)?1:0)
}

Since you used this filter with Vdub, you probably know how to configure the filter.
Here is a screenshot of the filter configuration dialog, when you use it with Vdub:



"Translated" to Avisynth's language it is

Avisource()
import("vdub_filters_v16")
VD_VHS(true,5,30,15,5,10,1,false,false,false,15,false,-1,0,false,false)

Download vdub_filters.avs

I don't know anything about the preroll. Since this filter contains a temporal cleaner, it might be necessary to define the "preroll". But I have no clue how many frames to choose.

[sammie]

Thanks Truman. Was running something else last night, so I'll try it this weekend. Yes, I was guessing the samething on the preroll with the temporal smoother. I know the filter uses a lot of accumulation buffers (it's a real memory hog but fast), but I don't see anywhere exactly how many frames it compares. If anyone knows some typical numbers for temporal smoothers that might help. Other than that I'll just start guessing.

[alienworkshop]

hey, can someone tell me why people say my svcd's that i make have lines in people and seem to cut them up when they move? i don't seem to notice this on my computer, but i've had two different people tell me that and i was wondering if i could get rid of this annoying thing. thanks!

[alienworkshop]

ok, i seem to know how to fix the lines in my video, i had to not select progressive frames because the video wasn't 23.97, it was already 29.97. but another problem i had is that i notice that during really fast motion for this format, it seems to get real blocky. i noticed that tmpeg's regular vcd look better during these motion scenes. and i was wondering if there was a way to decrease the blockiness. also, i did not seem to have this problem when i ripped another dvd which was film (23.97), i don't know if that makes a difference, but it seem to come out just perfect, so i'm really stuck on this one. any tips or help is greatly appreciated, thanks! :P

[Bizuser]

This may be considered a 'nit', or maybe I'm missing a simple point here, but I have what I think is a correction to the original guide ...

The guide says:

Te next command is bicubicresize. This will resize your video to what ever you choose, the first number is the vertical resolution and the second being the horizontal.

Now, the syntax for BicubicResize (from avisynth doc) is this:

BicubicResize(clip, int target_width, int target_height, float "b", float "c")

Note, target_width, then target_height.

I always have to think three times about which number is which, especially since working with SVCD (which is 480x480!) you don't have to think too hard.

Anyway, I'd say the guide should say " the first number is the horizontal resolution and the second being the vertical".

[troyvcd1]

I wish that you could be a little more descriptive for me: What does

Download Avisynth and copy the avisynth.dll to your system32 folder and run the install.reg from the unzipped package.

mean?>???

[Bizuser]

I didn't write the guide but I'll try to answer your question ...

Download Avisynth and copy the avisynth.dll to your system32 folder and run the install.reg from the unzipped package.

Download Avisynth - goto www.doom9.org, download page, goto section for 'support utils', find avisynth, download it.

Unzip it - double-click the zipped file you downloaded and extract the contents to a logically named directory on your hard drive (eg, c:\avisynth).

Copy avisynth.dll to your system32 folder - find the file 'avisyth.dll' in the directory you just created, copy it to (eg) c:\windows\system32. Could be c:\winnt\system32 - only you can say - depends on your OS and how you set things up.

Run 'install.reg' - go to the directory you extracted stuff to, then double-click on the file 'install.reg', and say yes to merging into registry.

Since you aren't comfortable with the terminology used in the original post, sounds like you haven't done stuff like this before, in which case, be careful! This stuff is not for the faint of heart!