Jump to content

Search the Community

Showing results for tags 'VAAPI'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 12 results

  1. Hi guys, I'm currently figuring out how I can enable ffmpeg to use my /dev/dri/renderD128 device which is the iGPU of my intel chip. Currently I have the following things covered: - drm module is loaded and /dev/dri/renderD128 is accessible in jail - emby user has access to the device node - I have installed libva-intel-driver and it is picked up by vainfo - ffmpeg is compiled with libva support I'm sure that emby can access the node and use it with the ffmpeg supplied by emby. As show in the following command output: Even if I supply an input file and output file for the sake of ex
  2. 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
  3. ZiemaF

    OMV DOCKER EMBY problem with VAAPI

    Hi, I can not run VAAPI on my server. My server is on an i5-8600K processor, OMV 0.4 4.1.17-1 installed. EMBY is placed on DOCKER EMBY works great except for VAAPI. Please help me how to run it. ffmpeg-transcode.txt embyserver.txt
  4. 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 everythi
  5. zeroidea

    QNAP + docker + iGPU hwaccel

    Just migrated to a new QNAP (TVS-951X) and there was an issue getting vaapi working in my emby docker container. In QTS 4.3.6.0875 there are no default system groups (like video) and the /dev/dri folder is owned by admin:administrators with restrictive permissions, which are reset upon reboot. It was necessary to create an autorun.sh script to set things up for docker use. #!/bin/bash chown admin:video /dev/dri chmod 775 /dev/dri chown admin:video /dev/dri/* chmod 660 /dev/dri/* The docker needs to run as a user assigned to the video group (or have the video group's GID listed in GI
  6. Hi, I have a server on UnRaid, Docker is running on this server. EMBY works on Docker, with HW transcoding (VAAPI Intel i5-8600k), generally works great. I have a problem with films with 10bit color. If I play the movie directly (without transcoding) the colors are ok. If I turn on transcoding (to any resolution), the colors are so faded. Can i do something about it? Thank you for your help
  7. I feel like I'm very close to having hardware acceleration working again, after switching to Debian Buster in a container, but I can't quite get it. This is AMD A10-5700, with Radeon HD 7660D. Please any help? As user emby, my ''vainfo'': error: can't connect to X server! libva info: VA-API version 1.4.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_4 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.4 (libva 2.4.0) vainfo: Driver version: Mesa Gallium
  8. Keltere

    No HEVC (H.265) encoder VAAPi

    Like the title i can seem to get the hevc encoder to appear on the list. I use the last version of arch linux (4.19.8-arch1-1-ARCH) with the last beta of emby (3.6.0.81) I've already installed intel-media-driver but it just won't appear
  9. Hello, I'm having difficulty getting hardware transcoding working. Docker /dev/dri / # ls -l /dev/dri total 0 crwxrwxrwx 1 root 44 226, 128 Oct 13 14:11 renderD128 Host /dev/dri > ls -l /dev/dri total 0 drwxr-xr-x 2 root root 120 Oct 1 18:01 ./ drwxr-xr-x 18 root root 3.7K Oct 13 10:22 ../ crw-rw---- 1 root video 226, 0 Oct 1 18:01 card0 crw-rw---- 1 root video 226, 1 Oct 1 18:01 card1 crw-rw---- 1 root video 226, 64 Oct 1 18:01 controlD64 crw-rw---- 1 root video 226, 128 Oct 1 18:01 renderD128 guid of video is 44. Hardware accelerat
  10. Hi, When I am trying to transcode 4K HEVC, I get the following error: [AVHWFramesContext @ 0x7fc9e006fc00] Failed to read image from surface 0x19: 1 (operation failed). Metadata: [hevc @ 0x555e9355a680] Failed to transfer data to output frame: -5. title : Chapter 5 Error while processing the decoded data for stream #0:0 Chapter #0:5: start 3008.964000, end 3781.778000 Conversion failed! The appropriate ffmpeg command is: /usr/bin/ffmpeg -ss 00:14:24.000 -hwaccel vaapi -hwaccel_output_format yuv420p -vaapi_device /dev/dri/renderD128 -i file:"input.mkv" -threads 0 -map 0:0 -map 0:1 -code
  11. derdigge1982

    trouble with intel hwacc vaapi

    Dear Community. I am quiet new to emby. Until now i like it very much, it is clean and simple. On my archlinux box i am playing around with it. During that time i tried the hw acceleration of my i7-3770, which supports h264 accel through vaapi within ffmpeg. Running vaapi as root just works fine. Emby fails. Hardware Intel i7 3770 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) Subsystem: ASUSTeK Computer Inc. P8 series motherboard Kernel driver in use: i915 Kernel modules: i915 emby
  12. I have Emby Server running on Ubuntu 16.04 and got VA-API hardware transcoding working (see my post here). I got it to play with transcoding on Chrome browser via the web app by setting max birate to 5Mbps. However, the same file doesn't play with the FireTV after setting to the same 5Mbps. Looking at the log, looks like ffmpeg is transcoding the file fine, but the FireTV (2nd gen, version 1.2.66a) doesn't want to play the file. Please see the attached logs. server-log.txt ffmpeg-transcode-chrome.txt ffmpeg-transcode-firetv.txt
×
×
  • Create New...