BI 5 Feature suggestion thread

[Pogo]

BVR Trimming

It would be nice to trim and save an existing BVR section as a separate BVR without re-encoding. Allows to save plenty of disk space in home setup, if done daily to keep only small video sections of interest. When required, some of these sections can be converted later to MP4, possibly in bulk on a more powerful PC. However, conversion might make them inadmissible into evidence in some jurisdictions, where video evidence is often treated by courts as "hearsay", especially if its not the original footage.

Why Trim feature wasn't added for all years BI exists? Its obvious not everyone wants or able to keep tons of useless recordings, or re-encode select sections daily for no particular reason, but only because its impossible to trim the BVR and preserve its overlay timestamp.

Better late than never...

Feature Request.jpg (102.5 KiB) Viewed 7489 times

[BIguy10]

The ability to see what recordings a user has watched.
We currently have the ability to see how many frames a user has watched and the duration of the video under the Connections tab in Status window but having the ability to see exactly what videos a user reviewed would be very useful for auditing users to make sure they're watching the right things.

[Pogo]

....to make sure they're watching the right things.

And who makes that determination?

Using Blue Iris to spy on its own users is certainly a novel use case. Not sure I'd call it a 'feature'.

Seems like key and screen loggers in the respective workstations of concern would be a more effective technique.

[camis]

Choose the alert label for an object in an AI configuration by selecting the video frame with the largest bounding box. This approach is typically more effective because larger objects within an image are generally recognized with higher accuracy.

This approach addresses my issue where a fox at a distance is mistakenly identified as a cat by the AI, often with a confidence level greater than 80%. As the fox moves closer to the camera, it is recognized as a fox with a confidence level exceeding 95%. Setting the confidence threshold above 95% could result in missing some fox detections.

[war4peace]

Feature Request

In Settings / Storage / Folders section, we can configure paths for Database, New, Stored, Alerts and AUX1 through AUX13.

The problem:
The way this works is by either browsing to an existing path, or entering an existing path manually (via copy/paste).

If we decide to move files around and change folder paths for various reasons (e.g. adding a storage device), having Blue Iris point to a new path requires shutting Blue Iris down, moving files, starting Blue iris, changing the paths and then restarting Blue Iris again. This usually triggers a DB rebuild, because Blue Iris first checks the old path, which is now obviously empty, then after changing path it rebuilds the database because files are detected again at their new destination.

The solution:
Add functionality which also allows usage of OS Path Environment Variables instead of hardcoded path strings.
That way, we could change the paths in the Environment Variables directly, leading to a simplified path update method for Blue Iris, no longer requiring a DB rebuild.

This allows the following simplified approach:
- Shut down Blue Iris;
- Move files to their new location;
- Change Environment Variables to point to the new paths;
- Start Blue Iris again.

No DB rebuild and/or file checks are required any more.

Related request: Have the ability to rename AUX1 through AUX13 to friendly names (e.g. "Camera 1 Timelapse").

Thank you for taking this request into consideration!

[jeyking]

Is this thread still usefull for posting feature requests?

It seems like this thread was started by a user. Who says it's (still) read by developpers? I don't see any reply in the sense of confirmation or something like that.

Why isn't this thread sticky? (Came accross it by accident)

[TimG]

All valid questions.

As I understand it, the Management don't visit here very often. I have spotted Ken logging in now and then, but he hasn't posted here in a long time. The forum is basically a user to user forum, with the advantage that I can inform Ken if I see an issue that he needs to know about, or if there is a question that only he could answer.

The best way to tell Ken about a feature suggestion is to write an email to Support, with a use case for the desired change. I have done this a few times now, and two were actioned, and the other was rejected (Leanback BI5 app).

I haven't "stickied" this thread since I don't think it will help it to be read by the Management, but I have created a poll to see what the rest of the world thinks and will "sticky" it if the result of the poll warrants it. It's in your hands now. Being a Brit I would have normally have posted "Bah Humbug!" at this time of the year but decided to go with Yes/No/Meh!

[jeyking]

I presume you voted No?
I don't get it. You'd rather see suggestions go down a black hole? I don't think so, do you? Or am I misinterpreting this?

[MikeBwca]

All suggestions should be sent to BI Support. The more they get on a particular subject, the more likely they are to implement it. Not saying they would ot should.

[TimG]

I presume you voted No?
I don't get it. You'd rather see suggestions go down a black hole? I don't think so, do you? Or am I misinterpreting this?

As MikeBwca said, please send suggestions directly to Support or they may be missed. We can discuss things here to gauge the reaction of our peers, but then need that use case and Support email to get it actioned.