Search results

  1. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    This has already been covered.... probably will all go away in a few days. Meanwhile, just use the date setting and not week. It works fine then. OR disable onvif authentication in cam. https://ipcamtalk.com/threads/5-7-5-april-20-2023-onvif-updates.69517/post-807876
  2. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    no problem, I am curious if this goes away after the real time change ?? Time will tell :lol: I did inform Ken as well.
  3. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    LOL, I was going to edit my post after figuring that out but hadn't got that far. Thanks for pointing that out. So for some reason on November 1 when Ken released the .12 update, then if you updated, your cameras are restarted within BI and the error showed up. I notice in the WEB 5.0 GUI if...
  4. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    UPDATE: I found that by selecting a date in the DST selection, then the problem is fixed. There is a bug in the camera's DST firmware and it is not reading the correct date using the week setting. Also found that using the date method, you cannot select 2:00 am on the start date, why I show...
  5. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    you are correct, I just tried to disable DST in the problem cam and still no luck. I then tried to change time back one hour, still no work. I then changed the time to 2 hrs. earlier and bingo, the onvif then authenticated.
  6. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    Yes, mine snyc to my BI machine via NetTime. Same settings I use in my others as well. Maybe this is the new WEB 5.0 issue ?? It is the only difference to my other cameras as they all run web 4.0
  7. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    Good point !
  8. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    Also, I did check and am running the latest version of ODM 2.2.250 and double checked my onvif user password in the camera twice now. Once I turn off onvif authentication in the camera then ODM will also connect fine. I also even tried my BI demo install and reverted it back to 5.7.9.12 and...
  9. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    Exactly, same error in it I get in BI. This camera is almost identical to all my other Dahua cams and they all work fine.
  10. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    Also, you can't use the find/inspect feature! I use this all the time. It's not just the events, it is failure to authenticate the onvif user. Here's another kicker, I tried to use Onvif Device Manager and it also will not authenticate. So now I am stumped as why this worked before the update...
  11. Tinman

    5.7.5 - April 20, 2023 - Onvif updates

    Just my newest PTZ cam did the same thing. And I could not roll back as it would not fix the error. I like you just disabled onvif authentication. I did not email Ken about it as I thought it was my cam, but yes it did start right after .13 update.
  12. Tinman

    Why work on Windows 12 when Windows 10/11 still isn't the perfect OS?

    I still use 3.11 LOL
  13. Tinman

    Warning ! BI update 5.8.0.11 will corrupt your database and will lose alerts.

    5.8.0.12 fixes the issue.
  14. Tinman

    Warning ! BI update 5.8.0.11 will corrupt your database and will lose alerts.

    I also just found another NASTY bug in 5.8.0.11. If you do an export of a camera that has a space in its name, for example (Front Door) this will instantly create a new camera in the registry. The new camera will be named Front_Door and this will completely hose BI when it is restarted. The new...
  15. Tinman

    Warning ! BI update 5.8.0.11 will corrupt your database and will lose alerts.

    do a compact/repair of your database to be positive. I think .10 is what got me, but Ken replied .10 or below ?
  16. Tinman

    Warning ! BI update 5.8.0.11 will corrupt your database and will lose alerts.

    I ran every 5.8.0.0 thru 5.8.0.11 The first few were ok, then they started having memory leak issues. The first issue I had with missing all my old alerts came when I went to 5.8.0.11. So you just don't really know if your alerts will stay intact on your next update as it may already be...
  17. Tinman

    Why work on Windows 12 when Windows 10/11 still isn't the perfect OS?

    As with all operating systems, it's the driver that depends on stability. I have no issues with W11 and knock on wood, not one BSOD.
  18. Tinman

    Warning ! BI update 5.8.0.11 will corrupt your database and will lose alerts.

    Just to update this, Ken has informed me the data base bug was actually in 5.8.0.10 and below and was fixed in the 5.8.0.11 release. So when I did the 5.8.0.10 update, the damage was done already and did not surface until 5.8.0.11 was installed. Since then I have ran 5.8.0.11 for 24hrs. and...
  19. Tinman

    Warning ! BI update 5.8.0.11 will corrupt your database and will lose alerts.

    Again, I think it is something to do with the AI icons or pointers on the alerts. I just tried to update a demo version I use for testing, but NO CPAI is used on it and it DID NOT lose any of the old alerts !
  20. Tinman

    Warning ! BI update 5.8.0.11 will corrupt your database and will lose alerts.

    Have experienced this issue on 2 installs, and there is no fixing by reverting back to the previous update.
  21. Tinman

    Memory leak on version 5.8.0.5

    So far 5.8.0.7 looks better than previous updates :) my memory is still holding under 1GB, none of the others did that .
  22. Tinman

    Memory leak on version 5.8.0.5

    Give 5.8.0.6 a try, I'm testing now, but mine is a slowww leak.
  23. Tinman

    Memory leak on version 5.8.0.5

    Well, it did grow and I have had it up now about 35hrs now.
  24. Tinman

    Memory leak on version 5.8.0.5

    Ok, so early this morning I went back to 5.8.0.5 and it has ran all day with NO memory leak ?? I could of jumped the gun on first time around by not doing a full windows reboot which is the only thing I did on this test differently. I normally try to do that on every update, but must of been in...
  25. Tinman

    SD49425XB-HNR - Odd spotting on the lens

    Just like your car windshield, you can see fine if it's dirty but when driving into sun...it's hard to see anything.
  26. Tinman

    CPU bug?

    W11 has never been correct reporting CPU usage to BI or vice versa. I run my CPU factor at 2.9 and its close most of the time but far from perfect. When I had BI on W10 it was much more accurate. Still not going back to W10 though :)
  27. Tinman

    Memory leak on version 5.8.0.5

    It appears to be related to CP or just motion, not sure. I can update and run 5.8.0.5 at night and the memory usage is stable, but once daylight comes and with more motion it continues to grow.
  28. Tinman

    Memory leak on version 5.8.0.5

    The leak is on 5.8.0.4 & 5 I went back to 5.8.0.1 and its not there. Ken is aware of the issue.
  29. Tinman

    AI is broken after switching from DeepStack to CodeProject

    LOL, I was looking at the 2000-06-06 date :idk:
  30. Tinman

    AI is broken after switching from DeepStack to CodeProject

    Yet, you still have time overlay and title overlay enabled on your cam?
Top Bottom