Thoughts

Why is it that Apple has three messaging apps?

  

Back when Apple brought out FaceTime, I couldn’t get why it had to make a separate video chat app when it already had iChat. Now we have a third app included with iOS 5, called iMessage. Why?

If the people at Apple are intent on making little messaging apps, each with their micro-purpose, then I’d like to suggest some new ones to them:

  • iShmooze: giving people a direct chat line to their boss or work hierarchy
  • iRx: so you can chat about your medications with your neighbors and know-it-all relatives, and get better prescription advice than from your doctor
  • iExChat: for venomous quips exchanged between ex-spouses and other ex-es…
  • iSeeAds: for people interested in seeing targeted ads; perhaps you can work in a micro-pyramid scheme where people can get something like 1-5 cents when they view an ad or invite their friends to view ads; that should be popular…
  • iSeeDeadPeople: photo sharing for zombie and vampire lovers
  • iPotty: for those who love to share those precious moments in the bathroom
  • iAte: see above and substitute food; this one could come with a photo sharing option, for those who love taking photos of said food; in hindsight, perhaps the photo sharing option could be extended to the iPotty app as well, I saw some folks online who would be interested in that.

For a company renowned for its design and the clear focus of its products, I’m surprised to see three messaging apps. Why? Didn’t anyone put their hand up to say, “Hey, don’t we already have iChat?”

Perhaps it makes sense to have the separation, from a software and procotol perspective. Perhaps iChat was designed for the computer. Perhaps the AOL messaging protocols it still uses aren’t suited for the purposes of FaceTime and iMessage. But it still makes NO sense.

If Apple was able to take OS X and turn it into iOS, then take features from iOS and put them back into OS X, then it’s quite capable of making iChat the go-to app for all its messaging needs. Rewrite it and make it work! It’s already incredibly capable on the desktop. It can do text chat, audio chat, video chat, file sharing and screen sharing. I use it all the time to do video conferencing with my parents, all the way across the Atlantic Ocean, and I use it for screen sharing as well, when I help them troubleshoot issues on their computers or simply teach them how to use them better. Why in the world would you leave a capable app like that behind and write a new one called FaceTime? And then why would you further fragment that segment and make another one called iMessage? Why?

I’d like to see iChat be the one and only app that does everything this set of three apps does and more. I’d like to challenge the people at Apple to make it work the way it should work, tailored to the capabilities of each device where it will be installed.

Standard
Thoughts

Do not use iMovie sounds for YouTube videos

Updated 4/24/12: YouTube has greatly improved the copyright claim dispute process in recent weeks, and it seems that even copyright holders have gotten much more responsive and willing to relinquish claims falsely flagged by YouTube’s Copyright ID engine. These are all good steps in the right direction! 

Are you a YouTube Partner? Great! Then don’t use sounds or tracks from the Final Cut Pro/iMovie/iLife library in your YouTube videos, because sooner or later, they’ll be flagged, taking them out of the revenue sharing program.

I’ve touched on this topic in this post and this earlier post as well. Until now, I thought filing a copyright dispute and trying to work within that process on the issue would lead to the correct solution, which would be a rejection of the false claims, but unfortunately that’s not the way the copyright dispute process is structured.

There is no mechanism on YouTube to adequately dispute a copyright claim, because the process is heavily tilted in the favor of the supposed copyright holder. There is a first step, which allows you to raise your hand and say to the alleged copyright holder, “Wait a minute, I’m not using your music, the track I’m using here is royalty-free, here is the iLife SLA, see where it says I’m allowed to use it commercially”, which may lead to the removal of the copyright claim, or not, in which case you can re-dispute but risk jeopardizing the standing of your YouTube account, the removal of your video along with its view count and the possible loss of your Partner status. That can be a terrible situation.

That’s right, beyond that initial “raising of your hand”, there is nothing else you can do. If YouTube staff is nice, they might give you an email address for the supposed copyright holder, and in some rare cases, someone might read your email at those places, respond and actually do something meaningful about your problem, but that chance is slim. The majority of the time, you’re going to be screwed over, and some alleged copyright holder is going to profit from your work.

