Managed and Instant Streams
Last updated
Last updated
Managed and Instant Streams are categorized in the Stream List, so you can easily distinguish them. Also, if you select Managed or Instant Stream and go to the Stream Monitoring screen, you can easily check it by the icon marked on the upper left of the OvenPlayer where the corresponding Stream is playing.
Stream Playback: You can play the stream through the embedded OvenPlayer after selecting the options, such as Output Stream, Playlist, Protocol, etc. on the left side of the Stream Monitoring screen.
Status: You can check the Ingress/Egress metadata and statistics of the stream.
URLs: You can see the Ingress/Egress URLs of the stream, and the available Ingress/Egress Protocols are displayed according to the OvenMediaEngine settings.
Supported Ingress Protocols: RTMP, WebRTC, WebRTC/TLS, WHIP, WHIP/TLS, SRT
Supported Egress Protocols: WebRTC, WebRTC/TLS, LLHLS, LLHLS/TLS, HLS
Recording: You can check the recording status of the stream.
Push Publishing: You can check the Push Publishing status that transmits the stream to other platforms.
Dump: You can check the LLHLS Dump status of the stream.
Ingress: You can check the Ingress metadata and statistics such as Protocol, Source location, Track, Input Traffic, etc.
Egress: You can check the Egress metadata and statistics such as Output Profile, Track, Output Traffic, etc.
If multiple Output Profiles are configured in OvenMediaEngine, it can work as ABR.
Depending on the playback options you have chosen, such as Output Stream or Playlist (depending on OvenMediaEngine settings), Protocol selection (LLHLS or WebRTC), Certificate availability (TLS or Non-TLS), etc., a Playback URL of the Stream is displayed. You can play it through OvenPlayer or an external player using the Playback URL.
Ingress URL: You can check the input stream URL address that is activated and available for use in OvenMediaEngine
Egress URL: You can see the stream playback URL address for each Output Stream, Playlist, and Protocol set in OvenMediaEngine.
You can easily copy the URL by clicking the Copy icon at the end of each URL.
The selected Playback URL can be played using OvenPlayer included in OvenMediaEngine Enterprise, but if playback fails, the system automatically provides the cause and solution at the bottom of OvenPlayer. If you encounter any problems, please refer to the information.
Recording is a function that records when the stream is Live. When the stream is recording, you can see at a glance that it is recording through the Recording marking in the Stream List.
In addition, you can use and control Recording using the API.
Recording Settings Guide: https://airensoft.gitbook.io/ovenmediaengine/recording
You can check the detailed recording status through the Recording tab in Stream Monitoring and control Recording using the Start/Stop Recording function.
Id: Unique ID to identify the recording task.
Output Stream Name: Output stream name to record.
Variant Names: Array of track names to record.
Interval: Recording time per file (milliseconds). Not allowed to use with the schedule.
Schedule: Same as Crontab syntax '10 */1 *' means to output the recorded file every 10 minutes of the hour. Not allowed to use with Interval.
Segmentation Rule: Define the policy for continuous or discontinuous timestamps in divided recorded files.
continuity: The timestamp of recorded files is continuous.
discontinuity (default): The timestamp starts anew for each recorded file.
Metadata: Metadata is used by the Record Delivery feature. An example of Record Delivery settings is shown below.
aws_access_key_id='xxx', aws_secret_access_key='xxx', endpoint='https://object.storage.com', region='us-east-1', bucket_name='bucket_name', object_dir='my/vod/path/',delete='true'
Push Publishing is a function that retransmits a stream ingested into OvenMediaEngine Enterprise to other platforms. While the stream is being Push Published, you can see the Push Publishing mark in the Stream List to know at a glance that it is being restreamed.
Also, you can use and control Push Publishing using the API.
Push Publishing Settings Guide: https://airensoft.gitbook.io/ovenmediaengine/recording
Push Publishing API Guide: https://airensoft.gitbook.io/ovenmediaengine/rest-api/v1/virtualhost/application/push
You can check the detailed re-streaming status through the Push tab in Stream Monitoring and control pushes using the Start/Stop Push Publishing function.
Id: Unique ID to identify the task.
Output Stream Name: Output stream name to Push Publishing.
Variant Names: Array of track names to push publish. This value is <Encodes> [Video|Audio|Data] <Name> in the <OutputProfile> setting. If empty, all tracks will be sent.
Protocol: Protocol to Push Publishing.
URL: Address of destination (Stream URL).
Stream Key: RTMP stream key. Not used in SRT and MPEG2-TS.
(Preparing image)
(LL)-HLS Dump is a feature that dumps the .m3u8 and all track segments when the stream is played back as (LL)-HLS, allowing you to provide the file to VoD immediately up to the dumped point, while Live. You can check the detailed (LL)-HLS Dump status through the Dump tab on the Stream Monitor page while the stream is being dumped.
In addition, you can use and control (LL)-HLS Dump using the API.
LLHLS Dump Settings Guide: https://airensoft.gitbook.io/ovenmediaengine/streaming/low-latency-hls#dump
You can check the detailed (LL)-HLS Dump status through the Dump tab in Stream Monitoring and control the Dump using the Start/Stop (LL)-HLS Dump function.
Id: ID for this API request.
Output Stream Name: The name of the Output Stream created with <OutputProfile>.
Playlists: Dump the Master Playlist set in <outputPath>. It must be entered in Json array format, and multiple Playlists can be specified.
Output Path: Directory path to output. The directory must be writable by the OvenMediaEngine process. OvenMediaEngine will create the directory if it doesn't exist.
Info File: This is the name of the DB file in which the information of the dumped files is updated. If this value is not provided, no file is created. An error occurs if a file with the same name exists.
User Data: If <infoFile> is specified, this data is written to <infoFile>. Does not work if <infoFile> is not specified.
