Directshowsource forcibily outputs 25fps, 23.98fps source

[rmm21]

Hi all, i've browsed these forums many times looking for information but now I really need help.

Recently, I have successfully encoded my videos to XVID using the latest Megui and latest Avisynth but up until two or three days ago i've noticed that they are all being converted to 25fps, regardless of original source fps, even though previously every one of them was giving output of 23.98fps which is what I wanted.

I tested to see if it was the video source by using a previous video I encoded last week that came out earlier to 23.98fps(same fps and total number of frames as original source), but ended up now(using the same exact script with same XVID profiles in MeGui)with a 25fps video file, even though I haven't changed anything and am using only this basic script:

DirectShowSource("C:\Documents and Settings\mymovies\Recording01.mkv",fps=23.97598565 27702,audio=false)
ConvertToYV12()
Lanczos4resize(640,368)
MSharpen(1,60,true,false,false)

Here is what the test.avs I did showed for the original non-XVID video:
Frame: 16860 of 33720
Time: 00:11:43:201 of 00:23:26:403
ColorSpace: YUY2
Width: 704 pixels, Height: 480 pixels
Frames per second: 23.9760 (10000000/417083)
FieldBased (Separated) Video: NO
Parity: Bottom Field First
Video Pitch: 1408 bytes
Has Audio: NO
CPU detected: x87 MMX ISSE SSE SSE2

Here is what the test.avs for the new 25fps video gave:
Frame: 16860 of 33720
Time: 00:11:14:400 of 00:22:28:800
ColorSpace: YUY2
Width: 640 pixels, Height: 368 pixels
Frames per second: 25.0000 (25/1)
FieldBased (Separated) Video: NO
Parity: Bottom Field First
Video Pitch: 1280 bytes
Has Audio: NO
CPU detected: x87 MMX ISSE SSE SSE2

The duration for each video is different as well:
Duration(Original non-XVID 23.98fps): 23:26:40minutes
Duration(New XVID 25fps): 22:28:80minutes

I viewed both videos using Media Player Classic and, as an example, at 02:36minutes in the original non-XVID 23.98fps file, the same scene shows up now earlier in the new XVID 25fps file at 02:29minutes. Strange but the 25fps video seems while watching to progress visually faster, I believe.

Playing the newly encoded 25fps XVID video in Media Player Classic gives a frame rate between 24.98-25.02fps(different fps from original but same total number of frames as original source). The older 23.98fps encoded non-XVID and XVID videos when played both stay around 23.98fps. Neither show when playing in Media Player Classic under statistics any frames being dropped.

The same video's mp3 muxed in fine with no audio sync issues at that 23.98fps but at the now 25fps it becomes also gradually unsynced as all the newest encoded videos.
I don't understand why the PAL fps is being forced. I've uninstalled and reinstalled the latest XVID codec, Megui and all tools, Avisynth(all new filters), FFDshow, and DirectX(latest), but the same thing happens. As you can see in my script, i've never had to use assumefps/changefps/convertfps in Avisynth to get 23.98fps with the same video I did before using the above script worked perfectly before as it is. I did add for variation convertfps=true and it still output 25fps.

Does anyone know why this is happening and what I could of changed unknowingly to get 25fps output?

Thanks, Jerrilyn.


P.S. I re-encoded the file and watched it's creation in the MeGui information window during both passes and suprisingly it showed 33719 frames total and 23.26minutes being processed for both passes but the output file was again only 22.28minutes but 33720 frames.
Here is the MeGui Log for the new 25fps XVID:

Looking for job processor for job...
Processor found!

------------------------------------------------------

Starting job job1 at 10:02:01 AM
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:
-i "C:\Documents and Settings\mymovies\Recording01.avs" -pass1 "C:\Documents and Settings\mymovies\Recording01.stats" -bitrate 1300 -kboost 100 -ostrength 0 -oimprove 0 -odegrade 10 -clow 5 -overhead 0 -turbo -max_key_interval 240 -nopacked -qmatrix "C:\Program Files\megui\extra\Didees SixOfNine.cqm" -nochromame -imin 3 -imax 5 -pmin 3 -pmax 5 -noclosed_gop -bquant_ratio 100 -bquant_offset 0 -bmax 3 -threads 0
successfully started encoding
Processing ended at 10:25:41 AM
----------------------