The really annoying part in this whole screwing-over business is there’s no middle ground. Your video’s either in the revenue sharing program or it isn’t. YouTube has chosen to ignore the whole video aspect of this altogether, meaning that when a copyright claim is filed for the music in a video, even though you have a video which is wholly yours, and only the music might belong to someone else (but it doesn’t when you use sounds from iMovie, because they’re royalty-free), they pull the video out of revenue sharing altogether, as if there’s no video, only audio. Shouldn’t they allow you to continue to make some money on that video? After all, you shot it and edited it! Your only “fault” (if we could even call it that) was using royalty-free tracks from Apple to score it. In a logical world, that’s what would happen, but we don’t live in a logical world. We live in a world where YouTube chooses to obey the demands of alleged copyright owners without standing up for its YouTube Partners. All these supposed owners have to do is to upload sound-alike tracks to their YouTube catalog and they’re set. YouTube’s Content ID engine will start identifying videos that are using similar-sounding tracks and flagging them, leading to a lot of frustration on our part. I know this sounds harsh and I love Google and YouTube, but this is so frustrating for me that I’m not sure how else to put it.

Things have gotten so bad that now the copyright trolls have started to make music that sounds like the tracks from the iLife Library, for the express purpose of cashing in on YouTube. See this thread in the YouTube forums. And for a bit of background on the issue, see this thread as well. The problem’s existed for years, not months. YouTube likely knows about it. Privately, they’re likely tweaking the copyright engine algorithm and they’re trying to address the problem, but publicly, all I’m seeing is people getting screwed over by the copyright trolls.

You can’t even rely on the initial copyright warning anymore. In the past, you’d upload a video to YouTube, and within a few minutes, you’d get a warning saying the video matches content from such and such entity. Fine. I’d pull it down and re-edit it, using other sounds, even though the sounds I’d used were also from Apple’s royalty-free library. But now, you upload the video, everything’s fine, and months down the road, after the video’s been seen by thousands of people or more, and it’s been linked to, etc., you get the dreaded copyright warning. What are you going to do then? Pull it down? As you can see from the thread I linked to in the paragraph above, the copyright trolls are going through popular YouTube videos, identifying the music used in those videos, and then profiting from this loophole. We, the YouTube Partners, who do the hard work to create the videos that make YouTube a popular website are the ones getting screwed over. When is YouTube going to stand up for us?

To be fair, I think the blame rests squarely on the shoulders of both Google and Apple on this matter.

What Apple should have done, years ago, was to sign up for the Content ID program and upload all of the tracks in the iMovie/iLife Library (you know, the ones they keep saying are royalty-free). Then, they should have indicated to YouTube that whenever a video uploaded to the platform matches one of the tracks in their library, YouTube should do absolutely nothing about it, because it’s perfectly okay, they’re royalty-free tracks. If they had done that, we wouldn’t be in this mess now, would we?

YouTube is to blame as well. The copyright dispute process does not work. It puts all the balance of power in the hands of those who file the copyright claim, and because no person at Google reviews our disputes, the trolls have all the say in the matter. (I understand the sheer amount of work it would take if YouTube staff would have to review every dispute filed for false claims, but at least they could do it for their YouTube Partners, there aren’t that many of us.)

Instead our copyright disputes only get seen by the staff at the various copyright holding groups, who have an interest in maintaining their claims, since there’s no recourse from Google/YouTube for wrongly identified videos, and of course, let’s not forget the copyright trolls, who hang onto every claim they make no matter what one says in a dispute.

I make that distinction above because there are some groups within the music industry who aren’t copyright trolls. For example, I’ve had copyright disputes reviewed by staff at the GoDigital Media Group and the Warner Music Group, and they’ve ultimately agreed with me and retracted their copyright claims. So there are some good guys around, there just aren’t enough of them.

So my advice to you, as stated at the start of this post, is do not use music from the Final Cut Pro/iMovie/iLife Library at all if you’re a YouTube Partner. You’re better off using music from independent artists and licensing it directly from them, or getting it from websites like MusOpen — or scoring your videos yourself, with original music.

Perhaps Apple and Google will fix this at some point. Until then, do yourself a favor and follow my advice. You’ll be able to sleep better for it.

Standard
Reviews

Two feature requests for Apple’s Pages

