Find the right screen size

[Impulsive Otaku]

When I am exporting out of Adobe P. is it best to use the default screen size of the footage. Or is there a AMV default I should go with?? BTW its a kenshin TV series AMV, so wide screen does not come into play here.

Thanks

[Voices_Of_Ryan]

When I am exporting out of Adobe P. is it best to use the default screen size of the footage. Or is there a AMV default I should go with?? BTW its a kenshin TV series AMV, so wide screen does not come into play here.

Thanks

720 x 480 for 4:3.
If you're using Top interlaced footage go into the Keyframes and Processing (it's something else in pro?) and change to Top Frame.

If you need any help PM me on here and I'll give you my aim.

[trythil]

When I am exporting out of Adobe P. is it best to use the default screen size of the footage. Or is there a AMV default I should go with?? BTW its a kenshin TV series AMV, so wide screen does not come into play here.

Thanks

Export at the same parameters that you used to import the footage, and do the aspect ratio correction in other programs, such as AVISynth.

[Voices_Of_Ryan]

When I am exporting out of Adobe P. is it best to use the default screen size of the footage. Or is there a AMV default I should go with?? BTW its a kenshin TV series AMV, so wide screen does not come into play here.

Thanks

Export at the same parameters that you used to import the footage, and do the aspect ratio correction in other programs, such as AVISynth.

SetMemoryMax(32)
avisource("D:\Videotitlenamehere.avi")
ConvertToYUY2()
Telecide(order=1)
Decimate(cycle=5)
BicubicResize(352,240)

That should work fine for a Kenshin L-Q Xvid.

[Voices_Of_Ryan]

When I am exporting out of Adobe P. is it best to use the default screen size of the footage. Or is there a AMV default I should go with?? BTW its a kenshin TV series AMV, so wide screen does not come into play here.

Thanks

Export at the same parameters that you used to import the footage, and do the aspect ratio correction in other programs, such as AVISynth.

SetMemoryMax(32)
avisource("D:\Videotitlenamehere.avi")
ConvertToYUY2()
Telecide(order=1)
Decimate(cycle=5)
BicubicResize(352,240)

That should work fine for a Kenshin L-Q Xvid.

Ignore the MM ><.

[trythil]

When I am exporting out of Adobe P. is it best to use the default screen size of the footage. Or is there a AMV default I should go with?? BTW its a kenshin TV series AMV, so wide screen does not come into play here.

Thanks

Export at the same parameters that you used to import the footage, and do the aspect ratio correction in other programs, such as AVISynth.

SetMemoryMax(32)
avisource("D:\Videotitlenamehere.avi")
ConvertToYUY2()
Telecide(order=1)
Decimate(cycle=5)
BicubicResize(352,240)

That should work fine for a Kenshin L-Q Xvid.

- YUY2 conversion is not needed. It should be YV12 if you're going to XviD.

- 352x240 is wrong without cropping. You need to at the very least crop 8 from left and right if it hasn't already been done. It's also a spectacularly low resolution these days.

- Post-editing inverse telecine is possible, but is also rather dumb if you've had access to AVISynth throughout the entire editing process. It is also a bad idea to use Telecide strictly for deinterlacing. Use something dedicated like Kerneldeint (if you have consistent field order) or TomsMoComp instead.

[Voices_Of_Ryan]

When I am exporting out of Adobe P. is it best to use the default screen size of the footage. Or is there a AMV default I should go with?? BTW its a kenshin TV series AMV, so wide screen does not come into play here.

Thanks

Export at the same parameters that you used to import the footage, and do the aspect ratio correction in other programs, such as AVISynth.

SetMemoryMax(32)
avisource("D:\Videotitlenamehere.avi")
ConvertToYUY2()
Telecide(order=1)
Decimate(cycle=5)
BicubicResize(352,240)

That should work fine for a Kenshin L-Q Xvid.

- YUY2 conversion is not needed. It should be YV12 if you're going to XviD.

- 352x240 is wrong without cropping. You need to at the very least crop 8 from left and right if it hasn't already been done. It's also a spectacularly low resolution these days.

- Post-editing inverse telecine is possible, but is also rather dumb if you've had access to AVISynth throughout the entire editing process. It is also a bad idea to use Telecide strictly for deinterlacing. Use something dedicated like Kerneldeint (if you have consistent field order) o
r TomsMoComp instead.

Number 1, I misslabled the YUY2 tag in my haste to Post, thanks for the correction.

Number 2, I've always used 352x240 for mpeg1s but I've never actually tried it with xvid. Once again. Sorry about that : O

Number 3, I find that Pre-Editing Inverse is a problem with slower computers (much like mine) so I usually do it post just for the fact that I like it when I have to go threw a huge amount of Scripts at one time in premiere.

[Impulsive Otaku]

Thanks everyone, This solves my problem quite well, quite well indeed.

[Voices_Of_Ryan]

Thanks everyone, This solves my problem quite well, quite well indeed.

Wish I coulda been more help though.

Thanks Tythil for correcting my 2 errors ^_^;; perhaps I'll read over the guide again in the next few days.

[trythil]

Number 3, I find that Pre-Editing Inverse is a problem with slower computers (much like mine) so I usually do it post just for the fact that I like it when I have to go threw a huge amount of Scripts at one time in premiere.

Use it. Premiere can handle it; Premiere Pro (< 1.5, anyway) can also do it. It is far less demanding on CPUs during the editing process.

Post-production inverse telecine has many flaws. You are working at a rate higher than the original (i.e. non-telecined) rate of the footage; thus, when you attempt to restore that original rate, all of your work done at the higher rate will be distorted. Obvious results of this are jerky pans (if you do pans in the editing process), jerky keyframing (as that is all time-based), and...well, just about anything time-based.

If you don't do any of that, fine, but in general it's a rather bad idea and it's not really worth recommending, especially with the sort of tools available these days.