[Support] Linuxserver.io - Emby


82 posts in this topic Last Reply

Recommended Posts

4 hours ago, cyruspy said:

I've moved from RPM install on openSUSE to this container on unRAID, everything works fine from an ShieldTV client once it loads, but initial loading of the server connection is kinda slow (10's of seconds).

 

I don't recall having this initial delay before, does it sound familiar?, is there anything I can tweak to fix that?

I have no problem here on a shield, so it must be something local to you.

Do you have the appdata on the array? If so, it might be spinning up the disks.

Link to post
  • 3 weeks later...
  • Replies 81
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Application Name: Emby Application Site: https://emby.media/ Docker Hub: https://hub.docker.com/r/linuxserver/emby/ Github: https://github.com/linuxserver/docker-emby   Ple

We've made it easier to get Nvidia & iGPU hardware trancoding working with this container.  This post will detail what you need to do to use either of these in your container. (Emby Premiere Requi

At the heart of it, there is no fundamental difference.  ie: Emby is emby is emby.   Difference lies in some subtleties. and as @jonathanm stated support regarding hardware transcoding.

Posted Images

On 8/10/2020 at 2:18 AM, saarg said:

I have no problem here on a shield, so it must be something local to you.

Do you have the appdata on the array? If so, it might be spinning up the disks.

It takes around 25 seconds from application launch to login stage. The data is on SSD cache, also any following retries take the same time.

 

Once logged in, it's quite snappy.

Edited by cyruspy
Link to post
14 hours ago, cyruspy said:

It takes around 25 seconds from application launch to login stage. The data is on SSD cache, also any following retries take the same time.

 

Once logged in, it's quite snappy.

Are you absolutely sure it's on the ssd? It sounds like it's on a spinner and it spins up.

Link to post
8 hours ago, saarg said:

Are you absolutely sure it's on the ssd? It sounds like it's on a spinner and it spins up.

 

user@nas03:/mnt/user/downloads/done$ ls -l /mnt/cache/appdata/emby/
total 0
drwxr-xr-x 1 user users  566 Aug 27 02:00 cache/
drwxr-xr-x 1 user users  130 May 25 15:37 config/
drwxr-xr-x 1 user users  670 Aug 30 03:17 data/
drwxr-xr-x 1 user users 2716 Aug 30 03:17 logs/
drwxr-xr-x 1 user users   24 May 17 12:13 metadata/
drwxr-xr-x 1 user users  676 May 25 15:39 plugins/
drwxr-xr-x 1 user users   54 Jun 16 00:00 plugins\\\\Statistics/
drwxr-xr-x 1 user users   14 May 17 00:38 root/
drwxr-xr-x 1 user users    0 Aug 30 03:17 transcoding-temp/

 

Link to post
14 hours ago, cyruspy said:

 


user@nas03:/mnt/user/downloads/done$ ls -l /mnt/cache/appdata/emby/
total 0
drwxr-xr-x 1 user users  566 Aug 27 02:00 cache/
drwxr-xr-x 1 user users  130 May 25 15:37 config/
drwxr-xr-x 1 user users  670 Aug 30 03:17 data/
drwxr-xr-x 1 user users 2716 Aug 30 03:17 logs/
drwxr-xr-x 1 user users   24 May 17 12:13 metadata/
drwxr-xr-x 1 user users  676 May 25 15:39 plugins/
drwxr-xr-x 1 user users   54 Jun 16 00:00 plugins\\\\Statistics/
drwxr-xr-x 1 user users   14 May 17 00:38 root/
drwxr-xr-x 1 user users    0 Aug 30 03:17 transcoding-temp/

 

That just shows files on the cache disk. It doesn't mean there is no files on the array. Check the share settings and also click the browse icon on the share to see which drives the files reside on.

Link to post
13 hours ago, cyruspy said:

 

image.thumb.png.2c037c6356d920d11f6543b169c26175.png

You should set use cache: only

That is most likely your problem. You also need to check on which drives the date is on so you can move it.

Edited by saarg
Link to post
  • 2 months later...

With the latest update i cant scan new media. It finds the media, but can't read what kind it is. And it wont play on Shield / Web. Media previously scaned works.

 

I went back to linuxserver/emby:4.5.2.0-ls59 And all is working like before again.

 

Link to post
22 minutes ago, jowe said:

With the latest update i cant scan new media. It finds the media, but can't read what kind it is. And it wont play on Shield / Web. Media previously scaned works.

 

I went back to linuxserver/emby:4.5.2.0-ls59 And all is working like before again.

 

You are a star! thank you! I was looking to roll back to the previous version but could not find a way 

Link to post

Something is definitely broken in the latest build. Below are errors from trying to run a library scan:

