# 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)](/tech-deep-dive/mailinglists.md), 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](/engineering/remote.md#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](/engineering/remote.md) 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](/engineering/remote/connection-test.md) 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: ![](/files/-M32t5SbI6RBLsSNsc0X) In Airtime it should look like this. The **`master` must be disabled** if you are using the `show` input. ![](/files/-M32z_DzjzKYW-wLYGz4) {% 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](/production/step-by-step-guide.md#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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.radioangrezi.de/production/step-by-step-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.