1888: Put the Phone Down

I'm coming to detest my phone, not necessarily for what it is, but for what it's done to me.

I don't specifically mean my actual phone, either; more the general concept of smartphones and the "always-connected" nature of modern existence.

I don't even specifically object to the "always-online" nature of modern society, more the habits — or, more accurately, compulsions — that it tends to instill in people. I've become very conscious of my own compulsions in this regard recently, and I'm making an effort to try and change my habits.

Here's the problem for me: picking up a phone and fiddling with it (usually checking Twitter and/or Reddit) has become a default thing to do if no better activity is available. Phones are great for that; with the wide variety of apps available these days, there's something sure to distract and entertain even the most attention-deficient individual, even if only for a few seconds. That "even if only for a few seconds" thing can become a problem, though; the fact a phone can fill an empty few seconds easily means that it's easy to reach for it while you're in the middle of something else, breaking your concentration and perhaps immersion.

I became particularly conscious of it while I was playing Criminal Girls the other day. (Side note: I've now completely finished that, so expect a comprehensive writeup on MoeGamer very soon.) I noticed that even mid-battle, I was reaching for my phone and fiddling with it while animations were playing, or sometimes between turns. There was no good reason for it, either; I wasn't particularly interested in what Twitter had to say at that moment, and I was genuinely enjoying the game. It was just a nigh-uncontrollable compulsion to reach for it and look at it.

It happens in the night sometimes, too. I can't get to sleep, so I pick up the phone and look at whatever vapid nonsense social media is spewing at any given hour. There's rarely anything meaningful — although there's occasionally an enjoyable late-night conversation with some of my friends in other timezones — and it doesn't really have any value; it certainly doesn't help me get to sleep when I find myself mindlessly refreshing for minutes at a time instead of putting the damn thing down, closing my eyes and trying to disconnect from the stimuli of the outside world.

So I'm trying to stop myself from doing these things. When I'm sitting down to play a game, unless I'm specifically intending on "liveblogging" my experiences as I play, I've started putting my phone out of reach or, at the very least, covering it over so I can't see the notification light and screen. When I go to bed, I've started switching my phone off altogether rather than just leaving it in standby mode. And while a phone is a convenient thing to fiddle with to stave off social anxiety when dealing with other people face-to-face, I'm going to try and make an effort to keep it in my pocket unless it becomes clear that I really am surplus to requirements in a particular social situation. (Not necessarily in a negative way; I may just be along for the ride while others are discussing making arrangements for something or other that doesn't directly involve me, for example.)

I feel like smartphones have done serious damage to our collective concentration spans over the last few years. And I'm quite keen to get mine back.

1847: Your TV Is Not Trying to Kill You

So another outlandish "privacy scandal" looked set to erupt on Twitter earlier. For the benefit of anyone who might be considering sharing anything regarding Samsung Smart TVs sending your personal information to third parties, allow me to clarify a few things.

