Frankly, I didn't use DirectShowSource since a long time - few years: I always use DGindex/MPEGsource with MPEG-2, and DSS2 with AVC (and the few times I deal with VC-1 as well).

I think I'll stay with FFvideosource, that, after index is made, is a bit more faster.

I agree that FFVideoSource is very good, once the index file is written (.ffindex file) it is saved in the same folder as the original file. I find it works flawlessly with MKV containers but can struggle with transport streams. In fact the wiki page describes seeking with a .ts as being 'off a few frames here and there'.

I too had all sorts of trouble with LSmash. I did everything suggested but it literally refused to work. 

spoRV: Did you ever have any weird artifacts using DGAVCDec? I found all sorts of strange stuff (blocking, corruption) unless I used deblock=true, but then the image is slighly filtered. I know that even the developer recommends not using it now. I can't use the newest version as I have an AMD CPU.

Frankly, the few times I tried to use DGAVCindex, it gave me any sort of errors, then the program suddenly closes itself...

.ts: it seems that DSS2 has no problems with it.

But I must admit that DSS2 should be as good as FFvideosource, talking about frame precision, and I suspected the contrary just because this night I spent few hours to put in sync a laserdisc and a BD, that took about 120 frames to be cut or repeated, and I wondered it was DSS2 fault... that was not the case, as the missing/repeated frames are there even watching each version frame by frame using a software player... that was the only case I had to adjust so many frames until now, where usually just few frames must be added or cut - normally three or four...

The strange thing is, in a shot of few dozen frames, LD has one frame more, but in the following one is missing one, or the contrary is true if seen from the BD perspective... in these cases, a scene detection script is a welcome help, even if it's not perfect, it helps to spot eventually differences, instead of be forced to watch the whole movie frame by frame!

My take with source filters is they are all frame accurate, until you start seeking... I tried using an avisynth proxy (with DSS) for editing and things started going wrong very quickly. In the end I had to render out a lossless to finish the edit.

I use megui/tool to do this , but always different source_decoder as media container

For DVD
DGIndex - DGDecode_mpeg2source()

mp4/mkv
L-smash works - LSMASHVideoSource()

3D-Bluray
ssifSource - for reading BD3D

Frimsource i tried it but didn't used it for encoding because it takes so long to read frames 1 to last and coz of manually setting last frame number , it take some time to get there so i didn't used it much.

I encode blu-ray this way with avisynth script.
Hd streams extractor with L-samsh works mostly , but recently i tried HD streams Extractor + FFVideosource for VC1 codec .m2ts .


HD Streams Extractor for extracting video to its raw format or Mkv since i've did it already , VC-1 mkv info coded below

here's encoded sample
https://www.sendspace.com/file/nr8ek1

AVC and VC-1 inside .ts/.m2ts files often are read "slowly" by ffvideosource/directsource/DSS2 - I mean, with heavy filters like the ones I usually use, they "catch" the sync after several frames... if I remux them onto a new .mkv, no problems!

(2018-03-29, 08:55 PM)spoRv Wrote: AVC and VC-1 inside .ts/.m2ts files often are read "slowly" by ffvideosource/directsource/DSS2 - I mean, with heavy filters like the ones I usually use, they "catch" the sync after several frames... if I remux them onto a new .mkv, no problems!

Yes i realise it when i tried it FFvideosource was reading a m2ts slower than usual so i tried HD stream Extractor to extract the .m2ts to mkv or to raw format and after when i tried mkv FFvideosource it was reading frames normally so i stick to this this method , and when i use heavy filter like smdegrain-16bit/ seesaw-8bit on bluray then i use mp_pipeline meta-filter to speed up the script and to keep it running steady and stable while x264 is encoding my .avs.

mp_pipeline is one of my favourite meta-filter which i perform on all of my script to speed up.

(2018-03-29, 09:23 PM)BlackMirror Wrote: mp_pipeline is one of my favourite meta-filter which i perform on all of my script to speed up.

It seems interesting, never used it... why don't you write a simple short guide about this? I think there will be others interested, apart me!

(2018-03-29, 09:52 PM)spoRv Wrote:

(2018-03-29, 09:23 PM)BlackMirror Wrote: mp_pipeline is one of my favourite meta-filter which i perform on all of my script to speed up.

It seems interesting, never used it... why don't you write a simple short guide about this? I think there will be others interested, apart me!

yes indeed it is very interesting, i am using it from many years by now and i always learn something new whenever tweaking mp_pipeline in my script. alright i will make a small guide to start up with the mp_pipeline .