
- Completely clean pluraleyes 4 windows mp4#
- Completely clean pluraleyes 4 windows driver#
- Completely clean pluraleyes 4 windows manual#
- Completely clean pluraleyes 4 windows pro#
I even went so far as to duplicate the Vegas Project, convert the clips to Cineform and replace the clips in the project - yet, the audio drift still exists - but doesn't in Premiere Pro.
Completely clean pluraleyes 4 windows pro#
I have the same audio drift issue when rendering via Vegas2Handbrake - Premiere Pro becomes more advantageous due to just rendering out and not exhibiting any audio drift.

Completely clean pluraleyes 4 windows mp4#
… remuxing the resultung MP4 after Here's the thing, Why should I have to do extra steps to fix what appears to be a glaring issue within Vegas Pro - at that point, Vegas loses any speed and efficiency in editing because of having to go outside the app to fix what it does during Rendering. … disabling GPU rendering for MainConcept AVC output. I'm hoping I'm wrong and this was just the odd project that just didn't go quite right (Had issues rendering with Vegas2Handbrake with this project as well)

I'm willing to give Vegas another try but I'm now having consider it not reliable for all projects and TBH, will feel the need to defer back to Premiere Pro CS6 - even though it's not near as fluid an editing experience as Vegas Pro. And other projects I've edited previously the past month or so haven't have the audio drift issue - same workflow as listed initially. Vegas is a great NLE - when it works right. That's my point exactly about Premiere - it rendered out the footage perfectly and no sync issues.I'm a little irritated that Vegas seems to let me down at the worst times. aggravating since Premier has no problem. It's a VBR codec (Variable Bit Rate) which means detail level in the video stream prior to encoding is the main trigger for bitrate distribution.

Completely clean pluraleyes 4 windows manual#
The main problem with the H.264 codec in the OM-D is the ridiculously low average bitrate, the manual says 20Mbit/s but it sort of averages out at 17Mbit at best and sometimes considerably lower. I did find something that indicates the codec for the EM5 footage is VBR. but I found it as a reason for sync going bad on render.
Completely clean pluraleyes 4 windows driver#
I think we've run into this mostly with those folks capturing game video (using VBR) and complaining that renders are out of sync.Īnother possible is if you are not using an ASIO driver for your sound. I think Vegas can have problems rendering VBR and keeping it in sync. Use "mediainfo" to see if this particular footage is VBR. Just when I was getting use to editing in Vegas Pro. The out of sync appears to be 2-5 frames difference from what I can tell.Īgain, same project exported from VP13 and imported into PPro CS6 renders audio and video in sync perfectly using both AME and direct render from PPro CS6. Video files themselves are in sync outside of any NLE. Using the direct render as in Vegas Pro - used the Mainconcept option:Īll footage shot on my Olympus EM5 recording dual sync audio and using PluralEyes 3.5 to replace scratch audio with clean audio before importing into Vegas Pro. Render template using Vegas2Handbrake (Latest version of HB) is 29.97, 1080p, 12,000kbps Mono audio rendering to h264 mp4. Project properties, render template, source material and so on inclusive of a snap shot of your timeline. To find a solution to your specific problem we would need more information. Sorry Cliff, I work exclusively with Vegas and never ever did I have an issue like yours. I thought I could finally settle on Vegas Pro - instead I'm back to where I was a couple of months ago for my post production tools.

If anyone has a suggestion in finding a fix for the out of sync video and audio issue I'd appreciate it. Now to investigate Media Composer First in addition to using PPro as it seems stability and reliability supersede ease of use. Now I'm back to PPro CS6 as the random crashes in Vegas along with this have me questioning my decision of committing fully to Vegas. If I were using nothing but Vegas, I'd be S.O.L. I exported out the Vegas project to a Premiere Pro project file, opened the project in PPro CS6, rendered out the videos and low and behold - perfect video & audio sync. I rendered out a video using both the Vegas2Handbrake script and directly rendered using one of the internet MP4 templates - in all instances, the video and audio are out of sync - even though on the timeline everything is in sync. Once again, at one of those critical points in meeting a deadline, Vegas has shown a side of itself again that has kept me away from using it for several years.