Samsung Smart TVs have a voice recognition feature. I know this because I have one. (I also never use it, because voice recognition is, for the most part, stupid and pointless when you have a remote control right there. Assuming you have hands, it is pretty much always just as quick to use the remote as it is to remember exactly how you're supposed to phrase a voice command.)

Anyway. The way this voice control works is very simple. You press a button on the "special" remote, not the "normal" one, and the microphone in the remote starts picking up your voice. When you've finished speaking, it sends what you said over the Internet to a speech recognition service (that more than likely converts the speech into computer-friendly text for more accurate processing) and then your TV receives an instruction based on what you said. The TV itself isn't doing any real processing; that all happens remotely, and the TV simply receives the instruction to do something based on what the speech recognition service thinks you said.

Astute iPhone-owning readers will know that this is exactly how Siri on Apple devices works — it's why you can't use Siri when you don't have an Internet connection, even to access information stored locally on your phone such as your address book and suchlike.

The reason these services work like this is to take some of the processing workload off the phone/TV/other device with voice recognition. It's not an ideal solution, but it does mean that the devices in question can be less expensive because they don't need hefty processing power or software to recognise voices pre-installed on them. One day we may have devices that can recognise our voices accurately without requiring an Internet connection — although chances are by the time we've perfected that, the Internet will be "everywhere", rather than just in Wi-Fi hotspots and mobile coverage areas — but until then, this is how voice recognition tends to work.

As such, a necessary part of the entire process involves sending a recording of what you said to the third-party speech recognition service. This means that if you press the microphone button on your Smart TV remote and then decide that the appropriate thing to say at that moment would be "My credit card number is…", a recording of you saying your credit card number will be sent to this speech recognition service. Chances are, nothing will happen with it, but as with any sort of unencrypted information transmitted across the Internet, there's a slim risk of nefarious types intercepting the transmission and taking advantage of it.

Because of this slim risk of stupid people telling their TV remote what their credit card number is, Samsung have had to put a disclaimer in their Smart TV documentation that the TV may send your personal information to a third party, and of course, people have misinterpreted this as the TV always listening to what you're saying, and it therefore being unsafe to share any personal information while within earshot of your TV. This is, of course, utter nonsense, because as I've outlined above, you have to specifically press a button in order to activate voice recognition mode, and the "third party" it's being sent to is doing nothing more than converting your babblings into something the computer in the TV can recognise as an instruction to do something.

That is it. Nothing more. Nothing sinister. And if you're still uneasy, you could 1) not buy a Smart TV, since technology clearly terrifies you, 2) not use the voice recognition function (which, in my experience, is patchy, slow and pointless anyway) or 3) not talk about credit card numbers or other personal information when you've pressed the button that specifically asks your TV to listen to you.

So there you go. This has been a public service announcement. I thank you.

1807: Learnin'

During quiet periods, I've been educating myself in some things that will doubtless prove beneficial to future career plans: specifically, I've been learning about the various languages of the Web thanks to a marvellous site that I remember seeing the genesis of a while back, but which I haven't really delved into until just recently: Codecademy.

Codecademy is a site that truly leverages the idea of interactive learning and makes programming accessible to anyone, regardless of their previous skills. It covers a range of topics, starting at HTML and CSS and working through other useful technologies such as JavaScript, jQuery, PHP, Python and Ruby, and also provides examples of how to use these technologies to leverage the APIs of popular platforms like YouTube, Twitter and Evernote to build your own apps.

There are a number of different approaches you can take through the currently available course material: you can take a specific "skill" (such as HTML and CSS, or JavaScript) and work your way through a series of multi-stage exercises, given clear instructions and the opportunity to immediately see the effects of your work as you go; you can take on a practical project (such as recreating the homepage of a popular site using established Web technologies such as HTML and CSS plus extensions like Bootstrap); or you can do one of the super-quick "this is what you'll be capable of if you stick with it" projects whereby you "create" something impressive like an animated interactive picture by referencing pre-existing libraries that have conveniently been built for you.

So far I've found I've responded best to the structured, skill-based work. These courses take the longest out of all of Codecademy's material, but they provide in-depth experience of getting your hands dirty, and tend to provide enough plausible context for the things you're doing to make them relatable to real contexts. The JavaScript course perhaps didn't go into quite as much depth as it could — I would have liked to see greater exploration of how JavaScript code is integrated into a website, rather than (or perhaps as well as) treating it as an entirely separate and independent language, but at least the course game me a reasonably firm understanding of some of the core concepts, and allowed me to get my head around object-oriented programming a lot more than I have done in the past.

I quite enjoy programming, though I haven't been properly "into" it since the 8- and 16-bit eras, when I used to use variations on BASIC (Atari BASIC on the Atari 8-bit computers, and STOS on the Atari ST) to put together simple games. I fell out of the habit of programming around the time you no longer had to put line numbers in manually, though a few abortive attempts to learn over the years have made me pretty familiar with common conventions such as {curly braces} and ending lines with semicolons();

As with any new skill, the real thing you need to do to ensure the knowledge sticks it to apply what you've learned in some sort of practical situation. I'm hoping that the later exercises in Codecademy will provide some of this much-needed context for my learning and allow me to confidently say "yes, I do know [language]". That sort of thing makes you eminently attractive when being considered for new positions, and while I'm not intending to move on anywhere just yet, it is, of course, always worth keeping one's eyes open for suitable opportunities to flex one's intellectual muscles and make use of the things you've learned over the years.

Still got a way to go before I'd consider putting any of these languages (except HTML and CSS, which I'm pretty confident in the use of) on my CV, though; better get back to the studying then, I guess!

