Starchive Wiki - User contributions [en-gb]

Create a Jingle

2021-10-13T13:53:06Z

Andrew: Update for 2021

A jingle is a 10-20 second musical introduction that you can play at the start of your show. They are a great way to make your show stand out and create a unique brand and style!

Here's a quick and easy guide to the 4 steps to creating a great jingle:

# '''Find an instrumental you like!''' This can be anything, maybe a piece of instrumental music that evokes the mood of your show or the karaoke version of your favourite tune. You could also search YouTube for "free (lofi/trap/pretty much anything) beats" that can be downloaded with YouTube mp3 converters. Alternatively, if you can't find quite find the right track, message our Head of Production [mailto:production@standrewsradio.com production@standrewsradio.com] with details of what you are looking for and he can try to make something from scratch!
# '''Choose your favourite section.''' Find your favourite section of the instrumental, there's no specific limits but 10-20 seconds is usually a good length. If you are doing voiceover you might want to think about finding a section that will make it easier to hear your voice on top of.
# '''Record a voiceover (optional).''' While listening to the instrumental on headphones, record a voiceover of you introducing your show. If you have co-hosts on your show who also want to feature on the jingle they are welcome to record voiceovers with you or separately. Maybe you have a particular catchphrase or show tagline? What you say is totally up to you but remember this is your chance to build a unique brand for your show! You can use free software such as Audacity to record this or just record with your voice notes on your phone. Don't be afraid to re-record as many times as needed until you find the perfect take. Alternatively if you want your jingle to just be instrumental with no voiceover, then feel free to skip this step.
# '''Email the files to our Head of Production.''' Email the audio files of the instrumental (preferably just the section you want to use but if not timestamps of the section will work too) as well as your final voiceover (if you have one) to [mailto:production@standrewsradio.com production@standrewsradio.com]. Feel free to send guidance on how you would like it all to piece together.

Once your jingle's ready, it'll be put into the playout system and you will be able to play them at the start of your show!

