Log in

View Full Version : Prob w/ 352 x 240 Resolution MPEG2


SimonSez07
11th June 2002, 06:43
I have been trying to encode a 352 x 240 x 29.97 source into MPEG2 using CCE, but it seems to always give me some messed up 352 x 256 output.

My source is from an AVISynth Script and I have tried CCE 2.50 directly from the AVS file and also tried CCE 2.64 (trial only) with AVI wrapping using Link2. No matter what, it adds a black bar to the bottom and screws up the picture.

I thought it might have something to do with an MPEG2 stream requiring vertical resolution in incraments of 32, but I always heard multiples of 16 is acceptable.

Any ideas or solutions would be appreciated since this problem is very frustrating.


Thanks,

- Simon

SimonSez07
15th June 2002, 06:27
does someone at least know if there is any prob encoding this res on tmpg?

does anyone else even attempt to encode mpeg2 at this res??

auenf
15th June 2002, 11:52
352x240 res is fine for mpeg-2

but...

when you play that back, its going to be played back in 4:3 or 16:9 (depending on what you picked) rather than 1:1

which means its going to playback at 352x264 or 320x240, depending on what the mpeg-2 renderer decides on.

Enf...

Holomatrix
20th June 2002, 19:46
Will it play alright on DVD standalone? I was trying the same thing because I was using very low bitrate. What I got was a 1 inch green strip on the bottom of the video when played on the PC but never tried it on the DVD player, just thought the video is screwed up???
PowerDVD and MediaPlayer showed he green line, WinDVD only played the Audio.

timekills
16th September 2002, 01:10
For NTSC, 352x240 is acceptable in either MPEG1 OR MPEG2 for DVD standard. I have encoded DVDs from DivX files where I have re-encoded at 320x240 in bothe MPEG1 and MPEG2 and then burned to DVD-RW and both play just fine in my stand alone player.

TMPEGEnc can encode in either MPEG1 or 2 at that resolution natively. CCE you have to resize prior of course (or use frame-serving of some sort with resizing) but it also works. Faster than TMPGEnc, but with perhaps more hassle.