1696: Side Effects

One of the side-effects of 1) having a job that doesn't involve staring glassy-eyed at the Internet all day and 2) being in the middle of a self-enforced social media blackout (it's going great, by the way) is that your priorities and even interests change.

Oh, don't worry, I'm not about to stop boring you with tales of obscure video games any time soon, but what I have found is that I'm in no hurry to keep up with the latest news in gaming and related spheres such as technology.

This was really driven home to me today when someone asked what I thought of Apple's new announcements.

Eh? I thought. I haven't heard anything about those.

Apparently Apple announced a new iPhone and a smartwatch, whatever the fuck one of those is. And I was surprised to find how little of a shit I gave about either of them. My current phone is a functional workhorse at best, though without Facebook and Twitter demanding my attention every few minutes it stays in my pocket or drawer a lot more than it used to, and is largely being used for a bit of lunchtime Web browsing and playing music in the car. As such, I find it hard to get excited about the latest piece of shiny, pretty and overpriced tech that Apple is coming out with. My honeymoon period with "smartphones" is well and truly over: I'm not interested in playing games on them, I'm rapidly discovering the value of not having social media in your pocket, and for organisation, frankly I'd rather use a paper notebook and calendar. Get off my lawn.

It was the watch that particularly bewildered me, though. Before I left the games press, tech writers were just starting to get excited about "wearables", and I couldn't fathom why. I still can't. It just sounds like an unnecessary step in the process of consuming digital content, and a way for the ever-present menace of notifications to be even more intrusive to your daily life than a constantly beeping phone already is. A little computer on your wrist is something straight out of sci-fi and a few years ago I'd have been all over it, but on reflection, now? That's not what I want. Not at all.

I'm not writing about this to be one of those smug "well, I don't care about those things you're excited about" people — though I'm well aware it may well come across that way. Rather, I'm more surprised at myself; I always had myself pegged as a lifelong gadget junkie, and the trail of defunct-but-useful-at-the-time technology (Hi, Palm!) my life has left in its wake would seem to back that up.

But I guess at some stage there's a saturation point. You see something, and see no way for it to possibly fit into your life; no reason to own one. I already felt this way about tablets — I barely use our iPad even today — and I certainly feel it about Apple's new watch. Smartphones still have something of a place in my life — if nothing else, it's useful and convenient to have things like maps and a means of people contacting you (or indeed contacting others) in your pocket — but their role is much diminished from what it was, and I'm in no hurry to upgrade to the latest and greatest.

It's another case of, as we discussed the other day, solutions to problems you don't have. All this technology is great, but it convinces us that our lives would be an absolute chaotic mess without it — when, in fact, it's entirely possible that the opposite could be true. After all, the human race survived pretty well before we discovered the ability to photograph your dinner and post it on the Internet, didn't we? While I'm not ready to completely let go of my smartphone — not yet? — I'm certainly nowhere near as reliant on technology as I once was, and I'm certainly not obsessively checking news feeds to find out the latest and greatest news about it.

And you know what? It's pretty nice and peaceful. I could get used to this.

1644: Contemplating My Now Not-So-New Phone

Avid readers (hah) will recall that a while back I jumped ship from iOS to Android when I upgraded my phone. My long-in-the-tooth (relatively speaking, anyway) iPhone 4S was replaced by an HTC One M8, a phone which had received some positive reviews from people I knew and trusted, so I decided to take a chance and give it a shot. It was a good time to do so, since I'd been becoming increasingly disillusioned with many of the apps available on smartphones generally, and as such I wasn't feeling particularly "invested" in the iOS ecosystem — in other words, there weren't very many apps that I felt particularly attached to.

