[Emily Maysilles]

Thank you so much for your reply David.

You are most likely right about the pulldown pattern getting messed up. I can say for certainty that the cuts were not made on the A frame because I myself was the idiot editor. I cut the scene over a year ago when I barely had a grasp on what A frames and pulldown cadences meant. Now that I’m older and wiser, I’m definitely kicking myself.

Unfortunately I do not have access to the dailies anymore without more trouble than this is probably worth. Thankfully there is no professional pressure to deliver this scene. I was going to use it for showcase purposes, but I think I may reconsider.

Looks like I may have to cut my losses, learn a lesson or two, and move forward.

[Emily Maysilles]

In our case there was no sample rate or bit rate mismatch, so the only solution we could find was trashing the caches, including the Thumbnail Cache, which I don’t think I included on my list above.

[Emily Maysilles]

Hello! I know this is an old thread, but I was dealing with this same phantom audio pop problem today and found a brilliant solution on another forum that I thought I’d pass along.

Try quitting FCP and trashing some of your caches. I trashed the waveform cache, audio render files, and also the render files just for kicks, and ta-da! No more pops! It might

Trashing databases and render files proved to be a useful daily activity when working in Avid (I worked in MC 2.8, not exactly the best version ever). This is the first time I’ve ever had to worry about it in FCP, but I guess no NLE is perfect.