h1

Keep taking the tablets

January 28, 2010

I had a bit of a “Doh!” moment when I finally discovered what the iPad was all about.  It should have been obvious long before Steve Jobs’s announcement yesterday.  My only excuse is the constant reference to the term “tablet” which I associate with devices that look superficially like conventional laptops but have swivelling screens.  I have one of those but they are in general regarded as a failed concept.

The iPad is not in that space at all.  It is not Apple’s answer to the tablet PC but Apple’s answer to the netbook and Amazon’s Kindle combined.

As ever, Apple pick up after a need for something new has alrready emerged and others have already created inadequate products in response. Usually those early attempts by others fail because they are trying to adapt something that already exists but the paradigm does not translate properly.  The tablet PC is a prime example.  Another would be every smartphone prior to the iPhone which was some unhappy marriage of PDA type device and conventional mobile phone, often involving use of a (ugh!) stylus.

Apple won in the smartphone stakes, improving on the earlier failed attempts by starting from a different direction.  They realised that they needed a device that was all touch screen but with an interface that did not need a stylus.  And not to try to do too much. Most users want to be able to get their media on there, browse the web and access their email, but not necessarily care about getting into the gubbings or hacking the device.  If they wanted to play games or expand the usefulness of the phone they would just download applications.

Similar story with the iPad. Netbooks have arisen because many people just want to browse the web at home or do their email but don’t want to wait ages for a PC to boot up.  They don’t need to do serious gaming or video encoding so something smaller, lighter, cheaper is fine.  To date the answer has been a smaller, lighter, cheaper laptop – ie the netbook.  Another need has been the eBook reader.  The Kindle has been successful but eInk is not everyone’s cup of tea.  Low contrast, slow page turning.  The only real benefit is a long battery life.

The iPad takes the paradigm that worked for the iPhone and reapplies it to the need to date met by the netbook and Kindle.  It brings the benefits of ease of use, touch interface without stylus and quick/convenient access to the lightweight tasks (web, email, reading a book, watching a movie) that most people actually want.  It will stretch to work type things but that is not its main market.

Do I want one?  Hell no, but I do think it will be successful.

h1

Avatar the Musical

January 20, 2010

Clapperboard I would like to create a musical version of James Cameron’s “Avatar”, maybe with some surprise special guests borrowed from Disney movies.

One of the characters would ask “Where do we find the Unobtanium?” in reponse to which Sebastian the crab would  break out into a rousing chorus of “Under the Tree”.

Under the tree, under the tree ...

What do you reckon?

Thought as much.

Hmmm.

h1

Tweeted off!

January 20, 2010

Vista busy cursor The most annoying thing about Twitter being “over capacity” (down) is that you can’t tweet about it being down.

It’s a natural reaction. I find it therapeutic to consign my milder moans to Twitter. So my followers think I’m a grouch. That’s OK.

But when it comes to mild moans about Twitter being down I have nowhere else to go but my tech blog. And no, I’m not going to sign up to tumblr or plurk just to have somewhere to go to complain about Twitter.

h1

Podshifter & TWiT: Thank You Lina

January 11, 2010

Vista busy cursor Podcasts from the This Week in Tech (TWiT) network can once again be processed by PodShifter so that they take less time to listen to.

The earlier problems, explanation and plea to Lina Calabria (one of PodShifter’s backers) are documented here and here.

I can only assume that the PodShifter development team have fixed the problem as promised by Lina, in which case I would like to thank Lina for her kind personal intervention, on my own behalf and on behalf of all TWiT listeners who rely on PodShifter to help them shift their way through Leo’s ever increasing stable of podcasts.

AddThis Social Bookmark Button

h1

The TWiT Podshifter saga: A plea to Lina

December 24, 2009

Vista busy cursor I am eating humble pie after suggesting that Leo Laporte might have acted deliberately to prevent This Week in Tech (TWiT) network podcasts from being speed-shifted, using the PodShifter service, when dowloaded via iTunes.

It turns out that Leo, or his staff, did take action which prevented PodShifter working on TWiT podcasts, but that was just a side effect. The intention was quite different and entirely innocent. Leo was gracious enough to respond to my earlier post to explain it all.