So, a little down the line, how am I finding it now the inevitable "honeymoon period" is over?

Well, I'm still really liking it, and the one peeve I had with it — the fact it seemed somewhat prone to random restarts and reboots while I was in the middle of doing things — appears to have worked itself out, and hasn't happened for a long time now. (Watch it start doing it again now I've written this.)

As I noted in my earlier posts, I'm not a hugely adventurous smartphone user these days. There are relatively few things I actually want to do with my phone, but most of them are beyond what a simple feature phone offers — or, in the case of facilities that feature phones do offer, smartphones inevitably do them all somewhat better.

Here's the limit of what I use my phone for: Email. Texting. Phone calls (only when there is no other option). Calendar. Music and podcasts. Google Hangouts. Twitter. Web browsing. Very occasionally Facebook and Google+, though I don't use either network very much any more. And, if there is nothing else to do during an extended visit to the toilet, playing a simple, toilet-friendly game like Threes.

That's about it. There's probably more I could do with it but I don't really feel the need to right now, since the stock apps and the few additional ones I've installed cover most of the things that I want to do with it on a daily basis. I can communicate with it, I can browse the Web with it, I can take snapshots with the camera if necessary and I can read information on a screen that's noticeably bigger than that offered by Apple's iOS devices.

I've been particularly impressed by Google Play Music, which provides a number of helpful services, chief among which is something similar to Apple's iTunes Match service, only it actually, you know, works. For those unfamiliar, iTunes Match (and Google Play Music) is a facility whereby you can upload tracks from your personal music library or "match" existing songs with iTunes/Google's online libraries, then stream or download them to any compatible device. In effect, this allows you to take your entire music library with you wherever you go, rather than being limited by the storage space available on your phone — though the streaming side of things is, of course, dependent on you having a good wireless Internet connection either via the mobile phone networks or Wi-Fi.

Where Google Play Music differs from iTunes Match is that it's a lot clearer in presenting its information. With iTunes Match, it was almost impossible to tell which songs you had downloaded to your phone — and consequently available when no Internet connection was around — and which would require streaming. Attempting to download songs often resulted in failure for no apparent reason — and with Apple's phobia of error messages, there was no way of discovering what was causing the problem. Google Play Music, meanwhile, while having a somewhat clunky interface in a few places — it'd be great to have just a plain list of albums, playlists, songs and that sort of thing rather than the overly graphical, space-wasting interface it has — but at least presents this sort of information clearly. It's obvious when you've downloaded something or if you'd be streaming it when you clicked Play, and, importantly, it's easy to remove things from your phone once you've downloaded them — something which iTunes Match made seemingly impossible to do manually for some inexplicable reason.

So that's been great, and the other apps I've been using regularly all seem to work pretty well, too. All in all I'm sure I'm using this phone to a fraction of its full potential, but it's doing everything I want it to and it's doing it well, with my only real criticism of the device as a whole being that the volume control buttons are in a stupid place and are much too easy to press accidentally while simply holding it normally.

1582: My Phone's Not Called "Mate"

So, an update on how I'm doing with my new phone after several days of fiddling around with it. (Said new phone, if you missed my post from the other day, is an HTC One M8 — my first Android phone, though not my first Android device.)

I'm really liking it! Like, way more than I thought I would. There are flaws, certainly — the phone has frozen and rebooted itself while I was in the middle of doing something rather more times than I would have preferred it to in the last few days — but on the whole, it's been a great experience so far and I dare say that I am actually starting to prefer it to iOS.

Don't get me wrong, I'm not going to suddenly become an Android fanboy, largely because I find Android fanboys to be some of the most insufferable fanboys on the entire Internet. Nor do I feel that iOS is now "bad" because of the time I've spent with Android. But there are clear and discrete markets for both, and they both do their own thing extremely well.

iOS, like most of Apple's other products these days, is designed to be accessible, simple and straightforward. I hesitate to say "designed for stupid people" but it's certainly designed in such a manner that stupid people can't break it easily. It doesn't blind you with unnecessary information — if there's something it can do quietly in the background without telling you what's going on, it will. This is great for people who panic when they see technical messages they don't understand; however, on the flip side, it's less than ideal for computer-literate people who like to know what their device is up to — and if it's up to something it shouldn't be (or not up to something it should be).

There are two features on iOS where this is painfully apparent, and as I count myself in the more "computer literate" camp they'd been becoming increasingly frustrating to me.

First up is Photo Stream, a feature whereby you take a photo with the phone's camera and it gets automatically backed up to your iCloud account and synced to any other devices you've also logged into iCloud with. This is, in theory at least, extremely useful for backing up images and just for transferring them from one device to another — from phone to computer, say — without having to faff around with long-winded sync processes or additional hardware. And, a good 90% of the time, it was great. The trouble was, for that remaining 10% of the time it would just not work, and it certainly wasn't going to tell you why. I eventually managed to figure out that if Photo Stream wasn't syncing it was generally for one of two reasons (the battery being below 20% or you not being connected to Wi-Fi) but the phone certainly didn't tell me that.

iTunes Match, the service that allows you "cloud" access to your full iTunes music library from any device, is the same way. A few weeks back, my iPhone simply started refusing to download certain iTunes tracks to itself, which made loading it up with tunes to take on a long trip to be troublesome at best, completely impossible at worst. Again, there was no means of getting feedback on what was going wrong and why some tracks would download but others wouldn't; it simply wouldn't do it. Infuriating. But I can sort of understand why Apple chose not to put frightening error messages in there — so as not to scare off the casual, less computer-literate people.

Android's big selling point is its customisability, and to be fair I haven't explored that a great deal with my new device just yet — I've been largely happy with the stock options so far. It comes preloaded with a standard app launcher and a special "car mode" with big buttons and quick access to music, navigation and other useful features you might need while driving, but I know the option is there for further customisation. I also like how you can have things installed on the device but not visible on the home screen.

What I've really liked so far is the notifications system. I can clear all my notifications with a simple tap on a button, or I can also take action on a lot of them right from the notifications feed — reply to a tweet, archive an email, all manner of other things. It took a little adjusting to the fact that the phone doesn't display messages on the home screen like the iPhone does, but having used it for a few days now, it's actually quite nice to have the peace and be able to review notifications at your leisure rather than when your phone thinks you should.

Plus there's the sound. I'm not normally a fan of playing music out of a mobile phone, but the M8 has some surprisingly competent speakers. They're never going to rival a proper setup, of course, but they're loud, reasonably beefy considering their size, and they make listening to music or podcasts without headphones while doing other things — housework, for example, or, more relevantly to now, packing — eminently practical. Combine with Google Music's much better, more stable implementation of "cloud music" than iTunes Match offers along with the ability to put an extra SD card in there for storage and you have a device that is a kick-ass media player as well as a solid communication device, too.

So I'm liking it a lot so far, and I'm certainly not missing my iPhone, which I gave to O2 for recycling in exchange for a little over a hundred quid — not to be sniffed at for minimum effort. Whether or not I'll stick with Android in the long term remains to be seen, but frankly it's looking quite positive right now.

1579: "Android?"

I took a bold step and did something very brave today. I… I…

I switched from iOS to Android.

Okay, "very brave" might be understatement of the century, but despite being curious about Google's mobile OS, I've resisted the temptation to ditch the iPhone series to date, largely because I felt that I was too invested in the iOS ecosystem to make breaking free practical.

I pondered this recently, though, and realised that I actually wasn't all that dependent on the iOS ecosystem at all. I run my mail, contacts and calendars through Google, I socialise through Facebook, Twitter and Google+, I take notes in Evernote and… well, that's about it, to be frank; I'm not an especially adventurous mobile user these days, largely because I feel that 95% of apps released these days are superfluous, pointless crap that no-one needs.

And so it is that I find myself with an HTC One "Don't Call Me Mate" M8 Android handset. It's a rather larger handset than the iPhone 4S I was using before, and it's larger than Andie's iPhone 5S, too. I once thought that large phones were worthy of mockery, but having been using the HTC for a day I'm already feeling the benefit of the larger screen size. It's not a huge amount bigger than an iPhone, but it's a significant enough difference that things don't feel nearly as cramped.

Bringing mail, contacts and calendars across was straightforward and easy because I was using Google. The one thing I was a little concerned about was being able to manage my music — something that I have, to date, relied on iTunes for. It turns out that Google's Google Music service has seemingly been designed for this exact situation, allowing you the ability to upload up to 20,000 tracks directly from your iTunes library to then be available for streaming or caching from anywhere. You can listen to them via the Chrome-based web player, or on your Android phone. There's even an optional Spotify-like subscription service where you can stream music you don't own, so as of today I've cancelled my Spotify Premium account and gone with Google instead.

There are things to adjust with on the new phone. Not having notifications on the lock screen is very odd having had them for several generations of iOS hardware, but this is more than made up for by the fact you can dismiss all notifications at once from the notification centre. I haven't delved particularly into the customisation side of things yet, but I understand with a bit of fiddling and tweaking it's possible to rectify this behaviour if it really bothers me.

There are a few things I really like. The fact that if you download an app and discover it's shit, you can delete it and automatically receive a refund if you do so within 15 minutes of purchasing. The way apps work together, sharing information much more easily than on iOS. The way the on-screen keyboard does a fake "haptic feedback" thing where it vibrates very slightly every time you press a key. The camera on this particular device is supposed to be very good, too, but I haven't really tried it as yet.

So far I'm very happy with the new device so far, particularly as the tariff I've moved to post-upgrade is, for once, actually a better deal than the one I was on previously. I'm paying the same and getting more cellular data allowance plus "4G" speeds where they're available, so the overall experience should be superior. I'm looking forward to exploring what it's capable of further; it's a pleasant and fun change, and wasn't riddled with nearly as many difficulties as I was expecting.

But don't worry. I'm not going to become one of those douchebags who comments on every article about a new iOS app/game and just says "Android?" like a brainwashed parrot. iOS is still great at what it does, and if you claim to be a lover of tech, you should be interested and curious in all the alternatives out there rather than swearing blind corporate allegiance to one company purely because they make the handset you currently own.

But that's probably a discussion for another day. I'm going to go and lie in bed and fiddle with my phone for a bit now. Or possibly just play Nanaca Crash on it.

1542: Terebi Desu

Our new TV arrived today at some ungodly hour in the morning — which felt all the more ungodly for the fact that excellent Vita dungeon crawler Demon Gaze had kept me enraptured until 3am — and I've been having a bit of a play with it. (For the curious, it's a Samsung Series 6 55-inch LED TV; it has a catchy three thousand-digit model number but I have no idea what it is.)

