Forum Replies Created

Page 11 of 14
  • Dustin Bowser

    July 28, 2011 at 6:24 am in reply to: Premiere Pro CS5.5 Interface Slowness

    The fact that you have 32GB of RAM worries me. I’ve only got 10GB and I figured that perhaps it was a lack of RAM issue, but clearly that’s not your problem.

    For me, this very subtle interface lag is enough to make Premiere unusable if I can’t get it worked out. Final Cut was just so much smoother it’s not even funny. I really want to love Premiere, I’m trying as hard as I can to give it a fair shake.

  • Dustin Bowser

    July 28, 2011 at 1:18 am in reply to: Playback stutter CS5

    I’m having the same problems here. Trying out CS5.5 after being with Final Cut for a few years. I’m a keyboard shortcut fanatic, so I’m able to move really fast in Final Cut because the user interface keeps up with me, but I’m finding that in Premiere I’m constantly waiting 1 second here and 2 seconds there every time I need to do something new. Same goes for playback, which is stuttery and my audio drops out as well. I’m constantly having go back to the start and hit play again, hoping that Premiere has caught up to me finally.

    My machine —

    OSX 10.5.8
    Dual Quadcore 2.8 GHZ
    10GB Ram
    Nivideo GeForce 8800 GT 512mb VRAM

    I was hoping I was going to love Premiere, all the new features really sounded awesome, but I’m finding the actual nitty gritty of editing very painful and frustrating.

  • Or if there was just a way to offset the start frame of a Proxy that was rendered out, then it would be possible to render out just the needed portion of a clip, and have the Proxy’s start frame be changed to the start frame of the Trimmed comp.

  • Ah yes, linking the path parameter with an expression is a really good start. That takes care of only needing to tweak one mask path. Now just wish there was any easy way to instance it without having to do a bunch of copy/pasting and then pickwhipping.

  • Yeah, not bad thought, but then it just punches a hole all the way through all layers to the bottom of your Comp, which makes it tough when you’re trying to bring together a bunch of different elements.

  • Sorry, that was meant to be Thanks!

  • Another gotcha I’m finding is — I’m used to the way Final Cut handles audio tracks, ie: 2 mono tracks to represent a stereo file. In Premiere there are both mono and stereo tracks. You can set the project to force mono for all tracks which is behavior similar to Final Cut, but I’m finding it frustrating when needing to apply an effect to a stereo clip and I’m forced to tweak 2 separate instances of the effect before I can hear what I’m doing. I have to tweak the left channel mono, and the right channel mono. Is there a better way to be going about this?

    Thanks?

  • Dustin Bowser

    July 27, 2011 at 2:26 am in reply to: Premiere Pro CS5.5 Interface Slowness

    It’s set to 3GB.

  • Dustin Bowser

    July 20, 2011 at 6:52 pm in reply to: Go to Next/Previous Edit Point not working

    But apparently it’s just a bug with using the Up and Down arrow keys, because I just tried with Page Up and Page Down and was able to get it to work…

  • Dustin Bowser

    July 20, 2011 at 6:50 pm in reply to: Go to Next/Previous Edit Point not working

    Yeah, I’ve made sure that the track is active. For some reason it still doesn’t want to work for me for some reason.

Page 11 of 14

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