Trying new stuff

[Joseph W. bourke]

Expertise as an editor in no way qualifies you to throw stones at something you don’t fully understand – nor does two glasses of Merlot. But everyone’s entitled to an opinion – however, an informed opinion is always preferable to putting something down as “clunky” when you haven’t mastered it.

I’ve been a professional musician for many years (as well as a designer and motion graphics artist), and I’ve found that the people with the strongest opinions against a type of music, are those who’ve never played a lick of that style. I’ve heard “Jazz sucks!” a million times by people who don’t know more than five chords, and woulnd’t know a two-five progression if they tripped over it. If you haven’t mastered it, don’t knock it.

Joe Bourke
Owner/Creative Director
Bourke Media
http://www.bourkemedia.com

[Gary Huff]

[Lance Bachelder] “As far as the extra clicks, the only way to show this would be to do a live side by side with other NLE’s to show just how clunky Premiere 6 is.”

I don’t think you’d need to go that far…you just kind of, you know, be more specific.

“Clunky” means nothing to me. In the other thread about FCPXs shortcomings, I very explicitly listed issues I had encountered while editing a complete project in it, things that I am actively utilizing in Premiere with the project I’m currently working on. I find Premiere CS6 to be nearly elegant in usage and incredibly powerful. I love the addition of the trim commands that closely mimic the controls in FCP where you can trim in and out points on the timeline for instance. I use those all the time. I love the fact that it works with practically every single piece of footage I could possibly use.

I do agree that the Sequence creation is clunky in needing to pick the overall codec that is in use, and that’s something I’m sure Adobe will end up address. Ultimately, I think it’s a not the end all breaking point, just something that could use spiffing up. I love the addition of the adjustment layer, love Dynamic Link. I love the ~ key command that maximizes whatever portion of the interface your mouse is currently hovered over. I love how the key-framing works.

I love the fact that if I use a 3rd party plugin, that it won’t cause green frames in the video.

I love the fact that I can do psuedo-After Effects-lite compositions using embedded sequences with Photoshop layers and keyframes.

So many specific things I have just mentioned. Always helps if you talk in specifics, and not in just generalizations because then people have a hard time whether you have a point, or are just talking shit.

[Dave Jenkins]

I think one of the big issues is that it’s been referenced as like FCP7. So I went into CS6 with that state of mind. I couldn’t change the audio tracks and had to copy everything out of that timeline into another timeline with the correct audio set up. That said to me, I don’t need to go backwards, which is what CS6 feels like to me. An FCP 6.5 equivalent. Sure I don’t know Premiere but if I have to learn a new way I’m going with a system that is a fresh start with new ideas and workflows. FCP X is far from perfect but it has a new fresh direction. I just started play the guitar and bought my first guitar. It didn’t feel right so I went and found one that fit me. It’s all person style, use what fits you!

Dajen Productions, Santa Barbara, CA
MacPro Two 2.66GHz Quad Core – AJA Kona LHe
FCS 3 OS X 10.7.4
FCP X, Adobe CS6, Logic Pro, Squeeze, Filemaker

[Gary Huff]

[Dave Jenkins] “So I went into CS6 with that state of mind. I couldn’t change the audio tracks and had to copy everything out of that timeline into another timeline with the correct audio set up.”

Could you explain this issue more?

[Chris Harlan]

[Lance Bachelder] “As far as the extra clicks, the only way to show this would be to do a live side by side with other NLE’s to show just how clunky Premiere 6 is. This doesn’t mean it can’t be used for any type of show and for those who’ve never used another NLE day in and day out in a high-pressure, broadcast or feature film type environment, they’d never know what I’m talking about and never know there are issues.
“

Sorry, Lance. You just aren’t bothering to dig in deep enough. Which is fine; no one says you have to. But you shouldn’t be throwing stones either. Premiere’s sync indicators aren’t as transparent as Avid or FCP 7, but are quite usable for anyone who knows what they are doing. Just open up the info window, turn it into a small column and then you have available all timecode in every track. There’s no color-coding like in FCP7, but its very useable for monitoring sync. If you were bazitching about this from the POV of an Avid or FCP7 editor, where the sync break is spelled out in the timeline with exact frame info, I might feel your pain; but in the same breath that you are whizzing on Pr, you are lauding X which doesn’t allow any sync monitoring–after breaking clips apart–at all. So, I’m happy to see you back and hanging around, but, yes–I cry foul.

[Erik Lindahl]

For me the best thing about PrPro CS6 is the “curroupt my project” feature not so many are talking about. When this happens and there is zero support from Adobes end it rings very bad from my PoV.

Regarding “many clicks” I’ve found the same in PrPro vs FCP7. I don’t have the concrete examples in front of me but I was struck by it on a project last fall.

[Chris Harlan]

[Erik Lindahl] “For me the best thing about PrPro CS6 is the “curroupt my project” feature not so many are talking about. When this happens and there is zero support from Adobes end it rings very bad from my PoV. “

Spoken like someone with little experience and lots to say.

[Erik Lindahl]

And you are adding what your comment? I don’t have much more to say really. Reading Walters article this is a common issue evedently.

Am ruling out CS6? No, it could potentially be the king of NLE’s in my domain as we are heavy AE-users. But my few initial tries with the application have been rough. Versions prior to CS6 where slow and / or not usable for proper video monitoring (again, somewhat of a “known issue”) and now in CS6 things seem solid – great or amazing even – until we ran into a very nasty case of project courpotion.

And the “more clicks” is something I experienced also. For example I think FCP7 assumes a few things the editor wants that PrPro asks. This seems to be the case when setting i/o’s the viewer and timeline for edits.

[Steve Connor]

I am very much enjoying the irony in his thread

Steve Connor
‘It’s just my opinion, with an occasional fact thrown in for good measure”

[Chris Harlan]

I wasn’t trying to add anything. I was just responding to the snark in your comment. I have never worked on an NLE that hasn’t had some sort of file corruption issue from time to time. I know that you got bit, and I’m sympathetic to that, as I’m sympathetic to people who have been bitten by various iterations of X and FCS. I understand that you didn’t get the feedback you wanted from Adobe, but that’s pretty much the case with anything you are not paying support for. Certainly, that is true with Apple.