When Andie suggested we grab a new TV, I was a little concerned that it might not be a significant upgrade over what we already had — a 40-inch Samsung, albeit one that is now about four or five years old. After all, despite the fact that my previous TV was an end-of-line model when I bought it — making it much cheaper — it was pretty good. Three HDMI ports, built-in Freeview tuner, full 1080p support — it had pretty much everything I needed, though it would have been nice to have an optical output port. Everything I connected to it worked just fine, though, ranging from the PlayStation 2 through the SCART port (yummy, blurry standard-def picture) to the various games consoles and PC through the HDMI ports.

With the previous TV working just fine, why buy a new one, you might ask? Well, having spent this evening playing some Final Fantasy XIV on it and having watched some anime and TV on it earlier… yes, it was a good investment. The increase in size is extremely noticeable — it's big enough to have a touch of "peripheral vision" now, giving a much more immersive feel to both video and games — and the LED screen is lovely, bright and clear. I have no idea if I've optimized its settings appropriately — I've put the PC input into Game mode, because prior to that there was noticeable input lag, but haven't really fiddled with much else — but it certainly seems to look very nice, although as Andie pointed out, the bigger the screen you get, the more of a dog's dinner standard-definition footage and TV broadcasts look. Oh well.

It's a Smart TV, too, which means it has two remotes, one of which has a trackpad rather than, you know, just being normal, plus "apps" for doing shit old, dumb TVs don't do. There's stuff like BBC iPlayer and Netflix built into it, for example, and even apps for things like Spotify and the like. (There are also games to download, but somehow I don't see them being particularly worthwhile, and as such I will be giving them a wide berth.) I'm not entirely convinced how much I will use the "smart" features over time, but it's nice to have them there, I guess — not to mention the fact it is seemingly now impossible to buy a new TV that isn't 1) "smart" and 2) 3D.

