How does Movie Stacker compare to DIKO?
 

Are MovieStacker and DIKO basically competing products that do similar things? Or is it more like VirModDub?

Are they suited for different types of situations?

Thanks,
-S

Moviestacker is only a tool to compute resizing/crop parameters + a facility to help writing avisynth scripts faster than by typing it by hand.

It has NOTHING to do with Diko nor Vdub.

The link to download moviestacker is broken. Anyone know where else to download? I've googled around and don't see it anywhere (except in languages I can't read!)

Unfortunally, there is no dl place currently. But you can use FitCD if you need something to compute resize settings.

Actually it was the WYSIWYG aspect of applying AVISynch filters to my video file that captured my attention.

I find the array of filters and their respective parameters to be overwhelming.

I've just finished burning a DVD with DIKO using your DialhotV4 script and the faces on the people come out pixxelated. I do use VirDir to preview my videos with the scripts loaded but its time consuming and cumbersome. There must be an easier way.

Re: How does Movie Stacker compare to DIKO?
 

excuse me for simple observation:

YES, are competing cos they together encrease the quality of the forum and of our results!
WE all have proud of that programs and you will have soon !
best regards Lumsmore and Phil!

Moviestacker
 

get a copy of swiftavs, its similar and wil calculate audio and video bitrate to suit. U can use the preview to see what it will be like. Its from Divxdigest - google it.

You're right about the help that give moviestacker to test filters. But FYI the problems that you have seems to be due to the encoding itself, so you can test the filter you want, you won't see the difference.

I noticed that in the Dialhot V4 script used by DIKO, it has the lines:

DivXResize(WIDTH, HEIGHT, 0, "LanczosResize",WIDESCREEN)

and

DivXBorders(HEIGHT,OVERSCAN)

whilst the V4 script found in these forums instead uses:-

GripCrop(WIDTH, HEIGHT, overscan=1, source_anamorphic=false)
GripSize(resizer="LanczosResize")

and

GripBorders()

Can I ask the following questions:-

1 Is the V4 in DIKO a personal modification from VM? Or an unannounced update from Dialhot?

2 Can some Avisynth expert explain what (if any) difference these changes have on an encode?

3 As regards Moviestacker, I still have a copy of the last version before it was withdrawn. I know that I can use its resize to replace the above lines in the V4 script, but can I replace the same lines in the DIKO version of V4?

Sorry if that is too many questions. :roll:

Hi Fingerbob,
1-The script is basically the same.
The only difference is in the resizing plugin.
Phil uses SansGrip GripFit plugin whereas VM uses his own function/approach to replace GripFit as this last one sometimes fails.
VM just named it DivxResize and it's very good indeed.
2-I'm far from an avisynth expert, but IMHO this shouldn't make any difference at all, besides maybe in it's speed :roll:
3-You're right: you can use Moviestacker or FitCD and just change the resizing/add bordering lines, but honestly I don't know the impact it will make in DiKo.
Maybe DiKo needs DivxResize to work properly...
Wait for more answers or do your own tests and see what you get ;-)
My bet is that it will work just fine :)
Cheers

I never go deep in VM functions but GripCrop remove existent black borders that may be in the source. The borders will be restored with the GripBoders line.
That can explain the diff in speed. Unfortunally, as you told, GripFit plugin leads sometimes to errors and this is why VM replaced it.