[Dale Mcclelland]

Sorry, Ann. I missed the link you posted and was focused on your sentence about dolby not being included in the trial. I see now that your link provides the same helpful instructions that Chris posted. I apologize, and appreciate your effort to help.

[Dale Mcclelland]

Chris, thank you! Renaming the media cache folders worked. I now get audio.

Unfortunately my 7-day trial period ends today or tomorrow so there won’t be much time to test.

[Dale Mcclelland]

Thanks, Ann. The Dobly codec was not included at installation time, but when I first added an older clip containing Dobly 5.1 audio to the timeline, it prompted me to download and install the codec, which I did. So I get audio for those clips.

It is my more recent non-Dolby, stereo AC-3 and AAC clips that don’t get audio and appear not to have the required codec installed.

I’m trying to determine if the trial is supposed to have those codecs.

[Dale Mcclelland]

Dave, I thought someone here just might happen to know if there are audio limitations for the trial version – perhaps someone who recently trialed it. I asked in the official Adobe Premiere Pro forum a few days ago and no one replied.

I agree, 7 days is much too short to evaluate something as deep and complex as PPro. My trial is up in a day or two. Given the inability to get audio, and 7 days not being enough to check the software out properly, I think I will stay with Sony Vegas Pro 13 for now.

[Dale Mcclelland]

I don’t know the answers to your questions, but if you don’t get an answer here in the Creative Cow Vegas forum, Creative Cow also has a Boris FX forum. Boris FX employees check-in frequently there to answer questions and provide help.

[Dale Mcclelland]

Thanks, James. I have now submitted the support form.

[Dale Mcclelland]

Thanks again Jon (didn’t realize that you work for Boris.) Your scrubbing suggestion definitely helped because I could scrub slowly enough to keep the video from advancing faster than the FX could track.

But then I discovered the real problem. I was invoking Vegas’s “Build RAM Preview” incorrectly. I was using CNTL-B, then clicking Play, which played the video at full real-time speed (and wasn’t really building a RAM preview because SHIFT-B is the correct command is SHIFT-B, not CNTL-B). Tracking at real-time speed caused the playback to get too far ahead of the tracking and resulted in the error message.

Once I discovered how to invoke “Build RAM Preview” correctly, I found that the RAM preview proceeds much slower than real-time, and is slow enough for the tracking to keep up. I no longer get the error.

So it turns out that it was my lack of understanding of how to use a Vegas feature that was the problem. The key to my being able to figure it out was your explanation that the error occurs when playback advances faster than the tracking can keep up with was. Thanks for explaining that. Understanding what was happening was a big help.

I now plan to purchase a license for the Match Move Unit (or maybe the entire BCC Complete).

[Dale Mcclelland]

Jon, thanks for the reply. The clips I have tried are the full master clip in the timeline.

I moved the 12.0 folder out of the parent folder while Vegas was closed as you suggested (to a different hard drive in fact), but still get the error part way into the tracking on the fly. With the Look Ahead slider at the maximum of 100 frames, I can typically get 175 to 250 frames into the clip before the error message pops up.
I can do what the error message suggests and rewind to the xxx frame, clear render cache, at start tracking again from that point. Usually that completes the tracking with out error on a 6-8 second clip.

That’s not too bad a process when rewinding only once, but I am concerned about trying to track a longer clip. It could become time-consuming to do several iterations of the “rewind to frame xxx and track from there” process. I don’t think I will buy the product if I can’t resolve this problem.

Unless you have some other suggestions, I will contact Boris tech support about the problem. Hopefully they will try to help even though I am using the trial version.

I appreciate your suggestions.

Dale

[Dale Mcclelland]

Terry, if by “not recognize the .mov files” you mean they don’t even show up in the Vegas Explorer tab, I had that very problem today with build 583. I still have VP11 installed, so I checked it and it recognized the same .mov files with no problem. So I uninstalled VP12 583 and then re-installed it (still build 583). After the re-installation, .mov files show up in the Explorer tab and can be placed on the timeline.

I’m not sure whether un-installing and re-installing build 583 will work for you since the problem occurred immediately after installing it . (I have had 583 installed for a while and something may have gotten corrupted.) But it might be worth trying since it only takes a few minutes.

[Dale Mcclelland]

If you mean they don’t appear in the “Render As” dialog, you can check to see if “Favorites Only” or “Match Project Settings” are check-marked under “Output Format” in that dialog. I wouldn’t think these would be selected by default on a new installation, but it might be worth checking.