Talking

Talking-Esports-FINAL-2 Talking-Esports-FINAL-2

16.08.2015 Views

EARLY BROADCASTINGTHE FIRST BROADCASTSo you have your software and hardware set up nicely, you’veopened up an account on Twitch and your XSplit is just waiting forsome juicy game content to flow through it: it’s time to find a matchto commentate on.First of all, stick to what you know and find a match from the gameyou play and know best. Ideally, pick a low key match, and not onefrom the upper echelons of the tournaments. That way, you won’tbe so heavily berated for making mistakes or be given a hard time ifsomeone doesn’t like your voice first time out. You should also findclans friendly and receptive to the idea of you covering their game -after all, who doesn’t want to be on TV?To start with, just jump into a game, commentate it and record itfor yourself. Do what you can in terms of commentating and don’tworry too much about anything else at this point. The first fewcommentaries you do will drastically improve every time providedyou follow a few simple steps.First, listen back and watch your first commentary before you doanother one. Then pick out the things you liked, things you didn’tlike (and be honest - it’s just you at this point anyway) and areasyou think you can work on initially. Leave it a day or so, reread yournotes on your first commentary and then find another match tocover. Do the same thing again, record it and watch it back whilemaking notes. Do this three or four times and you’ll already hearhow much better you’re getting each time.15

GOING PUBLICWhen you’re ready to go public (the earlier the better, but you needthick skin, too!), find your match ahead of time - a few hours, usually- and advertise your stream on social media, Reddit and anywhereyou can find that runs community-based forums or sites foryour game.Your first public game also needs a little more depth than just yourcommentary, so ensure you collect some of the basics in terms ofinformation before you go live. It will help you pad out the downtimeand gaps in between maps:Tournament name and structureWhich part of the tournament you are in (semi-finals,league, group stage, etc.)The two teams line-upsSome information on formThis is only really the bare basics, but it will get you up and runningin your early commentaries. Once you’re more comfortable andhave conquered some of the other skills, you can start to add betterpreparation (see later for more information on preparation).If you get a one-sided game and it’s a blowout, that’s when yourpreparation becomes important to maintain the interest in theshow. On a great game, it’s likely you won’t need 80% of your preparation,but don’t get into the bad habit of thinking “I won’t needit”, because one day you seriously will.16

GOING PUBLICWhen you’re ready to go public (the earlier the better, but you needthick skin, too!), find your match ahead of time - a few hours, usually- and advertise your stream on social media, Reddit and anywhereyou can find that runs community-based forums or sites foryour game.Your first public game also needs a little more depth than just yourcommentary, so ensure you collect some of the basics in terms ofinformation before you go live. It will help you pad out the downtimeand gaps in between maps:Tournament name and structureWhich part of the tournament you are in (semi-finals,league, group stage, etc.)The two teams line-upsSome information on formThis is only really the bare basics, but it will get you up and runningin your early commentaries. Once you’re more comfortable andhave conquered some of the other skills, you can start to add betterpreparation (see later for more information on preparation).If you get a one-sided game and it’s a blowout, that’s when yourpreparation becomes important to maintain the interest in theshow. On a great game, it’s likely you won’t need 80% of your preparation,but don’t get into the bad habit of thinking “I won’t needit”, because one day you seriously will.16

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!