Search the Community

I have a server consisting of the following hardware: Asrock N68C-GS FX AMD fx 4800 8 GB of Dual Channel DDR3 1600 RAM A generic usb 3.0 drive as boot drive A seagate barracuda 3TB HDD for media storage Ubuntu server 16.04.3 as OS playback on Chrome on a windows 10 pc When playing videos, the playback seems to drop very often and buffering seems to take forever. However when looking in the dashboard I often see that the server is either direct streaming or transcoding at over 60 frames per second. I also notice that when playing media firstly the process takes up around 60 to 70% of the cpu, at which point the playback is fine. However after some time the process disappears, and the playback stop, it then takes about a good 5 minutes for a new process to start streaming the media again. I have tried reinstalling emby-server as well has tried multiple versions of ffmpeg, however nothing seems to work. I hope someone else can spot the issue and bring me the sweet joy of smooth video playback GeneralLog.txt transcodingLOG.txt

Hi everyone, how are you? first, thank you for this wonder tool called Emby. So, reckoning about 1 week to the present time, my .strm files with the links in the format (H264 with AAC audio) that does not transcode, started suddenly to transcode and use my upload band, with that, all my clients were having problems of recurrent slowness. I imagine it should be in a possible update / maintenance of the Emby player that affected this, can you check? I am urgently needed due to completing 1 week of rework on account of this. Thanks for your attention, thank you in advance for your cooperation.

Hi all, I just switched from Plex to Emby just to give it a go. I have a WD TV Live that I'm using in the lounge however EAC3 audio isn't supported by WD and I can't for the life of me get Emby to automatically transcode it like Plex does. Here is a screenshot of the media info: https://imgur.com/fJXyJx4 Thanks in advance Nathaniel

Hello All Starting with stable release 3.2.35.0-3 (released today), Emby Server now includes improved h/w transcoding support for platforms that support Intel's VA-API. For some recent background, take a look at this thread: https://emby.media/community/index.php?/topic/48771-va-api-pixelation-on-ds416play/?p=505088. Any questions, issues or comments please post them here... Best - James

Hello Is it possible to get H/W transcoding running on a ESXi virtual machine? I have just installed Emby on a Ubuntu 16.04 server VM, but it runs terrible when I stream to browser or kodi. I've tried updating ffmpeg to 3.4 and installing i965-va-driver, but when run vainfo I get this: error: can't connect to X server! error: failed to initialize display Aborted (core dumped) I don't have a dedicated graphic card, so it possible the use the servers Intel Core i7-3770 onboard on the vm? If so could anyone help me getting this running?

I found a number of other threads with similar symptoms but not quite the same hardware; The closest being https://emby.media/community/index.php?/topic/45550-transcoding-performance-vs-that-other-server/ I have a no-name i7 mini PC ("Intel® Core i7-7500U CPU @ 2.70GHz") running Ubuntu 17.04 Recently installed Emby (release) next to Plex and paid for Premiere because it seems like a right thing to do. Anyway trying hardware transcode with the default ffpmeg fails: [AVHWDeviceContext @ 0x50d4520] No VA display found for device: /dev/dri/renderD128. [vaapi @ 0x312f1e0] Failed to create a VAAPI device But using the system shipped one (/usr/bin/ffmpeg) works OK, in ubuntu 17.04 is claims: ffmpeg version 3.2.4-1build2 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 6.3.0 (Ubuntu 6.3.0-8ubuntu1) 20170221 Hardware transcoding works, CPU usage is reasonable (70-80% of one core) but playback stutters - play 10 seconds, stop 5, play 10 seconds, stop etc. Not sure what this means (yet), but the only noticeable errors in the log are: [h264 @ 0xc6763beea0] Hardware accelerated decoding with frame threading is known to be unstable and its use is discouraged. Input stream #0:0 frame changed from size:1920x1080 fmt:yuv420p to size:1920x1080 fmt:vaapi_vld Unrepairable overflow! I've changed the CRF to 19 (from 23) with no difference, I've set the temporary path to a local scratch SSD with lots of space, turned off throttling. No effect. I have yet to try one of the custom ffmpeg builds, but looking at the log it's not the conversion performance that's the problem: frame=10024 fps= 67 q=-0.0 size=N/A time=00:06:58.34 bitrate=N/A speed=2.81x frame=10047 fps= 67 q=-0.0 size=N/A time=00:06:59.30 bitrate=N/A speed= 2.8x frame=10073 fps= 67 q=-0.0 size=N/A time=00:07:00.39 bitrate=N/A speed= 2.8x On the other hand, looking a bit more manually I *think* the stop/start is every time the m3u8 file is updated but "tail -f" doesn't work on that file for some reason, so it's hard to visually sync the changes to the display - just lots of repeated "ls -l" I also tried the beta but with the .net install it seemed to not quite work so I hurriedly backed out deciding that a pre-release of a new system is not quite the right thing to do just now. Any immediate suggestions and/or which logs would be useful? Peter

