mathgoy

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

5 Neutral

About mathgoy

  • Rank
    Newbie
  • Birthday 05/15/1984

Converted

  • Personal Text
    unRAID6 Plus
    System: Supermicro - X9SRE - Intel® Xeon® CPU E5-2650 @ 2.00GHz - 32 GB ECC RAM
    Storage: Samsung SSD EVO 850 250GB (cache) - 5x4TB HDD (Data)
    Network: Gigabit lan

Recent Profile Visitors

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

  1. Looks like it's all good Thank you so much
  2. When I don't use the nvidia hardware decode, you are right, the docker will stop when it crashes and won't disappear after a reboot. However, with the nvidia integration, any crash will delete the docker. Even stopping the docker or rebooting the server will delete the docker.
  3. hi @yayitazale, any news about the docker that goes orphan after a reboot?crash when using nvidia? Thanks mate
  4. Just some further inputs: If you use the "regular" docker and manually add the nvidia GPU support, the whole container will be marked as oprhan when it crashes too. Also, when you reboot your server, the container will also disappear.
  5. Hi @IpDo Thanks for the Tips. I did exactly what you were advising and It worked. I was missing the GPUID (i was using 'all" as it is mentioned in the documentation) as well as the extra arguments After it worked with the regular template, I moved to the new frigate-nvidia template (big thanks to @yayitazale) and it was even easier since all the variables were created. Just one thing. In the YAML config file, the documentation is telling us to add the following to enable the hardware decoding: It didn't work for me and it crashed t
  6. hi, Thanks for your feedback Yes I did install the Unraid Nvidia Plugin and it is functionnal with Plex for instance. Please let me know about any information I could help you with
  7. Hi Same feedback as @remati here. Just loaded my M.2 Dual edge TPU (using a PCIE adator) and it worked right off the bat. However, I am struggling with the Nvidia Hardware acceleration. I pulled the nvidia version of the docker and added the 2 environment variables as explained in the documentation. There is one sentence I don't understand in the documentation though. What does it mean? For your information, the error I get for the stream I am trying to process with my nvidia card is the following: [h264_cuvid @ 0x563acb21c3
  8. After some further investigations, I found out that it's related to the Reolink Cameras I use. It's recommended to use a RTMP stream instead of an RTSP. For those who may have the same issue, here is the link format for RTMP streams on reolink cameras: rtmp://IPADRESS/bcs/channel0_main.bcs?channel=0&stream=0&user=USER&password=PASSWORD You will find below the block that worked for my Reolink camera (with the input_args) cameras: descente: ffmpeg: inputs: - path: rtmp://IP_ADDRESS/bcs/channel0_main.bcs?c
  9. Thanks for the feeback After some further investigations, I found out that it's related to the Reolink Cameras I use. It's recommended to use a RTMP stream instead of an RTSP. For those who may have the same issue, here is the link format for RTMP streams on reolink cameras: rtmp://IPADRESS/bcs/channel0_main.bcs?channel=0&stream=0&user=USER&password=PASSWORD
  10. Hi All, I've been trying several CCTV docker containers (Shinobi, MotionEye, Zone Alarm and Frigate) and I have the same issue with all of them. Randomly, my video stream seem scrambled and messy (see attached) and when I have a look in the logs, I get the following errors: [h264 @ 0x562cc0734d00] left block unavailable for requested intra mode [h264 @ 0x562cc0734d00] error while decoding MB 0 4, bytestream 954579 [h264 @ 0x562cc0734d00] left block unavailable for requested intra mode [h264 @ 0x562cc0734d00] error while decoding MB 0 114, bytestream 16535 [h2
  11. Hi All, Considering moving from BI+Deepstack to Frigate so I installed that docker First of all, thanks a lot for the work because I had it up and running in less than 10min. Installation was really ez. Now I am running some few tests (CPU mode) and I have to say the detection is pretty good. However, the whole thing will work for 10-15min and then I noticed some issues. My camera stream becomes messy (see attached) and I have the errors below in the log (it's just an extract) [h264 @ 0x562cc0734d00] left block unavailable for req
  12. OK I found the issue. THis was a massive screwup fomr the desk-keyboard interface. Actually, in the VM Form, for some reason, the path to the windows10 drivers was wrong. I fixed it and it's all good now.
  13. Hi gents, I have a W10 VM running just fine for a while. This morning i updated to 6.9.0RC and decided to disable my GPU passthrough on that VM so I could use the GPU for hardware transcoding. I thought I did everything correctly but when I launch the VM I get that error message: You can see here mu XML file: This is a VM I use to rune blue iris only son using VNC graphics will be good enough (It's someting I've been using for a while) Can you see any obvious mistakes I did? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'>
  14. Hi, I am greatly interested since I opened a similar topic but didn't get any answer!