Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| requirements [2025/08/06 20:21] – [DECT/ Phones (optional)] jtbx | requirements [2026/07/26 21:08] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | = Requirements | + | # Requirements |
| - | Deutsche Fassung: | + | Deutsche Fassung: [de: |
| + | outdated). | ||
| - | === Help | + | ### Help |
| - | We need help(ers) (/ | + | We need help(ers) (/ |
| + | to operate cameras but also to operate the video mixer for switching | ||
| + | between camera and slides. The organizer is responsible for making these | ||
| + | helpers available. See also [ Helfereinführung](HelperIntroduction ) | ||
| + | ### AV | ||
| - | === AV | + | - The location must have some sort of PA system. Our audio equipment |
| - | * The location must have some sort of PA system. Our audio equipment does use XLR outputs, but we do bring adaptors to be able Cinch (RCA) and 3.5mm Mini-Jack if needed. | + | |
| - | * The location must have some sort of video display. This is usually a projector, but having a large screen also works. Our equipment produces a 1080p (" | + | |
| + | - The location must have some sort of video display. This is usually a | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | ### Schedule/ | ||
| - | === Schedule/Program | + | Our semi-automated editing platform needs the program/schedule in |
| + | schedule.xml format. These file are produced by the usual conference | ||
| + | planning solutions (frab, pretalx, ...) without needing to configure | ||
| + | anything. If you want to use pretalx, but don't have the means to run | ||
| + | your own instance, you can use | ||
| + | [the c3voc pretalx instance](https:// | ||
| + | [pretalx hosted](https:// | ||
| - | Our semi-automated editing platform needs the program/ | + | If you don't use any of these tools, we do have some tooling to import |
| + | spreadsheet files (CSV, ODS, XSLX, Google Docs, ...). See | ||
| + | [schedule](schedule) for more details. Of course, building it using your | ||
| + | own tools is fine as long as it conforms to the published XSD. | ||
| - | If you don't use any of these tools, we do have some tooling to import spreadsheet files (CSV, ODS, XSLX, Google Docs, ...). See [[schedule]] for more details. Of course, building it using your own tools is fine as long as it conforms to the published XSD. | + | ### Network |
| + | For our systems to work correctly, a wired internet connection is | ||
| + | required. We do require IPv4 connectivity, | ||
| + | fine. | ||
| - | === Network | + | Due to the nature of the infrastructure, |
| + | list of ip addresses we need to connect to. If your network does have | ||
| + | restrictions, | ||
| + | ports: | ||
| - | For our systems to work correctly, a wired internet connection is required. We do require IPv4 connectivity, but a NATed connection is fine. | + | - **TCP:** 22 (SSH), 80 (HTTP), 443 (HTTPS), 1935 (Stream), 6667 (IRC), |
| + | 6697 (IRC), 1883 (Mosquitto), | ||
| + | - **UDP:** 53 (DNS), 1194 (VPN), 1337 (Stream), 20000-20255 (VPN) | ||
| + | - **Optional, additionally for Users:** TCP 143, 587, 993 (Mail), UDP | ||
| + | 13337 (VPN), 60000-60100 (Mosh) | ||
| - | Due to the nature of the infrastructure, we cannot provide you with a list of ip addresses we need to connect to. If your network does have restrictions, | + | For streaming |
| - | * **TCP:** 22 (SSH), 80 (HTTP), 443 (HTTPS), 1935 (Stream), 6667 (IRC), 6697 (IRC), 1883 (Mosquitto), | + | per room is required. |
| - | * **UDP:** 53 (DNS), 1194 (VPN), 1337 (Stream), 20000-20255 (VPN) | + | |
| - | * **Optional, additionally for Users:** TCP 143, 587, 993 (Mail), UDP 13337 (VPN), 60000-60100 (Mosh) | + | |
| - | For streaming to work reliably, an uplink bandwidth of atleast 5mbit/s per room is required. | + | If we do put hardware into more than one room (or if we have a separate |
| + | office for post-processing), | ||
| + | rooms connected to a separate layer 2 segment (separate VLAN is | ||
| + | sufficient). We will bring our own router hardware, please do not put a | ||
| + | DHCP server in there. | ||
| - | If we do put hardware into more than one room (or if we have a separate office for post-processing), | + | ### Design |
| - | + | ||
| - | + | ||
| - | === Design | + | |
| We produce videos in FullHD (1920x1080, 25fps). | We produce videos in FullHD (1920x1080, 25fps). | ||
| Line 40: | Line 69: | ||
| You should supply us with the following artwork files: | You should supply us with the following artwork files: | ||
| - | * Background image as PNG, optionally as an animation. | + | - Background image as PNG, optionally as an animation. |
| - | * **Intro:** This should be either a static PNG or some sort of video which we can use in our generator to create intros. Optionally you can provide us with fully rendered videos for each event/talk that we should provide videos for. | + | - **Intro:** This should be either a static PNG or some sort of video |
| - | * **Outro:** Same as Intro. We can use event/ | + | |
| - | * When live streaming: | + | |
| - | | + | |
| - | | + | - **Outro:** Same as Intro. We can use event/ |
| - | | + | |
| - | | + | - When live streaming: |
| - | * Some design files for [[https:// | + | - **Break animation: |
| + | | ||
| + | - Example: | ||
| + | <https:// | ||
| + | - **Break music:** Music that is playing while the break animation is | ||
| + | | ||
| + | - **design for the live streaming website:** Logo, CSS see | ||
| + | <https:// | ||
| + | <https:// | ||
| + | - Some design files for [info-beamer](https:// | ||
| + | | ||
| + | | ||
| - | Detailed documentation: | + | Detailed documentation: |
| - | === Insurance | + | ### Insurance |
| - | The organiser has to insure our hardware for damages and theft during the event and relevant transportation from/to the event. Since the hardware is relatively expensive (roughly 16.000EUR per case) this is usually handled by an event insurance which most organizers will already have. When necessary we can supply relevant serial numbers, please get in contact if needed. See [[eventhowto# | + | The organiser has to insure our hardware for damages and theft during |
| + | the event and relevant transportation from/to the event. Since the | ||
| + | hardware is relatively expensive (roughly 16.000EUR per case) this is | ||
| + | usually handled by an event insurance which most organizers will already | ||
| + | have. When necessary we can supply relevant serial numbers, please get | ||
| + | in contact if needed. See | ||
| + | [eventhowto# | ||
| + | for more information on this topic. | ||
| - | === DECT/ Phones (optional) | + | ### DECT/ Phones (optional) |
| - | If there is a phone network (Eventphone, | + | If there is a phone network (Eventphone, |
| + | the following extensions and devices: | ||
| - | * Office (desk phone): 1561, 1562 | + | - Office (desk phone): 1561, 1562 |
| - | | + | - "VOC Helpdesk" |
| - | | + | - "VOC Legacy" |
| - | | + | - Per hall (replace '' |
| - | | + | - 16x2: " |
| - | | + | - optional 16x5: Herald (DECT) |
| - | | + | - optional 16x1: A/ |
| - | | + | - optional 16x3: External FoH (DECT or desk phone) |
| - | This is a simplified version of https:// | + | This is a simplified version of |
| + | <https:// | ||