Search results

I actually 'fixed' my issue by restoring a backup I made directly from the camera's GUI about 5 months ago. I don't see anything obvious in the settings or why it works now but I guess I must have changed something (inadvertently) from the last backup.

No, all 3 cameras are using their own AI that I set up to trigger BI to record. BI does not have any triggering set up and is only passively recording when the camera sends the ONVIF trigger event. I purposely set up these Dahuas because, in this case, I had better luck with the Dahua's...

I did just now notice that under my AI/IVS rules, the time plan there was set to custom... I'm going to change that to full time to see if that makes a difference. Though, I don't ever remember futzing with that particular setting.

Yeah I didn't change that, it's set to day 24/7 there. Thing is that I thought I remembered the camera triggering right along with the other two, as expected at night, for months after I set it up. I'm sure now because I set up a group of 3 "front" cameras and would go into clips and see that...

First let me say I think I'm now so deep in the weeds that part of my problem is my brain is fried from overthinking. Months ago, when I set my T180 up, I only set it up for triggering through the AI portion of the GUI and I set up BI to only trigger from ONVIF's from the T180. Somewhere along...

what screens do you want?

I may have spoken too soon. When I look at the stats for nerds it shows native res at 4096x1216, but the stream resolution is 3840x1144. Shouldn't it match the native res?

Well, that did it! Thanks! I should have thought of that.

No. I should run that again?

I recently changed this camera to a 4096*1216 resolution in the camera GUI but BI video resolution doesn't go that high. I am using ONVIF in BI so should I change to the actual camera model in BI to get the higher resolution? I'd prefer the higher resolution since this is the main camera that...

No, I was using onvif all this time... think I should switch to that one?

In the last month or so all of my PTZ cameras won't stop when I manually move them. They just keep moving in the direction I clicked on until I either press a preset number or click the opposite direction. This seems to have started in the last month or so and I kind of ignored it because I did...

I'll try that.

I can say with 100% certainty this is not from a camera picking up an external noise. 1. It never happens when I have UI3 running, sometimes for hours at a time. 2. It only happens on the computer which BI is running from. 3. The sound is identical each time in sound and length (2 seconds) 4...

I'll follow up with... if I had installed a ton of apps on that pc, I'd be suspicious about any of them but this machine is al most 'pure' for the reason of it's primary purpose, BI and a weather app. I can't even find any .wav/.mp3 sound files except some that reside in the BI \www\sounds...

I know that when I use UI3, for hours at a time on my second monitor, I never hear the above mentioned sound. It's only when I remote into my Weather PC which houses BI and 1 weather software package that I hear the sound. The weater pc's main use is BI and the weather app. Anything else put on...

I have 15 cameras, most without sound, but I'll check the ones that do anyway.

Where? Login to the UI3? If that's what you meant I don't see any setting for noise cancellation there.

So when I run BI console, every few minutes a very quick audio clip, maybe lasting 1 second plays of rushing water (or that is what it sounds like). I have looked everywhere I can think, including the user setup area for login/logoff sound and it isn't there. I can't pinpoint exactly how often...

But can you issue commands directly to the camera?

So I did a test. I manually moved the camera with the cam gui. The resume in BI is set for 10 seconds. After a minute still nothing. Then I right clicked the camera in BI console and used the PTZ command to choose a PTZ preset I have not programmed (ie: PTZ 20). The camera didn't move but...

I remember dealing with this issue a couple of years ago, exact issue, but I'd forgotten about it until I'm at the point of wanting to make this work now. I even wrote Ken about it but I don't recall his reply having a solution or maybe he had an explanation of the expected behavior. It would...

Yep

very interesting. Wonder why mine doesn't do that. Which preset does yours go back to, one set up as home or one that you were just on and manually moved the camera from?

That is kind of what I was after by using my middle (fixed) camera. Maybe I could set it up as the spotter cam and the next time it triggers it could move the other two cameras. Even if it moved them to each of the respective 'home' position, then maybe the resume command within BI would work...

I'm on the most stable one 5.7.7.8 I always just use the stable releases. That's odd to me about your scenario when mine does not. I've tried it on two of the cameras and it won't return to the scheduled PTZ, unlessI use BI to do "something" with the camera. Even using the PTZ to move it one...

Ok guys. come one, please read in the original post what I'm trying to do. I have two ptz schedules set for my camera in BI. One is a "day" schedule where my cam points "this way" One is a "night" schedule where my cam points "that way". If I move the camera via the GUI (not through BI) then BI...

Except that doesn't work as I described in the original post. If you move the camera using the camera's GUI, BI doesn't "know" it's moved so the resume doesn't work. If you move the camera, in any kind of way, via BI, then it of course would work.

Gonna think on that. Not sure I want two different time schedules (one in BI and one in the camera), but will look at it. Thanks.

Well I really like the IVS in the camera. Maybe down the road I'll look at some of the AI technologies connected to BI but for now the IVS in Dahua cams really does it for me.