Doom9's Forum - View Single Post - New AviSynth tool

Dr.Khron · 18th April 2007, 15:35

I just started using all the power features in AvsP... VERY cool program, much thanks to the developer.

Ok, so I've got an odd issue... Is there any way to set the FPS the program uses to determine time stamps?

My current script loads a D2V file with DGDecode. The DVD is NTSC material: 720x480 at 29.97 FPS. However, the program displays the video as being 640x480 at 23.976 FPS.

This causes descrepancies between frame counts and various time stamps... its a pain in the ass to try and convert frame counts into times for the TextSub filter and other things.

EDIT:
DOH. I just realized that AvsP is displaying the information for the ouput file... my de-interlace routine causes the FPS to change, and I resize the video in the course of the script.

Still doesn't solve my problem, tho...

EDIT:
Yes, it actually does solve my problem... as long as I use the 23.976 for my FPS, all of the frame math works out (for filters added after de-interlacing, anyway).

18th April 2007, 15:35	#637 \| Link
Dr.Khron Registered User Join Date: Oct 2006 Location: Gotham City, USA Posts: 389	I just started using all the power features in AvsP... VERY cool program, much thanks to the developer. Ok, so I've got an odd issue... Is there any way to set the FPS the program uses to determine time stamps? My current script loads a D2V file with DGDecode. The DVD is NTSC material: 720x480 at 29.97 FPS. However, the program displays the video as being 640x480 at 23.976 FPS. This causes descrepancies between frame counts and various time stamps... its a pain in the ass to try and convert frame counts into times for the TextSub filter and other things. EDIT: DOH. I just realized that AvsP is displaying the information for the ouput file... my de-interlace routine causes the FPS to change, and I resize the video in the course of the script. Still doesn't solve my problem, tho... EDIT: Yes, it actually does solve my problem... as long as I use the 23.976 for my FPS, all of the frame math works out (for filters added after de-interlacing, anyway). Last edited by Dr.Khron; 18th April 2007 at 15:47.