Blue Iris UI3

[bp2008]

@Tinbum It might be time for an exorcism for the BI machine.

BI and UI3 treat groups differently if there is only 1 camera in the group. Could this be part of the problem?

 

[Tinbum]

There are a few in the group. I can see the cameras OK in the other groups they are in and under 'all cameras'.

It seems it must be a BI5 thing as I can't see the group on the android app either.

I tried removing the group and adding it back with a slightly different name but still can't see it.

Edit- solved; The settings for the group- which is quite hard to find IMHO, had include hidden cameras unchecked and only one camera was not hidden.

 

[Walrus]

@bp2008 with the latest BI update, in UI3 when you hover over an alert, the mouseover thumb pops up very large for a split second, then shrinks to the original size?

 

[Tinbum]

Yes does it on mine also. (Firefox and IE)

 

[bp2008]

@bp2008 with the latest BI update, in UI3 when you hover over an alert, the mouseover thumb pops up very large for a split second, then shrinks to the original size?

Yes does it on mine also. (Firefox and IE)

That is because BI increased the thumbnail size and apparently UI3 didn't know how to scale it correctly. BI 5.0.2.1 (today) included UI3 version 89 which knows how to deal with this.

 

[Walrus]

Yup fixed now.

 

[Albert Einstien]

I wonder if some light could be shed on this one.
I have UI3 on Win 10 Chrome, and Ubuntu Firefox. I leave them on, logged in 24/7, full screen. UI settings timeout set at "0".
I will come back to look at them sometime later, and they have reverted to a normal window, not full screen anymore. I never got a chance to see when it happens, but it's consistent. Tonight I caught it in the act! It was running full screen, I got a small message at the bottom right that said "your Blue Iris Session may have expired", it automatically logged out, and then instantly logged itself back in, and now in a normal window, not full screen. I'm wondering what's going on? Any ideas?

 

[bp2008]

@Albert Einstien There are a number of reasons it could happen. BI could have restarted for an update (if you have auto-updates enabled, you might not even know it happened) so your existing web server session would be gone at that point. Or BI could have crashed and started again automatically. Or, much less likely, another web service could be trying to use the same cookie name for its session cookie, although to be a problem it would need to be accessed in the same browser, via the same host name.

 

[reverend]

A random one for you @bp2008 please - I've sent this to Ken / support as well but since I went to 5 I've noticed a strange behaviour with flagged alerts (it seems fine when just viewing all alerts without ticking flagged).

I went straight from the last 4.x release to 5.0.1.0 a couple of days ago and then 5.0.2.0 yesterday and 5.0.2.1 today.

Basically using UI3 for flagged alerts it seems that the first time I click on a flagged alert it starts playback from the start of the particular BVR file rather than at the alert time. If I click on the same thumbnail again it starts playback at the alert time.

If I hover over the alerts it does show the correct thumbnail with detected motion at the right time, but when I click on it then it jumps to whatever the start time of the full continuous clip containing the alert was.

For example in the latest 5.0.2.1 if I click the first alert on the 13th August at 05:16:51 I get the following timestamp playing in the video:



