Log in

View Full Version : Inverse telecine produces giant file ?


mmlnewbie
6th February 2004, 09:42
Question: The faq/guides mention that inverse telecine can increase the file size. Well my file-size increased from 720 MB to 2GB+ - is that reasonable ? Or am I just clueless and doing something completely wrong ?

Background: The other day I found a rare vid-capture of a standup act encoded in divx/mp3 at 29.97 fps. I wanted to put this on a cd for my hw divx player. Unfortunately whoever encoded it screwed up with the bitrate-calculator because it was in a 720 mb avi file. So I decided to re-encode the video and while I was at it convert to 25 fps. Perhaps I'm naïve, but here's what I did:

- demuxed audio track with virtual dub
- opened avi file in gknot
- changed settings for a single 700 mb cd, etc
- selected Inverse Telecine in Gknot encoding-job dialog in order to get to 23.976 fps
- edited avs script to include convertToYUY2, convertFPS(25)

The result was very, very good - much better quality than the source (and my expectations) - BUT, the damn file had swelled up to 2 gb! I reckon I can fix it by simple re-encoding with the 25 fps progressive giant file, but it would seem better to do this in a single encoding session so to speak. Any ideas ?

I've converted ntsc dvds to 25 fps many times using these avs commands, but have always used dvd2avi force-film for de-interlacing (when needed). Gknot usually gets upset about the incorrect frame-count after the first pass, but settles down after that and the results are usually good.

In this case I didn't really have a choice, so I used avs for de-interlacing whithout really knowing how to verify whether the source was interlaced in the first place. I just assumed it was since it was 29.97 fps and had interlacing artifacts on the computer screen.

jggimi
8th February 2004, 22:35
Open your 2GB .avi file with GSpot (http://www.doom9.org/Soft21/Editing/gspot221.exe), and see what it tells you. It is my guess that one of the following is the trouble. You are not using an MPEG-4 codec The encoding bitrate is messed up You are attempting to use an unsupported XviD release, such as 1.0.If none of these is obvious, then the _GKnot.log file may provide more information.