Item Code: CoralPipe
- CoralPipe solves your transport problems by acting as an error correcting protocol gateway. It leverages the new RIST error correction protocol standard with sophisticated distribution options.
- CoralPipe/Sync does for data files what CorelPipe does for streams. It is our cloud based backup and file replication service.
CoralPipe solves your transport problems by acting as an error correcting protocol gateway. It combines the new RIST error correction protocol standard with sophisticated distribution options. It also supports SRT, so that it can serve as the cloud transit point for all your streams. CoralPipe provides unlimited RIST-to-RIST based error correcting architecture. It’s geared to transport live streams with speed, fidelity and security, from remote to studio, studio to CDN or even from distribution point to end user viewer. At the remote side, it can also utilize the small hardware form factors of CoralMini to transport live streams to the CoralPipe in your NOC or cloud. CoralPipe Live can time-synchronize multiple sources, enabling true remote collaborative performances. It supports encryption even to the end-user-viewer.
The function of RIST is to ensure a media stream (or a set of multiplexed streams) which traverse(s) the public Internet with accuracy and efficiency, without adding jitter, while correcting the stream at the receiving end through its re-request mechanism.
The RIST processes provide an automatic re-request mechanism for dropped, corrupted or mis-ordered packets, and a mechanism to release each packet at the destination side based upon a relative timestamp. This latter process ensures that RIST adds no jitter.
There are a number of scenarios regarding RIST mode, additional senders and receivers, and network routing.
The two RIST modes are UDP, in which RIST is accessed by the operating system as a port, and tunneled. CoralPipe had implemented advanced functionality in the form of a layer on top of the RIST protocol which further allows:
- A sender can send one or multiple streams to multiple receivers.
- Multiple senders can send multiple streams to a single receiver.
- When sending multiple streams, each stream receives an arbitrary ID number, so that it can be properly identified at the receiving end.
It will be helpful to know, when you work with RIST that:
- The sender is called the RIST client.
- The receiver is called the RIST server. This can be confusing to some, so our documentation uses "sender" and "receiver" as much as possible.
- Where you have a sender/receiver combination with multiple Internet providers, you may use both paths. You may split the stream along both paths for speed, or duplicate it for redundancy.
CoralPipe/Sync does for data files what CorelPipe does for streams. It is our cloud based backup and file replication service. It uses the same general concept as ultra expensive products with a few major differences that improve reliability and efficiency. It takes a "cloud-centric" approach: rather than a file block-based method to check for errors, checking packet by packet. This catches (and repairs) network (i.e., Internet) reproduction errors sooner, and "smoothes" the traffic that it sends using the new RIST error correcting protocol standard. CoralPipe/Sync analyzes files of equal name and only transmits what is missing or changed.
You'll also find the installers for the client programs (Microsoft® Windows™ Apple® OS X® and others on the installer ISO.
How RIST Error Correction Works
RIST stands for Reliable Internet Streaming Transfer protocol. Its reason for being is that the Internet is a patchwork of equipment of constantly changing routes of variable quality. Internet packet loss normally runs somewhere between .01% and 1% on even the best quality networks.
To avoid these losses, important protocols such as mail, worldwide web and others rely on the tcp protocol. It provides a mechanism for confirmation that each packet was received. But this adds a huge overhead in messaging, and it automatically cuts speed severely at the very first error. HLS/DASH browser hosted videos try to solve this by requesting very small chunks of media and storing them in a fairly large buffer.
The alternative is the udp protocol, which RIST uses. The sender shoots out the packets as fast as it can without waiting for confirmation. There is no confirmation, and packets can be lost. But RIST also adds an error correction process. RIST tags each packet with a sequence number and a time stamp. The receiver checks that it has every number in the sequence. If it skips one, it tells the sender to re-send it, even as additional packets arrive -- it never stops. DenzTV’s implementation of RIST additionally leverages the specification to ensure proper time synchronization of the streams and jitter control. This is especially important when moving large numbers of h.264 (or other) encoded streams over the Internet.
Given a short buffer time, the receiver has time to insert a resent missing packet before handing it off to a viewer or writing it to file. RIST therefore is the fastest and most efficient way to copy files over the Internet.