
“Fluendo对视频解码过程和GStreamer框架的深入了解,使惠普通过我们的嵌入式设备系列提供了卓越的用户体验。 他们与AMD进行的工程师面对面讨论,是惠普嵌入式Linux操作系统的ThinPro能够运用更多的GPU功能的关键。”
John Robinson,
惠普精简客户端软件解决方案的研发经理
Fluendo Codec Pack利用了包含在ONEPLAY Codec Pack中的完整的插件集,并用新的与编码和流媒体相关的附加组件来补充它们。
Fluendo Codec Pack旨在满足这些OEM的要求,后者只需要将特定的多媒体插件集成到他们的硬件/软件解决方案中去。
为了满足我们的经销商要求,Fluendo提供了创建自定义Codec Pack的灵活性:他们可以选择具体的可以嵌入其平台的音频和/或视频插件,而不管其性质如何(PC,笔记本电脑,精简客户端,机顶盒......)。
Microsoft DirectShow应用程序编程接口(API)是一种针对Microsoft Windows的媒体流架构。我们的DirectShow到GStreamer过滤器允许我们的插件部署在基于Windows的环境中,无需GStreamer后端。因此,我们的过滤器会将Fluendo编解码包转换成独特的市场解决方案,能够在两种多媒体框架上均保证最受欢迎的音频和视频的专利合规性:DirectShow(Windows)和 GStreamer (Linux)。
Fluendo Codec Pack除了playblack元素,还包含一个能够编码和复合GStreamer元素的工具集合。
Fluendo Codec Pack是一套完整的GStreamer插件,这是当SoC(嵌入式系统)制造商、操作系统、浏览器引擎或播放器没有包括对这些格式的支持时,合法播放某些音频和视频所必需的。包含在Fluendo Codec Pack中的多媒体编解码器随其各自的专利许可证一同分发,这些许可证由最重要的多媒体专利持有人提供。
我们的音视频分离器包括必要的界面以保护业内领先的DRM系统中的内容(即:PlayReady, Widevine,Marlin)。
只要您的环境中(视频编辑应用程序、HTML5后端……)有GStreamer,Fluendo就可以轻松集成,Fluendo Codec Pack可以即装即用。
luendo Codec Pack包含所需的技术(合成器和分离器)创建合法的DVD解决方案,带来增强的多媒体体验。
Fluendo Codec Pack中包含的所有插件都是通过GStreamer框架构建并可用于0.1和1.X版本。只要它们有GStreamer后端,就能在Windows、Linux、OS X、iOS、Android环境中完美运行,我们的多媒体过滤器可以将Fluendo Codec Pack扩展到其他框架。
一旦Fluendo Codec Pack集成到OEM平台/设备中,我们为他们提供支持服务。支持服务包括在第一年的合同内。从那以后,OEM就可以自由选择续签年度支持,可以根据上一年的销售额,也可以根据固定费用支付。
Fluendo的支持团队将根据我们提供的服务水平协议(SLA) 根据提交的事件/问题/请求级别向客户保证回复。
Fluendo意识到,可能需要特定的开发,才能将Fluendo Codec Pack集成到某些特定的架构/平台中。 Fluendo经验丰富的多媒体工程团队与我们的客户合作,使集成过程变得轻松高效。
我们的产品为您的设备提供丰富而合法的多媒体体验。
自定义您需要的Fluendo Codec Pack。报告并仅为成功销售嵌入包的设备部分付费。 报告快速而简单,可通过我们的后台系统在线完成。
凭借十多年来在此多媒体框架基础上构建解决方案的经验,Fluendo可以帮助您改善GStreamer解决方案。Fluendo很自豪成为全球主要的GStreamer贡献者之一。
System on Chip
精简客户端
Set-top boxes
Desktops
我们产品的主要商业模式是“每单位特许权使用费”。我们根据产品和数量定价。
GStreamer is an open source multimedia framework mainly used to create media applications. The GStreamer framework is designed to make it easy to write applications that handle audio or video, or both. It uses plugins providing codecs and other functionalities. Visit our GStreamer page for more details.
FFMPEG | GSTREAMER | |
---|---|---|
Cross-platform support | FFmpeg cross-platform support is limited. Linux could be considered officially supported. However, other platforms builds (Windows, OS X, and Android) are maintained by volunteers. | GStreamer framework is fully compatible with all the major operating systems including Windows, MacOS, Android, OpenSolaris and Linux based distros like Ubuntu. |
Documentation and Support |
The official documentation is not clear and can
be quite confusing. Mailing list is active, but you must be very specific in your question. |
Really good tutorials and general
documentation. You can access a general API. Very active development mailing list, with very helpful members (even questions for beginners). |
Complexity |
It’s not easy for beginners to use and
implement. The API is huge, its use is often non-intuitive, and many important concepts are not explained clearly. |
Tutorials allow newbies to operate with basic
tools easily. GStreamer’s well defined architecture also allows to venture with more complex stuff without significant problems. |
Codec support | FFmpeg strength lies on its extensive list of supported codecs. It renders an active support for almost all the required codecs including lossless FFV1, lossy snow codec, WebM, FFVP8, VP9, HEVC, AAC and FAAC. Besides, FFmpeg also provides video streaming and web hosting capabilities. It supports popular media libraries such as libavcodec and libavformat. | It depends on how it was compiled; generally, every known format is supported for decoding, and a large number of formats is supported for encoding. MIDI playback is supported but depends on 3rd party software, so realistically it is only semi-supported on Linux. |
Filter support | A lot of filters of many kinds are available, from simple rotation and flipping to watermarking. | A lot of filters of many kinds are available, from simple rotation and flipping to watermarking, and even some exotic such as voice removal. |
Audio and video I/O | It doesn’t provide audio/video I/O and so you need other SDKs for this purpose. | Supports all known audio and video outputs and inputs, you will seldom need anything else. |
Framework redistributable size | It heavily depends on which codecs you want to support, (therefore) which libraries are included in the build. | Occupies larger storage space as compared to other frameworks. |
A codec is a device or computer program for encoding or decoding a digital data stream or signal. (codec is a portmanteau of coder-decoder). A codec encodes a data stream or a signal for transmission and storage, possibly in encrypted form, and the decoder function reverses the encoding for playback or editing. Codecs are used in videoconferencing, streaming media, and video editing applications.
Multimedia files (movies, music…) are huge, which means they are usually difficult to transfer over the network. To speed up downloads, codecs were built to encode, or shrink, a signal for transmission and then decode it for viewing or editing. Without codecs, downloads of video and audio would take three to five times longer than they do now.
There are hundreds of codecs in use out there, and you will need combinations that specifically play your files. There are codecs for audio and video compression, for streaming media over the internet, speech, video conferencing, playing MP3s, and screen capture. Selecting the right codec can depend on several factors. Target file size, output quality, and delivery method all factor in.
Some of the most popular codecs are:
Because there are so many codec choices, codec packs are a convenient option.
Fluendo Codec Pack is our complete set of audio and video encoders and decoders especially created for Enterprise. However, if you only require codecs for playback purposes, as an End User, ONEPLAY Codec Pack is the solution for you.
There’s wide extended confusion when customers/end users ask for certain codecs. Most of them really refer to containers’ formats instead of audio and video codecs.
A container or wrapper format is a metafile format whose specification describes how different elements of data and metadata coexist in a computer file. Containers "contain" the various components of a video: the stream of images, the sound, and anything else. For example, you could have multiple soundtracks and subtitles included in a video file, if the container format allows it. They’re easy to distinguish because they determine the extension of your video file. Popular container formats include MP4 (.mp4), AVI (.avi), QuickTime (.mov) and Matroska (.mkv).
According to the previous explanation, we have the following:
The different container formats all have different strengths and weaknesses, with certain formats preferred by certain content providers. Not all containers support all compression standards or allow for secondary features like subtitles and chapters. The container itself doesn’t affect the quality of the video directly, but it can limit the compression codecs available for use.
If you’re choosing a container format to use for an encoded video, you’ll want to pick one that has the right mix of supported compression codecs and features.