Specifically, the TWiT RSS feeds were modified by adding a new iTunes feature, the <itunes:new-feed-url> tag which is described here. The tag is there to help podcasters change feed URLs, or deprecate old URLs, without breaking existing iTunes subscriptions. The TWiT feeds have started using this tag to standardise all their feed URLs. Unfortunately, because PodShifter preserves all iTunes tags when it creates the shifted podcast feeds, iTunes just follows the URL in the <itunes:new-feed-url> tag and effectively replaces the shifted podcast feed with the unshifted original feed.

Leo became aware of my post thanks to Lina Calabria of Investling who is one of PodShifter’s backers and had, presumably, been scanning twitter for PodShifter related tweets.

Lina, I have a request for you. Having tried to get my mind around this, this is my take on what should happen next. While I understand that PodShifter (to quote one of your own tweets) respects iTunes tags, that really doesn’t make any sense in the case of the <itunes:new-feed-url> tag. People only use your service because they actively want a speed-shifted version of a given podcast. By preserving that tag you are causing them to get a normal speed podcast and so thwarting their wishes.

PodShifter should not ignore the <itunes:new-feed-url> tag, rather it should use it, if present, to identify the correct URL of the podcast to be shifted. This is in keeping with the spirit of the tag because it resolves issues over changed or deprecated URLs, which is why the tag was introduced in the first place.

Having thus updated the target URL, if applicable, PodShifter should work its speed-shifting magic in the normal way but NOT then pass on the <itunes:new-feed-url> tag. There is no need, because the purpose of that tag will already have been realised in the updating of the URL prior to shifting.

That way, the benefit of the tag is not lost (and in that sense it is still “respected”) and the end user still gets a shifted podcast to listen to, which is what they were trying to achieve. So everyone wins.

So what do you say, Lina? Could PodShifter customers have this change as a XMAS present? Please bear in mind that right now it only seems to be affecting TWiT, but Leo may just be quick off the mark. As more podcasters discover the use of the new tag the more PodShifter users will find their podcasts delivered unshifted and the vast majority will be at a loss to understand why or to do anything about it.

AddThis Social Bookmark Button

h1

Screw you, Leo, I’m back up to speed with my podcasts!

December 23, 2009

Vista busy cursor This is the second post on the spin that I find myself having a pop at Leo Laporte.  It’s in no way personal.  I admire Leo greatly and enjoy listening to most of the This Week in Tech (TWiT) podcasts.

