Forum Archive Home -> Advanced Video Conversion -> FitCD assumes source is PAL

FitCD assumes source is PAL

sambat posted 2008 Sep 02 08:10

This is an .m2v file from Dgindex loaded into Fitcd. The clip was an OTA capture from a Detroit station and is certainly NTSC. The initial settings on the input and output side were both set PAL by the program. I unchecked the PAL setting on the output and the script changed to add a line to change the FPS to 23.976 My questions are: 1 Is there an obvious reason why Fitcd could assume this was a PAL video 2 When I set the output to NTSC, why would it not add a line to convert the FPS to 29 instead of 23 General Complete name : C:\Documents and Settings\Superuser\Desktop\dgi\-2008-08-29-0.demuxed.m2v Format : MPEG Video Format version : Version 2 File size : 192 MiB Duration : 1mn 58s Overall bit rate : 13.6 Mbps Video Format : MPEG Video Format version : Version 2 Format profile : Main@High Format settings, Matrix : Standard Duration : 1mn 58s Bit rate mode : Constant Bit rate : 13.0 Mbps Nominal bit rate : 19.0 Mbps Width : 1280 pixels Height : 720 pixels Display aspect ratio : 16/9 Frame rate : 59.940 fps Colorimetry : 4:2:0 Scan type : Progressive Bits/(Pixel*Frame) : 0.344

jagabo posted 2008 Sep 02 09:52

FitCD isn't assuming PAL. Your video came up as PAL simply because that's how it was set last time you used it. Just untick it. But you're going to have a problem with 59.94 fps material. FitCD isn't prepared to deal with this so you'll have to do it yourself. If it's film material (ie, 23.976 fps film frames are duplicated to create 59.94 fps) you can decimate it down to 23.976 fps. If it's full 59.94 fps material (ie, every frame comes from a different point in time) you can either decimate down to 29.97 fps or interlace to 59.94 fields per second. To create interlaced frames add the following after the resize and addborders: AssumeTFF() SeparateFields() SelectEvery(4,0,3) Weave() Encode that as interlaced TFF MPEG2 for DVD.

sambat posted 2008 Sep 02 15:02

Many thanks. Dgindex said the the source was NTSC, progressive. I stepped through the frames in Virtualdub and it looked like each frame was different. I added your changes as indicated, but to get HCgui to accept it, I had to add the last line(?). The .m2v output from HCgui is interlaced and 39 seconds as opposed to the 54 seconds from DGI - is this normal - do I have to adjust the audio to fit? # -= AviSynth v2.5.7.0 script by FitCD v1.2.8 =- DirectShowSource("C:\Documents and Settings\Superuser\Desktop\dgi\court.demuxed.m2v") BilinearResize(720,368,0,1,1280,718) AddBorders(0,56,0,56) AssumeTFF() SeparateFields() SelectEvery(4,0,3) Weave() #Trim(0,2393).FadeOut(150) ConvertToYv12()

jagabo posted 2008 Sep 02 18:08

HCEnc requires YV12 input so ConvertToYV12() is necessary if the source isn't already YV12. An M2V source would normally be YV12 though. And since the video is interlaced at that point you should add the interlaced argument: DirectShowSource("C:\Documents and Settings\Superuser\Desktop\dgi\court.demuxed.m2v") BilinearResize(720,368,0,1,1280,718) AddBorders(0,56,0,56) AssumeTFF() SeparateFields() SelectEvery(4,0,3) Weave() ConvertToYv12(interlaced=true) The length of the video should not have changed in the above script. The audio doesn't need adjusting. Try adding Info() at the end of the script and opening it with VirtualDub or a media player. See what it says... If you'd rather have 30 fps progressive (playback will not be as smooth): DirectShowSource("C:\Documents and Settings\Superuser\Desktop\dgi\court.demuxed.m2v") SelectEven() BilinearResize(720,368,0,1,1280,718) AddBorders(0,56,0,56) ConvertToYv12()

sambat posted 2008 Sep 03 16:30

Thankfully, I resolved the length of video problem by using the .d2v file output by Dgindex instead of the .m2v file. I probably should have been doing that from the beginning. The last question is about the top line on some broadcasts as shown in the image. This line is visible on the encoded mpeg and is quite distracting. I assume it carries some information and I wonder if FitCD has a setting that takes care of it, or does it require modification of the script. As a point of interest , if it does carry information for the receiver is the information still usable once the original is encoded to another format. Much obliged for your helpful replies.

jagabo posted 2008 Sep 03 17:42

Yes, you should always use the D2V file and MPEG2Source() along with DgIndex. Regarding the junk at the top of the frame: just crop it away. FitCD has the option to crop any of the four edges of the source.

Login/Register to our forum to be able to post here.