Got a little issue with v6. I'm only getting output for my main New folder and nothing for Aux 1. I have storage set to false since I don't use it.
$show_folder1 = $true # 'New' folder, like 'D:\BlueIris\New'
$show_folder2 = $true # 'Aux1' folder, like 'E:\BlueIris\New'...
As an aside from my little experience with reolink before I got rid of them all, make sure "smart codec" is turned off if you have that option in your cam settings. I ran into that changing the frame rate constantly.
I'm running it, but I honestly haven't really messed with any trigger settings since. I saw some settings are on a different page, but not sure if there's more to it than just that.
Probably recording only the substream, and main when triggered which is a new strategy I'm playing with.
The thought is the sub is good enough for general surveillance but when the cam is triggered you get full 4k or whatever cam you are running
Man I'm hijacking my own thread here. :)
What are folks recording continuous sub + triggered running for bit rates? On my 4k cams, h265 is the only option. I have CBR 8192 for the main, and CBR 1024 fot the substream. Not sure if there's much or any benefit going higher.
All of my 4k's are Annke c800's. I know not the best but half decent for the price. 640x480 and 640x360 are the only options for substream. I sent an email to support asking if they could possibly add a 720p or 1080p option in future firmware.
I actually just started testing this out on a couple of my cams that don't see a whole lot of action. I wish I could go higher than 640x480 for the substream. It's a 4k cam, but that's my only sub option. I did bump up the bit rate of substream to hopefully get a better image should...
That is correct correct.
There is a global setting too under the main settings, but I found toggling it didn't stop the hw decode for me. I had to change it in each cam like your screenshot.
FWIW, I did what wittaj suggested about a week ago and disabled the hardware acceleration on all my cams. On average my CPU usage stayed right about the same, however memory usage went down a bit. Clock speeds and power consumption stayed about the same too. I have 14 cams, all but 3 of...
Just tried that, (knocks on wood) and everything seems okay.
I think I'm gonna start letting a version soak for a few days and check here for any issues before updating. I'm always updating to the latest and greatest but I've been dodging a couple bullets lately :)
I just noticed something. How come sometimes it's going by total GB and others total TB? :)
Folder: O:
Camera Type Count Total_TB Avg_GB Max_GB #Days Oldest Newest
------ ---- ----- -------- ------ ------ ----- ------ ------
TOTAL bvr 150...
I'm not sure of the issue then. I was just speculating based on some recent posts.
FWIW, it's probably best to refer to specific version numbers. The memory leak was resolved in 5.8.0.7.
What version are you running? I just read there was an issue with the database in .10, but fixed in .11.
For me the memory leak was fixed a couple versions ago.
This is actually pretty slick and I didn't realize it was even an option. I have a cam in my detached garage, that I usually only had record when triggered. I just set it up to run continuous sub + trigger. Pretty slick, you can still see everything but soon as it gets triggered, it goes...
I'm kinda in the same boat. Originally I only had about a week, but wanted a few more days. Enough to cover being on vacation for a week with a little padding on either end.
I added a couple extra 2tb drives I had laying around collecting dust in an enclosure. Depending what drive I'm...
Wow that's a lot of cameras. I'm not sure what the use case is, but I think you might actually want only continuous. I believe sub + alerts only records the substream, and records the main stream when the cam is alerted. If you set it to continuous, and check record dual streams if...
I have it loaded, and it seems to be kinda working. Some of the images analyzed it sees a positive result. Some get that unable to create yolo detector error. But even the ones that work are higher than my 50% threshold but I still never see those in my alert list.
Maybe it's how I have...
I totally forgot I started playing around with the delivery models. I have them installed and configured globally and per camera. But I'm never getting them identified. Under the AI tab on a alert, I'm seeing "Unable to create YOLO detector for model Delivery"
I am using the onnx files...
Making a little progress. My results thus far.. I've only tweaked 3 of my cams so far, using BI to schedule the shutter and gain.
A couple I keep in day mode with enough ambient lighting. But even 1/30 shutter at 50% gain is leaps and bounds better than default settings regarding motion...
Just came across this and figured I'd give it a try swapping my 4k cams over to h264. Low and behold, h265 is the only option. Annke C800s, Hikvision oem. I know they're cheap cams and you get what you pay for. <shrug>
Great post. This should be stickied somewhere if it isn't already.
I've had a few Hikvision based cams for awhile, but the image has been good enough I really haven't tweaked much.
But after adding a new 180* unit for my driveway the conditions are just right for some terrible motion ghosting...
I haven't found a way. But I made two macros in the main settings using %8 and %9. Those two contain everything I need to use in the alert. So if I ever need to change the lan IP, there's only one place I need to do it. I had to use two because it was too long to have in one.