My Macinations

Now that HD-DVD has officially lost the HD format battle, and Blu-Ray has emerged the victor, many Mac sites are speculating that Apple will soon implement Blu-Ray playback support into its system and start selling Blu-Ray drives in its computers.

I’m not sure Apple will implement Blu-ray playback into OS X any time soon.

One thing most people don’t know is the requirements to get the license to playback HD stuff on computers. The rules require that the playback device makes sure that the chain from the computer’s DVD drive, to the RAM, to buffers, to the graphics card, to the cable, to the display are all encrypted. That is all in order to close the ‘Analogue Hole’.

Did you know that Vista checks for chain encryption integrity for every frame when it’s playing HD contents? That’s 30 times every second (talk about paranoia). Try to buy a Vista system that can play HD stuff and see what onerous requirements you’ll find. You’ll have to buy specific graphics cards, specific monitors etc…

For Apple to implement Blu-Ray playback it has to do a lot of work to be compliant; and the requirements would put quite a burden on the system. I believe that’s the reason that currently, with iTunes rental service one can get HD rentals on the AppleTV only and not on one’s Mac. The AppleTV is a closed unit with an HDMI connection, meeting the stringent requirements for HD playback. Many people don’t expect this, but if you connect the AppleTV to your HD TV using the component video connectors instead of HDMI, the AppleTV won’t display rented HD contents in HD, you’ll get an SD version of the rented movie.

I’m not sure I want Apple to implement that kind of crap into the system that I use every day, in order to do something that I couldn’t care less about.

I mean really, does it make any difference if the stuff is true HD on a computer screen considering that the largest one currently is is 30″?

I would guess that Apple would implement Blu-Ray as a storage device on the Mac in order to take advantage of the huge capacity that it provides, and would leave HD playback to downloads and the AppleTV.

With Leopard 10.5.1, Apple’s developers changed the default status of html files downloaded from the internet from ‘safe’ to ‘Unsafe’.

While this may make sense from a security standpoint, for somebody like me that processes hundreds of html files downloaded every day, it’s a big annoyance.

I filed a bug with Apple, asking for a workaround. I was hoping that they would implement a preference somehow to enable me to either override the default settings or allow me to specify trusted servers.

Tonight, three months later, I received an answer and the workaround that I was looking for.

I turned out that you could have a user specific file to override the system’s default settings. The file is not there normally, so you would need to create it. It is:

~/Library/Preferences/com.apple.DownloadAssessment.plist

The contents of the file need to be:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>LSRiskCategorySafe</key>
	<dict>
		<key>LSRiskCategoryContentTypes</key>
		<array>
			<string>public.html</string>
			<string>public.xml</string>
			<string>public.php-script</string>
			<string>com.microsoft.windows-media-wmv</string>
		</array>
		<key>LSRiskCategoryExtensions</key>
		<array>
			<string>xhtml</string>
		</array>
	</dict>
</dict>
</plist>

Download Sample File

Hopefully that helps somebody else with this type of problem.

If you need to change the settings of other file types, here are the system-declared file types:

System-Declared Uniform Type Identifiers

For each type you add another <string></string> item to the above array.

For example, for jpeg2000 files you add:

	<string>public.jpeg-2000</string>

Right below the other <string> line in the first array.

To declare files by extension, you add:

	<string>odf</string>

Right below the other <string> line in the second array.

Yet another useful feature has been eliminated in Leopard.

The audio controller that the Finder’s column view had for the preview pane when previewing audio files has been eliminated. Why? I don’t know. No logical explanation can come to mind.

In Tiger, if you set your window’s view to the column view and point it to a folder that has MP3 files, when you select one of those files, the right-most column shows a controller that allows you to play the audio file, select the point where you want the play head to be and control the playback’s volume. Leopard: NO MORE!

What you get in Leopard is a silly, YouTube-like preview square with a big ‘play’ button in its middle. No volume control and no skipping ahead. You can always hit the space bar to get a big window showing iTunes like display, and you can skip ahead, but you still can’t control the volume.

Somebody should tell Apple’s engineers that an UPGRADE is when you make things better, not worse.

I’ve been using Leopard as my only OS for 4+ days now. Here is a first report on where I’ve encountered the most problems.

Safari:

I spend a lot of time with Safari (can’t use any other browser as my main browser). It’s the only Apple application that I use so extensively. So far I’ve noticed few thing:

1. It crashes way more than previous versions of Safari. I guess they’re using a code-base almost completely different from the beta 3.0 version that they released for Tiger. The beta Tiger version was almost bulletproof for me. I’ve had unexplained crashes so far at least twice per day. Most of the crashes happened when I started typing in a form.
2. It seems to be unable to block certain type of popup windows. I have the ‘Block pop up windows’ preference set, and yet I’ve had two or three instances where websites managed to show me some ads in a popup window. Not good.
3. Visual glitches: A site I visited changed the size of my main Safari window to a really small size and then back to full-screen. After the expansion to full size, the tabs bar got clipped and only a third of its normal hight showed. I couldn’t get it back to normal size without quitting Safari. (side note: I wish Safari had a resize blocking feature like Camino. I just hate it when a stupid website decides that my window size is not adequate for its display and ‘helps’ me by changing the size of my browser window).
4. Scripting: Apple changed the behavior of some AppleScript commands. The ‘open’ command used to open a new window with the URL, now it opens it in a tab. The kicker is that Safari doesn’t seem to respond to ‘make new window’ command. (I’ve worked around this one by modifying my code to anticipate a new tab instead of a new window and acts accordingly.)
5. Spontaneous cookie loss: It has happened few times already. I would be surfing and managing my various websites, (most of my websites rely on cookies for log in), and suddenly, I would be logged out. I looked over cookies and most of the cookies weren’t there. They simply vanished. Not all cookies, just some. I have no clue how to track this bug.
6. Web clippings don’t work: I’ve tested the Web Clip feature and it doesn’t seem to work. When I make a clip of a page, it appears correctly in Dashboard, but whenever I reload the Dashboard, the clip is empty. I tried it with various sites with the same result.

Folder Actions:

To show my geeky side, one of Leopard’s features that I anticipated the most is the enhancements to the Folder Actions engine. In Tiger, if you had multiple folders with folder actions, those actions don’t run concurrently. They run back to back. So if folder 1 fires its action and it takes a while to complete, folder 2 won’t fire its action until folder 1′s action ends. Leopard’s feature list promised to fix this.

However, not only they didn’t fix it, a bug seems to have broken Folder Actions further. Now, even if I have multiple folders with folder actions set up, only the first active one works. All the other ones don’t work at all. So now I have to choose which folder action I can live without and which ones are too crucial.

Well, I finally took the plunge. After yesterday’s problems installing it on my iBook, I took all the precautions that I can and took the plunge and installed it on my iMac.

Steps:

• Buy a 1 TB drive from Costco.
• Plug it in and realize it’s dead.
• Exchange 1TB drive at Costco.
• Plug it in and it works!
• Check main drive using DiskWarrior
• Make a bootable backup using Superduper
• Install Leopard by doing an ‘Upgrade’ install.

Done!

All my settings seem to be working. Had a hiccup with my keychain. For whatever reason Leopard didn’t read it properly. But strangely, even though I created a new keychain with the same name, the new – supposedly empty – keychain had all my old passwords!

I haven’t bumped into any incompatibility yet with any of the software that I use regularly:

• Path Finder
• BBEdit
• PowerMail
• Interarchy
• Hogwasher
• Vienna
• Adium
• SpamSieve
• Ulysses
• Photoshop

So far so good. The only thing that needed work to get it back up to its previous working status was my Apache/PHP/Mysql.