Search the Community

NAS: Synology DS224+, DSM 7.2.2-72806 Update 2 Emby: 4.8.10.0 with Premiere Enable hardware acceleration when available: Advanced But it is blank under "Preferred Hardware Decoders/Encoders I use this way to install Emby https://mariushosting.com/how-to-install-emby-with-hardware-transcoding-on-your-synology-nas/ How could I use hardware transcoding? hardware_detection-63868526968.txt

I was trying to get transcoding working on my emby server and it seems like there is lacking info on how to do it or I could just be a dumbass, but I have been following this (https://emby.media/support/articles/Hardware-Acceleration-Overview.html) and I got the .m files but at this point, I don't know what to do with them to enable the hardware acceleration if anyone has a windows guide or can help me that would be cool. the only things I can find are for docker and other programs.

Hi All, I have mostly made posts moaning about how stuff doesn't work right/the way I want to, but I'm going to give back to the community today! For the TL;DR skip down a few paragraphs, just me venting my woes I go into how I got hardware acceleration to work when it wasn't and everything said it should have been on an Ubuntu LXC container I originally built a FreeNAS machine, on which I planned to store loads of stuff including media, and saw that it had media player plugins. I didn't think too much of it at the time (except I didn't want to use Plex because my experience with it showed that it wasted resources/was the 'dummy' version) so I specced out my server and I built it. I chose a Sky Lake/Kaby Lake cpu for a number of reasons, but one of them was the iGPU. I tried using an Emby plugin but that didn't work (now know it's a whole .NET issue with FreeBSD) and then tried a Docker container of Emby - worked fine, but no hardware acceleration. I wasn't sure why, but I knew I needed more power in the server for the transcoding and other stuff I was using it for so I got a Kaby Lake Xeon cpu, making sure to get one with an iGPU, and kept on plugging away. To cut to the chase: - found out I needed to pass /dev/dri to docker - found out I needed VAAPI to get use of the gpu, but FreeNAS did not support it so it would need to be in a VM and FreeNAS was going through lots of changes - looked around for a few other operating systems that could be used for my purposes, tried OMV - it didn't like ZFS - landed on Proxmox, perfect for my needs - can spin up debian/ubuntu LXC containers easy peasy while passing through whatever I want from the root OS & can make VMs for other OS'/things I want more secure - found out that my motherboard had the C232 chipset & I needed the C236 chipset to use the iGPU - Finally bought the right motherboard Honestly, you would think I had done absolutely no research! But a lot of this was new to me and I didn't realize what I would be using the machine for (didn't know how much use I could get out of Emby per se - I already had an HDHomeRun and Apple TVs...). So I swapped in the right motherboard (plus I got some more SATA ports - gonna be cloning my zpool later to a much larger one w/ more redundancy since I'm using the machine for work too now) and went about making sure that dev/dri and fb0 were passed through to the Emby LXC container. *****Skip to Here***** At this point I double checked that everything was being passed through to the container (eg lspci) & went through the Emby documentation (they state that it Emby should have all the drivers that it needs built in, e.g. their own FFmpeg build). However, when I would play a file that was a direct feed it played fine, but when I tried playing a 4K HVEC or 9/10Bit/VP9/VP10 whatever they actually decided to call that, the video would just load and never start. I went into the console and VAAPI was indeed installed and showed that it was able to decode/encode the appropriate files for my cpu. Checked the log - it looked like FFmpeg was doing it's thing and transcoding the file writing stuff to the temp folder and including a transcoding rate (e.g. at one point it said it was transcoding at 66.6 x frames ). I was about to post on the forum, but I really really really have been wanting to get this working. So I looked around and I found the following site, or rather series of files from the VAAPI sites: https://github.com/intel/media-driver The genesis before that link was basically that VA API needed some extra libraries/intel media SDK to operate depending on the OS/CPU. So that link is for an addition driver that has links to two other libraries that are needed first (libva & GmmLib) along with their dependencies/reqs to build them. Follow the links and cit clone those libraries over to a build directory, make them and install them. For less experienced people the GmmLib instructions are less clear: after git clone GmmLib, make a build directory for cmake & change into it you issue the cmake command with '-DCMAKE_BUILD_TYPE=Release', the site just shows you the possible options. I left out the -DARCH=64 bit because from what I saw on the internet others didn't use it, but you DO need to reference a cmake build file for the command. That is in the root folder of the build folder you made. so either add '..' at the end or '/wherever you git cloned to/gmmlib' to the end of the cmake command and it will run. Then you do the make -j8 command followed by the make install command. Once those two guys are added I git cloned the media-driver bit in, followed the instructions, restarted the container and honestly didn't expect anything to have changed. But hardware transcoding started working like a charm! I do NOT know if it was a combination of those libraries, if it was a dependency of libraries (or maybe just me having to reset the BMC a bunch of times b/c my fan control script was acting up, but I highly doubt that's what it was) but after the above everything worked. As a final note, I don't think this is a shortcoming of the Emby team. As far as I can tell people are using hardware transcoding via the VAAPI files Emby installs just fine. Maybe it had to do with the specifics of my case - Emby running in an LXC container, the LXC container running inside of Proxmox, the fact that because I have IPMI the BMC has it's own video device that are seen in the OS'. I'm just happy I got it to work (maybe can help the Emby team do some investigating) & hope this can help others save some time. Cheers!

Trying to get HW Acceleration to work properly on my setup. I have a workstation running Windows 10 with Dual Xeon E5-2630 v3, NVIDIA Quadro P5000, and 64 GB RAM. I have looked through a few of the topics on this and some of the other users previous problems and have not been able to figure this out. I have attached a couple of logs that I have seen asked for in other threads already. From what I can see, the ffmpeg log says it is using the GPU, but when I am actively watching something and I check the usage on my computer and it has 0% utilization on the GPU with 35% utilization on the CPU with nothing else running other than the one video I am streaming so I know that's coming from the transcoding. ffmpeg-transcode-0fb17f84-9720-4248-a020-beb597a22fd6_1.txt hardware_detection-63729229044.txt

For inf, I have solved an issue with .ts format files recorded from broadcasts and saved on a NAS, played through emby on a Windows 10 pc to a chromecast. I set up hardware acceleration using an Nvidia card but only direct play happened, which stuttered and then failed. Solution was to transfer files and library pointers to the pc, after which the Nvidia kicked in. Hope that helps someone. Much better for recording than Plex, btw.

Hi, the Premiere webpage and feature matrix don't explicitely say if we need a premiere licence to activate the Hardware Transcoding (GPU) feature of server. Is it the case? Where can we find ALL the specifications of Premiere licence? Thank you Moreje

Hi, i will thank you for this great software it´s amazing. Now i have one little question. Will it be possible to use the GPU for transcoding (like Intel Quicksync) in the Webplayer? I know Mediabrowser Server 3 uses ffmpeg. I test with ffmpeg standalone at it can use quicksync to transcode. How could i turn this on in the MBS 3? It will be greate for all having a smal HTPC mit a CPU that allows this feature. I look forward to your response :-)

hi guys, I'm a user of plex and video station on synology, I'm testing emby and it works great ! I don't understand how video can stream without need of transcoding VS plex and emby but that not the point. during my tests, I purchased monthly premiere license to test material acceleration : a transcode consume 98% of my CPU, now with HA it consume 28% but, I have now transcode buffer problem : without material acceleration, transcode buffered 10/15 seconds, the video can be streamed but CPU goes to 98% with material acceleration, transcode buffered 3 seconds every 3 seconds so the video freezes every 2 seconds but CPU goes to 28/30% I use a mkv file with pgs subs to do a stress test, I want to test emby in every case before buying a full premiere license for many users but if one user cause 90% of CPU, others cannot use it and my license is useless. why material acceleration causes that ? emby plays transcoded temp files faster than ffmpeg created it. can someone explain me why and how to solve it please ? thank you synology DS916+ DSM 6.2-23824 Update 6 Intel® Pentium® CPU N3710 @ 1.60GHz emby 4.1.1.0 synology package behind synology ngynx chrome 74.0.3729.131 64 bits volume : 4x SEAGATE ST2000DM006-2DM164 7,2k SHR RAID here are my full logs hardware acceleration ON vs OFF HA_OFF.zip HA_ON.zip rundiags_20190510T135747UTC.log

This is a continuation from another thread as I thought it might be of general interest as there's not much real use case information about the Apple T2 chip and its role in hardware acceleration for their 2018 models. First, I'm an under 24 hours Emby user and I paid for my initial month of Premier membership not because I intend to use most of the services; I know I won't, but rather that I appreciate the time and effort it takes to keep something like Emby afloat. Hopefully the month will go well so that I can move to a yearly subscription. As mentioned in another post I'm a long time Plex user who's now a refugee after finding their new direction not one I wish to follow. So far every thing has gone unusually well. I'm sure something will come up. It always does; its the nature of the beast. I've recently put a 2018 Mac mini, MacMini8,1 with an 3.0GHz 6 Core Intel Core i5 Processor, 512 GB SSD and 16GB RAM running macOS Mojave 10.14.2 into service running Emby Server 4.0 24x7 in the background. It'll also be my primary desktop replacing a 2015 13" MacBook Pro with a buit-to -order i7 that wasn't cutting it as far as transcoding x264 files to x265 using HandBreak was concerned. It was used in the closed "clamshell" position attached to a 27 inch monitor, external trackpad, etc. etc. so the transition on my desk is almost painless. I also have a 2012 15" Macbook Pro 16GB RAM, modified with a 500GB SSD that never leaves the desk (too heavy) and has been my Plex server and does general utilities plus downloading/uploading and file transcoding as it was faster to transcode than the 2015. I archive all the video files I wish to keep initially to external drives, and then to 25GB BluRay disks as I spend part of the time in other lands. With Apple extending the T2 chip previously only on their 2017 Pro model to all their 2018 Mac line, I thought I'd share my initial impressions on how it has changed my transcoding workflow. The T2 chip, although primarily designed for security purposes, including continuously encrypting and decrypting data, is being used for additional purposes. One is acting as a digital to audio processor that makes a noticeable difference to my externally powered desktop speakers which I thought already sounded quite good. The T2 also provides hardware acceleration to applications using Apple's HEVC_VideoToolBox codec. Example of tests performed with a base line 1.14GB 720p x264 video file: 2012 MacBook Pro using HandBreak: 296 MB x265 file & 75 minutes to completion. 2018 i5 Mac mini using HandBreak: 295.4 MB x265 & 41:19 minutes with processor load of 97%. Not having seen any proof that the T2 chip was involved I installed ffmpeg 4.1 using HomeBrew and then the GUI for ffmpeg, ff·Works,found at http://www.ffworks.net. At that point I hadn't realized how few variables the Apple encoder had as there are only 2 that you can move around to get the best combination of quality versus file size. 2018 i5 Mac mini using ffMPEG and T2 hardware acceleration: 407.1MB and 3:57 minutes with a combined 7% T2/CPU load. (Trying two simultaneous transcodings took the same amount of time but with double the T2/CPU load.) Later on I tried a 15.94GB x264 file that resulted in a 3.34GB x265 file that took under 15 minutes to complete. My conclusions are that even though I don't achieve the smaller file sizes available via the libx265 encoder in HandBreak the time savings is worth my using the T2 as my daily encoder. Finally, I'll mention again that the T2's chip performance should be the same across all 2018 macOS models and beyond with the i7 models having better CPU performance because of the hyper-threading which is not available in the i5 even though both have 6 cores and similar clock speeds. That would be a factor only if I used HandBreak.

Hi, I'm thinking about buying a nas from Qnap (model ts-253BE), but I wanted to know if hardware acceleration is supported by the app. I've read an old thread where users said that it wasn't supported yet, so I was wondering it is now. Also, is the hardware acceleration working with h265 codec, or just h264? Thanks a lot !

What is the current status of hardware acceleration and Emby Server? I can't find a lot of information, but I can find more people asking this question. Is there or might there be one day, a guide that specifies what hardware acceleration option are actually available in certain situations like OS, GPU, CPU? I'm looking in to VA-API now. If something interesting pops up I'll post it here. EDIT: https://trac.ffmpeg.org/wiki/Hardware/VAAPI Hooked @" If you have multiple usable devices in the same machine".., but it's going to take me a while to dig tru this http://www.ffmpeg.org/ffmpeg.html#Advanced-Video-options Windows Server 2016 AMD 9590 @ 5Ghz 32GB RAM AMD R9 480 AMD HD7750 I just acquired some 4K, x265 material. Transcoding this material is a nightmare (doable for 1 stream)

Hi Everyone, Quick question...which Hardware Acceleration setting would the community recommend for an Intel HD5500 (Core i7-5500U, Dell XPS 13)? Thanks, hopefully this Topic will help someone else out also! -JBL

Hi guys, first post here. I have a new install of Emby on a server using an ASRock N3700-ITX motherboard. The CPU is small, but supports up to 4K hardware accelerated transcoding via Quick Sync. If I set Emby with Quick Sync disabled, I am able to watch on any of my clients, but only up to 480p. If I turn Quick Sync on, I get nothing on any client. The stream opens like normal, but nothing ever shows up. The system does not register any kind of an error, and unless I back out of the stream myself, it will sit indefinitely on a blank screen because the DLNA client is not aware that an error has occurred. If I watch from the Emby UI on a PC web browser, its the same story. Everything is current (Emby version, OMV updates, Debian updates, and BIOS). I installed Plex and get the exact same result. All clients hang with no stream and no error, so this is probably a compatibility issue more than it is a problem inherent in Emby. Any ideas here, though? I'm sure I'm not the first person to use these intel chips for this purpose. They've been out six months now and everyone online has been raving about them for HTPCs. Questions: (1) Even doing transcoding without acceleration, I think I should be able to do one 1080 stream without issue. Why am I locked at 480? (2) What can I do to troubleshoot Quick Sync under these circumstances?

Whenever Intel Quick Sync is selected in the Playback/Transcoding/Hardware Acceleration dropdown, none of my recorded TV shows will play. The hardware acceleration makes the overall live TV experience smoother, but the recorded tv failure is a major issue. The recorded tv fails to play in all web browsers, as well as Android TV and Android Mobile, so it seems to be a cross/platform issue. Has anyone else had this issue or can anyone else recommend a fix? I'd really appreciate it! Thank you!