<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bertie Baggio&#039;s Wonderland</title>
	<atom:link href="http://blog.roberthallam.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.roberthallam.org</link>
	<description>armchair rebel and cheerful raconteur</description>
	<lastBuildDate>Fri, 21 Sep 2012 15:38:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>MP4 / H264 Encoding Header Errors in Adobe Premiere Pro / Media Encoder / MainConcept</title>
		<link>http://blog.roberthallam.org/2012/09/mp4-h264-encoding-header-errors-in-adobe-premiere-pro-media-encoder-mainconcept/</link>
		<comments>http://blog.roberthallam.org/2012/09/mp4-h264-encoding-header-errors-in-adobe-premiere-pro-media-encoder-mainconcept/#comments</comments>
		<pubDate>Fri, 21 Sep 2012 15:38:01 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[all posts]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[error]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=480</guid>
		<description><![CDATA[I&#8217;ve been editing toether a few gameplay videos recently (eg DayZ &#8211; Tread Lightly).I came across a rather perplexing error when trying to encode a long video. Basically, I have a few sequences of footage taken with FRAPS that together run to about 2 hours and 45 minutes. I created a project for these to [...]]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/09/mp4-h264-encoding-header-errors-in-adobe-premiere-pro-media-encoder-mainconcept/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[Fixed] FTL &#8211; Blank Maps &amp; Invisible Ships Problem</title>
		<link>http://blog.roberthallam.org/2012/09/fixed-ftl-blank-maps-invisible-ships-problem/</link>
		<comments>http://blog.roberthallam.org/2012/09/fixed-ftl-blank-maps-invisible-ships-problem/#comments</comments>
		<pubDate>Sun, 16 Sep 2012 13:25:29 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[games]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[pc games]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[ftl]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=476</guid>
		<description><![CDATA[Update: fixed! The recently-released FTL by Subset Games has a problem with the 12.8 AMD Catalyst Drivers, whereby the jump map and enemy ships are not rendered See below) due to an issue with edge detection in anti-aliasing. The fix is to create a custom profile for FTLGame.exe in the Catalyst Control Center to over-ride [...]]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/09/fixed-ftl-blank-maps-invisible-ships-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[Solved] Google+ Notifications Not Working</title>
		<link>http://blog.roberthallam.org/2012/09/solved-google-notifications-not-working/</link>
		<comments>http://blog.roberthallam.org/2012/09/solved-google-notifications-not-working/#comments</comments>
		<pubDate>Tue, 04 Sep 2012 11:38:56 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[tech]]></category>
		<category><![CDATA[google+]]></category>
		<category><![CDATA[troubleshooting]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=472</guid>
		<description><![CDATA[I was having problems with Google+ notifications not working more often than not in Firefox: This service is currently unavailable Please try again later. The solution that worked for me was to disable the extension &#8220;Do Not Track Plus&#8220;, as noted in this post.]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/09/solved-google-notifications-not-working/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scrollback / Terminal History in screen or byobu</title>
		<link>http://blog.roberthallam.org/2012/08/scrollback-terminal-history-in-screen-or-byobu/</link>
		<comments>http://blog.roberthallam.org/2012/08/scrollback-terminal-history-in-screen-or-byobu/#comments</comments>
		<pubDate>Thu, 23 Aug 2012 13:56:18 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[byobu]]></category>
		<category><![CDATA[screen]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=470</guid>
		<description><![CDATA[This is another case of &#8220;should have read the manual&#8221;, but there are ways to see previous output in both screen and byobu. In screen: ctrl + a + [ In byobu: F7 These key combinations cause screen/byobu to enter copy mode, where you can navigate using vi keys, can set marks for copying using [...]]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/08/scrollback-terminal-history-in-screen-or-byobu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My Phone Won&#8217;t Load SMS Conversations</title>
		<link>http://blog.roberthallam.org/2012/08/my-phone-wont-load-sms-conversations/</link>
		<comments>http://blog.roberthallam.org/2012/08/my-phone-wont-load-sms-conversations/#comments</comments>
		<pubDate>Fri, 03 Aug 2012 16:33:11 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[all posts]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=466</guid>
		<description><![CDATA[I posted this on Google+, but I&#8217;m not sure it&#8217;s quite the right venue for troubleshoorint queries. I have an #android #troubleshooting query. I have an HTC Desire HD through 3 in the UK. When I go to open messages using the stock message application, it gives a &#8220;loading&#8221; spinner but never shows the messages. [...]]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/08/my-phone-wont-load-sms-conversations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plex Media Server Warning &#8216;Not Found&#8217; Errors (Fixed)</title>
		<link>http://blog.roberthallam.org/2012/08/plex-media-server-warning-not-found-errors-fixed/</link>
		<comments>http://blog.roberthallam.org/2012/08/plex-media-server-warning-not-found-errors-fixed/#comments</comments>
		<pubDate>Fri, 03 Aug 2012 14:56:56 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[htpc]]></category>
		<category><![CDATA[media]]></category>
		<category><![CDATA[plex]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=463</guid>
		<description><![CDATA[The media browser on my LG TV has been acting up recently. Instead of listing the categories set up in Plex it pops up a dialog saying &#8220;Warning: Not Found&#8221;. It does this despite being able to see the Plex Media Server (going to &#8216;bowse sources&#8217; or similar brings up the server&#8217;s name but selecting [...]]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/08/plex-media-server-warning-not-found-errors-fixed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adding Workspaces / Virtual Desktops in Cinnamon</title>
		<link>http://blog.roberthallam.org/2012/08/adding-workspaces-virtual-desktops-in-cinnamon/</link>
		<comments>http://blog.roberthallam.org/2012/08/adding-workspaces-virtual-desktops-in-cinnamon/#comments</comments>
		<pubDate>Thu, 02 Aug 2012 12:56:00 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[cinnamon]]></category>
		<category><![CDATA[mint]]></category>
		<category><![CDATA[workspaces]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=459</guid>
		<description><![CDATA[Mousing to the &#8220;hot corner&#8221; in Cinnamon gives an overview of current workspaces, &#224; la expose. Unfortunately a careless click can close one of those workspaces, as I found out last night. Equally, you may feel that the default 2 workspaces is too few and wish to expand upon that. Now, I think the numvber [...]]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/08/adding-workspaces-virtual-desktops-in-cinnamon/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Project Euler Problem 25 Pitfalls</title>
		<link>http://blog.roberthallam.org/2012/07/project-euler-problem-25-pitfalls/</link>
		<comments>http://blog.roberthallam.org/2012/07/project-euler-problem-25-pitfalls/#comments</comments>
		<pubDate>Thu, 26 Jul 2012 16:16:31 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[python]]></category>
		<category><![CDATA[wisdom]]></category>
		<category><![CDATA[project euler]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=455</guid>
		<description><![CDATA[Project Euler problem 25 is reasonably straighforward. It asks you to find the first term in the Fibonacci sequence with more than 1000 digits. In ones like these, not reading the question properly is more likely to be your downfall than anything else. So: Give the number of the first term which has 1000 digits, [...]]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/07/project-euler-problem-25-pitfalls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lenny to Squeeze Upgrade Problems</title>
		<link>http://blog.roberthallam.org/2012/07/lenny-to-squeeze-upgrade-problems/</link>
		<comments>http://blog.roberthallam.org/2012/07/lenny-to-squeeze-upgrade-problems/#comments</comments>
		<pubDate>Wed, 18 Jul 2012 14:58:32 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[squeeze]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=450</guid>
		<description><![CDATA[http://linux-knowledgebase.com/en/Tipoftheday/February/error23errorwhileparsingnumber saved my server. It wasn&#8217;t booting after an upgrade to Debian Squeeze, despite following the upgrade instructions. Connecting to the serial console showed there were problems with finding root (grub error while parsing number, error 23) which was at md1. Changing the first line to root (hd0,0) and adding initrd /boot/initrd.img-2.6.32-5-amd64 allowed the system [...]]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/07/lenny-to-squeeze-upgrade-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Correct Way To Iterate Over Files In Bash</title>
		<link>http://blog.roberthallam.org/2012/07/correct-way-to-iterate-over-files-in-bash/</link>
		<comments>http://blog.roberthallam.org/2012/07/correct-way-to-iterate-over-files-in-bash/#comments</comments>
		<pubDate>Fri, 13 Jul 2012 14:59:30 +0000</pubDate>
		<dc:creator>Rob Hallam</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[scripting]]></category>

		<guid isPermaLink="false">http://blog.roberthallam.org/?p=448</guid>
		<description><![CDATA[Because I keep forgetting, here&#8217;s a reminder to myself of the correct way to iterate through files and directories in bash, even considering spaces in filenames, whith a hat-tip to Thomas Howard Uphill: find . -type f&#124;grep .ext$ &#124;while read file do /do/something/to "$file" done Silly rabbit.]]></description>
		<wfw:commentRss>http://blog.roberthallam.org/2012/07/correct-way-to-iterate-over-files-in-bash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