But I do have a genuine gripe, and it has to do with his blocking of the PodShifter web application when used with TWiT podcasts.  [Author's note added 24/12/09: since posting this an innocent explanation has come to light - see the comments to this post including response from Leo] Podshifter is a tool that speeds up podcasts, to help podcast listeners get through more of them in the available listening time. Podshifter changes the tempo of the audio while preserving pitch, so that Leo and his co-hosts don’t end up sounding like something from Alvin & the Chipmunks.

It is very use to use. If you have already subscribed to the original podcast in iTunes, you right-click to copy the podcast URL then paste it into the box on the podshifter.com home page.  Next choose a target tempo;  I usually opt for 1.2x or 1.4x the speed of the original.  Click the “shift it” button and the tempo-adjusted podcast is created with a new URL which is displayed for adding to your preferred podcatching software.  Or you can just click the link to have it added automatically to iTunes.

Note that you can’t in general download each new podshifted episode straight away, because it takes a while for PodShifter’s servers to carry out the audio processing from the time that the original episode is first published.  No doubt some heavyweight Digital Signal Processing is required, probably involving Fourier Transforms.

Ironically, I first heard of Podshifter on a TWiT podcast, the Daily Giz Wiz.  Co-host Dick DeBartolo read out a listener’s letter which mentioned it.  I recall Dick and Leo having a good laugh about it, deliberately speaking very fast or very slowly, in a  mock effort to trick anyone listening to a podshifted version.  But Leo also immediately spotted the threat posed by PodShifter. Downloads of podshifted podcasts would not count towards the iTunes official TWiT podcast download numbers which drive Leo’s advertising revenue.  Ouch!

I saw that as Leo’s problem.  For my part, I valued the saving in time.  I have a lot of podcasts on my subscription list, many of them from the TWiT network, and only so much time in which to enjoy them.  Even after reluctant pruning of the least essential listening, I was still struggling to fit my podcasts and audible books in, and my audible.com credits were starting to mount up.  PodShifter made a big difference. Even  just sticking to 1.2x freed up 20% listening time and some podcasts are perfectly listenable at 1.4x.

It is surprising how well the human ear tolerates the speeding up effect. I guess we can listen to and absorb the spoken voice at much higher speeds than people normally speak.  We can’t ask Leo and friends to speak (and think) faster but we can keep up quite comfortably when a machine does the speeding up for them.  I tend not to go beyond 1.4x because it starts to become less comfortable and I don’t want my podcast listening to become hard work.  Some podcasts really can’t be sped up much because of the gabbling co-hosts. You can listen to Leo quite effortlessly at 2x or more thanks to his polished radio voice, but Gina Trapani on This Week in Google naturally speaks like a machine gun out of control and 1.2x is the absolute limit for TWiG.

The Podshift Party had been doing the business for me for a number of weeks when Leo decided to step in and spoil the fun. I guess he felt he had to try to limit the erosion of his official download numbers.   It looks like TWiT has done a behind the scenes deal with iTunes so that URLs pointing at shifted versions of TWiT podcasts get replaced automatically by the official unshifted podcast streams.  No warning.  It just happened.   I had copied the latest batch of podcasts to my phone one morning and started to listen on my car journey to work. The theme tunes were playing at the right speed.  Very odd. And the voices sounded plodding.  Back at home I checked iTunes and discovered the URL substitution.  I tried creating new podshifted streams.  In all cases shifted TWiT podcasts were replaced by the URL for the original unshifted stream. Other podcasts were not affected.

Happily I found a work-around, using a desktop podcatcher application called HappyFish. It accepts PodShifter URLs for TWiT podcasts without substituting for the originals.  I am back up to speed.

Now I understand Leo’s concern about PodShifter but I think he’s wrong on a couple of counts.  The first is that he is guilty of the same “put the genie back in the bottle” thinking that he berates “Old Media” for, and Rupert Murdoch in particular.  You can’t fight innovation with protectionism.  Blocking PodShifter on iTunes is an example of Murdoch Mentality and it doesn’t work.  He would have done better to work with both PodShifter and his advertisers to get the Podshifter TWiT stats counting towards the advertising totals.

The second point relates to a comment Leo made in the most recent episode of TWiG.  He suggested podcast consumption numbers had stopped rising because with the proliferation of podcasts people couldn’t easily find new ones they’d like to listen to.  Too much out there to find the right podcast for you.  He saw it as a search problem. I disagree.  From the perspective of a dedicated podcast listener I can tell Leo that I get plenty of “leads” for interesting new podcasts just from listening to the existing ones.  That’s not the problem.  It’s just that I’m maxed out on available listening time.  You can only spend so much time driving to work, walking the dog or at the gym.  After establishing a list of favourite podcast subscriptions you tend to stick to it.  I don’t try out any more new podcasts, however tempting, because I struggle to find time for the ones I already subscribe to.

The irony is that PodShifter is actually a potential solution to that problem.  An opportunity to achieve an expansion in the size of the podcast market.  So listen up, Leo.  Don’t try to kill PodShifter.  You’d do better to give them a helping hand.  They could be your best bet for getting your business growing again.

AddThis Social Bookmark Button

h1

Leo takes leave of his senses

December 3, 2009

Vista busy cursor Interesting, Chief TWiT Leo Laporte has openly decided to appropriate voluntary contributions to the This Week in Tech podcast network for his personal income.

This is in the name of establishing a direct link between his income from TWiT and his consumer approval rating, measured by said consumers’ voluntary contributions which were originally solicited as needed to help with the running costs of the (then infant) TWiT network. This arrangement replaces whatever income he would otherwise be drawing from TWiT. He promises to be transparent, and publish his income based on the contributions.

Despite my tongue in cheek opening paragraph, I don’t think Leo is attempting to do anything underhand but neither am I sure it makes a whole load of sense. I rather suspect that Leo is embarrassed about being perceived as rich. It recently became public knowledge that TWiT is turning over around $2.5m per annum. Listeners are aware of Leo acquiring no end of gadgets, going on expensive holidays and buying pricey cars, because he hardly makes a secret of any of these things on his various shows. Put that together with the turnover figure and suddenly Leo appears to be coining it.

Of course, it’s not as simple as that. TWiT now has a staff of 7 full time employees, considerable running costs as it gets technologically more sophisticated, and a good part of the advertising income presumably goes to pay co-hosts on the different shows. All the same, I can’t help wondering whether Leo is doing this to pre-empt criticism that he is making a mint from TWiT, not that there is anything wrong with that. He has been successful on merit – why can’t he reap the reward?

Maybe he has been given a big raise on his “old media” radio show and decided he can come over all frugal and responsible at a time when many are heading towards a recession-hit XMAS.

AddThis Social Bookmark Button

h1

The Black Screen of Death

December 1, 2009

Vista busy cursor According to the BBC (and doubtless others) Microsoft are investigating a new phenomenon affecting Windows 7 which is being dubbed the “black screen of death”.

Oh ho, methinks! Did I not myself verily encounter a most unwelcome phenomenon with Windows about a month ago which I also chose to describe in those exact terms? Except that it was Vista that was getting stuck at a steadfastly black screen, not Windows 7. I now believe that problem arose because I had a dual-boot arrangement (Vista plus Windows 7) which had not been set up correctly, so that the two OSs did not recognise each other’s presence and therefore felt at liberty to interfere with each other’s file and disk security settings. This had robbed both OSs of permissions to load key system files with the result that Vista’s boot up sequence came to a premature halt with a black screen of death while Windows 7 succumbed to an infinite reboot loop. These problems disappeared completely after I reinstalled Windows 7 from scratch and used NeoSmart Technologies’ EasyBCD to set up the boot options menus correctly for both OSs.

I have no idea whether the black screen of death now being reported has anything at all to do with the problem I had with Vista, but I would not be at all surprised to learn it was connected with some automatic system meddling with file and disk permissions, either in relation to a dual boot setup or otherwise.

AddThis Social Bookmark Button

h1

Dual-boot remote access – it can be done!

November 20, 2009

Vista busy cursor Just imagine that you have a dual-boot system, say at home, and want to access it remotely over the Internet and also want to be able to switch between the two operating systems.

The remote access part is now quite easy, thanks to Microsoft Live Mesh which has similar functionality to commercial product such as Citrix’s GoToMyPC but is helpfully free.  It also works on the Mac.  Live Mesh is still in beta but is rock solid.  From my office I can access my PC at home over the Internet.  It breezes past the enterprise firewall and proxy server setup as if they weren’t there.

But switching between the two operating systems on the home PC, while accessing it remotely, seems rather harder.  After all, while you can easily force a system reboot remotely, by the time the system is going through its boot-up processes your remote connection will have been lost, so you will have no access to the boot menu to choose which operating system you want to launch. Live Mesh will not restart until after the OS has booted up, so you will always get the default operating system back again.

For Windows users, the solution is a very simple utility called iReboot from NeoSmart Technologies.  It was designed with dual-boot systems in mind, to cut out the effort involved when switching between systems.  Once running, it lives in the notification area of the Windows taskbar.  Using that icon you can force a reboot into the OS of your choice, rather than having to make the OS choice from a boot menu at restart time.  That means you can choose the OS to boot up in when accessing the PC remotely.  I don’t think NeoSmart created iReboot specifically to help remote users of dual-boot systems, but it certainly can be used for that purpose, in combination with Live Mesh, GoToMyPC or similar.

Of course, Live Mesh will still lose contact with the PC while it goes through its reboot process, but you can connect again once the chosen OS has booted up, provided you had installed Live Mesh (with saved password) on both operating systems.  Provided both systems are Windows based, and you have iReboot installed on both, you can switch back and forth to your heart’s delight however many thousands of miles away you are.

The one complication is with Mac/Windows dual-boot systems, because iReboot is Windows only and there is no equivalent of iReboot on the Mac.  Having said that, if you make Windows your default OS and force a straight reboot from the Mac side of the system it will still boot back into Windows, and from the Windows side you can use iReboot to get to the Mac.

AddThis Social Bookmark Button

h1

Hasta la vista, Windows 7

October 30, 2009

Vista busy cursor For the second time in a matter of weeks I found myself unable to boot into Vista on my home desktop due to a file permissions problem. The tell-tale signs are becoming familiar. Boot-up starts as normal with the screen that has the pulsating green progress bar.

When that disappears we get a black screen and after a few seconds the mouse cursor appears in the centre. The disk continues to thrash for a few more seconds then settles, but we remain stuck looking at the mouse cursor on a black field. The black screen of death.

I believe the problem is that Windows has reached the point where it wants to write to the disk but is unable to because the file it is trying to access has been made read-only or otherwise had its permissions stripped away. You’d think that a booting OS would always have access rights but apparently not.

I wasted hours with Spinrite, thinking it must be due to a damaged sector. The only way out of this, short of a reinstall of the OS, is to boot up in a different OS, maybe on a different disk or from a CD, and then manually change the permissions on the files in the drive that won’t boot.

Ironically, it is the use of different OS’s on different disks on the PC that seems to be implicated in giving rise to the problem in the first place. Particularly if one of the OS’s is Windows 7, or at least the Release Candidate.

I have had two disks on my desktop for years. The larger one (250GB) is the Vista drive that came with the PC. I later added a 40GB drive salvaged from an older computer and for a long time had XP on it. I found I could switch between the two without problem. The BIOS allows you to choose which disk to boot from.

More recently, I used the 40GB disk to try out Windows 7 64-bit – first the Beta then the RC. All went well until my first “black screen of death” crisis. That sorry tale is recounted here. I blamed myself because I had meddled with the permissions on the Vista disk, but that was only to add permissions which seemed to have been “taken away” somehow without my intervention, making files inaccessible over the local network. I am starting to wonder whether Windows 7 was responsible in some way for messing with permissions on the Vista drive.

To my mind, an OS should not be making automatic file permission changes on other drives on the system. I’m not sure why but I suspect Windows 7 does this. The first black screen crisis was resolved when I booted in Windows 7 and could see that the Vista disk had been stripped of permissions. I added them back manually from within Windows 7 and was then able to boot back into Vista.

A second black screen crisis happened a couple of days ago. I had (as on the previous occasion) booted in Windows 7 to play around with a few 64-bit apps. I tried to uninstall an older 64-bit app but Windows 7 refused, claiming it could not locate the original MSI file. I then tried to return to Vista only to find I was back to my black screen of death. Worse, I could not get back into Windows 7 either. That would start to boot then spontaneously restart, causing a never ending loop.

I was forced to do a clean install of XP on the 40GB drive. I had no important data on that drive so it wasn’t an issue.  I could then see all the files on the Vista drive, so as a precaution copied around 200GB of data to my 1TB external drive. I did notice all the files came across with the read-only flag set, which seemed odd. As Vista continued to prove unbootable, even in safe mode, despite hours of Spinrite and other attempted solutions, I decided I would use XP as my main working system for the time being so I started installing apps and device drivers. I also wanted my data available on the network so turned on file sharing. I noticed that when I shared the Vista drive it took a very long time and gave me a message about writing permissions. That got me wondering. I tried booting in Vista and of course it came right up as if nothing had happened.

As I was coming to realise, it was a variant on the permissions problem which had stopped Vista from booting, and the act of sharing the drive had restored the required permissions.  It is though very worrying to think that Windows can so easily get itself locked into an unbootable state like this, with no eay way for the user to diagnose and no solution that does not involve fixing the unbootable disk via a second OS on another drive.

I am hugely relieved to be up and running again, but extremely suspicious of Windows 7 and whether it has tendencies to make unwelcome interventions in other drives on the system, potentially jamming up other OS’s which may be installed on them. Well, for now at least Windows 7 has gone. Hasta la vista.

AddThis Social Bookmark Button