The 3D thing surprises me somewhat, I must confess. I thought 3D TV and gaming had been a colossal failure, and yet all the televisions we looked at over the weekend were 3D in one form or another. The TV we ended up getting is "active 3D", which is supposedly better because you have to turn the glasses on before they work properly (and for some other reasons, too) and sure, it's quite fun — we watched a couple of trailers in 3D earlier and it was quite cool — but it's not something I can see myself using a lot of, and certainly not for protracted periods of time. It will almost certainly be something to show off to people who come and visit, but little else.

Anyway, I'm very pleased with it. It fits nicely on our TV stand and doesn't look too big or too small, and it's a noticeable upgrade over what we had before — plus the almost bezel-free design, with the picture going right the way to the edges of the front of the unit, looks absolutely smashing.

I'm sure I'll be taking it for granted before long — and I'm not looking forward to moving it when our new house is sorted — but yes; I'm glad we got it. And now I'm off to bed because I've been staring at it all evening and I think my eyes could probably do with a rest!

1518: New Media

I've been contemplating the ways that people "consume" (ugh, I hate that word, but it seems to be the one in use most frequently these days) content online, and trying to determine a way it could be applied to our currently-stalled podcast over at The Squadron of Shame.

The Squadron of Shame SquadCast certainly worked extremely well for the episodes we did it for, but it did often end up being a little more demanding on the editing time than I would have liked, particularly as we're all amateurs making use of not-brilliant equipment that often results in things like background hum, echo and other annoying flaws that are difficult to edit out. Much of my editing time was often spent manually trimming out echoes and funny noises, and in the case of a 2-3 hour episode — which most of our episodes tended to be — it would take the majority of the day to do this.

