Jump to content

alturismo

Moderators
 View Profile  See their activity

  • Posts

    6,393

  • Joined

  • Last visited

  • Days Won

    53

 Content Type 

Posts posted by alturismo

    [Support] Linuxserver.io - TVHeadend

    in Docker Containers

    Posted

    i see, nope, may cause i dont have this tab ...

     

    im in Expert mode and i have these tabs for settings

     

    image.thumb.png.02449d1bc720f8e98300f74c43c340ce.png

     

    No codec Profiles here ...

     

    heres the output from the docker bash grep, may something missing ?

     

    root@AlsServer:/dev/dri$ ffmpeg -codecs | grep vaapi.
    ffmpeg version 3.4 Copyright (c) 2000-2017 the FFmpeg developers
      built with gcc 6.4.0 (Alpine 6.4.0)
      configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libmp3lame --enable-librtmp --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --disable-stripping --disable-static --enable-vaapi --enable-vdpau --enable-libopus --disable-debug
      libavutil      55. 78.100 / 55. 78.100
      libavcodec     57.107.100 / 57.107.100
      libavformat    57. 83.100 / 57. 83.100
      libavdevice    57. 10.100 / 57. 10.100
      libavfilter     6.107.100 /  6.107.100
      libavresample   3.  7.  0 /  3.  7.  0
      libswscale      4.  8.100 /  4.  8.100
      libswresample   2.  9.100 /  2.  9.100
      libpostproc    54.  7.100 / 54.  7.100
     DEV.LS h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m h264_vdpau h264_cuvid ) (encoders: libx264 libx264rgb h264_nvenc h264_v4l2m2m h264_vaapi nvenc nvenc_h264 )
     DEV.L. hevc                 H.265 / HEVC (High Efficiency Video Coding) (decoders: hevc hevc_cuvid ) (encoders: libx265 nvenc_hevc hevc_nvenc hevc_vaapi )
     DEVIL. mjpeg                Motion JPEG (decoders: mjpeg mjpeg_cuvid ) (encoders: mjpeg mjpeg_vaapi )
     DEV.L. mpeg2video           MPEG-2 video (decoders: mpeg2video mpegvideo mpegvideo_vdpau mpeg2_v4l2m2m mpeg2_cuvid ) (encoders: mpeg2video mpeg2_vaapi )
     DEV.L. vp8                  On2 VP8 (decoders: vp8 vp8_v4l2m2m libvpx vp8_cuvid ) (encoders: libvpx vp8_v4l2m2m vp8_vaapi )
     DEV.L. vp9                  Google VP9 (decoders: vp9 libvpx-vp9 vp9_cuvid ) (encoders: libvpx-vp9 vp9_vaapi )
    root@AlsServer:/dev/dri$ ls -la
    total 0
    drwxr-xr-x  2 root root        80 Aug  5 16:52 .
    drwxr-xr-x 13 root root      3440 Aug  5 16:52 ..
    crw-rw----  1 root audio 226,   0 Aug  5 16:52 card0
    crwxrwxrwx  1 abc  abc   226, 128 Aug  5 16:52 renderD128
    root@AlsServer:/dev/dri$

    [Support] Linuxserver.io - TVHeadend

    in Docker Containers

    Posted · Edited by alturismo

    as i see TVH doesnt load the vaapi correctly, i ll try l8 when plex is turned off if then TVH would load vaapi correctly.

     

    Now i see TVH needs CPU power (cause software decoding) while PLEX using hardware acc ... no real CPU usage.

     

    i will try with plex off and restart tvh to see if then TVH is able to use vaapi, then it would be clear if theres only 1 access possible ;)

     

    thanks for trying

     

    EDIT

     

    tested now also with PLEX off, restarted TVH, no difference, same error, unable to open h264 vaapi ...

     

    just as note 

    [Support] Linuxserver.io - TVHeadend

    in Docker Containers

    Posted · Edited by alturismo

    and thats the error in TVH

      

    2018-07-31 16:05:38.303 transcode: 0003: Unable to open h264_vaapi encoder

    so maybe blocked cause already loaded by PLEX, thats what my question was if TVH even could use hardware acc if PLEX docker also preloaded --device ...

    [DOCKER] Pipework

    in Docker Containers

    Posted

    ok, got it working with pipework

     

    starting the docker several times in Host Mode, each time another extra parameter

     

    -e 'pipework_cmd=br0 -i eth4 @CONTAINER_NAME@ 192.168.1.211/[email protected]'

    -e 'pipework_cmd=br0 -i eth5 @CONTAINER_NAME@ 192.168.1.212/[email protected]'

    -e 'pipework_cmd=br0 -i eth6 @CONTAINER_NAME@ 192.168.1.213/[email protected]'

     

    now it has all 3 extra ips and host ip (and host mode)

     

    just in case someone is interested

    [DOCKER] Pipework

    in Docker Containers

    Posted

    thanks, i think im pretty straight forward with an VM, if deb or a libreelec one ...

    but as im really happy with the docker and i would like to keep it as simple as possible ...

    and im not really in a rush, currently i also have a octopus net with 4 tuners (wich i then would drop),

    a vu+ with 8 cable fbc tuner (currently as iptv source in TVH, but a pain to setup ...),

    so would be nice to have but not a must have now.

    And pipework seems to be a nice solution for ip´s for dockers when u want to let them talk to each other,

    just works out of the box, compared to buildin ip solution where a reverse proxy docker and the "client" dockers behind dont work anymore

    cause they cant reach each other anymore easy.

     

    thanks again for the tipps, time will tell ;)

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    Hi, may a dumb question, is it possible to assign a specific value for the disk warnings inside unassigned devices ?

     

    background, i added an nvme samsung 950pro as drive for my win 10 vm´s, all working good, just annoying cause temps are always higher

    then my default values (45°)

     

    now i could set my default up and change all my assigned drives to a lower level, but to me it would make more sence vice vers.

     

    thanks ahead for an tip.

     

    image.thumb.png.bf9f6d7e4cdb22e8c2844be5e52a4288.png

×
×
  • Create New...