macem

Members
  • Posts

    6
  • Joined

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

macem's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Sorry @auvevo, I don't have anything else than an Android device, Chromecast or LG WebOS (which sadly doesn't have a dedicated Jellyfin app released yet for testing). In general I use H.264 which is good enough for me, but notice @Phoenix Down suggested an alternative.
  2. Here I am reading on the forum, testing everything in browser / Android app and still don't understanding what is happening 🙃 But apparently Jellyfin indeed optimises their replay option. When I tried streaming to Chromecast (which I rarely use), I noticed it started to use streaming, which is also displayed in the Intel GPU Tool. Thanks all for ruling out any possible errors for me and the quick responses!!
  3. Thanks for the quick response! I am only using an Intel i5-3470, without any other GPU installed. Changed to what you suggested in the go file without the chmod, and updated the docker extra parameter to '--device=/dev/dri' and rebooted the server. In Jellyfin my setting for VAAPI is '/dev/dri/renderD128'. After the reboot I was still able to enter the folder and also the command in _Console did start the HW enabled transcoding. But when playing from the Android App, it still uses the CPU with 'Direct Play' instead of the HW transcoding. Only thing I noticed is that you suggest the extra parameter as '--device=/dev/dri', while I am using a [space] after the [=] sign, which would result in '--device=/dev/dri'. When I tried to remove this space before, I would get an error and needed to reinstall the docker, but now I am able to save the docker. The result however is only a change from 'Direct Play' to 'Direct Streaming', but still without using the HW transcoding when looking at Intel GPU Tools.
  4. I am also "one of them" spending my whole day trying to get HW transcoding to work 😏 As far as I can tell, I did all the recommendations in the various threats, but when I play a .mkv I don't see my HW is being used. What I did so far: I am using an Intel CPU with QuickSync support Added the following to my go file using the CA Config File editor and rebooted Unraid modprobe i915 chmod -R 777 /dev/dri Added --device=/dev/dri:/dev/dri to the extra parameters of the Jellyfin docker Enabled HW transcoding, using VAAPI and restarted Jellyfin When I hit the command /dev/dri I can access the folder (both from the server Terminal aswell in the Jellyfin _Console) When I hit the command in the Jellyfin _Console for a HW transcode (thanks @sir_storealot), I see it starts using the HW transcoder using the Intel GPU tools Even updated from Unraid 6.8.0 to Unraid 6.9.0 b35,rebooted the server, and hit the command to enable i915 support and did steps 5 and 6 again When I however start playing the same .mkv from the web-browser or the Android app of Jellyfin, it only uses my CPU and shows 'Direct Play'. When I look at the Intel GPU tools, it is also only using the CPU instead of the engine. Sorry for the details, but wanted to show what I did and not just gave up the first time it didn't work... Any suggestions what I am missing here?
  5. I actually hope Mace's actually keeps the EAP-Controller supported for v3.2.10 as it stands, as the upgrade to the Omada Controler v4.x.x doesn't support older v1 access points (like me). See more details on compatibility support over here: https://www.tp-link.com/en/omada-sdn/compatibility/ In case Mace (or someone else) would like to add support for v4.x.x anyway, either let there be an option to continu using v3.2.10 or create a second Docker.
  6. Sorry for the n00b question here, but can anyone direct me to a guide or idiot-proof step-by-step guide on how to deploy the app? I need to provide credentials to a mysql DB, but not sure if this is part of the container or if I need to use another docker app / VMware for this?