-
Audio won’t render out
I have a multi-cam sequence that is about 4 hours long, it was shot with several DSLRs and two audio recorders. So my milti-cam has six tracks of video (with a bunch of 12-20min clips in each track), two tracks of audio that extend the full length of the sequence and six corresponding tracks for the camera audio.
So, once the multi-cam was built and synced I placed it in a new sequence and chopped out all of the bad parts then drug each of the remaining clips, one-at-a-time, from the timeline to one of my bins (this was the only way that I could figure out how to make a sub-clip of a multi-cam).
Then, I built the show by pulling my multi-cam sub-clips into a new timeline, trimming and splicing everything up adding some stills, b-roll, titles and such.
At some point during this process, while I was playing the show there would be parts where the audio would cutout, if I stopped for a second then started again it would play fine…I didn’t think much of it until I got ready to render the show and the clips that gave me that problem didn’t render out.
So my question is: does anybody have any idea what would cause a particular audio clip to not render?
One thing to note is that I only have this issue with the audio in that giant multi-cam.
Another thing that is odd to me: when I send the sequence to AME and start the queue, I can see it process several audio files very quickly then it says “Rendering XMP”. I have to wait sometimes 30 to 45 min then it will rip through the video encoding very quickly.I first had this problem last week using Pr CS6, now I’ve tried it with Pr CC and there has been no improvement in regard to my audio issue.
My machine was built according to the DIY 9.5 specs by VideoGuys
Processor – Intel Core i7 3960X 3.3GHz
RAM – 32GB G.Skill Ripjaws
Boot Drive – Crucial M4 256GB SSD
OS – Windows 7 Professional 64-bit
GPU – Nvidia K5000Here’s their page: https://www.videoguys.com/guide/E/Videoguys+DIY9+Sneak+Peek+Its+Time+for+Sandy+Bridge+E/0xe9b142f408a2b03ab88144a434e88de7.aspx
Sorry, there were no replies found.