feederbox826

Generate doesn't use hwaccel

then you should be good! the development build is for bleeding edge stash pre-release builds. IIRC the breakage only occurred on development and patched in a later version. If you updated to 0.2 you can grab version one [here](https://github.com/feederbox826/plugins/tree/15194fbf20802e2b603340ae7fec2b9787171d17/plugins/overlay-info)

I have put in my own patch to stash and it works against the latest development build https://discourse.stashapp.cc/t/overlay-info/1602. If you're not on development then the old version should still work, if you're on development just update

Chased down some wild geese, try adding the environment variable STASH_HW_TEST_TIMEOUT and setting the value to 10

Another user also reported issues with NVIDIA, I sold off my 1060 in my server so I don't have the hardware available atm. I'll try to do some more testing on windows and will try to remember to update here as well as on github.

default should be "" (empty), you might've had an old version that has the default set to iHD, but your system is using i965. Will probably remove it as Jellyfin is much more reliable with driver selector

Phew! Glad I could help!

You might need to remove the LIBVA_DRIVER_NAME and LIBVA_DRIVER_NAME_JELLYFIN, im not sure if the driver is interpreting empty strings correctly. That's the end of my theories, will have to wait for the debug script to deploy

Let me add some more debugging for AUTO_AVGID, I have a feeling your --device flags are throwing it off, don't pass in /dev/dri after passing in /dev/dri/card0 and /dev/dri/render128, or just pass in the entirety of /dev/dri

Hm everything looks correct, try removing the Jellyfin Driver selector and Driver Selector variables in the config

can you pull the container startup logs? not from within stash but from the terminal, not everything is in the logfile yet

There you go, delete ffmpeg/ffprobe at /config, it's the version downloaded by stash which is missing hwaccel support

Can you post the startup logs for stash-s6? this is also available via stash-s6 helper with "get logs" or at /config/stash-s6.log

Try some of the steps in https://github.com/feederbox826/stash-s6/blob/main/docs/arc-troubleshooting.md but if transcoding is still working, it's probably safe to ignore

if you restart the container after removing requirements.txt it should populate it with a comment on which file it's from above it ``` # /plugins/plugin/requirements.txt spacy ```

Sorry, that's into the realm of srsly why it isn't compiling properly, if I had to guess it looks like it could be a python version they don't support. srsly and spacy arent used in any of the plugins at stashapp/CommunityScripts so it could be from another plugin index you added?

Wow, unraid really didn't like me trying to reply. g++ and dependencies are kind of a hard edge case to account for, so I've limited dependencies to what CommunityScripts has. for your case, I can't seem to find the other dependencies but this should cover it. Enter the container shell and execute the following command running as root on :alpine and :hwaccel-alpine ```sh apk add build-base python3-dev ``` on :hwaccel apt install build-essential

There has actually been an update for this, but is still only a theory https://github.com/stashapp/stash/issues/5731 HWAccel has been proven to have significant improvement in speed but will be probably quite a while before it's properly implemented and off the ground in a meaningful capacity

Nope, hwaceel is not used for generation and from a community member's tests to force it, yields little to no difference in speeds and instead adds complications.

Nope! There is a compatibility mode for running hotio/stash or stashapp/stash and migration scripts should you choose to move over. It's deailed here in the README

Alternative stashapp/stash container with hardware acceleration Links: - Comparison and breakdown between containers - hwaccel troubleshooting - stash-s6 GitHub - DockerHub