Recent content by Gerwin

Not really noticeable, a few percent cpu usage, I think less then 10%

Update on this: Tried to resolve this for a few days now with BI Support (Ken), i think, he is still after it. For me the temporary solution is to turn off hardware decoding on all cameras on my two installations, if i want to use substreams. Now the timeline is correct, no 49 days clips any...

The only way for me to get rid off this problem is to not use substreams at all. tested for the whole night now, not one wrong timecode or duration. I hope this will be fixed soon, because the substream function overall is a complete winner in my opinion.

Nice hint, thank you kklee, will try to turn off using RTSP/stream timecode. Had no randomly restarts so far on 5.2.7.12 EDIT: With "use RTSP/stream timecode" off, i have no wrong date & time, but wrong duration now, but also not at all clips as you can see...i´ll turn off all substreams for...

Hello, I can confirm niels detailed description of the Problem for my setup. Restarting fixes temporarily, manual trigger reproduces the wrong timestamp. I also use substreams since available and turned the specific one off now for testing if the failure comes again with the hires stream...

Hello! Since a few Versions i see a strange behavior on two different BI Setups running on Version: 5.2.7.12: One Setup has 4 identical Cameras (SV3C 1080p) and the other 6... In each Setup there is ONE Camera, from which BI records the Clips with wrong date&time . But not always, only from time...