Gknot bitrate calc/credits error

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Diegoll2k
    South American DivXer
    • Mar 2002
    • 48
    #1

    Gknot bitrate calc/credits error

    I am having a problem while doing 2-pass encoding with GKnot 0.26 beta and DivX 5.0.2, encoding credits separately at 20%. Here is a part of the log file GKnot made:

    10:16:36 a.m.: Started DivX5-Single, Quality 20%: G:\el hijo de la novia_Credits_Credits.avs
    10:28:53 a.m.: Finished DivX5-Single, Quality 20%. Duration: 12 minutes, 16 seconds.
    10:28:53 a.m.: Assumed: Main Movie has 217945 Frames.
    10:28:53 a.m.: Assumed: Credits Part has -38053 Frames.
    10:28:53 a.m.: Credits Size = 1966Kb
    10:28:53 a.m.: New Bitrate for Movie = 567 k(=1000)Bits/s

    The original bitrate was 689 Kbit and it had 179892 frames at 23,976 fps. As you can see, GKnot made a mistake when counting the number of frames, and corrected the bitrate (i checked it in the encoding options). The final AVI was downsized
    from the expected 685 MB to exactly 500 MB + 2 MB of the credits.

    I solved the problem by disabling bitrate correction, but it is
    supposed to work ok !! Any ideas on what could I have done wrong ?? If you need extra info please ask for it. Thanx in advance
    Tags: None
    • Diegoll2k
      South American DivXer
      • Mar 2002
      • 48
      #2
      Forgot to say, the credits where encoded OK.

        Comment

        • khp
          The Other
          • Nov 2001
          • 2161
          #3
          Strange, may we see the entire logfile.
          Donate your idle CPU time for something usefull.
          http://folding.stanford.edu/

            Comment

            • Diegoll2k
              South American DivXer
              • Mar 2002
              • 48
              #4
              Here goes the log file. I aborted the process when it was doing the second pass. I deleted the first log accidentaly and cannot recover it. However, the log shows clearly what happened. See for yourself.
              Attached Files

                Comment

                • khp
                  The Other
                  • Nov 2001
                  • 2161
                  #5
                  My guess is that your source still contain 29.97 fps.

                  Your fps is set at 23.976, for this to be correct you must use force film in DVD2AVI or preform IVTC .
                  Donate your idle CPU time for something usefull.
                  http://folding.stanford.edu/

                    Comment

                    • Diegoll2k
                      South American DivXer
                      • Mar 2002
                      • 48
                      #6
                      Wow man, you're a genius. That was the problem. I didn't use them, but can I use Force Film on NTSC Interlaced Material ???
                      I thought I couldn't. I should have used IVTC anyway, but I got misled by Gknot's advice.

                        Comment

                        • khp
                          The Other
                          • Nov 2001
                          • 2161
                          #7
                          Originally posted by Diegoll2k
                          but can I use Force Film on NTSC Interlaced Material ???
                          No, that would be bad, you should only use ForceFilm on material that shows up as Film in DVD2AVI.

                          Originally posted by Diegoll2k

                          I should have used IVTC anyway, but I got misled by Gknot's advice.
                          Yes getting IVTC to work properly in GKnot can be a bit tricky, don't ask me how this is done, I have no clue.
                          Donate your idle CPU time for something usefull.
                          http://folding.stanford.edu/

                            Comment

                            • Diegoll2k
                              South American DivXer
                              • Mar 2002
                              • 48
                              #8
                              Thanxs a lot anyway. I know what the problem is now........

                                Comment

                                Previous template Next
                                Working...