<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Church Tech Matters</title><link>http://churchtechmatters.com</link><description>A site for tech volunteers written by tech volunteers</description><language>en</language><lastBuildDate>Wed, 11 Nov 2009 02:05:04 PST</lastBuildDate><generator>WordPress http://wordpress.org/</generator><thespringbox:skin xmlns:thespringbox="http://www.thespringbox.com/dtds/thespringbox-1.0.dtd">http://feeds.feedburner.com/ChurchTechMatters?format=skin</thespringbox:skin><geo:lat>37.168985</geo:lat><geo:long>-94.311647</geo:long><image><link>http://www.churchtechmatters.com</link><url>http://www.feedburner.com/fb/a/feedcount?id=17153</url><title>Church Tech Matters</title></image><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/ChurchTechMatters" type="application/rss+xml" /><feedburner:browserFriendly>This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site.</feedburner:browserFriendly><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item><title>Google Wave: Cheat Sheet</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/IyVc-gLZ2uY/</link><category>software</category><category>support</category><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stuart</dc:creator><pubDate>Wed, 11 Nov 2009 02:05:04 PST</pubDate><guid isPermaLink="false">http://churchtechmatters.com/?p=1426</guid><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>I&#8217;m taking <span style="text-decoration: underline;"><strong>no</strong></span> credit for this &#8211; I was allowing myself to be sucked in by a public wave search and it literally felt like I was drowning &#8211; but I discovered this wave in the process.</p>
<p>If you haven&#8217;t tried viewing the live public wave feed then I dare you.</p>
<p>Anyway, the info below is the stuff I keep referring back to so thought where better to stick it than on one of the blogs I write on.</p>
<p>More after the jump:</p>
<p><span id="more-1426"></span><br />
<strong>Search Cheat Sheet</strong></p>
<p>This is a quick guide to the operators and restricts supported by wave search.</p>
<p>Keywords</p>
<p>about:[keyword] — finds waves which have [keyword] occurring anywhere. Same as [keyword].<br />
title:[keyword] — finds waves which have [keyword] in the title.<br />
caption:[keyword] — finds waves which have an attachment where [keyword] occurs in the caption.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Status</strong></p>
<p>is:read — finds all read waves.<br />
is:unread — finds all unread waves.<br />
Note: you cannot currently do a search like “-is:read” by itself and get reliable results due to an outstanding restriction on megastore queries</p>
<p>is:mute — finds all muted waves.<br />
is:unmute — finds all waves not muted<br />
is:active — currently the same as is:unread.<br />
is:note — finds all waves which have you as the only participant and contributor<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Participants</strong></p>
<p>from:[address] — finds waves from the participant identified by the address. Special case of from:me identifying waves from yourself.<br />
by:[address] — same as from:[address].<br />
to:[address] — find waves which are a dialogue between you and the participant identified by the address.<br />
with:[address] — find waves that have the participant identified by the given address explicitly listed.<br />
owner:[address] — find waves by person, that they created.<br />
only:[address] — finds waves to which only the participant specified by the given address contributed.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Date Search</strong></p>
<p>Currently, there are a few restricts:</p>
<p>past:[date term] — finds all waves in the last period.<br />
previous:[date term] — finds all waves in the period before the last period.<br />
before:[date term] — finds all waves before a certain period.<br />
after:[date term] — finds all waves after a certain period.<br />
which can be combined with date terms:</p>
<p>day<br />
week<br />
month<br />
year<br />
So you can have past:week, past:year. There is also support for</p>
<p>past:N[date term] where N &gt; 0. So you can have past:3days (today, yesterday, the day before yesterday).<br />
Also you can have</p>
<p>past:Ndays<br />
past:Nweeks<br />
past:Nmonths<br />
past:Nyears<br />
Finally, you can abbreviate days, weeks, months and years to a single letter (d, w, m, y). Thus you can write</p>
<p>past:3d<br />
past:2w<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Folders</strong></p>
<p>in:[folder name] — find waves in the folder with the given name. For example, in:inbox.<br />
in:[search name] — find waves in the saved search with the given name.<br />
is:unfiled — find waves which have not been moved to a user folder.<br />
is:filed — find waves which belong to some user folder.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Attachments</strong></p>
<p>has:attachment — finds waves with an attachment. This changed from “is:image”.<br />
has:document — finds waves with an attachment which is a document. (coming soon)<br />
has:image — finds waves with an attachments which is an image. (coming soon)<br />
caption:[keyword] — finds waves with an attachment with caption containing [keyword].<br />
filename:[keyword] — finds waves with an attachment with filename containing [keyword]. (coming soon)<br />
mimetype:[keyword] — finds waves with an attachment with mimetype containing [keyword]. (coming soon)<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Tags</strong></p>
<p>tag:[tag name] — finds waves with the tag [tag name].<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Gadgets</strong></p>
<p>has:gadget — finds waves which contain a gadget.<br />
gadget:[keyword] — finds waves which contain a gadget with name containing keywords. e.g. chess, fridge, map, risk, sokoban.<br />
gadgeturl:[keyword] — finds waves which contain a gadget with urls containing keyword.<br />
gadgettitle:[keyword] — finds waves which contain a gadget with a title containing keywords.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Expressions</strong></p>
<p>foo &amp; bar — match waves with foo and bar.<br />
You can use AND, or skip the operator altogether, as the logical and is the default.<br />
foo | bar — match waves with foo or bar (or both).<br />
foo OR bar — match waves with foo or bar (or both).<br />
-foo — match waves that do not contain foo. (There is an outstanding bug that causes searches with only negative terms to fail. To get around it, use to:me -foo)<br />
“foo … bar” — matches waves that contain the exact phrase “foo … bar” (There is an outstanding bug for live search not working with phrases)<br />
foo &amp; (bar | -baz) — matches waves that contain foo and either bar or do not contain baz.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Phrases</strong></p>
<p>“[multiple terms]” — match waves with one or more terms in sequence:<br />
“hot dog” catches waves with the terms hot and dog in sequence. This is also required for other operators such as in:”new inbox” where say “new inbox” is a saved search.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>XML Search</strong></p>
<p>tags:subtag — find all waves which have this  combination.<br />
tag:[tag] — find all waves which have this .<br />
attribute:[value keyword] — finds all waves which have &lt; …. attribute=value …&gt; where keyword is a token in value.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Wave ID</strong></p>
<p>id:”” — find a wave with a specific wave id.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Zero Inbox</strong></p>
<p>If you want to zero inbox, you can hack this temporarily by saving a search “my inbox” with the query:</p>
<p>in:inbox is:unread this:week. You can then use the menu option “Mark as read” in the wave panel.<br />
Alternative zero inbox: in:inbox is:unread past:7days -is:mail<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Saved Searches</strong></p>
<p>A search can be saved using one of two methods:</p>
<p>Create a search in the search box and then press the Save search button at the bottom of the Digest panel.<br />
Add a search using the searches Add button on the Navigation panel. Then add the search query and name of the search in the Saved Search popup panel.<br />
Saved searches can be edited and managed using the pop-up menu which shows when hovering over the saved search in the searches section of the Navigation panel.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Filters</strong></p>
<p>Filters are saved searches which also have an action to apply to all waves which match the saved search. The actions supported are</p>
<p>skip inbox – removes the wave from inbox. Whilst this wave continues to match the search, it will continue to stay out of the inbox. Skip inbox will shortly be renamed archive.<br />
mark as read – Whilst the wave continues to match the search, it will be marked as read.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Folders</strong></p>
<p>You can add a folder by using the Add button on the folders section of the Navigation panel. A folder is added by typing the folder name in the text box given and hitting enter.</p>
<p>Folders can be managed using the pop-up menu that shows when hovering over the folder on the Navigation panel.</p>
<p>Add folder &#8211; A subfolder can be added under the current folder.<br />
Rename – rename the current folder.<br />
Delete – delete the current folder.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Language Filter</strong></p>
<p>Much thanks to Geoffrey Spear for the help and insight:</p>
<p>The problem is that these tags aren&#8217;t exclusive; if a Wave has any English in it at all it will show up under &#8220;lang:en&#8221; even if it&#8217;s mostly in another language. This is particularly a problem since the search terms themselves are all English so a Wave in, say, Portuguese about using Wave will tell people they need to use &#8220;with:whatever&#8221; and the system will see &#8220;with&#8221;, an English word and suddenly the Wave is in both lang:en and lang:pt.<br />
&#8220;group:public@a.gwave.com lang:en -lang:es -lang:fi -lang:hu -lang:pt -lang:nl -lang:ja -lang:he -lang:fr -lang:ru -lang:sv -lang:zh -lang:de -lang:no -lang:da&#8221;<br />
&#8230; is fairly effective, although you basically need to keep adding more as you find Waves not in one of these languages. Not a really good solution <img src='http://churchtechmatters.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=New+CTM+post:+Google+Wave%3A+Cheat+Sheet+http://ka6wo.th8.us" title="Post to Twitter"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-twitter-big2.png" alt="Post to Twitter" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/11/11/google-wave-cheat-sheet/&amp;title=Google+Wave%3A+Cheat+Sheet" title="Post to Digg"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-digg-big2.png" alt="Post to Digg" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/11/11/google-wave-cheat-sheet/&amp;title=Google+Wave%3A+Cheat+Sheet" title="Post to Digg">Digg This Post</a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=IyVc-gLZ2uY:EgYHgup887A:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=IyVc-gLZ2uY:EgYHgup887A:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=IyVc-gLZ2uY:EgYHgup887A:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=IyVc-gLZ2uY:EgYHgup887A:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=IyVc-gLZ2uY:EgYHgup887A:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=IyVc-gLZ2uY:EgYHgup887A:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=IyVc-gLZ2uY:EgYHgup887A:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=IyVc-gLZ2uY:EgYHgup887A:kspCdTTORlE"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=kspCdTTORlE" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/IyVc-gLZ2uY" height="1" width="1"/>]]></content:encoded><description>I&amp;#8217;m taking no credit for this &amp;#8211; I was allowing myself to be sucked in by a public wave search and it literally felt like I was drowning &amp;#8211; but I discovered this wave in the process.
If you haven&amp;#8217;t tried viewing the live public wave feed then I dare you.
Anyway, the info below is the [...]</description><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">7</thr:total><creativeCommons:license>http://creativecommons.org/licenses/by-nd/2.0/</creativeCommons:license><feedburner:origLink>http://churchtechmatters.com/2009/11/11/google-wave-cheat-sheet/</feedburner:origLink></item><item><title>My Catalyst Experience</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/Q2eJFZWS104/</link><category>Uncategorized</category><category>#cat09</category><category>catalyst</category><category>catalyst09</category><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chase Livingston</dc:creator><pubDate>Wed, 21 Oct 2009 10:36:04 PDT</pubDate><guid isPermaLink="false">http://churchtechmatters.com/?p=1417</guid><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>I was so happy to be able to attend <a href="http://catalystconference.com" target="_blank">Catalyst</a> this year. I had heard about the conference several times, and always wanted to go, but never really had the money. Thanks to <a href="http://jimwalton.org" target="_blank">Jim</a>&#8217;s prompting and <a href="http://twitter.com/waynejames" target="_blank">Wayne</a> and <a href="twitter.com/mrsgeek" target="_blank">Elaine</a>&#8217;s generosity, I was able to go. It was great being able to stay in a house with 14 other people, because you got to know everyone else really well. Fortunately, we all had a comfortable place to sleep, although I doubt anyone got much sleep, because we were too busy talking, or laughing, or just hanging out.The conference itself was very exciting. I&#8217;m obviously very interested in the technical side of things, and Catalyst definitely didn&#8217;t disappoint. The entire stage was a screen that usually had some type of motion background running on it. They also had eight other projection screens which were used for live video, lyrics, etc. The sound was very well done, not overpowering, but loud enough to hear well.</p>
<p>The real power of this conference is not the A/V/L, though. The purpose of this conference is to develop current and future church leaders. The speakers were very motivational, yet challenging. I was stretched both as a leader, but also as a Christian. Something <a href="http://daveramsey.com" target="_blank">Dave Ramsey</a> said struck me very hard. He said &#8220;We don&#8217;t need any more half-butt Christians.&#8221; I began to think if maybe that&#8217;s what my walk with Jesus amounted to. I definitely don&#8217;t intend it to be that way, but I think we can all agree that sometimes, that&#8217;s what our walks look like. We&#8217;re halfway committed to serving Jesus, but also halfway committed to the world.</p>
<p>I am so thankful to have been given the opportunity to attend Catalyst, and I&#8217;m already looking forward to next year!</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=New+CTM+post:+My+Catalyst+Experience+http://4toz8.th8.us" title="Post to Twitter"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-twitter-big2.png" alt="Post to Twitter" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/10/21/my-catalyst-experience/&amp;title=My+Catalyst+Experience" title="Post to Digg"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-digg-big2.png" alt="Post to Digg" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/10/21/my-catalyst-experience/&amp;title=My+Catalyst+Experience" title="Post to Digg">Digg This Post</a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=Q2eJFZWS104:LvA7IcELJD8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=Q2eJFZWS104:LvA7IcELJD8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=Q2eJFZWS104:LvA7IcELJD8:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=Q2eJFZWS104:LvA7IcELJD8:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=Q2eJFZWS104:LvA7IcELJD8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=Q2eJFZWS104:LvA7IcELJD8:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=Q2eJFZWS104:LvA7IcELJD8:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=Q2eJFZWS104:LvA7IcELJD8:kspCdTTORlE"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=kspCdTTORlE" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/Q2eJFZWS104" height="1" width="1"/>]]></content:encoded><description>I was so happy to be able to attend Catalyst this year. I had heard about the conference several times, and always wanted to go, but never really had the money. Thanks to Jim&amp;#8217;s prompting and Wayne and Elaine&amp;#8217;s generosity, I was able to go. It was great being able to stay in a house [...]</description><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><creativeCommons:license>http://creativecommons.org/licenses/by-nd/2.0/</creativeCommons:license><feedburner:origLink>http://churchtechmatters.com/2009/10/21/my-catalyst-experience/</feedburner:origLink></item><item><title>The “Why” of Live Video – Part 1</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/nA4kbV-0i88/</link><category>Uncategorized</category><category>broadcast</category><category>cable</category><category>projection</category><category>video</category><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kirk Longhofer</dc:creator><pubDate>Wed, 14 Oct 2009 16:04:15 PDT</pubDate><guid isPermaLink="false">http://churchtechmatters.com/?p=1406</guid><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><img class="size-thumbnail wp-image-1407" src="http://churchtechmatters.com/wp-content/uploads/2009/10/TV-Camera-150x150.jpg" alt="Video Camera" width="150" height="150" align="left" vspace="5" hspace="5" />Over the past several years, the <strong>use of video in a church setting</strong> has exploded.  The use of video projection was common in the church by the early part of this decade.  Most of that use was limited to outlines of sermons and the occasional movie clip or still illustration.  Today, even the smallest of churches haul out a portable projector to project song lyrics and announcements on a screen, or in some cases, on a wall.</p>
<p>In the past few years, congregations in larger churches have suddenly been treated to (or assaulted with) the giant smiling face of the teaching pastor, and videos produced specifically to support that teaching. Other churches jumped to use video to extend the reach of their church, on <strong>broadcast or cable television</strong>, or on the Internet. They have installed broadcast quality cameras, state-of-the-art equipment in full video control rooms, and post production suites, investing hundreds of thousands of dollars in technology.</p>
<p>Over time, the use of live video has pushed down to even relatively small fellowships, both as a teaching aid, and as a way to take their brand and message beyond the walls of the church.   For the church considering taking video beyond simple lyrics and Powerpoint, or making a leap into the world of live video, it can be a confusing world.</p>
<p>But for most, the first step toward the use of live video in a worship context has nothing to do with technology.  It starts with a conversation, and a question:  <strong>“Why do we want to use live video?”</strong></p>
<p>It sounds like a simple question, but it’s not as straightforward was it might seem.  There are lots of reasons for using live video.  Some are likely valid for your congregation.  Some are not.  Answering this <strong>“why”</strong> question first will make decisions about equipment and technology much easier down the road.</p>
<p>There are many reasons that congregations are drawn to live video.  For those with large facilities, the use of Image Magnification, or IMAG helps to connect worship participants more directly to worship leaders.  It allows them to see things that might otherwise be obscured due to sight lines, or simply distance.</p>
<p><strong>IMAG is not for everyone.</strong> In a room where the distance from preacher to the most distant seat is 50 feet or less, there may not be any need for IMAG.</p>
<p>Further, doing IMAG well requires skill and effort, both from your technical team, and from the teaching pastor. It is used most effectively in conjunction with supporting images and video. Take a look at a television newscast.  You don’t see the anchor simply reading for very long.  Simply placing the image of the speaker on the screen for an entire sermon may not be the best use of your video system.</p>
<p>Another valid reason for the use of live video in worship is to <strong>leverage existing teaching and worship leadership</strong> resources. Video allows a teaching pastor to be in more than one venue, and to teach at multiple services over the course of a weekend without killing the teacher!</p>
<p>For those pushing video beyond the walls of the church via the Internet, cable or broadcast television, there is no denying it’s potential power in extending the church’s reach.  It can be a powerful tool for evangelism, and for growing a church.  It is important to remember, however, that that power can cut both ways.  Done poorly, <strong>a broadcast can do great damage</strong> to what might be a great church.</p>
<p>The church contemplating a broadcast ministry must also remember to <strong>count all the costs.</strong> A broadcast outreach can quickly become a tail that wags the worship dog.  Ego issues can surface. It’s also important to think through how, or if, you will provide pastoral services to people who connect with your church via a broadcast.  What happens when they call from the hospital, or request a pastor for counseling, or a funeral?</p>
<p>One huge benefit of having a broadcast or Internet outreach via video is the <strong>preservation of connection</strong> with older members of your congregation.  There comes a time for many folks where they simply are physically unable to attend their church.  A service delivered via television or the Internet can be a huge comfort to those members, allowing them to continue worshipping with their existing church family.</p>
<p>Perhaps the most powerful use of video in worship, however, has nothing to do with broadcasting, or with IMAG.  It is simply the use of the video medium in telling stories.  More on that next time!</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=New+CTM+post:+The+%E2%80%9CWhy%E2%80%9D+of+Live+Video+%E2%80%93+Part+1+http://hsowc.th8.us" title="Post to Twitter"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-twitter-big2.png" alt="Post to Twitter" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/10/14/the-why-of-live-video-part-1/&amp;title=The+%E2%80%9CWhy%E2%80%9D+of+Live+Video+%E2%80%93+Part+1" title="Post to Digg"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-digg-big2.png" alt="Post to Digg" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/10/14/the-why-of-live-video-part-1/&amp;title=The+%E2%80%9CWhy%E2%80%9D+of+Live+Video+%E2%80%93+Part+1" title="Post to Digg">Digg This Post</a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=nA4kbV-0i88:MYGgwQelhwU:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=nA4kbV-0i88:MYGgwQelhwU:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=nA4kbV-0i88:MYGgwQelhwU:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=nA4kbV-0i88:MYGgwQelhwU:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=nA4kbV-0i88:MYGgwQelhwU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=nA4kbV-0i88:MYGgwQelhwU:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=nA4kbV-0i88:MYGgwQelhwU:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=nA4kbV-0i88:MYGgwQelhwU:kspCdTTORlE"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=kspCdTTORlE" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/nA4kbV-0i88" height="1" width="1"/>]]></content:encoded><description>Over the past several years, the use of video in a church setting has exploded.  The use of video projection was common in the church by the early part of this decade.  Most of that use was limited to outlines of sermons and the occasional movie clip or still illustration.  Today, even [...]</description><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">8</thr:total><creativeCommons:license>http://creativecommons.org/licenses/by-nd/2.0/</creativeCommons:license><feedburner:origLink>http://churchtechmatters.com/2009/10/14/the-why-of-live-video-part-1/</feedburner:origLink></item><item><title>Why a Mac in Church?</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/qGU6fG2MFa4/</link><category>media</category><category>software</category><category>church</category><category>mac</category><category>propresenter</category><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chase Livingston</dc:creator><pubDate>Mon, 12 Oct 2009 09:44:36 PDT</pubDate><guid isPermaLink="false">http://churchtechmatters.com/?p=1392</guid><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Well, I&#8217;m glad you asked. Up until about a year and a half ago when I bought my first Mac, I was very against the whole idea. I thought Macs were just overpriced, hard to use, and incompatible with the rest of the world. But then, after playing with a few of my friend&#8217;s Macs, I decided I was going to get one, and I&#8217;ve loved every minute of it.</p>
<p>But I digress, the reason we&#8217;re here is to find out why someone would want to use a Mac in church rather than a PC. First of all, I believe that Macs are much better suited for multimedia. They come with many programs that out of the box are great for the average user when it comes to photo, video, and even sound. And if you&#8217;re someone who needs more than those programs offer, you can always try something from Adobe.</p>
<p>The second reason is <a href="http://propresenter.com/" target="_blank">ProPresenter</a>. ProPresenter is the leading presentation software for the Mac. While programs such as <a href="http://www.mediashout.com/" target="_blank">MediaShout</a> and <a href="http://easyworship.com/" target="_blank">EasyWorship</a> are great for the PC, I believe ProPresenter does a much better job. Like everything else about a Mac, ProPresenter is very user friendly, and easy to pick up even for someone who has never even seen it before. It does a great job handling lyrics, backgrounds, videos, etc. Version 4 will be coming out soon, and it looks like it&#8217;s going to include many new and useful features. I can&#8217;t wait to check it out. One of the most interesting features I&#8217;ve seen is the apparent ease of importing PowerPoint presentations. Now, having not been able to test this firsthand, I can&#8217;t vouch for how easy it is, but they claim it&#8217;s pretty seamless. Stage Display is another very useful looking feature, which allows you to format a display specifically suited for those on stage.</p>
<p>Right now, the church I attend is using <a href="http://songshow.com/Default.aspx" target="_blank">SongShow Plus</a>, but I&#8217;m planning on upgrading to EasyWorship 2009 in the near future. SongShow is very outdated and hard to use, compared to all of the other products available. As much as I like EasyWorship, I would switch to ProPresenter in a heartbeat if we could afford the extra expense of purchasing a Mac. The main reason for that is I trust a Mac much more than a PC. I know this is going to stir up some debate, but that&#8217;s ok, I&#8217;m ready for it. I&#8217;ve had many more problems out of PC&#8217;s I&#8217;ve owned in the past than I&#8217;ve had from my MacBook Pro.</p>
<p>Those are just a couple of the reasons I would choose a Mac over a PC in a worship environment. The church I volunteer in actually uses a PC, but again, if it were up to me we would have a Mac. Disagree? You can find me on Twitter, <a href="http://twitter.com/chaselivingston" target="_blank">@chaselivingston</a>, I&#8217;d love to discuss the topic further. Also, for further discussion, please check out the forum, <a href="http://forum.churchtechmatters.com/viewtopic.php?f=28&amp;t=34" target="_blank">here</a>.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=New+CTM+post:+Why+a+Mac+in+Church%3F+http://x99id.th8.us" title="Post to Twitter"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-twitter-big2.png" alt="Post to Twitter" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/10/12/why-a-mac-in-church/&amp;title=Why+a+Mac+in+Church%3F" title="Post to Digg"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-digg-big2.png" alt="Post to Digg" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/10/12/why-a-mac-in-church/&amp;title=Why+a+Mac+in+Church%3F" title="Post to Digg">Digg This Post</a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=qGU6fG2MFa4:G44ItOR0w28:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=qGU6fG2MFa4:G44ItOR0w28:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=qGU6fG2MFa4:G44ItOR0w28:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=qGU6fG2MFa4:G44ItOR0w28:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=qGU6fG2MFa4:G44ItOR0w28:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=qGU6fG2MFa4:G44ItOR0w28:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=qGU6fG2MFa4:G44ItOR0w28:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=qGU6fG2MFa4:G44ItOR0w28:kspCdTTORlE"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=kspCdTTORlE" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/qGU6fG2MFa4" height="1" width="1"/>]]></content:encoded><description>Well, I&amp;#8217;m glad you asked. Up until about a year and a half ago when I bought my first Mac, I was very against the whole idea. I thought Macs were just overpriced, hard to use, and incompatible with the rest of the world. But then, after playing with a few of my friend&amp;#8217;s Macs, [...]</description><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">9</thr:total><creativeCommons:license>http://creativecommons.org/licenses/by-nd/2.0/</creativeCommons:license><feedburner:origLink>http://churchtechmatters.com/2009/10/12/why-a-mac-in-church/</feedburner:origLink></item><item><title>New CTM Writer – Chase Livingston</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/ShLPpfXHCnY/</link><category>Uncategorized</category><category>media</category><category>churchtech</category><category>volunteers</category><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jim Walton</dc:creator><pubDate>Mon, 21 Sep 2009 21:04:38 PDT</pubDate><guid isPermaLink="false">http://churchtechmatters.com/?p=1375</guid><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>I am really excited to introduce to you someone I have followed on Twitter for a few months.  He is a tech volunteer at his church and has been for quite some time and he struck me as someone who has a story to tell.  To begin this story, I thought I would interview him, so here goes!</p>
<p><strong>What is your name?</strong></p>
<p style="padding-left: 30px;">Chase Livingston, aka <a title="@chaselivingston" href="http://www.twitter.com/chaselivingston" target="_blank">@chaselivingston</a></p>
<p><strong>I realize you are a tech volunteer at your church, as many of us are, what do you do fulltime?</strong></p>
<p style="padding-left: 30px;">I&#8217;m a college student at Clemson University, studying Electrical Engineering. That basically means I study all the time, and tweet about how boring or hard my classes are.</p>
<p><strong>What is the name of your church?</strong></p>
<p style="padding-left: 30px;"><strong><span style="font-weight: normal;">Mountain Creek Baptist Church</span></strong></p>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>What is Mountain Creek&#8217;s average attendance each weekend?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">I don&#8217;t know the exact number, and I&#8217;m glad I&#8217;m not the guy who has to count, but I think it&#8217;s between 200 and 300.</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>How long have you been involved with sound and media with your church?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">I&#8217;ve been doing it at Mountain Creek pretty much since I started going there about 4 or 5 years ago.</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>So, you started when you were how old?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">I really started with church media when I was about 13. There was a wedding at my grandparents church, and they didn&#8217;t have anyone to run sound. My grandfather knew I was into computers, and technical stuff, so he asked if I would be willing to help out. Being a true techie, I of course agreed. That was my first experience behind a sound board, and what really sparked my interest in everything I&#8217;m into now.</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>Describe a typical Sunday morning (What time do you arrive, routines you have, number of people that are involved etc)</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">I normally arrive about 8:30am for the service that starts at 10:30am. First things first, I get everything powered up and ready to go for the worship team to have a run through/sound check. They normally arrive about 9:00am to do that, then by the time they&#8217;re finished, the other guy who runs the projection PC is ready to pull up the song lyrics we&#8217;ll need, announcement slides, sermon slides, etc. We normally do some editing to the announcement slides and sermon slides to make them look as good as possible. By the time all that is done it&#8217;s about time for the service to start, and from then on, I&#8217;m pretty much behind the sound board.</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>How closely do you work with your worship pastor and what is his role in the sound/media/tech side of things?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">Well, first of all my worship pastor is a she. Just thought we should clear that up. I work pretty closely with her, she is the person on staff who is responsible for the tech side of things. Basically that means she&#8217;s in charge of letting me and the other guys know what needs to be done, and we do our best to make it happen. She&#8217;s also very helpful in giving us the lyrics for the songs we&#8217;ll be doing in worship to make sure we have the right lyrics in our database, and also the right order. She&#8217;s also responsible for the basic programming of the service, which is the order of service, where each service element goes, etc.</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>In all that you are involved in, is there a single thing that just really gets you going?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">I get really annoyed when someone brings me a video or something at the last minute and wants to show it in the service. I haven&#8217;t had time to preview it or sound check it. Really just not having enough preparation time in general really gets on my nerves. Many of my friends make fun of me because I&#8217;m usually super early everywhere I go, but to me, it gives me plenty of time to prepare for anything that could go wrong, or at least prevent the preventable things from going wrong.</div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>What are you passionate about?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">I am passionate about using technology in church to enhance the worship experience of everyone there. I know that my generation is especially drawn to anything to do with technology, so if they see a church that uses tech in cool and innovative ways, they are drawn to it. I also believe that if done wrong, it can be a detriment to the worship experience. There is a very fine line and I am constantly reading and trying to learn from other people who are definitely better than me about how they utilize technology in their church.</div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>I have heard rumors that you are moonlighting at a little church called <a title="New Spring" href="http://www.newspring.cc/" target="_blank">New Spring</a></strong><strong>. What&#8217;s that about?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">Well, I think <a title="New Spring" href="http://www.newspring.cc/" target="_blank">New Spring</a> is a great church, and I have been visiting there recently since I&#8217;m back at school and it&#8217;s pretty close. I have followed a lot of their staff on Twitter for a while, so I&#8217;m constantly trying to learn from them, because they&#8217;re really good at what they do. Who knows, maybe I&#8217;ll end up working with them someday.</div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>What is something about <a title="New Spring" href="http://www.newspring.cc/" target="_blank">New Spring</a>&#8217;s A/V/L and production that surprises you?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">Well, the obvious is that there&#8217;s so much of it. I feel they use technology very well in their services. Everything works together well, and like I talked about in one of the previous questions, it enhances the worship experience. But beyond the cool factor of all the technology, they work really hard to get it to the level that it&#8217;s at. I had the opportunity to sit in the control room with some of the volunteers a couple weeks back, and their preparation and execution of the service is amazing. You can tell they work hard to minimize mistakes, but when they do happen (and they are going to in any church), they do the best they can to minimize the impact on the service. I believe their attitude of &#8220;we can always make it better,&#8221; is something all churches and tech guys could learn from, including myself.</div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>Are there any production similarities between <a title="New Spring" href="http://www.newspring.cc/" target="_blank">New Spring</a> and Mountain Creek?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">No, there really aren&#8217;t too many. Mountain Creek is a very traditional church, while NewSpring is obviously very contemporary. Many of the people at Mountain Creek aren&#8217;t as receptive to technology in the service as they are at NewSpring. We have a lot of older members, so we try to respect them as much as we can, while not compromising our goal of reaching the lost.</div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>When you are not in school or serving at church, what other things occupy your time?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">I am a self professed computer nerd. I love learning about the newest thing, or reading about the newest releases when it comes to technology. I always want to try out the latest and greatest things before anyone else. Also, along these lines, I&#8217;m always trying to get ideas from other people in the church tech/media field. I read a lot of blogs and watch some podcasts, always trying to sharpen my skills. I also really love cars. I&#8217;ve been fascinated by them ever since I was a kid, so whenever I get the chance to go to a car show, or work on a car, I always take it.</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>What church leaders do you read and/or follow?</strong></div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">This is quite a long list. It would probably be easier for anyone who wants to know to look through my Twitter followers or find me on Google Reader. But to name a few, I read pretty much everyone from NewSpring, Ed Stetzer, Alvin Reid, Thom Rainer, Steven Furtick, Pete Wilson, Tim Stevens, etc. I&#8217;m sure I&#8217;m leaving a lot of really cool people out, so if you have any recommendations, please let me know.</div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>Any thoughts on how to build community among church tech volunteers?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">Well, to build community anywhere, the first thing I would recommend is just spending time with the people you are trying to build community with. Get to know them, and their stories. Everyone likes to eat, so get everyone together and go out to eat, or find something that everyone likes to do, and go do that. Invest in each other.</div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>Any conferences in your future?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">Well, by the grace of God I&#8217;m going to Catalyst in October. I&#8217;m so excited, I can&#8217;t even explain it. Everyone keeps telling me what an awesome experience it is, so I&#8217;m really looking forward to it. I&#8217;m going to try and blog as much as I can about it, so stay tuned for that, maybe Jim will post some of it on CTM. Also in January I&#8217;m going to Passion 2010. It&#8217;s basically a huge conference for young adults, started by Louie Giglio. I&#8217;ve also heard many great things about it, including the face that Hillsong United will be playing, so I am super excited about that. Again, hopefully I will be able to blog a little about my experiences.</div>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><strong>Do you ever get burned out on serving in the church? What have you done to deal with that?</strong></div>
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;">Yeah, I definitely do, I think everyone does at some point. I&#8217;m sure everyone involved with church tech loves what they do, but sometimes it just gets tiring. I try and take a step back, maybe take a week or two off from it, and just be a regular church member for a while. By regular church member, I mean just sit and enjoy the service, rather than working during it.</div>
<div style="margin-top: 0px; margin-bottom: 0px; padding-left: 30px;"></div>
<div style="margin-top: 0px; margin-bottom: 0px;">So, join me in welcoming Chase! I think he will definitely add an interesting perspective and there&#8217;s even a good chance we can all learn a thing or two from him.</div>
</div>
</div>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=New+CTM+post:+New+CTM+Writer+%E2%80%93+Chase+Livingston+http://wgay8.th8.us" title="Post to Twitter"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-twitter-big2.png" alt="Post to Twitter" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/09/21/chase/&amp;title=New+CTM+Writer+%E2%80%93+Chase+Livingston" title="Post to Digg"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-digg-big2.png" alt="Post to Digg" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/09/21/chase/&amp;title=New+CTM+Writer+%E2%80%93+Chase+Livingston" title="Post to Digg">Digg This Post</a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=ShLPpfXHCnY:VmB6RctQIq0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=ShLPpfXHCnY:VmB6RctQIq0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=ShLPpfXHCnY:VmB6RctQIq0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=ShLPpfXHCnY:VmB6RctQIq0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=ShLPpfXHCnY:VmB6RctQIq0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=ShLPpfXHCnY:VmB6RctQIq0:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=ShLPpfXHCnY:VmB6RctQIq0:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=ShLPpfXHCnY:VmB6RctQIq0:kspCdTTORlE"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=kspCdTTORlE" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/ShLPpfXHCnY" height="1" width="1"/>]]></content:encoded><description>I am really excited to introduce to you someone I have followed on Twitter for a few months.  He is a tech volunteer at his church and has been for quite some time and he struck me as someone who has a story to tell.  To begin this story, I thought I would interview him, [...]</description><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><creativeCommons:license>http://creativecommons.org/licenses/by-nd/2.0/</creativeCommons:license><feedburner:origLink>http://churchtechmatters.com/2009/09/21/chase/</feedburner:origLink></item><item><title>EasyWorship 2009: Display Foldback Overview</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/dOgZ-g_Pf84/</link><category>Church IT</category><category>Presentation</category><category>Tech Arts Team</category><category>easyworship</category><category>media</category><category>software</category><category>support</category><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Meyer</dc:creator><pubDate>Sun, 20 Sep 2009 20:40:55 PDT</pubDate><guid isPermaLink="false">http://churchtechmatters.com/?p=1367</guid><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>If you’re an EasyWorship user, there’s a new version available for you. EasyWorship 2009 was released recently, and it has several new features. One of the features that is causing some interest and even confusion is Display Foldback.</p>
<p>I’ve been using EasyWorship 2009 at our church for a few months now in its beta form, and it has been rock-solid. Our worship team really likes the Display Foldback capabilities, and has made it clear that this feature alone is worth the upgrade fee.</p>
<p>So, what is Display Foldback? Basically, it’s support for a third output from the computer that is intended specifically for the people on stage. It supports different settings for backgrounds and font size and style. In addition, you can display a clock for the worship team and preacher to use. Perhaps my favorite part of the system is that you can display the first line of the next slide in case your slide operator falls asleep at the wheel.</p>
<p><img title="Display Foldback comparison" src="http://farm3.static.flickr.com/2621/3940039474_1519108fbf_o.png" alt="" width="535" height="170" /></p>
<p>Display Foldback requires an additional level of hardware that you may not already have. You’ll need a third display output, which for many churches, means purchasing an extra video card. Our setup is unconventional, but it works all the same. We use the integrated video on the motherboard for our control screen. Then, a single PCI-E video card sends VGA to the congregation and Foldback to the stage via composite video. You could do any combination of video cards and monitors from something like what we use all the way to three independent cards.</p>
<p>Once your hardware is in place, setup is simple. First, configure Windows so that all three outputs are active. Hit the “Identify” button to be sure you’re not duplicating a certain output across two screens. You’ll want to see a “1” on the control screen, a “2” on the congregation screen, and a “3” on the foldback monitor. Then, start up EasyWorship. In the Live &gt; Options pane, set the main (congregation) output to “Secondary Monitor”. Click Ok. Now, in the Live &gt; Display Foldback Options pane and under the “Display Foldback” heading, change the dropdown menu selection to “Monitor 3” or whatever yours may be called.</p>
<p>That’s it! Change the Display Foldback settings as you see fit. Most of the foldback pane is similar to what you&#8217;ll see in the main Display Options pane, so you should be familiar with what you&#8217;re looking at. A plain background with the clock and next line preview turned on seems to work well for us.</p>
<p>There are two more features related to Display Foldback I’d like to mention. First is the “Foldback Alert”, found at Live &gt; Alerts &gt; Foldback Alert, or the Alerts button just to the left of the Logo, Black and Clear buttons. There, you can send a message only to the stage. Operation is identical to the “Message Alert”.</p>
<p>The other feature is enhanced PowerPoint slide operation. In the Live &gt; Display Foldback Options pane and in the PowerPoint Options tab, there are some options to add thumbnails of the next few upcoming slides. You can change the size of the previews as a percentage of screen height. However, if your foldback monitor is not very large or it is positioned far away, sharing that screen with thumbnails makes the primary slide small and hard to read very quickly.</p>
<p>All in all, EasyWorship 2009 is a good upgrade, and there are many more features besides Display Foldback. Another feature that I like is webpage integration, especially for YouTube.</p>
<p>Prices are $399 for a new license, $99 for an upgrade and free if you have purchased since the beginning of 2009. More information can be found at <a style="color: #1c51a8;" href="http://www.easyworship.com/" target="_blank">http://www.easyworship.com</a></p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=New+CTM+post:+EasyWorship+2009%3A+Display+Foldback+Overview+http://sgg7o.th8.us" title="Post to Twitter"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-twitter-big2.png" alt="Post to Twitter" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/09/20/easyworship-2009-display-foldback-overview/&amp;title=EasyWorship+2009%3A+Display+Foldback+Overview" title="Post to Digg"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-digg-big2.png" alt="Post to Digg" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/09/20/easyworship-2009-display-foldback-overview/&amp;title=EasyWorship+2009%3A+Display+Foldback+Overview" title="Post to Digg">Digg This Post</a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=dOgZ-g_Pf84:Z6jNgMwNCNc:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=dOgZ-g_Pf84:Z6jNgMwNCNc:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=dOgZ-g_Pf84:Z6jNgMwNCNc:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=dOgZ-g_Pf84:Z6jNgMwNCNc:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=dOgZ-g_Pf84:Z6jNgMwNCNc:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=dOgZ-g_Pf84:Z6jNgMwNCNc:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=dOgZ-g_Pf84:Z6jNgMwNCNc:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=dOgZ-g_Pf84:Z6jNgMwNCNc:kspCdTTORlE"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=kspCdTTORlE" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/dOgZ-g_Pf84" height="1" width="1"/>]]></content:encoded><description>If you’re an EasyWorship user, there’s a new version available for you. EasyWorship 2009 was released recently, and it has several new features. One of the features that is causing some interest and even confusion is Display Foldback.
I’ve been using EasyWorship 2009 at our church for a few months now in its beta form, and [...]</description><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><creativeCommons:license>http://creativecommons.org/licenses/by-nd/2.0/</creativeCommons:license><feedburner:origLink>http://churchtechmatters.com/2009/09/20/easyworship-2009-display-foldback-overview/</feedburner:origLink></item><item><title>Build a Website – Part Three</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/sgcHXgm2j44/</link><category>Equipping</category><category>media</category><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stuart</dc:creator><pubDate>Sat, 19 Sep 2009 16:10:36 PDT</pubDate><guid isPermaLink="false">http://churchtechmatters.com/?p=1358</guid><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><img class="alignnone size-full wp-image-1359" title="content-creation-box" src="http://churchtechmatters.com/wp-content/uploads/2009/09/content-creation-box.png" alt="content-creation-box" width="147" height="101" /></p>
<p>Part 3 is all about Content Creation. Parts 1 and 2 can be found <strong><a title="Link to part 1 of series" href="http://churchtechmatters.com/2009/06/14/build-a-website-intro/">here</a></strong> and <strong><a title="Link to part 2 of series" href="http://churchtechmatters.com/2009/07/24/build-a-website-part-deux/">here</a></strong>.</p>
<p>As project lead I was quite happy that this burden wasn&#8217;t on me. However it was down to me to drive the provision of it and to keep advising, suggesting, etc. Of course the type of site and target audience really drives the content. In our case the site I documented this process for was (<em>another story for another time</em>) our main church website.</p>
<p>The boss man wanted to effectively transplant our monthly newsletter; notices; calendar and his monthly message to the web. He also wanted it to be a place to publicly place our Church history along with items about why we believe what we believe and other associated, relevant to our Church information. The trouble with most of the documents produced is that they were full of what I&#8217;d call &#8220;Christianeese&#8221; and to a non-Church person they were dry and very boring.</p>
<p><span id="more-1358"></span></p>
<p>So with some trepidation I set out, along with a contact, to de-mystify the documents. Along with this was a need to categorise the data so that it could be placed on the website. When first we started the project I spoke at some length with my pastor about the need to &#8216;categorise&#8217; the data he wanted on the site and to have an idea of what headings it should come under. I pointed him at resources such as<strong> <a title="Link to study" href="http://www.eastonmass.net/tullis/WebsiteNavigation/WebsiteNavigationPaper.htm" target="_blank">menu layout study</a></strong> and <strong><a title="Layout Cookbook link" href="http://www.layoutcookbook.com/" target="_blank">Layout Cookbook</a></strong> so that he could see what was normal and what was acceptable. Little did I realise my error at the time but it was fortunately easily fixed. Within a few weeks I had been provided with raw data and no less than 14 main menu headings, along with many more sub headings &#8211; a potential nightmare for any designer, let alone the visual impact.</p>
<p>Thankfully we whittled this down to 6 major headings that we now have. We did this by a process of categorising the data and identifying where it could be placed.</p>
<p>Along with creating the content, you have to consider at whom it is aimed. This was a lot easier to argue the case that any (<em>and yes I believe this should hold true for all</em>) church site should target three distinct demographics. These are:</p>
<ul>
<li> The church membership / attendees</li>
<li>Other Christians visiting or moving into the area</li>
<li>Seekers</li>
</ul>
<p>How one does this is not easy but a lot of it has to be driven by talk. In our case it was easy to persuade the pastor that just doing a website for the church would make it a relatively static site and would defeat the main object of the web (as I see it) to be interactive. And here, interactivity doesn’t mean lots of buttons to press or things to do – simply that it draws in the attention of the reader and persuades them to return. Add to this the fact that we’ve had visitors over the years that told the pastor by email / chat / etc that they had found it really difficult to know when / where our services were and that our website was dreadful (<em>I confess, this last was my fault</em>) but I did it so that we had something and to show the pastor how bad a static content site can be.</p>
<p>Anyway, this talk from outsiders finally persuaded the pastor that we needed to do something about our online presence.</p>
<p>Now that this hurdle was over I hammered home the need to ensure the site was not static. Now you may have an easier time of this than I, but whilst my pastor is a happy user of the internet (<em>surfing and emails</em>) and despite being a few years younger than I; he has publically stated on more than one occasion that you&#8217;ll &#8220;never find him on facebook, myspace or similar locales&#8221;.</p>
<p>Thankfully a few web searches produced lots of articles and ideas that I was able to forward to him to get his thought processes running. Little things like telling him the stuffy (<em>they&#8217;re not, but it  served a purpose</em>) old CofE use twitter to run their annual &#8216;<strong><a title="CofE Link" href="http://www.livelent.net/" target="_blank">Love Life Live Lent</a></strong>&#8216; event and suddenly he&#8217;s thinking perhaps I should involve my self more.</p>
<p>For our part, interactive is going to come down to regular and changing content especially on the homepage. So transplanting his monthly magazine article to the web is one; persuading him to write more often is another; remembering to get any flyers designed for events into a web based graphic to go on our front page; to ensure that (<em>as an example</em>) the children&#8217;s page has regular updates and with content suitable to all ages; add pictures and graphics where appropriate and change them oin a regular basis. In fact anything that makes me, you or someone else keep returning.</p>
<p>I&#8217;m going to stop now as I could keep driving the nail home but want to leave you still breathing. In the final part of this series I intend to cover dealing with leadership issues; employing third parties and find some form of conclusion.</p>
<p>In the meantime &#8211; should you have any questions or wnat to continue discussing this then do pop over to the <strong><a title="CTM Forum" href="http://forum.churchtechmatters.com/about-ctm">CTM Forum</a></strong> and have your say.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=New+CTM+post:+Build+a+Website+%E2%80%93+Part+Three+http://x96ip.th8.us" title="Post to Twitter"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-twitter-big2.png" alt="Post to Twitter" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/09/19/build-a-website-part-three/&amp;title=Build+a+Website+%E2%80%93+Part+Three" title="Post to Digg"><img class="nothumb" src="http://churchtechmatters.com/wp-content/plugins/tweet-this/icons/tt-digg-big2.png" alt="Post to Digg" /></a> <a class="tt" href="http://digg.com/submit?url=http://churchtechmatters.com/2009/09/19/build-a-website-part-three/&amp;title=Build+a+Website+%E2%80%93+Part+Three" title="Post to Digg">Digg This Post</a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=sgcHXgm2j44:es5PH9-ld0Y:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=sgcHXgm2j44:es5PH9-ld0Y:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=sgcHXgm2j44:es5PH9-ld0Y:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=sgcHXgm2j44:es5PH9-ld0Y:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=sgcHXgm2j44:es5PH9-ld0Y:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=sgcHXgm2j44:es5PH9-ld0Y:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?i=sgcHXgm2j44:es5PH9-ld0Y:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ChurchTechMatters?a=sgcHXgm2j44:es5PH9-ld0Y:kspCdTTORlE"><img src="http://feeds.feedburner.com/~ff/ChurchTechMatters?d=kspCdTTORlE" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/sgcHXgm2j44" height="1" width="1"/>]]></content:encoded><description>Part 3 is all about Content Creation. Parts 1 and 2 can be found here and here.
As project lead I was quite happy that this burden wasn&amp;#8217;t on me. However it was down to me to drive the provision of it and to keep advising, suggesting, etc. Of course the type of site and target [...]</description><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><creativeCommons:license>http://creativecommons.org/licenses/by-nd/2.0/</creativeCommons:license><feedburner:origLink>http://churchtechmatters.com/2009/09/19/build-a-website-part-three/</feedburner:origLink></item><item><title>Links for 2006-03-23 [del.icio.us]</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/x3zZkSdMfXY/okwithat</link><pubDate>Fri, 24 Mar 2006 00:00:00 PST</pubDate><guid isPermaLink="false">http://del.icio.us/okwithat#2006-03-23</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://graphicdesign.about.com/library/weekly/aa092702a.htm"&gt;How do you Rate?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/x3zZkSdMfXY" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/okwithat#2006-03-23</feedburner:origLink></item><item><title>Links for 2006-03-21 [del.icio.us]</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/mmm83ewwOXs/okwithat</link><pubDate>Wed, 22 Mar 2006 00:00:00 PST</pubDate><guid isPermaLink="false">http://del.icio.us/okwithat#2006-03-21</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.adaptivepath.com/publications/essays/archives/000385.php"&gt;adaptive path &amp;raquo; ajax: a new approach to web applications&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/mmm83ewwOXs" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/okwithat#2006-03-21</feedburner:origLink></item><item><title>Links for 2006-02-26 [del.icio.us]</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/jLzJyGlEkUY/okwithat</link><pubDate>Mon, 27 Feb 2006 00:00:00 PST</pubDate><guid isPermaLink="false">http://del.icio.us/okwithat#2006-02-26</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://blog.hishamrana.com/2006/02/22/how-to-image-windows-xp-with-ghost-and-sysprep/"&gt;How-To: Image Windows XP with Ghost and Sysprep at Hisham&amp;rsquo;s Blog&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/jLzJyGlEkUY" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/okwithat#2006-02-26</feedburner:origLink></item><item><title>Links for 2006-02-24 [del.icio.us]</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/jy5fA3kvpVc/okwithat</link><pubDate>Sat, 25 Feb 2006 00:00:00 PST</pubDate><guid isPermaLink="false">http://del.icio.us/okwithat#2006-02-24</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.howtheinternetruns.com/"&gt;How the Internet Runs!&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.christianpodder.com/"&gt;Christian Podder&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/jy5fA3kvpVc" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/okwithat#2006-02-24</feedburner:origLink></item><item><title>Links for 2006-02-22 [del.icio.us]</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/7lnQEnSZbHc/okwithat</link><pubDate>Thu, 23 Feb 2006 00:00:00 PST</pubDate><guid isPermaLink="false">http://del.icio.us/okwithat#2006-02-22</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://ma.gnolia.com/"&gt;Ma.gnolia Social Bookmarking: Search and Find Web Sites &amp;amp; Build Community Online.&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/7lnQEnSZbHc" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/okwithat#2006-02-22</feedburner:origLink></item><item><title>Links for 2006-02-21 [del.icio.us]</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/HJ-Sbfe_ZSE/okwithat</link><pubDate>Wed, 22 Feb 2006 00:00:00 PST</pubDate><guid isPermaLink="false">http://del.icio.us/okwithat#2006-02-21</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.rbc.org/ds/q0610/point3.html"&gt;What If It&amp;rsquo;s True That The Church Is More Than Just Hypocrites?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.yale.edu/ynhti/curriculum/units/1998/3/98.03.07.x.html"&gt;98.03.07: Masks and the Stories Behind Them&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/HJ-Sbfe_ZSE" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/okwithat#2006-02-21</feedburner:origLink></item><item><title>Links for 2006-02-17 [del.icio.us]</title><link>http://feedproxy.google.com/~r/ChurchTechMatters/~3/RUc9pSMynfs/okwithat</link><pubDate>Sat, 18 Feb 2006 00:00:00 PST</pubDate><guid isPermaLink="false">http://del.icio.us/okwithat#2006-02-17</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.coffee2code.com/"&gt;coffee2code.com&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/ChurchTechMatters/~4/RUc9pSMynfs" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/okwithat#2006-02-17</feedburner:origLink></item></channel></rss>