One of the things I'm wondering right now is how relevant the podcast format still is. Obviously I know that there's enough of a market for sites like Giant Bomb to keep making one every week, and for established podcasting personalities like Garnett Lee to be able to start a new show and have people follow him to see what he's up to. But I'm also conscious of the rise of alternative means of "consuming" (blech) content in the last couple of years, with YouTube being one particularly disruptive influence, and live broadcasts such as Twitch streaming and Google Hangouts being another.

Awareness of these alternative forms of media has made me ponder whether the standard podcast format is absolutely the best possible thing for the SquadCast going forward, or whether it's worth contemplating an alternative means of presentation (with an accompanying means of archiving/downloading where necessary.)

The SquadCast has always been a "book group" style of discussion surrounding a game or gaming-related topic, and it's worked well for us in the past. But gaming is also an inherently visual medium, which makes me wonder whether some form of video presentation might be worth experimenting with, perhaps combined with live broadcasting.

Another reason I bring this up is that Skype, which we have previously used to talk to one another and record the discussions we have, has become a largely unworkable mess ever since Microsoft bought it, making it impossible for me to "archive" the complete conversation just in case someone's individual recording fails to work properly. I haven't needed this facility on many occasions, but on the couple where someone's recording was destroyed by Audacity's frequent crashes, having that backup facility was a godsend. With the way Skype works now, though — you can't run it in more than one user account on a Mac at once, which is what I used to do — working this way is impossible without an unnecessarily convoluted setup involving more than one computer.

