Jump to content

Dirtyrobot

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by Dirtyrobot

  1. 10 hours ago, patrickstigler said:

    Hi Sorry for the delay. 

     

    I will take a look at it, but currently I am quite busy so I had no time to do something on the image. 

    Also my network interface broke (might be a software issue) but now I have to fix the build pipeline first. I will update you guys here.

    Thank you!

  2. On 2/23/2023 at 1:53 AM, hoeman said:

     

    Actually I got it right, you just have to change extra parameters to --device=/dev/dri and when you spin up the container, open OBS, settings, streaming, advanced, you will see that there's the hardware encoder available for usage. The problem now is that this container seems abandoned by the dev and the latest one has broken NDI implementation where under sources, NDI doesn't even show up. Sigh, it would be nice if @patrickstigler would come back to this.

    Bummer!

  3. On 1/19/2023 at 10:15 AM, hoeman said:

    How do I use Intel Quick Sync with this instead of Nvidia? I'd like to use my 12th gen iGPU for encoding as it actually has better quality then Turing / Ampere NVENC as shown in eposvox video

     

     

    Edit: Can anyone confirm if the way to get Intel iGPU as the encoder is to change extra parameters from --runtime=nvidia to --device=/dev/dri?

    I've been trying to get this to work but no luck :(

  4. On 10/29/2022 at 4:27 AM, ich777 said:

    First of all, I would recommend that you upgrade to 6.11.1

     

    Can you please post a screenshot form your template?

     

    Which CPU are you using? Can you post your Diagnostics?

     

    EDIT: I've now tried it on my system and it works just fine (Intel 10th gen).

    Thanks, I updated UnRAID and re-installed the container. Hardware acceleration is working now with an Intel i5-11400.

    The next problem I need to resolve is getting it to work through Traefik 🙄

    • Like 1
  5. Any Owncast users? I have it up and running but I can't seem to get it to work with Intel Quicksync. Plex on the same machine will use hardware decoding no problem. The container has the device link defined:
     

    devices:
    
      - "/dev/dri/:/dev/dri/"

     

    When I set Owncast to use hardware decoding I get the following error:

     

    Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': I/O error

     

    UnRAID 6.11.0

     

    Any ideas to point me in the right direction would be appreciated, thanks!

  6. On 7/2/2022 at 5:56 PM, _Shorty said:

    Have you selected any files/directories to attempt a job yet?  They're inaccessible until there's something selected, at which point they become clickable.

    Thanks, user error here. Turns out the drive I was selecting had no data on it.

  7. On 5/16/2022 at 10:39 AM, grigsby said:

    Hi all. I'm having a problem with the most recent homer docker container updates (https://hub.docker.com/r/b4bz/homer). The problem is described by others here: https://github.com/bastienwirtz/homer/issues/441

     

    Basically, there was a change in the docker compose file, so the latest container doesn't work on Unraid. The error is that the container runs as the incorrect user and group, so the container doesn't have read/write permissions for the appdata folder.  Adding the normal PUID and PGID environment variables doesn't work, I think because the docker compose file expects to see something in the form of "-user 99:100". Also, having the appdata folder owned by root didn't help either.

     

    I can't figure out how to update the Unraid docker template, or how to get the latest homer containers to work. For now, I've just set the tag to b4bz/homer:22.02.2, which was the last version that worked before the repo changed the format of the docker compose.

     

    Any ideas?

     

    Thank you!

    I have this problem as well. Any workaround?

×
×
  • Create New...