Difference between revisions of "Team:Productiehuis"

From SHA2017
Jump to: navigation, search
(Relations to other teams)
Line 36: Line 36:
  
 
|-
 
|-
|[[Buildup Mgmt]] and [[Team:Volunteers]]
+
|[[Team:Volunteers]] and [[Buildup Mgmt]]
|Setup and test
+
|
 +
* Pre-build up checking of gear (off site)
 +
** Testing audio gear
 +
** Testing video setup
 +
** Checking supplies, i.e. batteries and spare-<anythings>
 +
* People on build up
 +
** Building up Audio
 +
** Building up Lighting
 +
** Building up Streaming infrastructure
 +
** Building up VOC
 +
** Building up monitoring network to probe VOC health
 +
* People operating the gear during the event
 +
** Mixer (per tent)
 +
** Camera's per tent
 +
** Camera switcher
 +
** Wiring up the presenters
 +
** Monitoring the streamers
 +
** Monitoring the Content Delivery Network
 +
** Lighting operator
  
 
|-
 
|-
 
|[[Team:Volunteers]]
 
|[[Team:Volunteers]]
|People operating the gear during the event.
+
|Teardown, with caution to the sensitive gear.
  
 
|-
 
|-
|[[Team:Volunteers]]
+
|[[Content]] and [[Team:Broadcast]]
|Teardown
+
|To anticipate special requests Productiehuis *MUST* be kept in the loop to facilitate properly. Examples:
 
+
* Additional close-up camera
|-
+
* Interfaces to audio, video, etc
|[[Content]]
+
* Dual beamer requirements perhaps
|To anticipate special requests, Productiehuis *MUST* be kept in the loop to facilitate special interfaces, camera's and more.
+
* Amount of microphones required per stage
 
+
* Facilitate conference calls of proprietary protocols/media/carriers
|-
+
* Other stuff which requires magic to pull off a hat trick and avoid a last-minute McGuyver hack 5 minutes before stage time.
|[[Team:Broadcast]]
 
|To anticipate special requests, Productiehuis *MUST* be kept in the loop to facilitate special interfaces, camera's and more.
 
  
 
|-
 
|-
 
|[[Team:Infrastructure]]
 
|[[Team:Infrastructure]]
 
|Productiehuis will have special power requirements for the lighting, AV, streaming and radio.
 
|Productiehuis will have special power requirements for the lighting, AV, streaming and radio.
 +
* Radio requirements are unknown, but might require more than regular 240V.
 +
* Lighting at every stage will require sufficient power to each tent.
 +
* Power to audio and lighting must be separated to avoid overload.
 +
* The audio system should be galvanically in harmony to avoid 50Hz buzzzing at the stage and front-of-stage setup.
  
 
|-
 
|-
Line 76: Line 96:
  
 
|}
 
|}
 
 
  
 
== Todo ==
 
== Todo ==

Revision as of 20:31, 18 April 2016

Productiehuis
1st line contacts: geekabit
Does: Stage:
  • stage lights
  • projectors
  • video (equipment and streams)
  • audio stage
  • desks on stage

Radio:

  • equipment radio station
Does not: Stage:
  • the stage itself (the physical thing)
  • stage decoration (plants, etc.)

Radio:

  • radio content
  • radio license
Is an exclusive team: Yes
Contact: orga-av@lists.sha2017.org
IRC: #sha2017-productiehuis
Deadlines:
  • 2017/02/01 - point of no return (order list)
Needed resources:
Comment: Made up of voc, a/v, stage
Vacancies: 0
Current team size / amount of ppl: 0
Contact at projectleiding:
Backup Contact at projectleiding: {{{Backup_Projectleiding}}}
"{{{Backup_Projectleiding}}}" cannot be used as a page name in this wiki.
Managed Vacancies:
You can add for your team on a page by adding: {{TeamVacancies|Productiehuis}}

17 Team Members Productiehuis

team:avid during OHM2013

Team members

Relations to other teams

Team Relation
Team:Volunteers and Buildup Mgmt
  • Pre-build up checking of gear (off site)
    • Testing audio gear
    • Testing video setup
    • Checking supplies, i.e. batteries and spare-<anythings>
  • People on build up
    • Building up Audio
    • Building up Lighting
    • Building up Streaming infrastructure
    • Building up VOC
    • Building up monitoring network to probe VOC health
  • People operating the gear during the event
    • Mixer (per tent)
    • Camera's per tent
    • Camera switcher
    • Wiring up the presenters
    • Monitoring the streamers
    • Monitoring the Content Delivery Network
    • Lighting operator
Team:Volunteers Teardown, with caution to the sensitive gear.
Content and Team:Broadcast To anticipate special requests Productiehuis *MUST* be kept in the loop to facilitate properly. Examples:
  • Additional close-up camera
  • Interfaces to audio, video, etc
  • Dual beamer requirements perhaps
  • Amount of microphones required per stage
  • Facilitate conference calls of proprietary protocols/media/carriers
  • Other stuff which requires magic to pull off a hat trick and avoid a last-minute McGuyver hack 5 minutes before stage time.
Team:Infrastructure Productiehuis will have special power requirements for the lighting, AV, streaming and radio.
  • Radio requirements are unknown, but might require more than regular 240V.
  • Lighting at every stage will require sufficient power to each tent.
  • Power to audio and lighting must be separated to avoid overload.
  • The audio system should be galvanically in harmony to avoid 50Hz buzzzing at the stage and front-of-stage setup.
Team:Logistics Productiehuis gear will need to be stored, pre-serviced before transport to the terrain, stored safely, moved and returned. We need tents to work in and sufficient space in the NOC to create a VOC. Access to a golfkart or other motorized vehicle to quickly drive towards a tent with technical problems.
Team:NOC Modern audio and lighting equipment might need a private network, streamers need dedicated bandwidth from tents to the VOC to monitoring each tent equipment health (private/closed network). The streams must also be delivered to a content delivery network to stream online. Accesspoints in the truss/rigging.
Team:DECO The stages must look pretty, besides just functional. Style is everything. We also need functional lighting in the tents.
Team:Lounge Coherent audio/DJ-gear with the lounge makes it possible to use the audio from the Lounge for broadcasting on radio, streaming or just get gear at one AV-supplier.

Todo

There is a wiki page with a todo list.

Meetings

All meetings (so far) are held via mumble No meetings planned. Look at the PastMeetings page, or link-3DForm:Team Meeting add a meeting here.