Forum Replies Created

Page 2 of 6
  • Cliff Stephenson

    May 14, 2012 at 2:41 pm in reply to: Pluggins for Premiere Pro

    So I just downloaded and installed the Sapphire Edge trial based on the recommendation (I’m running CS6 on a Mac Pro with Lion and (pardon me while I yell)…

    THEIR TRANSITIONS DON’T WORK AS F******G TRANSITIONS!!!! This is the same problem as Boris, the same problem as Core Melt, the same problem as (seemingly) all of them!!! The transitions actually appear as filters and are applied to the entire clip?!? Now https://www.filmimpact.net/ has a batch of great transitions that dare to work as actual transitions, but unfortunately, his are free. I’m much more satisfied paying $1500-$2000 and have transitions that are totally useless in my bin unless I somehow rig them to appear as transitions. I watched a YouTube tutorial on how to do a 12 frame swish pan that took 4 minutes to do.

    And the idea that an Adobe guy told you to do straight editing in Premiere and move to AE for transitions and such is stupid. Part of the editing process is using transitions from shot to shot to complete the edit. I shouldn’t have to fire up After Effects to do a simple 6 frame blur dissolve. I also might have to (I know it sounds crazy) adjust an edit after I’ve placed a transition on. Yeah, let me fire up AE to create a whole new comp so that my lens flare wipe (which can be easily applied/created in Final Cut 7 for god knows how many years) is even possible.

    Please tell me I’m missing something because the plug in situation with Premiere is the dumbest, most useless I’ve seen in all of my years editing. It’s one of the things that makes me most irritated with Premiere, but I don’t know if blame lies with Adobe or with the third party guys.

  • Cliff Stephenson

    May 8, 2012 at 5:18 pm in reply to: CS6: Thank you Adobe!

    I agree. I’m in the middle of a rather large project as well and after weighing the pros and cons (my “brain said no, don’t it” but my heart knew the advances in CS6 could really help me out) I decided to switch over, mid-project. After getting things put back in their place and editing all night, I’m really impressed with a lot of what’s new. Hover Scrubbing is a godsend when dealing with a lot of b-roll. There’s so many little hidden tweaks (like additional options if you have to adjust audio gain) that it’s fun editing again. I love that during thumbnails, it’ll tell you which clips you’ve already used in a sequence and how many times… just cool things like that.

  • Cliff Stephenson

    May 8, 2012 at 4:40 pm in reply to: Should I uninstall CS5.5?

    Good point, I can’t tell you how many times I needed someone to open a final cut project (I was always on the newest version) on their machine and they would have to upgrade before they could work with me.

  • Cliff Stephenson

    May 8, 2012 at 4:06 pm in reply to: Should I uninstall CS5.5?

    I have both installed right now and what seems to happen is that the first time you try to open a project from 5.5, it actually creates a new project (without changing the original) and you can place that in a separate cs6 folder. So it seems like each version actually creates their own specific projects. Don’t know if you can open a CS6 project in 5.5 (don’t know why you’d want to though).

  • Hey Alex,
    My response actually wasn’t directed at you. But, unfortunately, hitting reply just puts the actual reply at the very bottom and I wasn’t smart enough to quote the text from Tom I was actually responding to.

    Sorry for the confusion.

    Cliff

  • Greg did say that he just made one and was just coming here to find out what others thought. So he sounds a step ahead. I don’t think ALSO reposting it here is a bad thing for two reasons…
    A) We know that Adobe also frequents these forums and interacts, so they’ll also see it here (-you can’t present a good idea too many times).
    and
    B) I think Greg is trying to drum up additional user support for the idea so that Adobe might see a lot of enthusiasm for it in the community and perhaps weight it differently than a single submission. (which is probably how most of their new features make it to the head of the line).

    While I love Adobe and the fact that they have a place to submit features, let’s be honest… there’s no protocols in place that tell us whether or not a feature request was read and understood, much less considered and implemented. I’m sure they get a blizzard of suggestions time and again and most of them are probably less than gold. How many good or even great requests occasionally fall through the cracks created by the bad ones? If Greg makes a great request through the proper channels (and one that many others like and agree would be a great addition to PPro), I think having those users actually weigh in on it publicly might actually improve it’s chances of getting implemented.

  • I’m totally with you. I’ve been thinking about submitting a feature request that’s very, very similar. When I’m doing minor color correction in the timeline (with Fast Color Corrector or something similar), it would be great to have the option to apply that filter to all the clips from the same source in that timeline. So if I brighten a shot or increase saturation in an interview shot, dropping the filter on the first clip would automatically apply it to all in the cut. Or give users the option to apply filters in the source window, so that they get ‘filtered’ down the shots in the timeline. They could include a toggle in the filter to apply globally on/off so you could “lock” or “unlock” an effect to other clips in the edit.

    Totally agree.

  • I hope so. I have to completely edit in an adobe desktop timeline in order to get the effects of my CUDA card and then near the end copy and paste THE ENTIRE timeline into a new Blackmagic timeline so I can actually do some accurate color correction. The way that Premiere has interacted with both Blackmagic and AJA has been fairly underwhelming.

  • I do often break up my timelines. The 90 minute doc I just delivered was actually broken up into 6 different, shorter timelines with the longest section being about 25 minutes. I crashed often.

  • And I would agree with that except I’m not running on an iMac. I’m running a Mac Pro 4,1 dual quad-core 2.93GHz with 48 gigs of RAM and the same quadro 4000 card you’re running. My system should therefore be unstoppable, but it often is.

Page 2 of 6

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy