kilg0r3
16th December 2002, 10:57
The post concerns Xvid bframes as well as VirtualDubMod. I wasn't really sure where to post it. so the mods may feel free to move it if desired.
I am using Koepi's XviD-09122002-1 build and the latest version of VirtualdubMod. The last movie i encoded was 2001. Which is an extremely compressible one. 2:20h on one CD with full resolution + ogg 3.5q.
Chroma Motion - on
Bframes - 4
Bframe Qu - 100
BF Qu Offset - 100
DX50 Comp - on
But on to buisness. Since i wanted the ac3 sound i put on two cds. And the splitting was where the fun started. It is quite difficult to describe the problem. Firstly, the usual method 'jump from key frame to key frame, set the mark and just save' does not work. The saved file all ways includes some 5 or more seconds of the preceeding scene. When i push the mark forward frame by frame, even 20 frames into the scene, I still get the exact same file (size) including the same amount of frames from the previous scene. Even when i try to cut the superfluous frames from the resulting file by loading it into vdubmod and use the 'delete selected frames' function. The saved file remaines the same.
The phenomenon is extremely fuzzy, also because of the static nature of the movie. So that i am not really sure if have been able to find one real cut point. However I have the impression that when one finally arrives at a point where the preceeding scene is no longer included in the saved file, there seem to lack some of wanted frames. Yet, i hadn't the nerve to figure that out.
Furthermore, there seem to be some scene changes which are easier to locate and use than others. Still, having found one of these 'better'keyframes' i noticed that moving one frame forward with the cursor keys in vdubmod produced a preceeding frame instead of a successor. Everything in the preview moved backward.
Thanks for reading ..
kilg0r3
PS: Since neither vdub nor vdubmod show the frame type, is there an app that does. Would make it easier to figure out if a key frame has been inserted at all or not.
I am using Koepi's XviD-09122002-1 build and the latest version of VirtualdubMod. The last movie i encoded was 2001. Which is an extremely compressible one. 2:20h on one CD with full resolution + ogg 3.5q.
Chroma Motion - on
Bframes - 4
Bframe Qu - 100
BF Qu Offset - 100
DX50 Comp - on
But on to buisness. Since i wanted the ac3 sound i put on two cds. And the splitting was where the fun started. It is quite difficult to describe the problem. Firstly, the usual method 'jump from key frame to key frame, set the mark and just save' does not work. The saved file all ways includes some 5 or more seconds of the preceeding scene. When i push the mark forward frame by frame, even 20 frames into the scene, I still get the exact same file (size) including the same amount of frames from the previous scene. Even when i try to cut the superfluous frames from the resulting file by loading it into vdubmod and use the 'delete selected frames' function. The saved file remaines the same.
The phenomenon is extremely fuzzy, also because of the static nature of the movie. So that i am not really sure if have been able to find one real cut point. However I have the impression that when one finally arrives at a point where the preceeding scene is no longer included in the saved file, there seem to lack some of wanted frames. Yet, i hadn't the nerve to figure that out.
Furthermore, there seem to be some scene changes which are easier to locate and use than others. Still, having found one of these 'better'keyframes' i noticed that moving one frame forward with the cursor keys in vdubmod produced a preceeding frame instead of a successor. Everything in the preview moved backward.
Thanks for reading ..
kilg0r3
PS: Since neither vdub nor vdubmod show the frame type, is there an app that does. Would make it easier to figure out if a key frame has been inserted at all or not.