End user gains by using ffms2 input instead of avisynth/DirectShowSource

[HaraldBluetooth]

I make a lot of re-encodes of 720p sources (4-7 movies per day) and I'm using MeGui to make the avisynth script (and to analyse the source for interlaced content and so on) and normally I don't use any filtering at all.

Since the introduction of tuning and presets in x264, I've been using Preset: Slow and Tuning: Grain and CRF22 and I've been very satisfied with the results so far, which to my eyes are fairly transparent to the source. Up to now I've used LoRd_MuldeR's  "Simple x264 Launcher" to encode in 64-bit on a Windows 7 platform.

CoreAVC is my system default decoder for x264/H264 content.

What will my gains as an unexperienced end user be by using ffms2 input instead of my normal workflow with avisynth and DirectShowSource.

Please help me out - I can't see the forrest for all the trees.

[Dogway]

As long as I know its frame accurate seeking, and it also keeps the variable framerate on certain video sources. So it doesnt shift with the audio. Although I still havent managed to make it work.

I have read the documentation but there's not any synthom-solution like of help. So far the code Im struggling with is:

Code:

loadplugin("...\AviSynth 2.5\plugins\ffms2.dll")
FFIndex("...\source.mp4", indexmask=7, dumpmask=0, overwrite=true)
FFVideoSource("...\source.mp4",cache=true,seekmode=1,cachefile="test.ffcache")

with no success.

I guess there are other benefits, I would also like to know.


EDIT:
This seems to work Herald.

Code:

source="mysource.mp4"
FFIndex(source,cachefile = source + ".ffindex",audiofile = "%si%.%trackzn%.w64",errorhandling=1)
FFVideoSource(source,cache=true,seekmode=1,cachefile="mysource.mp4.ffindex")

I would also like to know the practical benefit of its use and in under what circumstances make use of it.