Tech Checks Guide

Thank you for volunteering to help out with tech checks in an upcoming Pixel Perfect Event. If you think of a speedrun marathon as a sandwich, with the run as the filling, the host being the butter, and tech as the bread, the tech check is the process of purchasing those ingredients, you can't make the sandwich if you haven't prepared it first. Tech checks are essential for ensuring runners are prepared ahead of time, solving any potential issues before the marathon has started, and allowing for speedy intermissions once the event is underway.

Organising Tech Checks

PPM# Full Schedule Tech Sheet

The Tech Check

Organising Tech Checks

Tech checks usually start three weeks before an event, and run for two weeks. That gives the runners a decent scope for fitting one in, and ensures they're all completed with a week spare, in case of any issues. They're booked using a Google Sheet like the one below, the link for which will be pinned on Discord:

Tech Check Timetable Sheet

Runner Check Sheet

Runners will enter their name in the Tech Check Timetable Sheet to book a slot. It is up to the Tech Check team to check the spreadsheet periodically and add their name next to any tech check they're able to complete. If a booking is getting close, no-one has claimed it and you know you can't make it, ping @PPMX-Tech to let others know a booking is urgent.

The Runner Check Sheet automatically records if a runner has booked in a Tech Check. Don't worry if a runner hasn't booked in and the deadline is approaching, it's @Staff's responsibility to monitor this, not yours. Once a runner's check has been completed, you can add any notes in the complete column, so any custom settings for that runner can be picked up during the marathon.

PPM# Full Schedule Tech Sheet

The other Google Sheet you'll access is the PPM# Full Schedule. This is a master spreadsheet that contains all of the information all volunteers need about the event. Please do not edit anything in this spreadsheet. Runners do not have access to this sheet.

One of the sheets in this workbook is the Tech Sheet. This sheet includes each runner, their closest server, whether they've requested additional tech help and their stream URLs. We'll refer to this sheet throughout the guide and the link to it can be found in the pinned posts of the Tech area on Discord.

The Tech Check

When you're ready for a scheduled tech check, meet up with the runner in the Back Room voice channel. Only the runner will be present, their commentators are not required to join. Any racers or multiple-person runners will complete tech checks separately and not together.

The runner should have already set up their own Portable OBS with the instructions they were given - it is not your job to set it up for them. If they are not prepared at all, you are welcome to instruct them to go back and follow the instructions first and then book another timeslot. However, if they've already tried and have had problems, or they specifically advised that they'd like additional help (this will have been advised on the PPM# Full Schedule Tech Sheet) you should of course assist them. Check out the Runner Setup Guide for details on what they're expected to do. If you need to see what they're doing on OBS, ask them to stream their OBS view on Discord.

Streamkey

Each runner has a unique streamkey and these are provided at the time of the tech check and their run. The PPM# Full Schedule Tech Sheet advises these - there is a separate one for the tech check and the run. Provide the runner with the full tech URL which will look something like this:

https://ams3-tech.capture.pixelperfect.events:3334/capture/RUNNER?direction=whip&transport=tcp

The runner will need to paste this into 'Settings' > 'Stream' > 'Server'. They should not need to touch any other settings - the 'Bearer Token' entry on the page should remain blank.

Viewing The Stream

To view a runner's stream, first ask them to start streaming. Then head to https://capture.pixelperfect.events where you'll be presented with the screen on the right.

In the 'Streamkey' field, enter just the runner's name as it appears in the PPM# Full Schedule Tech Sheet - do not paste the whole URL.

In the left drop-down, select the Tech-check server the runner is closest to, again this is advised in the PPM# Full Schedule Tech Sheet. Leave the right drop-down as 'Capture' unless @Staff have advised switching to 'Backup'.

Click 'Viewer' and you should be taken to a video screen. Click play, and you should see the runner's stream. If it doesn't, refresh the page and try again. If it still doesn't show, check:

a. The runner is streaming

b. The runner's stream key is what you sent them

c. The runner has selected a profile that matches their set-up

If you're confident these are correct, you'll need to contact @Staff.

Enter only the name of the runner, not the full URL

Once their stream is visible, check to make sure it looks correct:

The runner is using the correct stream profile
Runners have several stream options available to them. If they're running a modern, full HD game, you should be receiving their stream at 1080p & 60fps. If they're running an older or retro style game, you should be receiving their stream at 720p & 60fps. Those with weaker internet connections will have used lower settings, just double-check which setting they've used and that they've deliberately picked it. The available profiles can be found in the Runner Setup Guide.
The stream looks mostly stable
The runner's game should look good and run at a stable frame rate with no big hitches. Some minor jumps are to be expected as we use a cheaper and busier server for Tech Checks, so these minor hiccups shouldn't occur during the full run. But if the stream is continuously poor, ask the runner to drop down their stream profile to the next setting.
The runner is using the correct stream layout
If incorrect, ask them to select a different scene in their OBS; you can check the schedule to see which one they should be using.
There are no black borders around the webcam or game feeds
If the runner's feed is already black like in the screenshot above, ask them to show you some gameplay where the background isn't black. If there are any black borders, ask them to adjust the crop filter on the game/camera source.

Audio Check

The runner's stream should only be sending their game's audio:

If you're receiving their voice through the stream, ask them to remove the mic as a source in their OBS.
If you can't hear their game, ask them to check if one of their audio sources is showing that sound is being picked up. The source that captures the video should also capture the audio, but if that isn't working, there is a Backup Audio that they can manually set.
If you can hear desktop sounds (such as your voice through their Discord), this means they've added their desktop audio instead of their game audio.
If you click on 'Toggle Meter' underneath the stream you're watching, you'll be given an audio meter. The runner's game volume should be peaking around the -25 to -20 mark (it's ok if very occasional loud noises goes over this slightly).

Get the runner to play a particularly noisy section of the game, and get them to adjust their own OBS slider or in-game volume until the audio is peaking at the right spot.
If the audio is too quiet and the runner can't turn it up any further, ask the runner to right-click on the source in OBS, click 'Filters', and add a 'Gain' filter. Get them to adjust this filter until the volume is correct and note the level you've added in the Runner Check Sheet.

All voice audio from the runner(s), commentators, and host will come through Discord. You don't need to worry about this now, as you only have the runner with you at the tech check. These will be balanced before their run starts on the day.

Stream Quality

Once you're happy that everything is set up correctly, ask the runner to just play the game for a few minutes. This is to ensure the stream stays stable over some time. Use this time to monitor the stream and look out for any issues, both from the game and from their camera.

If you see any issues, ask the runner to check the stats on their OBS for any dropped frames, or high CPU usage. If they report that they are seeing these issues, ask them to stop streaming, drop to a lower stream profile or reduce the load on their PC (close other programs, turn down in game settings) and try again. If you're unable to get a consistent stream from them for five minutes, report this back to @Staff after the tech check.

Once happy, thank the runner for their time and advise them not to make any changes to their setup before the marathon. Remember to add any notes to the Runner Check Sheet once you're finished. If you've tech checked a race, note down which side of the screen the runner is on - hopefully both racers will have agreed upon which side they're using.

Google Sites

Report abuse