800-420-4459
Sign In
logo

  • In dealing with storage, does Brevity integrate with and use other 3rd party storage? Or does it only use its own proprietary storage?

    Brevity has been tested with a number of SANs for originating points and receiving zones. Since almost all SANs work similarly, using integration through a standard operating system, it is easy for us to use virtually any 3rd party storage. Brevity does provide its own storage but we also expect a pass-through to occur, so we are prepared for this as well. If you have a file system exposed through network permission, then we can certainly use it.
  • Is the Brevity file stored in the cloud or on our local network?

    Files can be stored in the Brevity cloud, in your private cloud, on your local network storage, or in a combination of these, in fact virtualizing all these storage areas from a user perspective. This is dependent upon your company’s needs, and our deployment team will work with you to determine the best fit for you.
  • If sending one file to twelve different locations, how many times is the Brevity warp file going to be transported from the send side?

    The warp file will only be sent once from the ingesting Brevity Engine.  As the file is received at the first destination it is in parallel sent to the next and so on; think of it as one pipe with spigots at each destination. The warp file remains temporarily on the scratch storage at the receiving location, until deleted when space is needed for other jobs. As the warp file could also copied to cloud storage (or any other persistent storage location and technology which is configurable to adapt to specific customers’ infrastructure),  any further requests from other users to process/transcode the file later on, will not incur in an additional ingest from source. This is accomplished by keeping track of the asset and warp file via a unique ID. In these instances, the cloud stored warp file will be transferred from persistent storage to destination  using the same pipeline protocol and processed as usual.
  • Does running a file through ImageWarp multiple times degrade the quality? If so, how many times can you run the file before it is noticeable?

    The Brevity Engine software is designed to avoid this type of quality degradation. Our system transports a proprietary mezzanine file created by our ImageWarp and DataWarp algorithms. This mezzanine file is created at the first ingestion of the video. As long as you have this original transport file, quality degradation is not a factor. The only way it could be a factor is if you’re doing multiple generations of the same file when doing meaningful pixel edits where you re-warp the files. Our tests show that you can do roughly six of those before you see any meaningful loss; this is well below the threshold of any workflow out there, especially with the mitigation we take on our software. Overall, we never re-compress unless the user specifically wants to accomplish that.
  • Is there any special Metadata handling?

    We never alter metadata and take steps to carefully save and preserve metadata as part of the content transport. Metadata is an integral frontline feature that we offer, as we are aware it is a very important part of any project. This whole paradigm may also extend to any partners you’re using. There are extensive provisions for metadata at all levels (individual clips, final products, franchise series you’re working on, and much more). Metadata is entered in a very common way and the system will hold on to those pieces throughout the course of project development. So when it is time to deliver the final project, there are a number of ways to do so.
  • Is there a way to look at a file after the transcode but before transmission?

    Brevity uses a mezzanine format that enables it to reach landing zones in multiple formats and to multiple destinations. For efficiency purposes and to avoid bottlenecks, we pass our only payload to all of those destinations. There is really no opportunity to evaluate files separate from the transcode. However, this should not pose an issue because if you want an alternate and completely lossless format on the other side, we can accommodate that. The file will arrive in your transcoded format, but also any other format you require. If you want to evaluate it that is what the lossless algorithm looks like before it has been transcoded.
  • How does Brevity handle versioning in its ImageWarp format, are corresponding software revisions required at the edge?

    The bit-stream itself contains versioning information. As we enhance algorithms, we make sure there is outward capability that builds into the stream. Our customers can avoid worrying about compatibility because your existing Brevity files and transport payloads will be unaffected. We take versions of your product. We don’t want customers to have to think about transporting, transport, or warp files; the system does it for them. You set up a project and we handle the versioning for your files so that you don’t have to be concerned with issues like sending files. With our project management software, your files go where they need to go in all the right formats. As versions take place in the project, they are accounted for and dealt with properly from the client’s perspective.
  • Does Brevity have the ability to run a transmission on the same pipeline as other transport companies?

    We have found other transport products to be bandwidth-hogs. In our first scenario test, we had a 100MB pipe and the other transport product ate up about 85MB of the bandwidth; they had no management system. In another scenario, the other transport product was given a percentage of the pipe and we played very well with them. Therefore, these companies must be managed in some way. In contrast, Brevity’s approach is very controlled and allows you to set the amount of bandwidth you want to allocate for transport.
  • Is the compression algorithm for DataWarp and ImageWarp spatial or temporal?

    It is spatial and temporal; Brevity does both.
  • What is the bit-to-bit comparison for a pre and post delivery (including header and metadata remaining intact)?

    The bit-for-bit comparison has been eyed extensively in the lab and it is absolute; there has not been a single file that is not bit-for-bit guaranteed. ImageWarp has been looked at outside of the lab and although some of the bits will be different, they are visually the same. With ImageWarp you gain speed enhancements at a high enough or better quality then some of the H.264s or other formats shipped around today. With DataWarp, the content or data is bit-for-bit loseless.
  • What extra functionality does Brevity offer for transcoding?

    Brevity has extensive functionality for all transcoding. We encompass anything you would expect from a professional-level suite such as de-interlacing, audio remapping, scaling, cropping, HD to SD down conversion, standards conversion, frame rate conversion, letterboxing, center-cut, time-code burn-in, and much more. If your company has a complex transcoding workflow or needs we can accommodate those as well.