Versions Compared

Old Version 14

changes.mady.by.user Hannah Petty

Saved on

compared with

New Version 15

changes.mady.by.user Hannah Petty

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To ensure operational effectiveness, every attempt should be made by Echo360 customers to comply with the environmental standards contained herein. Echo360 understands that our customers are faced with many factors when choosing IT infrastructure and respects the business decisions of our audience. The intent here is not to forcibly drive those business decisions, but instead to establish a framework within which risk is understood. Should a customer decide to deviate from the aforementioned standards, it is agreed that the customer assumes the operational risk and at some point, Echo360 might not be able to resolve a reported technical problem.

...

This product...Is supported on these operating systems...
ESS

Windows:

  • Windows Server 2012 R2 (SQL Server 2008) - Standard, 64-bit. Pen/touch input was not tested.  
  • Windows Server 2008 (and R2) - Standard or Enterprise Only, 64-bit.

Linux: 

  • RHEL Server releases 6 and 7, 64-bit.
  • CentOS 6.5, 32/64-bit.
Media Processor

Windows:

  • Windows Server 2012 - Standard, 64-bit. Pen/touch input was not tested.  
  • Windows Server 2008 (and R2) - Standard or Enterprise Only, 64-bit.

Linux: 

  • RHEL Server releases 6 and 7, 64-bit.
  • CentOS 6.5, 32/64-bit.

Personal Capture for Windows

or

Classroom Capture

Windows: Either Personal Capture or Classroom Capture.

  • Windows 7
  • Windows 8.1

NOTES:

  • We have not fully tested Windows 10 for use with the ESS, and therefore cannot add this to our documentation as being compliant. Windows 10 support is currently available on the Echo360 active learning platform.
  • Personal Capture for Windows and Classroom Capture have not been qualified on hybrid PCs (touch screen PCs, writable screen PCs, etc.) Unfortunately, we cannot guarantee full compatibility with these devices.

For additional information on supported cameras and input devices, Supported Cameras and Input Devices for Capture

Personal Capture for Mac

 

Macintosh: Mac OS X 10.9+ (Mavericks)

NOTES:

    • Personal Capture will not run properly on a Mac with Retina display when there is an external monitor attached. This is a known issue and will be addressed in a future release.
    • Personal Capture for Mac is supported on Mavericks (Mac OS X 10.9), however upgrading to Mavericks may cause corruption in an existing PCAP installation. Captures will work fine but , however, publishing the capture will get stuck in the "Transcode Pending" state. If this happens, save any unpublished captures, then uninstall and reinstall PCAP.
       

For additional support information, see System Requirements for Personal Capture Mac

For additional information on supported cameras and input devices, Supported Cameras and Input Devices for Capture

...

  • More CPUs = Larger disk requirement. With 4 CPUs, 160GB is a minimum space recommendation.
  • With respect to CPU's, while it is possible to use virtual CPU's, the media processing generates very high CPU and disk I/O, making it a bad candidate for virtualization.  Where possible, use physical CPU's CPUs for EchoSystem Media Processors.
  • Windows allows you to specify a separate data directory from the application files (where the processing is done); Linux does not. If you maintain the media processor application and the data on the same drive (the main partition), be sure there is sufficient space for everything.
  • Processing long recordings, and especially editing long recordings, consumes a lot of temporary space on the media processor. As a result, be sure your configuration allows for at least 32 GB of free space on the main partition at all times (the partition onto which the media processor application is installed).

  • For a large production system, calculate space based on 40GB per CPU core. In addition, if the media processor server contains 8 cores or more, we strongly suggest that you specify the data directory to be 2 or more RAID 0 SAS drives. The reason is that without the RAID, the disk I/O for the processing becomes a bottleneck, wasting the additional core processing capability. Using a RAID for data also allows you to plan for future growth and to scale the system appropriately.

  • Please review the Migration Guide for migration-specific configuration recommendations.

...