PDA

View Full Version : Encoding with CCE results in shorter length video!


Lambchop
4th June 2003, 16:08
I originally posted this here (http://forum.doom9.org/showthread.php?s=&threadid=54576) but it was suggested I ask here.

I have some captured files (MJPEG AVI) which I am trying to convert to video MPEG using CCE. However, when I encode, a ~15 minute clip ends up at around 4 1/2 minutes long. It seems to have the correct start / end point, but its dropping frames along the way through the middle of the video. The jumps don't appear in places with particular high noise levels or anything, they're pretty random. Does anyone have any idea why?

thanks

ultimatebilly
4th June 2003, 16:32
I dont have a clue, but you could maybe try to feet the MJPEG-avi into avisynth, either with the command avisource("file") or with directshowsource("file"), and to encode the avs with CCE...
Is probably a bit slower, but worth a try I think...
You know how avisynth works? If not, here it is:

You install it, then you create a new text file, write your commands in it, and save it with the extension avs.
Thats it...

Hope this helps!

bb
4th June 2003, 17:45
Are the dropped frames present in the source AVI (MJPEG) or only in the CCE encoded MPEG-2 file?

By the way: your question is not DV related...

bb

Lambchop
4th June 2003, 20:54
there's no problem with the frames in the original source (i.e. no skipping or noise or anything like that). The problem only crops up in the CCE encoded file (hence the drop in total clip length). I've also tried serving using AviSynth, but with the same problem. Its happened on multiple occasions with different video clips. It's totally confused me! Is there a setting I might have inadvertently changed that could result in this effect?
sorry if this is in the wrong place bb :stupid:

bb
5th June 2003, 20:08
No problem, I always try to help where I can. Unfortunately I have never run into such a problem, although I've done a few dozen MJPEG->MPEG-2 conversions using CCE.

Which settings did you use?

bb

Lambchop
5th June 2003, 20:19
I pretty much used the standard settings. I think it was okay the first time I tried it (either that or I wasn't paying attention). I thne adopted some of the settings from the doom9.org website, not realising that some of them were aimed more towards re-encoding DVD video (i.e. not understanding what they actually meant!!). Last night, I tried turning off a couple of video settings (progressive scan, zigzag) and got a video that registered at full length when I load it up, but when I played, it skipped to the end when it got around 4 mins through...I'm looking into this and encoding another, longer video now, so will be able to tell if its still a problem later, or more likely tomorrow :)

Out of interest, what settings do you have on/off when compressing from an MJPEG captured source? thanks bb :)

bb
6th June 2003, 22:02
Usually I capture progressive hollywood films. Pre-processing is done in AviSynth, e.g. removing a possible phase-shift by telecide().

I capture at 768x576, crop what's needed, resize to 720x576. If there are black bars, I crop them off and add them again using AddBorders() (to get clean black). I do not encode anamorphic, because I can't capture at 1024x576 ;)

So my CCE settings are basically as follows:
- 4:3 encoding
- multi-pass encoding (two or three passes)
- bitrate set taking into account the audio (AC3) to fill up the entire DVD-R
- progressive frame flag set
- zigzag scan
- "Upper field first" checkbox off (else the video would be shifted by one line, which never makes sense for progressive video)
- no filtering in CCE (but Convolution3D in AviSynth)
- Quantizer characteristics (Flat part priority) to 16
- Intra block DC precision to 9
- No audio encoding in CCE (using BeSweet / AC3Machine instead)

bb

Lambchop
14th June 2003, 22:32
Thanks for the tips bb.

I think its worth mentioning what's happening now....encoding works fine (correct video length) when I encode at CBR, but I still get the problem with VBR....does this shed any light on what might be going on?
Its got me!:confused: