Differences

This shows you the differences between two versions of the page.

--- requirements [2021/09/18 16:10] – andi
+++ requirements [2026/08/19 16:35] (current) – [Design] commanderred
@@ Line 1: / Line 1: @@
-= Requirements
+# Requirements
-Deutsche Fassung: [[de:requirements]]
+Deutsche Fassung: [de:requirements](de:requirements) (probably
+outdated).
-=== Help
+### Help
-We need help(ers) (/volunteers?) to run our setup in each room, mainly to operate cameras but also to operate the video mixer for switching between camera and slides. The organiser is responsible for making these helpers available. See also [[HelperIntroduction | Helfereinführung]]
+We need help(ers) (/volunteers?) to run our setup in each room, mainly
+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
-* Audio: we need a Mono audio mix per XLR, which we insert into a camera directly.
-* We also own audio equipment (mixer, microphones), which we don't always bring with us. When our equipment is absolutely necessary, clarify this as soon as possible with us.
-* We *do not* own a PA system, this will have to be provided by the location or rented externally. Please clarify this as early as possible.
-* Slides, projector signal via HDMI preferred, VGA as a backup. 19:9 aspect ratio is required.
-* Projektor/Folien: Projektor-Signal per VGA oder HDMI – bevorzugt in 16:9. Please clarify where we can split the video signal into our system.
-=== Schedule/Program
+- 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 ("FullHD") signal via HDMI or SDI. If your display
+  does not support that, please get in contact with us, we have a
+  stockpile of adaptors which we can bring if needed.
-Our semi-automated editing platform needs the program/schedule in the schedule.xml format. When you are not using Frab or Pretalx, we can also use a spreadsheet based file (CSV, ODS, XSLX, Google Docs, etc) or you can build your own tooling. For more information see [[schedule]].
+### Schedule/Program
-=== Network
+Our semi-automated editing platform needs the program/schedule in
-Our system more or less requires access to the Internet. If a firewall is on site, we need free access to ports (80, 443, 1194 TCP + UDP) at various (often changing) addresses on the Internet, unfiltered access is much preferred. Access should also be *without* a browser based portal.
+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.c3voc.de) or
+[pretalx hosted](https://pretalx.com).
-When sufficient Upload bandwidth is available we can also offer live streaming. We need at least 3MBit/s per stream/room, 5MBit/s is better.
+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.
-At events with more than one room we need all presentation rooms and our own office room connected to the same Layer 2 segment (for instance our own VLAN). Each room should have free Ethernet port(s), WiFi is insufficient. In an "emergency" we can run cabling through open windows or under doors etc.
+### Network
-=== Design
+For our systems to work correctly, a wired internet connection is
+required. We do require IPv4 connectivity, but a NATed connection is
+fine.
-We produce videos in Full HD, meaning 1920x1080p25. This means that we require artwork in these formats:
+Due to the nature of the infrastructure, we cannot provide you with a
-* Background image as PNG, optionally as an animation.
+list of ip addresses we need to connect to. If your network does have
-  * See the background of [[https://cloud.githubusercontent.com/assets/40266/24840604/3ab09c48-1d70-11e7-98e6-569970d152d2.png|1]] - there are several possible use cases for the background, see this video https://youtu.be/DNMpEpZnPLk?t=24m16s for possible limitations.
+restrictions, please ensure we can reach the whole internet on these
-  * https://github.com/voc/voctomix/issues/131#issuecomment-293774582
+ports:
-    * [[http://babelmonkeys.de/%7Eflorob/voctomix/template.svg|SVG Example]]
-    * [[http://babelmonkeys.de/%7Eflorob/voctomix/template.psd|Photoshop Example]]
-* Intro titelcard as SVG
-  * Example: https://github.com/voc/intro-outro-generator/blob/master/fossgis17/artwork/intro.svg
-  * When possible including animation
-    * supplied as MP4 or using the Generator
-* Outro titelcard as SVG
-  * Example: https://github.com/voc/intro-outro-generator/blob/master/fossgis17/artwork/outro.svg
-  * When possible including animation
-    * supplied as MP4 or using the Generator
-* When live streaming
-  * Pause image or animation
-    * Example: https://github.com/voc/intro-outro-generator/blob/master/sotmeu14/examples/pause.mp4?raw=true
-  * Optionally include "streaming logos" with room names
-    * Example https://github.com/voc/intro-outro-generator/blob/master/fossgis17/artwork/overlay.svg
-  * Optionally Artwork/design for the live streaming website
-    * Logo, CSS see https://streaming.media.ccc.de/fossgis17/ and https://github.com/voc/streaming-website/blob/master/README.md#konfiguration
-  * Optionally an Infobeamer design
+- **TCP:** 22 (SSH), 80 (HTTP), 443 (HTTPS), 1935 (Stream), 6667 (IRC),
+(IRC), 1883 (Mosquitto), 8883 (Mosquitto)
+- **UDP:** 53 (DNS), 1194 (VPN), 1337 (Stream), 20000-20255 (VPN)
+- **Optional, additionally for Users:** TCP 143, 587, 993 (Mail), UDP
+(VPN), 60000-60100 (Mosh)
-Intro/Outro-Generator https://github.com/voc/intro-outro-generator
+For streaming to work reliably, an uplink bandwidth of atleast 5mbit/s
-(Requires Python and Inkscape knowledge)
+per room is required.
-* Examples of generated Intros/Outros/Pause artwork https://github.com/voc/intro-outro-generator/tree/master/sotmeu14/examples
-=== Insurance
+If we do put hardware into more than one room (or if we have a separate
+office for post-processing), it would be very beneficial to have all the
+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.
+### Design
+We produce videos in FullHD (1920x1080, 25fps).
+You should supply us with the following artwork files:
+- 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.
+- **Outro:** Same as Intro. We can use event/talk-specific intros, but
+  usually we use one conference-wide outro.
+- When live streaming:
+- **Break animation:** A looping video that informs the viewers that
+  there's currently no stream running.
+- Example:
+  <https://github.com/voc/intro-outro-generator/blob/master/sotmeu14/examples/pause.mp4?raw=true>
+- **Break music:** Music that is playing while the break animation is
+  playing. **Must** be royality-free (ideally CC-BY or CC-0)
+- **design for the live streaming website:** Logo, CSS see
+  <https://streaming.media.ccc.de/fossgis17/> and
+  <https://github.com/voc/streaming-website/blob/master/README.md#konfiguration>
+- Some design files for [info-beamer](https://info-beamer.com/) so we
+  can show pretty animations on the projection screens while no talk is
+  running.
+[Detailed documentation](howto:design-artefakte)
+### 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#anlieferung_versicherung](eventhowto#anlieferung_versicherung)
+for more information on this topic.
+### DECT/ Phones (optional)
+If there is a phone network (Eventphone, microPOC or similar), we need
+the following extensions and devices:
+- Office (desk phone): 1561, 1562
+- "VOC Helpdesk" (callgroup): 1601
+- "VOC Legacy" (redirect to 1601): 1600
+- Per hall (replace ''x'' with hall number):
+- 16x2: "Mixer/ Regie" (desk phone)
+- optional 16x5: Herald (DECT)
+- optional 16x1: A/V-Technician (DECT)
+- optional 16x3: External FoH (DECT or desk phone)
+This is a simplified version of
+<https://wiki.cccv.de/crews/saal_coordination/public/saal_team_nummern>
-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 (ca. 10kEURO / room) this is usually handled by an event insurance which most organiser will already have. When necessary we can supply relevant serial numbers upon request. See [[eventhowto#anlieferung_versicherung]] for more information on this topic.