Trim Tool FCP 7.0.3 Makes Audio Pop?

[Jerry Hofmann]

I’ve not seen this behavior at all, and about the only difference between my setup and yours is that my media is local and not being accessed through an XSan…

Jerry

Apple Certified Trainer, Producer, Writer, Director Editor, Gun for Hire and other things. I ski. My Blog: https://blogs.creativecow.net/Jerry-Hofmann

Current DVD:
https://store.creativecow.net/p/81/jerry_hofmanns_final_cut_system_setup

8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO2 with MAX – Cinema Displays I have a 22″ that I paid 4k for still working. G4 with Kona SD card, and SCSI card.

[Benjamin Byleen]

Thanks for the response.

Yeah I was kind of leaning against a glitchy tool / FCP version but had to ask. Currently I am looking into hardware causes.

Any other responses still welcome of course!

Thanks!

[Jerry Hofmann]

That’s a good point… I do hear pops if the media is an MP3 or other highly compressed file.

Jerry

Apple Certified Trainer, Producer, Writer, Director Editor, Gun for Hire and other things. I ski. My Blog: https://blogs.creativecow.net/Jerry-Hofmann

Current DVD:
https://store.creativecow.net/p/81/jerry_hofmanns_final_cut_system_setup

8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO2 with MAX – Cinema Displays I have a 22″ that I paid 4k for still working. G4 with Kona SD card, and SCSI card.

[Benjamin Byleen]

Thanks again for responding. Actually that was my first thought and I made sure that everything was 48khz.

I’m currently investigating the below error message and whether it is related or not. My rather unscientific thinking is that if I have a flaky RAM chip, the necessary overhead for the trim tool is not met. System profiler reports that the RAM is “OK” but I’ve heard (heresay of course) that’s not always 100% reliable. I’ve searched online for this error, but no posts that really relate to mine. Anyone seen these errors before and know specifically what they mean?

Nov 22 10:57:16 Final Cut Pro[45715]: Final Cut Pro(45715,0xde7500) malloc: *** mmap(size=268439552) failed (error code=12)\n*** error: can’t allocate region\n*** set a breakpoint in malloc_error_break to debug
Nov 22 10:57:16 [0x0-0x139139].com.apple.FinalCutPro[45715]: Final Cut Pro(45715,0xde7500) malloc: *** mmap(size=268439552) failed (error code=12)
Nov 22 10:57:16 [0x0-0x139139].com.apple.FinalCutPro[45715]: *** error: can’t allocate region
Nov 22 10:57:16 [0x0-0x139139].com.apple.FinalCutPro[45715]: *** set a breakpoint in malloc_error_break to debug

It seems somewhat implausible but I cannot ignore the error, so maybe going to try a few new sticks of RAM, and see whether it gets rid of the error and the audio problem.

Thanks again all!

Ben

[Andy Mees]

Just thinking out loud here, but if its popping whilst monitoring via the BMD card it might be an idea to test to see if the Mac’s built-in audio output presents the same issue and/or try without the BMD drivers installed. (Just in case there is some kind of driver conflict going on). And does the issue present on your system regardless of source and sequence settings, or are you finding it’s specific to the particular config you’re working with right now?

[Jerry Hofmann]

You can remove ram chips one at a time to see if the issue goes away before you buy more…

Jerry