These Release Notes contain a summary of changes made for the December 17-18, 2019 release of Echo360. For changes made in previous deployments, see the other Release Notes articles located in this Topic group, or contact email@example.com.
Our typical two-week release cycle will continue as normal into December. To accommodate the end of year holidays, there will be a 4-week break prior to the first deployment in January 2020.
Our deployment dates for the upcoming releases are as follows:
- Dec 17-18 (this one)
- Jan 14-15, 2020 (four weeks from previous)
End of Life for Classroom & Personal Capture
As you know by now, Echo360 Universal Capture is in general availability for both Mac and Windows, and for Personal and Classroom modes. Universal Capture replaces the existing applications Classroom Capture (CCAP) and Personal Capture (PCAP) for a better and easier capture experience. We are seeing excellent adoption rates for Universal Capture, so it is time to plan for the end of support for the legacy applications.
We plan to phase out both technical support and functional support in the platform over the following timeline:
August 30th, 2019: The download links for both CCAP and PCAP were removed from the platform. This was also the end of support date for these applications in Europe, the Middle East, and Africa (EMEA). While the applications will likely continue to work for the rest of the year, there will be no support available.
Clients in the EMEA region should plan a full transition to Universal Capture before this time. Clients in other regions can continue to use existing CCAP and PCAP installations but will no longer have the ability to download it.
- January 15th, 2020: This date marks both the end of life and the end of support for these applications globally. As of this date, CCAP and PCAP will cease to work with the Echo360 platform due to enhancements in the capture pipeline that will only work with Universal Capture.
It is of the utmost importance that all Echo360 clients complete their transition to Universal Capture by this time. If you have any questions about your transition to Universal Capture, please contact your Echo360 representative and see our Universal Capture documentation.
New Create Media option for embedding videos in your LMS! Along with selecting media from their content library, or uploading media to embed, users can now launch their installation of Universal Capture from the Embed Media window, create a capture, then embed the new media.
Along with the ability to create media and embed it as a single process, LMS embeds can now be fully authenticated (as long as the user is logged into the LMS). This allows Echo360 to better track unique views of these embedded videos and provide more accurate media analytics. For more information, see Authentication for Embedded Videos in LMS Content Windows.
New LIVE column in the Admin Captures page! We have added a column to the Captures page for Administrators that shows whether a capture was a Live capture (or is a Live capture, for those in Capturing status). Admins also have the ability to filter by this new field.
Please note that while all current and future captures will have this information going forward, we will only be able to provide this data on older captures going back approximately one year.
- The Rooms tab for Administrators now shows a red Live badge on any room card where a Live capture is occurring.
Device Software Update: Version 6.0.676259215
NOTE: The Device Software Update entry is only included when an update is being deployed; the legacy software version is NOT likely to change often, and it is not included if no updates are being deployed.
- Resolved an issue where administrators were receiving Device Offline alerts for devices not assigned to rooms.
- Resolved an issue where the Universal Capture: Device web UI was unable to be accessed with SSO credentials.
- Resolved an issue where a user could not log out of the Universal Capture: Device web UI when logged in with SSO credentials.
- Resolved an issue where Universal Capture was not handling tokens correctly while the application was making other calls, potentially resulting in users having to log in frequently due to a loss of their user session.