In this new technology-driven era where consumers can access and enjoy media on a vast array of platforms, file-based quality control (QC) is critical to maintaining the best possible image and audio output. From a viewer standpoint, bad quality represents another reason to watch something else. From a business standpoint, bad quality can mean content gets rejected for not meeting published standards. To complicate matters further, distribution formats continue to evolve along with the quality standards to support them. QC workflows certainly have come a long way since the days when “golden eye” expert reviewers would sit all day watching content on a color calibrated grade one broadcast studio monitor obsessing over quality.

Broadcast, studio production, and live production facilities are transitioning from SDI to IP infrastructure. Much of this relies on ST 2110 which means that resolving problems relies on moving from point-to-point diagnosis to network-centric troubleshooting. Monitoring by exception is critical to easing this transition.

Introduction

Companies are ingesting more and more media into Non-linear Editing (NLE) systems like Avid Media Composer and Adobe Premiere Pro. Creative and editing talent can spend valuable time manually ingesting and creating viewing copies; automating the ingest process saves time and money. 

The Challenge:

Many companies are facing the challenge of managing a rapidly growing library of files and metadata that are valuable to the business. Therefore, it is important to protect these media assets and ensure long-term retrieval and secure files from unauthorized access, hack, or ransomware. 

Diagnosing and Resolving faults in an ST 2110 IP Video network requires comprehensive root-cause analysis. Monitoring by exception and a seamless transition to IP diagnostics tools can significantly improve your ability to do it. It does not matter whether a fault results from IP errors or from some type of deterioration to, or glitch in, the program essence elements like video, audio, or data. All that matters to a viewer, and thus to your business, is rapid resolution.

In our busy world of editing and post-production, we need to ensure that any final deliverable conforms to the different broadcast regulations that exist around the world. You may already be aware of these if you are currently producing file-based deliverables and are utilizing quality control software.

In today’s social media environment, anyone with a good idea for a show or live event—and the best live streaming software—can become a live video streaming pro. Just check out all the live videos and podcasts being shared on Facebook, YouTube, and other online and social media forums. These platforms not only enable live streaming to a world of connected devices, but they also give users the means to invite and entice followers to watch what they’re streaming.

So, if you’re looking to begin a streaming media initiative, such as a video podcast series, bear in mind that your videos will be seen on the same screens that viewers also use to watch the high-value, premium fare high-end media pros are producing.

In this third in our series of posts on IP diagnostics, we’ll discuss analyzing stream timing with a waveform monitor like the Telestream PRISM. As before, the details are covered in our technical guide. This is but a taste of why a Waveform Monitor is a valuable addition to your tool kit and some of the features that PRISM offers.

Delays, Paths, and Order

In an IP network with many devices, every packet can take a different path from source to destination. That means that the arrival times of 2 consecutive packets are not deterministic. Another cause of unpredictability is congestion within a switch or anywhere along a path that delays a packet’s ultimate arrival. These delays cause packets to get to a destination device in a different order than they were sent. They also cause excessive latency or its inverse, burstiness. ST2110-21 provides a Virtual Reciever Model which we discuss in the paper you can get using the link below. In this post, we will provide a glimpse into using PIT Histograms to Diagnose Timing.

The root cause of many IP network issues is packet jitter. Excessive packet jitter leads to buffer over- and under-flows which, in turn, result in dropped packets and stalled data flows. In what follows, we will describe these issues and some of the ways that waveform monitors diagnose packet jitter problems.