ui3
ui3 copied to clipboard
Opening alerts sometimes does not open the correct timestamp in the clip
I haven't got a configuration that allows this issue to be reproduced, but here are the details: https://ipcamtalk.com/threads/blue-iris-ui3.23528/page-143#post-497567
Still unable to reproduce this issue.
I just encountered a similar issue after making the following changes:
- upgraded to Blue Iris 5.3.9.13, and
- relocated the Samba share I use for recording to a new filesystem (same server and export name). Existing files were copied with
rsync -Aavx
.
I have no idea if the changes are related, but now when I press on an alert in UI3 it takes me to the beginning of the clip. If I keep pressing on the alert it will eventually seek to the correct timestamp (usually on the second or third press).
I am recording continuously and logging motion alerts in the database.
I hit this also. It appears to be an issue anytime I'm rerouted to the login page first, it doesn't redirect me to the correct clip after authenticating (even for a 3sec auto login).
Example url I'm opening: <ip address>/ui3.htm?tab=timeline&timeline=1681723608105.0000&cam=cat
Once my mobile browser is authenticated, if I go back and click the notification to open this url again, it brings me to the correct timestamp as expected.
Hi @ahaverty. You'll need to be more specific about what happens, because that URL goes to the timeline, not to a clip or alert as would be appropriate for this issue. I have tested a few timeline URLs and I do note that sometimes the playback begins at "live" instead of at the requested time. Is that what you are seeing? I will need to do more testing to determine if the jump to live is UI3's fault or Blue Iris's.
I have identified and fixed the bug responsible for the &timeline=####
argument sometimes failing to function properly. The fix is in release UI3-234.
This issue (#50) remains open however because it is unrelated to the timeline.
Exactly that @bp2008 thanks! Sorry, I thought that's what this issue was about.
Closing this issue. I think it is not relevant anymore.