What I've been pondering is making use of something like Google Hangouts, which allows for a number of features that would seem ideal for a discussion about games. It allows participants to converse via either audio or video chat, and it also allows for the footage of the participants to be intercut with other things such as videos from YouTube and the like. For example, while discussing a particularly interesting scene in a game, making use of Google Hangouts would allow you to find that scene on YouTube and then broadcast it to the people watching the Hangout, which strikes me as an eminently good idea. Presumably it would also allow for playing footage while the conversation continues over the top, which is a little more interesting than just gazing at a bunch of talking heads for a few hours.

Google Hangouts can also be easily archived to YouTube, and then one of the many YouTube-to-MP3 converters out there can be used to archive an offline version of the discussion's audio, which can subsequently be released as a standard podcast for those who wish to continue listening in that way. It'll be rawer due to the lack of editing and its inherently live nature, but I've often felt when I edit a show that I was making the job a lot more difficult and time-consuming than it really needed to be.

Anyway. I'm just thinking out loud here. Interested to know your thoughts, though, particularly if you've been either a listener or a participant in the SquadCast at any point in the past. (Those who are neither, you can educate yourself thanks to our archives here.)

1182: Fixed That For You

Page_1 I've had a week of not having a lot of luck with technology. Firstly, I was reminded that my electric piano was suffering a sticky key issue on the B above middle C (which is quite a commonly-used note) and proving rather difficult to play effectively. This was annoying, because as I noted yesterday, I'd just come into possession of the official piano arrangements for the Nier and Final Fantasy X-2 soundtracks along with some fan-arranged printouts of a variety of anime and game pieces.

Secondly, my PS2 Slim mutilated my Ar Tonelico 2 disc right in the middle of one of the endings I hadn't seen, causing it to freeze up completely and not be able to go any further. (I have since replaced the PS2 Slim with a PS2 Fat — which hasn't arrived yet — and acquired a new copy of Ar Tonelico 2, but that's some money I didn't really need to spend.)

Fortunately, one of these problems has been rectified thanks to Andie's willingness to get her hands dirty and tinker around inside things. (Get your mind out of the gutter.) Loosely following some instructions online, we took the casing off my Yamaha P80 and had a look inside. It wasn't immediately obvious what was causing the key in question to stick, but as it happened, the process of popping it out (which we didn't even manage to do completely, just sort of half-out) and popping it back in again completely fixed the problem. This was, as I'm sure you can imagine, extremely pleasing as it means 1) I don't have to attempt to fit my piano into the back of a Peugeot 207; 2) I don't have to drive it 25 miles to the nearest Yamaha engineer; and 3) I don't have to pay aforementioned Yamaha engineer £100+ to get it fixed. Don't get me wrong, I would have happily paid Captain Piano-Fix his fee in order to get things sorted, but given that the fix was apparently that simple — I guess the key must have got knocked out of its normal place somehow, perhaps while we were moving house — I'm glad that I don't have to do any of the above three things.

This isn't the first time I've seen something get "fixed" by peculiar means. Back in university, I came into possession of a Sega Saturn, which I still own to this day (though I no longer have any games for it). The controller that came with the Saturn didn't work very well, so, having nothing better to do that evening — my housemate was out and no-one fancied going down to the Union to get obliterated on Juicy Lucies — I took it apart and decided to see what I could do, despite not having any clue whatsoever about how it worked. Eventually, I ended up cleaning the contacts on the circuit board using a piece of kitchen towel dipped in vodka — I honestly have no idea why this particular combination of things seemed like the right thing to do at the time; I was possibly a bit drunk — and putting it back together again. Astonishingly, it worked after this. To date, I have no idea if my ridiculous efforts to "fix" the thing actually had any effect or whether it was just the simple process of taking it apart and putting it together again.

I guess the moral of this story is that if something is broken (and out of warranty) then there are worse things you can do than pull out all the screws, pull everything out and then put it back together again. Obviously don't try and do this on a human body, however, because 1) human bodies don't have any screws and 2) they're a lot harder to put back together once you've disassembled them, which is why degrees in Medicine take so long to complete.