Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Vegas + Pluraleyes: There Must be a Better Way Than What I’m Doing!

  • Vegas + Pluraleyes: There Must be a Better Way Than What I’m Doing!

    Posted by Chris Mosner on August 23, 2012 at 11:16 am

    Hiya!

    I have been trying to sync several hours worth (and dozens of shots) using Pluraleyes. Initially, I tried just bringing in the shots individually, as I needed them, and selecting them for sync. However, it doesn’t seem like Pluraleyes works selectively: it always ends up completely screwing everything that was already on the timeline.

    So now I pulled EVERY shot – hours worth – to the timeline. Pluraleyes did a fair job of syncing it all… but I can’t look at more than a few shots before the FPS slows to an unwatchable crawl.

    I have 10 gigs dedicated to the RAM preview, in Vegas Pro 11, on an x64 machine. Using a Geforce 570 and a hexacore i7.

    Is there a better workflow? Is there actually some way to sync only one shot at a time without impacting the entire timeline?

    Thanks!!!

    Roger Bansemer replied 13 years, 11 months ago 3 Members · 5 Replies
  • 5 Replies
  • Dave Haynie

    August 23, 2012 at 12:05 pm

    I use Pluraleyes all the time, with 1-3 cameras and usually a secondard recorder or two. I sync everything up with PluralEyes, no problems. I usually have one field recorder as the “master”, having the whole event recorded, so it’s quite easy for Pluraleyes to find where everything else goes in relation to that master track.

    Having additional tracks on the timeline does not slow Vegas down by any measurable amount, at least not until you do something with them (eg, compositing them, adding FX, etc). Unless you’re used to looking at your whole video project via RAM preview, which you just might given your huge buffer.

    How much memory do you actually have in your system? Keep in mind that when you specify RAM preview, Vegas is allocating that memory whether you use it or not, and you can very easily starve your PC of resources needed for other things. Have you tried cutting that way, way back?

    If you really like working in tiny chunks, you can create a master project, sync everything, then break it up into sub-projects. When you’re done with the individual edits, drop those sub-projects into a new project and use them just as clips, to create the final edit.

    -Dave

  • Roger Bansemer

    August 23, 2012 at 1:43 pm

    If you highlight just the video you want to sync with PluralEyes, it will only sync that video and not try to sync everything on the timeline. But, it will sometimes, maybe always I can’t remember, put that audio at the very beginning of your project. If you have ripple on, that can mess everything up.

    What I do if I have several tracks I want to add to an already open project using PluralEyes is:
    Open a new project with the video I want synced. After it syncs them, I simply copy and paste them over to the project I’m working on. That way it doesn’t mess up any existing video on my project.

    Roger Bansemer

  • Chris Mosner

    August 23, 2012 at 9:33 pm

    Thanks, Dave, for the response. I do have 16g or RAM, but I will back that off. Sometimes, though, the answer can be quite simple: I rebooted my machine, and the sluggishness seems to have cleared up.

    I will try your advice regarding sub-projects. That makes a lot of sense!

    Once I have a shot synced with the proper audio, will grouping them be enough to hold them together? I’m not really sure what the limitations of “group” are?

    Thanks again!

  • Chris Mosner

    August 23, 2012 at 9:34 pm

    Thanks, Roger! I’m definitely going to try something along the lines of multiple projects. Do you have multiple projects open at once?

  • Roger Bansemer

    August 23, 2012 at 10:55 pm

    I often have multiple projects open at the same time for different reasons but mainly to copy and paste sections of one video to another.

    Roger Bansemer

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