-
PR CS6 and AF100: Audio woe oh-oh.
Long-time FCP user, I’ve been test-flighting CS6 to move on over soon.
First big bug bite so far. I’m working with AF100 footage 1080p24 w/ LPCM audio from two mics, originals from the heirarchified folder on a local hard drive. It’s a large ~1hr long clip.
When I first imported the footage, originally I couldn’t get PR to preview any audio. I opened the file in another program (finder) to make sure it was there, and there was indeed audio.
Went back into PR, and mow my audio plays (?). OK, whatever, swell, throw it on the timeline… but now it only comes in as one audio channel that I can’t split out into two mono channels. Groan.
That’s ok, I figure I can work with that… search for a few seconds, find the option to “normalize audio clip” to -4.5db, and do so…
…that’s when it all went really wrong.
PR has now completely messed up the audio track in that project (simple trim edit of one ~1hr clip). Audio is completely and utterly out of sync, almost as if it’s been “condensed,” or something… just randomly jumps around within the audio track. I can’t get it to undo whatever it has done short of trashing the project file and starting over. Thinking it might be a preview problem, I rendered out a small 1min clip from the video… that’s wound up completely farked audio-wise.
So… does working with raw camera audio always suck this terribly in CS, or is this new?
Is there a simple and easy way to make it not suck so fiercely?
Hopefully so, because the advertised ability to flawlessly work with raw camera files was a big draw for me to potentially switch.
-
2 Replies
-
updates:
– Finally figured out clip->modify->audio channels. Only it more completely kills the audio (no audio at all on either channel now).
– Transcoded, trimmed, adjusted, and compressed in FCP while waiting for some sort of answer or resolution. Not throwing that away any time soon.
– Adobe doesn’t appear to offer any help to people only running trials (even if they’re seriously considering a purchase of their flagship product – or at least were)
RESOLUTION: trashed everything CS6 related. Rebooted, disk util’d, and reinstalled. Now it all works fine.
Guess my install was hosed in some manner.
-
Hey Kevin –
I don’t know how you’ve tried contacting Adobe, but 6pm on a sunday night may not be the best time to get responses. They are on these forums as well as Adobe’s forums and you can ususally rouse someone if you give them a day or so and no user helps you out.
I would submit to you that the reason you couldn’t see the audio at first is because it was conforming. Check out this thread for more on that: https://forums.creativecow.net/readpost/3/919222. Because it was an hour long file, it takes a little while. Sounds like you were able to get it to play.
It seems like you figured out the “Breakout to Mono” command to split tracks that are imported as Stereo. I am not sure if there’s anything wrong with your install, but it definitely should be able to work with compressed audio fine – that’s what it’s doing when it “conforms” the audio – it’s converting audio to an uncompressed format, so it should be no different if it’s compressed audio or just raw WAV data.
I have seen instances where, if I mess with the original file at the same time that Premiere is conforming it, it will wind up skipping in the same way you described. It sounds like you might have been doing that. And because the erroneous conform data is generated, Premiere relies on that instead of the original audio file. I’ve discovered that I can trick Premiere to not do this by 1. Taking audio file offline, 2. navigating to original file location and append a _1 to filename or something, and 3. RE-linking media. It thinks it’s a new version, so it re-conforms audio.
This is a bit of a pain, but you’re dealing with a little bit of an odd problem… I’ve only seen it twice in the last 3-4 years of the Adobe “conform” methodology.
Reply to this Discussion! Login or Sign Up