Linux Transcoding Software ^HOT^
There is a good range of open source software available on the Linux platform for transcoding digital data. One application not featured in this article but is worthy of a mention is Transmageddon. This video transcoder is built using the pipeline-based multimedia framework, GStreamer. Transmageddon is in an early stage of development.
Linux Transcoding Software
This article highlights the finest open source transcoding applications for Linux. Individuals that are interested in making digital media available for playback on mobile phones, or make frequent use of Home Theatre software will find transcoding software to be invaluable. Transcoding helps to ensure there is universal access of multimedia content.
To provide an insight into the quality of software that is available, we have compiled a list of 9 of the finest transcoders. There is a mix of graphical and console based applications featured here. Hopefully, there will be something of interest for anyone wanting to transcode digital data.
When possible, Plex Media Server uses hardware acceleration for both decoding and encoding. Some formats are not compatible with hardware acceleration for decoding. In those cases, normal software decoding without hardware acceleration will automatically be used.
*The listed native system decoders/encoders are only used when they indicate that hardware acceleration is available. Otherwise, Plex uses its own bundled software libraries (libavcodec/x264) for maximum compatibility and quality.
Despite its free status, FFmpeg includes libavcodec, a codec library typically found in premium video conversion software. Use the libavformat audio/video mux and demux container, along with the libavfilter library for GStreamer filter graph enhancing and editing.
The Videomass video conversion tool belongs to a rare breed of FLOSS software or Free/Libre and Open Source Software. This resourceful, cross-platform converter helps you transcode videos to and from a large variety of formats.
You can run it on both 32-bit and 64-bit systems and push it to tweak the audio quality samples on conversion projects. This video converting software assists you with grayscaling, video rotation, subtitle encoding, and video scaling.
Cine Encoder aggregates the best video conversion and encoding library plugins for handling multimedia tasks on Linux. This open-source conversion software combines the ever-powerful FFmpeg with the MKVToolNix and MediaInfo libraries.
Noticing that HEVC files are software transcoding instead of hardware transcoding. As far as I know, Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 8 core, on an Intel board running Ubuntu Linux 18.04.2 & Emby Server 126.96.36.199 should have the ability to hardware transcode this. Everything else outside of HEVC hardware transcodes fine utilizing VAAPI. Both H.264 (AVC) & H.265 (HEVC) on VAAPI HD Graphics 530 are enabled in the Emby Server Dashboard. Is there anything you can see in the logs that might be causing this or remedies we might be able to try?
Been trying to make this work, but for me it is still unclear whether the pentium J4205 (Apollo lake) is fully suitable for hardware acceleration. As mentioned above, HEVC images are transcoded using software but the rest is successfully through hardware acceleration
The Jellyfin server can offload on the fly video transcoding by utilizing an integrated or discrete graphics card (GPU) suitable to accelerate this workloads very efficiently without straining your CPU.
This decision was made because Raspberry Pi is currently migrating to a V4L2 based hardware acceleration, which is already available in Jellyfin but does not support all features other hardware acceleration methods provide due to lacking support in FFmpeg. Jellyfin will fallback to software de/encoding for those usecases.
The hardware decoding of H.264 / AVC 10-bit (High 10 profile) video is not supported by any Intel, NVIDIA and AMD GPU. Jellyfin will always fallback to software decoding for it. Consider upgrading such video to H.265 / HEVC 10-bit (Main 10 profile).
On modern GPUs the peak throughput of video transcoding can be limited by the I/O speed of your hard drives. In this case, an SSD or RamDisk can be used for caching the transcoded temporary video segments.
AWS Elemental MediaConvert is a new file-based video transcoding service that provides a comprehensive suite of advanced transcoding features, with on-demand rates starting at $0.0075/minute. Read more.
Amazon Elastic Transcoder is designed to be easy to use. You can get started by using the AWS Management Console, the service API or the SDKs. System transcoding presets make it easy to get transcoding settings right the first time. We provide pre-defined presets to create media files that will play on a wide range of devices (like smartphones or tablets), as well as presets to create media files that are optimized for playback on a specific device (like the Amazon Kindle Fire HD or Apple iPod touch). You can also create segmented files and playlists for delivery using the HLS, Smooth, or MPEG-DASH protocol to compatible devices. Developers building applications that need transcoding can use the AWS SDKs for Java, .NET, Node.js, PHP, Python and Ruby, and the new AWS Command Line Interface.
Amazon Elastic Transcoder is designed to scale seamlessly with your media transcoding workload. Amazon Elastic Transcoder is architected to handle large volumes of media files and large file sizes. Transcoding pipelines enable you to perform multiple transcodes in parallel. Amazon Elastic Transcoder leverages other Amazon Web Services like Amazon S3, Amazon EC2, Amazon DynamoDB, Amazon Simple Workflow (SWF) and Amazon Simple Notification Service (SNS) to give scalability and reliability.
Amazon Elastic Transcoder uses a content duration-based pricing model: you pay based on the length of the output, in minutes, of the media you are transcoding. For example, if your video's transcoded output is 30 minutes in duration, you will pay for 30 minutes of transcoding. Similarly, if you create a 20 minute video clip from a 30 minute input file, you will pay for 20 minutes of transcoding. Alternately, if you are stitching together two 5 minute input files to create a single 10 minute output file, you will pay for 10 minutes of transcoding. With Amazon Elastic Transcoder, there are no minimum transcoding volumes, monthly commitments, or long term contracts.
Amazon Elastic Transcoder enables you to focus on your content rather than on managing transcoding software in a distributed cloud-based environment. The service takes care of scaling and operating the system, and manages the process of keeping codecs up to date. Combined with our service API and SDKs, this makes it easy for you to build media solutions that use Amazon Elastic Transcoder.
Amazon Elastic Transcoder provides an important media building block for creating end-to-end media solutions on AWS. For example, you can use Amazon Glacier to store master content, Amazon Elastic Transcoder to transcode masters to renditions for distribution stored in Amazon S3, stream these renditions at scale over the Internet using Amazon CloudFront, and monitor the health of your transcoding workflow using CloudWatch.
To use video transcoding workloads on Amazon ECS, register Amazon EC2 VT1 instances. After you registeredthese instances, you can run live and pre-rendered video transcoding workloads as taskson Amazon ECS. Amazon EC2 VT1 instances use Xilinx U30 media transcoding cards to accelerate liveand pre-rendered video transcoding workloads.
When creating a service or running a standalone task, you can use instancetype attributes when configuring task placement constraints. This ensuresthat the task is launched on the container instance that you specify. Doingso helps ensure that you use your resources effectively and that your tasksfor video transcoding workloads are on your VT1 instances. For moreinformation, see Amazon ECS task placement.
You configure a container to use the specific U30 card available on thehost container instance. You can do this by using thelinuxParameters parameter and specifying the devicedetails. For more information, see Task definition requirements.
Amazon ECS provides a sample repository that you can use to build an AMI forvideo transcoding workloads. This AMI comes with Xilinx U30 drivers. Youcan find the repository that contains Packer scripts on GitHub. For more information about Packer, see the Packer documentation.
To run video transcoding containers on Amazon ECS, your task definition must contain avideo transcoding application that uses the accelerated H.264/AVC and H.265/HEVCcodecs. You can build a container image by following the steps on the Xilinx GitHub.
The task definition must be specific to the instance type. The instance types are3xlarge, 6xlarge, and 24xlarge. You must configure a container to use specificXilinx U30 devices that are available on the host container instance. You can do sousing the linuxParameters parameter. The following table details thecards and device SoCs that are specific to each instance type.
In the context of a home NAS, many people buy these devices to act as home media servers. Running software such as Plex, transcoding lets the NAS serve media files to local network users and users connecting to the content over the internet.
A NAS is a busy device at the best of times. It might be handling file transfers, running backup software, and acting as a web server at the same time you want it to play movies on your TV. Transcoding is a CPU-heavy job, and if the NAS has to do it fast enough for real-time viewing, it will drop the ball on other tasks. Offloading the job to a dedicated hardware transcoder or (as is often the case) a GPU frees up the CPU to ensure everything else is taken care of without skipping a beat. 041b061a72