Forum Replies Created

  • Bob Richardson

    January 23, 2016 at 5:59 pm in reply to: NEW TO PREMIERE- Will A DOC Survive Natively

    When editing multicam, it has been my experience that files in some interframe codecs (such as AVCHD), the longer the clip length, the slower the editor is for basic operations such as starting playback as you get further and further into the multicam clip.

    For clips of less than 15 minutes in length, this does not seem to present a problem. But if you have interviews that have gone on for 45 minutes or an hour or two, consider transcoding just those, for improved editing performance.

    If you use a camera which resets clip numbering from zero (such as AVCHD cameras again), which can generate a lot of clips on your drive with the same filename (but in different folders), Premiere has been known to lose track and sometimes associate the wrong audio with the wrong video, and it’s difficult but not impossible to recover from that when it happens. If you have such footage, it is best to use a utility to transcode AND name your files uniquely.

    I’m currently cutting a doc for a client, with 20+ interviews which will be 30-40 minutes in finished length. Have been working on it for about 8 months. There are other bugs which I’ve encountered but I won’t mention them here as they seem to have been addressed in the latest versions of Premiere CC.

  • Thanks for the tips… My footage isn’t usually “big boy”, in this case AVCHD from Panasonic/Lumix GH2s. (I suspect that interframe-compressed formats such as H264, AVCHD, XDCAM and even .VOB are at the root of many problems in Premiere, actually.)

  • I’ve produced a post comparing various shadow/highlight methods and alternatives:
    https://forums.creativecow.net/thread/3/968995

    Summary: Adobe please, please fix this, there isn’t a direct alternative, even from 3rd-party vendors.

  • Open the Title tool… keep a title around with a single text object on it. Arrange the Title window so its always open but out of the way. There is a color picker for various attributes. So even though you aren’t actually creating a useable title with this tool, you can use the color picker to find the values you need for your AE-based titles. Cumbersome, but at least you’re not switching apps.

  • Start by creating a multi-camera sequence with just the first file from each camera. Then, you can open this multi-camera sequence in the timeline (right-click on the sequence, then open in timeline), and you’ll see each camera as a separate track. You can then add additional clips to each track manually. There can even be gaps between clips (such as a camera where recording was stopped and started again later.)

    As for synchonization (lining up the clips on the timeline), this depends on your footage and the presence of 3rd-party tools such as pluraleyes. But if these multiple clips don’t actually drop any frames, you should be able to drag them back-to-back.

    A versatile thing about being able to edit within the multi-camera sequence, is that you can apply effects and color correction. But save that for last, as it can bog down processing and frame rates while you’re editing.

    But let’s take a step back: What camera are you using? Are you using the Media Browser to import the clips? The Media Browser is smart enough to combine multiple clips from a single recording into a single “clip” in your Project. But it needs to be a camera that Media Browser recognizes.

  • Bob Richardson

    January 14, 2013 at 10:11 pm in reply to: time line won’t play in Premier Pro CS6

    Well, I guess I “spoke” too soon. The playback problem has recurred and the save-project fix described above no longer works for me. I’m stuck. 🙁

  • Bob Richardson

    January 7, 2013 at 9:32 pm in reply to: time line won’t play in Premier Pro CS6

    Wow… After searching for days to fix this problem, and trying Adobe’s recommended file deletion procedure to no avail, I followed your advice and created a dummy project and saved it to a network drive, closed it, reloaded it, and presto: Playback capability was restored! I then loaded a large project that had stopped working and playback was fine. That’s a pretty subtle bug. I hope to not run into playback problems again but I’m grateful to this community (I’ve just joined formally now as a result) for delivering a workaround.

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