Figured I'd post this in case anyone else has a similar issue.
After updating to 5.5.8.1 I started having issues with FPS drops when live viewing cameras in UI3, also affected recordings. Motion recordings when played back would be extremely jerky, video would freeze, then speed up a few seconds to catch up, like rubber banding. Recordings would also get ghosting where motion was happening in the video.
Recordings recorded prior to updating to 5.5.8.1 play back no problem, it's just recordings saved while running 5.5.8.1 or 5.5.8.2.
My set up has been working perfectly with BI5, DeepStack GPU, Intel H/A, etc for a few months and this issue just started with 5.5.8.1 and then continued with 5.5.8.2. I am using direct-to-disk recording, and sub-streams.
Tried troubleshooting as best as I can, the only thing that appeared to stop the problem was disabling H/A entirely which I'd prefer to not do when I have CPU capable of reducing CPU usage by offloading decoding. I even went so far as to delete all of my cameras and set them all back up as brand new, issue persisted. It appears to happen the worst when deepstack is receiving motion images from BI and churning through them on my nvidia T400. When theres no motion, live view is smooth and normal but gets choppy, rubberbandy, and unusable as soon as motion begins and BI starts sending data to DeepStack. In UI3 you can see the FPS bar drop and fluctuate wildly when motion starts happening in live view. I'm curious if it's something to do with the new SenseAI code added to the 5.5.8.1 and 5.5.8.2 update that's interfering with DeepStack. Or maybe I'm just an idiot and missed a changelog message where I'm not supposed to install 5.5.8.1 unless I'm using SenseAI.
Either way, rolling back to 5.5.7.11 solved the issue. Hope it helps
After updating to 5.5.8.1 I started having issues with FPS drops when live viewing cameras in UI3, also affected recordings. Motion recordings when played back would be extremely jerky, video would freeze, then speed up a few seconds to catch up, like rubber banding. Recordings would also get ghosting where motion was happening in the video.
Recordings recorded prior to updating to 5.5.8.1 play back no problem, it's just recordings saved while running 5.5.8.1 or 5.5.8.2.
My set up has been working perfectly with BI5, DeepStack GPU, Intel H/A, etc for a few months and this issue just started with 5.5.8.1 and then continued with 5.5.8.2. I am using direct-to-disk recording, and sub-streams.
Tried troubleshooting as best as I can, the only thing that appeared to stop the problem was disabling H/A entirely which I'd prefer to not do when I have CPU capable of reducing CPU usage by offloading decoding. I even went so far as to delete all of my cameras and set them all back up as brand new, issue persisted. It appears to happen the worst when deepstack is receiving motion images from BI and churning through them on my nvidia T400. When theres no motion, live view is smooth and normal but gets choppy, rubberbandy, and unusable as soon as motion begins and BI starts sending data to DeepStack. In UI3 you can see the FPS bar drop and fluctuate wildly when motion starts happening in live view. I'm curious if it's something to do with the new SenseAI code added to the 5.5.8.1 and 5.5.8.2 update that's interfering with DeepStack. Or maybe I'm just an idiot and missed a changelog message where I'm not supposed to install 5.5.8.1 unless I'm using SenseAI.
Either way, rolling back to 5.5.7.11 solved the issue. Hope it helps
Last edited:
