edix 2.2 Server Installation Guide XTRMX January 2018 XTRMX.com/edix

Transcription

1 edix 2.2 Server Installation Guide January 2018.com/edix Remote Editing Proxy-free workflow Integrated with Adobe Premiere Pro Audio Support up to 16 tracks Storage agnostic LTD.

2 VERSION INFORMATION Version Date Remarks Author Alpha Beta First Release Auto Installation Disclaimer: software is covered by this disclaimer: While make every effort to deliver high quality products, we do not guarantee that our products are free from defects. Our software is provided as is," and you use the software at your own risk. We make no warranties as to performance, merchantability, fitness for a particular purpose, or any other warranties whether expressed or implied. No oral or written communication from or information provided by shall create a warranty. Under no circumstances shall be liable for direct, indirect, special, incidental, or consequential damages resulting from the use, misuse, or inability to use this software, even if has been advised of the possibility of such damages. These exclusions and limitations may not apply in all jurisdictions. You may have additional rights and some of these limitations may not apply to you. LTD.

3 Table of Contents System Overview edix Rendering Server Specification Installation edix Streaming Server Specification Storage Bandwidth Network Streaming Bandwidth Ports Installation & Configuration Appendix 1: Add users Appendix 2: Edit the hosts file Edit host file on Windows Edit host file on Mac OS (Any version) IV V V V VII VII VII VII VIII VIII XIII XV XV XVII LTD.

4 System Overview edix software environment is compound of: Streaming Service: Software components that are responsible to: o facilitates remote editing sessions (user authentication, robustness, security) o streaming content for the remote editing Rendering Service o Rendering execution Storage: where the original media is stored, and streamed using to the remote editing workstations. The streaming service, Rendering service and the storage component compose the Media Streaming Unit. Editing Workstations: user end-points with an Adobe Premiere Pro CC and the edix plugin installed. Adobe Premiere Pro CC is a professional video editing application used in film, broadcast, and web content creation. Media Streaming Unit Work Stations Streaming Service Rendering Service edix uses two servers: edix streaming server: Streaming content to the remote editing workstations edix Rendering server: Remote rendering execution Although theoretically both servers can be installed on the same machine, we recommend keeping the servers separated so the rendering jobs resources-consumption won t interfere with the realtime streaming process. The following sections describe the pre-requisites and installation procedure of each of those servers. LTD.

5 edix Rendering Server Specification Windows Operating System, RAM & processors according to Adobe Media Encoder system requirements The following software component should be installed on the rendering server: o Adobe Premiere Pro (v12.0 and up) + Adobe Media Encoder o edix rendering plugin Installation 1. Invoke as administrator: Setup will prompt for administrator privileges. 2. Login to your account: Setup will prompt for your account user name ( ) and password. If you don t have an account yet, you will be able to create one with the link provided at the bottom of that dialog ( LTD.

6 3. Set username, password and port: The rendering service account should have rights to access the storage and administrator privileges on the local machine. Use the Browse-button to select the appropriate user, and select the adequate rendering-service port (8000 by default). 4. Done! Congratulation, you had successfully installed the edix rendering service! Once the setup is finished, you can validate that the streaming server is running: Open the services window, and find the _AME (Stands for Adobe Media Encoder ) with a Running status. LTD.

7 edix Streaming Server Specification Operating System: Windows Server 2016 R2 or RAM:128 GB RAM GPU/CPU: The server s GPU/CPU determines the performances in terms of concurrent streams. The following configurations are validated and benchamrked. The performance of each server spec (in terms of number of concurrent streams) is given based on the assumption below: Server specification Concurrent streams i5-5200u@2.2ghz, OpenCL 2.0 Support 1 Xeon E5-2620V4@2.1GHz, Tesla M60 16 Xeon E5-2620V4@2.1GHz, Tesla P Xeon E5-2690V4@2.6GHz, 2 x Tesla M60 22 assumptions and constraints 1) Source format: XDCAM x fps, with 4 audio streams (PCM 24bit 48KHz). Important note: As the sources used for this benchmark are 4:2:2 chrominance-sampled, the decoding hardware acceleration was limited. Other source formats gave significantly better results. We used these results as a lower-bound. 2) Streaming format configured to HEVEC 960X540 3Mbps 3) All streams were playing simultaneously. 4) Maximum CPU/GPU capacity was set to 85% of the actual maximum capacity. Storage Bandwidth To assure efficient streaming, the streaming server has to read from the storage using a UNC protocol from the storage at a rate of at least 60fps. Network Streaming Bandwidth For smooth playback, the default stream (720p) requires 4.5Mb/sec on the download direction (from the server to the workstation). Two concurrent streams (for example, two videos layered one on top of the other) will require about twice as much (~9Mb/sec) and so on. However, the stream bitrate and resolution are configurable. The bitrates given below are average bitrates required by the stream while playing, sorted by the stream resolution (see Bandwidth column below). However, since the NLE uses a play-ahead caching policy, the bandwidth required from the source to the target for smooth playback and scrubbing, is higher than the average stream bitrate (see Required Bandwidth column below). The association below of the configured resolution and the avg. streaming bandwidth is based on our best practices and experience with HVEC compression. That said, the bitrate and resolution may be configured independently by the system administrator. Streaming Avg. Bandwidth / Required Bandwidth / stream Resolution stream 1920x Mbps 12.0 Mbps 960x540/1080x Mbps 4.5 Mbps 704X Mbps 1.0 Mbps LTD.

