Weeknotes: Saturday 22 May

Another week has gone by, and the tech team have done some more stuff.

(Re)discovering the light

We did some investigation on how the church’s lighting is controlled behind the scenes so that we could make some recommendations on future improvements.

At the moment we don’t have any particular plans for this, but many things have been suggested including coloured lighting, more granular control, automation, and integrating our external lighting. Knowing how our existing system works means we can make more informed decisions about which of these are feasible, both in terms of raw cost and in terms of effort, so that we can decide which (if any) are worth pursuing.

Thinking about the North aisle

Possible future works in the church building would involve moving the tech desk, so we did some thinking about where it could go and the implications for how things would look.

Before anything happens here though there are plenty more hoops to jump through!

Weeknotes: Saturday 15 May

Another week, another weeknotes. Here’s what the tech team have been up to!

More technicians!

We’ve trained another video technician, increasing the number of people who can stream and record services.

As with other parts of the Church, it’s important that our technology is understood and usable by enough people to make sure the workload is spread out. Over lockdown this hasn’t been the case, so we’re trying to correct that as quickly as possible.

It’s also a great opportunity to revise our documentation and make sure that it’s clear and comprehensive.

Defeating the cable snake

Anyone who has ever put more than two cables in the same place will know how quickly they get tangled. Our tech desk has literally dozens of them, for audio, video, data and power. You can imagine how chaotic this can become.

One of our ongoing battles is making sure all our cables are kept as tidy and organised as possible. It’s not just for the look of things (although we all appreciate a clean desk), but also to help make faults easier to diagnose, make changes simpler, and make it less likely that moving one thing will disturb something else.

To help in this we’ve re-organised a chunk of our cables (with more to come) using some adjustable, re-usable cable ties. These haven’t just let us keep our spare cables from becoming tangled, but we’ve also used them to help bundle and distinguish cables between different parts of kit.

Weeknotes: Saturday 8 May 2021

Another week, another weeknotes! Here’s what the technical team have been doing:

Further audio refinements

We’ve made some more adjustments to how we pipe audio from our in-church microphones and into our video stream. This gives the technician more control over the different sources of sound, and hopefully will help to reduce some of the echoing which becomes apparent when certain combinations of microphones are used.

Moving the wifi

We’ve changed the position of our wifi transmitter in the church, which should now give better coverage across more of the building.

Weeknotes: Saturday 1 May 2021

Happy long weekend everyone!

The last week for the tech team here at Whitkirk has been all about configuring, optimising and planning. Here’s what we’ve been up to.

A bit of printer tweaking

We’ve changed how our printer is configured to connect to our network. This is a hangover from the days before we had a network spanning two buildings, and the printer was instead plugged directly into the office computer. The change makes it more reliable, more visible to our network management tools, and most crucially enables us to queue print jobs remotely using our VPN.

Optimise all the images

Following on from last week’s website tweaks, we’ve gone through our entire collection of uploaded images and run them through an optimiser, shaving an average of 60% off the size of each image we serve. These small changes add up, especially for people on lower bandwidth connections, making our site seems faster and more responsive.

Continue reading “Weeknotes: Saturday 1 May 2021”

Weeknotes: Saturday 24 April

Now we’re back in the church building we’ve had to make some tweaks to how we stream services, so here’s what happened last week!

Some new audio tweaks

We added two new bits of cabling to our audio setup – one which lets us bring audio from our new PC into the church’s sound system, and one which lets us bring a second output from our mixer into our video stream.

This second output gives us the ability to more cleanly separate the vocal microphones in the church – such as the lectern and altar microphone – from the organ microphone which picks up the music. By doing this we can reduce the amount of chatter which is picked up from the returning congregation at the end of the service, whilst still feeding our organ voluntaries out into the world.

Continue reading “Weeknotes: Saturday 24 April”

Weeknotes: Sunday 18 April

This has been a pretty uneventful week for the tech team, as we’ve focussed on building on last week’s fix for some connectivity problems.

A new router

We’ve switched our existing combination modem/router which connects the Community Centre to the internet into ‘bridge mode’, so it acts exclusively as a modem. To provide routing across our internal network, we’ve added a new, dedicated router.

This brings us a few extra goodies, such as better remote administration, better controls over how we handle data from various devices, and the ability for us to remotely connect to the Church’s network to perform maintenance and diagnose faults from anywhere.

Access point controller

To boost the reliability and flexibility of our wifi networks in the church we’ve added an access point controller, which lets us treat our entire wifi estate as one single managed entity. This helps give us a better image of how things are behaving, which is important as we encourage people to use their own devices to access the order of service.

Weeknotes: Sunday 11 April

After the busyness of Holy Week, what have the tech team been up to?

New PC for the tech desk

Since the beginning of the first lockdown, way back in March last year, every service we’ve streamed has involved some element of borrowed equipment.

This week we finally installed the last piece of the puzzle to allow services to be entirely streamed using our own gear – a small PC that lets the technician manage some of the more advanced features of our video mixer, start and stop the stream, keep an eye on our infrastructure, play audio files and more.

Because we love automation this PC has been hooked into our existing user and device management system, seamlessly setting up user accounts and configuring security policies.

Recording the services

We’ve attached a high-speed disk to the video mixer, so we can directly record services in high quality. In the past we’ve always had to include an extra step in our process to record services, so this not only simplifies our own content pathways for things we do with recordings (like pulling out service audio to deliver via phones and podcasts) and adds certainty that we get a good recording, but also gives us the possibility of offering video recordings of services such as weddings.

Improving the connectivity to the church

Following a particularly bad spell of connectivity which affected our streaming, we spent some time finding and fixing the problem.

Oops: Yet more excessive buffering during a service

Today’s service suffered from very poor connectivity throughout, leading to stuttering and buffering. This wasn’t up to the standard we aim to meet, so we spent a few hours getting to the bottom of exactly what was going on.

So, what was the problem?

After eliminating most possibilities we isolated the fault to the wireless link between the Community Centre and the church. The church building itself has no telephone line, so to provide internet we use a pair of high-power directional wifi devices. One of these is positioned on the outside of the Community Centre, but we’re not able to (and we have no real desire to) fasten one to the outside of our Grade I listed building and ruin the look of things.

Continue reading “Oops: Yet more excessive buffering during a service”