Buy a Smart TV. Or Make your own that does more for less?

(I'm not the first to write on this subject, I won't be the most informative either, but I need to get back into the habit of semi-technical writing so excuse this indulgence...)

New Year, New Minor Project

My father, bless him, decided a bigger TV was in order. He decided to get one that fits into the category "Smart TV" and, I won't deny, it's a clever box which can stream from internet and local network sources a variety of content provided the usual boxes are ticked about compatibility, codecs etc etc...

His estimate was this added a premium of £50-100 on top of the "dumb" TV cost for the same size. But insists the choice was down to picture, size of screen, thinness of frame. And I believe him...

Anyway, this freed up their old TV for which no in-house use could be found. So we brought it home with us. Now, what to do with a 32" 2007-vintage LCD...

Motivation, or Prime Cause

Back in the day, this section would have read "Because I can". But I'm getting older and (even) lazier these days, and even though something's ostensibly cool I still need to see some personal value before attempting - the range of stuff available today exceeds my goldfish-like attention span and, mayflower-like, expires before I can get around to it. That's enough cliched metaphors.

We've got a MythTV box next to the lounge TV, and have had it for 6 years. The biggest vote of confidence I can give it - and a mark of it's utility to the household - is that I haven't dared upgrade or replace it since a one-off upgrade in 2009, such is it's value. Nearly everything we watch is through the Myth box - one of my proudest parenting achievements is that the kids pretty much only get to see Adverts when they stay over with grandparents. Doesn't say much for my parenting skills, but at least I picked a winner with the Myth box.

However, the kids are older and we're down to about an hour a day when we can watch stuff WE want to watch without their comments or interference. Bit of a problem when it's a 2-hr Swedish Jumper Documentary masquerading as a crime thriller. 

As it's Myth'd, we can watch - separately - on our computers. But it would be nice to have a second spot in which we can BOTH watch something together, away from the kids...

Open Source Solutions

As an admitted casual dabbler in these matters (as I said, I've had no need to pay attention to the field since 2009...), I've been aware that XBMC has been around, and a sort-of competitor to my beloved Myth for quite a while. You won't travel far on t'internets looking for open-source media centre solutions before XBMC is mentioned, and you'll come across it far more frequently than Myth. 

Actually, the two solutions complement each other and take opposing approaches. Myth concentrates on bottom-up - being an excellent recorder, archiver, file manipulator box with (subjectively) a weaker front-end user interface. XBMC concentrates on being the best possible playback solution possible, with (subjectively) weaker capture and management capabilities. 

So rather than being competitors, per se, it makes sense for the well-equipped home network to have one of each (or, more likely, a MythTV server capturing and collating video, and a network of XBMC front-ends playing it back). 

This fits from a cost & power perspective too: a Myth box needs some horsepower (mainly for transcoding though - capturing video streams is fairly lightweight these days), plenty of storage and some expansion capability to host capture cards etc. XBMC, on the other hand, is a close approximation to the classic Thin Client model, needing modest hardware for playback & the user interface, and only enough storage to hold the OS and some metadata about the content available on the network. 

Enter Raspberry

Most intriguing of all are the results of the experiments of the hoards of bedroom coders with their Raspberry PI boxes. This is a remarkable little box - the power of a 8-9 yr old desktop machine combined with the hackability of a 80's era ZX Spectrum all at a (let's face it) disposable cost of £25 a pop (i.e. cheap enough that when you do make one go "pop" and release it's magic smoke because of a mis-wired GPIO experiment, you won't be sobbing for too long before managing to afford a replacement). 

Even better than this, the wonderful geeks have turned the whole thing into a pretty-much plug-and-play solution. I shall document it pretty fully here:

Build Your Own Smart TV

The ingredients:

