Jump to content

dee31797

Members
  • Content Count

    236
  • Joined

  • Last visited

Community Reputation

29 Good

About dee31797

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Hi, The first half of the process is motion detection and it will be the majority of your CPU usage. Motioneye uses the application "Motion" to detect changes in the video. The more camera feeds, the more CPU usage and it's all software based. Once motion is detected and motioneye is set to record video on said motion, Motioneye either encodes the video to a new video codec or you can use passthrough to save the video in the original codec. Encoding of the video can be done with a hardware device if available and supported. For hardware accelerated encoding you must pass a hardware device to the container. For example, V4L2M2M requires a hardware device that's typically located at "/dev/videoX" and must be mapped to the container. I've only seen V4L2M2M with ARM based SBC's such as the Odroid XU4 hardware accelerated encoding (reference https://github.com/ccrisan/motioneye/releases/tag/0.42). Other options supported by motioneye are Nvidia's NVENC (requires a Nvidia GPU) and Intel's QSV (requires an Intel iGPU apart of an Intel CPU). Even though ffmpeg has options such as VAAPI (also GPU based), Motioneye does not support it. Here's the catch, even if you do have a Nvidia GPU or Intel iGPU to map to this container, since this container image is based on Alpine linux it doesn't have support for it. So to use hardware encoding I recommend you use the docker container that's created by Motioneye's original author, located at https://hub.docker.com/r/ccrisan/motioneye . It's based on Ubuntu so it's 3 times the size of my container. I haven't tested it myself (I use passthrough video setting personally) but I believe his container does support hardware encoding. As we mentioned once you install his container you have to map a supported GPU to his container before hardware accelerated encoding will work.
  2. Thank you! Currently there's no options for the audio but I will look into adding something like that in the future.
  3. click "clipboard" in the top right click text box, press ctrl + v on your keyboard to paste text you desire the container to have click submit in the uget wegui go to where you need the text, press ctrl + v on your keyboard to paste text you desire edit: the container is still usable with pasting text.
  4. I can help with the file system, but you're going to have a tough time with this container. It's an advanced setup running a web server, dhcp server, text based configuration via config files. The docker container settings (in Unraid GUI) has a list of volumes, variables, devices, etc and are managed by you. In this specific instance you need to add "/etc/dhcp/dhcpd.conf" to the docker container. The most common why this is done is with an appdata folder, "/mnt/user/appdata/glasss-isc-dhcp/dhcpd.conf" mapped to "/etc/dhcp/dhcpd.conf", but the choice is yours use whatever host directory you desire. Once your selection is made, use the Unraid GUI docker settings to change the host path to your selection and the container path should already be filled in when you installed the container. For an more in depth explanation on docker settings and volumes please see https://wiki.unraid.net/UnRAID_6/Docker_Management
  5. Yes, the directory exists on your machine, you access them however you wish. The docker container only sees them as a mapped volume. If not mapped from your machine to the docker container, then they don't exist.
  6. I believe the issue that causes it to shutdown is the missing dhcp configuration file, log message "dhcpd-pools: parse_config: /etc/dhcp/dhcpd.conf: No such file or directory" WIthout this file the DHCP server will not start as well as glass admin. For a sample config file, see www.github.com/djaydev/docker-glass-isc-dhcp/blob/master/sample.dhcpd.conf
  7. If the MakeMKV ripped DVDs are .ts files then Recordings-autoconverter will convert them. If they are not .ts files, you will have to use a different program like unmanic, handbrake, tdarr, or H265ize. I believe there are others but these I know for sure are in Unraid's CA Apps.
  8. That's the same as my go file. What processor are you using? Also, the igpu has to be turned on in bios. Lots of variables to get igpu working in Unraid and this thread isn't the best place to figure it, I just put together the intel-tools container.
  9. Until that's working this docker will be blank/black screen.
  10. The app can't find the GPU for some reason. Goto the unraid cli console, type ls -la /dev/dri post the output here
  11. logs: go to unraid dashboard, click docker icon, click logs
  12. Please post the logs. The webui from your settings is port 7800, so goto http://yourunraidip:7800
  13. Thanks for the feedback. I'm very sorry for the confusion. I wasn't saying you knew or didn't know, I was just saying why that temporary directory is not mapped to a volume by default. All I can do from here is acknowledge your feedback and offer assistant to you if you need/want it. Since you said you already mapped your /tmp directory on your system you are already good to go from that standpoint. Of course, the other obvious thing is to limit the amount of 4k videos you have in your source folder, and/or increase the docker image size.