killerteengohan
6th February 2015, 13:48
I have a .FLV file of a single episode. I tried file indexing the .FLV but it had bad results and crashed, so I extracted the .264 video and .aac audio from it with flvextract (http://www.videohelp.com/tools/FLV-Extract) and worked with those instead.
Everything seems to go fine. I file indexed the .264 file and converted the .aac file to mp3. For some reason though, when avisynth (http://www.videohelp.com/tools/Avisynth) is all done encoding the single episode, on playback random blocks and or signs of corruption keep appearing on the video at random times.
http://i.imgur.com/MLil9K8.png
http://i.imgur.com/hhVwSE6.png
The .FLV file when played back does not have this issue, its only after going through avisynth that this happens. Im sure its not the filters Im using because I have used them many times before.
I havent tried to do this since 2011 and it worked perfectly fine back then, this was not an issue. I have since gotten better at encoding and wanted to refix it up but I am having this problem.
Any idea on why it would be getting this issue now? The only new thing about my computer I can think of since back then is I got a new NVidia GTX 980 graphics card. Not sure if that can be a cause but thought I would point it out.
Everything seems to go fine. I file indexed the .264 file and converted the .aac file to mp3. For some reason though, when avisynth (http://www.videohelp.com/tools/Avisynth) is all done encoding the single episode, on playback random blocks and or signs of corruption keep appearing on the video at random times.
http://i.imgur.com/MLil9K8.png
http://i.imgur.com/hhVwSE6.png
The .FLV file when played back does not have this issue, its only after going through avisynth that this happens. Im sure its not the filters Im using because I have used them many times before.
I havent tried to do this since 2011 and it worked perfectly fine back then, this was not an issue. I have since gotten better at encoding and wanted to refix it up but I am having this problem.
Any idea on why it would be getting this issue now? The only new thing about my computer I can think of since back then is I got a new NVidia GTX 980 graphics card. Not sure if that can be a cause but thought I would point it out.