Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Native… Are you sure it’s native?

  • Native… Are you sure it’s native?

    Posted by Jon Frost on April 3, 2012 at 1:14 am

    I’m in the midst of re-editing a project shot on a Canon 7D and audio recorded on an SD 788T-SSD digital recorder.

    For all the praise about Native editing… seems like PPro CS5.5.2 is sneaking all sorts of extra files into the workflow…. at the bottom right of the screen and adding MBs of data on my HDD.

    It wants to “Conform” H.264 files and create “Audio Peak” Files when the project is set up as 1080p24 with 48K 24-bit multitrack BWAV files from the Sound Devices recorder. All this takes a bunch of time “in the background”???

    The project and timeline are both set to 1920 x 1080p24…

    When I import the video files into a Bin called Video Files; and import the audio files into a Bin called Audio Files, the software all of a sudden starts trying to write all sorts of extra files… What gives?

    Is there some kind of Rendering going on that I wasn’t aware of?

    Seems like this is a waste of time since I am going to use PluralEyes to replace the camera audio with my pristine multitrack files.

    I guess I could eat a bunch of bad food and set the files to Conform while I read the a paper in the lew.

    If anyone has an answer I’f love a PM…
    Thanks,

    Jon Frost
    Florence, MA

    Jon Frost replied 14 years, 1 month ago 3 Members · 6 Replies
  • 6 Replies
  • Todd Kopriva

    April 3, 2012 at 2:35 am

    The first paragraph of this page explains what the conforming and indexing is doing:
    https://help.adobe.com/en_US/premierepro/cs/using/WSa41b87baf39dd9b0-4a7aee25125bce32690-8000.html

    ———————————————————————————————————
    Todd Kopriva, Adobe Systems Incorporated
    product manager, professional video software
    After Effects Help & Support
    Premiere Pro Help & Support
    ———————————————————————————————————

  • Jon Frost

    April 3, 2012 at 4:42 am

    Todd:

    Thanks,

    I found the proper link in the Help section after some false starts.

    I have been pulling my hair out with my first project in PPro. I certainly wasn’t aware when I bought it as a jump from FCP7, that there were going to be myriad files added to my HDD. Also not pleased with the slow down in performance. I have 32GB DIMM and 28GB dedicated to PPro. I spent 18minutes conforming and creating Peak files for the 81 audio files from my SD 788T recorder.

    Is there a better way to deal with these files in PPro?

    Also notice again after many attempts, that PluralEyes doesn’t seem to be working with PPro CS 5.5.2. I have the current version of PluralEyes and I didn’t have any trouble in FCP7.

    9 clips with associated audio files placed on the timeline in a new sequence. Select All and Export as FCP XML. Save the project. Exports as XML… with a strange report generated. Open PluralEyes and tell it to Open my XML file… Sequence1 with Level Audio, Try Real Hard and Multiprocessing enabled. Press Sync and it runs through the files. When I go back to my timeline, the first file isn’t even close to synced.

    I know you’re going to tell me to contact Singular Software and I will in the morning… but I have to wonder if this is a bug…

    At this point FCP7 outperforms PPro CS5.5.2 even with FCP7s need to transcode to ProRes 422LT!!!!!!!!!!

    Hope you have some answers.

    Jon Frost

  • Mike Molenda

    April 3, 2012 at 1:49 pm

    PluralEyes generally does a decent job, but it’s far from fool-proof. I’ve infrequently had issues with it syncing even clips where a clapper was used. (Fortunately that was easy to fix the “old-fashioned” way)

    How is the first file not synced? Is it off by a few seconds or frames, or is the audio clip completely not matched up with the video clip? If it’s the latter, PluralEyes couldn’t successfully find any sync points. Did the other eight clips sync up fine?

    If you’re roughly lining up the audio and video beforehand, it may be worth checking the “Clips are Chronological” option as well.

    PluralEyes for Premiere was built for CS4 and earlier, and hasn’t been updated to work seamlessly with CS5 or 5.5. Which is why you have to work off an XML instead of the project file. If you’re just syncing second-system audio to video, and not syncing multiple camera angles, you could also consider DualEyes, which is NLE-agnostic.

    30-day demos of DualEyes are available for free. And don’t quote me on this, but I believe Singular Software will exchange any of their products for any of their other products of equal or lesser value for free if you do it within a few months of your initial purchase.

  • Jon Frost

    April 3, 2012 at 3:00 pm

    Mike:

    Thank for the insight… will look at DualEyes. It would have been nice to let buyers know that Pluraleyes is not yet ported for PPro 5.5.2 yet.

    I think the issue was not Importing the Sync XML file after running Pluraleyes… No one is perfect.

    Thanks again,

    Jon

  • Mike Molenda

    April 4, 2012 at 12:49 am

    Technically, PluralEyes DOES work with CS5 and 5.5, but you have to use the XML workaround.

    But should you really have to deal with two separate XMLs just to sync up a couple shots? It is kind of a letdown after working with the seamless roundtripping between PE and FCP.

    And out of curiosity, how much is PrPro writing to your drive? In my experience, excluding renders, the files used to conform are usually only around 0.1% of the size of the total amount of footage I bring into the project.

  • Jon Frost

    April 4, 2012 at 1:43 am

    DualEyes works nicely on most of my files… Too bad it won’t save the
    new synced files to a new folder rather than placing them back in the
    folder they came from… duplicating most of the files…

    Going on a RED EPIC Cluster tomorrow… waiting to see what the DIT
    plans are… Glad I am bringing my MacPro with R3D Data Manager for
    all those GBs of files.

    Jon
    – Show quoted text –

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