# Step-by-Step form Home ## Send proposal and show info to Plenum Minimum info for a broadcast: * Your name * Your phone number + E-Mail * Show title * Show description (\~ 250 characters) * Date, time and duration If you did not agree with your plenum contact person on anything else, **email this info** to . This info will be put on the [Angrezi website](http://radioangrezi.de/), the [mailing list(s)](https://docs.radioangrezi.de/tech-deep-dive/mailinglists), the [Telegram channel](https://t.me/radioangrezi), [Facebook](https://facebook.com/radioangrezi), [Instagram](http://instagram.com/radioangrezi). Each show has a fixed ***Pat\*in***** (plenum contact person)**, which helps with announcing, setting up, testing and organising the broadcast. Please don't do solo-broadcasts. It is nice to have a helping hand (even if it is just a fallback). ## Get booked airtime Your broadcast must be [scheduled in AirTime](http://studio.radioangrezi.de/schedule) (by somebody with access, usually the coordination gang). This way it will be also visible on the website. If you [stream using your own account](https://docs.radioangrezi.de/engineering/remote#direct-one-way-streaming-to-the-studio-harbor) form a remote location, the booking **must include your user account**. Otherwise you will not be able to connect! You will get your **login credentials (username and password)** form the [tech crew](mailto:tech@radioangrezi.de) or your plenum contact person. These accounts are managed in [Airtime](http://studio.radioangrezi.de/user/add-user) and must be "DJ accounts". Coordinators with access to the `studio` account can create user accounts at: ## Do a rehearsal Before your broadcast you should do a **rehearsal** using your setup (soundcard, computer, mixer, etc.) and a test connection. Therefore you should book a second "rehearsal slot", also including your user account. Prefix the show title with `(Test)`, to make it invisible on the website. Follow the [detailed guide on how to stream form a remote location](https://docs.radioangrezi.de/engineering/remote) to set yourself up. {% hint style="warning" %} Your "rehearsal" will be live on the stream, available **publicly**. (We don't have a private test possibility yet.) {% endhint %} You can additionally use the [testserver](https://docs.radioangrezi.de/engineering/remote/connection-test) for an early rehearsal. ## Connect to stream If your show time has come. **Connect to the stream and start the recording.**\ Usually you should open the stream with a **jingle** and an **announcement** of what is coming up. You find all jingles here:\ If you use butt, it should look like this: ![](https://1185056148-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LZz-gDif_VD8dauQ2-7%2F-M32q_TAP4ZaMKZ8lOFx%2F-M32t5SbI6RBLsSNsc0X%2FScreenshot%202020-03-21%20at%2016.59.38.png?alt=media\&token=9aa03bfd-8b2f-45b4-927b-761ea6273a3c) In Airtime it should look like this. The **`master` must be disabled** if you are using the `show` input. ![](https://1185056148-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LZz-gDif_VD8dauQ2-7%2F-M32wcaumzcMTVRbFz3W%2F-M32z_DzjzKYW-wLYGz4%2FScreenshot%202020-03-21%20at%2015.56.17.png?alt=media\&token=fdb05427-edd0-4d21-9ce6-a58933db4f58) {% hint style="danger" %} Currently there seems to be an issue with liquidsoap, which causes the stream to stay silent even though your are successfully connected. [see below](#stream-stays-silent) {% endhint %} ## Record Don't forget to record. (We are working on a server-side recording currently.) Local recordings have a better quality anyway, though. ## Enjoy! your broadcast. Keep an eye on the **shoutbox** on the website. You can also use the studio view:\ (If you run **overtime** your slot must be prolonged, otherwise you will be kicked out of the stream.) ## Known Issues ### Stream stays silent Currently there seems to be an issue with liquidsoap, which causes the stream to stay silent even though your are successfully connected. Workaround 1: **Manually restart `airtime-liquidsoap` on the server.** \ \&#xNAN;*You find the username and password in the general passwords.txt file.* Workaround 2: It could also be true, that the **master source is still enabled**! This would block (= silence) the show source.