-
Why does Premiere suck so bad??
Why does premieres media encoder suck so bad? It is by far the worst flash encoder I’ve ever used. I have tweaked every setting possible, but unless you max out the bitrate, the thing looks like absolute crap. So many, many artifacts.
In camtasia, I can export the same video at a VASTLY lower bitrate and it comes out fine. The artifact are essentially non-existent.
Is there a way around this? Is this just me? Am I doomed to edit in premiere, wait the ages it takes to export as avi, wmv, etc.. then import into camtasia or flash just to convert it?
This is driving me insane.
-
26 Replies
-
Wish you luck, just hate seeing s….d Subject Titles like this all the time, no other way to professionally request assistance?
-
I’m taking the fox new approach. Hyperbolic title for views.
I tried a nice simple post about a month back, but that got me nothing.
Your post is as useful as my title.
-
Adobe’s problem is that the list a minimum system requirement that is for basic DV editing.
when editors try and use their program on inferior hardware and start messing with multiple stream or use HD content they run into problems everytime.
I edit on a dual quad-core xeon machine with 16GB of ram and a high end video card.
I never have had a crash that I can recall.
I also do not have other programs trhat are not compatible with Premiere on the same machine.
People love Final Cut and their Macs because final cut was made for the Mac. -
I have no problems with crashing. I edit on a Dual-core, 2.53GHz, 4 GB ram, mid-level video card.
I’m not editing HD content. I’m not doing giant projects. I’m editing a 640×480 video from a frame grabber.
My post is about Adobe Media Encoder’s non-ability to export as a FLV. Crashing is not an issue.
-
What sort of Camtasia output are you editing and Flash encoding? File format? Bitrate? Project settings? Encode settings?
If you don’t start with good material you won’t end up with it.
And your original post title has nothing to do with Premiere, it has to do with Adobe Media Encoder.
-
Flv is no where near the best format out there. In fact many of us now us h.264 from Sorenson (so does Youtube).
As far as comparing Premiere’s output to Camtasia, are you comparing with an uncompressed output from Camtasia brought into Premiere. Recompressing a Camtasia export is going to get ugly.
Are we also talking about the same type of motion?
Remember, compressing screen capture is easy, there is usually very little motion on screen so all the encoder has to do is repeat most of the pixels on every frame to save space. When it comes to camera foorage and motion graphics, these days a minimum bitrate of 800-900 kb/s is becoming the norm for SD encoding.
Vince Becquiot
Kaptis Studios
San Francisco – Bay Area -
What sort of Camtasia output are you editing and Flash encoding? File format? Bitrate? Project settings? Encode settings?
If you don’t start with good material you won’t end up with it.
And your original post title has nothing to do with Premiere, it has to do with Adobe Media Encoder.
Camtasia capture settings: AVI, 24fps, Techsmith screen capture codec.
The recording from camtasia is great. Nice and crisp. I would describe this as decent source material.
Camtasia’s FLV encoding settings: 15fps, keyframe every 5 seconds, 13kbps. I have matched these exact settings with premiere and it looks absolutely like shit.
-
I guess I should clear up exactly how I’m comparing the two. The camtasia outputs the AVI. I don’t do anything else to the file. I can import it into premiere, then export it with AME to flash video, and it suddenly looks like crap. Or I can do the same thing with camtasias encoder and it looks just fine.
Same file. Same motion. That’s what’s confusing. I mean, they only change slides every few minutes, so it’s mostly just a static image the whole time.
I’d like to use the h.264 codec, but these are all being delivered through a flash projector file that is set up to load FLVs..
-
I’m not sure what process/encoder is used in Camtesia (there are many different encoders out there). But I’m sure it’s customized to take advantage of the low motion and sudden scene changes. Try really increasing the keyframes interval in your AME settings. 13 kb/s needs some drastic setting changes from standard type motion encoding.
Vince Becquiot
Kaptis Studios
San Francisco – Bay Area -
Here’s what it looks like after AME has touched it.
It doesn’t look as terrible as I’m describing in the picture, but all of those little distortions are pulsing around the image constantly. Which makes it look awful..
I feel like I’ve tweaked every setting possible, but I just cant get it be be even close to clear with out extreme setting which yield a giant file..
Reply to this Discussion! Login or Sign Up