I guys . I'm totally new to emby so i hope my question won't be too stupid for you Status : HP n 54l with xpenology and plex media server. I want to switch from plex to emby because there is nos significant improvement on hardware transcoding since a year and i need a plex pass to use it. Purpose : Adding a Nvidia gt1030 for Hardware transcoding on the fly 4K HEVC from it to read it from a distant place. Is there any chance it works ? Like i dont whant to waste my money I decided to try emby on my gaming computer (gtx980 + 6600k + win 10) to see how mature was hardware transcoding on Emby. Just installed the server and running it. No configuration other than switching to Nvidia NVENC. Switch to my Z3 tablet with the android app and do this : Try to read a full HD movie in H264 - without transcoding => OK CPU 1% NO GPU - Transcoding to 720P 2mbps => 13% CPU 20% GPU (why ? shoudln't the cpu stay to 1%) Try to read a Full HD movie in H265 - without transcoding => OK CPU 1% NO GPU - transcoding to anything Doesn't work . (log attached). Any advice on the probability to decode 4h hevc with Hpn54l + gt1030 is welcome.(most of all for say to me it will works ) Any help to understand why my test was a faile dis welcome too. Let me now if you need any other informations or If i forgot something.

I was trying to watch a blu-ray mkv file yesterday from yesterday at 6:58pm til 7:08pm (tried starting and restarting the movie at different transcoding settings) but the loading screen kept appearing during playback. Also got a http request error when trying to watch a dvd mkv file around 711pm Lastly, does Intel QuickSync still have an issue with transcoding timestamps? since i'm forced to transcode without HA currently. server log 9-25-2017 (12am).txt server log 9-26-2017 (12am).txt transcode log 9-25-2017 (701am).txt transcode log 9-25-2017 (707am).txt transcode log 9-25-2017 (709am).txt transcode log 9-25-2017 (710am).txt transcode log 9-25-2017 (712am).txt

I have emby setup, have a test folder, have firetv, and have allot of mp2, mp4, files. I did setup the nfs to network storage. My questions are does the trial version of the amazon firetv app allow play by VLC and directplay? Can I turn off all transcoding and only if a file would not play I would then process that file through handbrake. Yes or no, I guess what has now started to frustrate me is a poorly documented process that has tiers of support and feature and no real answers. But again what i want is: Nas to feed the nfs path Artwork at the storage folder location Let fireTv do the transcoding use the VLC player or native codec to fire run from Ubuntu server finally the emby software seemed to require that VLC cache the password to a shared drive While no password was required for the alternate path Again, want no transcoding, can it be done? Just serve up the library and art from a server, yes or no?

Hi, I don't know how this works so please forgive me if I'm wrong. If 2 or more users play the same video , let's say that first user already have the full movie trans-coded and buffered, when second user play the same video why have to trans-code again the entire movie if is already trans-coded by the first one ? Maybe is just a dumb question All I want to know is a little bit more how it works

Hi folks, Since a few days ago we've noticed the audio sometimes cuts out on our Chromecast. I've done some testing and found the following: It only cuts out when transcoding and the audio is mapped to AAC, MP3 works fine. It will cut out within the first few minutes. Usually between 1 and 3 minutes. Stopping and restarting playback fixes the problem for a few more minutes until it cuts out again. I've rolled back the server version to a time I knew it worked OK yet the problem remains. Can anyone replicate this problem for me, just so I know I'm not going crazy? Cheers,

Hi ! I have a screen attached to a Chromecast v2. I have a Raspberry Pi 2, with Emby server with DLNA support. From my iPad, with the Emby official application, I can stream all my movies. But, for each video, there is transcoding, my CPU is > 99% even for videos that don't require transcoding because the Chromecast v2 support it. If I use a simple iPad application to play a DLNA video to my Chromecast (without any transcoding), I can play the same video with less than 5% of CPU usage. So, I suppose this could be fixed if I create a ChromeCast profile to skip some supported audio/video codecs, to be in direct play, but it's really complicated for me to do this because there is a lot of informations to known, and my knowledges are too limited to fill this correctly. I would like to known if someone have already created this DLNA profile and could share it please? Best regards,

Hey guys, Running Emby Server on my Synology DS216j and a client on a nvidia Shield (Android TV) I am wondering why some files are having to be transcoded (see attached log) The same file seems OK when running in Emby Theater (on my PC) Anything I should be doing different? Any way you guys can help? Thanks

I always had my server's services such as Emby running in bare-metal because I did't like the performance loss in VM/Hypervisor, etc (I know it's little, but it's something). But it's true that having all services in the same OS is a pain in the a** because if you need to change or reboot something, everything goes down. In addition I need VAAPI transcoding for my server so I needed direct access to iGPU through /dev/dri/renderD128 device. After reading a lot about LXC containers and the benefits of isolation and bare-metal peformance they have, I decided to change and go containerize everything. So installed Debian Strech in the server with LXC 2.0.8 (only available in testing repositories) and created an Ubuntu 16.04 container just for the Emby server. In order to get VAAPI working inside the Emby container, you need to "pass" the required device (/dev/dri/renderD128) from the host to the container and have all drivers installed in the host system. So let's do it. (I assume you already created a container and Emby and ffmpeg are installed in it) (All commands are ran in the host, not inside the container) Stop your container if it's running: lxc-stop -n containername Get the required drivers in the host (my server is a Skylake i5-6600) by installing vainfo (it will automatically install intel-i915-driver, etc.): apt install vainfo Check that vainfo outputs something like this (run vainfo in the command line): error: can't connect to X server! libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice Now we have to pass the /dev/dri/renderD128 device (which is in charge of VAAPI transcoding) to the container. To do so, we'll write a little script who creates the renderD128 device inside the container everytime this one is started. For that we need to know what kind of device we have and it's minor/major numers, so we run: ls -l /dev/dri Output: total 0 drwxr-xr-x 2 root root 80 ago 5 17:18 by-path crw-rw---- 1 root video 226, 0 ago 5 17:18 card0 crw-rw---- 1 root video 226, 128 ago 5 17:18 renderD128 The info we need is: the letter "c" (in crw-rw----) meaning it's a character device and "226 128" which are the major/minor numbers of the device. Let's create the script then, it will be inside your container's directory but you can place it anywhere changing the paths obviously. Run: nano /var/lib/lxc/containername/autodev And copy inside: #!/bin/bash cd ${LXC_ROOTFS_MOUNT}/dev mkdir dri mknod -m 0666 dri/renderD128 c 226 128 Save, exit and give it privileges with: chmod +x /var/lib/lxc/containername/autodev Perfect, now we have to grant container's access to the device and tell him to run the script when the container starts. To do so, you have to edit the container's configuration file. Run: nano /var/lib/lxc/containername/config And add these two lines at the en of the file: lxc.cgroup.devices.allow = c 226:128 rwm lxc.hook.autodev = /var/lib/lxc/containername/autodev The first line will grant container's access to the device and the second line will run the script which will create the device inside the container. That's all! Now you you can start your container again, attach to it, check the /dev/dri directory and you'll find the renderD128 device inside of it. You can now tell Emby to use it as if you where in a host machine! Enjoy LXC! Referece: https://blog.cavebeat.org/2016/02/how-to-create-tuntap-devices-for-lxc-in-proxmoxve-4-1/

Hello, I recently moved from Plex to Emby because the first still doesn't support the Chromecast Ultra but I'm coming across a different problem with Emby: While most video files I have are 5.1 or 7.1 audio tracks and thus require transcoding, which I know is normal for the CCU since it only supports stereo audio or passthrough, I notice Emby transcodes the whole file instead of only the audio... So because the MKV has 5.1 audio, the video is transcoded from HEVC to h264 all the time which obviously uses unnecessary CPU and lowers the quality of the stream. This occurs for any HEVC files I have that includes an audio track over 2 channels... HD or UHD. So is this normal? Did I forget to configure anything? Where can I get more info as to why exactly it's being transcoded? emby_server.log emby_transcoding.log

/usr/bin/ffmpeg -ss 01:34:18.000 -i file:"/srv/b2e24e20-856e-4b9e-9fa5-c504efb2b7cc/Media/Movies/Ratatouille (2007)/Ratatouille (2007).mp4" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 libx264 -pix_fmt yuv420p -preset veryfast -crf 23 -maxrate 2871711 -bufsize 5743422 -profile:v high -level 4.1 -x264opts:0 subme=0:me_range=4:rc_lookahead=10:me=dia:no_chroma_me:8x8dct=0:partitions=none -force_key_frames "expr:gte(t,n_forced*3)" -vf "scale=trunc(min(max(iw\,ih*dar)\,1920)/2)*2:trunc(ow/dar/2)*2" -copyts -vsync -1 -codec:a:0 copy -f segment -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -segment_time 3 -segment_time_delta -5658 -individual_header_trailer 0 -segment_format mpegts -segment_list_type m3u8 -segment_start_number 1886 -segment_list "/var/lib/emby-server/transcoding-temp/3b94f4fbda40e23c54cb9833a1b959d6.m3u8" -y "/var/lib/emby-server/transcoding-temp/3b94f4fbda40e23c54cb9833a1b959d6%d.ts" I am trying to figure out if my system is using quicksync. If I am reading that line correct, it isn't telling FFMPEG to use hwaccel. Is that normal for the transcoding with hardware acceleration? Emby Version 3.2.26.0 Logs: https://1drv.ms/f/s!AtItXRNac1nKhfBw9ih_VuIY2XJFJA Emby Version 3.2.26.0

I am trying to switch to the system install version of FFMpeg and it won't let me. Every time I refresh the page after saving changes it goes back to custom.

I just reinstalled emby, long time user and premium. I recently purchased an HDHomeRun CONNECT, Model: HDHR4-2US, and I can't get any thing to play through emby. I can use VLC and connect and view channels through it but through the web, TV, android i get the spinning wheel. Are there any good troubleshooting steps to try besides resets and re-configs. Fresh Ubuntu 16.04 LTS and emby Version 3.2.26.0. Also I did get it to play once but I left it sit for an hour before it started playing.

Hi, I compiled my own ffmpeg build in order to use vaapi acceleration. It is working fine when I am transcoding without any scaling (e.g. from 1080p 30MBit to 1080p 5Mbit). However, when I change the resolution (e.g. from 1080p 30MBit to 480p 1Mbit) the scaling is off and I only see the top left segment of the original picture (see "down scaling 480p.png and "org scaling 1080p.png). Without vaapi acceleration the scaling works fine. I am running emby on Openmediavault 3.0.84 with Intel HD Graphics P4600 (Dell T20), as you can see in the server log (Log.txt) attached. So, what could be the problem? I would be delighted if you guys could help me. Thanks, kaufhauslicht Log.txt transcode_log_480p.txt transcode_log_1080p.txt

Good Evening, I am submitting this issue as I can't seem to find a way have the chromecast maximum bit-rate respected. There is an option in the web browser and the android client to specify the max bit-rate however it doesn't seem to actually pay attention to it. Below there is a screenshot where I have specified a max bit-rate as 3mbps and the server dashboard shows that it is trans-coding at 5.6mbps, the same happens from the web app on android and from the native android app. I have attached the full server lot and some of the relevant trans-coding logs. Please let me know if there is anything else that I can submit to assist. server-63635846400.txt ffmpeg-remux-4de2156a-7532-4988-959a-f02839ad183a.txt ffmpeg-transcode-a341d09a-6f12-4705-97da-dc47265cf1dd.txt ffmpeg-transcode-ca113fd6-f9bb-4c3e-a869-6a41719c86c0.txt ffmpeg-transcode-ee51c2b7-dd04-480a-8c50-7100f4b023f6.txt

Greetings, I've really been enjoying running Emby on an old Mac Pro that was given to me; generally with the two Xenons I figured it'd do alright and for the most part I've been correct - across a vast range of media it plays things back flawlessly. However, I watch a lot of Anime (which is an understatement) and a lot of it features subtitles of the ASS variety. Usually when I watch them with VLC on a computer just like the one I have Emby running on, they move fluidly with all the crazy animations that the subbers have added; but in Emby when streaming to any other client that apparently isn't the case. They are often just a little slow, even in shows that have really minimal subbing and in the ones that have crazy stuff going on I've actually seen it pause the video intermittently and take a break during heavy sections like the openings and endings. If you wanna see what a log looks like of me watching an entire episode of something you can find it attached Log.txt . Basically, is there anything I can do to improve playback and prevent this from happening? I really don't want to bake these in to my files, but maybe I'd experience more uniform experiences if I shelled out for a GTX 950 with NVENC or something. What's your opinion? Anyone else have this happen to them? Thanks -Kb

I am CPU transcoding to Android mobile client over the internet (LTE). When I seek using the scrub bar server CPU utilization goes from 90% to 100% and stays there for at least several minutes. When I look at the running processes in task manager, I see a second ffmpeg process was started, I presume to support transcoding from the new seek location. Yet the previous ffmpeg process was not shut down - the two ffmpeg processes are hogging 100% CPU, at 50% each. When I stop playing the Android client one ffmpeg process stops, while the second ffmpeg lingers at 10% CPU for several minutes before terminating. I did check transcoding without seeking through the movie, in this case the server and transcoding are well behaved with ffmpeg using the typical 90% CPU (i7-6800K, slow and 22 quality settings). If I stop playing at the client, the single ffmpeg process terminates immediately. It seems the server would be much more responsive if the unneeded second ffmpeg process were terminated promptly. I suspect this unnecessary server load is degrading the user experience. Perhaps it is not that hard to track down and resolve? Please let me know if there is anything further I can do to help troubleshoot besides the attached logs. Android client is 3.8.x.x beta within the past two days, not sure where to find the version number in the app. Thanks! server-63633825041.txt ffmpeg-transcode-4099a602-80de-4868-a1c2-6ced9ef179f6.txt ffmpeg-transcode-ccf995f1-dae1-460d-974a-1cdca25b27f8.txt ffmpeg-transcode-4b804d44-38b4-437a-98b8-c9572c19c3ae.txt

I am having some issues getting hardware transcoding to work properly with Emby Server on Centos 7.2.1511. I have successfully installed Media Server Server Studio and build the necessary custom ffmpeg. When I try to play something that should get transcoded I get an error. What is strange is when I run vainfo as seen above, it trys libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so But the emby transcoding logs show it trying libva info: Trying to open /usr/lib64/dri/i965_drv_video.so How do I make emby use the version that shows from vainfo? The analyzer tests pass: [media-admin@DFES ~]$ ./sys_analyzer_linux.py -------------------------- Hardware readiness checks: -------------------------- [ OK ] Processor name: Intel® Core i7-6700K CPU @ 4.00GHz -------------------------- OS readiness checks: -------------------------- [ OK ] GPU visible to OS -------------------------- Intel® Media Server Studio Install: -------------------------- [ OK ] user in video group [ OK ] libva.so.1 found [ OK ] vainfo reports valid codec entry points [ OK ] /dev/dri/renderD128 connects to Intel i915 -------------------------- Media SDK Plugins available: (for more info see /opt/intel/mediasdk/plugins/plugins.cfg) -------------------------- H264LA Encoder = 588f1185d47b42968dea377bb5d0dcb4 VP8 Decoder = f622394d8d87452f878c51f2fc9b4131 HEVC Decoder = 33a61c0b4c27454ca8d85dde757c6f8e HEVC Encoder = 6fadc791a0c2eb479ab6dcd5ea9da347 -------------------------- Component Smoke Tests: -------------------------- [ OK ] Media SDK HW API level:1.21 [ OK ] Media SDK SW API level:1.21 [ OK ] OpenCL check:platform:Intel® OpenCL GPU OK CPU OK This is ffmpeg version: ffmpeg version N-86566-g067e42b Copyright © 2000-2017 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-4) configuration: --extra-cflags=-I/home/media-admin/ffmpeg_build/include --extra-ldflags='-L/home/media-admin/ffmpeg_build/lib -ldl' --bindir=/home/media-admin/bin --pkg-config-flags=--static --enable-shared --enable-libmfx --enable-nonfree --enable-gpl --enable-decoder=aac --enable-demuxer=mov --enable-libxcb --enable-zlib --enable-protocol=http --enable-filter=aformat --enable-filter=volume --enable-filter=aresample --prefix=/usr libavutil 55. 66.100 / 55. 66.100 libavcodec 57. 99.100 / 57. 99.100 libavformat 57. 73.100 / 57. 73.100 libavdevice 57. 7.100 / 57. 7.100 libavfilter 6. 94.100 / 6. 94.100 libswscale 4. 7.101 / 4. 7.101 libswresample 2. 8.100 / 2. 8.100 libpostproc 54. 6.100 / 54. 6.100 configuration: --extra-cflags=-I/home/media-admin/ffmpeg_build/include --extra-ldflags='-L/home/media-admin/ffmpeg_build/lib -ldl' --bindir=/home/media-admin/bin --pkg-config-flags=--static --enable-shared --enable-libmfx --enable-nonfree --enable-gpl --enable-decoder=aac --enable-demuxer=mov --enable-libxcb --enable-zlib --enable-protocol=http --enable-filter=aformat --enable-filter=volume --enable-filter=aresample --prefix=/usr and my vainfo: [media-admin@DFES usr]$ vainfo error: can't connect to X server! libva info: VA-API version 0.99.0 libva info: va_getDriverName() returns 0 libva info: User requested driver 'iHD' libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so libva info: Found init function __vaDriverInit_0_32 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.99 (libva 1.67.0.pre1) vainfo: Driver version: 16.5.1.59511-ubit vainfo: Supported profile and entrypoints VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: <unknown entrypoint> VAProfileH264ConstrainedBaseline: <unknown entrypoint> VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : <unknown entrypoint> VAProfileH264Main : <unknown entrypoint> VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : <unknown entrypoint> VAProfileH264High : <unknown entrypoint> VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : <unknown entrypoint> VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileVP9Profile0 : <unknown entrypoint> <unknown profile> : VAEntrypointVideoProc VAProfileNone : VAEntrypointVideoProc VAProfileNone : <unknown entrypoint> Here is the rest of the transcoding log. https://tv-internal.securefamily.cloud:8920/emby/videos/7199a462b0d7e08b46eae2b629b4cf01/hls1/main/0.ts?DeviceId=51c87acac428fadb310d4701d8a7176608e4963e&MediaSourceId=7199a462b0d7e08b46eae2b629b4cf01&VideoCodec=h264&AudioCodec=aac&AudioStreamIndex=0&VideoBitrate=808001&AudioBitrate=192000&Level=51&Profile=high&PlaySessionId=6f952a1b69bf48b8bfbc9fdfba527d0c&api_key=e3d6cf64fb104da49a7b946daa01a008&CopyTimestamps=false&TranscodingMaxAudioChannels=6&EnableSubtitlesInManifest=false&Tag=709d00d94b625e4115acb8c1940e5ec4&RequireAvc=true&RequireNonAnamorphic=false&DeInterlace=true&SegmentContainer=ts&MinSegments=1&BreakOnNonKeyFrames=False {"Protocol":"File","Id":"7199a462b0d7e08b46eae2b629b4cf01","Path":"/storage/TV Shows/Paw Patrol/Season 2/Paw Patrol - S02E04-05 - Pups Save the Penguins + Pups Save a Dolphin Pup WEBDL-720p.mkv","Type":"Default","Container":"mkv","Name":"720P/H264/AAC","IsRemote":false,"ETag":"709d00d94b625e4115acb8c1940e5ec4","RunTimeTicks":14025279488,"ReadAtNativeFramerate":false,"IgnoreDts":false,"IgnoreIndex":false,"GenPtsInput":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":true,"IsInfiniteStream":false,"RequiresOpening":false,"RequiresClosing":false,"SupportsProbing":true,"RequiresLooping":false,"VideoType":"VideoFile","MediaStreams":[{"Codec":"aac","Language":"eng","TimeBase":"1/1000","CodecTimeBase":"1/48000","DisplayTitle":"Eng AAC stereo Default","IsInterlaced":false,"ChannelLayout":"stereo","BitRate":192000,"Channels":2,"SampleRate":48000,"IsDefault":true,"IsForced":false,"Profile":"LC","Type":"Audio","Index":0,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"Level":0,"IsAnamorphic":false},{"Codec":"h264","Language":"eng","TimeBase":"1/1000","CodecTimeBase":"125/5994","NalLengthSize":"4","IsInterlaced":false,"IsAVC":true,"BitRate":4211058,"BitDepth":8,"RefFrames":1,"IsDefault":true,"IsForced":false,"Height":716,"Width":1280,"AverageFrameRate":23.976,"RealFrameRate":23.976,"Profile":"High","Type":"Video","AspectRatio":"16:9","Index":1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"PixelFormat":"yuv420p","Level":31,"IsAnamorphic":false},{"Codec":"subrip","TimeBase":"1/1000","CodecTimeBase":"0/1","DisplayTitle":"Und Default","IsInterlaced":false,"IsDefault":true,"IsForced":false,"Type":"Subtitle","Index":2,"IsExternal":false,"IsTextSubtitleStream":true,"SupportsExternalStream":true,"Level":0,"IsAnamorphic":false}],"PlayableStreamFileNames":[],"Formats":[],"Bitrate":4403058,"RequiredHttpHeaders":{}} /home/media-admin/bin/ffmpeg -c:v h264_qsv -i file:"/storage/TV Shows/Paw Patrol/Season 2/Paw Patrol - S02E04-05 - Pups Save the Penguins + Pups Save a Dolphin Pup WEBDL-720p.mkv" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:1 -map 0:0 -map -0:s -codec:v:0 h264_qsv -preset 7 -look_ahead 0 -b:v 808001 -maxrate 808001 -bufsize 1616002 -profile:v high -level 4.1 -force_key_frames "expr:gte(t,n_forced*3)" -vf "scale=trunc(min(max(iw\,ih*dar)\,720)/2)*2:trunc(ow/dar/2)*2" -copyts -vsync -1 -codec:a:0 copy -copypriorss:a:0 0 -f segment -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -segment_time 3 -individual_header_trailer 0 -segment_format mpegts -segment_list_type m3u8 -segment_start_number 0 -segment_list "/transcoding/transcoding-temp/27a5187f4519d6b8cd458ce2826b887e.m3u8" -y "/transcoding/transcoding-temp/27a5187f4519d6b8cd458ce2826b887e%d.ts" ffmpeg version N-86566-g067e42b Copyright © 2000-2017 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-4) configuration: --extra-cflags=-I/home/media-admin/ffmpeg_build/include --extra-ldflags='-L/home/media-admin/ffmpeg_build/lib -ldl' --bindir=/home/media-admin/bin --pkg-config-flags=--static --enable-shared --enable-libmfx --enable-nonfree --enable-gpl --enable-decoder=aac --enable-demuxer=mov --enable-libxcb --enable-zlib --enable-protocol=http --enable-filter=aformat --enable-filter=volume --enable-filter=aresample --prefix=/usr libavutil 55. 66.100 / 55. 66.100 libavcodec 57. 99.100 / 57. 99.100 libavformat 57. 73.100 / 57. 73.100 libavdevice 57. 7.100 / 57. 7.100 libavfilter 6. 94.100 / 6. 94.100 libswscale 4. 7.101 / 4. 7.101 libswresample 2. 8.100 / 2. 8.100 libpostproc 54. 6.100 / 54. 6.100 Input #0, matroska,webm, from 'file:/storage/TV Shows/Paw Patrol/Season 2/Paw Patrol - S02E04-05 - Pups Save the Penguins + Pups Save a Dolphin Pup WEBDL-720p.mkv': Metadata: encoder : libebml v1.3.0 + libmatroska v1.4.1 creation_time : 2014-12-21T18:31:30.000000Z Duration: 00:23:22.53, start: 0.000000, bitrate: 4211 kb/s Stream #0:0(eng): Audio: aac (LC), 48000 Hz, stereo, fltp (default) Metadata: BPS : 135217 BPS-eng : 135217 DURATION : 00:23:22.496000000 DURATION-eng : 00:23:22.496000000 NUMBER_OF_FRAMES: 65742 NUMBER_OF_FRAMES-eng: 65742 NUMBER_OF_BYTES : 23705260 NUMBER_OF_BYTES-eng: 23705260 _STATISTICS_WRITING_APP: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_APP-eng: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_DATE_UTC: 2014-12-21 18:31:30 _STATISTICS_WRITING_DATE_UTC-eng: 2014-12-21 18:31:30 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Stream #0:1(eng): Video: h264 (High), yuv420p(tv, bt709, progressive), 1280x716 [sAR 1:1 DAR 320:179], 23.98 fps, 23.98 tbr, 1k tbn, 2k tbc (default) Metadata: BPS : 4073248 BPS-eng : 4073248 DURATION : 00:23:22.528000000 DURATION-eng : 00:23:22.528000000 NUMBER_OF_FRAMES: 33627 NUMBER_OF_FRAMES-eng: 33627 NUMBER_OF_BYTES : 714105596 NUMBER_OF_BYTES-eng: 714105596 _STATISTICS_WRITING_APP: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_APP-eng: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_DATE_UTC: 2014-12-21 18:31:30 _STATISTICS_WRITING_DATE_UTC-eng: 2014-12-21 18:31:30 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Stream #0:2: Subtitle: subrip (default) Metadata: BPS : 97 BPS-eng : 97 DURATION : 00:22:53.237000000 DURATION-eng : 00:22:53.237000000 NUMBER_OF_FRAMES: 499 NUMBER_OF_FRAMES-eng: 499 NUMBER_OF_BYTES : 16666 NUMBER_OF_BYTES-eng: 16666 _STATISTICS_WRITING_APP: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_APP-eng: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_DATE_UTC: 2014-12-21 18:31:30 _STATISTICS_WRITING_DATE_UTC-eng: 2014-12-21 18:31:30 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES libva info: VA-API version 0.99.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: va_openDriver() returns -1 [AVHWDeviceContext @ 0xf6c580] Failed to initialise VAAPI connection: -1 (unknown libva error). Device creation failed: -5. [h264_qsv @ 0xf8cc00] No device available for decoder (device type qsv for codec h264_qsv). Stream mapping: Stream #0:1 -> #0:0 (h264 (h264_qsv) -> h264 (h264_qsv)) Stream #0:0 -> #0:1 (copy) Press [q] to stop, [?] for help [NULL @ 0xfa69e0] non-existing SPS 0 referenced in buffering period [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened Too many packets buffered for output stream 0:1. Conversion failed!

