To begin using the system, the user is required to input their data through the customer/admin page.
The callback functionality facilitates the transmission of system events to an application using an HTTP POST request. In this section, users can specify the URL information for the application. All relevant events occurring within the system are subsequently sent to the designated application. It is important for users to specify the applications they are utilizing to ensure seamless event transmission. For more information:
If an internal in-house system is to be utilized, it is necessary to introduce the servers to the system. This step allows for the incorporation of basic server information into the system. Erstream can provide input for any Origin Server which accepts MP4; FMP4; AAC.
Workers are the machines responsible for executing download, encoding, packaging, and upload operations within the system. If you intend to utilize an internal in-house system, it is necessary to introduce workers to the Erstream VMS system. There are two types of workers available: CPU and GPU. By default, VMS utilizes GPU workers, which offer enhanced processing capabilities.
Workers are equipped with multiple working logics to accommodate different operational strategies:
- Static: Templates in the system can be assigned different priority statuses, such as high, normal, or low (represented by priorities 1, 2, and 3, respectively). By selecting the static working strategy, you can determine the number of operations each priority level will handle. For example, if the workers can handle five transactions simultaneously, appropriate distribution should be configured to ensure efficient processing based on priorities.
- Pool: This working logic processes incoming content based on a first-in, first-out approach, disregarding the priority status defined in the templates. In this scenario, content received at similar times is processed in the order it enters the queue.
- MinAndPool: In certain cases, it may be desirable to set a lower limit for processing based on the priority status in the templates. This option allows for such customization. For instance, you can reserve one queue exclusively for high-priority content, ensuring that worker 1 consistently handles high-priority processing. Moreover, a lower limit can be set for each priority level, and the remaining number of transactions is distributed accordingly.
Configuring the appropriate working logic for workers enables efficient resource allocation and processing of content within the Erstream VMS system.
4. WORKER GROUPS
In the case of utilizing an internal in-house system, it is necessary to introduce worker groups to the Erstream VMS system. Worker groups are formed by assembling individual workers. Since workers can employ different working logics, they can be added to the group accordingly. By default, the worker group will be displayed in the menu as "VMS Group."
Worker groups offer flexibility in organizing and managing workers based on different strategies. Additionally, it is possible to incorporate region-based worker groups and workers into the system, allowing for more granular control and optimization of resource allocation.
Introducing worker groups to the system ensures efficient coordination and utilization of workers within the Erstream VMS system, enabling seamless handling of tasks and improved performance.
Customers who wish to utilize an FTP account must activate the FTP tab within the Erstream VMS system. This enables them to leverage FTP functionality for content management and transfer. Additionally, region-based FTP options are available, allowing customers to select FTP servers based on their geographical preferences or requirements.
Erstream VMS incorporates multiple storage options within its system. By default, the system selects the appropriate storage for the customer based on predefined criteria. However, if a customer wishes to send data to an additional storage, they must introduce their own storage to the system.
To add a new storage, the customer needs to specify the storage type and provide the necessary information within the Erstream VMS system. It is crucial to ensure accurate and valid storage information entry, as an incorrect input can result in failed ingest operations.
Introducing custom storages to the system grants customers the flexibility to manage and utilize their preferred storage solutions, expanding the capabilities and options available for data storage and management within the Erstream VMS system.
7. STORAGE GROUP
To effectively manage the storage options within the Erstream VMS system, the introduced storages should be organized into storage groups. This grouping enables streamlined content distribution and storage allocation.
The first ingest operation is typically directed to the VMS Storage, which serves as the primary storage location. Subsequently, if additional storage options are available within the storage group, the uploading process can continue onto these designated storages.
By utilizing storage groups, customers can ensure efficient storage utilization and seamless content management throughout the Erstream VMS system.
By selecting a Storage Group, corresponding Storage belonging to this group can be listed & managed.
8. ENCODE PROFILES
Erstream VMS includes a set of predefined encoding profiles. However, users have the flexibility to introduce their own custom encoding profiles if desired. These profiles need to be configured based on whether they are intended for CPU or GPU processing.
Users can define their own encoding profiles to align with their specific requirements and preferences. By customizing the encoding profiles, users can optimize the encoding process and tailor it to their hardware capabilities, whether utilizing CPU or GPU resources.
Configuring appropriate encode profiles allows for efficient and effective processing of content within the Erstream VMS system, ensuring optimal encoding results based on the available hardware resources.
During the creation of an Encode Profile in Erstream VMS, the Profile Type, whether CPU or GPU, is indeed set as part of the profile creation process. This allows users to specify the intended hardware for encoding operations. An example screen can be seen below.