Constant QT Reader Errors in Procoder v3

[eniwetok]

I've been searching the net and here for some way to deal with the constant errors I'm getting using Procoder 3. Most seem to revolve around file naming conflicts which were supposed to have been taken care of in v2 with a new option to overwrite file names for an entire project.

Anyway I'm trying to use Procoder to improve the framerate through interpolation of some 12.5fps .MOV video shot with my digital camera. When I can get Procoder to work it encodes the video for 6 seconds then I get only audio.

Any ideas?

Which raises the larger question, are there any better encoders out there for frame interpolation?

Thanks!

[eniwetok]

It may not all have to do with file names. At times, depending on what "target" I choose, I can get more video processed. Using the QT NTSC might give me 8 seconds while the H264 might convert 1 minute before I get the QT Reader: General Error popup.

When I did H264 NTSC 2pass, it got through the first pass but again crashed on the second.

[Arky]

Hi, what codec is your source material?


Arky

[eniwetok]

Hi, what codec is your source material?


Thanks for responding. According to GSpot the source video is MPEG4 but the codec is undetermined. The container is MPEG Elementary Video. It was shot on a 4 year old Kodak digital camera.

Procoder only says it was compressed with MPEG4.

I was able to work with an AVI file shot on a friend's camera (Canon?) but that does me no good since I really need to improve the framerate of video shot with my camera.

[Blue_MiSfit]

Which raises the larger question, are there any better encoders out there for frame interpolation?


Yessir :)

AviSynth (while not an encoder) has a fantastic plugin for doing just this - MVTools!

Specifically, its wonderful MVFlowFPS2 function!

http://avisynth.org.ru/mvtools/mvtools.html

Read this, specifically the code examples towards the end of the document for MVFlowFPS2. I have pasted it in for convenience's sake:

# assume progressive PAL 25 fps source
backward_vec = source.MVAnalyse(isb = true, truemotion=true, pel=2, idx=1)
# we use explicit idx for more fast processing
forward_vec = source.MVAnalyse(isb = false, truemotion=true, pel=2, idx=1)
source.MVFlowFps(backward_vec, forward_vec, num=50, den=1, ml=100, idx=1) # get 50 fps


Let's adapt this for your source, assuming you have 12.5fps, and want to go to 25fps:

#First, load the MOV
QTInput("c:\video.mov")

#Second, do the motion analysis
backward_vec = source.MVAnalyse(isb = true, truemotion=true, pel=2, idx=1)
forward_vec = source.MVAnalyse(isb = false, truemotion=true, pel=2, idx=1)

#Now, do the conversion
source.MVFlowFps(backward_vec, forward_vec, num=25, den=1, ml=100, idx=1)

#At this point we have 25p video. You can resize, denoise, sharpen as necessary


Load the script into something fancy like x264 and rock 'n' roll :)

Let me know if you need help getting this working. It won't be too hard, and the results will impress :)

~MiSfit

[eniwetok]

Hi, what codec is your source material?


I tracked it down in the camera manual:

Video: QuickTime (CODEC MPEG4)

Yessir :)
AviSynth (while not an encoder) has a fantastic plugin for doing just this - MVTools!
Specifically, its wonderful MVFlowFPS2 function!
http://avisynth.org.ru/mvtools/mvtools.html


Thanks for responding MiSfit... I believe I had tried AVISYNTH on my last PC when I was going to attempt deblocking these same videos. While it is a capable tool, I was put off by the lack of a GUI then I got sidetracked with frame interpolation then who knows what. I downloaded and installed AVISYNTH and if I can't get ProCoder working, I'll try it again.