hendu

When I get a delay with my reolink from preview to full single can, it's very brief. Maybe a second or two, however; your settings look a bit different so I'm going to play around a but with it. I don't use the web interface, no. We have it a shot. But the android app is nearly identical to the desktop app. My wife had an iphone and the app isn't quite as nice. I'm going to reinstall the iphone app for her to try that again before jumping ship. If that works I can set that up securely. I hate opening up ports on the router, but there is no way I can get her to use a vpn.

I wonder if part of it is number of cameras. I'm considerably lighter than you on cameras. I haven't found a way to make Xeoma use the clear stream in the preview windows, so I know what you mean by that slight delay to swap from preview to full. In talking with the mrs, I'm tempted to go back to blue iris for her and just deal with the VM situation. I found it friendlier for her for accessing the cameras than messing with the web interface in xeoma. It also performed a lot better for that. The archive pieces are more of a pain but I can work through those. Something to test more after camera 4 is up and running.

I run pretty basic with mine so far and only have 3 reolink 4mp cameras (until I can get to planning wiring for the fourth that arrived this week), however; I idle at Around 4% CPU. at the camera source: Clear stream 2560x1440 at max bit rate 4096 and 30fps Fluent stream q720p at 160 bit rate and 7 fps audio on in Xeoma: Fps set to max h.264 recording to archive without conversion checked audion not disabled the only modules I run are the scheduler, motion detector, preview/archive, and email. Someday I'll probably do more with all of that, but I'm happy at the moment. i run on an e3 1245 v3 which shouldn't see such a difference over your i5, depending what else you're server is running. I do notice that playback from the archive is less than ideal. The video files work flawlessly though. I'll probably look at getting a dedicated drive for that. now to start planning my summer attic wiring work...

Thats strange that youre seeing that performance on that processor. Did you have cameras set at a high frame rate and what kind of modules did you have set up?

I am happy with Xeoma, being a former blue iris user. However; I am coming from using BI in a VM. If I had a standalone BI machine, I am not so sure I'd feel the same way. You can see what my experience has been in prior posts. The biggest drawback I've seen so far with Xeoma is due to the fact that I run it in docker. The licensing works oddly, in my opinion, for video security software. You have to have constant internet connection for the license to stay active when using a VM. I've only had it happen twice since starting use this spring, but I've lost internet long enough to deactivate my system. Reactivating simply takes registration again, but that's still some downtime I've experienced. I understand the reason, but it's the only aspect that tempts me to go back to BI. The benefits I gain from the improved system resources outweigh that so far. As for zoneminder; I've never gotten far enough with that to give you my 2 cents. I have reolink cameras and had a heck of a time getting zoneminder to play nice. I was also not a big fan of the interface.

I think it depends on your set up. I only purchased a 4 camera license, so my cost wasn't much different from blue iris, though I do own both. However; blue iris in a VM was less than ideal. I liked it but I literraly air at 1% cpu usage with Xeoma in idle. I also have a huge decrease in ram utilization. In other words, for my specific scenario, it just works better. I'm planning to pick up my 4th camera this week, then I'll have to decide what I want to do about licensing. The updates are included for 1-3 years depending what you purchase. Blue iris also charged for one of it's major updates if I remember correctly a few versions back. So to answer your question, it's better at some things than Blue iris. Specifically resource management in a Linux system, some pretty nice workflow set ups, and I get less false alarms now. Blue iris is better at other things.

I found using the IP address search of the camera and entering the user/pass was easiest. The self discovery worked, but it was slow. I can't remember, but I think you still have to select the option to 'add camera' even after it finds it with that. As for motion trigger, it's a matter of setting up the workflow properly. I have a simple scheduler one (so I can adjust by time of day at some point), then the motion sensor. I had to fiddle with my settings for sensitivity and zones. From the motion sensor I have an email branch to send me notifications of movement and then a Preview and Archive. I have a lot of customization I still need to do but this got me up and running quickly. I really am liking my set up now, and I am thoroughly enjoying not having to run a windows VM for BI. I have switched to the beta branch and my issue with losing license connection seems to have gone away. The Xeoma support was very helpful with this.

I've been running this licensed for the last week and a half now. Overall I'd say things have been great. I think I lose a few features over blue iris, but not having to run a windows vm that was consuming the amount of CPU necessary for BI is a nice trade off. I am noticing that occasionally the licensing must lose connection to their servers, and since the docker is a vm and requires constant connection, this requires me to re-enter my code. I have to see why that's happening, I've been rebooting my server a bit more lately as I work on things, I'll have to see if that's related.

Looks like that fixed it. Having gone from BI to the @coppit, do you think it's a worthwhile leap in order to get out of a BI VM?

Just some findings for you @coppit. works great on first run. However; when restarting the container, I get the following error. Simply stopping the container and then starting it reproduces it. The work around I get is simply go to edit the docker and save. Removing the directory didn't fix it. Note, I run with my appdata on a separate drive mounted via unassigned devices. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...*** Running /etc/my_init.d/50_configure_xeoma.sh...mkdir: cannot create directory ‘/.config’: File exists*** /etc/my_init.d/50_configure_xeoma.sh failed with status 1*** Killing all processes...

Great work. I'm up and running now. I just need to decide if I want to run the xeoma docker and save some resource (and pay another 50 for licensing) or stick with my VM and blue iris...the cpu save is pretty big and it seems like the 3 cameras I have are performing well so far in the trial.

