PAL to NTSC and NTSC to PAL

[Wilbert]

@a2j,

Try this version: http://www.geocities.com/wilbertdijkhof/SmoothDeinterlacer_25.zip

[a2j]

Thank you - it did work!

[spanky123]

Thanks

I got a bit of a problem. I've just tried converting a 23.97 fps avi to 25fps PAL MPEG-2 with Procoder and the file length is different to the original by a few minutes

The output framerate is 25fps as I wanted and is dvd-compliant mpeg-2 pal but it seems like procoder has just used only the frames it had from the source, rather than blending them and adding an extra frame every second (I hope I've explained that clear)

How do I fix this in Procoder ? Is there an option anywhere ?

I know how to do it in the avisynth script with CCE, but I wanna do it in Procoder

[scharfis_brain]

procoders default setting is to speed up or slow down.

blending or duping whole frames will look terrible...

is you don't want to alter speed I recommend using dgpulldown to force a 23.976fps 720x576 MPEG file to 25 fps. fields getting duplicated during playback, then.

[manono]

How do I fix this in Procoder ?

If you're sure of what you said (the frame count is the same, just speeded up), then you can "reset" the speed by running the M2V through DGPulldown set for 23.976->25.000 as scharfi suggested. That way, the original speed will be retained, the video length will be the same as the original, you can use the same untouched audio (if already DVD compliant), you won't have a nasty blended or jerky playing result (not as jerky as having dupe frames inserted anyway), and it should be a nice and compliant PAL M2V, ready for authoring.

This has already been explained in your Videohelp.com thread. What, you didn't believe us? Needed a second opinion?

http://forum.videohelp.com/viewtopic.php?t=315461

[spanky123]

Thanks. All clear with the DGPulldown I think

This has already been explained in your Videohelp.com thread. What, you didn't believe us? Needed a second opinion?

http://forum.videohelp.com/viewtopic.php?t=315461

Well actually, if you check the times of my posts, you'll see that I made this post before the VideoHelp one.

:)

:thanks:

[manono]

Not the way I read them, you didn't. But that's OK, as long as you got it sorted out.

[spanky123]

Not the way I read them, you didn't. But that's OK, as long as you got it sorted out.

You might have the timezone set wrong in either videohelp or here.

Anyways. .. Yeah I think it's all sorted. I just gotta try a few
Thanks for the help

[Maiko Herajin]

I have a question about the normal standards conversion script that has been given on here, maybe someone can explain it to me.

I have this script currently running (in my case going from PAL to NTSC)


MPEG2Source("whatever.d2v", iPP=True)
AssumeTFF()

securebob()
lanczos4resize(width, 480)
convertFPS(59.94)
separatefields().selectevery(4,0,3).weave()

Now from what I gather, what we're doing is smart bobing the video so it's 50p, in order to preserve any "fast motion" that might occur. Then we resize it, change the FPS, and then... split and double the video again, weaving together every fourth and eigth frame?

What I'm not sure I understand is why the deinterlacing step is nessisary in the first place. Why wouldn't code like this work?


separateFields()
lanczos4resize(width, 240)
ConvertFPS(59.94)
selectevery(2,0,1).weave()

Since the first line basically creates a 720x288x50p, which is later weaved back, becoming half of a 720x480x29.97i video, I don't see where any loss of detail would occur. I tested the script on a DVD rip, and sure enough, I got a video that was 720x480x29.97. I didn't actually process the video, however, because I figured you guys were all smarter than me. :D

So what process does the first script preserve / improve over the second (much faster) script? Am I misunderstanding something in the process here?

[foxyshadis]

Well, the weave is wrong (should be 4,0,3 unless you want selecteven), but on trickier topics:

The pixels aren't centered. The resize assumes that the top and bottom are absolute, but when you weave that assumption is invalid. That means a picture that was perfectly stable before, will have a slight up-and-down jitter after resizing. (A correct subpixel crop might fix that.) There's also a little bleed between lines within fields that wasn't there before, that could cause combing in static areas where none was before.

Although that's the theory, I don't find it very visible. Give it a try and see if you notice.

[Brent212]

Why is it that in Xesdeeni's conversion scripts (here (http://www.geocities.com/xesdeeni2001/StandardsConversion/#PALVideoDVD2NTSCDVD)), the ConvertToRGB() doesn't contain "interlaced=true"? From what I've read, this parameter defaults to false, which seems bad because I thought the video is interlaced at the end of the script. I'm mainly looking at the "PAL video DVD (25i FPS) --> NTSC DVD (29i FPS)" script, since I want to try using that as input to TMPGEnc.

[Xesdeeni]

Probably because he screwed up and doesn't use TMPGEnc enough to have noticed himself. ;-)

Xesdeeni

[kOoL tHuG]

But how to convert Pal (25) Menus to
NTSC (29.97) huh frnds?

[cweb]

[QUOTE=kOoL tHuG;1119647]But how to convert Pal (25) Menus to
NTSC (29.97) huh frnds?[/QUOTE
Recreate a similar or different menu..