iTunes Genius Mixes are nice. They group common music together in a playlist and the songs usually work well together. But there are problems. There is no easy way to tell exactly what songs you may get stuck with on a playlist. Plus, the Genius Mix list will keep playing, even if it has exhausted all songs available to it.
This means that users, especially those with smaller libraries, may hear the same songs pop up repeatedly, especially if they listen to the same Genius Mix for a long period. This hint is designed to better tailor playlists from Genius Mixes and eliminate duplicates.
For those of us that have downloaded FaceTime for Mac from the Mac App Store and have seen a dialog box with the following text: 'An Internal FaceTime error has occurred. There was a problem with FaceTime. You need to quit and open FaceTime again.'
In doing an investigation as to why FaceTime was not launching (which has been going on since the beta), I came up with this solution to the vexing problem, and here's what you need to do: Go to /Applications, then Right (or Ctrl)-click on FaceTime.app and choose 'Show Package Contents.' Then open the Contents/LaunchAgents folder, and copy the file called com.apple.imagent.plist to your ~/Library/LaunchAgents folder.
There is another file that you need to copy to your ~/Library/LaunchAgents folder as well, but that file on some Macs may or may not be installed. That file is called com.apple.apsd.plist. If that file is not located in ~/Library/LaunchAgents, you may have to download it.
You can do a search for the file on Google or your favorite search engine. After it's downloaded, rename the file com.apple.apsd-ft.plist and put this file in ~/Library/LaunchAgents and launch FaceTime.
If you see your camera light turn on and see your face, just sign in with your Apple ID or MobileMe account and you're all set.
[crarko adds: I haven't tested this one. If anyone has a further explanation of what is going on here, and why the .plist files are not installed in ~/Library/LaunchAgents to begin with, please post it in the comments.]
Lots of times, to get just the right look for your website, you want to use a font that is considered 'unsafe,' meaning unless someone viewing your page has that same font installed, the browser will pick some other default font to take its place. This obviously is undesirable. There are definitely more sophisticated and better ways to use non-web safe fonts, but if you want something easy and quick in iWeb, here's one thing you can do that's very easy and doesn't require any CSS or HTML code or widgets.
For any text using an unsafe web font, just rotate the text box marginally and iWeb will convert it to an image file so that your font appears as-is in any web browser. I asked if anyone noticed that the text was rotated and no one ever noticed.
There are two ways (that I know of) to rotate a text box. In either case, you first must click on the text box so that the corners have little white squares over them. Then hover your mouse over the corner while holding the command key, click and drag. The other option is to use the inspector. Under the tab that looks like a ruler, you can enter the number of degrees to rotate the font. I use this since it's easier to rotate an undetectable fraction (like 0.1 degrees).
I did this in iWeb 3.x. Of course, if you do this with a lot of text, then you're making your page bulky to download, so I only use it for fancy headings. Note, I have seen some buggy behavior with browsers not completely loading the images which (oddly enough) causes text to switch places. Hitting reload has always resolved this for me.
Songs created with the iPad version of GarageBand can not be opened with the Mac version (at least not at the time of writing). I've found a kludgy workaround that will allow you to open at least part of your project on your Mac.
Basically you just need to edit the version number embedded in the project file. I've posted the full step-by-step details to my blog.
Here are the steps:
Right-click a project and select 'Show Package Contents.'
Find the projectData file and open it with the Plist Editor (or a text editor if you don't have the Developer Tools installed).
Find the version key with the value 45000 and change that to 40000.
Save the file.
That's it! The project will now open, albeit with a bunch of warning messages and certain things (some instruments and loops) may be missing. But recorded audio, track settings, etc. should all be there.
[crarko adds: I haven't tested this one. Hopefully Apple will have that update out soon.]
Arguably the most useful part of the Office suite, Remote Desktop Connection is available as a free, separate download from Microsoft. The standard installation process will automatically install a bunch of background stuff that you arguably don't need, for instance, the auto-updater, crash reporter, and office dock package. Following this simple hint will allow you to install RDC without the added bloat and annoying auto-update popups.
Ctrl+click or right click on the RDC Installer package and choose 'Show Package Contents.'
Drill down to /Contents/Packages. You will see four installer packages. Copy the Office2011_en_rdc.pkg installer to your desktop.
Unmount (eject) the disk image and run the installer you just copied.
Everything should work normally, with the exception of no extra processes running in the background. This hint is obviously most useful to users wanting to run RDC, but not the full Office suite, and especially to sysadmins wishing to operate with RDC in a cleaner environment.
[crarko adds: I tested this, and it works as described. The current version of RDC is 2.1, which was a slight update for me.]
Unfortunately Apple decided to drop support for PPC, SDKs 10.4/10.5 and GCC 4.0 in Xcode4. This hasn't been done for technical reasons, though, but only because Apple wanted to do that. If you have a parallel installation of Xcode3 on your Mac, you can easily restore all that functionality to Xcode4. I posted a detailed step by step guide at Stack Overflow how this can be done. For convenience and to reach a wider audience I'm posting it here again.
Before I get to the how it is done part, here are some notes about my patch/hack/fix. Right from the start the major goals have been:
Keep all modifications to an absolute minimum.
We want to keep the Xcode setups as original as possible.
By all means, try to avoid patching or modifying any files.
We want all files to stay untouched and keep their original content.
Try to avoid moving or copying files around, unless absolutely necessary.
I was able to keep all those goals. Almost everything is done by creating symlinks. Only a single existing symlink had to be replaced and we'll back it up before replacement, just in case.
If you are no expert on terminal operations, I strongly advise you to copy/paste all terminal commands from my reply to your terminal, to avoid typos. Bear in mind that even spacing, quoting and especially capitalization can be important. Copy/paste them line by line, never more than one line at once and hit return after each pasted line to execute the command. Should any operation ever prompt you for a password, this will be the password of the currently logged in administrator user (your keystrokes are not displayed while typing, this is normal, don't worry, just keep typing the password and hit return; re-try if you had a typo and get prompted again).
If you have multiple FaceTime devices: iPhone, iPad, iPod Touch, Mac, Multiple Macs, etc. The iPhone's ID is the phone number, but the rest use an e-mail address. If you don't want them all to ring when someone is trying to contact you, then they each need a different address. You could set up a separate e-mail address for each device, but that's a pain.
All you need to do to have multiple IDs per e-mail address is append '+something' to the e-mail address. For example if your e-mail address is email@example.com and you wanted to have a separate FaceTime address for your iPad and for your Mac you could use: firstname.lastname@example.org and email@example.com.
As an aside, e-mails sent to firstname.lastname@example.org and email@example.com will still go to firstname.lastname@example.org as well. In general adding '+something' to your e-mail is a useful way to keep track of who is sending you mail (provided the services support it).
[crarko adds: I haven't tested this one, yet. As soon as I get an iPad 2 I will revisit this, though.]
Using information found in the article listed in the Comprehensive summary of Mac Metadata hint, I was able to find a way to write metadata from the CLI, making it possible for shell scripts to modify files in a way that is visible to the Finder, and therefor in Smart Folders and other search results.
Using xattr on the CLI you can write arbitrary metadata to files. This is useful for other CLI scripts because you can search for these arbitrary attributes using mdls. However, if you want to set metadata that is easily searchable in applications like Finder, you have to set the values for existing attributes.