Jump to content

soder

Members
  • Posts

    65
  • Joined

  • Last visited

Posts posted by soder

  1. 8 minutes ago, nickp85 said:

    Did you pick "plex" from the list of templates? It's definitely maintained.

    After uninstalling Plex, and removed the docker file, I went to "apps", searched for Plex and tock the version from linuxserver's Repository, and there the version "on top" that was "docker" in VERSION and "lscr.io/linuxserver/plex" in repo (the lscr.io part is new for me).

     

    After that, the path I had before was gone, and I noticed a small difference in the layout from my previous version...

     

    Anyhow, now I'm back, adding my media as path and transcode to /dev/shm

  2. 4 minutes ago, nickp85 said:

    Shouldn't matter the Plex version you pick, the fix is part of the container. Linuxserver is laying down the bits for this part, not Plex. I am currently using the linuxserver/plex repo with version latest since I am a PlexPass subscriber.

    I'm a plexpass subscriber as well, but this spring someone told me to use "plexpass" as version to get the fix for that HDR tone mapping problem.

     

    But I now switched back to linuxserver/plex as repo, and "plexpass" as VERSION, and that took me back to non working HDR tone mapping.

     

    Gonna try "latest" as version.

     

    EDIT: It didn't worked. What else do I need to do in Unraid, then "edit" my Plex docker, and changing repo and version?

     

    /Söder

  3. 28 minutes ago, nickp85 said:

    The Linuxserver Plex container. I did also have to delete my Plex image and re-add it but now working flawlessly on 9900K without any scripts or messing around.

    I changed repository to fix this problem, from linuxserver/plex, with VERSION plexpass, to lsiodev/plex:amd64-1.25.2.5319-c43dc0277-pkg-c2e7263a-dev-2f08980441f26b55db4d95db8ee42c958882cc36.

     

    If I now want to switch back to repo linuxserver/plex, what shall I put in VERSION to get the fix one? Is it "plexpass", or "latest" or "docker" or "public"?

     

    /Söder

  4. 6 hours ago, thunderclap said:

    I'm trying to get Quick Sync working properly with Plex. I've got everything set up properly, however when I try to transcode a 4k file it always reverts to the CPU (a Core i7-9700K) instead of the iGPU like I want. However, when it's a non-4k file it works properly. See the attached screenshot.

     

    transcode.png.30942ec8b3832033ae42867178cfe4fd.png

     

    Any idea how to get the system to transcode 4k like it does other content?

     

    Update: Upon experimenting, it seems if I disable Enable HDR tone mapping everything works fine, however the colors are muted a bit and don’t pop like they should. 

     

    Update 2: It's Plex. After a lot of searching I stumbled upon a post in the Plex forum. Rolling back to version 1.25.1.5286-34f965be8-ls91 fixes the problem.

     

    Yes, there's a bug right now with HDR tone mapping and HW transcoding (again, had this problem in the spring 2021 as well). But for me downgrading PMS doesn't work now.

     

    /Söder

  5. All of a sudden I've noticed that my HW transcode doesn't work for HDR tone mapping any longer, just like the problem with PMS the spring 2021. What can it be causing this? My HW transcoding work for non HDR movies or if I turn of HDR Tone Mapping in the settings for Plex.

     

    Here's the thread about the HW problem from this spring...

     

    /Söder

     

  6. On 4/29/2021 at 3:01 AM, BrianL said:

    I'm so sorry to ask this question for the 8 million time, I appreciate your patience.  Complete noob here when it comes to Unraid and Plex.

     

    When I first built this machine:

    Asus Tuf H470 -PRO

    i5-10400

    (no discrete GPU)

     

    UNRAID version was initially 6.9.1 (at some point went to 6.9.2)  - starting version could have been 6.9.0, don't remember

     

    Tried reverting Unraid from 6.9.2 to 6.9.1, didn't help.

     

    Using the official PLEX repository

    Plex Version 1.22.3.4392  (not the version I started with)

     

    A few weeks back - I initially followed the steps on the first page and was successful in enabling HW transcoding with the intel iGPU.

     

    Just recently I noticed it's not working anymore (no more HW indication and high CPU usage numbers)

     

    I have tried countless things, tried the new steps above.  However, no idea how to downgrade the Plex version (so not everything from above).  

     

    Didn't seem to need an HDMI fake monitor do-dad, previously worked without it.  Tonight, I Tried hooking up a monitor to see if that was the issue.  Still can't get it to work.

     

    Could downgrading the Plex version help and how do I do that?

     

    Appreciate all the help.

     

    Brian.

     

     

    ****UPDATE****

     

    It seems that it is only 4K HDR files that I am having trouble with.  4K in standard DR seem to be ok for transcoding via the iGPU.

     

    This requires that PLEX version downgrade?

     

    Check my post above, where I find out how to downgrade. It's just to change "latest" to a specific version you want, and press Apply. Then the docker is rebuilt.

     

    I've read that the newer version 1.23 should have fixed this problem with 4K HDR hw to SDR issue, but the docker is still not updated to 1.23.

      

    image.png

     

    /Söder

  7. 39 minutes ago, TopherHax said:

    If you have an issue HDR to SDR tonemapping then downgrade plex to version 1.22.0.4163

     

    There's a bug in plex, they are currently working on fixing it but until then downgrade is best solution.

    But, how do I do that in Unraid with Plex in docker? Is there an easy way?

     

    Edit: I'm using this docker (are there any differences on the dockers, anyone I should use instead?). https://hub.docker.com/r/linuxserver/plex/ and when when changing from "latest" to "1.22.0.4163" in VERSION on the "edit docker page" in Unraid and press Apply, I'm still on Version 1.22.2.4282 in app.plex.tv when I'm checking from a browser.

     

    Edit2: Is it version-1.22.0.4163-d8c4875dd I shall write instead? Or do I need to specify more?

     

    Edit3: 1.22.0.4163-d8c4875dd was the exact line. Now I'm down do the working version.

     

    When Plex has fixed the problem, what is the best version to be on then? docker, latest or public?

     

    /Söder

    • Thanks 2
  8. So, can someone please help to to straighten some things out for me.

     

    Also for me HW has stopped working for 4k videos HDR to SDR with tone mapping on in Plex settings. For other stuff HW works.

     

    In my GO file I've had that modprobe line, even after the update to 6.9.1 but I've also still got the /dev/dri folder.

     

    I've read that the problem in some way may be with Plex, and not an Unraid error?

     

    So, what should I do now? I've removed the modprobe line in the GO file, and in my Plex settings I still use the --device=/dev/dri as Extra Parameters, and after a reboot I still got that folder.

     

    image.png.9f55a1177b6e17cff510733c22b22912.png

     

    My HW still works, as long as I don't enabled the HDR tonemapping setting again.

     

    Got a i3 10100, worth mentioning...

     

    /Söder

  9. Hmm, I did a pretty stupid thing today.

     

    In my array I got 5 disks, but for my share "media" I only use two disks. For many years I've had ProFTTd installed, and for my user I had the path /mnt/user/FTP and the FTP folder was a share called FTP.

     

    That shared was set to "prefer" for the cache, but also that it was for all the disks. I today changed that setting to yes, meaning that when mover started, and it didn't fit on the cache, it started to move the stuff in FTP (that is, my media) in to new disks...

     

    I had to stop the mover, and then with unbalance get the folders back the disks where media should be.

     

    So, what is the best way for me to have this FTP? I want the user to get to my media. Should I set that folder as my user path then?

     

    EDIT: What I now did was to umount my media I had to the /mnt/user/FTP folder, and then removed the share FTP. I can now again just add the FTP folder on /mnt/cache I guess..

     

    But is there a way for my to have the FTP folder as a smb share without have an unraid share like I had before?

     

    EDIT2: It's now clear for my that when I create a folder in /mnt/cache, there is also a share in unraid created.

     

    What's the best way then for me if I don't want to risk the same thing again, with different cache pool settings for FTP and media share?

     

    /Söder

  10. Thanks. I just found out that I hade debug on for my Plejd (lights).

     

    Edit: Also, that I logged all with the Logger: option in .conf..

     

    /Söder

     

     

  11. I've been using Home Assistant as Docker in my UnRaid for some years now, and I once in a while having problem with my Docker image running out of space. Now I've found out that it has something to do with my Home Assistant.

     

    First of all when I did this the size went back to normal.

    truncate -s 0 /var/lib/docker/containers//-json.log

     

    I then in UnRaid noticed that it's Home Assistant that grows in log size. It grows with 0.1 GB in an hour? (But also, I was 45 days ago I had this problem the last time).

     

    image.png.709b83b1cdb2a6707c0a09c7f965ecbb.pngScreenshot 2020-10-30 at 13.00.24

    image.png.69d2d21c8177b5320d1521f37f8090b6.pngScreenshot 2020-10-30 at 14.05.11

     

    This is my settings for the Docker, and the appdata is on my cache disk, where also my Docker img is I think, but it's not the disk that is running out of space, but the docker with a fixed size of 35GB or something like that.

     

    image.png.5408952e9cc160b6474ad8f90c282ccc.png

     

    When I check the dockers this way

    image.png.1bff90cadb99b47eee1d545c9c2d5056.png

     

    It's like I'm only in the app data, and not in the Docker img, as I thought this way should do?

     

    image.png.21d2c02d452c0adbacc0723ff1f82264.png

     

    It's like the same as in app data..

    image.png.c343b22f843b9bea2c562919abfd8afa.png

     

     

    Should I do something else, and what can I do to fix this log problem filling up my Docker Img?

     

    Thanks.

     

    /Söder

     

     

    image.png

  12. 20 minutes ago, a_n_d_y said:

    Nice!

     

    Just follow the integration for it here:

    https://www.home-assistant.io/integrations/deconz/

     

    And the devices will pop up and be available in HA to do your bidding. Really easy!

    I'm reading that right now, but there's nothing popping up for me in the HA interface on reboot.. 

    There's nothing else I should do with the docker now when I got the deCONZ interface working and finding sensors?

     

    EDIT: I did the API thing, and then in HA I could find it and the sensor. 😃

    Thanks.

     

    /Söder

  13. 36 minutes ago, a_n_d_y said:

    I believe sudo usermod -a -G dialout $USER adds the current user (root in your case) to the dial out group.

     

    The docker should be running under root unless your specifically assign it a different user to run under  (I'm not sure how to do that, but I'm running mine with the default user fine).

     

    I used ls -l /dev/serial/by-id to get the serial ID. As long as you don't plug the Conbee into a different USB port than the one its in now in the future, what you have should work fine.

     

    Once you log into Phoscon > Hamburger Menu > Settings > Gateway, if it shows a firmware number, its connected. Otherwise it will say "not connected"

    Great. It's live for me. I even found my first unit (Aqara Termometer och hygrometer) in a couple of seconds. 😃

     

    I will now spend some time to get these units in to Home Assistant in some way. 😃

     

    /Söder

  14. 21 hours ago, a_n_d_y said:

    In Community Apps, search for deconz and click the Click Here To Get More Results From DockerHub and install the container from marthoc.

     

    You'll want to set Network Type to Host.

     

    At the bottom of the page will be the link Add another Path, Port, Variable, Label or Device. It does what it says.

     

    Add the container path /root/.local/share/dresden-elektronik/deCONZ to point to your config directory, ex. /cache/appdata/deconz

     

    You'll also want to pass your device into the container. I just use the Extra Parameters field to do this: --device=/dev/[your_device]

     

    Then pass any of the environment variables you need listed on this page (passing them all is fine, just define the values):

    https://hub.docker.com/r/marthoc/deconz/

     

    The Conbee II defaults to the device name /dev/ttyACM0. If you have another USB device like an Aeotec Zstick, it will also try to assign itself  /dev/ttyACM0 or  /dev/ttyACM1 (depends on which device is assigned first upon boot).

     

    Read this about setting a persistent name if thats the case:

    https://forums.unraid.net/topic/71372-usb-passthrough-device-location-changing/

     

    Then add the Environment Variable DECONZ_DEVICE and enter the value of your persistent name, ex. /dev/[persistent_name]

     

    Make sure to telnet into your server and add the user to the dial out group the Drahznar suggested above.

     

    If you're having problems with the device connecting in the container, try updating the firmware. I did my firmware update in Windows as I couldn't get it to flash successfully using the docker firmware method described on the docker page.

     

    Attached is how I setup my container.

    Screen Shot 2020-01-02 at 2.37.30 PM (2).png

    About "adding the user to the dial out", the "sudo usermod -a -G dialout $USER", if I use the terminal from within the unraid interface, I'm root.

     

    Does that mean I just should do "sudo usermod -a -G dialout root" ?

     

    I've got the docker running now, and bought the Conbee II stick today and plugged it in the server. lsusb points me to

    Bus 002 Device 005: ID 1cf1:0030 Dresden Elektronik 

    and I've set "/dev/bus/usb/002/005" in the deCONZ device and rebuilded the docker.

     

    How should it look in the deCONZ interface if the server and software recognizes the usb-stick?

     

    Thanks.

     

    EDIT: I changed my device to /dev/ttyACM0 and now it worked. The /dev/bus/usb path is for something else?

     

    /Söder

×
×
  • Create New...