Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

Community Reputation

31 Good

About Taddeusz

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. I just installed the Nextcloud Talk plugin. It seems to work fine web client to web client. Video works fine if both clients are on the same network. Text works fine when a client is outside the network but video does not. I can't get either of the Android or iOS apps to work whether or not they are on the same network. The iOS app gives me error 405 and the Android app just says there was an error. I tried to install and configure the instrumentisto/coturn docker and configure the talk plugin to use it but I'm not sure I have coturn configured correctly. Anyone have any pointers on how to get this working correctly?
  2. I use the official Plex Docker. Any trouble I have I go here: https://forums.plex.tv/c/plex-media-server/nas-devices
  3. I don’t know if there was another forum discussion about the problem but here is the beta announcement. https://forums.plex.tv/t/plex-media-server/30447/296
  4. @rix Are you using Plex to test this? I ask because there is currently a bug in their Quick Sync code that affects 8th Gen CPU’s. It’s supposed to be fixed in the latest beta but that version is not available on their Docker container and it’s not yet released.
  5. I'm not sure how Tips and Tweaks adjusted it before but I might see the CPU frequency scaling difference. In Performance the energy_performance_preference is also being set to "performance". On Power Save it is set to "balance_performance". I'm guessing the performance energy preference essentially disables all scaling.
  6. I have an i5 8400 which I had previously set the scaling governor to Power Save. Recently I changed it to Performance and noticed that my CPU's normal idle usage is much lower. I also noticed on Performance governor my CPU seems to be pegged at the 6-core turbo frequency of 3.8Ghz rather than doing any scaling, which I'm not entirely certain is a bug or not. 6.7 would still scale the CPU on Performance but not quite as aggressively as Power Save. Maybe this is a change in the scaling driver. Idle temps have only risen about 4-6C. I'm ok with that change. Just something else I noticed. I don't know how the dashboard calculates CPU usage but it seems like it has something to do with the CPU frequency.
  7. Docker Hub has been having service disruptions yesterday and today.
  8. @Djoss I'm not sure what changed but I just noticed that it was started and is running. If it's at all a help here is the output anyway. handbrake.txt
  9. I just installed Unraid 6.8.0 rc1 this morning and went to run something through Handbrake and noticed it’s not starting.
  10. Set them to “yes” to move data to the array. Set them to “prefer” to move data to the cache.
  11. To be more specific. The shares you want to move from the cache to the array should be set to "Yes". That way the mover will move the data to the array. When you're ready to move the shares back to to the new cache you should set them to "Prefer" so that the mover will move the data to the cache. Once the mover is finished you can set those shares back to "only". Setting to "no" or "only" will not allow data to be moved between cache and array. It only tells where new data should be written. Keep in mind that any files you have outside the array such as maybe your docker.img file will need to be moved manually. I personally keep those files in, I believe what is the default location, at /mnt/cache/system/docker/docker.img. I had originally manually set it so I actually have no idea now what the default location should be. Keep in mind you might have to disable Docker and the VM Manager for it to move all your files from the cache.
  12. You can do this all with the mover by changing the "Use cache disk" option appropriately on each of the shares you have assigned to the cache drive. Then manually run the mover so it will automatically move all the files for you.
  13. I think the way I would do this is on the old system to move all the data on the cache drives back to the array. Then remove the cache drives from the configuration. Then move just the array drives to the new system. Configure the M.2 drives as the new cache. Then move everything that should be on the cache to the new drives.
  14. The left side is the original video format, in this case HEVC. That’s what it is decoding. The right side is showing that it is encoding to H.264 using hardware. Your E3 is a Haswell architecture CPU so it cannot decode or encode HEVC in hardware.
  15. @Zonediver Just to discount Quick Sync hardware acceleration out of hand because it doesn’t meet your own quality standards doesn’t mean it wouldn’t be acceptable for others in different situations. Coming on here berating others for using it is rather rude.