coppit just curious, are you using a paid license or trial?

I messed around a bit with things and switching to the beta and proper config removal fixed the libx11 error. Now I'm in the same boat as bokchoy and simply cannot connect to it from my desktop. I'm going to take a look at some network items for that, but I don't have a problem connecting to a VM with it so I'm pretty sure it is related to docker. FWIW docker -v is also 1.12.6 here.

I gave this a shot. Below is my full log after forcing an update and starting the docker. It continues to run but this is the log. I cannot connect to it. I tried it in a linux VM and had no issues. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...*** Running /etc/my_init.d/50_configure_xeoma.sh...*** Running /etc/rc.local...*** Booting runit daemon...*** Runit started as PID 21[Apr 20 09:24:20 PM] Using the stable version of Xeoma[Apr 20 09:24:20 PM] Setting the passwordApr 20 21:24:20 0712462b9a51 syslog-ng[30]: syslog-ng starting up; version='3.5.6'Failed to open 'libX11'Password set successfull[Apr 20 09:24:20 PM] Starting the server in 5 seconds...

Sadly, reinstalling the container doesn't fix this. Deleting the config directory and starting over doesn't fix it either.

I'm very interested in switching from Blue Iris to this if I can get the docker to work. I'm very tired of running a VM just for BI. Unfortunately, I get the following error in my logs. Any ideas? Failed to open 'libX11'

I saw the 100% disk usage issue early on in my win10 installs. I was able to band aid it so it didn't occur ALL of the time, but it was frequent enough that I didn't like it. When it'd occur, I'd also see a spike in the servers cpu usage. One thing I never checked was if it was related to virtual memory or not. Instead, I shot gun fixed this puppy since I have things I'm trying to run in the vm's. Ultimately, I made the following changes. These gave me some incredible performance gains. I can remote into the VM's and I get incredible video playback and application performance. Increased ram from 4gb to 6gb Increased number of CPU's from 2 to 4 (one vm is set to 6) Moved from cach HDD to dedicated VM SSD

For one vm, I used Core 7, for the other Core 6. I decided to not have them share, they were doggin' enough without my help. Also a Xeon E3 1245 v3

Switching to a single cpu also worked for me! Great find and very helpful. I was seeing the issue on 2 VM's and this worked for both. Thanks!

Upgraded via plugin without any issues. Really happy to see some of these additions. I did notice that checking plugins for updates is less verbose, but that's not a big deal.

After some banging of my head against the wall as to why this wasn't working, I realized that you have to use the AMD64 drivers. Now to learn more!

I'm VERY new to the world of VM. I've tried getting windows 7 and windows 10 up and running. I can get into the point where I am installing the OS, but unfortunately the VM isn't recognizing my hard drive. I'm sure I'm not passing my sata through properly, but I am not having luck with finding the proper way to handle this. Any advice?

I've been running my upgrades this week using your method. This has been working perfectly for me. I am down to my last drive, which is running now. I turned off all Dockers and have been letting it run without issue. I do miss using my Plex server, but I should be back up and running tomorrow in full force.

Well, it was hard not to pass up the Lenovo deals that randomly show up lately, so I managed to do this on my Lenovo TS440 that is running the RAID 500 controller (MegaRAID 9240-8i). This was purely accidental and just a combination of what many people have already done. I used a few different posts in here to get to where I was, but I truly don't remember which ones fully . I ran everything through the existing system, I didn't take out the card. The TS440 does fully support UEFI. I was meeting endless errors where it wouldn't properly find megarec. The error was in the lines of "megarec is not recognized as an internal or external command..." despite the fact that I was looking right at it and the exe in the direcotry. I ended up taking some big risks and did the following. [*] First I downloaded and prepared the LSI MegaRAID to SAS2008(P11).zip from the front page. [*] I ran the steps from 1 and on until I didn't get any errors. This eventually ended with a PAL error. IIRC this was on step 5. [*] I then followed xtree's instructions - I prepared a usb with BetaQuasi's instructions BetaQuasi's M1015 Cross flashing instructions as a guide [*] Created the bootable USB. [*] Grabbed the P19 package from LSI. LSI Link [*] Replaced the 2118it.bin and mptsas2.rom files on the USB key with the ones in the package. [*] Created a directory structure \efi\boot\ on the USB key [*] Copied Shell_Full.efi to \efi\boot\bootx64.efi on usb. [*] Set BIOS on TS440 to UEFI only. While I was in there, I fixed my boot orders too. [*] Start system and wait for efi shell. [*] Typed fs0: to get to the usb device and where all of my files were. This is where things got weird again. I was continuously getting errors like the ones I received earlier, that sas2flsh was unrecognized, despite the fact that I could see it in my directory listing. I decided what the hell, why not. So this is what I did to continue. I then simply ran the following commands with sas2flash.efi instead, something I was reading in another forum. [*]sas2flash.efi -o -f 2118it.bin -b mptsas2.rom [*] sas2flash.efi -o -sasadd 500605b0xxxxxxxx (replace the xx's with the SAS address from your card) I rebooted and boom, all of my drives were available in the unraid interface. I don't know if what I did was right or wrong, but it worked...I'm sure someone can find the holes in this and stream line for those jumping on the recent string of thinkserver deals.