Hopeless Geek

Codesign error: no certificate for identifier “iPhone Developer” was found in your keychain

Getting this error when building an iPhone app? Yeah … you’re going to love the solution:

After much tinkering around, I tracked the problem to a keychain error.

And TADAAAAA: Go to Keychain Access -> Preferences -> Certificates and deactivate both automatic checking gizmos.

Quit Xcode, relaunch. It worked for me. Instantly.

Best advice for .Mac Sync failures, ever.

One creative little AppleScript later and with a couple of keystrokes you can see your bank balances on screen immediately. Oh, the things curious coders will code.

read more | digg story

To get money, I have to bug people. It’s a sad fact of software development, but if the software didn’t destruct in a period of time, I’d be working for naught.

Right now, Notae goes four weeks (28 days) in a full-access demo and then locks down, hard. I’m seeing the majority of conversions within the first three days, and most of the rest in the first week. While I look at it and say “I would, myself, appreciate thirty days to get used to something as intimate as a notes program” I can also see getting used to it within two weeks as well.

Of course, with a time period that short, you run the risk of someone downloading it, opening it, poking around, and then forgetting about it. Some weeks later he goes to test it out seriously and bam the demonstration period has expired. Suck.

A compromise, then. I’m considering letting Notae run in a full demo for two weeks, and then locking out the user for two weeks before resetting the demo. That should be just enough time to get used to it if you just downloaded it and then enough of a wait so that if you wanted to try a new release after a couple of weeks that it would let you. The registration dialog would explain this and then give either the date of expiration or the date the lockout will reset.

My concerns, then, are these:

• Is two weeks enough time to get to know a program you’ll use pretty much daily?
• Is two weeks downtime enough? I’ve also considered four weeks here.

I love text-to-speech. I love it even more when it sounds clear. As such, I wrote Text Reader to save some documents as audio to my iPod. However, I realized later, Mac OS X’s default voices .. well … suck. Then I came across these gems. While the engine that takes words and creates phonemes is the same (it’s Mac OS X) the end result from those phonemes is much clearer. Finally, after ten years of TTS on the Mac, someone releases a third-party voice for it.

Cepstral TTS Demo

Go on, get it. It’s awesome.

Some lessons for using ecto with Drupal.

As promised, the parts of Drupal that I changed to get CP working the way I like it.

A quickie.

To make Hollywood-style credits in Final Cut Pro, create two “Scrolling Text” generators. Left-align one, put the part names in that one, then set the indent to 51%. Put the actors’ names into the second one, set it to right-align, and set the indent to 51% (they measure from opposite sides). If you change font metrics in one, change it in both, of course.

To get sections (cast, crew, locations, etc.) create a third generator, set the font metrics to be the same, and set it to center. Put in one blank line for every line in the others. Put blank lines in the others where there is text here.

It’s a hack, yes, and until Apple creates a real credits generator it’s what we have, but it beats keyframing a Photoshop file by a significant margin.