Premiere CC Workflow Issues

[Steve Sherrick]

Not sure whether to categorize these as bugs or just different ways of doing things. Either way, they seem troubling. It could also be that I'm doing something wrong.

Problem #1
Deleting a clip from the browser/bin deletes that clip anywhere you have used it. So if you used it in your timeline there is now a black hole and no reference to the clip. I don't think there is any kind of warning that this will happen. That seems very dangerous.

Problem #2
Many of us use subclips. In Media Composer you can create a subclip cut it into your sequence, matchback to subclip, matchback to original master clip, find in bin, etc. In Premiere it seems that when you edit a subclip into your sequence you can matchback to what appears to be the subclip. However, if you extend the clip (go beyond subclip limits) it will no longer matchback to the subclip when you are parked over one of the extended frames. This happens with the option to go beyond subclip boundaries, so I don't think it's a preference thing.

Curious to hear if others are having issues like these and how you are addressing them. I actually really like the performance I'm getting in Premiere and even on an older machine playback is really good. But I get nervous when there are issues like the ones above because then I wonder what else will I come across that will burn me later in a project. I know Walter Murch is liking Premiere but he had mentioned there were a few things they were working with Adobe on solving. I wonder if these are things he was referring to.

 

[Aaron Nanto]

Hi Steve,

Problem #1 - this is expected behavior for any clip that you delete out of your project file, but it has always warned me first that the clip was being used in a timeline to make sure I really wanted to delete it. I've not tried this with the latest update, so maybe they changed it.....there are many bug regressions with the latest update (some big ones with audio that I'm having to work around).

Problem #2 - sorry, can't comment on that.

 

[Christoffer Glans]

This is why I never use Premiere, the subclips hell is stupid and tedious. Right now, I went on a job that wanted me to cut in Premiere and I asked how I can work with the subclips so that it could link back to the original files. The answer was "uhhh, well, you can't, uuuh, why do you want to do that?". Problem with Premiere is that it isn't made for editors with experience, it's made for those who edit once in a while, who don't need the fast workflow that Avid brings. It's a marketing illusion that Premiere is faster, it's not. Just because you can open a file directly in Premiere doesn't mean the entire editing workflow is faster, it just means that you can start faster. So the editing experience is a lot slower and the exports are a lot slower.

Premiere is often a producers choice when it comes to editing. Any editor with years and years of experience who work with editing on a daily basis will almost always choose Avid. As with choices for cameras, producers shouldn't be the ones choosing the equipment, ever. I don't even know why producers keep making technical choices, that should be left to the editor, the technical staff and the creatives.

 

[Alberto Guglielmi]

#1. I have the same thing as Aaron. A warning comes up about deleting a clip that is used in some timeline.
#2. Have you tried with nesting clip?