For some examples of great jingles from last year check out the jingles for [https://www.youtube.com/watch?v=fjXHyPUozLM The Record] and [https://www.youtube.com/watch?v=3PPr9gCARvc OK UK].

2021/22

2021-07-08T08:17:12Z

Andrew: Created page with "From April 2021 to March 2022. == Committee == {| class="wikitable" |- ! Position ! Name |- | Station Manager | Julia Swerdlow |- | Deputy Station..."

From April 2021 to March 2022.

== Committee ==
{| class="wikitable"
|-
! Position
! Name
|-
| [[Broadcasting Officer|Station Manager]]
| Julia Swerdlow
|-
| [[Deputy Station Manager|Deputy Station Manager]]
| Rose Kleeger
|-
| [[Secretary]]
| Lynn Nguyen
|-
| [[Treasurer|Treasurer]]
| Joseph Daly
|-
| [[Head of Programming]]
| Joel Butcher
|-
| [[Head of Marketing]]
| Grace Betteridge
|-
| [[Head of Design]]
| Matthew Colquhoun
|-
| [[Head of Production]]
| Brendan Head
|-
| [[starTV|Head of starTV]]
| Eden Igwe
|-
| [[Head of Music]]
| Emily Baxter
|-
| [[Head of Events]]
| Surina Martin
|-
| [[News Editor|Head of The Record]]
| Maddie McCall
|-
| [[Head of Web]]
| Harris Hutchison
|-
| [[Head Technician|Head of Tech]]
| Andrew Barron
|-
| [[Hearing Aid Editors|Hearing Aid Print Editor]]
| Maia Rakovic
|-
| [[Hearing Aid Editors|Hearing Aid Online Editor]]
| Patrick Denvir
|-
| [[Head of Music|Music Events Manager]]
| Sachairi Nixon
|-
| [[Head of Marketing|Assistant Head of Marketing]]
| Kashika Malhotra
|}

Main Page

2021-07-08T08:12:58Z

Andrew: /* By year */ Add 21/22

Welcome to the Starchive Wiki.

This wiki includes a history of the station, details of the studio technology, and helpful guides for committee members.

Additionally, this wiki contains handy guides on how to upload new memories to the Starchive. As editing the Starchive is restricted to pre-approved users, these guides probably won't be too handy for most people; however, feel free to have a look if you're interested in how the Starchive works.

This wiki will be updated periodically with a whole host of new information as and when it becomes available. For more information, or if you've got memories of your own to submit, please contact the Tech Team at [mailto:archive@standrewsradio.com archive@standrewsradio.com].

----

== All About STAR ==

* [[2005/06|Formation]]
* [[Old Articles|Old articles]]
* [[Links to Musicians|Links to musicians]]
* [[Gorilla Joe]]
* [[Logos]]
* [[Studio]]
* [[Festivals]]
* [[Constitution]]
* [[Notable Shows|Notable shows]]
* [[starTV]]
* [[Unrelatable Content|Unrelatable content]]
* [[Future ideas]]

==== By year ====
* [[2005/06]]
* [[2006/07]]
* [[2007/08]]
* [[2008/09]]
* [[2009/10]]
* [[2010/11]]
* [[2011/12]]
* [[2012/13]]
* [[2013/14]]
* [[2014/15]]
* [[2015/16]]
* [[2016/17]]
* [[2017/18]]
* [[2018/19]]
* [[2019/20]]
* [[2020/21]]
* [[2021/22]]

==== By committee position ====
* [[Broadcasting Officer| Station Manager]]
* [[Deputy Station Manager| Deputy Station Manager]]
* [[Secretary| Secretary]]
* [[Treasurer| Head of Finance]]
* [[Head of Marketing| Head of Marketing]]
* [[Head of Music| Head of Music]]
* [[Head of Programming| Head of Programming]]
* [[Head of Design| Head of Design]]
* [[Head of Production| Head of Production]]
* [[Head of Events| Head of Events]]
* [[starTV| Head of Video]]
* [[News Editor| News Editor]]
* [[Head of Web| Head of Web]]
* [[Head Technician| Head Technician]]
* [[Hearing Aid Editors| Hearing Aid Editors]]

== Tech ==
* [https://www.broadcastradio.com/myriad-5-playout-support Myriad documentation]
* [http://bit.ly/radioshowguide Show guide 2019/20]
* [[Create a Jingle|Create a Jingle]]
* [[Tech Info|Station Tech Info]]
* [[Studio Equipment|Studio Equipment]]
* [[Wordpress Tips|Wordpress tips]]
* [[Stream Status]]
* [[Remote broadcast]]
** [[Broadcasting via Discord|Via Discord]]

== Programming ==
* [[Station Rules|Station Rules]]
* [[Show Agreement|Show Agreement]]

== Starchive Help ==
* [[Guide to Starchive Gallery|Managing Starchive Gallery]]
* [[How to edit the Timeline|Editing the Starchive Timeline]]
* [mailto:tech@standrewsradio.com Email the tech team]

2020/21

2021-07-08T08:11:11Z

Andrew: Events and broadcasting info

From April 2020 to March 2021, STAR did... Many things. The position of Music Events Manager was introduced as an assistant to the [[Head of Music]], and from the start the committee had to deal with the coronavirus lockdown restricting in-person events.

== Committee ==
{| class="wikitable"
|-
! Position
! Name
|-
| [[Broadcasting Officer|Station Manager]]
| Anna Rose Harris
|-
| [[Deputy Station Manager|Deputy Station Manager]]
| Jamie Rees
|-
| [[Secretary]]
| Maia Rakovic
|-
| [[Treasurer|Treasurer]]
| Hagar Manssour
|-
| [[Head of Programming]]
| Rose Kleeger
|-
| [[Head of Marketing]]
| Julia Swerdlow
|-
| [[Head of Design]]
| Lucas Capone
|-
| [[Head of Production]]
| John Kite
|-
| [[starTV|Head of starTV]]
| Calum Esler
|-
| [[Head of Music]]
| Emily Baxter
|-
| [[Head of Events]]
| Surina Martin
|-
| [[News Editor|Head of The Record]]
| Joseph Luke
|-
| [[Head of Web]]
| Harris Hutchison
|-
| [[Head of Web|Head of Development]]
| Kieran Wallbanks
|-
| [[Head Technician|Head of Tech]]
| Andrew Barron
|-
| [[Hearing Aid Editors|Hearing Aid Print Editor]]
| Laine Capshaw
|-
| [[Hearing Aid Editors|Hearing Aid Online Editor]]
| Mia Baker
|-
| [[Head of Music|Music Events Manager]]
| Sachairi Nixon
|-
| [[News Editor|Assistant Head of The Record]]
| Maddie McCall
|-
| [[starTV|Assistant Head of starTV]]
| TBC
|-
| [[Assistant Head of Programming]]
| TBC
|-
| [[Assistant Head of Tech]]
| TBC
|-
| [[Assistant Head of Marketing]]
| TBC
|}

== Website ==
Numerous changes were made to the website:
* "Quarantine" temporarily added to menu, contains [https://standrewsradio.com/quarantine-songs/ "Quarantine Songs"] and [https://standrewsradio.com/quarantine-playlists/ "Quarantine Playlists"] on hover.
** A community quarantine [https://open.spotify.com/playlist/1dEXnDvCN7mr3ciqNIzwmH?si=PE235eBoTW2sc4LcR_wZ7w playlist] was created with songs sent in from listeners.
** We asked for lockdown inspired playlists from listeners to be showcased on the STAR [https://www.instagram.com/standrewsradio/ Instagram].
* Show categories added to showcase shows that were nominated and those that won STAR awards.
* Show category added to showcase honorary lifetime members (awarded to shows that ran throughout the hosts time at the University).

== Events ==
Due to the [https://en.wikipedia.org/wiki/COVID-19_pandemic pandemic], STAR's events were held online, usually via Facebook Live.

Events included [https://www.facebook.com/93671600314/videos/1248661125511985 Q&As], [https://www.facebook.com/93671600314/videos/298671248449448 many music events], [https://www.facebook.com/93671600314/videos/156849136452437 the STAR Awards], and [https://www.youtube.com/watch?v=OKsH0jHH-YA a careers panel].

== Broadcast ==
We custom-built a solution for [[Broadcasting via Discord]] so shows could keep going from anywhere.

2020/21

2021-07-08T08:04:16Z

Andrew: /* Committee */ Update name

Head of Music

2021-07-08T08:04:02Z

Andrew: /* Assistant Head of Music */ Update name

The Head of Music is responsible for updating the database of music on Myriad, and responding to emails and letters from artists requesting airtime. They are sometimes responsible for organising gigs for student musicians, and booking acts for larger events. They should expect exact tasks relating to music events to change each week, with jobs swapping between the Head of Events and Head of Music.

In [[2009/10|2009/10]], the Head of Music organised a DJ mixtape series, ''Hear no Evil''. [https://www.facebook.com/notes/star-st-andrews-student-radio/hear-no-evil-2-falkyx/246418314477 [Source]]

In [[2010/11|2010/11]], the Head of Music created a compilation CD of artists in and around St Andrews, and an accompanying night of live music in Venue 1 (the predecessor to 601). Artists involved included [https://www.facebook.com/TheBlueswater The Blueswater] and [https://www.facebook.com/polarsets Polarsets]. Some of the artists were also invited to perform live on STAR, together with an interview. [https://www.facebook.com/notes/star-st-andrews-student-radio/star-unsigned-artists-compilation-cd-2010/387697729477 [Source]]

The Head of Music is a big role, which is sometimes not understood during applications. This has resulted in an unusually high dropout rate.

They are contactable via [mailto:music@standrewsradio.com music@standrewsradio.com].

== Previous Heads of Music ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2012/13|2012/13]]
| Kelly Provan
| Director of Music
|-
| [[2013/14|2013/14]]
| Abby Frank
| Head of On-Air Music
|-
| [[2014/15|2014/15]]
| Hector Selby
| Head of Music
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Jess Morgan
| Head of Music
|-
| [[2018/19|2018/19]]
| Hugo Jobst
| Head of Music
|-
| [[2019/20|2019/20]]
| Greer Ross-McLennan
| Head of Music
|-
| [[2020/21]]
| Emily Baxter
| Head of Music
|-
| [[2021/22]]
| Emily Baxter
| Head of Music
|}

In [[2019/20]], Jimmy (James) Fortuna was appointed as Head of Music, and Greer Ross-McLennan as Assistant Head of Music. Jimmy left the University over summer, and Greer became Head of Music.

=== Assistant Head of Music ===
Some committees may decide to appoint an assistant to the Head of Music. This was introduced in [[2019/20]] to alleviate some of the workload. Applications for this position were opened in September, to allow new students to apply. In [[2020/21]] the Music Events Manager was introduced to manage [[Links to Musicians#Sounds of Sandy's|Sounds of Sandy's]].

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2019/20|2019/20]]
| Olivia Ramo
| Assistant Head of Music
|-
| [[2020/21]]
| Sachairi Nixon
| Music Events Manager
|-
| [[2021/22]]
| Sachairi Nixon
| Music Events Manager
|}

== Handover ==
=== Intro ===
You need to be in the know when it comes to musicians in St Andrews, Fife, and Scotland, as you'll be booking them regularly. You also need to have a big library of mp3s, and a willingness to sacrifice many hours uploading mp3s to Myriad.

=== Tasks ===
* Liaise with the Head of Events to find musicians to perform at our live music events.
* Familiarise yourself with Myriad Playout, especially mass-editing songs (/carts), adding metadata to songs, AutoFade, and AutoFade's presets and schedule.
* Keep STAR's Spotify, Soundcloud, and Mixcloud profiles active.
* Update the database of music on Myriad, which is used by AutoFade. Use the AutoFade schedule to set specific genres for hours when there are no live shows (i.e. 2am-9am). You now effectively control more hours on air than anyone else!
** In Myriad Playout, go to Station -> Edit InstantTrack Assignments Grid/Presets. Ask the Head Technician for help, and to make sure your account has access to this.
* Respond to messages and emails from local musicians; be nice to them! Offer to play their songs on STAR, let them perform at a live lounge, or send them over to Hearing Aid for an interview. Any way you can think to promote their music, suggest it. You, along with your assistant, will be added to the music@ and radio@standrewsradio.com email groups. These receive musical spam from across the globe.
* Handle any music-related mail STAR receives, i.e. CDs from musicians
* Depending on the DoES this year, you might be asked to help look for a bigger act for (re)Freshers' Week.
** Make sure to ask the DoES if starTV or Hearing Aid can interview acts in Freshers' Week.
* Allocate tasks to your assistant, to split the workload.

=== Links ===
* Google Drive: [https://drive.google.com drive.google.com]
* [https://www.youtube.com/channel/UCNvE3qfLy-qXTAk3K5zxJPA/playlists Myriad Playout tutorials], especially [https://www.youtube.com/watch?v=VDbs9XPrFJk this one] and [https://www.youtube.com/watch?v=qkl61lj-gSA&list=PLdJN1nETuCqkSFyAnBOzNKnzVwyX3JK6p&index=29 this one]
* [https://www.facebook.com/groups/standrewsmusic Musicians of St Andrews] Facebook group
* [https://standrewsradio.com/music standrewsradio.com/music] STAR list of musicians – you should work with the [[Head of Web]] to update this.
* [https://open.spotify.com/user/standrewsradio open.spotify.com/user/standrewsradio]
* [https://soundcloud.com/standrewsradio soundcloud.com/standrewsradio]
* [https://www.mixcloud.com/standrewsradio mixcloud.com/standrewsradio]

=== Contacts ===

* Previous Head of Music
* Director of Events and Services (DoES): [mailto:does@st-andrews.ac.uk does@st-andrews.ac.uk]
* Whoever runs Sofar St Andrews this year – they're a useful person to befriend, as they can forward visiting musicians that don't fit with their dates/venues, or musicians who could perform for both Sofar and STAR (we found [[Links to Musicians|Mauvey]] this way).

Treasurer

2021-06-23T10:47:26Z

Andrew: /* Previous Treasurers */

The Treasurer, also known as the Head of Finance, is responsible for managing STAR's bank account, and liaising with the Students' Association cash office. In some years, they are also responsible for obtaining sponsorships, i.e. audio adverts for STAR, and sometimes printed adverts for Hearing Aid, though the [[Hearing Aid Editors|Hearing Aid Editors]] tend to do this within their sub-team.

They are contactable via [mailto:finance@standrewsradio.com finance@standrewsradio.com].

== Previous Treasurers ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2012/13|2012/13]]
| Francesca Jaconelli
| Director of Finance
|-
| [[2013/14|2013/14]]
| Gus Townsend
| Director of Finance
|-
| [[2014/15|2014/15]]
| Tierney Riordan
| Director of Finance and Sponsorship
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Flora Rowe
| Head of Finance
|-
| [[2017/18|2017/18]]
| David Kleeger
| Treasurer
|-
| [[2018/19|2018/19]]
| David Kleeger
| Head of Finance
|-
| [[2019/20]]
| Emma Stitt
| Head of Finance
|-
| [[2020/21]]
| Hagar Manssour
| Treasurer
|-
| [[2021/22]]
| Joseph Daly
| Treasurer
|}

== Handover ==
=== Intro ===
The Head of Finance is in charge of the STAR budget and spending. This role is integral for the smooth running of STAR, as you have to plan the committee’s spending for the year. You also need to find sponsorship for both STAR and Hearing Aid. You should be added as a signatory on STAR's bank account, along with the Station Manager and someone from the Cash Office.

=== Tasks ===
* Meet [mailto:jc82@st-andrews.ac.uk Jillian Cowan] with the Station Manager, for treasurer training, and to become a signatory of the STAR bank account.
* Get details of the STAR bank account from the previous Treasurer or Station Manager. You'll need the account number and sort code for people to pay money into the account, e.g. when ordering committee merch.
* Make sure you know where the cash office is, as you’ll be going there a lot.
* Plan the budget for the coming year. This should be done in liaison with every other committee member, to check their aims for the year, and how much money they will need. Your finished plan should be sent to the Union before the given deadline, usually around the end of May.
* Keep track of spending; each expenditure should be recorded in a Google Sheet, which can be shared with the whole committee.
* Create a Google Form for committee members to send you their receipts, with a description of what they bought.
* Liaise with the Cash Office and Station Manager to approve expenditure, and sign reimbursement cheques.
* We are one of the few subcommittees with a bank account. Check the balance occasionally to confirm you’re on top of everything.
* Hearing Aid prints three magazines each year. They usually have an annual budget of £1500. The Hearing Aid Editors, like other committee positions, will email you a receipts, which must be forwarded to Jillian to pay.
* If we ever need a cash box, ask to borrow one from the cash office. It’s then your responsibility!
* Remember to save some money for the incoming committee to use, before they receive the following year's budget.

=== Reimbursement Process ===
# A committee member sends you an invoice or receipt via your Google form.
# Forward to [mailto:jc82@st-andrews.ac.uk Jillian].
# Go to Jillian at the Cash Office to approve the expenditure, and fill in a slip. They’re easy to fill in; if in doubt, ask the Cash Office.
# Put the expenditure in your spreadsheet.
# After about a week, check if the committee member has been paid, or if a cheque is waiting for them to collect from the Cash Office.

The process is the same for reimbursing a show host, or ordinary student.

=== Links ===
* Google Drive: [https://drive.google.com drive.google.com]
* Google Sheets: [http://docs.google.com/spreadsheets docs.google.com/spreadsheets]
* Example budget: [https://docs.google.com/spreadsheets/d/1L8HJC6RTbewfcfyQqUDHKbgei4BI7io9mcvKuvqDs-Y/edit?usp=sharing Proposed Budget 2019/20]

=== Contacts ===
* Previous Treasurer, e.g. Emma Stitt: [mailto:emma.stitt@standrewsradio.com emma.stitt@standrewsradio.com]
* Cash Office: [mailto:unionfinance@st-andrews.ac.uk unionfinance@st-andrews.ac.uk]
* Jillian Cowan, Union Management Accountant: [mailto:jc82@st-andrews.ac.uk jc82@st-andrews.ac.uk]

=== Recurring expenses (as of 2019/20) ===
Funding from the Union has always been around £5,500 per year. The following are included in the budget each year.
{| class="wikitable"
|-
! Item
! Cost
! When
|-
| PPL license
| ~£260
| Yearly, usually January
|-
| DigitalOcean (website server)
| $27.60
| Monthly, on 1st day of each month
|-
| Hearing Aid Squarespace
| ~£200
| Yearly
|-
| Hearing Aid printing
| Up to Station Manager; max. £1500
| Yearly, split between number of issues (usually 3)
|-
| Freshers' Week merch
| Up to Station Manager
| Yearly, around August
|-
| Unexpected tech repairs
| Up to Station Manager
| Up to Station Manager
|}

Tech Info

2021-05-11T10:49:35Z

Andrew: /* Subdomains */ Remove status page

Information on this page is intended for the Tech Team.

== Email Accounts ==
* STAR's emails are managed via [https://admin.google.com/standrewsradio.com admin.google.com/standrewsradio.com]
* STAR has a G Suite legacy account (i.e. created before December 2012), allowing the creation of unlimited free accounts, each with 15GB of storage.
** We started using G Suite around May 2008 (citation needed)
* Email addresses for committee members should follow forename.surname@standrewsradio.com.
* There are also multiple groups, e.g. news@, music@, programming@, and hello@. Committee members can be added to groups to receive emails sent to the group. Emails cannot be sent from a group address.
* Both users and groups may have aliases, e.g. bo@ redirects to manager@.
* The invalid user account, *@, will catch any emails sent to non-existent addresses within our domain. This is useful for unlocking old STAR pages connected to long-departed committee members.

== Stream URLs ==
* MP3: [https://stream.standrewsradio.com/stream.mp3 stream.standrewsradio.com/stream.mp3]
* Ogg: [https://stream.standrewsradio.com/stream.ogg stream.standrewsradio.com/stream.ogg]

== Domains ==
* STAR also owns [http://standrewsradio.co.uk standrewsradio.co.uk]; it should simply redirect to the main site.
* [https://sta.radio sta.radio] is STAR's custom URL shortener, which is hosted at [https://www.heroku.com/ Heroku]. The source code for the shortener is on [https://github.com/standrewsradio/sta.radio GitHub].
* Domains are managed by Rachel Hughes, Union Design & Marketing Manager ([mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk])
* The rapid.standrewsradio.com subdomain was associated with RapidSwitch; STAR moved from RapidSwitch to DigitalOcean in 2019, so no rapid. URLs should now be in use.

== Subdomains ==
* [https://studio.standrewsradio.com studio.standrewsradio.com]: the version of the Buzzbox displayed in the studio, showing listener counter and help section.
* [https://listen.standrewsradio.com listen.standrewsradio.com]: a separate version of the Buzzbox including a stream player. Appears to have once been part of a larger legacy website.
* [https://buzzbox.standrewsradio.com/ buzzbox.standrewsradio.com]: the listen. subdomain without the STAR logo at the top.
* [https://help.standrewsradio.com/ help.standrewsradio.com]: contains the help section, which is also shown within the studio. subdomain.
* [https://stream.standrewsradio.com/ stream.standrewsradio.com]: the subdomain used for [[#Stream URLs]].
* [http://archive.standrewsradio.com/ archive.standrewsradio.com]: you are here.
* <s>[https://status.standrewsradio.com/ status.standrewsradio.com]: website status (subdomain created 5th Feb 2020)</s> Removed in May 2021 as the provider stopped supporting custom domains on their free plan.
* [https://manage.standrewsradio.com/ manage.standrewsradio.com]: .svg version of 2012 Gorilla Joe logo.
** <s>[https://manage.standrewsradio.com/grafana manage.standrewsradio.com/grafana]</s>: graph of listener stats (Grafana removed 5th Feb 2020 due to unreliability and a planned move to Google Analytics).
** [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]: global server stats, and list of mount points.
** [https://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]: extensive server stats.

== Tools ==
* [[Podcast Recorder]]: shell script that records, stores and cleans up archived podcasts.
* [https://github.com/Kezz101/ic2ga ic2ga]: Java programme that forwards Icecast statistics to Google Analytics.
* [[Stream Status]]: PHP page that checks if the stream is currently silent.

== Other links ==
STAR has team accounts on the following sites. Ask Tom, Kieran, or Ryo to add you if necessary.
* [http://analytics.google.com/ analytics.google.com]
* [https://cloud.digitalocean.com/ cloud.digitalocean.com]
* [https://github.com/StAndrewsRadio github.com]

Hearing Aid Editors

2021-04-13T09:20:08Z

Andrew: Add 2021 role holder and email address

The Hearing Aid Editors are responsible for producing STAR's printed music magazine, [[Hearing Aid|Hearing Aid]], and associated website, hearingaidmagazine.com. This is often split between a Print Editor and an Online Editor.

They are contactable via [mailto:hearingaid@standrewsradio.com hearingaid@standrewsradio.com].

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2013/14|2013/14]]
| Kelly Provan
| Hearing Aid Chief Editor
|-
|rowspan="2"| [[2014/15|2014/15]]
| Abby Frank
| Hearing Aid Print Editor
|-
| Austin Bell
| Hearing Aid Online Editor
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
|rowspan="2"| [[2017/18|2017/18]]
| Annabel McLean
| Hearing Aid Print Editor
|-
| Sarah Jack
| Hearing Aid Online Editor
|-
|rowspan="2"| [[2018/19|2018/19]]
| Lucy Bidie
| Head of Hearing Aid (Print)
|-
| Claudia Hockey
| Head of Hearing Aid (Online)
|-
|rowspan="2"| [[2019/20|2019/20]]
| Lucy Bidie
| Hearing Aid Print Editor
|-
| Evelyn Benson
| Hearing Aid Online Editor
|-
|rowspan="2"| [[2020/21]]
| Laine Capshaw
| Hearing Aid Print Editor
|-
| Mia Baker
| Hearing Aid Online Editor
|-
|rowspan="2"| [[2021/22]]
| Maia Rakovic
|-
| Patrick Denvir
|}

Head Technician

2021-04-13T09:18:46Z

Andrew: Add 2021 role holder and email address

The Head Technician, also known as the Head of Tech, is responsible for keeping the studio equipment functional and up-to-date, and buying new equipment when deemed necessary. In most years, they are also expected to keep the studio clean and tidy, and to help with tech at STAR gigs and external broadcasts. They are also responsible for managing the station's PPL license, and creating Myriad logins for shows.

The position used to be called the Director of Audio Engineering, with a focus on the studio equipment, and the rest of the committee helping to keep the studio tidy. Nowadays, it is more common for the Head Technician to be responsible for the studio computers, network, and web stream, as well as much of the website maintenance and content. They therefore work closely with the Head of Web.

For more information on studio equipment, see [[Studio Equipment]].

They are contactable via [mailto:technician@standrewsradio.com technician@standrewsradio.com], or as part of the whole tech team at [mailto:tech@standrewsradio.com tech@standrewsradio.com].

== Previous Head Technicians ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2009/10|2009/10]]
| Walker Angell
| Chief Audio Engineer
|-
| [[2012/13|2012/13]]
| James Hardy
| Director of Audio Engineering
|-
| [[2013/14|2013/14]]
| Ryo Yanagida
| Director of Audio Engineering
|-
|rowspan="2"| [[2014/15|2014/15]]
| Ryo Yanagida
| Director of Audio Engineering
|-
| Johannes Mckay
| Chief Engineer
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Jessy Staney
| Head of Tech
|-
| [[2017/18|2017/18]]
| Tom Groves
| Head of Tech
|-
| [[2018/19|2018/19]]
| Tom Groves
| Head of Tech
|-
| [[2019/20|2019/20]]
| Emily Baxter
| Head Technician
|-
| [[2020/21]]
| Andrew Barron
| Head of Tech
|-
| [[2021/22]]
| Andrew Barron
| Head of Tech
|}

=== Assistant Technician ===
Some committees may decide to appoint an assistant to the Head Technician. The responsibilities of the assistant are normally up to the Head Technician. Assistants are usually appointed in March, at the same time as the rest of the committee. However, in 2019/20 the assistants were appointed in September, to allow new students to apply.

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2012/13|2012/13]]
| Luke Hodgeman
| Director of Technical Operations
|-
| [[2018/19|2018/19]]
| Danil Flewelling
| Assistant Head of Tech
|-
| [[2019/20|2019/20]]
| Andrew Barron
| Assistant Technician
|}

== Tech Team ==
In some years, the committee may attempt to have more people helping the Head Technician, forming a Tech Team. In 2010, there was a team of people dedicated to outside broadcasts, which allowed STAR to cover far more events. [https://www.facebook.com/notes/star-st-andrews-student-radio/a-list-of-important-things-you-all-should-read-concerning-the-restart/343850429477 [Source]]

== Handover ==
=== Intro ===
As the Head Technician, you are in charge of all station equipment. This means keeping the studio fully working, thinking of new equipment we can buy to improve shows, training every show host, and then responding to their messages asking for help throughout the semester. You may also be asked to operate live sound equipment at STAR events, broadcast live events, and train people to use our external recording equipment. This role can be very rewarding, and can open a lot of doors, if you engage with it properly.

=== Tasks ===
* When you first join the committee in April, meet up with the outgoing Head Technician in the studio, and go through all equipment together. Spend as much time as possible familiarising yourself with everything in the studio, control room, and our cupboard in the TV Edit Suite (The Saint's office).
* Work with the Station Manager and Treasurer to prepare a budget for the next year. Think about what equipment we could buy, replace, or upgrade. The Treasurer has to submit a proposed budget to the Union around the end of May.
* Download broadcasting software that can handle two streamers at once (MP3 and Ogg Vorbis). This will let you take over the live broadcast from your laptop. I recommend Ladiocast for Mac.
* Download Audacity or another DAW if you haven’t already.
* Show training:
*# After show applications close in September, ask the Head of Programming to share their confirmed schedule, with show names, host names, and email addresses.
*# Set aside a weekend to train all the new shows, and create a spreadsheet with available timeslots
*# Share this spreadsheet with all shows. Post it in the shows group, and ask the Head of Programming or Secretary to send an email to all shows with a link to the spreadsheet. All new shows must be tech trained before going on air.
*# If your assistant is ready to train people, or someone else on committee is capable, try to have 30 minute slots starting every 15 minutes, with one of you in the control room and one in the main studio.
*# Work through a list of training points (example below).
*# If the Head of Programming has asked you to go through some programming tips, do this at the end of each tech training session.
* Repeat a smaller version of the training process in January (there should be fewer new shows).
* Train any new shows that appear throughout the semester.
* Create Myriad Playout accounts for each show, and make a list of the login details and cart range each account can edit. Make sure these accounts are in the "shows" permissions group. Pin the list in the shows hosts' Facebook group.
* Create Myriad Playout accounts for committee members who need specific access, e.g. the Head of Programming needs to see the login report; the Head of Music needs to be able to edit a large cart range, and access the AutoFade presets/schedule; the Head of Production needs to be able to upload adverts and jingles, and schedule them.
* Stay active in the show hosts' Facebook group; they will be relying on you to fix their tech problems all day, every day.
* Keep the studio and equipment clean and tidy.
* Make sure AutoFade is active whenever no show is on air.
* Broadcast or record live events, especially live lounges.
* Manage STAR's external recording equipment, including repairs, new equipment, loans to students, and training these students.
* Manage STAR's licenses, including submitting quarterly PPL reports.
* Work closely with the Head of Web and their assistant. Make a group chat with all of you, and the Station Manager. Your roles overlap a lot, and you should help each other with tasks wherever possible. This means you should have an active role in keeping the website up to date, and should know how to do many of the Head of Web's tasks if they are unavailable. For example, being able to delete podcasts from the [https://archive.standrewsradio.com/podcasts.html podcasts archive] if it reaches the storage limit (which could prevent listeners from accessing the main website).
* You will often be the one left to deal with tedious things, such as
* Split these tasks between yourself and your assistant.

=== Links ===
* Stats: [http://manage.standrewsradio.com/grafana manage.standrewsradio.com/grafana]
* More stats: [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]
* Mountain of stats: [http://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]
* Admin console: [https://admin.google.com admin.google.com]
* Wordpress: [https://standrewsradio.com/wp-admin standrewsradio.com]
* Archive: [http://archive.standrewsradio.com archive.standrewsradio.com]
* [http://listen.standrewsradio.com listen.], [http://buzzbox.standrewsradio.com buzzbox.], and [http://studio.standrewsradio.com studio.] subdomains
* Server: [https://www.digitalocean.com digitalocean.com]
* [https://drive.google.com drive.google.com]

=== Contacts ===
* Previous Head of Tech
* Tom Groves, Head of Tech 2017-19: [mailto:tom.groves@standrewsradio.com tom.groves@standrewsradio.com] (procrastination wizard)
* Kieran Wallbanks, Head of Web 2017-19: [mailto:kieran.wallbanks@standrewsradio.com kieran.wallbanks@standrewsradio.com] (archive wizard)
* Ryo Yanagida, Director of Audio Engineering 2013-14: [mailto:ryo.yanagida@standrewsradio.com ryo.yanagida@standrewsradio.com] (everything wizard)
* IT Services: [mailto:itservicedesk@st-andrews.ac.uk itservicedesk@st-andrews.ac.uk]
* Bruce Turner, Union Building Supervisor: [mailto:det8@st-andrews.ac.uk det8@st-andrews.ac.uk]
* Jillian Cowan, Union Management Accountant: [mailto:jc82@st-andrews.ac.uk jc82@st-andrews.ac.uk]
* Broadcast Radio (Myriad): [mailto:hello@broadcastradio.com hello@broadcastradio.com]

=== Training checklist ===
This is an example of what to work through during tech training; it should be updated as appropriate.

* Control room
** Basics of STAR
**# Internet radio, standrewsradio.com
**# Every show will have a page on the website
**# Form for show bios/fb links going out soon
** Myriad Playout
**# Carts
**# Cart players
**# Searching the database
**# Jumping between carts
**# Cart ranges
**#* Show ranges
**#* AutoFade range
**#* Sound FX range
**#* Imaging range
** Uploading songs and other audio files
** Ingest PC can't affect live broadcast

* Studio
** Mixer
**# Mic faders
**# Myriad faders
**# Faders determine what is being broadcast
**# Column for each channel
**# Trim (/gain) dials – most important for sound quality
**# Pan (/balance) dials
**# Speaker/headphone dials
** Myriad
**# Playout PC sends live broadcast
**# Standby/Live/AutoFade
**#* At the end of your show, activate AutoFade and put all four Myriad faders up
** Buzzbox
**# Help section

* Programming
** Sign-in book
** Segments
** Arrive at least five minutes early
** Script your intro
** If you’re a talk show, bring 30 mins of music to your first show; music show, bring an hour of music
** Plan your show structure and discussion points in advance
** Someone from committee will sit in on your first show

* Summary
** Retrieving podcasts, archive.standrewsradio.com
** Uploading podcasts to Mixcloud
** Passwords
** Show hosts' Facebook group
** Show guide
** Who to contact when (tech@, programming@, hello@)
** Drop-in Monday 5-6pm

* Advanced training
** Aux fader/taking phone calls
** Shortcuts
** External USB controller
** Segue editor
** Creating pads
** Using FX pads
** Pre-fade buttons
** Auto pre-fade buttons/”column”s for monitoring
** Challenge: work out what “split pre-fade” and “talkback” do

Head of Web

2021-04-13T09:17:50Z

Andrew: Add 2021 role holder and email address

The Head of Web is responsible for maintaining the website content, server, and relevant certificates. In some years, they are also responsible for developing or maintaining the STAR mobile app.

They are contactable via [mailto:web@standrewsradio.com web@standrewsradio.com], or as part of the whole tech team at [mailto:tech@standrewsradio.com tech@standrewsradio.com].

== Previous Heads of Web ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2009/10|2009/10]]
| Walker Angell
| Head of IT
|-
| [[2012/13|2012/13]]
| Matthew Dooler
| Director of Web Development
|-
| [[2013/14|2013/14]]
| Matthew Dooler
| Director of Web Development
|-
| [[2014/15|2014/15]]
| Chris O'Lenskie
| Director of Web Development
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Kieran Wallbanks
| Head of Web
|-
| [[2018/19|2018/19]]
| Kieran Wallbanks
| Head of Web
|-
| [[2019/20|2019/20]]
| Nirmal Rajesh
| Head of Web
|-
| [[2020/21]]
| Harris Hutchison
| Head of Web
|-
| [[2021/22]]
| Harris Hutchison
| Head of Web
|}

=== Assistant Head of Web ===
Some committees may decide to appoint an assistant to the Head of Web. The responsibilities of the assistant are normally decided by the Head of Web. The assistant position was introduced in 2019/20, with applications opening in September, to allow new students to apply.

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2019/20|2019/20]]
| Harris Hutchison
| Assistant Head of Web
|}

In addition to the Assistant Head of Web, some committees may also include an extra web role, to increase the expertise within the web team. They are typically more focused on the server and major updates to the website.

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2019/20|2019/20]]
| Kieran Wallbanks
| Head of Development
|-
| [[2020/21]]
| Kieran Wallbanks
| Head of Development
|}

== Handover ==
=== Intro ===
You’re now in charge of all things website (and computers).

=== Tasks ===
* When you first join committee, go through the website with the Station Manager and make a list of small features that need changing, or could be added.
* Keep the website up to date, including the interactive show schedule, the merch page, team page, and events list.
* Update Wordpress/plugins regularly.
* Embed show/committee application forms when needed.
* Regularly check that the website is functional across platforms, especially the audio stream.
* Try to improve the design and functionality of the website, Buzzbox, and studio computers.
* Actively find new features to implement on the main website and subdomains.
* Manage the STAR app.
* Work with the Head Technician to implement new features on the studio computers
* Manage the server
* Help the Station Manager to manage STAR email accounts on [https://admin.google.com admin.google.com]
* Split these tasks between yourself and your assistant.

=== Links ===
* [https://www.st-andrews.ac.uk/about/professional-services/it-services IT Services info]
* Stats: [http://manage.standrewsradio.com/grafana manage.standrewsradio.com/grafana]
* More stats: [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]
* Mountain of stats: [http://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]
* Admin console: [https://admin.google.com admin.google.com]
* Wordpress: [https://standrewsradio.com/wp-admin standrewsradio.com]
* Archive: [http://archive.standrewsradio.com archive.standrewsradio.com]
* [http://listen.standrewsradio.com listen.], [http://buzzbox.standrewsradio.com buzzbox.], and [http://studio.standrewsradio.com studio.] subdomains
* Server: [https://www.digitalocean.com digitalocean.com]
* [https://drive.google.com drive.google.com]

=== Contacts ===
* Previous Head of Web, e.g. Nirmal Rajesh ([mailto:nirmal.rajesh@standrewsradio.com nirmal.rajesh@standrewsradio.com])
* Kieran Wallbanks, Head of Web 2017-19: [mailto:kieran.wallbanks@standrewsradio.com kieran.wallbanks@standrewsradio.com] (archive wizard)
* Tom Groves, Head of Tech 2017-19: [mailto:tom.groves@standrewsradio.com tom.groves@standrewsradio.com] (procrastination wizard)
* Ryo Yanagida, Director of Audio Engineering 2013-14: [mailto:ryo.yanagida@standrewsradio.com ryo.yanagida@standrewsradio.com] (everything wizard)
* IT Services: [mailto:itservicedesk@st-andrews.ac.uk itservicedesk@st-andrews.ac.uk]

News Editor

2021-04-13T09:16:58Z

Andrew: Add 2021 role holder and email address

The Head of The Record is responsible for STAR's online news and opinions section, [[The Record|The Record]].

Their responsibilities include finding writers, organising reviews and photographs for events, editing articles, and publishing articles on STAR's website. They are also expected to write a few of their own articles.

They are contactable via [mailto:therecord@standrewsradio.com therecord@standrewsradio.com].

== Head of The Record ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2012/13|2012/13]]
| Francesca Vaghi
| News Editor in Chief
|-
| [[2013/14|2013/14]]
| Mark Gregory
| News Editor in Chief
|-
| [[2014/15|2014/15]]
| Matt Gibson
| News Director
|-
| [[2015/16|2015/16]]
| Unknown
| News Editor in Chief
|-
| [[2016/17|2016/17]]
| Natasha Franks
| Head of News
|-
| [[2017/18|2017/18]]
| Euan Elder
| Head of News
|-
| [[2018/19|2018/19]]
| Jamie Rodney
| Head of The Record
|-
| [[2019/20|2019/20]]
| Cady Crowley
| Head of The Record
|-
| [[2020/21]]
| Joseph Luke
| Head of The Record
|-
| [[2020/21]]
| Maddie McCall
| Head of The Record
|}

=== Assistant Head of The Record ===
The inclusion of an assistant varies each year. The responsibilities of the assistant are usually decided by the Head of The Record.

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2014/15|2014/15]]
| Katherine Gemmell
| Director of Press
|-
| [[2015/16|2015/16]]
| Unknown
| Director of Press
|-
| [[2017/18|2017/18]]
| Claire Fenerty
| Deputy Head of News
|-
| [[2018/19|2018/19]]
| Kaylee Kelley
| Assistant Head of The Record
|-
| [[2019/20|2019/20]]
| Shannon Fox
| Assistant Head of The Record
|-
| [[2020/21|2020/21]]
| Maddie McCall
| Assistant Head of The Record
|}

== Handover ==
=== Intro ===
The Head of The Record manages The Record, the news and opinions branch of STAR. This involves recruiting authors and illustrators, navigating Wordpress, and handling The Record's social media presence.

=== Tasks ===
* Recruit writers; give them topics to write about, if they need it. (Re)Freshers' Fayre is a good place to do this.
* Write articles yourself.
* Use Wordpress to post articles on [https://standrewsradio.com/the-record standrewsradio.com/the-record]
* Contact other committees to arrange press passes for events, for both your writers and photographers. This is important for both big and small events.
* Plan events to preview/review well in advance.
* Schedule regular writers' meetings, ideally every fortnight, to discuss columns, playlists, and event coverage.
* Respond to emails asking for coverage.
* Publicise The Record's Facebook page, and share articles on this page. If it's a particularly good article, ask the Head of Marketing to share The Record's post on STAR's Facebook page.
* Create a Messenger group for your writers and illustrators, and send regular reminders of deadlines.
* Ensure articles are at least 500 words long, with exceptions for editorial statements and interactive content.
* Make sure articles include plenty of (relevant) photos.
* Ask the Head of Web, Head of Tech, or Station Manager for help with Wordpress, especially when you first join the committee. The Head of Web should give you a restricted account, so you shouldn't have to worry about breaking the whole website.
* When posting an article on Wordpress, be sure to include the date and author's name at the top of the post.
* Split these tasks between yourself and your assistant.

=== Links and tips ===
* [https://www.facebook.com/TheRecordStA The Record] on Facebook
* [https://www.facebook.com/groups/252359109303348 The Record Writers Group] on Facebook – consider making a new group if the current one is full of ancient graduates
* [http://standrewsradio.com/wp-admin Wordpress login]
* [https://drive.google.com drive.google.com]
* [https://www.facebook.com/events Facebook events] – use this to browse for events to cover

=== Contacts ===
* Previous Head of The Record/Assistant Head of The Record

StarTV

2021-04-13T09:15:38Z

Andrew: Add 2021 role holder and email address

starTV is a [https://www.youtube.com/channel/UCnfqd8kiwFrdOP7JgW1rp8A YouTube channel], active from [[2019/20]]. It produces a variety of content about St Andrews, such as coverage of STAR's [[Links to Musicians#Sounds of Sandy's| Sounds of Sandy's]] events, climate strikes, and traditions such as May Dip. It was created in response to the collapse of [https://www.youtube.com/user/BubbleTVonline Bubble TV].

Anyone can join the starTV team and help to create videos, though much of the content is produced by the Head of Video. Hence, the general style of content is likely to depend upon the Head of Video each year.

They are contactable via [mailto:startv@standrewsradio.com startv@standrewsradio.com].

== STARadioTV ==
A decade before starTV, an attempt was made to establish "STARadioTV". The project uploaded its first video in April 2009, and its 27th and final video in February 2012. The project has both a [https://www.youtube.com/user/STARadioTV YouTube channel] and a [https://vimeo.com/standrewsradio Vimeo account]. The Vimeo account has only five videos, three of which also appear on the YouTube channel.

Videos promoting STAR appeared on Lightbox's YouTube channel throughout 2012: [https://www.youtube.com/watch?v=6hEouJU6jy8 STAR Library Ad], [https://www.youtube.com/watch?v=ttVayCt7RIQ STAR Thank You], [https://www.youtube.com/watch?v=z6zOqRKyI8M How To Paint a Monkey], and [https://www.youtube.com/watch?v=3MajwFd2G0U Sick of The Silence?]

Video marketing was also used in [[2014/15|2014/15]]: [https://vimeo.com/108119056 Get involved (Vimeo)]; [https://www.facebook.com/standrewsradio/videos/10155107930370315 STAR Open House (Facebook)].

Videos were uploaded to STAR's Facebook page sporadically from 2013-2018, but the majority of these are simply livestreams of music events, filmed with a phone.

== JSM Vlogs ==
Much of the early content on starTV was a series titled [https://www.youtube.com/playlist?list=PLkLFzUv7HEa_Iz0JolYUnILep5xWPci4b STAR Vlogs], produced by the hosts of JSM, which included Julia (Head of Marketing 2019/20). The series was inspired by vlog-style updates about [[2009/10#reSTARt| reSTARt]] published a decade earlier. JSM also has its own YouTube channel, [https://www.youtube.com/channel/UCi_dKpi2Ia9QSuovnoO1--g JSM Radio].

= Head of Video =
The Head of Video is responsible for managing starTV. This position was created, along with starTV itself, in 2019/20.

== Previous Heads of Video ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2019/20|2019/20]]
| Calum Esler
| Head of Video
|-
| [[2020/21]]
| Calum Esler
| Head of starTV
|-
| [[2021/22]]
| Eden Igwe
| Head of starTV
|}

== Handover ==
=== Intro ===
As Head of Video, you are tasked with promoting starTV to the town's population.

=== Tasks ===
* Before summer, work with the Station Manager and Treasurer to create a budget for starTV in the coming year. This is the time to plan new equipment purchases, and any props required for future videos, as much as possible.
* Create videos of local events, whether they be run by STAR, another society, or a tradition (e.g. May Dip) or one-off (e.g. protests)
* Upload videos to the starTV YouTube channel
* Work with the Head of Marketing to generate awareness of starTV, and promote finished videos
* Develop the starTV team to be an active community of videographers (camera operators, interviewers, actors, editors, animators, etc.) and ensure all are involved in content creation as much as they want to be. Where projects may lapse due to deadlines, you should try to maintain momentum as much as possible.
* Look after starTV's equipment, and manage loaning of equipment to the starTV team.

=== Links ===
* [https://drive.google.com drive.google.com]
* [https://www.youtube.com/channel/UCnfqd8kiwFrdOP7JgW1rp8A starTV YouTube channel] – check that you can access this as a brand account via your STAR email
* Emails sent to [mailto:startv@standrewsradio.com startv@standrewsradio.com] should appear in the inbox of your personal STAR address. Confirm this before telling people to email startv@.

=== Contacts ===
* Previous Head of Video, e.g. [mailto:calum.esler@standrewsradio.com Calum Esler]

Head of Events

2021-04-13T09:14:37Z

Andrew: Add 2021 role holder and email address

The Head of Events is responsible for organising show socials and committee socials throughout the year, as well as any workshops and other events. They are sometimes also responsible for organising live music events, though the [[Head of Music|Head of Music]] is normally in charge of booking the acts. They should expect the exact tasks to vary each week, with some swapping between Head of Music and Head of Events.

They are contactable via [mailto:events@standrewsradio.com events@standrewsradio.com].

== Previous Heads of Events ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2009/10|2009/10]]
| Sarah Tyler
| Head of Events
|-
| [[2013/14|2013/14]]
| Lara Johnson-Wheeler
| Director of Events
|-
| [[2014/15|2014/15]]
| Julia Drevas Bantema
| Head of Events
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Tay Davant
| Head of Events
|-
| [[2018/19|2018/19]]
| Alex Ehrenberg
| Head of Events
|-
| [[2019/20|2019/20]]
| Alex Ehrenberg
| Head of Events
|-
| [[2020/21]]
| Surina Martin
| Head of Events
|-
| [[2021/22]]
| Surina Martin
| Head of Events
|}

=== Assistant Head of Events ===
Some committees may decide to appoint an assistant to the Head of Events.
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2014/15|2014/15]]
| Bruce Kerr
| Deputy Head of Events
|-
| [[2017/18|2017/18]]
| Sofie Surraco
| Head of Fresher Events
|-
| [[2018/19|2018/19]]
| Hannah Gilchrist
| Head of Fresher Events
|}

== Handover ==
=== Intro ===
As Head of Events, you work closely with the Head of Marketing, Head of Music, Station Manager, and DoES. You need to make sure every STAR event runs smoothly, by checking which dates and times avoid clashes with other large events, booking suitable venues, making sure events are promoted effectively, arranging any items needed for an event, and dealing with any unpredictable problems.

=== Tasks ===
* Before summer, work with the Station Manager and Treasurer to plan a budget for the next year. Try to plan the year's events now (as much as possible), so you know how much money you'll need. The budget is never set in stone, so don't worry about slight changes later in the year. The Treasurer has to submit the proposed budget to the Union around the end of May.
* Check STAR's [https://www.facebook.com/pg/standrewsradio/events past events] for ideas
* Over summer and winter break, plan events for the following semester. It helps to create a planning calendar on Google Sheets, that you can share with other committee members. Aim to have dates and venues confirmed before the start of semester, wherever possible.
* Have one or two show socials each semester. Check when the Head of Programming is planning to have shows on air (or at least confirmed) before picking a date for a show social.
* Introduce yourself to the DoES, DoSDA, and Ents Convenor, as you'll be needing their help a lot throughout the year.
* Book spaces as soon as possible. As a subcommittee, we get a week to book Union spaces before societies towards the end of summer – don't miss this deadline, and always aim to book Union spaces at least three weeks in advance. If you asked for help from Ents, attend their "users meeting" at least two weeks before the event.
* Create a risk assessment for any one-off events, e.g. a bonfire, and send this to [mailto:unionra@st-andrews.ac.uk unionra@], at least two weeks before the event.
* Make sure STAR hosts live music events at least once a fortnight, with a mix of student and external musicians. The Head of Music will help to organise these, and book the musicians.
* Organise at least one committee social each semester.
* Organise workshops, e.g. jingle workshop (with the Head of Production), logo/social media workshop (with the Head of Design/Marketing), or invite a "real" radio figure to host a presenter workshop.
* Split tasks between yourself and your assistant

=== Links and tips ===
* [https://www.yourunion.net/ents/howtobookanevent Union room booking form] – note that events in Main Bar cannot be ticketed
* [https://www.yourunion.net/activities/societies/runningyoursociety/resources/riskassessments Example risk assessment]
* [https://drive.google.com/drive drive.google.com]

=== Contacts ===
* [mailto:ents@st-andrews.ac.uk Ents Crew Convenor] – make sure you're familiar with Ents Crew's policy on tech help, e.g. attending a users meeting well before your event, and always remember they are overworked student volunteers.
* Director of Events and Services (DoES): [mailto:does@st-andrews.ac.uk does@st-andrews.ac.uk] – STAR's line manager, who can offer advice on most things if the Station Manager can't. Good to contact about booking a stage/large venue.
* Director of Student Development and Activities (DoSDA): [mailto:dosda@st-andrews.ac.uk dosda@st-andrews.ac.uk] – similar to DoES, good to contact about society collabs, event ideas, and general room bookings.
* Pee (Union drinks): [mailto:sabar@st-andrews.ac.uk sabar@st-andrews.ac.uk]
* Sam (Union catering): [mailto:sacatering@st-andrews.ac.uk sacatering@st-andrews.ac.uk]
* Union reception: [mailto:union@st-andrews.ac.uk union@st-andrews.ac.uk]
* Students' Association rooms: [mailto:sarooms@st-andrews.ac.uk sarooms@st-andrews.ac.uk]
* Previous Head of Events, e.g. [mailto:alex.ehrenberg@standrewsradio.com Alex Ehrenberg]
* Bruce Turner (Union Building Supervisor): [mailto:det8@st-andrews.ac.uk det8@st-andrews.ac.uk] – for help with any big ideas; he's been part of the Union since the 1970s, so knows the feasibility of anything you could imagine.
* Phil Hulse (Union Deputy Building Supervisor): [mailto:prh@st-andrews.ac.uk prh@st-andrews.ac.uk] – for help with risk assessments.

Head of Production

2021-04-13T09:13:56Z

Andrew: Add 2021 role holder and email address

The role of Head of Production changes each year. They may be responsible for creating jingles for shows and the station, producing audio adverts for sponsors, working with show hosts to develop their content, acting as an assistant to the [[Head of Programming|Head of Programming]], or a combination of these. As such, a committee may choose to instead split this role between the [[Head Technician|Head Technician]] and the Head of Programming, if a suitable person applies for these roles. The Head of Production is also likely to be responsible for loaning of STAR's spare recording equipment.

As it is a fairly new role, the responsibilities may change in the future; for example, the Head of Production may be asked to organise an Outside Broadcast (OB) team, to create a series of podcasts, or to make sure shows are uploading podcasts properly.

They are contactable via [mailto:production@standrewsradio.com production@standrewsradio.com].

== Previous Heads of Production ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2009/10|2009/10]]
| Cam Curran
| Head of Imaging/Audio Editor
|-
| [[2019/20|2019/20]]
| Jamie Rees
| Head of Production
|-
| [[2020/21]]
| John Kite
| Head of Production
|-
| [[2021/22]]
| Brendan Head
| Head of Production
|}

== Handover ==
=== Intro ===
The Head of Production needs to regularly create short jingles for the station, and upload them to Myriad Playout. They play after every few songs on AutoFade, so people will quickly get sick of them if they aren't updated. You may also be asked to help the Head of Programming to create the schedule, monitor show attendance, and give feedback on shows.

=== Tasks ===
* Create short jingles (station idents), with a mixture between 3 and 20 seconds long
* Meet with show hosts to record jingles with them
* Meet with sponsors to create radio adverts for them
* Attempt to record jingles with visiting musicians, or ask starTV or Head Technician to do this if applicable
* Upload all jingles and adverts to Myriad Playout, and adjust settings so that
* Manage loaning of STAR's spare (external) recording equipment:
** Train users in use of the external recording equipment when necessary.
** Keep track of who is in possession of what equipment and when.
** Possibly in future: arrange contract for users of external equipment (insurance, health and safety, mentioning STAR in final products, etc.)
* Possibly in future: managing the Outside Broadcast team – setting up recordings/broadcasts and live sound at events around St Andrews. This could become a kind of "external Ents crew".

=== Links ===
* [http://bbcsfx.acropolis.org.uk BBC sound effects]
* [https://www.youtube.com/channel/UCNvE3qfLy-qXTAk3K5zxJPA/playlists Myriad Playout tutorials], especially [https://www.youtube.com/watch?v=VDbs9XPrFJk this one]

=== Contacts ===
* Previous Head of Production, e.g. [mailto:jamie.rees@standrewsradio.com Jamie Rees]

Head of Design

2021-04-13T09:13:20Z

Andrew: Add 2021 role holder and email address

The Head of Design is responsible for creating graphics and promotional material for STAR, including the Facebook page photo, cover photo, Instagram promotions, paid adverts, event posters, and station merchandise. As such, they tend to work closely with the [[Head of Marketing|Head of Marketing]].

They are contactable via [mailto:design@standrewsradio.com design@standrewsradio.com].

== Previous Heads of Design ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2012/13|2012/13]]
| Benoît Grogan-Avignon
| Creative Director
|-
| [[2013/14|2013/14]]
| Sam Moore
| Creative Director
|-
| [[2014/15|2014/15]]
| Omar Ali
| Creative Director
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Nathan Lovelace
| Head of Creative
|-
| [[2018/19|2018/19]]
| Sabine Denat
| Head of Creative
|-
| [[2019/20|2019/20]]
| Maia Rakovic
| Head of Design
|-
| [[2020/21]]
| Lucas Capone
| Head of Design
|-
| [[2021/22]]
| Matthew Colquhoun
| Head of Design
|}

=== Assistant Head of Design ===
Some committees may decide to also appoint an assistant to the Head of Design, to alleviate their workload. In 2019/20, applications for this position opened in September, allowing new students to apply.

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2014/15|2014/15]]
| Alice Lecointe
| Creative Team
|-
| [[2019/20|2019/20]]
| Roberto García
| Assistant Head of Design
|}

== Handover ==
=== Intro ===
The Head of Design is in charge of creating promotional material for the station, e.g. fliers, social media cover photos, event posters, and merchandise. You work closely with the Head of Marketing, Head of Events, and Station Manager.

=== Tasks ===
* Create material for social media and marketing
* Design merchandise
* Look for other student artists to design posters and merchandise.
* Encourage each radio show to produce its own logo, and help them in doing this.
* Update the studio decor.
* Print posters for upcoming events; put them on the studio door and around the Union.

=== Links and tips ===
* Best place to store and share designs with committee – [https://drive.google.com drive.google.com]
* Old STAR photos to use for collages etc. – [https://archive.standrewsradio.com/gallery archive.standrewsradio.com/gallery]
* If you don’t have a personal copy of Photoshop, the computers in the Union’s Design Suite do. There are also alternatives, like [https://krita.org Krita], [https://www.canva.com Canva], and [https://www.picmonkey.com PicMonkey].
* STAR yellow: #FEDE59
* STAR logo font: [https://fonts.google.com/specimen/Fugaz+One Fugaz One]
* Upload all of your logos and designs to one folder, and share the link with the Station Manager and Head of Marketing.
* Use [http://bit.ly bit.ly] to update [http://bit.ly/starlogos bit.ly/starlogos], which is available for shows to include STAR's logos on their promo material.
* Scanning artwork on University printers:
*# Place artwork face down in top-left corner of the glass
*# Hit the "email" button on the main menu
*# Hit "more options" at the bottom of the email screen
*# Set "File type" to JPG
*# Set "Resolution" to 400 dpi
*# Set "Image size" to high (large file)
*# Send email! (Click "retain settings for next job" if scanning multiple designs)
* Posters:
*# Send the poster to Rachel ([mailto:sadesignmail@st-andrews.ac.uk sadesignmail@st-andrews.ac.uk]) for approval.
*# Print the posters (there's a colour printer and a black & white printer in the Union's design suite).
*# Take the posters to Union reception to get them stamped.
*# Put the posters up around the union.
*#* Rachel (Design Office) will have a tool for opening the poster holders in the toilets
*#* Spread posters across Main Bar, Rector's, etc.
*# Ask at library and hall receptions if you can put posters up there too.

=== Contacts ===
* Previous Head of Design, e.g. [mailto:maia.rakovic@standrewsradio.com Maia Rakovic]
* Rachel Hughes, Design & Marketing Manager: [mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk]

Head of Programming

2021-04-13T09:12:15Z

Andrew: Add 2021 role holder and email address

The Head of Programming, in some years known as the Director of Programming, is responsible for show applications, the show schedule, monitoring show attendance, and sometimes helping to develop the content and quality of shows.

They are contactable via [mailto:programming@standrewsradio.com programming@standrewsradio.com].

== Previous Heads of Programming ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2009/10|2009/10]]
| Maria Mackenzie
| Head of Programming
|-
| [[2012/13|2012/13]]
| Jasper Hamlet
| Director of Programming
|-
| [[2013/14|2013/14]]
| Sean McDonald
| Director of Programming
|-
| [[2014/15|2014/15]]
| Unknown
| Unknown
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Blandine Hoge
| Head of Programming
|-
| [[2018/19|2018/19]]
| Blandine Hoge
| Head of Programming
|-
| [[2019/20|2019/20]]
| Anna Rose Harris
| Head of Programming
|-
| [[2020/21]]
| Rose Kleeger
| Head of Programming
|-
| [[2021/22]]
| Joel Butcher
| Head of Programming
|}

=== Assistant Head of Programming ===
The inclusion of an assistant varies each year. The responsibilities of the assistant are usually decided by the Head of Programming.
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2018/19|2018/19]]
| Anna Rose Harris
| Assistant Head of Programming
|-
| [[2019/20|2019/20]]
| Rose Kleeger
| Assistant Head of Programming
|}

== Handover ==
''This section is intended to help the new Head of Programming settle into the role. Adapted from 2019 handover document, written by Blandine Hoge.''

=== Intro ===
As Head of Programming, you’re in charge of choosing who gets to host a show each semester, and making sure that STAR shows are the best they can be. You will have to create application forms, arrange and run demos, build the schedule, organise first show sit-ins, organise show skimming/feedback, and track show attendance, all whilst being available to help out show hosts when they need you. It’s a difficult and time-consuming role, especially around the start of each semester, but it can be incredibly rewarding.

=== Tasks ===
==== September ====
* Show application form
** Include the following:
**# Name of show
**# Emails of all hosts
**# Show description for the website
**# Whether they are a new or returning show
**# At least five time slots they are available
**# The attendance policy and station rules
** Check previous forms as examples
** Double-check that "required answer" is active for every question
** Double-check that the form can be shared outside of standrewsradio.com, and test this with someone before sharing the form publicly

* Demos
** Demos are the second part of show applications. They're basically an informal interview to hear people describe their idea.
** All shows, including returning shows, should go through demos in semester 1. Make sure the application form mentions this.
** Have a document ready to make notes, and share this with your assistant, and anyone else helping to run demos.
** Demos are a chance for people to explain their idea to you, especially if their application was unclear – sometimes people can explain a concept much better in person than in writing.
** Ask people to prepare the following for their demo:
**# A verbal description of their show
**# An overview of what their first show would sound like
**# A preferred time slot – this may have changed since they completed the application form
** What to look for in a demo:
**# Are they keen?
**# Do they really want to be on air?
**# Do they believe in their idea?
**# Are they organised – did they arrive on time, with a clear idea, and everything you told them to prepare?

* Scheduling
** Set aside an evening to meet with your assistant and the Station Manager
** Work through applications filling every available slot on the schedule
** Remember to leave a space for the Office Hours show before committee meetings, and other committee shows if applicable (e.g. The Record's show), although they should have sent an application anyway!
** Leave a block empty for live lounges if the Station Manager requests this. They may also want a space left for one-off shows, e.g. society collabs.
** Try to avoid getting a headache

* Acceptance emails
** Send acceptances first, rejections last, incase a successful show has changed their mind, or can no longer do their allocated time
** Either you or the Station Manager should create a closed Facebook group for all show hosts to join
** Make sure every current host joins this group: include the link in acceptance emails, post it in last year's show group, and ask the Head Technician to remind everyone during training
** Include a PDF version of the show guide in acceptance emails
** Make it clear (in both acceptance and rejection emails) that every show will have to reapply in January
** Keep a list of current show hosts' emails, so you can copy and paste this whenever needed
** When sending mass emails, put the recipients in the "bcc" line, and your own email (or hello@) in the "to" line, and remember to cc the Station Manager

* Training
** Once you have sent out acceptance emails to shows, the Head Technician will organise show training. This usually takes them a whole weekend. Whether you want to join them, and give programming advice to the shows here, is up to you. This advice should include:
**# Arrive at least five minutes before your show is due to start
**# Complete the sign-in book
**# For your first show, script your introduction, and bring more music than you think you will need: one hour for music shows, half an hour for talk shows
**# Plan the structure of each show using bullet points, but don't completely script beyond the intro

* Sit-ins
** Create a copy of the schedule, with all new shows highlighted, and share this with committee@
** All committee members who have had their own shows before must sign up to help
** Every new show must have a committee member with them for their first show
** Guidelines for sit-ins:
**# Arrive early to help upload music to Myriad
**# Help with tech, e.g. turning microphones on/off
**# Give feedback afterwards, e.g. "work on improvising talk sections", "prepare more music"

* As of [[2019/20]], new shows can apply throughout the semester. It should be a similar process, just for individual shows, as soon as their application comes in. Towards the end of the semester, let any new applicants know that their application will be reviewed at the start of semester 2, since there's not much point starting a new show in revision week.

==== January ====
* Application form
** Much the same as in semester 1, but ask if returning shows want to keep the same time slot as they had last semester if possible.

* Demos
** Same as in semester 1, except returning shows are not usually required to have another demo.
** Use podcasts of returning shows to check they are of a good standard.
** Be biased towards returning shows that are actively engaged in STAR e.g. by submitting a bio for the website, having good publicity, attending events, etc.

* Sit-ins
** Same as in semester 1, i.e. only new shows require sit-ins.

==== Throughout the year ====
* Attendance
** Create a private copy of the schedule each week, and colour-code each show as i) present, ii) absent with notification, iii) absent without notification, iv) absent for two weeks in a row without notification, v) absent for three weeks in a row
** To check attendance, use a combination of:
**# Signatures in the sign-in book
**# [https://archive.standrewsradio.com/podcasts.html Podcasts]
**# Myriad login record – ask the Head Technician to show you how to access this, and to set your Myriad account up so it can access this
** It may help if you ask other committee members to send a picture of the sign-in book to [programming@standrewsradio.com programming@] whenever they go in for their show
** If you suspect a show was absent, always email the hosts; many people forget to complete the sign-in book or login to Myriad, and it's easy to mistake a music show's podcast for AutoFade
** If a show misses two weeks in a row, reach out to them.
** If a show misses three weeks in a row, with no contact, remove their show from the schedule. Update the schedule whenever this happens, and notify the Station Manager, Head Technician, and Head of Web, so they can remove the show from the website schedule, etc.

* Skimming
** You can decide whether to check every show, or only check shows that request feedback. Hopefully you listen to a lot of shows anyway, so will know which ones need improvement.
** Ask other committee members to help, and use the [https://archive.standrewsradio.com/podcasts.html podcasts archive].
** The aim of skimming is up to you and the Station Manager. You can decide to email feedback to all shows that need to improve, regardless of whether they request it.

=== Key dates ===
* Summer:
** Make the show application form
** Help the Head of Marketing promote the application forms for both shows, and assistant committee positions
* Semester 1:
** Close applications around a week after Freshers' Fayre
** Prepare the schedule and send acceptance emails in the following week
** Aim to be on air by week 3, allowing a weekend for the Tech Team to train everyone beforehand
* Christmas break:
** Help the Head of Marketing promote show applications
* Semester 2:
** Close applications around the end of Refreshers' Week
** Aim to be on air by week 2 – there shouldn't be as many new shows, so the Tech Team hopefully won't need a whole weekend to train everyone

=== Links and tips ===
* [https://docs.google.com/forms Google Forms] – learn how to change sharing access to public, and how to use "jump to section" based on previous answers
* [http://bit.ly bit.ly] – use this to create a short url for your master copy of the schedule. (The Head of Marketing may be able to redirect bit.ly/starschedule to the newest version.)
** Include show names, host names, and emails on this version of the schedule
** Send this schedule to the Head of Web and Head Technician, so they can update the website schedule and Myriad database

=== Contacts ===
* Previous Head of Programming, e.g. [mailto:blandine.hoge@standrewsradio.com Blandine Hoge]; [mailto:annarose.harris@standrewsradio.com Anna Harris]

Head of Music

2021-04-13T09:11:20Z

Andrew: Add 2021 role holder and email address

The Head of Music is responsible for updating the database of music on Myriad, and responding to emails and letters from artists requesting airtime. They are sometimes responsible for organising gigs for student musicians, and booking acts for larger events. They should expect exact tasks relating to music events to change each week, with jobs swapping between the Head of Events and Head of Music.

In [[2009/10|2009/10]], the Head of Music organised a DJ mixtape series, ''Hear no Evil''. [https://www.facebook.com/notes/star-st-andrews-student-radio/hear-no-evil-2-falkyx/246418314477 [Source]]

In [[2010/11|2010/11]], the Head of Music created a compilation CD of artists in and around St Andrews, and an accompanying night of live music in Venue 1 (the predecessor to 601). Artists involved included [https://www.facebook.com/TheBlueswater The Blueswater] and [https://www.facebook.com/polarsets Polarsets]. Some of the artists were also invited to perform live on STAR, together with an interview. [https://www.facebook.com/notes/star-st-andrews-student-radio/star-unsigned-artists-compilation-cd-2010/387697729477 [Source]]

The Head of Music is a big role, which is sometimes not understood during applications. This has resulted in an unusually high dropout rate.

They are contactable via [mailto:music@standrewsradio.com music@standrewsradio.com].

== Previous Heads of Music ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2012/13|2012/13]]
| Kelly Provan
| Director of Music
|-
| [[2013/14|2013/14]]
| Abby Frank
| Head of On-Air Music
|-
| [[2014/15|2014/15]]
| Hector Selby
| Head of Music
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Jess Morgan
| Head of Music
|-
| [[2018/19|2018/19]]
| Hugo Jobst
| Head of Music
|-
| [[2019/20|2019/20]]
| Greer Ross-McLennan
| Head of Music
|-
| [[2020/21]]
| Emily Baxter
| Head of Music
|-
| [[2021/22]]
| Emily Baxter
| Head of Music
|}

In [[2019/20]], Jimmy (James) Fortuna was appointed as Head of Music, and Greer Ross-McLennan as Assistant Head of Music. Jimmy left the University over summer, and Greer became Head of Music.

=== Assistant Head of Music ===
Some committees may decide to appoint an assistant to the Head of Music. This was introduced in [[2019/20]] to alleviate some of the workload. Applications for this position were opened in September, to allow new students to apply. In [[2020/21]] the Music Events Manager was introduced to manage [[Links to Musicians#Sounds of Sandy's|Sounds of Sandy's]].

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2019/20|2019/20]]
| Olivia Ramo
| Assistant Head of Music
|-
| [[2020/21]]
| Annaliese Nixon
| Music Events Manager
|-
| [[2021/22]]
| Annaliese Nixon
| Music Events Manager
|}

== Handover ==
=== Intro ===
You need to be in the know when it comes to musicians in St Andrews, Fife, and Scotland, as you'll be booking them regularly. You also need to have a big library of mp3s, and a willingness to sacrifice many hours uploading mp3s to Myriad.

=== Tasks ===
* Liaise with the Head of Events to find musicians to perform at our live music events.
* Familiarise yourself with Myriad Playout, especially mass-editing songs (/carts), adding metadata to songs, AutoFade, and AutoFade's presets and schedule.
* Keep STAR's Spotify, Soundcloud, and Mixcloud profiles active.
* Update the database of music on Myriad, which is used by AutoFade. Use the AutoFade schedule to set specific genres for hours when there are no live shows (i.e. 2am-9am). You now effectively control more hours on air than anyone else!
** In Myriad Playout, go to Station -> Edit InstantTrack Assignments Grid/Presets. Ask the Head Technician for help, and to make sure your account has access to this.
* Respond to messages and emails from local musicians; be nice to them! Offer to play their songs on STAR, let them perform at a live lounge, or send them over to Hearing Aid for an interview. Any way you can think to promote their music, suggest it. You, along with your assistant, will be added to the music@ and radio@standrewsradio.com email groups. These receive musical spam from across the globe.
* Handle any music-related mail STAR receives, i.e. CDs from musicians
* Depending on the DoES this year, you might be asked to help look for a bigger act for (re)Freshers' Week.
** Make sure to ask the DoES if starTV or Hearing Aid can interview acts in Freshers' Week.
* Allocate tasks to your assistant, to split the workload.

=== Links ===
* Google Drive: [https://drive.google.com drive.google.com]
* [https://www.youtube.com/channel/UCNvE3qfLy-qXTAk3K5zxJPA/playlists Myriad Playout tutorials], especially [https://www.youtube.com/watch?v=VDbs9XPrFJk this one] and [https://www.youtube.com/watch?v=qkl61lj-gSA&list=PLdJN1nETuCqkSFyAnBOzNKnzVwyX3JK6p&index=29 this one]
* [https://www.facebook.com/groups/standrewsmusic Musicians of St Andrews] Facebook group
* [https://standrewsradio.com/music standrewsradio.com/music] STAR list of musicians – you should work with the [[Head of Web]] to update this.
* [https://open.spotify.com/user/standrewsradio open.spotify.com/user/standrewsradio]
* [https://soundcloud.com/standrewsradio soundcloud.com/standrewsradio]
* [https://www.mixcloud.com/standrewsradio mixcloud.com/standrewsradio]

=== Contacts ===

* Previous Head of Music
* Director of Events and Services (DoES): [mailto:does@st-andrews.ac.uk does@st-andrews.ac.uk]
* Whoever runs Sofar St Andrews this year – they're a useful person to befriend, as they can forward visiting musicians that don't fit with their dates/venues, or musicians who could perform for both Sofar and STAR (we found [[Links to Musicians|Mauvey]] this way).

Head of Marketing

2021-04-13T09:10:32Z

Andrew: Add content@ email address

The Head of Marketing is responsible for promoting STAR to the student population, the local community, and the world. They are in charge of all of STAR's social media accounts, and regularly posting content on them.

In November 2008, the position was described as one of the "biggest and most expensive" areas of STAR.[https://www.facebook.com/notes/star-st-andrews-student-radio/want-to-join-the-star-committee/47154449477 [Source]]

They are contactable via [mailto:marketing@standrewsradio.com marketing@standrewsradio.com].

== Previous Heads of Marketing ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2009/10|2009/10]]
| Michael Curran
| Head of Marketing
|-
| [[2012/13|2012/13]]
| Samuel Bachelor
| Director of Publicity
|-
| [[2013/14|2013/14]]
| Claes Winberg
| Director of Public Relations
|-
| [[2014/15|2014/15]]
| Sam Moore
| Expansion Director
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Minoli De Silva
| Head of Publicity
|-
| [[2018/19|2018/19]]
| Minoli De Silva
| Head of Marketing and Outreach
|-
| [[2019/20|2019/20]]
| Julia Swerdlow
| Head of Marketing
|-
| [[2020/21]]
| Julia Swerdlow
| Head of Marketing
|-
| [[2021/22]]
| Grace Betteridge
| Head of Marketing
|}

=== Assistant Head of Marketing ===
Some committees may decide to appoint an assistant to the Head of Marketing. In [[2009/10|2009/10]], there were two extra positions related to marketing; the exact role descriptions are unknown, so they are listed here as assistants, for simplicity.

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
|rowspan="2"| [[2009/10|2009/10]]
| Gillian Cook
| Head of Community Relations
|-
| Dan Matthews
| Head of Advertising
|-
| [[2021/22]]
| Kashika Malhotra
| Assistant Head of Marketing
|}

== Handover ==
=== Intro ===
You are in charge of getting this town listening to STAR, going to STAR events, and generally knowing STAR exists. Good luck!

=== Tasks ===
* Decide on promotional merchandise to give out at Freshers’ Week events, working with the Station Manager and Head of Design. Decide on quantities, and order everything early in summer. Remember you can get things delivered to the Union. Examples: USB sticks, stickers, business cards, lanyards.
* Order committee merch, again early in summer. This should be pre-order only, and everyone on committee should pay for what they ordered before collecting it. Examples: jumpers.
* Order merch for assistants, once they join the committee in September.
* Order more merch throughout the year. Pre-orders are best for more expensive items. Examples: show mugs, t-shirts.
* Publicise any merch we have for sale; ensure it’s on our Union website [https://www.yourunion.net/activities/subcommittees/star subcommittee page], our [http://standrewsradio.com/merch website], and our [http://facebook.com/standrewsradio/shop Facebook page shop]. Head of Web/Tech can help with this where necessary.
* Actively reach out to University groups and societies to see if they want to collaborate, or if they want STAR to cover their events, via live broadcast, podcasts, The Record articles, starTV videos, etc.
* Reach out to groups like On the Rocks (OTR) and balls, to make sure STAR receives press passes to either review, broadcast, or film specific events. This is also a task for the Head of News, so work together!
* Organise show photos, to go on the website schedule.
* Once the Head of Programming has confirmed shows for the semester, collect short bios from each show to go with their photo on the website. Use a Google form.
* Regularly promote shows on our social media accounts.
* Talk to the University about taking over their Instagram account at some point.
* Make sure the Union is sharing our most important events on their Facebook pages, and in the weekly sabb emails.
* Make sure you publicise special shows, e.g. if a show has a well-known guest one week.
* Help shows to run competitions and giveaways.

=== Where to promote a (music) event ===
* STAR mailing list
* STAR profiles
** Twitter
** Facebook page
** Instagram post
** Instagram story
* STAR Facebook groups
** Shows group
** Musicians of St Andrews
* Other Facebook groups
** Class of 20** (last 4 years)
** [https://www.facebook.com/groups/383596922180554 st polldrews] (disguise as poll)
** [https://www.facebook.com/groups/STIMS STIMS]

* Pages that will share an event if asked:
** [http://facebook.com/yourunionevents Your Union Events]
** [https://www.facebook.com/standrewsmusic St Andrews Music (MiL)]
** [https://www.facebook.com/stimstims STIMS]
** [https://www.facebook.com/groups/pgsoc Postgraduate Society]

* Physical posters
** Studio door
** Buchanan
** Halls
** Library
** Union (must be approved by Rachel (sadesign@) and stamped by reception before putting up)
*** Rector's pinboard
*** Main bar pillars
*** Sabb office glass wall

=== Links ===

* Google Drive: [https://drive.google.com drive.google.com]
* Google Forms: [https://docs.google.com/forms docs.google.com/forms]
* Most reliable merch site: [https://www.awesomemerchandise.com awesomemerchandise.com]
* Alternative merch sites: [https://www.everythingbranded.co.uk Everything Branded]; [https://www.digitalprinting.co.uk digitalprinting.co.uk]
* USB sticks: [https://www.usbmakers.com usbmakers.com]

Social media accounts use the content@standrewsradio.com email address, which forwards to you.

=== Contacts ===
* Previous Head of Marketing, e.g. [mailto:julia.swerdlow@standrewsradio.com Julia Swerdlow]
* Rachel Hughes, Union Design & Marketing Manager: [mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk]

=== Examples of Previous Collabs ===
* FemSoc live podcast
* Protocol Magazine feature
* PhySoc aired their monthly podcasts on STAR as a pre-recorded weekly show

Head of Marketing

2021-04-13T09:08:56Z

Andrew: Add 2021 role holder and email address

The Head of Marketing is responsible for promoting STAR to the student population, the local community, and the world. They are in charge of all of STAR's social media accounts, and regularly posting content on them.

In November 2008, the position was described as one of the "biggest and most expensive" areas of STAR.[https://www.facebook.com/notes/star-st-andrews-student-radio/want-to-join-the-star-committee/47154449477 [Source]]

They are contactable via [mailto:marketing@standrewsradio.com marketing@standrewsradio.com].

== Previous Heads of Marketing ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2009/10|2009/10]]
| Michael Curran
| Head of Marketing
|-
| [[2012/13|2012/13]]
| Samuel Bachelor
| Director of Publicity
|-
| [[2013/14|2013/14]]
| Claes Winberg
| Director of Public Relations
|-
| [[2014/15|2014/15]]
| Sam Moore
| Expansion Director
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Minoli De Silva
| Head of Publicity
|-
| [[2018/19|2018/19]]
| Minoli De Silva
| Head of Marketing and Outreach
|-
| [[2019/20|2019/20]]
| Julia Swerdlow
| Head of Marketing
|-
| [[2020/21]]
| Julia Swerdlow
| Head of Marketing
|-
| [[2021/22]]
| Grace Betteridge
| Head of Marketing
|}

=== Assistant Head of Marketing ===
Some committees may decide to appoint an assistant to the Head of Marketing. In [[2009/10|2009/10]], there were two extra positions related to marketing; the exact role descriptions are unknown, so they are listed here as assistants, for simplicity.

{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
|rowspan="2"| [[2009/10|2009/10]]
| Gillian Cook
| Head of Community Relations
|-
| Dan Matthews
| Head of Advertising
|-
| [[2021/22]]
| Kashika Malhotra
| Assistant Head of Marketing
|}

== Handover ==
=== Intro ===
You are in charge of getting this town listening to STAR, going to STAR events, and generally knowing STAR exists. Good luck!

=== Tasks ===
* Decide on promotional merchandise to give out at Freshers’ Week events, working with the Station Manager and Head of Design. Decide on quantities, and order everything early in summer. Remember you can get things delivered to the Union. Examples: USB sticks, stickers, business cards, lanyards.
* Order committee merch, again early in summer. This should be pre-order only, and everyone on committee should pay for what they ordered before collecting it. Examples: jumpers.
* Order merch for assistants, once they join the committee in September.
* Order more merch throughout the year. Pre-orders are best for more expensive items. Examples: show mugs, t-shirts.
* Publicise any merch we have for sale; ensure it’s on our Union website [https://www.yourunion.net/activities/subcommittees/star subcommittee page], our [http://standrewsradio.com/merch website], and our [http://facebook.com/standrewsradio/shop Facebook page shop]. Head of Web/Tech can help with this where necessary.
* Actively reach out to University groups and societies to see if they want to collaborate, or if they want STAR to cover their events, via live broadcast, podcasts, The Record articles, starTV videos, etc.
* Reach out to groups like On the Rocks (OTR) and balls, to make sure STAR receives press passes to either review, broadcast, or film specific events. This is also a task for the Head of News, so work together!
* Organise show photos, to go on the website schedule.
* Once the Head of Programming has confirmed shows for the semester, collect short bios from each show to go with their photo on the website. Use a Google form.
* Regularly promote shows on our social media accounts.
* Talk to the University about taking over their Instagram account at some point.
* Make sure the Union is sharing our most important events on their Facebook pages, and in the weekly sabb emails.
* Make sure you publicise special shows, e.g. if a show has a well-known guest one week.
* Help shows to run competitions and giveaways.

=== Where to promote a (music) event ===
* STAR mailing list
* STAR profiles
** Twitter
** Facebook page
** Instagram post
** Instagram story
* STAR Facebook groups
** Shows group
** Musicians of St Andrews
* Other Facebook groups
** Class of 20** (last 4 years)
** [https://www.facebook.com/groups/383596922180554 st polldrews] (disguise as poll)
** [https://www.facebook.com/groups/STIMS STIMS]

* Pages that will share an event if asked:
** [http://facebook.com/yourunionevents Your Union Events]
** [https://www.facebook.com/standrewsmusic St Andrews Music (MiL)]
** [https://www.facebook.com/stimstims STIMS]
** [https://www.facebook.com/groups/pgsoc Postgraduate Society]

* Physical posters
** Studio door
** Buchanan
** Halls
** Library
** Union (must be approved by Rachel (sadesign@) and stamped by reception before putting up)
*** Rector's pinboard
*** Main bar pillars
*** Sabb office glass wall

=== Links ===

* Google Drive: [https://drive.google.com drive.google.com]
* Google Forms: [https://docs.google.com/forms docs.google.com/forms]
* Most reliable merch site: [https://www.awesomemerchandise.com awesomemerchandise.com]
* Alternative merch sites: [https://www.everythingbranded.co.uk Everything Branded]; [https://www.digitalprinting.co.uk digitalprinting.co.uk]
* USB sticks: [https://www.usbmakers.com usbmakers.com]

=== Contacts ===
* Previous Head of Marketing, e.g. [mailto:julia.swerdlow@standrewsradio.com Julia Swerdlow]
* Rachel Hughes, Union Design & Marketing Manager: [mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk]

=== Examples of Previous Collabs ===
* FemSoc live podcast
* Protocol Magazine feature
* PhySoc aired their monthly podcasts on STAR as a pre-recorded weekly show

Treasurer

2021-04-13T09:07:31Z

Andrew: Add 2021 role holder and email address

The Treasurer, also known as the Head of Finance, is responsible for managing STAR's bank account, and liaising with the Students' Association cash office. In some years, they are also responsible for obtaining sponsorships, i.e. audio adverts for STAR, and sometimes printed adverts for Hearing Aid, though the [[Hearing Aid Editors|Hearing Aid Editors]] tend to do this within their sub-team.

They are contactable via [mailto:finance@standrewsradio.com finance@standrewsradio.com].

== Previous Treasurers ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2012/13|2012/13]]
| Francesca Jaconelli
| Director of Finance
|-
| [[2013/14|2013/14]]
| Gus Townsend
| Director of Finance
|-
| [[2014/15|2014/15]]
| Tierney Riordan
| Director of Finance and Sponsorship
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Flora Rowe
| Head of Finance
|-
| [[2017/18|2017/18]]
| David Kleeger
| Treasurer
|-
| [[2018/19|2018/19]]
| David Kleeger
| Head of Finance
|-
| [[2019/20]]
| Emma Stitt
| Head of Finance
|-
| [[2020/21]]
| Hagar Manssour
| Treasurer
|-
| [[2021/22]]
| Joseph Luke
| Treasurer
|}

== Handover ==
=== Intro ===
The Head of Finance is in charge of the STAR budget and spending. This role is integral for the smooth running of STAR, as you have to plan the committee’s spending for the year. You also need to find sponsorship for both STAR and Hearing Aid. You should be added as a signatory on STAR's bank account, along with the Station Manager and someone from the Cash Office.

=== Tasks ===
* Meet [mailto:jc82@st-andrews.ac.uk Jillian Cowan] with the Station Manager, for treasurer training, and to become a signatory of the STAR bank account.
* Get details of the STAR bank account from the previous Treasurer or Station Manager. You'll need the account number and sort code for people to pay money into the account, e.g. when ordering committee merch.
* Make sure you know where the cash office is, as you’ll be going there a lot.
* Plan the budget for the coming year. This should be done in liaison with every other committee member, to check their aims for the year, and how much money they will need. Your finished plan should be sent to the Union before the given deadline, usually around the end of May.
* Keep track of spending; each expenditure should be recorded in a Google Sheet, which can be shared with the whole committee.
* Create a Google Form for committee members to send you their receipts, with a description of what they bought.
* Liaise with the Cash Office and Station Manager to approve expenditure, and sign reimbursement cheques.
* We are one of the few subcommittees with a bank account. Check the balance occasionally to confirm you’re on top of everything.
* Hearing Aid prints three magazines each year. They usually have an annual budget of £1500. The Hearing Aid Editors, like other committee positions, will email you a receipts, which must be forwarded to Jillian to pay.
* If we ever need a cash box, ask to borrow one from the cash office. It’s then your responsibility!
* Remember to save some money for the incoming committee to use, before they receive the following year's budget.

=== Reimbursement Process ===
# A committee member sends you an invoice or receipt via your Google form.
# Forward to [mailto:jc82@st-andrews.ac.uk Jillian].
# Go to Jillian at the Cash Office to approve the expenditure, and fill in a slip. They’re easy to fill in; if in doubt, ask the Cash Office.
# Put the expenditure in your spreadsheet.
# After about a week, check if the committee member has been paid, or if a cheque is waiting for them to collect from the Cash Office.

The process is the same for reimbursing a show host, or ordinary student.

=== Links ===
* Google Drive: [https://drive.google.com drive.google.com]
* Google Sheets: [http://docs.google.com/spreadsheets docs.google.com/spreadsheets]
* Example budget: [https://docs.google.com/spreadsheets/d/1L8HJC6RTbewfcfyQqUDHKbgei4BI7io9mcvKuvqDs-Y/edit?usp=sharing Proposed Budget 2019/20]

=== Contacts ===
* Previous Treasurer, e.g. Emma Stitt: [mailto:emma.stitt@standrewsradio.com emma.stitt@standrewsradio.com]
* Cash Office: [mailto:unionfinance@st-andrews.ac.uk unionfinance@st-andrews.ac.uk]
* Jillian Cowan, Union Management Accountant: [mailto:jc82@st-andrews.ac.uk jc82@st-andrews.ac.uk]

=== Recurring expenses (as of 2019/20) ===
Funding from the Union has always been around £5,500 per year. The following are included in the budget each year.
{| class="wikitable"
|-
! Item
! Cost
! When
|-
| PPL license
| ~£260
| Yearly, usually January
|-
| DigitalOcean (website server)
| $27.60
| Monthly, on 1st day of each month
|-
| Hearing Aid Squarespace
| ~£200
| Yearly
|-
| Hearing Aid printing
| Up to Station Manager; max. £1500
| Yearly, split between number of issues (usually 3)
|-
| Freshers' Week merch
| Up to Station Manager
| Yearly, around August
|-
| Unexpected tech repairs
| Up to Station Manager
| Up to Station Manager
|}

Secretary

2021-04-13T09:06:37Z

Andrew: Add 2021 role holder and email address

The Secretary, also known as the Director of Internal Communications, is responsible for taking minutes at committee meetings, and sending the weekly email to subscribers.

They are contactable via [mailto:secretary@standrewsradio.com secretary@standrewsradio.com].

== Past Secretaries ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2013/14|2013/14]]
| Rachael Leach
| Director of Internal Communications
|-
| [[2014/15|2014/15]]
| Camille Hamilton-Villemur
| Director of Internal Communications
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Florence Langford
| Director of Internal Communications
|-
| [[2017/18|2017/18]]
| Laura Mueller
| Director of Internal Communications
|-
| [[2018/19|2018/19]]
| Bear Hutchison
| Head of Internal Communications
|-
| [[2019/20|2019/20]]
| Jordan McKay
| Secretary
|-
| [[2020/21]]
| Maia Rakovic
| Secretary
|-
| [[2021/22]]
| Lynn Nguyen
| Secretary
|}

== Handover ==
=== Intro ===
Within the role of Secretary you will be responsible for writing minutes at committee meetings, and creating the weekly emails which will be sent out to everyone on the mailing list.

=== Tasks ===
* After writing minutes for a meeting, you must send them to [mailto:cem4@st-andrews.ac.uk Christine McCue] as a PDF or Word document. It's also good to send the minutes to [mailto:committee@standrewsradio.com committee@].
* Be creative with the weekly email. Check if the Station Manager and other committee members have anything to include on the email, e.g. events, tech updates.
** Use Mailchimp to check the layout of previous emails. Last year, the layout consisted of: welcome message, events, anything else important, merch sales, office hours, and song of the week, but you can include any extra segment you like.
** Make sure that Mailchimp sends the newsletter from newsletter@standrewsradio.com. Outlook acts strangely around some email security policies which STAR has, and so there's a special exemption in the University's spam filter to let our newsletter come through. Replies to that email address will still come through to your STAR email.

=== Links ===
* [https://mailchimp.com mailchimp.com]
** Take some time to work through the settings, and get familiar with the user interface. You'll need to change your account details, and things like the "from" address on new email templates.

=== Contacts ===
* Previous Secretary
* Christine McCue, Union Receptionist: [mailto:cem4@st-andrews.ac.uk cem4@st-andrews.ac.uk]

Deputy Station Manager

2021-04-13T09:02:53Z

Andrew: Add 2021 role holder and email address

The Deputy Station Manager, also known as the Deputy Broadcasting Officer, is second in charge of STAR. Their exact responsibilities change significantly each year, and can include acting as a social rep for the committee, liaising between STAR and Hearing Aid, or taking on some of the [[Broadcasting Officer|Station Manager's]] tasks. The Deputy Station Manager chairs meetings whenever the Station Manager is unable to attend.

They are contactable via [mailto:deputy@standrewsradio.com deputy@standrewsradio.com].

== Past Deputy Station Managers ==
{| class="wikitable"
|-
! Year
! Name
! Position Title
|-
| [[2012/13|2012/13]]
| Oscar Swedrup
| Deputy Broadcasting Officer
|-
| [[2013/14|2013/14]]
| Jasper Hamlet
| Deputy Station Manager
|-
| [[2014/15|2014/15]]
| Rachael Leach
| Deputy Station Manager
|-
| [[2015/16|2015/16]]
| Unknown
| Unknown
|-
| [[2016/17|2016/17]]
| Unknown
| Unknown
|-
| [[2017/18|2017/18]]
| Sabine Denat
| Deputy Broadcasting Officer
|-
| [[2018/19|2018/19]]
| Euan Elder
| Deputy Broadcasting Officer
|-
| [[2019/20|2019/20]]
| Blandine Hoge
| Deputy Station Manager
|-
| [[2020/21]]
| Jamie Rees
| Deputy Station Manager
|-
| [[2021/22]]
| Rose Kleeger
| Deputy Station Manager
|}

== Handover ==
=== Intro ===
As Deputy Station Manager you will be expected to assist the Station Manager in any way possible. You will be a second voice in all decisions, and a second pair of hands for all tasks. This could mean helping to chair meetings, organising events, or researching new ideas. This is a great role if you want to see, and influence, how every part of STAR works.

The Deputy Station Manager has usually been on committee for a year, and should therefore have a good understanding of how STAR is run, and which areas need the most help. This role assists everyone on committee, but also initiates new ideas.

=== Tasks ===
Tasks are likely to change each year, but will be roughly as follows:

* Assist the Station Manager wherever possible, and represent STAR whenever the Station Manager is unable to.
* Act as a main point of contact between Hearing Aid and STAR.
* Ensure that all members of the committee are given a fair and reasonable workload, that does not hinder their university studies.
* Actively attempt to secure nominations for various student radio awards.
* Host the “Office Hour” show at 5pm on Mondays.
* Help as much as possible with Freshers’ Fayre, Refreshers’ Fayre, show demos, and first show sit-ins.

=== Links ===
* [https://drive.google.com drive.google.com]

=== Contacts ===
* Previous Deputy Station Managers, e.g. [mailto:blandine.hoge@standrewsradio.com Blandine Hoge].

Broadcasting Officer

2021-04-13T09:01:54Z

Andrew: Add 2021 role holder and email address

The SSC Broadcasting Officer (BO), also known as the Station Manager, is in charge of STAR. They are elected in the student elections of March each year, and sit on the Student Services Council (SSC) of the University of St Andrews Students' Association.

They are contactable via [mailto:manager@standrewsradio.com manager@standrewsradio.com].

== Past Broadcasting Officers ==
{| class="wikitable"
|-
! Year
! Name
|-
|rowspan="2"| 2005
|Sandy Walker
|-
| Steve Pidcock
|-
| [[2005/06]]
| David Wilkinson
|-
| [[2006/07]]
| David Wilkinson
|-
| [[2007/08]]
| Unknown
|-
| [[2008/09]]
| Unknown
|-
| [[2009/10]]
| Phil Torts
|-
| [[2010/11]]
| Unknown
|-
| [[2011/12]]
| Tristan van Deventer
|-
| [[2012/13]]
| Kate Reid
|-
| [[2013/14]]
| Oscar Swedrup
|-
| [[2014/15]]
| Sean McDonald
|-
| [[2015/16]]
| Bruce Kerr
|-
| [[2016/17]]
| Charlotte Flatley
|-
| [[2017/18]]
| Flora Rowe
|-
| [[2018/19]]
| Laura Mueller
|-
| [[2019/20]]
| Tom Groves
|-
| [[2020/21]]
| Anna Rose Harris
|-
| [[2021/22]]
| Julia Swerdlow
|}

== Handover ==
''This section is intended to help new Station Managers settle into the role.''
''Adapted from 2018 handover document, written by Flora Rowe.''

=== Intro ===

Firstly, congratulations! Welcome to one of the most stressful, time-consuming, rewarding, exciting, and unpredictable adventures of your university career. You are the new SSC Broadcasting Officer, more commonly known as the Station Manager of STAR: St Andrews Radio. As head of the Broadcasting Society, you are tasked with running STAR, starTV, The Record, and Hearing Aid.

This position requires a lot of dedication and multitasking. To put it simply, you are now a manager: your job is to manage people, and make sure they do the tasks you assign them. Whereas many people on your committee will be responsible for one aspect within STAR, you are required to pay close attention to each element, in order to ensure that everyone on your committee is working hard.

For instance, you must work closely with the events team to make sure STAR is putting on plenty of events each semester. You must work with your Head of Design and Head of Marketing to ensure a constant STAR presence throughout the student body and in different buildings throughout the university. You must work with the Hearing Aid Editors to ensure the magazine doesn’t go over budget. You must work with the Head of News to try and get more writers, have regularly published articles, etc.

As a result, communication between committee members is essential. You need to ensure that your team members constantly keep you updated on what they’re doing. If people do not tell you what they are doing or how projects are progressing, you may start to think they aren’t doing any work whatsoever. Communication is particularly important during deadline season; you don’t want to have constantly hassle committee members about tasks when they haven’t even had time to start brainstorming. It’s important to show your committee that you understand they probably have a lot of commitments throughout the academic year, and that it’s difficult to juggle everything at once. However, they are pivotal members of a subcommittee whose main purpose is to provide a unique extracurricular activity for students, and this cannot be achieved without their hard work.

Some of your other main responsibilities are to chair committee meetings, create a budget, and provide all matriculated students with the opportunity to learn more about radio. The committee's momentum and progress will be proportional to your own motivation.

=== First Tasks ===
When you first get voted in, you will be overwhelmed. Hit the ground running, be proactive, and everything will be fine; I promise.

# Read the [[Constitution|constitution]]
#* This should be chapter 24 of the "Laws" document available [https://www.yourunion.net/union/policiesandprocedures/constitutionandlaws here], though this source is slow to update changes.
#* This should explain many of the Union's complicated rules. 
# Search for your committee
#* As soon as you are voted in, you will need to start looking for your committee.
#* The constitution should have a list of positions, and rules about the interview process.
#* Most importantly, the application form should be advertised for at least two weeks, and the following people should be present at interviews: incoming Station Manager, outgoing Station Manager, and one of incoming/outgoing DoES.
#* Try to leave applications for assistant positions until September
#* Make a Google form with questions such as "what experience do you have", "why do you want to be a part of STAR", etc. Ask the previous Station Manager to share previous forms as examples.
#* In the form, use "jump to section" to show questions based on answers. Then you can have a section to ask the Head of Design/Video/Production for examples of their past work, or ask the Head of Music to make a playlist, etc.
#* Ask the Union to help share the form on their social media, and in the sabbs' weekly email. 
# Committee interviews
#* After you have applications in, organise interview times. I would recommend 10 minutes per person, and tell them when to be there (rather than a sign-up system).
#* The incoming Station Manager, outgoing Station Manager, and one of the incoming/outgoing DoES or DoSDA must be present at interviews, to ensure they are democratic and fair.
#* Choose your committee! Send successful emails first, incase someone turns down the offer. Send rejection emails once all positions are confirmed.
#* People often apply for position X when they're clearly more suited to position Y; don't be afraid to talk to them about this! 
# Committee handovers
#* Organise a meet-up between new and old committee members. This could be as part of a group meeting, or just in pairs. 
# Have your first committee meeting
#* Establish what each committee member aims to achieve in the coming year.
#* Let everyone know your own priorities from your manifesto, and what you aim to achieve.
#* Start discussing the budget for next year. 
# Organise the STAR Awards
#* Book a venue, advertise, release nominations, find prizes, advertise more, and have fun. 
# Spend a committee meeting getting ready for summer. What do you want to be done before September? 
# Organise committee photos.
#* Post a group picture.
#* Save individual photos for promoting show applications in September. 
# Check everyone has access to everything they need
#* See detailed table below ("Account Access").
#* Head of Web and Head Technician can help with this, especially making STAR email addresses for everyone. 
# Update the committee on the website [http://standrewsradio.com/team team page].
#* Ask everyone to write a short blurb.
#* Head of Web can update the page for you. 
# Over summer, organise the budget.
#* Based on what your committee has planned for the upcoming year, get the Head of Finance to create a spreadsheet.
#* Ask outgoing Station Manager to share previous budgets as examples. The total amount of funding from the Union is unlikely to change much.
#* Make sure you send the budget to the sabbs before their deadline, usually around the end of May.
#* Ask the Head of Finance to set up an expenditure spreadsheet, to make sure you stick to the budget throughout the year. 
# Apply for a Freshers' Fayre table, and get merchandise ready
#* Merchandise can take a long time to design and produce, so make sure you start this well before September.
#* [https://www.awesomemerchandise.com Awesome Merchandise] and [https://www.usbmakers.com usbmakers.com] are great places to look. 
# Plan events for September
#* Usual examples: give-it-a-go, drinks night.
#* Book spaces before deadlines (subcommittees should get priority over societies!)
#* Request free drinks, etc. well in advance.
#* The DoES and DoSDA are the ones to ask about booking spaces, and event planning in general. 
# Book a room for committee meetings next year
#* We usually go for the "Committee Meeting Room", 6-7pm Mondays, from September to May.
#* Make sure you do this before the '''subcommittee''' deadline, as we should get an extra week before societies can book rooms. 
# Info Night
#* Organise for the Monday of week 1 (the day after Freshers' Fayre)
#* Book a space (e.g. Sandy's)
#* Make a presentation. Include how to get involved with The Record, Hearing Aid, starTV, Outside Broadcast team, event photography, and poster design. Focus on how to apply for a radio show, what hosting a show involves, and the structure of a typical show. 
# After Freshers' Week
#* The programming team will need a lot of help with show applications and demos. Together with Tech Training, this will be the main focus for the first couple of weeks.
#* Get into a routine! Make sure design/marketing/tech/events/music teams are communicating seamlessly about events, and the programming team is checking show attendance.

=== What is Councils? ===
This is probably wrong, but it's the best I've come up with in four years.

* The Broadcasting Officer sits on the Student Services Council (SSC), along with people like the Mermaids President and Union Debating Society President.
* There's also the Student Representative Council (SRC), with people like the Member for First Years and Member for Racial Equality.
* Above SSC and SRC is the "Association" – people like the Alumni Officer and LGBT+ Officer.
* Above the Association is the sabbatical officers (sabbs) – people like the Director of Events and Services (DoES) and the Association President (Big Pres).
* The SSC, SRC, Association, and sabbs together form "Joint Councils".
* Everyone on Joint Councils is elected in March (apart from the Ents, Design Team, and Arts Festival Convenors).
* The Broadcasting Officer has to go to meetings for SSC and Joint Councils. This will take up most of your Tuesday evenings.
* More info on Councils positions [https://www.yourunion.net/voice/elections/positions here].

=== What is the Union? ===
The Union is the building and its staff (bartenders, cleaners, porters, receptionists, etc.) and exists to provide services like meeting rooms and pablos.

The Students' Association is all of the elected students ("Councils"), and works to improve the experience of all students at the University of St Andrews. It is a [https://www.oscr.org.uk/about-charities/search-the-register/charity-details?number=19883 registered charity] in Scotland, and works to represent the views of St Andrews students to the University and beyond. It is based within the Union building.

The University is a separate body (and another registered charity), but works closely with the Union. The Union receives most of its income from pablos, and the University. As a ''subcommittee'' of the Union, STAR receives its funding from the Union, and can book spaces within the Union for free. ''Societies'' can also do this, but receive most of their funding from membership fees. All St Andrews students are automatically members of all subcommittees.

=== An average week as Broadcasting Officer ===
It’s difficult to describe what an average week is like as Broadcasting Officer. Even if you’re not working on a specific STAR-related task, you’ll probably find yourself constantly thinking about STAR. This is pretty common, especially at the start of your term, as it can be quite difficult trying to balance coursework with your SSC responsibilities.

Councils: most weeks you will have either an SSC or Joint Councils meeting, a weekly STAR committee meeting, check-ins with the DoES about potential STAR events, going to see Jillian Cowan (Management Accountant) in the Cash Office to sign invoices, and a meeting with the Deputy Station Manager to discuss how STAR is doing and future plans for the Broadcasting Society.

Committee: I would recommend making meetings compulsory for the most important positions, and optional (but encouraged) for assistants. It may also help to send an agenda to committee@ the day before each meeting, incase anyone wants to add anything. Having a task sheet is also helpful, as everyone can see what they need to be working on before the next meeting. Update this task sheet after each meeting, and check on everyone's progress a few days before the next meeting.

Social media: you will receive hundreds of emails and Facebook messages. Generally they are small queries or musicians asking random questions, but keep on top of these or they will quickly build up. Having a Music Team to deal with spam sent to music@ helps. It can also help to assign messages to STAR's Facebook page to the Head of Programming/Events/Tech/Music where relevant. If someone gets in touch about an event idea, society collaboration, performing at a STAR event, or query about hosting a show, try to always be positive, reply promptly, and in detail.

=== What to expect from Councils meetings ===
The week before an SSC or Joint Councils meeting, the Association Chair will request a report from you. This report should summarise what your committee has been doing, and what is being planned for the next few weeks. The Chair will then send out an agenda two days before the meeting, containing everyone's reports. You can reply with amendments if necessary. If you do not submit a report in time, it counts as half an absence. Whilst this might not seem like much, it can quickly add up, to the point where you could potentially be removed from your position.

Meetings begin with the Association Chair proposing to adopt the meeting’s agenda; at this time, you can propose to amend the agenda – either a change the order in which things are debated or discussed, or even to add something to the General Business section of the agenda. The Chair then passes the adoption of the agenda, as well as the minutes from the previous meeting, assuming there are no objections.

All Councils meetings are open to the entire student body, and students can raise any issues or concerns during the Open Forum section of the agenda. It's not uncommon to have a large group of students sit in the meeting for this section and give short speeches, if an important motion is being discussed.

Following this, the Sabbatical Officers give their reports, and then all elected officers are given the opportunity to add to their previously submitted reports, and answer questions.

After General Business, the meetings usually end with Collaborative Solutions. At this time, any non-councillors (including student journalists) must leave the meeting. Collaborative Solutions provides officers with the chance to tackle issues together, and get advice from the other subcommittee heads. Issues that have been raised during Collaborative Solutions include: how to get your committee members to be more passionate about different projects, the best ways to publicise an important event to the student body, how to deal with conflict either within your committee or with other matriculated students, and how to successfully collaborate with other student societies.

Another member of Councils may ask you to second their motion. If so, read through their motion, and suggest adjustments/corrections. If you agree with their idea, tell them to list you as a seconder. Past examples of motions are [https://www.yourunion.net/activities/ssc/sscpolicies here]. You can submit your own motion, e.g. to update the Broadcasting Society's constitution, following the format of these examples. You will need two people on Councils to second your motion before it is accepted onto the agenda.

As part of the SSC you can run to be SSC Senior Officer, SSC Secondary Nominee to SAEC, SSC Tertiary Nominee to SAEC, a member of the Association Discipline Committee, and a member of the Societies Committee. Towards the end of your term, you can also run to be on the Elections Committee. These are all great opportunities to get more involved with the Union. If you have any questions, the best person to ask is the Association Chair, or a current sabb (see Useful contacts section).

Finally, if you want to make any changes to STAR, the Union, or even the whole town, this is the time to do it. Again, email the SA chair and they will be able to help you write a paper to get any changes made!

=== Useful contacts ===
{| class="wikitable"
|-
! Name
! Position
! Contact info
! When to contact
|-
| (Changes yearly)
| DoES
| [mailto:does@st-andrews.ac.uk does@st-andrews.ac.uk]
| Events, committee issues, or general advice about your position. (Also your line manager!)
|-
| (Changes yearly)
| DoSDA
| [mailto:dosda@st-andrews.ac.uk dosda@st-andrews.ac.uk]
| Booking spaces in the Union, or general advice about your position
|-
| Jillian Cowan
| Management Accountant
| [mailto:jc82@st-andrews.ac.uk jc82@st-andrews.ac.uk]
| Budget, cash, money, wonga
|-
| Bruce Turner
| Building Supervisor
| [mailto:det8@st-andrews.ac.uk det8@st-andrews.ac.uk]
| Changes to studio (e.g. new plug socket), knowledge of everything Union, giver of nicknames
|-
| Chris/Christine/Kyle
| Union Receptionists
| [mailto:union@st-andrews.ac.uk union@st-andrews.ac.uk]
| Room bookings, parcels, gossip
|-
| (Changes yearly)
| Association Chair
| [mailto:sachair@st-andrews.ac.uk sachair@st-andrews.ac.uk]
| Councils, help writing a motion
|-
| (Changes yearly)
| Previous Broadcasting Officer
| Flora Rowe, Laura Mueller, [mailto:tom.groves@standrewsradio.com Tom Groves]
| Everything
|-
| Ryo Yanagida
| God of STAR
| [mailto:ryo.yanagida@standrewsradio.com ryo.yanagida@standrewsradio.com]
| You survived the apocalypse. Everything is destroyed, including STAR's server. Only Ryo can save us now.
|}

=== Further advice ===
# Read the constitution at the start of your term, to see if there are any amendments you could make to improve how STAR is run. This includes updating the constitution with all committee positions you intend to have. 
# When choosing your committee members, don't let other people influence your decision. The DoES and outgoing Station Manager sit in on the interviews, and will naturally form their own opinions about each candidate. They are meant to act as resources, and can help you talk through the pros and cons of certain choices. The outgoing Station Manager will know which reapplying committee members have worked hard, but in the end, it's important that you feel confident about your newly-elected committee. 
# It might be tempting to give committee positions to your friends, but it's important to give people a position on the STAR committee based on their own merit, and how passionate they are about the job. 
# When choosing a committee, take their previous involvement with STAR into consideration. Do they go to every event? Have they hosted two shows for the last year? Or have they appeared out of nowhere, claiming to listen to lots of shows? 
# It can be difficult to become friends with committee members if you only see them once a week during committee meetings. You can’t force friendship, especially if you’re constantly assigning people arduous tasks, but it’s important to make sure your committee members know you value their hard work. 
# Sadly, there isn’t always enough time in the academic year to fulfil every promise made in your manifesto, but don’t get discouraged! Try to focus your attention on projects you feel can be achieved and will directly benefit the student experience. 
# You will inevitably hit a point in the semester when your committee loses momentum. Firstly, send out a quick questionnaire with questions like "how could meetings be improved", "how could the committee be more enjoyable", and "what do you think is STAR’s biggest weakness". Then organise quick meetings with the Deputy Station Manager and each committee member separately; this gives the committee a chance to chat properly with you about any concerns or stresses. 
# If you are unfortunate and have a committee member who is lacking in commitment, misses meetings, or isn’t doing their job, you may need to reconsider their position. Firstly, don’t jump to any conclusions; they might be having a hard time at home, struggling with their studies, have family issues, or in an argument with their best friend, so don’t presume anything. Secondly, organise a one-to-one meeting with them, and give them the opportunity to explain why they aren’t 110%. They might then opt out of committee, but equally this may kick start them. 
# Whenever you have issues, talk to the DoES. They're there to help you, and will have been through this with another subcommittee for sure! 
# Have fun! This is your opportunity to be freakishly involved with any and all aspects of STAR. Take advantage of the fact that you can bring about real change and improve the student experience. Don't be afraid to test something new, and accept that you will run into a lot of challenges. 
# Don't have too much fun! You have a degree to finish. 
# Try to avoid deleting any old stuff, and make sure your committee is in the same mindset. This goes for things like old STAR Facebook posts which no longer link to a valid page, old show pages on the website, and old articles on The Record. They might seem insignificant, but having all of these minor parts together really helps to build a sense of progress and history. It also helps when working on the archive!

=== Account Access ===
It is the Station Manager's responsibility to ensure everyone on committee is able to do their tasks. This means checking people have access to the right accounts, with suggested access as below. The most important site for the Station Manager is [https://admin.google.com admin.google.com]. From here, you can control login information for all STAR email addresses and accounts. You can also access accounts such as invaliduser@, which catches all emails sent to addresses that don't exist (such as very old committee members).

'''It is essential that you check the necessary people have access to the correct accounts for the committee to function smoothly.'''

{| class="wikitable"
|-
! Account
! Positions with access
|-
| [http://standrewsradio.com standrewsradio.com] Wordpress (Administrator)
| Station Manager, Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| [http://standrewsradio.com standrewsradio.com] Wordpress (Editor)
| Station Manager, Head of News (+ Assistant)
|-
| [https://admin.google.com admin.google.com] Admin
| Station Manager, Head of Web, Head Technician
|-
| Personal @standrewsradio.com email account
| All current committee; members of starTV and Tech Team if appropriate
|-
| [https://admin.google.com admin.google.com] hello@ group
| Station Manager, Deputy Station Manager
|-
| [https://admin.google.com admin.google.com] committee@ group
| All current committee
|-
| [https://admin.google.com admin.google.com] other groups
| Should be obvious, e.g. music team for music@; make sure all group memberships are up to date. Station Manager should be in every group.
|-
| All STAR social media (Admin)
| Head of Marketing, Station Manager, Deputy Station Manager
|-
| [https://www.facebook.com/standrewsradio STAR Facebook page] (messaging)
| Head of Programming, Head of Events, Head of Music, Head Technician
|-
| STAR music social media (Admin), e.g. [https://open.spotify.com/user/standrewsradio Spotify], [https://soundcloud.com/standrewsradio Soundcloud], [https://www.mixcloud.com/standrewsradio Mixcloud]
| Head of Music, Head of Marketing, Station Manager
|-
| STAR show hosts' Facebook group (Moderator)
| Most of committee
|-
| Server ([https://cloud.digitalocean.com cloud.digitalocean.com])
| Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| [http://analytics.google.com Google Analytics]
| Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| SSH server (username[https://garfield.standrewsradio.com @garfield.standrewsradio.com])
| Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| [http://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]
| Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]
| Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| Streaming encoders (e.g. [https://apps.apple.com/gb/app/ladiocast/id411213048?mt=12 Ladiocast]) (.ogg and .mp3)
| Head Technician (+ Assistant), Outside Broadcast Team
|-
| Code store ([https://github.com/StAndrewsRadio GitHub])
| Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| All The Record social media (Admin)
| Head of News (+ Assistant), Station Manager
|-
| [http://www.hearingaidmagazine.com hearingaidmagazine.com] Squarespace (Admin)
| Hearing Aid Editors, Head of Web
|-
| All Hearing Aid social media: [https://twitter.com/hearingaidmag_ Twitter], [http://instagram.com/hearingaidmagazine Instagram], [https://www.facebook.com/HearingAidMagazine Facebook], [https://www.yumpu.com/user/hearingaidmagazine Yumpu (1)], [https://www.yumpu.com/user/standrewsradio Yumpu (2)], [https://issuu.com/standrewsradio Issuu (1)], [https://issuu.com/hearingaid-standrews Issuu (2)] – try to combine to only Yumpu (1)?
| Hearing Aid Editors, Station Manager
|-
| STAR bank account
| Station Manager, Head of Finance, and someone from the Cash Office
|-
| [https://mailchimp.com mailchimp.com]
| Secretary, Station Manager
|-
| Myriad Playout (Administrator)
| Head Technician (+ Assistant), Head of Web (+ Assistant)
|-
| Myriad Playout (extended cart range, and access to AutoFade/scheduling settings)
| Head of Music (+ Assistant), Head of Production
|-
| Myriad Playout (access to log reports)
| Head of Programming
|-
| Myriad Playout (standard cart range)
| Every show
|-
| [https://www.youtube.com/channel/UCnfqd8kiwFrdOP7JgW1rp8A starTV YouTube] (Owner or Manager)
| Head of Video, Station Manager
|-
| [https://www.youtube.com/channel/UCnfqd8kiwFrdOP7JgW1rp8A starTV YouTube] (Communications manager)
| Head of Marketing
|-
| [http://archive.standrewsradio.com archive.standrewsradio.com] Gallery (Admin)
| Station Manager, Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| [http://archive.standrewsradio.com archive.standrewsradio.com] Wiki (Admin)
| Station Manager, Head of Web (+ Assistant), Head Technician (+ Assistant)
|-
| PPL [https://customerportal.ppluk.com/OA_HTML/xxrlWrpCAcdLogin.jsp webcasting report] account
| Head Technician
|-
| [https://www.linkedin.com/company/standrewsradio LinkedIn]
| Head of Marketing, Station Manager
|}

* All account access for Ryo Yanagida, Tom Groves, and Angus Ireland should kept as is, incase of future forgotten passwords/bad handovers.
* Head of Web can help to set up personal email addresses and manage admin.google.com groups if needed
* Head Technician should manage Myriad Playout accounts
* Check with people on past committee before removing their @standrewsradio.com email; when deleting, tick "transfer data to another account"
* Ask previous Station Manager or Head of Marketing for access to STAR social media accounts
* Ask Ryo for access to server (SSH)
* Ask Tom if any of this is confusing

Broadcasting via Discord

2021-02-12T14:20:44Z

Andrew: /* Controlling Music */

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://sta.radio/discord '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show'''.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

If you need to end a song mid-way through, use <code>_forceskip</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause the music player.
* <code>_resume</code>: Resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, ask them to join the Discord server using the link [https://sta.radio/discord https://sta.radio/discord]. Your guests don't need to go through the <code>!verify</code> process - just ask them to let you know their Discord username.

During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code> to give them access to the studio.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host on your show, ask them to join the Discord server using the link [https://sta.radio/discord https://sta.radio/discord].

You can then use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>. You can send this command into <code>#registration</code> at any time.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2021-02-12T14:19:47Z

Andrew: /* Going Live */ Restructure to discourage cutting off music

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://sta.radio/discord '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show'''.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

If you need to end a song mid-way through, use <code>_forceskip</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, ask them to join the Discord server using the link [https://sta.radio/discord https://sta.radio/discord]. Your guests don't need to go through the <code>!verify</code> process - just ask them to let you know their Discord username.

During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code> to give them access to the studio.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host on your show, ask them to join the Discord server using the link [https://sta.radio/discord https://sta.radio/discord].

You can then use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>. You can send this command into <code>#registration</code> at any time.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2021-02-02T16:29:37Z

Andrew: Clarification about how to add new co-hosts

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://sta.radio/discord '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, ask them to join the Discord server using the link [https://sta.radio/discord https://sta.radio/discord]. Your guests don't need to go through the <code>!verify</code> process - just ask them to let you know their Discord username.

During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code> to give them access to the studio.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host on your show, ask them to join the Discord server using the link [https://sta.radio/discord https://sta.radio/discord].

You can then use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>. You can send this command into <code>#registration</code> at any time.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-11-07T11:17:27Z

Andrew: /* Guests */ Slight rewording for clarity

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://sta.radio/discord '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, ask them to join the Discord server using the link [https://sta.radio/discord https://sta.radio/discord]. Your guests don't need to go through the <code>!verify</code> process - just ask them to let you know their Discord username.

During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code> to give them access to the studio.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-10-09T12:43:30Z

Andrew: /* Guests */ Add short link to invite guests

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://sta.radio/discord '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using this link: [https://sta.radio/discord https://sta.radio/discord]. During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-10-09T12:42:39Z

Andrew: /* The Basics */ Changed to short link for Discord invite

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://sta.radio/discord '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Studio Equipment

2020-10-08T13:57:18Z

Andrew: /* Speakers */ Note about stereo feeds to the monitor speakers

= Computers =
The studio has four active computers, all of which are located in the control room, with connections to studio screens going through holes at the bottom-middle of the separator wall.

{| class="wikitable"
|-
! Computer
! Nickname
! Asset Tag
! MAC
! OS
! CPU
! RAM
! Use
! In use since
|-
| HP EliteDesk 800 SFF G3
| Ingest
| 13491
| 3C-52-82-72-4B-C9
| Windows 10
| Intel Core i5-6500 @ 3.2GHz, 3192MHz, 4 core
| 8 GB
| Allows show hosts to upload music from the control room, i.e. off-air Myriad Playout. Also holds SQL server.
| July 2018
|-
| HP EliteDesk 800 SFF G3
| Playout
| 13764
| 18-60-24-9D-56-DC
| Windows 10
| Intel Core i5-7500 @ 3.4GHz, 3408MHz, 4 cores
| 8 GB
| Used by show hosts during broadcast, i.e. on-air Myriad Playout
| July 2018
|-
| HP Compaq 8000 Elite
| Buzzbox
| 01148
| 1C-C1-DE-52-AB-FE
|style="width: 10%"| Windows 7 (awaiting upgrade)
| Intel Core 2 Duo E8400 @ 3GHz, 3000MGz, 2 core
| 4 GB
|style="width: 30%"| Allows show hosts to use Buzzbox
| The big bang
|-
| HP Compaq 8000 Elite
| Video
| 01151
| 1C-C1-DE-52-A9-EF
| Windows 7 (awaiting upgrade)
| Intel Core 2 Duo E8400 @ 3GHz, 3000MGz, 2 core
| 4 GB
| No current use. Planned to be used for studio livestream. Previously used as Ingest/Playout.
| The big bang
|-
| HP Compaq 8000 Elite
| Tay-Tay
| 01398
| 00-23-24-29-7B-C4
| Windows 7 (awaiting upgrade)
| Intel Core 2 Duo E8400 @ 3GHz, 3000MGz, 2 core
| 4 GB
| No current use.
| The big bang
|-
| HP Compaq 8000 Elite
| Stream
| 07023
| 00-23-24-13-35-92
| Windows 7 (awaiting upgrade)
| Intel Core 2 Duo E8400 @ 3GHz, 3000MGz, 2 core
| 4 GB
| Sends audio to stream
| The big bang
|}

= Audio Hardware =

{| class="wikitable"
|-
| Model
| Type
| Use
| In use since
| Cost
|-
| SRM mixer v1 †
| Audio mixer
| Main studio controller
| February 2013
| Probably ~£5,000
|-
| Yamaha MG12XU
| Audio mixer
| External
| Probably circa. 2012
| Probably ~£300; comes with flight case
|-
| dbx 286s (silver)
| Microphone pre-amplifier/processor
| Processes one studio mic
| c. 2018
| ~£110
|-
| dbx 286s (black)
| Microphone pre-amplifier/processor
| Processes one studio mic
| The big bang
| Probably ~£110
|-
| dbx 286s (black)
| Microphone pre-amplifier/processor
| Processes one studio mic
| The big bang
| Probably ~£110
|-
| dbx 286s (black)
| Microphone pre-amplifier/processor
| Processes one studio mic
| The big bang
| Probably ~£110
|-
| M-Audio M-Track Eight
| Audio interface
| Collates audio from Myriad (i.e. songs)
| The big bang
| Unknown
|-
| Behringer compressor thingy (?)
| Compressor
| Collates audio from mic preamps and M-Track Eight
| The big bang
| Unknown
|-
| Avid Fast Track C400
| Audio interface
| Sends fully collated audio to Stream computer
| The big bang
| Unknown
|-
| Behringer UMC404HD
| USB audio interface
| External
| March 2019
| £109
|-
| Tascam US-2x2
| USB audio interface
| External
| November 2018
| £99
|-
| Yamaha Stagepas 400BT
| 2x PA speakers, integrated mixer, and 2x speaker stands
| External
| March 2020
| £458.99
|}

[[File:SRM PSU overheated August 2019.jpg|thumb|330px|Overheated SRM PSU, August 2019.]]

† The faders of the SRM mixer developed a "jitter" when fading a mic/song. This got worse with time, but was helped by opening the mixer and scraping fluff out of each fader. Eventually this cleaning process stopped improving the jitter. A new fader was ordered for £28.78 from Broadcast Radio in April 2019 to confirm that the faders were the problem. A further eight faders were then installed in August 2019 at a cost of £191.90. One of the eight new faders was bent in transit; a replacement was sent free of charge, and installed in September 2019.

Immediately after the set of eight new faders were installed, the mixer went completely dead. Upon inspection, part of the power supply appeared to have overheated. The PSU's earth wire was also found to be loose, though this was likely caused by the inspection. A new SRM PSU was ordered from Broadcast Radio for £167.94, and installed in September 2019. The mixer then worked perfectly.

= Microphones =
{| class="wikitable"
|-
! Model
! Use
! In use since
! Cost
|-
| Shure SM7B
| Studio presenter 1
| c. 2013
| ~£400 probably
|-
| Shure SM7B
| Studio presenter 2
| c. 2013
| ~£400 probably
|-
| Shure SM7B
| Studio presenter 3
| c. 2013
| ~£400 probably
|-
| Shure SM7B
| Studio presenter 4
| c. 2013
| ~£400 probably
|-
| Audio-Technica AT4040
| Spares/external
| c. 2008
| ~£300 probably
|-
| Audio-Technica AT4040
| Spares/external
| c. 2008
| ~£300 probably
|-
| Comica CVM-WM100 (2x lavalier mics, 2x wireless transmitters, 1x combined receiver)
| starTV interviews/external
| October 2019
| £222.27
|-
| Shure SM58
| External
| March 2020
| £85.75
|-
| Shure SM58
| External
| March 2020
| £85.75
|}

Note: we have three boxes and stands for the AT4040s, but only two have been seen since 2017.

= Headphones =
{| class="wikitable"
|-
! Model
! Use
! In use since
! Cost
|-
| Beyerdynamic DT 770 Pro (80 Ohm)
| Studio presenter 1 headphones
| November 2019
| £102
|-
| Beyerdynamic DT 770 Pro (80 Ohm)
| Studio presenter 2 headphones
| November 2019
| £102
|-
| Beyerdynamic DT 770 Pro (80 Ohm)
| Studio presenter 3 headphones
| November 2019
| £102
|-
| Beyerdynamic DT 770 Pro (80 Ohm)
| Studio presenter 4 headphones
| November 2019
| £102
|-
| Sennheiser HD 201
| Spares/external (previously used in studio)
| October 2017
| £24.99
|-
| Sennheiser HD 201
| Spares/external (previously used in studio)
| October 2017
| £24.99
|}

= Speakers =
{| class="wikitable"
|-
! Model
! Type
! Use
! In use since
|-
| M-Audio BX5something
| 5" speaker
| Studio monitor, for shows to hear themselves
| The big bang
|-
| M-Audio BX5something
| 5" speaker
| Control room monitor, for tech team/visitors to hear the show live
| The big bang
|}

The studio and control room monitors each take one side of a stereo feed - it is not double mono.

= Cables =
{| class="wikitable"
|-
! Type
! Length
! Quantity
! Use
! In use since
! Cost
|-
| XLR (m) - XLR (f)
| 5m
| 4
| Studio mics to mic preamps
| April 2018
| £16.57 each
|-
| XLR (m) - 1/4" TS
| 5m
| 4
| Mic preamps to studio SRM mixer
| April 2018
| £20.53 each
|}

= Software =
{| class="wikitable"
|-
! Program
! Use
! In use since
! Cost
! Installed on
|-
| Myriad Playout v5
| Main broadcast software and music database UI
| August 2018
| Part of £1499.99 Myriad buyout
| Ingest, Playout
|}

= starTV =
{| class="wikitable"
|-
! Model
! Use
! In use since
! Cost
|-
| Manfrotto tripod
| Camera tripod
| October 2019
| £47.19
|-
| Canon EOS 4000D DSLR + 64GB SanDisk memory card
| Camera and SD card
| February 2020
| £269.99
|}

= Miscellaneous =
{| class="wikitable"
|-
! Model
! Use
! In use since
! Cost
|-
| Røde PSA1 (black)
| Studio presenter 1 mic boom arm
| March 2019
| £65
|-
| Røde PSA1 (black)
| Studio presenter 2 mic boom arm
| November 2019
| £65
|-
| Røde PSA1 (black)
| Studio presenter 3 mic boom arm
| November 2019
| £65
|-
| Røde PSA1 (black)
| Studio presenter 4 mic boom arm
| November 2019
| £65
|-
| AFHS4 Pro Acoustic Foam (32x AFW305 + 4x Bassblock Bass Traps)
| Acoustic treatment for studio
| May 2019
| £55
|-
| Jelly Comb 2.4G wireless mouse with nano receiver (blue)
| Wireless mouse for Playout computer
| March 2019
| £6.99
|-
| Jelly Comb 2.4G wireless mouse with nano receiver (purple)
| Wireless mouse for Buzzbox computer
| March 2019
| £7.99
|-
| Jelly Comb 2.4G wireless mouse with nano receiver (purple)
| Wireless mouse for Buzzbox computer
| March 2019
| £7.99
|-
| Cloudplate T1 fan system (1U)
| Rack-mounted fan to cool mic preamps and compressor
| c. 2018
| ~£120 + ~£15 US-UK plug adapter
|}

Tech Info

2020-10-08T13:48:12Z

Andrew: /* Subdomains */ Add more info about `listen.` subdomain, add `stream.` subdomain.

Information on this page is intended for the Tech Team.

== Email Accounts ==
* STAR's emails are managed via [https://admin.google.com/standrewsradio.com admin.google.com/standrewsradio.com]
* STAR has a G Suite legacy account (i.e. created before December 2012), allowing the creation of unlimited free accounts, each with 15GB of storage.
** We started using G Suite around May 2008 (citation needed)
* Email addresses for committee members should follow forename.surname@standrewsradio.com.
* There are also multiple groups, e.g. news@, music@, programming@, and hello@. Committee members can be added to groups to receive emails sent to the group. Emails cannot be sent from a group address.
* Both users and groups may have aliases, e.g. bo@ redirects to manager@.
* The invalid user account, *@, will catch any emails sent to non-existent addresses within our domain. This is useful for unlocking old STAR pages connected to long-departed committee members.

== Stream URLs ==
* MP3: [https://stream.standrewsradio.com/stream.mp3 stream.standrewsradio.com/stream.mp3]
* Ogg: [https://stream.standrewsradio.com/stream.ogg stream.standrewsradio.com/stream.ogg]

== Domains ==
* STAR also owns [http://standrewsradio.co.uk standrewsradio.co.uk]; it should simply redirect to the main site.
* [https://sta.radio sta.radio] is STAR's custom URL shortener, which is hosted at [https://www.heroku.com/ Heroku]. The source code for the shortener is on [https://github.com/standrewsradio/sta.radio GitHub].
* Domains are managed by Rachel Hughes, Union Design & Marketing Manager ([mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk])
* The rapid.standrewsradio.com subdomain was associated with RapidSwitch; STAR moved from RapidSwitch to DigitalOcean in 2019, so no rapid. URLs should now be in use.

== Subdomains ==
* [https://studio.standrewsradio.com studio.standrewsradio.com]: the version of the Buzzbox displayed in the studio, showing listener counter and help section.
* [https://listen.standrewsradio.com listen.standrewsradio.com]: a separate version of the Buzzbox including a stream player. Appears to have once been part of a larger legacy website.
* [https://buzzbox.standrewsradio.com/ buzzbox.standrewsradio.com]: the listen. subdomain without the STAR logo at the top.
* [https://help.standrewsradio.com/ help.standrewsradio.com]: contains the help section, which is also shown within the studio. subdomain.
* [https://stream.standrewsradio.com/ stream.standrewsradio.com]: the subdomain used for [[#Stream URLs]].
* [http://archive.standrewsradio.com/ archive.standrewsradio.com]: you are here.
* [https://status.standrewsradio.com/ status.standrewsradio.com]: website status (subdomain created 5th Feb 2020).
* [https://manage.standrewsradio.com/ manage.standrewsradio.com]: .svg version of 2012 Gorilla Joe logo.
** <s>[https://manage.standrewsradio.com/grafana manage.standrewsradio.com/grafana]</s>: graph of listener stats (Grafana removed 5th Feb 2020 due to unreliability and a planned move to Google Analytics).
** [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]: global server stats, and list of mount points.
** [https://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]: extensive server stats.

== Tools ==
* [[Podcast Recorder]]: shell script that records, stores and cleans up archived podcasts.
* [https://github.com/Kezz101/ic2ga ic2ga]: Java programme that forwards Icecast statistics to Google Analytics.
* [[Stream Status]]: PHP page that checks if the stream is currently silent.

== Other links ==
STAR has team accounts on the following sites. Ask Tom, Kieran, or Ryo to add you if necessary.
* [http://analytics.google.com/ analytics.google.com]
* [https://cloud.digitalocean.com/ cloud.digitalocean.com]
* [https://github.com/StAndrewsRadio github.com]

Tech Info

2020-10-08T13:46:14Z

Andrew: /* Domains */ Add URL shortener

Information on this page is intended for the Tech Team.

== Email Accounts ==
* STAR's emails are managed via [https://admin.google.com/standrewsradio.com admin.google.com/standrewsradio.com]
* STAR has a G Suite legacy account (i.e. created before December 2012), allowing the creation of unlimited free accounts, each with 15GB of storage.
** We started using G Suite around May 2008 (citation needed)
* Email addresses for committee members should follow forename.surname@standrewsradio.com.
* There are also multiple groups, e.g. news@, music@, programming@, and hello@. Committee members can be added to groups to receive emails sent to the group. Emails cannot be sent from a group address.
* Both users and groups may have aliases, e.g. bo@ redirects to manager@.
* The invalid user account, *@, will catch any emails sent to non-existent addresses within our domain. This is useful for unlocking old STAR pages connected to long-departed committee members.

== Stream URLs ==
* MP3: [https://stream.standrewsradio.com/stream.mp3 stream.standrewsradio.com/stream.mp3]
* Ogg: [https://stream.standrewsradio.com/stream.ogg stream.standrewsradio.com/stream.ogg]

== Domains ==
* STAR also owns [http://standrewsradio.co.uk standrewsradio.co.uk]; it should simply redirect to the main site.
* [https://sta.radio sta.radio] is STAR's custom URL shortener, which is hosted at [https://www.heroku.com/ Heroku]. The source code for the shortener is on [https://github.com/standrewsradio/sta.radio GitHub].
* Domains are managed by Rachel Hughes, Union Design & Marketing Manager ([mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk])
* The rapid.standrewsradio.com subdomain was associated with RapidSwitch; STAR moved from RapidSwitch to DigitalOcean in 2019, so no rapid. URLs should now be in use.

== Subdomains ==
* [https://studio.standrewsradio.com studio.standrewsradio.com]: the version of the Buzzbox displayed in the studio, showing listener counter and help section.
* [https://listen.standrewsradio.com listen.standrewsradio.com]: a separate version of the Buzzbox.
* [https://buzzbox.standrewsradio.com/ buzzbox.standrewsradio.com]: the listen. subdomain without the STAR logo at the top.
* [https://help.standrewsradio.com/ help.standrewsradio.com]: contains the help section, which is also shown within the studio. subdomain.
* [http://archive.standrewsradio.com/ archive.standrewsradio.com]: you are here.
* [https://status.standrewsradio.com/ status.standrewsradio.com]: website status (subdomain created 5th Feb 2020).
* [https://manage.standrewsradio.com/ manage.standrewsradio.com]: .svg version of 2012 Gorilla Joe logo.
** <s>[https://manage.standrewsradio.com/grafana manage.standrewsradio.com/grafana]</s>: graph of listener stats (Grafana removed 5th Feb 2020 due to unreliability and a planned move to Google Analytics).
** [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]: global server stats, and list of mount points.
** [https://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]: extensive server stats.

== Tools ==
* [[Podcast Recorder]]: shell script that records, stores and cleans up archived podcasts.
* [https://github.com/Kezz101/ic2ga ic2ga]: Java programme that forwards Icecast statistics to Google Analytics.
* [[Stream Status]]: PHP page that checks if the stream is currently silent.

== Other links ==
STAR has team accounts on the following sites. Ask Tom, Kieran, or Ryo to add you if necessary.
* [http://analytics.google.com/ analytics.google.com]
* [https://cloud.digitalocean.com/ cloud.digitalocean.com]
* [https://github.com/StAndrewsRadio github.com]

Tech Info

2020-10-08T13:44:44Z

Andrew: /* Stream URLs */ Changing to `stream.` subdomain

Information on this page is intended for the Tech Team.

== Email Accounts ==
* STAR's emails are managed via [https://admin.google.com/standrewsradio.com admin.google.com/standrewsradio.com]
* STAR has a G Suite legacy account (i.e. created before December 2012), allowing the creation of unlimited free accounts, each with 15GB of storage.
** We started using G Suite around May 2008 (citation needed)
* Email addresses for committee members should follow forename.surname@standrewsradio.com.
* There are also multiple groups, e.g. news@, music@, programming@, and hello@. Committee members can be added to groups to receive emails sent to the group. Emails cannot be sent from a group address.
* Both users and groups may have aliases, e.g. bo@ redirects to manager@.
* The invalid user account, *@, will catch any emails sent to non-existent addresses within our domain. This is useful for unlocking old STAR pages connected to long-departed committee members.

== Stream URLs ==
* MP3: [https://stream.standrewsradio.com/stream.mp3 stream.standrewsradio.com/stream.mp3]
* Ogg: [https://stream.standrewsradio.com/stream.ogg stream.standrewsradio.com/stream.ogg]

== Domains ==
* STAR also owns [http://standrewsradio.co.uk standrewsradio.co.uk]; it should simply redirect to the main site.
* Domains are managed by Rachel Hughes, Union Design & Marketing Manager ([mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk])
* The rapid.standrewsradio.com subdomain was associated with RapidSwitch; STAR moved from RapidSwitch to DigitalOcean in 2019, so no rapid. URLs should now be in use.

== Subdomains ==
* [https://studio.standrewsradio.com studio.standrewsradio.com]: the version of the Buzzbox displayed in the studio, showing listener counter and help section.
* [https://listen.standrewsradio.com listen.standrewsradio.com]: a separate version of the Buzzbox.
* [https://buzzbox.standrewsradio.com/ buzzbox.standrewsradio.com]: the listen. subdomain without the STAR logo at the top.
* [https://help.standrewsradio.com/ help.standrewsradio.com]: contains the help section, which is also shown within the studio. subdomain.
* [http://archive.standrewsradio.com/ archive.standrewsradio.com]: you are here.
* [https://status.standrewsradio.com/ status.standrewsradio.com]: website status (subdomain created 5th Feb 2020).
* [https://manage.standrewsradio.com/ manage.standrewsradio.com]: .svg version of 2012 Gorilla Joe logo.
** <s>[https://manage.standrewsradio.com/grafana manage.standrewsradio.com/grafana]</s>: graph of listener stats (Grafana removed 5th Feb 2020 due to unreliability and a planned move to Google Analytics).
** [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]: global server stats, and list of mount points.
** [https://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]: extensive server stats.

== Tools ==
* [[Podcast Recorder]]: shell script that records, stores and cleans up archived podcasts.
* [https://github.com/Kezz101/ic2ga ic2ga]: Java programme that forwards Icecast statistics to Google Analytics.
* [[Stream Status]]: PHP page that checks if the stream is currently silent.

== Other links ==
STAR has team accounts on the following sites. Ask Tom, Kieran, or Ryo to add you if necessary.
* [http://analytics.google.com/ analytics.google.com]
* [https://cloud.digitalocean.com/ cloud.digitalocean.com]
* [https://github.com/StAndrewsRadio github.com]

Broadcasting via Discord

2020-10-07T09:54:47Z

Andrew: /* Guests */ Fix grammar

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-10-07T09:54:35Z

Andrew: /* Guests */ Fix syntax error

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code>. to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-10-07T09:53:17Z

Andrew: /* Guests */ Add where to send command

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> in <code>#control-room</code. to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-10-03T10:58:10Z

Andrew: /* Going Live */ Corrections about end of show and playing music

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <something></code>''' (without angle brackets), where <code>something</code> is a search term for a song you'd like to play or a YouTube link - for example, <code>_play Hello Lionel Richie</code> or <code>_play https://www.youtube.com/watch?v=dQw4w9WgXcQ</code>.

At the '''end of your show''' disconnect from <code>#the-studio</code> using the Disconnect button (phone with a cross icon), next to the phrase "Voice Connected".

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Main Page

2020-09-28T10:02:45Z

Andrew: /* Tech */ Add Jingle creation link

Welcome to the Starchive Wiki.

This wiki includes a history of the station, details of the studio technology, and helpful guides for committee members.

Additionally, this wiki contains handy guides on how to upload new memories to the Starchive. As editing the Starchive is restricted to pre-approved users, these guides probably won't be too handy for most people; however, feel free to have a look if you're interested in how the Starchive works.

This wiki will be updated periodically with a whole host of new information as and when it becomes available. For more information, or if you've got memories of your own to submit, please contact the Tech Team at [mailto:archive@standrewsradio.com archive@standrewsradio.com].

----

== All About STAR ==

* [[2005/06|Formation]]
* [[Old Articles|Old articles]]
* [[Links to Musicians|Links to musicians]]
* [[Gorilla Joe]]
* [[Logos]]
* [[Studio]]
* [[Festivals]]
* [[Constitution]]
* [[Notable Shows|Notable shows]]
* [[starTV]]
* [[Unrelatable Content|Unrelatable content]]
* [[Future ideas]]

==== By year ====
* [[2005/06]]
* [[2006/07]]
* [[2007/08]]
* [[2008/09]]
* [[2009/10]]
* [[2010/11]]
* [[2011/12]]
* [[2012/13]]
* [[2013/14]]
* [[2014/15]]
* [[2015/16]]
* [[2016/17]]
* [[2017/18]]
* [[2018/19]]
* [[2019/20]]
* [[2020/21]]

==== By committee position ====
* [[Broadcasting Officer| Station Manager]]
* [[Deputy Station Manager| Deputy Station Manager]]
* [[Secretary| Secretary]]
* [[Treasurer| Head of Finance]]
* [[Head of Marketing| Head of Marketing]]
* [[Head of Music| Head of Music]]
* [[Head of Programming| Head of Programming]]
* [[Head of Design| Head of Design]]
* [[Head of Production| Head of Production]]
* [[Head of Events| Head of Events]]
* [[starTV| Head of Video]]
* [[News Editor| News Editor]]
* [[Head of Web| Head of Web]]
* [[Head Technician| Head Technician]]
* [[Hearing Aid Editors| Hearing Aid Editors]]

== Tech ==
* [https://www.broadcastradio.com/myriad-5-playout-support Myriad documentation]
* [http://bit.ly/radioshowguide Show guide 2019/20]
* [[Create a Jingle|Create a Jingle]]
* [[Tech Info|Station Tech Info]]
* [[Studio Equipment|Studio Equipment]]
* [[Wordpress Tips|Wordpress tips]]
* [[Stream Status]]
* [[Remote broadcast]]
** [[Broadcasting via Discord|Via Discord]]

== Programming ==
* [[Station Rules|Station Rules]]
* [[Show Agreement|Show Agreement]]

== Starchive Help ==
* [[Guide to Starchive Gallery|Managing Starchive Gallery]]
* [[How to edit the Timeline|Editing the Starchive Timeline]]
* [mailto:tech@standrewsradio.com Email the tech team]

Create a Jingle

2020-09-28T10:00:43Z

Andrew: Initial version

Jingles are a 5-20 second musical introduction to your show and a great (and easy) way to solidify your show branding and set yourself apart from the crowd.

== Creating a Jingle ==
# Find an instrumental. This could be the karaoke track of your favourite song, or just search ‘free (lofi, trap, pop, sad, sexy, literally anything) beats’ on YouTube and copy and paste the link into a YouTube to MP3 converter and download it. Alternatively, if you can’t quite find the one, send an email to [mailto:production@standrewsradio.com production@standrewsradio.com] with details of what you want and they may be able to help you make something from scratch - see [https://www.youtube.com/watch?v=fjXHyPUozLM The Record's jingle].
# Choose the bit you like best. 10-20 seconds is ideal but go with what feels right. Dependent on whether you want to do a voiceover (see the next step), you may want a section with more or less happening instrumentally.
# Do you want to do a voiceover? You might want the jingle to introduce the show for you (e.g. you’re listening to/welcome back to/ introducing/insert anything you want to say - see the example of [https://www.youtube.com/watch?reload=9&v=3PPr9gCARvc OKUK's jingle]). If you decide you want to record vocals, proceed to step 4. If you just want the instrumental, skip to step 5.
# Record your voiceover. To make sure it all sounds ‘together’, pull the instrumental up on your computer and play it in-ear via headphones. Open Voice Memos on your phone, hit record and say your piece over the beat. Record it as many times as you need until you’re happy. If there's more than one show host who wants to feature, you can record together or separately, it doesn't matter! And don't worry, nobody likes the sound of their own voice (but if you're really desperate John can say it for you with the same beautiful voice as the OKUK jingle).
# Email the files to our Head of Production. Email [mailto:production@standrewsradio.com production@standrewsradio.com] with the instrumental and, if you have one, the voiceover file (which you can usually attach directly to an email from the Voice Memos app). You can also mention any guidance on how you’d like it to sound (when should the voiceover kick in? Do you want it to fade in or out? Reverb? Delay? Or if this makes no sense don’t worry and he'll do what sounds best). We can then put them both together, and get them ready for you to play on air!

Broadcasting via Discord

2020-09-26T09:38:57Z

Andrew: /* Controlling Music */ Updating Skip command

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <search term></code>''' (without angle brackets), where <code>search term</code> is a search term for a song you'd like to play - for example, <code>_play Never Gonna Give You Up</code>.

At the '''end of your show''', you'll be removed from the studio automatically. You can leave early by disconnecting from <code>#the-studio</code> using the Disconnect button (phone with a cross icon).

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_forceskip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-09-26T09:38:40Z

Andrew: /* Going Live */ Updating command

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_forceskip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <search term></code>''' (without angle brackets), where <code>search term</code> is a search term for a song you'd like to play - for example, <code>_play Never Gonna Give You Up</code>.

At the '''end of your show''', you'll be removed from the studio automatically. You can leave early by disconnecting from <code>#the-studio</code> using the Disconnect button (phone with a cross icon).

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-09-23T12:03:15Z

Andrew: /* More Detail */ Emphasise that it's not essential

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_skip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <search term></code>''' (without angle brackets), where <code>search term</code> is a search term for a song you'd like to play - for example, <code>_play Never Gonna Give You Up</code>.

At the '''end of your show''', you'll be removed from the studio automatically. You can leave early by disconnecting from <code>#the-studio</code> using the Disconnect button (phone with a cross icon).

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

'''This part is not essential reading''', but you might find it useful. Everything you need to know to run your show is written above.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-09-23T12:02:07Z

Andrew: /* More commands */ Correcting incorrect command

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_skip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <search term></code>''' (without angle brackets), where <code>search term</code> is a search term for a song you'd like to play - for example, <code>_play Never Gonna Give You Up</code>.

At the '''end of your show''', you'll be removed from the studio automatically. You can leave early by disconnecting from <code>#the-studio</code> using the Disconnect button (phone with a cross icon).

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

This part is not essential reading, but you might find it useful.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>!help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-09-23T12:00:13Z

Andrew: Correcting syntax of !addhost, tidying sections

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# Lead host only: '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_skip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <search term></code>''' (without angle brackets), where <code>search term</code> is a search term for a song you'd like to play - for example, <code>_play Never Gonna Give You Up</code>.

At the '''end of your show''', you'll be removed from the studio automatically. You can leave early by disconnecting from <code>#the-studio</code> using the Disconnect button (phone with a cross icon).

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More Detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

This part is not essential reading, but you might find it useful.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests ===
If you have a guest on your show, you can ask them to join the Discord server using the link in the [[#Starting the Semester]] section of this guide. During your show, you can use the command <code>!invite @guest-username</code> to give them access to the studio.

Your guests don't need to go through the <code>!verify</code> process.

To remove someone from the studio, use <code>!uninvite @guest-username</code>.

Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.

Listeners shouldn't be invited to the studio. They can listen on [https://standrewsradio.com standrewsradio.com] as normal.

=== New Co-Hosts ===
If you have a new co-host, you can use <code>!addhost <show day> <show time> @host-username</code> to automatically give them access to the studio during your show each week - for example, <code>!addhost Friday 5PM @Gorilla Joe</code>.

To stop granting someone access, use <code>!removehost <show day> <show time> @host-username</code>.

If you've got guests (who only need access once, or only while you're there), invite them as [[#Guests]] instead.

Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
For archival purposes, our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>#help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-09-23T11:47:38Z

Andrew: Lots of re-writing and organising to create a step-by-step guide which matches training better

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

'''Only current STAR shows can access the remote broadcast system:''' you'll still need to apply as normal, and wait to hear if you've been accepted.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== The Basics ==
A Discord server is a group of channels, where each channel is like a chat room. Think of Microsoft Teams, but each team is a server.

Channels can be for text chat, or voice chat. We use both - you can read information, talk to other people, and control the music by sending messages in text channels. To speak on air or hear what's going on, you connect to a voice channel.

'''STAR listeners should not join the Discord server.''' Your listeners can listen on [https://standrewsradio.com standrewsradio.com] as usual.

=== Starting the Semester ===
At the start of the semester, shows will receive an email about training. Follow the instructions in that email to '''book a practice slot'''.

'''Before your practice slot:'''
# [https://discord.gg/vfEH3dx '''Join''' the Discord server].
# '''Verify yourself''' with our system. Find our bot, Gorilla Joe (or Starbot Admin), in the list of server members. In a private message to Gorilla Joe, send the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you put on your show application. Follow the instructions Gorilla Joe sends back.
# '''Read the rest of this guide''' so you know how the system works.

=== Going Live ===
At the start of your show's slot, you'll be given access to the studio. You can't access our broadcast channels outwith your show time.
# '''Join the text channel <code>#control-room</code>'''. During your show, you'll send commands here to control the music. You can also send messages to chat to your co-hosts - our bots will just ignore anything that doesn't look like a command.
# '''Join the voice channel <code>#the-studio</code>'''. Now, you'll be able to hear everything going out on air. You can '''use the mute button to turn your mic on and off''' - for example, you should probably turn it off during songs. The mute button is usually in the bottom left of the screen, next to your username. When your mic is on, your voice will be broadcast on STAR.
# In <code>#control-room</code>, send the command '''<code>_clear</code> to get rid of the automatically-scheduled music'''. Then, you can either '''wait until the currently-playing song finishes to start your show''', or '''cut it off immediately''' using <code>_skip</code>.
# You can then '''unmute your mic to talk on air''', or '''play some music using <code>_play <search term></code>''' (without angle brackets), where <code>search term</code> is a search term for a song you'd like to play - for example, <code>_play Never Gonna Give You Up</code>.

At the '''end of your show''', you'll be removed from the studio automatically. You can leave early by disconnecting from <code>#the-studio</code> using the Disconnect button (phone with a cross icon).

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== More detail ==
If you'd like to get into the nitty-gritty, here's even more detail and commands you can use.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Play the music player if it's paused.
* <code>_play <YouTube link></code> (without angle brackets): Queue the specified YouTube link for playout. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_play <search term></code> (without angle brackets): Search YouTube for the specified term, then queue the first result. If the player is stopped, the song will start playing immediately. If the player is paused, the song will be queued.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next. If there's nothing queued, the player will stop.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely and clears the queue.
* <code>_queue</code>: Show the music that's currently queued.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Show what's currently playing.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Listener Counts ===
<code>!listeners</code> will let you know how many people are currently tuned in to STAR.

=== Guests and New Co-Hosts ===
* <code>!invite</code> and <code>!uninvite</code>: If you have a guest on your show, you can ask them to join the Discord server using the link above, then you can use the command <code>!invite @guest-username</code> during your show to give them access to the studio. Your guests don't need to go through the <code>!verify</code> process. To remove someone, use <code>!uninvite @guest-username</code>. Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.
* <code>!addhost</code> and <code>!removehost</code>: If you have a new co-host, you can use <code>!addhost @host-username</code> to automatically give them access to the studio during your show each week. To stop granting someone access, use <code>!removehost @host-username</code>. If you've got a guest who only needs access once, use <code>!invite</code> (above) instead. Again, be careful not to remove yourself by accident and get locked out of the studio!

=== Server Channels ===
Our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit-chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

=== Autoplay ===
Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. Autoplay can be forced to start using <code>!autoplay</code>.

=== More commands ===
Starbot Admin provides more commands you can use. Send <code>#help</code> to any channel to see the list. It's probably best to do that in a testing channel.

Broadcasting via Discord

2020-09-20T09:44:22Z

Andrew: Syntax correction

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Note about the video:''' You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.

== Getting Started ==
# [https://discord.gg/vfEH3dx Join the Discord server].
# Verify yourself with our Discord system. Only current show hosts can have shows on our remote broadcasting system. In order to verify youself, use the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you signed up with when you applied to be a show host. Normally, this is your University email address. Send the command in a [https://discord.com/channels/@me/706821087815794739 private message to the Gorilla Joe bot] (<code>Starbot Admin#9915</code>) - look for the list of server members to find the bot. Then, follow the instructions you receive back.
# Read the rest of this guide so you know how the system works.

== Server Channels ==
A channel is like a chat room, and a server is a group of channels.

Our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

Voice channels are for audio only, and chat channels are for text messages only. So, to control access to <code>#the-studio</code> and to control the music bot, send your command messages into <code>#control-room</code>. Any non-command messages in <code>#control-room</code> are ignored by our bots, so you can also use this text channel to talk to your co-presenters during your show.

== Going Live ==
At the time of your show, you and your co-hosts will automatically be given access to the studio. You can't access any of the broadcast channels until your show time.

To get started on air:
# Connect to <code>#the-studio</code> voice channel.
# Open the <code>#control-room</code> text channel.

Commands to control the music bot should all be sent in <code>#control-room</code>. You can also message your co-hosts there.

Everything in <code>#the-studio</code> is sent to broadcast, including your mic and music. You can use the mute button to turn off your microphone if you don't want your voice going to air (for example, during a song).

Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. If there's already music playing when you came in, or you arrived a bit late to the studio, these commands might help you out:
* <code>_remove all</code>: This will remove every song from the music queue. When the currently playing song has finished, no more songs will be played, which is a good time for you to get on air!
* <code>_nowplaying</code>: When you begin your show, you might want to let people know whatever song was just playing. If so, this command will show whatever song is currently playing.

At your show's end time, you will all be automatically removed from the studio.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Plays the music player.
* <code>_play <YouTube link></code> (without angle brackets): Queues the specified YouTube link for playout.
* <code>_play <search term></code> (without angle brackets): Searches YouTube for the specified term, then queues the first result.
* <code>_pause</code>: Pause or resume the music player.
* <code>_stop</code>: Stop the music player.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Shows what's currently playing.
* <code>_queue</code>: Shows the music that's currently queued.

You can see all music commands by sending <code>_help</code> to <code>#control-room</code>, but be aware the list it sends back doesn’t include the leading underscore before each command.

=== Other Commands ===
* <code>!listeners</code>: This will let you know how many people are currently tuned in to STAR.
* <code>!invite</code> and <code>!uninvite</code>: If you have a guest on your show, you can ask them to join the Discord server using the link above, then you can use the command <code>!invite @guest-username</code> to give them access to the studio. Your guests don't need to go through the <code>!verify</code> process. To remove someone, use <code>!uninvite @guest-username</code>. Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.
* <code>!addhost</code> and <code>!removehost</code>: If you have a new co-host, you can use <code>!addhost @host-username</code> to automatically give them access to the studio during your show each week. To stop granting someone access, use <code>!removehost @host-username</code>. If you've got a guest who only needs access once, use <code>!invite</code> (above) instead. Again, be careful not to remove yourself by accident and get locked out of the studio!

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://octave.gg Octave], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

Broadcasting via Discord

2020-09-20T09:43:22Z

Andrew: Syntax correction

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Note about the video:'''' You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.

== Getting Started ==
# [https://discord.gg/vfEH3dx Join the Discord server].
# Verify yourself with our Discord system. Only current show hosts can have shows on our remote broadcasting system. In order to verify youself, use the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you signed up with when you applied to be a show host. Normally, this is your University email address. Send the command in a [https://discord.com/channels/@me/706821087815794739 private message to the Gorilla Joe bot] (<code>Starbot Admin#9915</code>) - look for the list of server members to find the bot. Then, follow the instructions you receive back.
# Read the rest of this guide so you know how the system works.

== Server Channels ==
A channel is like a chat room, and a server is a group of channels.

Our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

Voice channels are for audio only, and chat channels are for text messages only. So, to control access to <code>#the-studio</code> and to control the music bot, send your command messages into <code>#control-room</code>. Any non-command messages in <code>#control-room</code> are ignored by our bots, so you can also use this text channel to talk to your co-presenters during your show.

== Going Live ==
At the time of your show, you and your co-hosts will automatically be given access to the studio. You can't access any of the broadcast channels until your show time.

To get started on air:
# Connect to <code>#the-studio</code> voice channel.
# Open the <code>#control-room</code> text channel.

Commands to control the music bot should all be sent in <code>#control-room</code>. You can also message your co-hosts there.

Everything in <code>#the-studio</code> is sent to broadcast, including your mic and music. You can use the mute button to turn off your microphone if you don't want your voice going to air (for example, during a song).

Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. If there's already music playing when you came in, or you arrived a bit late to the studio, these commands might help you out:
* <code>_remove all</code>: This will remove every song from the music queue. When the currently playing song has finished, no more songs will be played, which is a good time for you to get on air!
* <code>_nowplaying</code>: When you begin your show, you might want to let people know whatever song was just playing. If so, this command will show whatever song is currently playing.

At your show's end time, you will all be automatically removed from the studio.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Plays the music player.
* <code>_play <YouTube link></code> (without angle brackets): Queues the specified YouTube link for playout.
* <code>_play <search term></code> (without angle brackets): Searches YouTube for the specified term, then queues the first result.
* <code>_pause</code>: Pause or resume the music player.
* <code>_stop</code>: Stop the music player.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Shows what's currently playing.
* <code>_queue</code>: Shows the music that's currently queued.

You can see all music commands by sending <code>_help</code> to <code>#control-room</code>, but be aware the list it sends back doesn’t include the leading underscore before each command.

=== Other Commands ===
* <code>!listeners</code>: This will let you know how many people are currently tuned in to STAR.
* <code>!invite</code> and <code>!uninvite</code>: If you have a guest on your show, you can ask them to join the Discord server using the link above, then you can use the command <code>!invite @guest-username</code> to give them access to the studio. Your guests don't need to go through the <code>!verify</code> process. To remove someone, use <code>!uninvite @guest-username</code>. Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.
* <code>!addhost</code> and <code>!removehost</code>: If you have a new co-host, you can use <code>!addhost @host-username</code> to automatically give them access to the studio during your show each week. To stop granting someone access, use <code>!removehost @host-username</code>. If you've got a guest who only needs access once, use <code>!invite</code> (above) instead. Again, be careful not to remove yourself by accident and get locked out of the studio!

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://octave.gg Octave], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

Broadcasting via Discord

2020-09-20T09:42:46Z

Andrew: A couple more commands and a note about the video

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

```Note about the video:``` You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.

== Getting Started ==
# [https://discord.gg/vfEH3dx Join the Discord server].
# Verify yourself with our Discord system. Only current show hosts can have shows on our remote broadcasting system. In order to verify youself, use the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you signed up with when you applied to be a show host. Normally, this is your University email address. Send the command in a [https://discord.com/channels/@me/706821087815794739 private message to the Gorilla Joe bot] (<code>Starbot Admin#9915</code>) - look for the list of server members to find the bot. Then, follow the instructions you receive back.
# Read the rest of this guide so you know how the system works.

== Server Channels ==
A channel is like a chat room, and a server is a group of channels.

Our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

Voice channels are for audio only, and chat channels are for text messages only. So, to control access to <code>#the-studio</code> and to control the music bot, send your command messages into <code>#control-room</code>. Any non-command messages in <code>#control-room</code> are ignored by our bots, so you can also use this text channel to talk to your co-presenters during your show.

== Going Live ==
At the time of your show, you and your co-hosts will automatically be given access to the studio. You can't access any of the broadcast channels until your show time.

To get started on air:
# Connect to <code>#the-studio</code> voice channel.
# Open the <code>#control-room</code> text channel.

Commands to control the music bot should all be sent in <code>#control-room</code>. You can also message your co-hosts there.

Everything in <code>#the-studio</code> is sent to broadcast, including your mic and music. You can use the mute button to turn off your microphone if you don't want your voice going to air (for example, during a song).

Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. If there's already music playing when you came in, or you arrived a bit late to the studio, these commands might help you out:
* <code>_remove all</code>: This will remove every song from the music queue. When the currently playing song has finished, no more songs will be played, which is a good time for you to get on air!
* <code>_nowplaying</code>: When you begin your show, you might want to let people know whatever song was just playing. If so, this command will show whatever song is currently playing.

At your show's end time, you will all be automatically removed from the studio.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Plays the music player.
* <code>_play <YouTube link></code> (without angle brackets): Queues the specified YouTube link for playout.
* <code>_play <search term></code> (without angle brackets): Searches YouTube for the specified term, then queues the first result.
* <code>_pause</code>: Pause or resume the music player.
* <code>_stop</code>: Stop the music player.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Shows what's currently playing.
* <code>_queue</code>: Shows the music that's currently queued.

You can see all music commands by sending <code>_help</code> to <code>#control-room</code>, but be aware the list it sends back doesn’t include the leading underscore before each command.

=== Other Commands ===
* <code>!listeners</code>: This will let you know how many people are currently tuned in to STAR.
* <code>!invite</code> and <code>!uninvite</code>: If you have a guest on your show, you can ask them to join the Discord server using the link above, then you can use the command <code>!invite @guest-username</code> to give them access to the studio. Your guests don't need to go through the <code>!verify</code> process. To remove someone, use <code>!uninvite @guest-username</code>. Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.
* <code>!addhost</code> and <code>!removehost</code>: If you have a new co-host, you can use <code>!addhost @host-username</code> to automatically give them access to the studio during your show each week. To stop granting someone access, use <code>!removehost @host-username</code>. If you've got a guest who only needs access once, use <code>!invite</code> (above) instead. Again, be careful not to remove yourself by accident and get locked out of the studio!

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://octave.gg Octave], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

Broadcasting via Discord

2020-09-20T09:18:04Z

Andrew: Updates in preparation for training at start of semester

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

== Getting Started ==
# [https://discord.gg/vfEH3dx Join the Discord server].
# Verify yourself with our Discord system. Only current show hosts can have shows on our remote broadcasting system. In order to verify youself, use the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you signed up with when you applied to be a show host. Normally, this is your University email address. Send the command in a [https://discord.com/channels/@me/706821087815794739 private message to the Gorilla Joe bot] (<code>Starbot Admin#9915</code>) - look for the list of server members to find the bot. Then, follow the instructions you receive back.
# Read the rest of this guide so you know how the system works.

== Server Channels ==
A channel is like a chat room, and a server is a group of channels.

Our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

Voice channels are for audio only, and chat channels are for text messages only. So, to control access to <code>#the-studio</code> and to control the music bot, send your command messages into <code>#control-room</code>. Any non-command messages in <code>#control-room</code> are ignored by our bots, so you can also use this text channel to talk to your co-presenters during your show.

== Going Live ==
At the time of your show, you and your co-hosts will automatically be given access to the studio. You can't access any of the broadcast channels until your show time.

To get started on air:
# Connect to <code>#the-studio</code> voice channel.
# Open the <code>#control-room</code> text channel.

Commands to control the music bot should all be sent in <code>#control-room</code>. You can also message your co-hosts there.

Everything in <code>#the-studio</code> is sent to broadcast, including your mic and music. You can use the mute button to turn off your microphone if you don't want your voice going to air (for example, during a song).

Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. If there's already music playing when you came in, or you arrived a bit late to the studio, these commands might help you out:
* <code>_remove all</code>: This will remove every song from the music queue. When the currently playing song has finished, no more songs will be played, which is a good time for you to get on air!
* <code>_nowplaying</code>: When you begin your show, you might want to let people know whatever song was just playing. If so, this command will show whatever song is currently playing.

At your show's end time, you will all be automatically removed from the studio.

'''Tip:''' If you have a guest on your show, you can ask them to join the Discord server using the link above, then you can use the command <code>!invite @guest-username</code> in <code>#control-room</code> to give them access to the studio. Your guests don't need to go through the <code>!verify</code> process. To remove someone, use <code>!uninvite @guest-username</code>. Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in immediately.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Plays the music player.
* <code>_play <YouTube link></code> (without angle brackets): Queues the specified YouTube link for playout.
* <code>_play <search term></code> (without angle brackets): Searches YouTube for the specified term, then queues the first result.
* <code>_pause</code>: Pause or resume the music player.
* <code>_stop</code>: Stop the music player.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Shows what's currently playing.
* <code>_queue</code>: Shows the music that's currently queued.

You can see all music commands by sending <code>_help</code> to <code>#control-room</code>, but be aware the list it sends back doesn’t include the leading underscore before each command.

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://octave.gg Octave], for music.
* [https://carl.gg Carl], for announcements, logging, etc.