Autoplay enabled means when one clip ends the next one will begin. Autoplay disabled means the video player will just stop at the end of every clip. Is that not happening?
Blue Iris UI3
- Thread starter bp2008
- Start date
Autoplay enabled means when one clip ends the next one will begin. Autoplay disabled means the video player will just stop at the end of every clip. Is that not happening?
Albert Einstien
Young grasshopper
Thanks bp, I thought autoplay meant when you select a clip in the clip pane, it just starts playing automatically. thanks for the explanation. All is working okay.
Does anyone know how to get groups to show up under the "Filter alerts by" and "Current Group" drop downs? I made various groups including 1 for each individual camera to try to get individual camera alert filtering like UI2 had but only 1 of those groups I made actually shows up in UI3. The rest do not show at all?
awsum140
Known around here
UI3 filters the alert/clip lists by whichever camera(s) you have currently visible. To filter by a single camera, just click on that camera. It will be maximized and the alert/clip list will be filtered. The dropdown list just lets you pick different groups so you can filter by a group of cameras instead of by single cameras only.
And @awsum140 is right. Blue Iris doesn't report single-camera groups via its web server so UI3 does not know they even exist.
And @awsum140 is right. Blue Iris doesn't report single-camera groups via its web server so UI3 does not know they even exist.
looney2ns
IPCT Contributor
bebopblues
n3wb
- Feb 26, 2018
- 6
- 0
Is there a way to keep the audio streaming when minimizing or switching to another tab? That's how ui2 worked and I like that option again.
If you need it to keep streaming you will need to leave the browser tab open (put it in its own window and don't minimize it). The fact that UI2's audio player does not react to the tab becoming hidden is an oversight, actually.
bebopblues
n3wb
- Feb 26, 2018
- 6
- 0
If possible, I would prefer developers give the user the option rather than decide for us on how things should be. So, a simple check box for background audio would be nice.
UI3 version 25 is now available. For this update, I decided to bring back the more-efficient native video player in Chrome, for as long as it lasts. Google has plans to remove support for the framework it is based upon, but until that happens, UI3's H.264 player should be much more efficient in Chrome than in any other browser.
This player has had relatively little testing, so I'd appreciate it if as many people as possible download and try it before it goes live with a Blue Iris update.
Get it here: bp2008/ui3
To install releases from github, download the release zip and extract it to Blue Iris 4/www, overwriting all files.
This player has had relatively little testing, so I'd appreciate it if as many people as possible download and try it before it goes live with a Blue Iris update.
Get it here: bp2008/ui3
To install releases from github, download the release zip and extract it to Blue Iris 4/www, overwriting all files.
Interesting. Uncapped bit rate has often presented problems, but unfortunately there's nothing I can do about them.
I fixed a couple of bugs with the new player, including one really nasty one where it didn't deactivate and reactivate correctly when switching to and from a jpeg streaming mode.
Version 26 has the fixes: bp2008/ui3
To install releases from github, download the release zip and extract it to Blue Iris 4/www, overwriting all files.
Version 26 has the fixes: bp2008/ui3
To install releases from github, download the release zip and extract it to Blue Iris 4/www, overwriting all files.
Jeff DeWolfe
Young grasshopper
- Feb 18, 2017
- 31
- 13
Just installed this. Whatever comes with 4.7.5.3 wasn't working. After I installed this and restarted the service, it was back up and running with no issues.
I just tried updating to 4.7.5.3 on one of my other systems and it was fine. Not sure what was wrong in your case.
Also there is never any need to restart the service when installing UI3 or when making any other changes in the web server directory. As far as Blue Iris is concerned it is just a few files it delivers when a web browser wants them.
Also there is never any need to restart the service when installing UI3 or when making any other changes in the web server directory. As far as Blue Iris is concerned it is just a few files it delivers when a web browser wants them.
Jeff DeWolfe
Young grasshopper
- Feb 18, 2017
- 31
- 13
Good to know, thank you. Yeah, I'm not sure what happened. I did the update and the UI went down. After placing the new files it has been up solid.
looney2ns
IPCT Contributor
I'm really excited for this update!! I learned today that HTML5's "Media Source Extensions" API no longer has the requirement that the MP4 files you send it must start with a keyframe. Apparently that hasn't been a requirement for a few years now, and I feel like such a fool for not discovering this sooner.
Anyway, this means UI3 can now take full advantage of hardware-accelerated H.264 decoding using the browser's native player, without adding a ton of video delay. This should work in all major browsers. I'm interested in hearing how it works for everyone else. Here is what I've tried so far:
To install releases from github, download the release zip and extract it to Blue Iris 4/www, overwriting all files.
Version 27
Anyway, this means UI3 can now take full advantage of hardware-accelerated H.264 decoding using the browser's native player, without adding a ton of video delay. This should work in all major browsers. I'm interested in hearing how it works for everyone else. Here is what I've tried so far:
- Chrome (works great)
- Opera (works great)
- Firefox (works, but stuttery -- still requires the configuration change noted in the first post)
- Edge (terrible, adds about 3 seconds of delay and it gets worse over time)
- Android Chrome (works pretty well, adds some delay though)
To install releases from github, download the release zip and extract it to Blue Iris 4/www, overwriting all files.
Version 27
- Added a new H.264 player option that uses HTML5 Media Source Extensions for more-efficient playback than the old JavaScript player. It has a few compatibility issues in some browsers, most notably MS Edge where I have disabled it by default.
- The situation is now handled better when the browser refuses to play camera audio until the first user interaction with the page. The audio speaker icon will turn red and the first interaction afterward will cause audio to begin working.
- Fixed a bug in a debugging utility function in the Queue library.