The configuration of an Etere Ingest Service is performed through the Etere Web Interface, where all service parameters are managed centrally.
When services are installed via Etere Update, the system automatically generates a corresponding XML configuration file for each service instance. By default, these XML files are created in:
C:\Program Files (x86)\Etere
After the initial configuration is completed and the service is properly applied, the XML files are automatically moved to the following directory:
C:\ProgramData\Etere\Ingest.Service
Each XML represents a single ingest service configuration and must not be edited manually, as all modifications are handled exclusively via the Web interface.
After logging into Etere Web with a user authorized to modify service settings, navigate to:
User → User Preferences → App Settings → Ingest
From this area, all installed ingest services are displayed in a structured tree view, organized by server node and service instance.
Each node represents a service running on a specific server and includes a unique communication port, used to identify the associated ingest channel.
This mapping allows precise identification of each ingest instance.
Each ingest service is configured through a set of structured parameter groups.
NB: The settings for the Scheduled ingest channel and the Station must be entered if you wish to use the service for scheduled recordings as well; otherwise, the service can only be used for manual recordings.
Defines the input signal configuration:
Manages interaction with external control systems and routing:
Defines output media format and technical parameters:
Once all parameters are defined, two actions are available:
Etere Ingest Services are configured through a structured web-based workflow that links each service instance to a dedicated configuration XML. All parameters are managed via the Web interface, ensuring centralized control, while the final configuration is applied through the Apply and Restart process, which synchronizes database settings and service runtime behavior.
Important Note:
Each service is designed to operate either in manual recording mode or in scheduled recording mode; concurrent use in both modes is not supported.
During the scheduling process, the system evaluates both the start time and the recording duration to identify any potential overlaps within the timeline. Should an overlap be detected, the system will generate a notification to inform the client, thereby helping to prevent possible recording conflicts or data loss.
Additional Note:
During the scheduling phase, user permissions and station assignments are strictly enforced. If a user is connected and operating under a specific station (e.g., Station 1), to which certain channels are assigned (e.g., Channel 1 and Channel 2), the user will be allowed to schedule recordings exclusively for that station.
To prevent configuration errors and ensure operational consistency, the system will display only the channels associated with the currently selected station, thereby restricting access to channels assigned to other stations.