Forum Replies Created

Page 11 of 18
  • Jp Pelc

    August 11, 2014 at 2:23 pm in reply to: We are no longer using Pr CC 2014

    I am going to stop using CC 2014 as well. I haven’t experienced your specific issue as I haven’t worked with P2 footage in years, but several other serious issues in Premiere + AE 2014. Back to CC until they are fixed

  • Jp Pelc

    August 11, 2014 at 2:07 pm in reply to: Premiere CC 2014 laggy

    Few things:

    – Just like Jim, I experience all the same problems that you do IF I have AE opened with a dynamically linked project. When I quit AE all the problems go away.

    – Check your GPU acceleration, and whether it is set to on or off, try the other way. GPU acceleration is much faster but whenever there is a strange issue it is often the source.

    – Don’t edit too much H.264. While Premiere can handle it, it’s an inter-frame codec, meaning most frames are referencing another frame 4 or 5 away. This adds to the processing needs. While it’s probably too late for this project, future projects with a decent amount of DSLR footage should have it converted to ProRes 422 before going into Premiere.

    – In my experience, CC 2014 is pretty buggy, and for future projects you might consider going back to CC until some of these issues are ironed out.

  • Jp Pelc

    August 11, 2014 at 1:57 pm in reply to: Audio Glitch in Premiere Pro

    I experienced the same problems very recently with Premiere CC 2014 on OSX 10.8.5. I have never really solved it, all I know is that it happens sometimes and sometimes it doesn’t. Either way, it hasn’t shown up on the final render

  • Jp Pelc

    August 11, 2014 at 1:54 pm in reply to: On all the time or off every night?

    I guess like Steve said this is more of a gut feeling then based on scientific research, but I don’t see how it can be a beneficial to leave all machines running nonstop for months at a time. I shut down every night unless I have an overnight render happening

  • Jp Pelc

    August 5, 2014 at 6:16 pm in reply to: Sharknado 2 edited on…..(drumroll) Premiere Pro CC

    Not sure if this is a win for Adobe or not…

  • Jp Pelc

    August 1, 2014 at 4:49 pm in reply to: Endless development

    I’ll second this. (Minus the 10 years part)

  • Jp Pelc

    August 1, 2014 at 1:29 pm in reply to: “Error Compiling Movie. Unknown Error”

    The file should be much smaller than 2GB, close to 150 MB as it’s a short video for web. I tried exporting to desktop as well as shortening the file name (as I seem to have had a few issues in the past exporting with long file names). No luck.

  • What are your export settings? H.264 has a lot of sound sync issues. Usually it is just a frame or two, sometimes it is a bit more. That is a problem as the C300 shoots to h.264 (side rant: it’s ridiculous that a camera at that price shoots to such a terrible raw codec, but obviously you are stuck with it).

    So basically the raw footage could be going in and out of sync by a few frames within your timelines, then if you export to h.264 it can be swinging back and forth in either direction by even more frames.

  • I’m not sure of any way to rename the actual file via Premiere or Bridge. I’ve never used Prelude (no real need as all our projects are only handled by one or two editors anyway) but it seems like it’s the way to go. If it’s the best tool for the job, why the aversion?

  • For vignetting you can install CI Vignette (free)

    https://www.creativeimpatience.com/vignette/

Page 11 of 18

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