Venue-specific issues in vcon and streaming: Difference between revisions

From Iskomunidad
Mabriola (talk | contribs)
No edit summary
Mabriola (talk | contribs)
No edit summary
Line 11: Line 11:
* good network connectivity
* good network connectivity
* erratic audio feed from the hall's mixer  
* erratic audio feed from the hall's mixer  
==NIGS Auditorium==
* no network connectivity


==NISMED==
==NISMED==
* erratic network connection
* erratic network connection
==Pav 4 (Rm 4105))==
* tested 202.x network
* erratic audio feed from the room's mixer
* poor room acoustics
==CS Auditorium==
* erratic network connectivity


==Preparations==
==Preparations==

Revision as of 13:26, 5 July 2011

These are the issues encountered in attempts to mount vcon or live stream from these venues:

Claro M Recto Hall

  • erratic audio feed from the hall's mixer
  • untested 202.x network

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
  • erratic audio feed from the room's mixer
  • poor room acoustics

CS Auditorium

  • erratic network connectivity

Preparations

  • A schedule of 3-5 hours of field testing (prior to the date of the event itself) should be mandatory, except for very short notice event coverages.

See Also