2020-11-12 17:59:12.921 Info FfmpegManager: FFMpeg: /app/emby/ffmpeg
2020-11-12 17:59:12.921 Info FfmpegManager: FFProbe: /app/emby/ffprobe
2020-11-12 17:59:12.921 Info FfmpegManager: FFDetect: /app/emby/ffdetect
2020-11-12 17:59:12.932 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Execute: /app/emby/ffmpeg -hide_banner -version
2020-11-12 17:59:12.977 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Process exited with code 127
2020-11-12 17:59:12.978 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Output:
	
2020-11-12 17:59:12.978 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Error Output:
	/app/emby/ffmpeg: error while loading shared libraries: liblibsmb-samba4.so: cannot open shared object file: No such file or directory
	
2020-11-12 17:59:12.983 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -decoders' Execute: /app/emby/ffmpeg -hide_banner -decoders
2020-11-12 17:59:12.985 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -decoders' Process exited with code 127
2020-11-12 17:59:12.985 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -decoders' Output:
	
2020-11-12 17:59:12.985 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -decoders' Error Output:
	/app/emby/ffmpeg: error while loading shared libraries: liblibsmb-samba4.so: cannot open shared object file: No such file or directory
	
2020-11-12 17:59:12.986 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -encoders' Execute: /app/emby/ffmpeg -hide_banner -encoders
2020-11-12 17:59:12.988 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -encoders' Process exited with code 127
2020-11-12 17:59:12.988 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -encoders' Output:
	
2020-11-12 17:59:12.988 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -encoders' Error Output:
	/app/emby/ffmpeg: error while loading shared libraries: liblibsmb-samba4.so: cannot open shared object file: No such file or directory
	
2020-11-12 17:59:13.012 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -hwaccels' Execute: /app/emby/ffmpeg -hide_banner -hwaccels
2020-11-12 17:59:13.014 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -hwaccels' Process exited with code 127
2020-11-12 17:59:13.014 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -hwaccels' Output:
	
2020-11-12 17:59:13.014 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -hwaccels' Error Output:
	/app/emby/ffmpeg: error while loading shared libraries: liblibsmb-samba4.so: cannot open shared object file: No such file or directory
	
2020-11-12 17:59:13.015 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -protocols' Execute: /app/emby/ffmpeg -hide_banner -protocols
2020-11-12 17:59:13.017 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -protocols' Process exited with code 127
2020-11-12 17:59:13.017 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -protocols' Output:
	
2020-11-12 17:59:13.017 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -protocols' Error Output:
	/app/emby/ffmpeg: error while loading shared libraries: liblibsmb-samba4.so: cannot open shared object file: No such file or directory
	
2020-11-12 17:59:13.017 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -filters' Execute: /app/emby/ffmpeg -hide_banner -filters
2020-11-12 17:59:13.020 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -filters' Process exited with code 127
2020-11-12 17:59:13.020 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -filters' Output:
	
2020-11-12 17:59:13.020 Error FfmpegManager: ProcessRun 'ffmpeg -hide_banner -filters' Error Output:
	/app/emby/ffmpeg: error while loading shared libraries: liblibsmb-samba4.so: cannot open shared object file: No such file or directory

Logs are similar when trying to play anything requiring transcoding. Errors about ffmpeg not found, read-only filesystem, etc.

Link to post

I'm having issues, too. Recordings from HDHomerun (*.ts files) give a playback error (No compatible streams available). Emby is set to use quicksync, but in Settings, Transcoding, switching to Advanced doesn't show any hardware encoders/decoders available.

 

I rolled back to linuxserver/emby:4.5.2.0-ls59, as suggested above. Hardware shows back up and recordings play again.

 

Link to post

So with the latest Unraid beta release (6.9 beta 35), GPU drivers have been added to the OS.

 

I had a quick stab at getting an AMD GPU passed through to the lsio Emby Docker, but have run in to an issue.

 

I enabled the AMDGPU driver on Unraid, I installed the lsio Emby Docker with the `/dev/dri/` device added.

 

Emby Server shows my GPU available for transcoding (I have Emby Premiere so no restriction on transcode).

 

I started a transcode job, and it was using the CPU, not GPU to transcode.

 

Looking at the transcode log, it looks like it attempted to open the GPU for transcoding, but failed and fell back to CPU.

 

I've attached the Emby transcode log, but the first error that occurs is:

/home/embybuilder/Buildbot/x64/libdrm-x64/staging/share/libdrm/amdgpu.ids: No such file or directory

Then FFMPEG fails with some sort of I/O error.

 

I had a look in the docker container, and the `/home/embybuilder` directory did not exist...

 

