Export Problems – PLZ HELP!!!

[Jason Harris]

while not an expert i would suggest using the ADVANCED settings in output

basically pick a flv setting in the prests close to what you want, then MANUALLY adjust video size, it should work, not sure what CS (3, 4) ? you are using but we also output in 720X480 and i found a nice preset,

if you have CS3 let me know!

Good luck

[Christy Nels]

I’m using CS4 (you can’t even export FLVs in previous Premiere Pro editions).

I’ve BEEN using the advanced settings. How else would I have created custom export settings? Not trying to be rude, but please read the original post.

I’ve tried every single preset and custom setting I possibly can think of, and nothing is taking away the vertical black bars unless I export at 655×480, but I want to export 720×480.

[Christy Nels]

This appears to be some sort of problem with Premiere Pro CS4’s programming. It’s incompetent. Use FCP, not Adobe. Adobe products are clearly inferior.

[Peter Berthet]

I laughed a little 🙂

~Peter Berthet
Sydney, Australia

[Brian Louis]

<>I cannot figure out for the life of my why I can’t export a 720×480 video as 720×480 without adding these stupid vertical black bars!<>
Because you are a 4:3 NTSC 720×480 which contains non-square pixels with a Pixel Aspect Ratio(PAR) of .89 horiz. exporting to FLV which uses square pixels, the encoder will conform it to 4:3 square pixels(AME FLV preset for this is usually 648×480), reason for the preset is that FLV is usually viewed on a computer screen, trying to view the resulting video on something that is expecting 720×480 .9, will result in black bars on the sides.

<>It’s incompetent. Use FCP, not Adobe. Adobe products are clearly inferior.<>
no comment necessary

[George Socka]

I have been exporting FLV out of CS3 for 2 years now, since I upgraded from ppro 1.0. Its right there in the dropdown at the top of AME where it says Adobe Flash Video. Get it? FLV?

If you are using 720×480 DV source, then you of course know that it is really just 640×480 (NTSC) with a .09 pixel aspect ratio. Flash is square pixels, so when 720×480 becomes square pixels, it is only 640. Plash plays on computers, which are all square pixels unless you have a badly set up monitor.

If you needed to convert your 720×480 DV to 720 square pixels you would need to create a custom project setting not using DV. Try QT, whatever. But round objects will become oval. Which some people think is weird.

Hope that pointing this out was not THAT rude, but whatever.

George Socka
BeachDigital
http://www.beachdigital.com

[Tim Kolb]

[Christy Nels] “This appears to be some sort of problem with Premiere Pro CS4’s programming. It’s incompetent. Use FCP, not Adobe. Adobe products are clearly inferior.”

Um…yes…helpful.

I’m glad someone finally mentioned that number 1: PPro has been exporting FLV in the encoder section before CS4…and number 2: the pixel shape makes a difference…

As far as FCP vs Adobe Premiere Pro…that’s a tired discussion. Anyone can pick a workflow where they can say one is better than the other, but I’ve certainly done fine with PPro.

Such remarks are not useful, and usually come from uninformed people.

If you can’t help, don’t type.

TimK,
Director, Consultant
Kolb Productions,

[Peter Berthet]

i could counter tim… but in this case i agree with you 🙂

i wish people would make a decent case when they bash the software … sigh

~Peter Berthet
Sydney, Australia

[Tim Kolb]

[Peter Berthet] “i wish people would make a decent case when they bash the software … sigh”

Well…making a decent case wasn’t so much my point. 🙂 I’ve posted on the FCP forum, but to try to be helpful (even on the “FCP vs PPro” threads). I haven’t joined any of the threads where FCP users are complaining about the disappointments they have with the newest version and said “Hey if you really need native editing for your EX cam…get Adobe.”

That is not helpful.

I think that you can make a case for either product by describing your workflow and then pointing out the particular features on one that give you an advantage over the other… But someone else can point out an advantage on the other side within their own workflow.

Neither program is worth forming a religion around…they’re tools. They do a number of things differently, both companies have had home runs and errors (check both forums…FCP users have issues too), and personal preference is a legitimate reason to choose one over the other, but those who have a different personal preference are not somehow ‘unprofessional’ or stupid.

I do find it amazing when I happen upon an informed user who has used both solutions to the point where they can be productive on either one… They usually have a preference, but I have yet to meet a person like this who would say that one is head and shoulders above the other. I’ve also never heard one of these people use words like “sucks” or call one app or the other unfit for professional use, etc.

(I’m not quite as fast in FCP as I am in PPro due to my own knowledge of FCP just not being equal to PPro, but I have worked in both.)

TimK,
Director, Consultant
Kolb Productions,

[Alan Lloyd]

That was useful. Thanks ever so much.