Current recommended Version 1.35.? and Image Latency
Posted: Tue Mar 30, 2021 8:04 pm
I have 2 questions
1) what is the recommended stable 1.35 version (i'm at 1.34.23 now (assuming there is a stable version -- otherwise i'll stick at 34) and
2) I have a strange issue that has occurred since i recently rebuilt my entire unbuntu system (20.04.2 lts) after changing out the Motherboard, going to an intel I3 10100 chip and such .. and now, curiously, I have the strange behavior that the ZM monitoring can get as much as 45 seconds to a 1min DELAYED from the actual time of the camera. So while the clock time is really 2:00:45, ZM (using a time display from the actual camera) is showing that the time is only 2:00:00 .. so it's lagging behind.
CPU is running at no more than like 10-15% busy.
This is unsettling, and unfortunate at the same time; the other day I watched as the AmVet folks stopped by to pickup my bags of donated goods, and when I tried to go out to catch them (i'd forgotten to put the bags outside), they had actually been gone for nearly 45 seconds or more.
So this didn't ever use to happen (prior to my rebuild especially) -- so i'm wondering did I accidentally enable some "delay" somewhere that is causing this latency, or is there possibly some other nefarious cause?
thanks...
1) what is the recommended stable 1.35 version (i'm at 1.34.23 now (assuming there is a stable version -- otherwise i'll stick at 34) and
2) I have a strange issue that has occurred since i recently rebuilt my entire unbuntu system (20.04.2 lts) after changing out the Motherboard, going to an intel I3 10100 chip and such .. and now, curiously, I have the strange behavior that the ZM monitoring can get as much as 45 seconds to a 1min DELAYED from the actual time of the camera. So while the clock time is really 2:00:45, ZM (using a time display from the actual camera) is showing that the time is only 2:00:00 .. so it's lagging behind.
CPU is running at no more than like 10-15% busy.
This is unsettling, and unfortunate at the same time; the other day I watched as the AmVet folks stopped by to pickup my bags of donated goods, and when I tried to go out to catch them (i'd forgotten to put the bags outside), they had actually been gone for nearly 45 seconds or more.
So this didn't ever use to happen (prior to my rebuild especially) -- so i'm wondering did I accidentally enable some "delay" somewhere that is causing this latency, or is there possibly some other nefarious cause?
thanks...