Search results

LOL pretty sure it was the recycle bin on the NAS drive. I set a schedule for it to delete the recycle bin hourly, hopefully that solves the issue.

so everything has been going smoothly, the cpu usage issue resolved with swaping out hard drives in cpu. the issue i'm having now is.....blue iris filled up the NAS drive and its not deleting the files on the NAS. It is set to delete in blue iris but for some reason its not deleting. I'm...

Thats what I assumed to start with. Checked that and cleaned the lens this morning. But I just went out there, really scrubbed the lens, and it seems to have fixed the haze. So it must have been really really dirty this morning. Sorry to bug yall with that jeez.

I just checked my other PTZ and both look the same. I repositioned the haze camera so there is no white wall. There is now zero sun in the frame. The light is completly flat. Haze still there. I know if I moved the other camera to this position there would be no haze one it. There must...

OK I will wait for the sun to go down and post another photo.

for reference, this is the same model camera facing the other direction. that white wall is the same white wall. this camera is never hazy.

unfortunatly no difference on manual mode.

its exactly this, the reflection of the camera lens from the protective lens/cover. Both of my PTZ's do this. Like I was saying when its from the sun its not too big of a deal it lasts for about 1/2 hour each day. But at night its bad, because there are several sources of light pointed at the...

cam with haze: IPC-T54IR-AS-6mm-S3 cam with reflection: PTZ5A4M-25X

thanks for suggestion but no joy

On the PTZ....there will always be some lens flare with cameras pointed directly at a light source, but this isnt that. That big circle is a reflection of the camera. The protective lens is reflecting the camera. The haze though - I will try pointing the camera away from the wall and thus...

Thanks, photo 1 is from the sun. It happens to both PTZ's. When its from the sun during the day its not that big of a deal, it dosent last long, but it sucks at night as its pretty much constantly there depending on where its pointed (from street light, landscape lights, house lights, etc)...

So everything has been running great for about 24 hours. fingers crossed it was just that drive. I've noticed two cameras look strange, they are not dirty, just cleaned. Is this an internal reflection of the camera lens on the protective lens? and any idea what this fog looking haze is?

so I swaped out the hard drive in the desktop running BI to a WD purple. Been running for a few hours and CPU usage isnt climbing. Hopefully when the new drive fills up and things start transfering to the NAS it will remain stable. The move speed of the new drive BI is reporting is like...

half hour later were at 40%. only thing in the log between 20% and 40% is a move

i removed all the push notifications from the cameras but it is still happening. I will restart BI, everything is good, working as expected, task manager reports under 10% CPU. Seems stable enough, but it very slowly just creeps up. After about 20 minutes its at 15%, 30min 20% until about two...

so i found the speed test within BI for the drive, it did the test of 4gb of data and reported 117mb/s. I cant expect anything more from my Gigabit network and drives, and it should be way more than I need anyhow right? But after running for 4 hours, BI is back to using 35% CPU. So something...

Its transfering files to NAS at about 90mb/sec which seems slower than it should be but should be plently fast to keep up. So I guess I'll just watch it and see. I have web UI open, 15 cameras continuous recording, and its transfering data to the NAS and staying below 10% CPU. If it spikes...

it is currently moving files, my NAS is growing, and everything is sitting below 10%. OK so if I have NEW set to move to STORED when new gets to 1000gb - it will just constatly roll FIFO to STORED drive?

i restarted BI and the desktop. BI started back fine, has been running for 10 min, maintenance message said it was transfering files but I dont think it did (my NAS didnt grow). It didnt go over 10% CPU usage on task manager the whole time. Now its sitting around 5%. Super weird. How...

maybe there is a bottleneck somewhere unloading files to stored drive on my NAS and thats whats causing all this.

so I guess when I deleted the cameras and added them back the right way, by putting the username/password in before find/inspect to find the camera - doing that caused my CPU usage to go back up - its now around 50%. I checked all the substream settings on the cameras, and they are all similar...

I allocated 25% less than drives capacity so it shouldnt get close to full. Ill keep an eye on it.

but i guess it levels out and says this, so all good?

things are acting a little funky. froze ptz, etc. BI reporting this on the hdd:

LOL ok. Well hopefully it stays good for a while :)

actually, renaming 2 of the 15 cameras caused it to crash. 13 were AOK, but two camera renames caused a crash.

well. I went to rename the cameras - and renaming a camera causes BI to crash. It comes back and new cam name sticks, and everything seems OK. Is that a known issue?

The alerts were not working, so I also deleted, and added back all the cameras by putting in the password BEFORE find/inspect - confirmed that it found all the right substreams. That made the alerts start working .

i restarted BI this morning and got the version screen pop up this time, so I was able to revert back to latest stable version. Everything seems to be stable, it was up overnight, hasnt crashed since I moved the database onto the same drive as alerts/new. it was immediate, so either 1)...