Skip to end of banner
Go to start of banner

How live service works

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

  1. Register IMS on the CMS server, 4DRS/4DML instance, and 4DPD/4DDM. Upload an IMS Excel file containing camera group information, channel information, video/audio information, and adaptive streaming information in the venue environment to the IMS Instance.

  2. It takes the video data from the set and delivers it to the PostSd PC. Click the Refresh button to load the IMS information from the Preference - Streaming tab of 4DPD or 4DDM. Then, when the image is connected in 4DPD, the camera image data compressed by HEVC (H.265) is transmitted from the VPd PC to the PostSd PC using TCP communication.

  3. The AJA HELO equipment receives an external signal (A/V source) from the SDI of MMS.

  4. The PostSd PC receives an external signal (A/V source) from the LAN of AJA HELO.

  5. The Audio Out information is converted to AAC compression form and delivered as 4DPD.

  6. A/V Sync and Position Swipe are the steps. A/V Sync is adjusted through Test Live Streaming before the actual Live Streaming, and Position Swipe delivers Position Swipe information to the PostSd PC when connected from 4DPD based on the pts file, which is 4DDM's calibration data.

  7. The PostSd PC sends the image data to the AWS 4DRS instance with SEI (Position Swipe Data, MultiView Data) for every frame.

  8. 4DML performs the recoding of video and audio streams entered into the 4DRS.

  9. 4Convert media information generated in DML into Transcoding / Segmenting / Making Playlist and store it in AWS Media Store. Master/Media Playlist and Media Segments exist in the form of Video (GOP 1 or GOP30), Audio, and Meta Data.

10. A playlist encoded in UTF-3 encoding of the m8u file is created and delivered to the CMS. UTF-8 encoding is a method that is often used in formats for streaming.

11. Transfer the contents list of the CMS to the Mobil APP or Web Player. The Contents List consists of a Master Playlist or a Media Playlist.

12. Playlist (m3u8) & segment information stored in AWS Media Store is delivered to Cloud Front.

13. Use HTTP Protocol to deliver to Mobile 4DHLS SDK or Web Player.

14. Users watch 4DLive videos through mobile or web players.

  • No labels