I sent the following enhancement request to the Pages team via the Apple website and figured it’d be a good idea to share it here as well. Perhaps you have some suggestions for me, something that could help me in the meantime?

  1. Better memory management. My wife and I write graphics-rich books (recipe books, piano methods etc.). Currently, there is no way to layout an entire book in a single Pages document, because after 5-7 pages or so containing digital photographs imported at print-ready resolution, Pages runs into a memory management bottleneck and every keystroke takes 1-2 seconds. We’re forced to either work on individual pages as separate files, which makes pagination and text flow a real hassle, or to divide the book into sections of a few pages each and basically run into the same pagination and text flow issues.
  2. Support for offset printing in Pages. It’s great that I can export to digital book formats (ePub, PDF) but what I really need is support for export to offset printing methods. When I export to a PDF from Pages, the text is never 100% black. It’s a mixture of colors, which is a disaster in the making for offset printing and necessitates a lot of work on the resulting files after they’re exported from Pages, just to get them offset-ready. Please include a one-click PDF export for offset; call it what you will, but make it work.
I know Pages is not supposed to be a full-featured design and layout application, but it could almost fill those shoes if these two things were resolved.

Standard
Thoughts

Wonderful thoughts on Steve Jobs from a neighbor in Palo Alto. The article shows a different view of Steve, that of the devoted family man.

My Neighbor, Steve Jobs This article first appeared in Palo Alto Patch. My neighbor, Steve Jobs, has been in the news lately. The talk of the town is the recent announcement he will be stepping aside to let other seeds grow at Apple. The business press, the general press, the blogosphere, and just about everybody else has waxed poetic about the “greatest CEO of all time” saying that this “boy wonder” has shaped the very nature of our lives with his genius.  It’s all tru … Read More

via Lisen’s “Blog” – An Angle of PrismWork

Get well, Steve!

Link
Reviews

Initial thoughts after installing OS X Lion

I thought I’d jot down a few thoughts about OS X Lion, having just installed it on my MacBook Pro. I looked forward to getting it for months, and as luck would have it, I happened to be out of town with little internet access when it was released on the 20th.

  • The upgrade was painless. I bought it from the App Store, it began to download, and when it was done, it ran and finished without any bugs.
  • Without a media disc of some sort, or at least an image file, I am somewhat concerned about a re-install of the OS, should I need to do a fresh install. I hear there’s going to be a Lion Flash Drive available for sale in a month or so, but short of paying for that as well, is there some way for me to burn Lion on a DVD or make a bootable flash drive?
  • Overall, I like it. The design is more refined. It feels like a more mature OS.
  • I like the full-screen functionality of the apps.
  • The login screen is interesting. It’s a departure from what we’ve seen thus far. I like it, but I’m not sure what to think about the round thumbnails for the accounts yet. I’m used to square thumbnails. Photos are rectangular. Square photos? They used to be en vogue in the late 1800s. But who knows, maybe those round thumbnails will grow on me.
  • I do wish iCloud were launched at the same time as OS X Lion. For example, I don’t know if I did something to cause this, but every time I start up Safari, it wants to log me into MobileMe, where I don’t have an account. (I only have a .Mac email address.) If iCloud had been available right now, this glitch wouldn’t have occurred, because .Mac and MobileMe would have been unified already. And I think more people are going to run into it as they poke around in the new OS.
  • The hidden scrollbars are great, but they’ve changed the direction of the scrolling, haven’t they? It’s counter-intuitive… and yet it’s not. You now push up with two fingers on the trackpad to scroll down, and pull down to scroll up. If you think about it, it makes sense, but it’s been the other way around until now, so it’ll take a while to get used to it.
  • I like Launchpad. I think it’s a visually appealing way to present a list of all the Apps on my Mac, and to allow me to easily choose which one I want to run.

A couple of pieces of advice before you upgrade:

  • Run Software Update to make sure you’ve got the very latest version of Snow Leopard and whatever other updates you need.
  • Run Time Machine to make sure all your stuff’s backed up, just in case something goes wrong.

For those who like this sort of thing (I do), I’ve included a couple of before and after screenshots of my “About This Mac” window.

Before the upgrade to OS X Lion

After the upgrade to OS X Lion

That’s it for now.

Standard