Hola buen día, me gustaría saber si se puede deshabilitar la transcodificacion.

Hi all, I´m new to Emby/Synology so please bare with me if I ask any dumb questions... I recently bought a new DS416 in order to consolidate all media (movies, photos, music, etc) and coming from PC/MediaPortal I have decent knowledge of how things work in general. However, I´ve ran into some issues with my Emby setup and hopefully someone else out there has experienced the same problem(s) and has a magical solution... My DS416 runs on 4 Western Digital Red NAS 3TB harddrives (SHR) with DSM version 6.1.1-15101 Update 4. Emby Server is recently upgraded to version 3.2.19.0 and is setup according to Embyserver for NAS and Synology : Setting Up Your Media Library Share. After this I´ve imported all my videos and everything seems ok except the playback which sucks... My friend who recommended Emby said something about subtitles, i.e. Emby tries to transcode certain types and therefor the CPU is constantly on ~99% (where mono eats about 49% and ffmpeg about 49%). I´m not sure what to do about that more than I´ve done below..?!? So, any help here is greatly appreciated. He also mentioned that native apps are better than 3d part, i.e. browsers, but regardless if I try to watch a movie on my Ipad (native app), my Sony Bravia (native app) or from Firefox, the playback is lagging in 90% of the cases. If/when I disable the subtitles the playback usually gets better but regardless filetype (avi, mkv, mpeg) there´s always a lag and when I check the Emby Dashboard for active devices, the playback is almost always in Transcoding Mode instead of Direct Play or Direct Streaming. Every single movie that´s lagging through Emby, works perfect with VLC from my old (network attached) computer regardless if I use subtitles or not. Besides my old computer, everything else is connected wireless, i.e. my TV, all devices, etc. I´ve also tried to use hardware acceleration; VA API and Intel Quick Sync but no change at all. My router (Asus RT-AC87U with MerlinWRT) is setup with port-forwarding and Emby has both an in-home and remote address which are tested and working. The general WiFi throughput on the LAN side is between 150-500Mbit depending on the connected device and that is sufficient for casting a 720p movie to a Chromecast on the 2d floor without any lag. I don´t intend to use the DS416/Emby to stream to multiple devices, I just want to be able to watch a 720/1080 video at home, from my Sony TV, with smooth playback and subtitles. So, my questions are: 1. Anyone else having the same problem? 2. Have I missed something in the setup? 3. Is there any other/newer ffmpeg version that´s better for my DS416? Like I said, I´m new to DS416/Emby but I know my way around computers/network/routers/etc and I´m more than willing to try out any solution that might fix my problems. Tnx in advance. Cheers,