Syndicate
      Back to home
      1. Knowledge Base
      2. Distribute
      3. Syndicate

      Imagen Live Connect đź“•

      Connect your live-streamed media to Imagen, capturing every moment for instant clips and bespoke post-processing

      Introductionđź“•

      Configuration⚡

      Supported SRT formatsđź“„

      How it works 👩‍🏫]]

      Live Connect API đź“„

      What Next 🤔

       

      đź’ˇ Pro tip: Imagen live connect requires a license. Your account manager will be happy to help with this

       

      Introduction 

      Imagen offers the option to display and ingest live streams. Platform users may clip from live video, annotate media and timeshift (jump back through the feed). Imagen treats a live Stream as a piece of media, encoding a web proxy on the fly and creating a growing file.

      The live streaming functionality processes streams up to 5Mbps (not full HD) and creates a 1Mbps version in real-time, from which users can make clips. After the event has ended, Imagen will re-encode the file to the platform's proxy quality.

      Live streaming formerly relied on manual scheduling by our Client Services team. This new feature puts you in control.  

      Can I still use RTMP (Real-Time Messaging Protocol Stream)?

      Yes. It is possible to use both RTMP and SRT, although SRT is far more reliable, faster and more secure. 

      đź’ˇPro tip: Check out the SRT alliance for further info on the benefits of this protocol.


      Configuration

      Imagen captures your live streams using our scalable server farm, allowing you to create clips on the fly and choose a workflow for post-production.

       

      To use a passphrase, simply add it to the end of the SRT URL as demonstrated below. Please keep this in mind that this must be alphanumeric and between 10 and 79 characters

      Url:

      This is the URL from which the stream will originate. 

      srt://[ip address or DNS]:[port]?mode=listener

      Example:

      srt://somelivestream.com:9999?mode=listener

      Passphrase

      srt://somelivestream.com:9999?mode=listener&passphrase={Passphrase goes here}

      Passphrase Example:

      eyJib2R5Ijp7Im1lZGlhSUQiOjY2MSwidXNlcklEIjoiNTEiLCJGUUROIjoiZGV2dGVzdGltYWdlbi5pbWFnZW5jbG91ZC5jb20iLCJ0aW1lc3RhbXAiOiIyMDIyLTExLTMwIDE3OjA1OjQ1In0sImhtYWMiOiJ2TXg2MkxvVXB1Z25wM25QckhjbVpHWFlZSGdiMktmN0FiMGVxM2tIQlFrIiwiaG1hYzIiOiIzZG9TVHJ2b3VnczlDWllSeVZtM21GWGdPMWxYZEhNWVFXV1c1V2hCSUE0In0

       


      Supported SRT formats

      SRT fully supports FFMPEG so the supported formats are the same as any other video on the platform. Check out our supported formats page for more info. 

      How it works 

      Now that your record has been created, Imagen will connect your new media object to the incoming SRT stream.

      SRT is an open-source protocol that allows users to stream video and audio packets of information with AES encryption. The stream parameters, such as frame size, frame rate, and sample rate, will remain the same as the stream output. SRT is particularly effective on slower networks, as it adds a configurable degree of latency to the stream. This means that two SRT endpoints can receive, acknowledge, and resend packets of data that may have been lost on the slower network.

      The following are two ways that devices can initiate the connection. They do not have any bearing on how data is transferred. each device can be configured to be a caller or listener.

      Listener Mode

      By setting the device to wait for the request to start. The listener device needs to know that it should listen to the SRT stream on a specific port.

      Caller Mode

      This mode sets the device to initiate the connection of the SRT stream. 

      Live connect API

      Resource URL

      PUT, to create a stream

      https://{Your Imagen URL}/iweb/v1/live/123456 

      Where 123456 is the media object ID

      POST, to modify a stream

      https://{Your Imagen URL}/iweb/v1/live/123456

      Where 123456 is the media object ID

      Resource Information

      Response formats XML JSON
      Requires authentication? Yes
      Required scope(s) createJobs

       

       

      Required JSON Body

      ALL times in UTC. UNIX timestamp in json for start and end time
      • Stream title
      • stream URL. (no validation just a string)
      • start time (validation already on farmer, pass through errors)
      • end time. (validation already on farmer, pass through errors)
      • workflow (no validation just a string)

      What Next

      As a workflow must be chosen before the stream begins, it may be worth looking at our workflows section if you are unfamiliar with or unsure which to choose. The workflow will 

      handle post-processing of your live stream