Friday, October 2, 2009

What Model Mac Are You On?

If you're troubleshooting a Mac and aren't sure what exact model it is...so you don't know what firmware this or that needs...there's an easy way to find out not only the model designation but the type of CPU as well.

Fire up the Terminal (From the Finder hit Command + Shift + U, then T, then Command + O) and type in:

sysctl -a hw

Then hit Return.

You'll see fun info like:

hw.activecpu: 2
hw.physicalcpu: 2
hw.physicalcpu_max: 2
hw.logicalcpu: 2
hw.logicalcpu_max: 2
hw.cputype: 7
hw.cpusubtype: 4
hw.cpu64bit_capable: 1
hw.availcpu = 2
hw.machine = i386

but most importantly:

hw.model = Macmini2,1

If you want to see the exact CPU type, type in:

sysctl -a

and hit Return then look for something like:

machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz

QuickTimeMPEG2 Component vs Snow Leopard



If you install Snow Leopard and have the QuickTime Mpeg2 component installed, Snow Leopard will likely delete it. So, before you install Snow Leopard back this file up:

/System/Library/QuickTime/QuickTimeMPEG2.component

If you have already installed Snow Leopard and are now missing this file there are three things you can do to get it back:

01) Go to your Time Machine backup and restore it.

02) Head over to Apple and see if you can download it again if you bought it there under your account in Downloadables.

03) If you initially got it via Final Cut Studio then pop your FCS Install disc back in and then in the Finder hit Command + Shift + G (for Go to Folder...) and head to /Volumes/Final Cut Studio/Installer/Packages. Look for QuickTimeMPEG2.pkg and install it.

And this is curious, if you Right Click on the QuickTimeMPEG2 Component in Snow Leopard and choose Open With... you'll see the odd option KoreanIM as the default. If you try to open it with KoreanIM you'll be greeted with "Hangul cannot open files of this type."

Fun stuff.

Thursday, October 1, 2009

Final Cut Pro 7 Professional Formats and Workflows



If you haven't yet grabbed a copy of Apple's 132 page Final Cut Pro 7 Professional Formats and Workflows PDF, you should. There is a mountain of useful information in it.

Quicktime Player Launcher preventing always "Open With" QuickTime Player 7

Try this in Snow Leopard:

01) Get Info on a typical .mov file.
02) Set "Open With" to QuickTime Player 7. (which will be in your utilities folder...)
03) Hit "Change All".
04) Watch the Open With pulldown magically change to QuickTime Player Launcher...which will launch QuickTime Player (X)...sigh.

What is QuickTime Player Launcher? It's an application INSIDE the QuickTime Player 7 app. Right Click on it so Show Package Contents to see it. Then if you want, do that again on QuickTime Player Launcher itself.

What does it do? I have no idea other than seemingly prevent a Snow Leopard user from opening their movie files in something other than QuickTime Player (aka QuickTime X). Seems a little heavy-handed to me coming from Apple.

Here is a thread about it:
Setting .mov files to play in QuickTime Player 7



There is a workaround but I have no idea how "safe" it is.

01) Right-Click on QuickTime Player 7 in your Utilities folder and Show Package Contents
02) Goto Contents>Resources and locate "QuickTime Player Launcher".
03) Right-Click on it and select Compress "QuickTime Player Launcher". The resultant .zip file may appear on your desktop because you probably don't have Write permissions to this folder. Just drag it into the folder and Authenticate when it asks you to.
04) Drag (or highlight and Command + Delete) the original QuickTime Player Launcher to the trash. Authenticate if needed.
05) Empty the trash. (Command + Shift + Option + Delete)

Now, Get Info on a .mov (or whichever) file and tell it to Open With QuickTime Player 7 and Change All and then all of those files types should (so far for me) open with QT7.

The only issue you may see are some messed up QT icons in the Finder, either blank or the generic Unix app icon. Possibly because the OS thinks QT now has an unregistered extension.

I'll update this post if any weirdness happens.