How to Choose an Enterprise Video Encoder
I’ve been spending a lot of time with enterprise encoders lately, 这些昂贵, mythical beasts that input 和 transcode multiple files complete (in some cases) with quality checks, 适合自己的元数据, 还有字幕. 这包括两个评论 基本的服务器 和 Telestream剧集引擎)和在 流媒体东部 on choosing an enterprise-class video encoder.
While the most obvious benefit of enterprise encoders is throughput -- typically via either dedicated hardware or server farm operation -- many other factors dictate whether or not you need to step up to an enterprise system. These include the need for multiple-format closed captioning or metadata packages, API-level integration with content management 和 web publishing systems, or access to features 如 quality control or encryption. Most enterprise systems can also ensure failover protection, so if one encoding station goes down, 继续编码.
在选择企业编码器时, the first choice is between workflow system 和 high-volume encoder. While all enterprise systems offer API-level 和 watch folder integration, 高容量的编码器, 如 索伦森挤压服务器, 基本的服务器, Telestream剧集引擎, are primarily encoding engines that quickly crunch through the files you send them for delivery to a folder or remote FTP site.
In contrast, workflow systems 如 Telestream有利 和 Rhozet工作流系统 (WFS) build intelligence into the encoding workflow. 例如, they can sense if an incoming file is SD or HD or 4:3 or 16:9, 和y can apply a different encoding preset based on this 信息. They can also perform post-encoding quality control checks 和 kick out a nonconforming file, or even re-encode at a higher data rate to ensure quality. While 高容量的编码器 can access third-party quality control programs, typically it’s via watch folder operation, so operation 和 reporting isn’t so well-integrated. The downside of workflow systems is cost; they typically require a separate workflow module on top of the encoding module, with quality control an added cost whether via an integrated option or third-party product.
Beyond the workflow versus high-volume encoder decision, you should next focus on issues 如 metadata 和 closed-captioning. In particular, the latter is a major distinction between the various offerings. Most enterprise encoders can pass-through EIA-608 (Line 21) or EIA-708 closed-captioning to MPEG-2 encoded transport streams, but few can repurpose these inputs for playback on Flash, iOS设备, 还有其他常见的目标, which is becoming increasingly important.
Workgroup operation is another distinguishing factor. Most enterprise encoding systems are black boxes from the end user’s perspective, with presets created 和 operation controlled centrally by an administrator. 在一些商店, it might be better to have individual encoders on some desktops with access to high-volume encoding when needed; this is one of the key benefits of the clustering capabilities found in the Telestream Episode line of products or 紧缩的桌面 和挤压服务器.
Another related consideration is the robustness of server-farm operation. Can a single point of failure bring the entire system down, or can the system work around any failures? If so, what does this functionality cost? For some operations, this feature will be the most important product differentiator.
If you’re just starting out your search, consider watching my 流媒体东部 session, 或者至少 下载简报. Also, you might search StreamingMedia.com for reviews of your c和idate systems. I should be adding to the list all year.
This article first appeared in the June/July 2012 issue of 流媒体 under the title "Enterprise Encoding: Time to Move Up?"
相关文章
硬件? 软件? 工作流系统? 各自的优势是什么? For those not sure where to start, look here first.
9月11日
While Episode Engine is a solid st和alone enterprise encoder, a few caveats keep it from taking the top spot.
2012年6月6日
如果你需要一个加速H的工具.264 encoding, 基本的服务器 should be on the top of your list.
4月13日
在艰难的开始之后, Telestream is back on track; Episode Pro is now free of the problems that plagued Pro 6.0.
2011.06