Sw337s

Members
  • Posts

    3
  • Joined

  • Last visited

Sw337s's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Found a simple method using regedit in the github reported issues (https://github.com/jshridha/docker-blueiris/issues/35) Other problems I have found workarounds for: - Freespace detection in BI under wine shows the root drives free space. Wine maps/mounts unraid shares as a folder mapping. I got around this by ticking to not monitor free space in BI settings. - No H265 decoder available according to error log. I changed the camera to H264+ and the error disappeared. Outstanding issues that arent immediately apparent after looking at scripts and dockerfile: 1. Resolution bug. Not all resolutions seem to take effect. RESOLUTION=1920x1080x24 does not work. RESOLUTION=1440x768x24 seemed to be larger vertically so I could click OK buttons but then it isnt consistent. 2. Registering BI seems to work but the registration doesnt survive reboots/restarts of blueiris.exe. The evalution version notice stays on presumably because it isnt restarted after registering. (Looks like BlueIris 5 licences do not allow upgrades within the current major version as soon as the licence has expired - huge security risk if not receiving updates and default behaviour is to expose to the internet 🤬) 3. Changing any settings in unraid deletes the docker and hence wine environment. I have to install everything from scratch. When the blueiris was working for about 5 minutes I was seeing 5% cpu usage on a 6700k for 5x 1080p camera feeds (no transcoding/frame analysis). It was promising as I typically was seeing around 10-20% cpu usage on a VM running just BlueIris. For now I will need to spin up the VM until hopefully these bugs can be sorted. Will try and run a single camera feed and not import settings and see if that fixes any issues.
  2. I'd love to give this a try but not looking forward to setting up my cameras again. Any idea how to import a config if backup/restore does not work? (according to docker hub page)
  3. I came across this searching for a solution to the mystery of mover. I thought I could look at iotop but everything is hidden under the veil of shfs +1 to some way of seeing mover progress. Thanks! P.S. The previous suggestions indicate unBALANCE is used like mover? Are people ignoring the warning "unBALANCE needs exclusive access to disks, so disable mover and/or any dockers that write to disks, before running it.". mover is great as is balances the cache/array while everything is running. I assume unBALANCE can be used for this??