Venue-specific issues in vcon and streaming: Difference between revisions
From Iskomunidad
mNo edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
* erratic network connectivity | * erratic network connectivity | ||
* needs ad-hoc wiring | * needs ad-hoc wiring | ||
<br /><br /> | |||
== | ---- | ||
==Notes== | |||
* A schedule of 3-5 hours of field testing (prior to the date of the event itself) is mandatory. | * A schedule of 3-5 hours of field testing (prior to the date of the event itself) is mandatory. | ||
* For online audience feedback, please also check for connection via providers like Globe or Smart. | |||
---- | ---- | ||
==See Also== | ==See Also== | ||
* [[Recommended equipment at the venue for video or webcast coverage]] | * [[Recommended equipment at the venue for video or webcast coverage]] | ||
* [[Guidelines for video or webcast coverage by DILC]] | |||
Revision as of 09:36, 26 August 2011
These are the issues encountered in attempts to mount vcon or live stream from ff venues:
Claro M Recto Hall
- erratic audio feed from the hall's mixer
- untested 202.x network
- ad-hoc wiring required both for network and audio feed
GT Toyota Hall
- erratic network connection
Malcolm Hall
- good network connectivity
- erratic audio feed from the hall's mixer
NIGS Auditorium
- no network connectivity
NISMED
- erratic network connection
Pav 4 (Rm 4105)
- tested 202.x network
- no audio mixer
- poor room acoustics
CS Auditorium
- erratic network connectivity
- needs ad-hoc wiring
Notes
- A schedule of 3-5 hours of field testing (prior to the date of the event itself) is mandatory.
- For online audience feedback, please also check for connection via providers like Globe or Smart.