If I click it again it jumps to the right timestamp (it's on 4x playback so a couple of seconds out by the time I stopped it).



The first timestamp of 04:55:33 corresponds to the time it last cycled the continuous BVR clip.

Using the full BI GUI it seems to work, just seems to have this happening in UI3 - not sure if it did this in the last version of 4.x before I upgraded as to be honest I wasn't keeping that close an eye on it.

I've tried a full DB rebuild but not sure whether this is a UI3 quirk maybe?

It's more obvious with the next alert down which shows the timestamp of 05:23:32PM and the video timestamp is 04:00:10PM - the second clip jumps to the right time with a second left click.

I'm using the latest Chrome OS 77.0.3865.18 - I'll dig out a Windows PC later to see if that shows the same with Chrome.

Thanks in advance

 

[bp2008]

@reverend I can confirm this odd behavior occurs for me too. It is bizarre that it happens only with the Flagged Only checkbox ticked. I'll need to debug line by line to see what the heck is causing it

 

[reverend]

@reverend I can confirm this odd behavior occurs for me too. It is bizarre that it happens only with the Flagged Only checkbox ticked. I'll need to debug line by line to see what the heck is causing it

To be honest I only found it while testing things out after the upgrade - it might be safer to leave it as is if it's just us that see it as normal alerts work great thank-you and a double click isn't the end of the world. I was more hoping it wasn't a corrupt DB so I'm happy at that thank-you

Long story short but I was only diving deep after the upgrade as it seems we have a knocking shop being operated by the neighbour two houses down. She's doing it all on her own which it turns out isn't illegal in the UK and appears to be specialising in more than one guy at once who all turn up around 2am and leave within an hour or so I thought the street was getting quieter but now this goes and happens It's not really what you want on a street full of kids, all the cars that turn up seem to be uninsured and no tax either so potentially not the sort of characters we want either.

 

[bp2008]

@reverend LOL

It is fixed for UI3 version 91, which I'm submitting to Ken now.

The problem was fairly recent, only appearing after BI 5 update due to a change in how the Flagged Only checkbox works. It is a bit complicated. Blue Iris was including a bit of extra metadata with the flagged view which UI3 wasn't handling correctly. So basically what happened was you clicked on your highlighted alert, and UI3 thought the clip was only 10 seconds long, so it immediately triggered logic that believed the playback position was out of bounds, and things kind of devolved from there. By the time you clicked again, UI3 had already requested and received the actual length of the clip, so it behaved fine.

 

[reverend]

Wow that was a quick turnaround thank-you very much @bp2008 - I'll keep an eye out for that one.

I'm still getting to grips with some of the new features in BI5 but it's great so far, just having a dabble with the AI side now, lots of new things to play with

 

[Albert Einstien]

@Albert Einstien There are a number of reasons it could happen. BI could have restarted for an update (if you have auto-updates enabled, you might not even know it happened) so your existing web server session would be gone at that point. Or BI could have crashed and started again automatically. Or, much less likely, another web service could be trying to use the same cookie name for its session cookie, although to be a problem it would need to be accessed in the same browser, via the same host name.

I checked my BI updates check boxes, they are all unchecked. I just took a look at my Win 10, Chrome browser and again it is a normal window, as I had set it to full screen at the time I last posted about this. It seems to be way too fast for a BI crash and restart, as when I did observe it in action, it logged out, and then immediately, I mean within one or two seconds, logged back in, no delay. I never saw it in action on the Ubuntu - Firefox machine, but when I check on it, it also goes to a normal window by itself sometime after setting it to full screen. I don't suspect another session cookie because I only recently installed Chrome on the Win 10 just for BI and only used it for BI. In fact I installed Chrome because I suspected Firefox of being the culprit, but it started right away with Chrome too. I'll try clearing the cache of all cookies anyway to see if that helps. I'd be curious if anyone else had seen this?

 

[bp2008]

There could also be a session time limit for your user accounts in Blue Iris settings.

 

[AMP]

Question for anyone that might know...

The Blue Iris native Windows application supports 40 presets, and so does the Blue Iris Android app. UI3 shows 20 presets with the thumbnails that you can hover over in the left pane of the camera screen. There appears to be enough room in the left pane of UI3 to display all 40 presets with thumbnails. Does anyone know if it's possible to have 40 preset thumbnails? I've looked through the options, googled, and couldn't find anything.

 

[bp2008]

UI3 isn't coded to enable 40 presets. You are actually the first person I recall even noticing this.

 

[AMP]

UI3 isn't coded to enable 40 presets. You are actually the first person I recall even noticing this.

I can't imagine many people have the need for more than 20 presets. My PTZ overlooks the Cincinnati skyline and the Ohio River, and I can actually fill up more than 20 with various things. There's no easy code mod I could do myself in any of the UI3 directory files is there? I haven't poked around yet.

 

[bp2008]

I don't think it would be easy to mod in. I'll make a note to add another 20 presets as an option it in a future update.

 

[AMP]

I don't think it would be easy to mod in. I'll make a note to add another 20 presets as an option it in a future update.

Awesome, thanks so much taking it in a feature request and possibly implementing in the future!