• A TV. Preferably with a HDMI socket, so something newer than about 2005 or so in a LCD format would be preferred. Bonus points if the manual mentions CEC or the manufacturer-proprietary renaming of such (VIERA Link etc etc).
• A RaspberryPI. Model A or B will do, B probably works a bit better (more memory) and would be mandatory if you're intending to use a wired ethernet connection.
• SD Card. 4GB minimum, 8GB or up preferred
• USB WiFi Dongle. If you're not going to use wired Ethernet, that is.
• HDMI Cable. 1M or less preferred. Substitute with RCA if TV has no HDMI, but then you'll need to do something about Audio too.
• (Recommended) A 2-a 5V power supply for the Pi. You may be lucky and be able to use a USB output on the TV to power the Pi, but (certainly for a Model-B) a dedicated power supply is much more reliable especially when using a USB Wifi dongle.
• (Optional) A TV Wall Mount Kit. Best for space saving installations.
• (Optional) A case for the Pi. Not required, but recommended - some of the components on the Pi are vulnerable to being knocked off or damaged by mis-handling.

Minus the TV and wall-mount kit, the parts required should be around £50 (Total manifest for a Model-A kit with all optional components, from RS linked above, comes to £52) - less if you've got spare bits already like SD cards and various cables. This is around the "Smart TV Premium" level, not bad for DIY component solutions in this day of mass-manufactured discounts.

I also note that if you're intending to play back "native" recordings from MythTV obtained via FreeView / FreeSat recordings (i.e. in MPEG2 video format), you'll want to obtain a hardware decoder licence (MPEG2 Licence Key) for your Pi from the RaspberryPI shop. This will add £2.74 to the parts cost.

The Recipe:

1. Take the SD card from the Pi and insert it into the nearest available computer. 
2. Go to the New Out Of Box Software (NOOBS) Download link of the Pi site, and get a copy of the latest offline installer (~1.38GB, so get a grown-up internet connection to help you with this step. Alternatively try the net installer - "NOOBS Lite" - for smaller size, especially as we're going to only use a fraction of the software for our solution )
3. Follow the instructions to format the SD card and put NOOBS onto it.
4. Plug the Raspberry PI into the TV, attach the USB dongle and a spare USB keyboard (only needed during build & configuration). 
5. Insert the SD Card into the PI, attach power, and wait
6. At the prompt, select to install OpenELEC
7. Reboot into OpenELEC & configure for your local environment. I'd recommend doing an update (System -> OpenELEC -> Update) to get the latest updates first, then doing configuration
8. Don't forget to do a library scan to pickup metadata about what's on your network. Not absolutely required (you can select by file) but makes the interface so much nicer and quicker to navigate.
9. Follow the instructions on the XBMC Wiki to configure MythTV as a Backend to XBMC

That's about it, really. I've elided a few details you can find for yourself, especially using the XBMC Wiki, as they'll be installation dependent but as a reference I got through steps 1-9 in about 90 minutes elapsed attention-span (omitting some longer delays for download time), and ended up with the following installation working well (see below for limitations and caveats) with about 8 hours total effort (3 of which were fitting the wall-mount kit for the TV):

For the Avoidance of Holy Wars...

NOOBS includes 2 Media Centre solutions. Firstly there's a full-fat XBMC install at pretty much current specs, about 2GB space required. I tried this, it seemed to work OK but the Pi add-ons (in particular the Web Browser) didn't sit right with me. After trying one - the Web Browser - I was unable to reboot the Pi back into XBMC because it'd cocked-up one of the boot loader files. This, along with the rather long boot times for XBMC, persuaded me to instead try the RaspberryPI-optimised OpenELEC build of XBMC which is also included in NOOBS.

For my money, it's lighter weight (therefore better fitted to the Pi), boots faster, and has all the features I can see myself wanting from a front-end, so whatever I've lost from the full-fat XBMC I won't miss. It's also survived several test "pull the plug" reboots of the Pi so far (a scenario tailor-made for SD card corruption). Your mileage may vary, choose as you will.

Controlling the Pi

One point I've missed so far is how to control XBMC once you're all installed. Several answers are available.

• The worst option is to keep the keyboard fitted. Even if you've got a wireless keyboard (or a bluetooth one with dongle), I wouldn't recommend it - XBMC does work and everything can be selected from a keyboard, but it's just not made for it. 
• Probably the cheapest if not most effective solution is to use the TV's own remote control. If your TV supports CEC, you should be able to use it to control XBMC as there's a CEC module built in. Despite my TV, Pi and Remote all claiming to support this (via Panasonic's "VIERA Link" rebranding), I've been unable to do so. I suspect either a non-compliant HDMI cable or (more likely) the TV's too old to properly support the full protocol.
• For those of a hacker bent, there are GPIO-based IR Blaster solutions for the Pi to use existing or dedicated remote controllers
• But by far the coolest option is to use either an iOS or Android Smartphone to obtain full control.  Both the official iOS XBMC App and the official Android XBMC App act as (very) smart controllers over your WiFi network, allowing search and direct selection of media from the app to playback on XBMC. 

If you don't like the official apps, others are available particularly on Android. The Yatse app works particularly well on my Nexus 7 tablet, for instance.

Caveat Implementor

One point I've omitted to mention so far is that as it stands it's all great and everything works with one exception: Because my Myth box is so old (v0.21), although XBMC can connect to it, find what channels it's got, what's recorded and what's scheduled (and also, presumably, schedule new recordings although I've not tried it) there's one limitation:

It won't play anything back from the Myth box. I can find it, select it, but when I look at the log I see the XBMC box is asking for recordings that the Myth box is refusing to admit exists. Ditto for watching LiveTV. I suspect a mis-match in protocol versions solved by upgrading the Myth box, but it'll be a while before we attempt that.

(I can't just upgrade Myth as the box is so back-level even apt-get update fails with unknown / retired repositories. So it'll need a re-build. Which will mean losing the database and all the recordings. Of all the Xmas stuff. So I'll need to transcode them first, or convince the family to watch them and delete them. Either of which will take at least a month....)

Ah well. In the meantime, there's always the ability to run BBC iPlayer on it...

Art, or something like it

Took the nice shiny SLR along to the Petersfield Fireworks display last night after reading a bit about some tips and tricks. Couldn't use all of them - mostly because the best tips required a tripod, remote-release and (preferentially) a very wide-angle lens, none of which works well in a crowd of 3,500 other people.

So the best of these shots are 1.3 second long exposures, at low ISO numbers (100-400 as I phaffed around), and f/9-f/10. All used manual focus. Despite the obvious hand shake, I'm very happy with the way these turned out....

iOS6: Panorama mode against Microsoft Photosynth

One of the stand-out features Apple promoted with iOS 6 is a new Panorama mode in the Camera (available on "all dual-core iPhones and iPads" - effectively only iPhone 4S and 5, and the retina iPad).

I'm interested in this because for a couple of years now I've been using the actually quite excellent (you've no idea how much it pains me to admit that) Microsoft PhotoSynth app to capture panoramas.

Functionally, there's no point in performing a comparison: PhotoSynth can take full 360-degree horizontal and vertical panoramas and can post them online using a viewer app that corrects for distortion and allows for interactive display. Whereas the iOS native functionality just captures a horizontal 180-degree strip as a single wide photo. So there's no way I'd ditch PhotoSynth just yet anyway.

Having said that, though, I am still interested in the technical differences: Very often with PhotoSynth the choice of stitch points and overlaps is less than perfect (or in English: You Can See The Joins). I've used this a couple of times to deliberate effect (a favourite of mine being capturing a helicopter taking off twice; less favourite being the appearance of my daughter no less than 8 times in a single panorama), so it's a Bug that's also a Feature. But it makes casual use harder.

With Photosynth, the gyroscopes / position sensors are used to detect the orientation of the camera; when it's moved sufficiently outside of the current frame another shot is taken (with plenty of overlap). For mostly horizontal scans this works well enough (although one does have to remember to only rotate the iPhone and try and avoid moving one's body or even just arm in an arc). The orientation sensors work less well taking deep vertical shots and tend to mis-align shots straight up or straight down, although the app's tap-to-take feature mostly allows one to work around this.

The iOS app works by just getting the user to follow a horizontal arrow across the screen held in portrait mode from left to right. There's no discrete shot-taking going on, it operates more like a video mode. As long as one rotates at the correct speed and keeps the camera horizontal, the shot works. Attempts to move or rotate the camera vertically either abort the panorama (big moves) or just clip the top and bottom of the vertical movement (small moves): the end result is always just a horizontal panorama with centre point and height determined by the starting position.

So really the only meaningful technical comparison that can be made between the two techniques is to compare the accuracy of the stitching and the compensation for focus distance and exposure across the apps.

I captured the same (or nearly so) 180-degree panorama sat on a bench outside my local leisure centre yesterday on a bright sunny day, moving from down-sun at the start straight into the sun at the finish. Because of orientation glitches and PhotoSynth's auto-start, I've had to crop the PhotoSynth panorama at top and bottom to reflect approximately the same strip as the iOS Panorama. As I took my time with both apps (particularly PhotoSynth which I more normally use in a discrete rotate-shoot-rotate movement), there was less difference in the results than I was expecting (or in English: I got better-than-normal stitching from PhotoSynth this time). But what I do find interesting is that both modes of panorama have considerably more softness to the results than I was expecting.

Here's the PhotoSynth capture (Scroll right for more of it):

Taro Leisure Centre 2012-09-21; Microsoft PhotoSynth, cropped to close to iOS Panorama output dimensions

And here's the iOS Panorama (pretty much untouched from as-taken):

The Same, only taken with iOS 6's Panorama function

My verdict (yours may vary): iOS does a better job of blending the frames together (there's some obvious exposure differences in the PhotoSynth example whereas the only obvious example on the iOS panorama can be explained away as Lens Flare if one's of a mind). Focus is also sharper in the iOS photo, although to be absolutely fair I may have over-cropped the PhotoSynth example and we're seeing some interpolation instead. I prefer the colour balance and exposure of the iOS example except for directly into sun which is better handled by PhotoSynth (which is taking multiple shots so can adjust the exposure to suit).


I don't have a conclusion: I thought I'd ignore iOS Panoramas as they're nowhere near as versatile as PhotoSynth, but the difference in quality is enough to make me reconsider for certain use cases.

£0.02 on the Latest and Greatest Software from Apple

Everyone else has an opinion, here's mine.

Upgrading both the Mac (OS X 10.8.2, iTunes 10.7, iPhoto 9.4) and the iPhone (iOS 6) at the same time was a mistake. It's made determining which side of the equation is glitching harder.

I did both late last night, so this is preliminary. In particular I may be mis-assigning glitches:

OS X 10.8.2

1. I got prompted on login to supply a password for "Back To My Mac". I've never enabled that before, so this was a surprise. Not as much as being told I was using the wrong password over and over though (As it's the same iCloud account that works for everything else....)
2. Attempting to change an iCloud account setting caused System Preferences to hang. Killing it and launching again got a pop-up about changed terms of service. And "Back to My Mac" now enables (although it doesn't appear on icloud.com; should it?)
3. Facebook integration's a bit intrusive, isn't it? 

iPhoto 9.4

1. Seems to have improved performance over previous versions; it navigates faster than the previous point-release on my library, which is welcome
2. Not sure if PhotoStream agent is working; I had to kill the previous incarnation due to it sucking up bandwidth during the patch download, even though it was uploading photos. Reboot / relaunch and the new agent is sitting there idle making no attempt to upload. We'll see, we'll see.

iOS 6

1. iCloud settings appear to have gotten messed up a bit: Reminders weren't syncing to the cloud. I thought that was a Mac problem but changes/updates made on the iPhone weren't appearing on icloud.com either. If you're affected, disabling the service (Settings -> iCloud -> Reminders OFF in my case) then re-enabling seems to cure it
2. Maps is hopeless, isn't it?
3. I'm mightily annoyed that Podcasts have completely disappeared from the iTunes Library. I've got the Podcasts App, and the latest version is moving closer to working territory but for years I've used a smart playlist in iTunes to manage what and how I go through Podcasts and now that doesn't work.
4. Whilst Podcast loss on the phone itself is irritating, it's a real blow to me using it in the Car: my car's iPhone integration pulls across playlists from iTunes on the phone. So now I've lost that, and if I'm lucky the override "just act like aux in" option will let me use the podcasts app as a substitute.

iTunes 10.7

On balance, most of my issues with this update lie here, particularly with syncing:

1. Photo syncing got mightily screwed up. On first attempt I ended up with duplicates of about 1,000 random photos in the iPhone's library. Not stuff that was also on PhotoStream, stuff that's older than that. Had to turn off all syncing, which left me with only the "orphan" duplicates, then sync to a blank directory to wipe those, then turn iPhoto Library syncing back on. 
2. Even after this, I've got 20-30 phantom Events appearing in iTunes's Event List. I sync "last 3 events" plus some favourites and this is now broken because I have 10 entries saying "20 Sep 2012" with no photos in (all newer than the latest actual events in iPhoto itself). I don't know what got messed up but I've checked and there's no empty events in iPhoto... Doing  Repair Library in iPhoto doesn't seem to fix this either.

3. Similar sorts of Orphan Data glitches with Music syncing. e.g. my Voice Memos are set to sync, but don't appear in the library any more. I've turned OFF Music sync to wipe the library and start again, and I've still got (empty) playlists on the phone.
4. After initially contacting but not completing a sync (for some reason), WiFi sync just flat out would not work last night. This morning it's back again. My best guess is that the uPNP port assignment magic got screwed up on my router; it's got a time-out for all that so leaving it for a bit sorted it out. 

Edited 2012-10-02: iPhoto '11 9.4.1 update, just applied, fixes the phantom events problem nicely.

Done a bike ride.

Inspired by @ChateauGateaux's epic rides and prodded not too subtly by @henleysmissus to do some sodding exercise, I took to the bike this morning. Several things were learned:

1. 6 weeks is far too long to leave between rides...but...
2. The difference between "less unfit" and "very unfit" is state during and after the ride. I still average 20km/h.
3. I still don't have my seat position correct (oww...)
4. East Hampshire has become less flat in the last couple of months
5. There's a LOT of East Hampshire I've never seen, even after close-on 20 years here
6. There's a lot more military presence within 10 miles of my house than I was aware of
7. Our country lanes suffered a lot with the poor weather this year
8. They're still suffering from some odd drilling and other maintenance activities leaving crud all over the roads
9. Just because someone in a 4x4 on a tiny road nearly runs you over doesn't mean they're a bad man. He even pointed me in the right direction at a crossroads.
10. My god it's beautiful out there.

London to Brighton After Action Report

I had the great pleasure of riding the London to Brighton bike ride organised by and with fund raising on behalf of the British Heart Foundation.

My main motivation for doing it was simple - Friends have done it in the past and enjoyed it, and Patricia did it last year and, frankly, I was jealous and eager to have a go myself. So we did a deal, and used her priority booking as a result of the money she raised, entered her and then swapped for me.

So I've known since January that I'd have a ride (places are limited, despite there being 27,000 of them), and I've had every incentive to prepare. For I am not a fit man, I work at a desk and I have no idea what most gym equipment does let alone any inclination to use it.

I've been riding most weekends since the end of January, starting with some depressingly short rides but ending up at a respectable 40-50KM in a couple of hours or so. Sadly conditions have conspired to keep me out of the saddle for a couple of weeks now, but I got a little warm-up done last night (and I needed to warm up as I got drenched going to the station) cycling 11KM from Waterloo station to the hotel I'd booked into in what was laughably described as "Wimbledon South" but resided at the end of Balham high street. If you're ever tempted to try this route, a word of advice: cycle lanes are respected in central London but the denizens of the suburbs treat them as parking spaces and 3-point-turn overflow points. Scary stuff.

So I woke this morning feeling a little apprehensive, but quite excited that today's the day. Thankfully the weather had improved - the wind dropped, and the sun came out (so much so I've got sunburnt arms, not that I'm complaining). 

A quick note to Mon Pere to say Happy Father's day, an adequate breakfast shared with several other riders sharing the same accommodation, and off we go. 15 minutes back up Balham High Street and I arrived at Clapham Common, along with several thousand other riders. Despite appearances it was very, very well organised with big entry lanes complete with start times (riders go into 30 minute blocks, with first come first served through the block). I had 20 minutes or so to wait, and enjoy the spectacles laid on like jugglers, one-man-bands and stilt walkers.

I made it through the start gate at 08:53, and saw my first puncture 50M up the road. Poor fellows; that must be disheartening. Over the next 50 minutes I got as far along (via a more triangular route) as crossing the same road I'd ridden up the previous hour, which was dis-heartening. Although the mood of all involved was good - a real festival atmosphere percolated through the day - an hour or more of this stop/start and crawling along drew groans at every new traffic light. We wanted to cycle, not push bikes.

It took me about 90 minutes to get to the same rest-stop as Patricia used last year, at the 18K line. A quick piddle, some phaffing around to raise my sagging seat, a bit of banter with others using the facilities and off I went again. 

Things went much better - or rather, faster - from here on. I don't have much to say about the next 25KM other than I enjoyed the ride, it's the English Curse that as soon as the rain stops and the sun comes out the pollen rises and the itchy eyes start, and DEAR GOD why do all these people get off and walk at the slightest incline? 

I arrived, a little unexpectedly if I'm honest, at the halfway point (the Hedgehog Inn outside East Grinstead) moments after 12. I was feeling great, I'd done 42KM, the sun was out and the biggest and greasiest bacon cheese and egg burgers you've ever seen were on sale. 

Took a nice 30 minute stop here to load up on grease and water and enjoy the sights. Including Batman, Robin and Superman, funnily enough.

Fought my way out of the rest stop, past the crowds of drinkers (really? I mean, I like a pint but with ~30 miles still to go that was never going to happen), and pushed on. The GPS's next waypoint was set to the top of Ditchling Beacon, 29km as the crow flies. The next hour or so wasn't so bad, although it was noticeable that I had less in reserve going up inclines than I had in the morning; the effects of this were masked by the preponderance of people walking up the hills and causing road-blocks at the top where there was inevitably a refreshment stop with accompanying traffic going in and out to add to the confusion. 

But after 90 minutes or so - around about 2pm - and as I went through Heywards Heath, about the 60KM mark and notably 8KM past my longest training distance, it became clear that I was (not to put too fine a point on it) knackered and suffering. The old legs weren't playing ball, my arse was in agony from the seat, and the heat was causing a headache despite getting through several litres of water. 

Not long after I had one of those fantastic moments of Random Kindness thrust upon me, as an older geezer pulled alongside and berated me for having a badly-adjusted seat. He pointed out the nose was raised, and that must be agony (how perceptive). I replied that I'd tried adjusting it and it only went fore and aft, not up and down. He insisted he knew how to fix it, and pretty much forced me off the road to demonstrate. Out came his surprisingly complete toolkit, and by extensively loosening the seat post bolt he showed convincingly that it's easy to rotate the seat up and down, as well as fore and aft. With the seat now firmly nose-down, and with my eternal thanks ringing in his ears, this made one hell of a difference to my nethers, with blood swiftly returning to parts I'm perhaps over fond of, and the adjusted position aiding my pedalling as a bonus.

However, this effect wasn't a magic panacea, and as the South Downs hove into view I was clear my underlying problem hadn't vanished. The route heads due South from Heywards Heath, and it's mostly downhill until one arrives in Ditchling village. Then it's not, any more. The little and minor uphill sections through and immediately after the village proved really hard work, so at the last stop before the hill I collapsed in a heap, ate half a packet of jelly babies, swallowed more water, and took a good long rest. 

But that wasn't going to crack the hill, so eventually I decided to have at it. I got a couple of hundred metres into the hill proper, and then hit my first snag: dropping from 2nd to 1st gear jumped the chain over onto the spokes, twice. Much cursing ensued. I got a bit further in 2nd and then successfully into 1st, only for the chain to slip on 4-5 occasions. This caused a bit of dispair, and I hopped off and walked. After some cursing and percussive maintenance (observed in humour by a very fit but not stupid gent carrying his single-speed racer up the hill), I had another go in 2nd gear. I got another couple of hundred metres, but again attempts to use 1st gear proved futile. That was it, my legs were shot and I was (if honest) somewhat despondent. I dismounted and pushed the bike about 2/3 of the way up to arrive feeling a bit of a failure at the summit.

There's not much more to report: the remaining 12KM or so of the ride from Ditchling to the finish line are all downhill and flat, and the only incident of note was that 7th and 8th gears in top didn't want to play, and freewheel wasn't really working. On reflection, I was resting my bike on the wrong side today - gears down - and I somewhat suspect I've dislodged or otherwise affected the positioning of the derailleur gears.

I arrived at the finish line down on the seafront at 15:42, 6 hours and 50 minutes since starting. It was very good to finish, a little disheartening to do so on my own (we'd agreed that getting wife + kids to the centre of Brighton was, logistically, foolish so it wasn't a surprise). But in glorious sunshine, on a fantastic day, with the marvellous company of similarly inclined strangers I'd ridden twice as far as I'd ever managed in a day, raised a lot of money for the BHF, and generally - despite the setbacks - had a great day out.

The fact that it took me another 45 minutes to get from the finish line, past the pier and along the seafront to Hove Tesco is incidental. The hair I discovered on removing my hat (I'd deliberately kept it on all day) provided what I had hoped would be the "money shot" of a daft final appearance to amuse or at least confirm the suspicions of my friends and acquaintances:

Patricia and the girls picked me up soon after, having spent the day on and around the beaches of East Sussex geocaching, eating ice-cream and throwing frisbees. Kate managed the shortest time ever from getting out of a car to showing her father with kisses, hugs and a big bag of Father's Day goodies which was very welcome but a little out of place.

The minor coda to this tale is that, through faulty memory I was sure I'd beaten Patricia's time by about 5 minutes - a technicality really since she cycled up Ditchling Beacon which is a win by default - however on comparing GPS tracks I see I'd badly mis-remembered, and was never in the running: she has a good half an hour on my time; partly through making shorter stops but mostly because she's actually fit and healthy and I'm not.

Finally, I would like to take this opportunity to publicly thank all of the people who I badgered, pestered, annoyed and cajoled into supporting me in this endeavour. Without your assistance, I'm not sure I wouldn't have given in at Heywards Heath, and the motivation of a bunch of people willing to stand behind actual money in their confidence that you can do it is a great push to get one across the finish line. Thank you all, gentlemen and ladies, I really mean it. 

Thank you, Shelly. Thank you very much, Dave. Big thanks to Rich not only for the financial support but also for the fantastic advice and guidance and benefit of your experience. Thanks to Tony, to Brian, to Bode, to Nick, to Paul W and Paul P, to Len and to Dave - all of whom go to show that great colleagues shouldn't be taken for granted and will always support you if you ask them. Thanks to Helen and to Simon for showing me that old friends don't mean distant friends. I owe you all an enormous debt of gratitude. Or failing that, beer.

Now it's time for bed.

Charitable Begging

At the risk of sounding like a stuck record about this: I'm doing the London to Brighton Bike Ride this year on 17th June, and any sponsorship in aid of the British Heart Foundation would be very, VERY gratefully received.

For more information please visit my fundraising page:

http://uk.virginmoneygiving.com/MatthewExley

Many thanks.