Anyone interested in learning more about computers might enjoy ‘Code’ by Charles Petzold. I’ve just finished it, and found it very readable.
It sets out to be a beginners guide to how computers work, but without all the cute analogies and pictures of 1′s and 0′s in pidgeon holes that seem to crop up in other texts like this.
It probably helps that I first encountered the author as my introduction to programming Windows. As I type this I’m unsure if I ever read all of his classic ‘Programming Windows’ (I was a student when I needed to, and probably borrowed it), but I certainly read large chunks. It has a clear, no-nonsense, style I enjoyed.
All you really need to understand to follow Code is how a relay works, and he explains that from first principles. He then works up to laying them out by the thousand to produce a computer recognisable today. One interesting observation is that much of the technology needed to create a computer was around a hundred years old before someone assembled one we would recognise. There’s a different path the world might have taken, if that had happened earlier!
Some time ago, I stopped following the ins and outs of Windows development. I keep wondering if I will ever return, but it hasn’t happened yet.
I still see echos of the work the DirectShow team did in the 1990′s (I’m aware they were building on the work of others), and today I stumbled on this update from Geraint Davies, one of the original architects.
It was nice to learn what happened next – thanks Geraint!
I finally got caught up with wiring in several recent additions to our main TV. I needed to replace a 5 way ethernet switch with an 8 way, in order to keep them connected. At some point in the last few years, everything entertainment has grown an ethernet socket. Buying the 5 way felt outrageously advanced, only a few years ago!
The technical among you may have noticed I use the ‘WordPress‘ package to host this blog. As I noted a long time ago, this was largely because the folk behind it seemed to be respectful of the fact that URLs are part of the human interface to the web.
I’ve been a happy user of WordPress for a few years now, and I enjoy the new features they’ve added in that time.
However their basic position is that the only way to get security patches is to stay on their latest release. This is problematic. I’ve invested considerable effort in integrating this blog into the rest of mcaleely.com, by creating a custom theme. Sadly, the WordPress team don’t appear to claim to maintain the APIs that themes talk to in a stable fashion. Every time I upgrade, I’m expected to review (At least – at worst, I must re-do) the technical work of creating a theme. This is non trivial effort, but apparently this time of mine is not important enough to the WordPress team. If it were, I think they’d nominate stable API releases, and provide security patches for them. Otherwise I find the claim that I can upgrade with a ‘known amount of work‘ niave and mildly insulting.
I’m finding the fact that I’m required to do this work for a time critical security patch on a Sunday evening just plain annoying.
Unless this attitude changes, I’ll have to shop for a new blog provider. Any suggestions?
I’m now about half way through my sabbatical year, so I thought a progress update would be in order. You may recall that I wanted to see if I could do two things:
- Integrate more cycling into my habits.
- Find out if I have the capacity to start my own software company.
Taking the cycling first, I haven’t much. Indeed, I cycle as infrequently as when I had a full time job. An early start has fizzled out, and my main activity has been to watch this year’s Tour de France. However, I got a nice new cycle computer for my birthday last week, so perhaps the trick of ‘new equipment’ will get me going (it has worked in the past).
On the software company front, I have made more progress, although I don’t claim to have a going concern yet! I have formed Transmission Begins, and developed its first product, My Own TV Channel. This is now just starting to be used by people other than me. It’s well received whenever I discuss it, so my current plan is to improve it somewhat and then focus on building a service business around it. The software itself is available for download with an open-source licence.
Inspired by my encounter with the Miro team, and mindful of a need to broaden my skillset beyond client software, I’ve been busy the last few weeks. One comment that was made at the Miro presentation was that most of the channels are hosted over plain http, and make no use of the bittorrent client in Miro. In the pub discussion afterward, we seemed to conclude that bittorrent server software was still too hard to use.
Curious, I started looking around. Most of the bittorrent software I could find was limited in some awkward way – perhaps implemented in a less popular language, or designed to handle the needs of the high traffic pirate content servers rather than small providers of their own content. Two services stood out: Amazon’s S3 service lets you turn any hosted file into a torrent by adding the ‘.torrent’ extension to its URL, and the Miro Team’s Broadcast Machine did all the torrent generation server side, on your own server.
However, Broadcast Machine is no longer supported, and S3 leaves you needing to create an RSS feed. I’ve therefore been busy implementing a bittorrent server that can be hosted at any domain that supports PHP and MySQL. If you can install WordPress, I intend this software to work too. It can create a .torrent for any file already on your server, and then include it in an RSS based channel feed, ideal for clients like Miro.
I’m looking for a few beta testers to see if this software works outside of my own test set up. If you want to host some video content (perhaps you already post them to youtube) on your own domain, and you are familiar with installing software like WordPress there, you would be an ideal candidate. It would also be useful to see how multiple downloads work, so if you already use a torrent aware RSS reader (Miro is one), or would like to, please get in touch.
Feel free to email me (email@example.com), or post a response to this blog entry.
Incidentally, selling this software is not my business idea. This is BSD licensed open source.
I recently rummaged through my loft, and found my collection of Psion PDAs. I’ve got fond memories of these, and there is no way I would part with them. Or so I thought. On review, I had no less than seven of them, including many duplicates.
So, its off to eBay with some of them:
If you fancy buying one, you could always install some of my software!
Other internet video products have frustrating limitations which mean I don’t use them very much: Perhaps the files can only be watched for a few hours; I’m limited to watching programming that can sustain a large technology infrastructure or I have to put up with muddy, low quality, pictures. Often they are just incredibly complex combinations of technologies and applications.
Miro eliminates all these gripes, and I’ve been impressed by the experience of using Miro on my TV over the last six months or so. I’ve tried to write up some of the reasons from a professional perspective over the last few blog entries: Miro respects my own honesty; respects the authoring effort of the people who create video; allows people to publish at low cost and is easy to understand and use.
There’s another reason I like it though – it has become easy for me to download and watch some really high quality video on my TV I wouldn’t see elsewhere. Right now, Miro claims to have more HD content than similar competitors, and it looks great!
I’ve not seen a better way to watch video on the internet.
Miro makes Channels a central part of its user experience, using the same technology as a blog. Having chosen not to offer instant playback video (unlike, say, YouTube) I think that the metaphor of a channel to helps me to understand what I will see after waiting for a download to occur. The TV channel metaphor was easy to grasp, since I’m often asked to subscribe in some way to a channel on my TV. Using the technology behind a blog (syndication feeds like RSS), it makes me consider a flow of new videos in the future, again like a TV channel. By using bandwidth friendly downloading, it can allow a channel to make the promise that the download will be better quality than a live feed.
While it is running, Miro is capable of downloading in the background without impacting the playing video. Therefore it’s often my experience that once I’ve watched one video in a channel, the next has downloaded. By leaving Miro running on the computer attached to my TV, there are also always downlaods that have completed while I’m away. As such, whenever I want to watch channels in Miro, there is something to view. In practice, this means that when I encounter a new channel, I hit the subscribe button, anticipating I will be able to watch it next time I sit in front of the TV.
As an aside, downloading before viewing has another advantage – playback is far more reliable. Most of the internet live feeds I’ve used experience breakup and dropout, making them unpleasant to watch. Miro never suffers from this, which is great.
Whilst I’m generally sceptical about copying the user experience from traditional TV’s and HiFi’s, the channel as blog metaphor seems to work well for Miro.
Hosting video (or any large file) on a webserver has a problem – when a moderately large number of clients want to download it simultaneously the overhead of each individual connection can overwhelm the server. The number of people that can be serviced is quite likely to be lower than the audience for any popular file, and waiting an unpredictable time for the server to become free is a frustrating experience for the viewer.
There are several possible solutions to this:
- Multicast IP
- Hosting on multiple servers via Mirroring or a Content Delivery Network (CDN)
- Collaborative (peer-to-peer) downloading
Multicast IP allows the server to share a connection among many clients, but for various reasons is not available on the public internet so needs to be discounted. Hosting on multiple servers is straightforward, but is costly and out of reach of individual authors.
Collaborative downloading allows the author to require each viewer to also act as a server for that file. In this way an ad-hoc multiple server system can be created, with costs split between the author and each viewer. Whether your viewers will be happy with this probably depends on what you charge them, and what they get in return. Most pay-per-month internet connections allow them to make a useful server contribution at no direct financial cost to them.
A popular collaborative download protocol is BitTorrent, which is included in Miro. An author distributing video to Miro (or similar) viewers can therefore choose whether to deploy multiple servers, or rely on viewers to collaborate as downloads occur. The ability to broadcast without investing in a network of servers should make it materially easier to distribute video from small providers on the internet, in a similar way that blogging has brought publishing words within an individuals reach.