A Look at Premiere Elements 10

Adobe sent a free copy of their brand new Premiere Elements 10 video editor for a review, and I took up on the challenge to see what’s new. Premiere Elements and Vegas Platinum are undoubtedly the best two sub-$100 consumer-based video editing suites that could actually deliver Pro features when someone uses them to their full extend. They both can do 24p, time stretching, burn DVDs and AVCHDs, deal with color correction etc.

For the 10th version, Adobe added some additional color correction plugins: Auto Tone and Vibrance, and a three-way color corrector. You can independently adjust color in highlights, shadows, and midtones, while the “auto tone” plugin is actually pretty accurate, even if fully automatic.

Another major feature is 64bit support, but this only works on Windows 7 (Vista/XP won’t work with the 64bit version). There’s also “AVCHD exporting” now, which lets you export M2T or MP4 files with customization support. That’s the only exporting option I found that had acceptable parameters to tweak (e.g. VBR support), and use for personal viewing/YouTube/Vimeo. I put together an exporting tutorial here.

Other new features include AVCHD burning (burned on DVD discs) in addition to plain DVD and Blu-Ray burning, automatic Facebook and Youtube exporting (which unfortunately exports in the wrong frame rate and doesn’t let you edit it), you can tag photos using your Facebook Friends list, turn photos into movies, and photo tagging. And of course, even more kits DVD templates & multimedia files for use in your video.

The app seemed more stable than the previous version, but it took a good while to load. The “auto-analyzer” feature Adobe added supposedly for photos-only is super-slow though even when no pictures exist on the project bin, and it’s best to be turned off. Also, the app is not particularly “smart”. It loads effects on clips all by itself by default (e.g. motion, opacity etc), and this has a speed repercussion. On a slower PC for example, this was the difference between super-smooth and dropping-frames on 1080/60i HDV footage. The playback speed also dropped to the floor even if I changed no options on an active plugin (e.g. leave Three-Way Color Corrector loaded as-is without changes, but active). There’s definitely room for improvement on that front.

Additionally, Adobe added DV PF24 pulldown removal support, but not HDV one. I tried to enable the “DV 24p pulldown removal” option on a PF24 Canon HF11 clip, but the checkbox wouldn’t become enabled. Honestly, adding DV pulldown removal but not HDV/AVCHD one, is pretty lame in this day and age. Not to mention that in some dialogs, the app would change my typed 23.976 to 23.98, which could force resample, and enable ghosting.

Features missing is the Mercury Engine, as found on CS5.5, that could make h.264 playback even faster. There’s also no way to tweak the project settings as you can do with Vegas. For example, there is no AVCHD 1080/24p option with 5.1 audio setting. The user is forced to use the dSLR 1080/24p preset, and lose his 5.1 sound settings! Adobe is trying to make everything in the UI be a pre-selectable option, but some of these options simply need to be editable rather than just pre-selections. See, not all use cases are covered by pre-selections. Let the user decide how to mash-up the project properties to suit the myriad formats of camera footage that exist in the world.

And that’s the biggest pitfall of Premiere Elements, and I don’t personally see any way out of this unless its product manager really changes direction. Premiere Elements is more of a “here are 30 choices, select one” kind of app, while Vegas is more like “here are 10 choices, or customize it yourself” kind of app. It’s that difference that makes Vegas more suitable for both home & serious projects on a low budget, while PE remains suitable for home projects but not so much for more complex projects.

Between the two, Vegas is less clunky and confusing after the initial shock, while Premiere remains painful to use even after you learned its tricks. Then again PE now has a 64bit version and a Mac version. On the other hand, Vegas can do 3D editing and has more flexibility. At the very end, for family users it might just be a question of price at the very end. Checking prices today, Vegas Platinum 11 costs $63 on Amazon, while Premiere Elements costs $91.


Ivan wrote on October 13th, 2011 at 12:03 AM PST:

I have Premiere Elements 9 installed on my pc for 6 months now, and I have given a try several times, but… the key-word here seems to be pain: painfully slow, painfully cluttered, etc.
Vegas is fast and snappy and very tweakable. If they would invest in multi-language interfaces, like Elements does, Vegas would be king of the hill!

Charity Meinhart wrote on October 21st, 2011 at 10:49 PM PST:

I love Vegas more and more every day. Underrated, so underrated. :)

zima wrote on October 22nd, 2011 at 12:17 PM PST:

>it might just be a question of price at the very end. Checking prices today, Vegas Platinum 11 costs $63 on Amazon, while Premiere Elements costs $91.

It’s perhaps a bigger difference (even if not in most of the individual instances, but in the overall & long-term average) – it seems like PE might induce more people to, otherwise largely unnecessary, upgrades; brings somewhat greater potential for faster “obsolescence” & retirement of perfectly fine but “too slow” PCs.

A bit less likely when software tries to better acknowledge how PCs became generally “fast enough” a few years ago already, tries to not stand out negatively in this regard unless mostly where it’s necessary.

Comments are closed as this blog post is now archived.

Lines, paragraphs break automatically. HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

The URI to TrackBack this blog entry is this. And here is the RSS 2.0 for comments on this post.