Log for job job1

xvid_encraw - raw mpeg4 bitstream encoder written by Christoph Lampert 2002-2003

Trying to retrieve width and height from input header
xvidcore build version: xvid-1.2.0-dev
Bitstream version: 1.2.-127
Detected CPU flags: ASM MMX MMXEXT SSE SSE2 TSC
Detected 1 cpus, using 1 threads.

Tot: enctime(ms) =405248.00, length(bytes) = 458147148
Avg: enctime(ms) = 12.02, fps = 83.21, length(bytes) = 13586
I frames: 751 frames, size = 47319/35536794, quants = 2 / 2.00 / 2
P frames: 11592 frames, size = 21972/254699966, quants = 2 / 2.00 / 2
B frames: 21346 frames, size = 7866/167910200, quants = 2 / 2.00 / 2
N frames: 31 frames, size = 6/ 188

----------------------
Starting postprocessing of job...
Job completed successfully and deletion of intermediate files is activated
Postprocessing finished!
End of log for job1
-------------------------------------------------------

Looking for job processor for job...
Processor found!


------------------------------------------------------

Starting job job2 at 10:25:41 AM
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:
-i "C:\Documents and Settings\mymovies\Recording01.avs" -pass2 "C:\Documents and Settings\mymovies\Recording01.stats" -bitrate 1300 -kboost 100 -ostrength 0 -oimprove 0 -odegrade 10 -clow 5 -overhead 0 -max_key_interval 240 -nopacked -vhqmode 4 -qmatrix "C:\Program Files\megui\extra\Didees SixOfNine.cqm" -imin 3 -imax 5 -pmin 3 -pmax 5 -noclosed_gop -bvhq -bquant_ratio 100 -bquant_offset 0 -bmax 3 -threads 0 -avi "C:\Documents and Settings\mymovies\Recording01.avi"
successfully started encoding
Processing ended at 11:10:32 AM
----------------------

Log for job job2

xvid_encraw - raw mpeg4 bitstream encoder written by Christoph Lampert 2002-2003

Trying to retrieve width and height from input header
xvidcore build version: xvid-1.2.0-dev
Bitstream version: 1.2.-127
Detected CPU flags: ASM MMX MMXEXT SSE SSE2 TSC
Detected 1 cpus, using 1 threads.

Tot: enctime(ms) =1697945.00, length(bytes) = 219077936
Avg: enctime(ms) = 50.35, fps = 19.86, length(bytes) = 6496
I frames: 751 frames, size = 33878/25442938, quants = 3 / 3.00 / 3
P frames: 11592 frames, size = 7814/90580812, quants = 2 / 4.36 / 5
B frames: 21346 frames, size = 4827/103054000, quants = 2 / 3.44 / 4
N frames: 31 frames, size = 6/ 186
desired video bitrate of this job: 1300 kbit/s - obtained video bitrate (approximate): 1250 kbit/s
----------------------
Starting postprocessing of job...
Job completed successfully and deletion of intermediate files is activated
Postprocessing finished!
End of log for job2
-------------------------------------------------------

[Alex_ander]

Does anyone know why this is happening and what I could of changed unknowingly to get 25fps output?

From my own recent experience I can tell that the only correct way of opening a file via DirectShowSource is specifying its actual and exact FPS value, otherwise you'll get different video/audio duration (serious synch problems) and repeated frames (in the end if you specify a bigger value than actual, e.g. 12.5 instead of 12 or spread along the file if you set convertFPS=true). You can only estimate the exact value by testing script frame by frame in VDub. Most tools report incorrect values for wmv, asf and flv (like 25 instead of 12.5, 12.5 instead of 12, etc.), even opening a script without FPS parameter in DirectShowSource can show wrong value in VDub.
In case of MKV I'd try to unpack avi stream and then use AviSource.

[rmm21]