Is there something else I should be doing to get this working?

ffmpeg-transcode-646aefab-ad63-4910-a5d6-fc108c6b9031_1.txt

Link to post
  • 3 weeks later...

Hey there,

 

I'm using the latest lsio container with Unraid 6.8.3.

To get HW transcoding running with my J4105, I have to use this workaround: 

 

cd /app/emby/dri
mv mv iHD_drv_video.so iHD_drv_video.so.disabled

Unfortunately, I have to do this again after updating the container. Is there a quick and easy way, to keep this workaround?

 

Link to post
6 minutes ago, olfolfolf said:

Hey there,

 

I'm using the latest lsio container with Unraid 6.8.3.

To get HW transcoding running with my J4105, I have to use this workaround: 

 


cd /app/emby/dri
mv mv iHD_drv_video.so iHD_drv_video.so.disabled

Unfortunately, I have to do this again after updating the container. Is there a quick and easy way, to keep this workaround?

 

 

I use the User Scripts plugin to run this script every hour - although maybe there's a more clever solution using Post Arguments in the docker template?

#!/bin/bash

# EmbyServer
#
# Verify it's running
running=`docker container ls | grep EmbyServer | wc -l`
if [ "${running}" != "0" ]; then
  docker exec EmbyServer /bin/sh -c "mv /lib/dri/iHD_drv_video.so /lib/dri/iHD_drv_video.so.disabled" 2>/dev/null
  if [[ $? -eq 0 ]]; then 
    echo "EmbyServer: Detected iHD driver. Disabling and restarting EmbyServer..."
    docker restart EmbyServer
    echo "Done."
  fi
fi

exit 0

 

Link to post
On 11/16/2020 at 12:58 AM, flexage said:

So with the latest Unraid beta release (6.9 beta 35), GPU drivers have been added to the OS.

 

I had a quick stab at getting an AMD GPU passed through to the lsio Emby Docker, but have run in to an issue.

 

I enabled the AMDGPU driver on Unraid, I installed the lsio Emby Docker with the `/dev/dri/` device added.

 

Emby Server shows my GPU available for transcoding (I have Emby Premiere so no restriction on transcode).

 

I started a transcode job, and it was using the CPU, not GPU to transcode.

 

Looking at the transcode log, it looks like it attempted to open the GPU for transcoding, but failed and fell back to CPU.

 

I've attached the Emby transcode log, but the first error that occurs is:


/home/embybuilder/Buildbot/x64/libdrm-x64/staging/share/libdrm/amdgpu.ids: No such file or directory

Then FFMPEG fails with some sort of I/O error.

 

I had a look in the docker container, and the `/home/embybuilder` directory did not exist...

 

Is there something else I should be doing to get this working?

ffmpeg-transcode-646aefab-ad63-4910-a5d6-fc108c6b9031_1.txt 48.16 kB · 0 downloads

I have the same issue with you, hope some one can dial it out, hw transcoding with amdgpu in emby.

Edited by rallos_hoo
Link to post
  • 1 month later...
On 11/15/2020 at 11:58 AM, flexage said:

So with the latest Unraid beta release (6.9 beta 35), GPU drivers have been added to the OS.

 

I had a quick stab at getting an AMD GPU passed through to the lsio Emby Docker, but have run in to an issue.

 

I enabled the AMDGPU driver on Unraid, I installed the lsio Emby Docker with the `/dev/dri/` device added.

 

Emby Server shows my GPU available for transcoding (I have Emby Premiere so no restriction on transcode).

 

I started a transcode job, and it was using the CPU, not GPU to transcode.

 

Looking at the transcode log, it looks like it attempted to open the GPU for transcoding, but failed and fell back to CPU.

 

I've attached the Emby transcode log, but the first error that occurs is:


/home/embybuilder/Buildbot/x64/libdrm-x64/staging/share/libdrm/amdgpu.ids: No such file or directory

Then FFMPEG fails with some sort of I/O error.

 

I had a look in the docker container, and the `/home/embybuilder` directory did not exist...

 

Is there something else I should be doing to get this working?

ffmpeg-transcode-646aefab-ad63-4910-a5d6-fc108c6b9031_1.txt 48.16 kB · 0 downloads

 

I pulled out an old Radeon card I had kicking around to play with and see if I could get it to work with Jellyfin

 

I'm on RC2 now, setup the driver modprob.d thing

 

From Jellyfin docs (basically same as Emby), you need to use this parm on the docker container:


 

--device /dev/dri/renderD128:/dev/dri/renderD128 

--device /dev/dri/card0:/dev/dri/card0

 

I did that, enabled VAAPI encoding in Jellyfin and tried playing a file.. it seems to be picking up the card, but transcoding is slooooow

 

