Resize Suggestion for AVI-DVD Encode

[Soopafresh]

I could use some help on this one as I don't do AVI-DVD encodes that often, especially with small source files.

I have a source AVI which is 576x432 square pixels, 1:30 length, originally PAL source and still at 25fps. I'd like to encode to NTSC 720x480, 4:3 A/R. Suggestions on resize and/or letterbox?

Thanks.

[guns1inger]

It basically is 1.33 (4:3). FitCD gives it as 1.337 when converted from 1:1 to NTSC, so you may have very narrow pillarboxing in the overscan region.

The basic FitCD is

DirectShowSource("pathtoavi")
LanczosResize(704,480,0,0,576,431)
AddBorders(8,0,8,0)
AssumeFPS(23.976, true)
#Trim(0,-1).FadeOut(150)
ConvertToYUY2() # For VirtualDub or CCE

Personally, I would drop the Assumefps statement, encode it as 25 fps, then apply pulldown with DGPulldown to get to 29.970 fps for playback.

[j4gg3rr]

704 x 480 YUK!

Full screen, no overscan, don't loose a drop.

# 4:3 encoding NTSC
AviSource("D:\Temp\test576.avi", false) #no audio
Lanczos4Resize(720,480)
AssumeFPS(23.976,1,False) #do not audio sync no audio

# 4:3 encoding PAL
AviSource("D:\Temp\test576.avi", false)
Lanczos4Resize(720,576)

Its 4:3 display source therefore will be converted to fullscreen x 4:3 aspect regardless of format.

16:9 would be:

# 16:9 encoding NTSC
AviSource("D:\Temp\2.avi", false)
Lanczos4Resize(536,480)
AddBorders(92,0,92,0) #Pilars
AssumeFPS(23.976,1,False)

# 16:9 encoding PAL
AviSource("D:\Temp\2.avi", false)
Lanczos4Resize(536,576)
AddBorders(92,0,92,0) #Pilars

AssumeFPS is stretching the video runtime a few minute longer!
But no frames get skipped, blended or whatever.
Just do the same to audio if encoding seperately.

You may like to keep it 23.976 Progressive no pulldown MPEG-2 with TMPGEnc/Procoder.

[guns1inger]

Regardless of resolution being 704 or 720 x 480, encode at 25 fps and use pulldown, simply because you already have 25 fps source..

[Soopafresh]

Thanks, gents. 25fps w/ DGpulldown and 704x480 it is...

[FulciLives]

These two threads might be helpful:

https://forum.videohelp.com/topic296341.html

https://forum.videohelp.com/topic316333.html

And yes I would also use DGPulldown to make it NTSC instead of trying to adjust it from 25fps to 23.976fps when encoding.

- John "FulciLives" Coleman

[Alex_ander]

AssumeFPS is stretching the video runtime a few minute longer!
But no frames get skipped, blended or whatever.
Just do the same to audio if encoding seperately.

You may like to keep it 23.976 Progressive no pulldown MPEG-2 with TMPGEnc/Procoder.

It is only useful for restoration original audio pitch/video length in case PAL was slowed down from film (not PAL TV) source. Anyway, you can't use progressive 23.976 for watching DVD without telecining at playback that inserts interlaced frames using repeated fields. DGPuldown 25=>29.97 is better in case the video originates from PAL footage (you keep undistorted audio) and you also don't drop (or blend) frames unless you force it in DGPulldown for some lip-synch reason.

[j4gg3rr]

I must admit I've never tried a 23.976 no pulldown progressive DVD till just now.
Rather I always convert them to 25 in AVISynth with AssumeFPS.

But I've done quite a few 23.976 no pulldown progressive SVCD's that look better than 3:2 pulldown 29.97 at playback SVCD's. And thought the same could be done with DVD.

I just tried to author a 23.976 MPEG to DVD and saw it would only let me do it as internal progressive 23.976 > 29.97 at playback unlike the SVCD's I've done in the past.

[FulciLives]

I just tried to author a 23.976 MPEG to DVD and saw it would only let me do it as internal progressive 23.976 > 29.97 at playback unlike the SVCD's I've done in the past.

You can encode a MPEG-2 DVD spec file to a "straight" 23.976fps without 3:2 pulldown so that you can use DGPulldown to apply a 23.976fps ---> 25fps pulldown in order to make it PAL (remember to resize during the encoding to a PAL compliant DVD size like 720x576 etc.)

However if you intend to make a compliant NTSC DVD then you need to apply 3:2 pulldown.

- John "FulciLives" Coleman

[j4gg3rr]

Just tried that 23.976 > 25 with DGPulldown out of curiosity,
Whilst motion seems relatively smooth, the 2 per 12 frames that have the pulldown applied look to be sharper brighter images than the untouched frames.
This gave my test footage a slightly noticable pulsing effect especially on edges 2 times per second.

The sample I use has a timecode present in the top right corner and the numbers within were even more destinctly different to the point of irratating.

I think it better to keep all the frames as is and shrink the timeline 4% with AssumeFPS for video and Besweet's -ota( -r 23976 25000 ) for audio. Works for me anyway!

EDIT:
Procoder also does it like AssumeFPS instead of using pulldown for these close Film/Pal frame rates.
449 frames 23.976 fps @ 18.727 seconds runtime input = 449 frames 25 fps @ 17.960 seconds runtime output.

[Midzuki]

If your standalone player is capable to do real-time PAL2NTSC conversion, and if you have the time to as well, you might want to try this:

AddBorders(96, 72, 96, 72)
BilinearResize(720, 576)

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