Glitch in decoding H.264 #3
Posted: Tue Oct 02, 2012 5:53 am
I'm back with the same kind of glitch like before and I hope we finally figure it out this time 
I got a 15 frames long glitch caused by decoding of H.264 track from TV capture via DGDecNV. The glitch is not there when I use DirectShowSource or FFVideoSource, or if I play it in mpc-hc with CoreAVC or ffdShow decoder or in VLC. As far as I can tell the capture is glitch-free. I got this kind of unforeseeable glitch few times also on video track from Blu-ray, I do not believe it is HDTV related.
The glitch appears when I play the avisynth script (only with DGSource() in it) in VirtualDub or frame-step in AvsPmod from frame 0. The glitch appears only when the script is played from the beginning, if I seek to some frame and play from there, it doesn't appear! This is the same behaviour like I got few times before already and I believe it is the same exact bug that's causing it.
I replicated the glitch on my desktop pc with GTX 570 (various drivers) and on my laptop with GT 220M, with DGDecNV 2042 and 2043, using decode modes 0,1,0 and 1,1,1. It is there when I index the track in mkv or demuxed h264.
Here's 40sec video from the very beginning of the capture, which is enough to replicate it:
http://www.mediafire.com/?02g61wt751sk9ca
As you can see, it's like it was overlapping with frame from 900 frames before:
The glitch is from frame 889 to frame 903. And like I said, it is there only when it's played/frame-stepped from frame 0, it is not there when seeking to frame X before 889 and frame-stepping from X, or when seeking to frames 889-903 directly.
It is there if I use DGSource("source.mkv").Trim(1, 0), but it isn't there if I use DGSource("source.mkv").Trim(200, 0).
It is really strange and it's bugging me a lot, I hope we'll be able to figure it out soon. If you need any more assistance, please let me now.
I got a 15 frames long glitch caused by decoding of H.264 track from TV capture via DGDecNV. The glitch is not there when I use DirectShowSource or FFVideoSource, or if I play it in mpc-hc with CoreAVC or ffdShow decoder or in VLC. As far as I can tell the capture is glitch-free. I got this kind of unforeseeable glitch few times also on video track from Blu-ray, I do not believe it is HDTV related.
The glitch appears when I play the avisynth script (only with DGSource() in it) in VirtualDub or frame-step in AvsPmod from frame 0. The glitch appears only when the script is played from the beginning, if I seek to some frame and play from there, it doesn't appear! This is the same behaviour like I got few times before already and I believe it is the same exact bug that's causing it.
I replicated the glitch on my desktop pc with GTX 570 (various drivers) and on my laptop with GT 220M, with DGDecNV 2042 and 2043, using decode modes 0,1,0 and 1,1,1. It is there when I index the track in mkv or demuxed h264.
Here's 40sec video from the very beginning of the capture, which is enough to replicate it:
http://www.mediafire.com/?02g61wt751sk9ca
As you can see, it's like it was overlapping with frame from 900 frames before:
The glitch is from frame 889 to frame 903. And like I said, it is there only when it's played/frame-stepped from frame 0, it is not there when seeking to frame X before 889 and frame-stepping from X, or when seeking to frames 889-903 directly.
It is there if I use DGSource("source.mkv").Trim(1, 0), but it isn't there if I use DGSource("source.mkv").Trim(200, 0).
It is really strange and it's bugging me a lot, I hope we'll be able to figure it out soon. If you need any more assistance, please let me now.