8 Ports By default, edix uses the following ports: edix Server: 443 edix streaming: These ports are configurable via the administration portal. Installation & Configuration 1. Invoke as administrator: Setup will prompt for administrator privileges, since it opens the default ports (see Ports section above) on the local machine s firewall, and install the edix streaming services. 2. Set username, password and port: The streaming service account should have rights to access the storage and administrator privileges on the local machine. Use the Browse-button to select the appropriate user. 3. The installation is completed! LTD.

9 4. Login to the admin portal: Once the installation is over, admin will open to display the administration portal login page. You should use the default administrator credentials: User name: Password: ! 5. Change admin Password: Since it s your first login to the admin, a dialog will prompt you to replace the administrator s password. Note that a valid password must conform to several requirements. After the new password is set, a wizard will guide you through the configuration process. LTD.

10 6. Auto/Manual installation: First you ll set the configuration to be (mostly) automatic or manual. The automatic setup is much simpler, and allows remote-editing via the internet. The manual setup does not rely on the internet, and will require you to configure your DNS or host files 7. Auto Install: If you ll choose the automatic installation, the server s IP will be published via public DNS (e.g. if your account is ComapnyName, then your server URL will be CompanyName.xtrmx.com). 8. Set the Remote Storage Folder: The remote storage folder contains your remote media. Mind that this folder should be accessible both to the streaming server and to the rendering server The edix streaming server should be able to read from this folder in sufficient speed for your needs (as discussed in network streaming bandwidth section). LTD.

11 9. Set the Rendering Output Folder: The render server renders the output files into that folder. The folder should be provided as an absolute path (UNC or local path). In case the folder is not local, mind that it should be accessible to the rendering server. 10. All Done! Your edix Server is ready. LTD.

12 11. Manual Install: If you ll choose the manual installation, the servers URLs will be manually configured using your own DNS or host files. 12. Set the rendering Server: Make sure you ve successfully installed the rendering server before attempting to configure this step. See Render server installation section for more details. Provide the rendering server URL and port. Mind that the rendering server URL should be accessible to the edix streaming server: Map the rendering server IP to its URL either via the network s DNS or by the local hosts file. See Edit your host file section for more details about editing the hosts file. 13. Set the edix Server host name and port: Next, we ll configure the hostname and port for the edix streaming server. As a default hostname we've used the computer name. As a default port we used 443. The streaming server URL should be accessible from the rendering server, the edix workstations, and from the streaming server itself. Map the streaming server IP to its URL under the xtrmx.com domain (StreamingServerName.xtrmx.com ) either via the network s DNS or the local hosts file. See the Edit Your hosts file for more info about editing the hosts file. LTD.

13 Appendix 1: Add users Once your edix system is up and running, you can add more users. You already have the admin (with user name and the password that was set during the setup). To add more users: 1) Open the admin terminal: On the edix streaming machine s desktop, you ll find a shortcut to the admin portal ( Edix Server Admin ). Click it and the admin portal will open, prompt you to enter the admin credentials 2) Add new user: Click the Add User icon LTD.

14 3) Fill the new user details: User name: The user s would be used as a user-name (for login sake). First and last user name are optional. Admin: Use the admin-switch to grant administrator authorizations, which will allow the user to modify his settings (such as the video and audio configuration). See the edix user manual for further details. Password: The password must fulfill certain constraints (click the question mark near the password for more info), and it has to be repeated in the Retype password field, for verification. The Save option will be enabled once all the details are valid. 4) Editing / Removing users: If you wish to modify any of the user s settings, click the edit (pencil) icon for the relevant user Click the trash icon to delete a user. Only none-admin users can be deleted. LTD.

15 Appendix 2: Edit the hosts file The hosts file is used to resolve hosts names before DNS, by means of mapping URLs to ip address. The hosts file syntax is as follows: The first part will be the location to redirect the address to, the second part will be the address that you will want to redirect, and the third part (which is optional) is a comment. They can be separated by a space, but for ease of reading they are typically separated by one or two tabs. Suppose you want to access the URL edix.xtrmx.com which is located at ip , then you will add the following two entries in the host file: edix.xtrmx.com #edix server #edix server (SSL) To edit the host file, you'll have access it as an administrator. Here is how to do it on Windows 10.0 and MacOS: Edit host file on Windows Open the start menu and type Notepad. Right click the notepad icon to open notepad as an administrator LTD.

16 Once you ve done so, open up the following file using the File -> Open menu. The host file is located at c:\windows\system32\drivers\etc\hosts Once notepad is open you can edit the file. In the example below, the URL facebook.com is mapped to (which is probably not serving web pages, so don t expect it to work...). LTD.

17 Don t forget to save... Edit host file on Mac OS (Any version) Use the terminal as follows to edit your hosts file. LTD.

18 Again for the example sake we are redirecting the facebook.com URL to the IP. LTD.