Anyways, Turkey Day is coming up again, and there’s demand to do another time lapse recording of the event. Therefore I had some incentive to fix the problem once and for all.

isightcapture was failing to acquire an image and was simply returning the following:
Fylgia:Desktop james$ isightcapture out.jpg
Bus error


When I ran EyeSight fortunately I got the option to generate an error report and here’s where I saw something interesting:

i.e. there’s some QuickTime component installed that I vaguely remember installing but can’t remember why:
Fylgia:Desktop james$ locate CamCam
/Library/QuickTime/CamCamX5.component
/Library/QuickTime/CamCamX5.component/Contents
/Library/QuickTime/CamCamX5.component/Contents/Info.plist
/Library/QuickTime/CamCamX5.component/Contents/MacOS
/Library/QuickTime/CamCamX5.component/Contents/MacOS/CamCamX5
/Library/QuickTime/CamCamX5.component/Contents/Resources
/Library/QuickTime/CamCamX5.component/Contents/Resources/CamCamX5.icns
/Library/QuickTime/CamCamX5.component/Contents/Resources/CamCamX5.rsrc
/Library/QuickTime/CamCamX5.component/Contents/Resources/English.lproj
/Library/QuickTime/CamCamX5.component/Contents/Resources/English.lproj/InfoPlist.strings
/Library/Receipts/boms/com.b-l-a-c-k-o-p.CamCamX5.pkg.bom


CamCamX is a 6×2 video mixer. Use it to create LIVE TV webcasts using only your Mac, iSight, pictures and movie files. Since CamCamX virtualizes the webcam (iSight camera) in your Mac you can use all your favorite cam applications AT THE SAME TIME. CamCamX also makes non-Apple webcams iSight compatible (via emulation).

That definitely sounds like something that could be causing the problem, and sure enough, upon deleting the component isightcapture now ran but generated a new error:

Fylgia:Desktop james$ isightcapture -t png output.png
[000:000] Error(magiccammac.cc:265): MagicCam 0: MagicCamOpen: Not an allowed process!
[000:000] Error(magiccammac.cc:265): MagicCam 1: MagicCamOpen: Not an allowed process!


I figured it might be some other QuickTime component causing this error as well and noticed these in /Library/Quicktime/

MagicCam 0 and 1, Google Camera Adapter 0 and 1. I’m assuming these are part of the Google Voice and Video Chat functionality I installed a couple of weeks back. Pulling them out of /Library/QuickTime made the error go away but since they don’t stop isightcapture from working I’m going to leave them installed.

For those of you who haven’t found these settings, select Window Settings… under the Terminal menu and then choose the Color menu option. Apple’s default is black text on a white background, rather like the default for most windows on the Mac since way back when. Personally, I’ve been using orange on black and green on black for nostalgic reasons since I first got my hands on OS X.

You can also modify the font and the look of the cursor/prompt from within the Display menu option. Again, for nostalgic reasons, I like a blinking block. But, hey, the first computer I ever used on a regular basis was an Apple ][ with a green screen monitor and the first computer I ever owned had an amber monitor. Happy days

Anywho, my conversation with Scott reminded me of a couple of things I’ve found in addition to playing around with the above that may benefit/interest some of you. The first is the use of the “-G” argument when using the “ls” command line directory listing command. This argument will colourise the output making it visually obvious which items are files, folders, executable, hidden, etc. If you like this, make either a new command like “lc” using an alias, or simply replace the existing ls command with an alias to ls -G and add to your .bash_profile or .profile file. Something like alias ls="ls -G" will do the trick.

Another useful thing to have is Mike Solomon’s TerminalColors. It adds a new pane to the Window Settings… menu option mentioned above that allows you to tweak the colours used by the terminal for displaying text. Some colours (like blue) are almost impossible to read clearly over black.

My final thought on colour which may be interesting to some of you is a thing I saw on Mac OS X hints a while back. An anonymous poster submitted a script for tcsh that randomly changes the background and text colour of each new Terminal window as they are created. An interesting conversation follows with many of other ideas about how this can be done more efficiently. I haven’t used any of that stuff myself – but it occurs to me that it might be useful to have a script that automatically changes the tint of a Terminal window when something is being executed as root or privileges have been elevated using sudo.