I'm thinking maybe my Radeon is just too old and doesn't support enough to do the job, not sure... but does seem to be trying to use it, my cpu didn't do much at all while this was happening

 

ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9 (Ubuntu 9.3.0-17ubuntu1~20.04)
  configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --disable-doc --disable-ffplay --disable-shared --disable-libxcb --disable-sdl2 --disable-xlib --enable-gpl --enable-version3 --enable-static --enable-libfontconfig --enable-fontconfig --enable-gmp --enable-gnutls --enable-libass --enable-libbluray --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libdav1d --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --arch=amd64 --enable-opencl --enable-vaapi --enable-amf --enable-libmfx --enable-vdpau --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvenc --enable-nvdec --enable-ffnvcodec
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'file:/movies/21 Jump Street (2012)/21 Jump Street (2012).720p.x264.AAC.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    creation_time   : 2016-07-02T13:36:10.000000Z
    title           : 21.Jump.Street.2012.720p.BluRay.H264.AAC-RARBG
    encoder         : Lavf56.40.101
    comment         : 21.Jump.Street.2012.720p.BluRay.H264.AAC-RARBG
  Duration: 01:49:37.66, start: 0.000000, bitrate: 1731 kb/s
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x544 [SAR 1:1 DAR 40:17], 1500 kb/s, 23.98 fps, 23.98 tbr, 11988 tbn, 47.95 tbc (default)
    Metadata:
      creation_time   : 2016-07-02T13:36:10.000000Z
      handler_name    : VideoHandler
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 223 kb/s (default)
    Metadata:
      creation_time   : 2016-07-02T13:36:10.000000Z
      handler_name    : SoundHandler
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_vaapi))
  Stream #0:1 -> #0:1 (aac (native) -> mp3 (libmp3lame))
Press [q] to stop, [?] for help
[h264_vaapi @ 0x55cdfe839980] Driver does not support some wanted packed headers (wanted 0xd, found 0).
[h264_vaapi @ 0x55cdfe839980] Driver does not support packed sequence headers, but a global header is requested.
[h264_vaapi @ 0x55cdfe839980] No global header will be written: this may result in a stream which is not usable for some purposes (e.g. not muxable to some containers).
Output #0, hls, to '/transcode/4ec8b4af326024ebb7f8e27377b1b2ca.m3u8':
  Metadata:
    encoder         : Lavf58.45.100
    Stream #0:0: Video: h264 (h264_vaapi) (High), vaapi_vld, 640x272 [SAR 1:1 DAR 40:17], q=-1--1, 776 kb/s, 23.98 fps, 90k tbn, 23.98 tbc (default)
    Metadata:
      encoder         : Lavc58.91.100 h264_vaapi
    Stream #0:1: Audio: mp3 (libmp3lame), 48000 Hz, stereo, fltp, 223 kb/s (default)
    Metadata:
      encoder         : Lavc58.91.100 libmp3lame
frame=    2 fps=0.0 q=-0.0 size=N/A time=00:00:00.30 bitrate=N/A speed=0.343x    
frame=    3 fps=2.1 q=-0.0 size=N/A time=00:00:00.36 bitrate=N/A speed=0.256x    
frame=    4 fps=2.1 q=-0.0 size=N/A time=00:00:00.40 bitrate=N/A speed=0.214x    
frame=    5 fps=2.1 q=-0.0 size=N/A time=00:00:00.45 bitrate=N/A speed=0.188x    
frame=    6 fps=2.1 q=-0.0 size=N/A time=00:00:00.50 bitrate=N/A speed=0.173x    
frame=    7 fps=2.0 q=-0.0 size=N/A time=00:00:00.52 bitrate=N/A speed=0.154x    
frame=    8 fps=2.0 q=-0.0 size=N/A time=00:00:00.57 bitrate=N/A speed=0.146x    
frame=    9 fps=2.0 q=-0.0 size=N/A time=00:00:00.62 bitrate=N/A speed=0.141x    

 

Link to post
  • 4 months later...

Hello,  I've been running the 4.6 beta and now that it's released I'd like to switch to the released version (4.6.50).  When I change the tag from beta to latest, the docker downloads 4.5.  Does lsio need to do something to the docker to indicate that the release is 4.6.50?

Link to post
15 minutes ago, Adam64 said:

Hello,  I've been running the 4.6 beta and now that it's released I'd like to switch to the released version (4.6.50).  When I change the tag from beta to latest, the docker downloads 4.5.  Does lsio need to do something to the docker to indicate that the release is 4.6.50?

The latest version we released is 4.6.0.50, so you haven't updated your container. It's probably just using the latest version you had on your system, so do a force update.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.