rix

Community Developer
 View Profile  See their activity

  • Posts

    423

  • Joined

 Content Type 

Everything posted by rix

  1. rix
    Then there is not much I can do about this without further info. Could you please send me the output of a ls command in the /tmp folder?
  2. rix
    Changed Status to Closed
  3. rix
    There seems to be a general issue with plex hardware transcoding that is likely the root cause of my report. Seems like there is nothing you guys can do on your end. More details: https://forums.plex.tv/t/plex-media-server/30447/296
  4. rix
    Thanks - this is likely the root cause of my current issue. I'll report back if that update helps solve it.
  5. rix
    Could you link me to their thread about this? This could likely be the remaining issue. Would love to close my bug report in this forum!
  6. rix
    I just started having issues with Quicksync on 6.8 (it worked smoothely on 6.7.2): Any help would be appreciated
  7. rix
    Hi all, this looks an aweful lot like my issue (that has only started after upgrading to 6.8 RC4 from 6.7). I tried applying the syslinux line as follows: default menu.c32 menu title UNRAID prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append intel_iommu=off initrd=/bzroot label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest Hardware transcoding is now starting again, as it did on 6.7.2, but the video is extremely glitched and blocky (unwatchable). Anyone else with a J4105 having the same issue on 6.8?
  8. rix
    I edited the post accordingly. Thanks for the helpful comment - this looks an awful lot like my issue, but the workaround is not working for me. Also note, that Quicksync was working fine with 6.7 for me.
  9. rix
    Yes, because once you started the image it places the ripper.sh on your disk and will not overwrite it. Delete your ripper.sh then check again.
  10. rix
    It has perfectly worked from 6.6 up until now - look up the integrated HD Graphics 600, the issue has to be something else.
  11. rix
    I have set up my server to be a low power consumption base for my Plex media server. Upon upgrading to the v6.8.0 Release Candidates (starting with the first one) hardware transcoding through Plex is broken for me. Symptoms are: Stream appears to be started, yet video is not progressing Instead of an image the screen remains black If at all, the stream starts extremely stuttery and (I kid not) in a somewhat low resolution of 16x16px (estimated) If I turn of hardware transcoding in Plex, streaming is possible again (hogging my low power CPU). Where is was previously able to serve multiple 1080p x265 streams my server now barely handles a few 720p transcodes.. It was previously working fine with the CPU listed in my signature. Only required modifications to Unraid were these lines in the go script: modprobe i915 chmod -R 777 /dev/dri The encoding device is showing up as previously. There is no informational log entry in the Unraid, Plex Docker or even Plex debug logs - hence none are attached. This post is mainly to raise awareness for the issue, since my previous comments achieved no response. Is this happening to anyone else? Any idea how to fix this or break the issue down? Any help is highly appreciated! I am most willing to assist in getting this fixed. EDiT: This is my CPU https://ark.intel.com/content/www/de/de/ark/products/128989/intel-celeron-j4105-processor-4m-cache-up-to-2-50-ghz.html ninja-diagnostics-20191024-2057.zip
  12. rix
    This requires you to remove your custom ripper.sh Or just add these lines to the file: https://github.com/rix1337/docker-ripper/commit/92cf8f62bb6d430ca07358ea21743b98022d8e68
  13. rix
    Thanks for investigating. I have updated the included ripper.sh which will now delete all .tmp files located at /tmp minutely. Docker Image should update within the next hour.
  14. rix
    Has anyone else had issues with Intel Quicksync hardware transcoding running the 6.8 rc series? Streams have stopped working for my users and if they start at all, they are extremely blocky and unwatchable.
  15. rix
    Hardware transcoding with Intel QuickSync broke for me running 6.8 - has this happened for anyone else, or might this be a Plex-Update related issue?
  16. rix
    Not currently, The script always looks for the latest release on github. This probably could be solved - but not actively by me. I will however integrate a Pull Request that does this, if one appears.
  17. rix
    Hi, this has nothing to do with the latest docker build, but rather the Version string suddenly containing a dash followed by letters. (-beta1) I have fixed the script that detects the latest version of DNScrypt https://github.com/rix1337/docker-dnscrypt/commit/93475503fa0e9e32b91244b164684af6ca1f75a0 Pull the latest docker image, once it is built an test if it now works.
  18. rix
    Happy to help - you just need patience, if I am not available for a couple of weeks.
  19. rix
    This looks wrong - the parameter needs to be passed as follows: You need to enter it in the advanced container settings And on changing what ripper does please refer to: https://github.com/rix1337/docker-ripper#how-do-i-set-ripper-to-do-something-else Just edit this line in your local ripper.sh https://github.com/rix1337/docker-ripper/blob/master/root/ripper/ripper.sh#L122 so it does not have a 2 after -c 0,2 This will only output mp3: /usr/bin/ripit -d "$DRIVE" -c 0 -W -o "$STORAGE_CD" -b 320 --comment cddbid --playlist 0 -D '"$suffix/$artist/$album"' --infolog "/log/autorip_"$LOGFILE"" -Z 2 -O y --uppercasefirst --nointeraction >> $LOGFILE 2>&1 For more info take a look at http://manpages.ubuntu.com/manpages/cosmic/man1/ripit.1.html
  20. rix
    This could be due to the verbose logging of the container. Try and add --log-opt max-size=50m as Extra parameters in the container's advanced settings. This should drastically limit the container size due to docker logs.
  21. rix
    Just ping me on github, this happens every other month.
  22. rix
    Please refer to https://github.com/rix1337/docker-ripper#makemkv-needs-an-update I have triggered said update, which should be built in ~3hours
  23. rix
    Sold mine and went with a 1080 Ti
  24. rix
    Glad you got this sorted.
  25. rix
    Not that I am aware of. Passing through /dev/sr0 is all thats required.