Contact Us
Feel free to ask any questions about our products and the solutions you can create with them. We are happy to help!
Note: Please use your corporate email address (not GMail, Outlook, etc.).
Note: Please use your corporate email address (not GMail, Outlook, etc.).
By using this form you agree with the nablet GmbH privacy policy.
Video recording, processing and normalization
nablet engines and technologies can be used in combination to fulfill the requirements of different video processing workflows. Read about real-world scenarios our customers use in their everyday work.
Multi-camera video recording
Around a football pitch, there are 8 SDI cameras. All the signals should be recorded into a predefined standard format for further processing and archiving. At different angles of the pitch, the overall loudness of fans' support is different, so the recorded content should be normalized.
Here come mediaEngine and Audio Gain Normalization elements to process the recording of each of the SDI signals to AVC Intra 100 MXF files.
Here come mediaEngine and Audio Gain Normalization elements to process the recording of each of the SDI signals to AVC Intra 100 MXF files.
Record NDI to storage and distribute the Master
The next scenario is a hockey workflow where the video is captured with NDI devices. All the NDI streams come to a director's mixer to define a master signal. All the NDIs should be recorded to MXF files for further archiving. The Master Signal should be streamed via SRT to a broadcast studio where the signal is distributed to the viewers. The Master Signal should be prepared for the fast delivery of highlights to mobile devices at the same time.
Here the mediaEngine is used as a transcoding component to convert the sources to the target format (MXF, SRT), and also Shrynk and HeighScreen are used to prepare content for mobile devices.
Here the mediaEngine is used as a transcoding component to convert the sources to the target format (MXF, SRT), and also Shrynk and HeighScreen are used to prepare content for mobile devices.
Basic Video Content Normalization
In a broadcast studio, you might have thousands of files provided to you from multiple sources. Some of the files might not fit the standards of your current workflow (e.g. NLE editor might not accept some files, or the original files are corrupted). So you set up a watch folder where you place all the original files dynamically and normalize them.
The normalization process uses the nablet MXF Analyzer that checks if each file in the folder matches your standard and if it doesn't, then remux and transcode the original file to the target format. Otherwise just moves the original file to the target storage for further processing.
The normalization process uses the nablet MXF Analyzer that checks if each file in the folder matches your standard and if it doesn't, then remux and transcode the original file to the target format. Otherwise just moves the original file to the target storage for further processing.
Advanced Normalization and Video Processing
An extended scenario includes more Elements. The original or transcoded files are processed by Shrynk and HeightScreen to prepare content for social networks and highlight reports of your events. The original video goes through the Quality Control process so you can be sure that viewers of the content will have the best possible experience.
Live Monitoring of Transcoding
During the transcoding with mediaEngine, you can monitor the processing remotely. You can use JSON and JPG outputs from mediaEngine instances to preview the content and monitor the overall performance of the process. For a start, you might use a web server available in mediaEngine.