Thank you for the response.
The mkv i'm using has an H264 video contained within so I don't believe avisource will work, unfortunately. The odd thing is everything worked a couple of days ago without using convertfps or changefps in the scripts. I don't understand what I could of changed for it not to work after doing the same process a few dozen times with exact source fps to exact newly encoded XVID fps output.
I've downloaded and reinstalled brand new programs after cleaning out the registries, and temp locations, and program folder leftovers but nothing helped yet.

Jerrilyn.

[Midzuki]

In case of MKV I'd try to unpack avi stream and then use AviSource.

The mkv i'm using has an H264 video contained within so I don't believe avisource will work, unfortunately.

But you could try using DirectShowSource on the h264 file.
Perhaps the whole trouble is in the Matroska container itself ---
it usually is as problematic as RMVB.

==================================

[rmm21]

I thought of that so I tried using vob files and other avi files I have(23.98fps originally) and ended up with 25fps output also. I almost feel the only way to fix this is to format my harddrive since I didn't have system restore on at the time of the change. I really don't want to do that though.
I wonder if it is some strange region coding going on with Directx. I'm saying this because I also tried output using just virtualdubmod on vob file and it also gave 25fps output. The same 23.98fps file worked previously and output 23.98fps just last week using MeGui and Avisynth and the script I posted.

Thanks for the help though. Any other ideas? Jerrilyn.

[guns1inger]

23.98 is a rounded up figure anyway. DVDs would be encoded at 23.976 fps, not 23.98.

[rmm21]

I know it is. Actually, I was using 23.9759856527702fps, but 23.98fps was a lot easier to type out.

I wonder what changed with my computer and the installed programs to keep it from producing the same 23.98fps outputs it has been giving me(happily) for the last several weeks.

Jerrilyn.

[Midzuki]

Recently, I have successfully encoded my videos to XVID using the latest Megui and latest Avisynth

I've uninstalled and reinstalled the latest XVID codec, Megui and all tools, Avisynth(all new filters), FFDshow, and DirectX(latest), but the same thing happens.

The latest Avisynth is 2.5.8., still an alpha thing, according to sourceforge.net;
Is this what you're using?

Besides, latest DirectX, plus ffdshow? Perhaps this mish-mash is
the cause of your current problems, I am not sure. As to myself, I use Avisynth
2.5.7 and DirectX 9; still, sometimes AVS's ImageSource/Reader does not want
to work on .PNG files, other times, DirectShowSource simply refuses to detect
the audio stream of a specific file. If uninstalling ffdshow and/or downgrading AVS plus
DirectX do not work, I'm afraid you'll really have to re-install the OS and applications :-(

======================

[rmm21]

Actually, i'm using the almost latest Avisynth build(257) and DirectX 9c(I think the latest stable one). Audio shouldn't be an issue with the mkv file I was feeding into MeGui because it doesn't have any audio in the container. I extracted it using mkvmerge so only the H264 is in the mkv which as of last week was able to work just fine for producing source 23.98fps to 23.98fps finalized output.

I was hoping doing a reformat was a last option.

Jerrilyn.

[rmm21]

Here's an update: I unstalled every multimedia related program on my computer(Avisynth, FFdshow, Haali Media Splitter, MeGui, Vobsub, CCCP remnants, latest XVID codec, mkvtoolnix, etc...), cleaned temp and registries, defragmented hard drive, and re-downloaded the programs I needed: Avisynth257, MeGui w/.net 2, Mkvtoolnix, Mkvextractgui, and Gabest mkv splitter.
No FFdshow or Haalimedia Splitter anywhere on my computer.

I used Mkvextractgui to recreate the same files I needed to encode(that H264 file I am trying to convert to XVID) just in case of some weird anomaly in the source which, just to recall, produced a perfect 23.98fps XVID last week at the same exact duration as the original.

Installed MeGui, created new avs, let it go for about an hour using XVID profile 30%, and yahooooo, was given, from a 23.98fps H264 source file, a shiny new f-ing 25fps XVID file at 22.28minutes in duration(original was 23.26minutes long FYI).

I think when I say this sucks it's hardly touching what I feel.

I would say that my computer has a big problem with Directshow which is for some reason dropping frames. The only thing that seems to correlate with the change in correct output is that I recently did a Windows Express Priority Update. Maybe something put a kink in my computer?

I just don't know.
Jerrilyn.