2 Replies Latest reply: May 18, 2011 3:10 AM by Kevenly
soulartist Level 1 Level 1 (5 points)
I discovered this repeating error in the system log.

I did see an archived post that said this was issue with an old Final Cut Studio plug-in that it would not load on Intel mac. I don't have Final Cut Studio.

I do have final cut express hd installed, and thought maybe the error producing plug-in is there, but I can't locate it.


Feb 25 17:39:37 eden-maxwells-imac-3 System Preferences[1920]: Error loading /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: dlopen(/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHD Audio, 262): no suitable image found. Did find:\n /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: no matching architecture in universal wrapper

Feb 25 17:39:37 eden-maxwells-imac-3 System Preferences[1920]: Cannot find function pointer NewPlugIn for factory C5A4CE5B-0BB8-11D8-9D75-0003939615B6 in CFBundle/CFPlugIn 0x20039d060 </Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin> (bundle, not loaded)

iMac 24" 3.06 GHz, Mac OS X (10.6.6), 4 GB
  • 1. Re: DVCPROHDAudio.plugin error / system log
    soulartist Level 1 Level 1 (5 points)
    I should add this:

    The not loading HAL/DVCPROHDAudio plug-in happens with FCE not running.

    I did find a few HAL/DVCPROHDVideo (no audio) files in Quicktime. Maybe the HAL/DVCPROHDAudio is hiding in a package file.
  • 2. Re: DVCPROHDAudio.plugin error / system log
    Kevenly Level 1 Level 1 (25 points)

    I have been having this problem for years.  Searching around the net you find many instances of people reporting the endless crashing of that plugin even with no audio apps running.  Apple has failed to ever respond to any of it, and to this day my completely up-to-date current system still has this issue.  Even when I wipe the hard drive, install Snow Leopard fresh, then Logic Studio, fully update everything, the issue is there.  There is absolutely nothing that is known to resolve it that I can find anywhere.  The only solution is removing the plugin from Library.  I zip it and stash it in my documents folder awaiting the day Apple bothers to acknowledge their Pro App users and do something about this issue that's been going on since at least 2009 with every OS X released since.