Blue Iris UI3

bp2008 said:
UI3 can't load separate audio streams of any kind. Only whatever comes with H.264 video.

How did you add the group video stream to blue iris as a new camera? It should definitely be capable of doing audio, but you might have to use a different URL to stream from than you are currently using. 5.3.1 - July 16, 2020 Your Blue Iris web server now is also an RTSP server.
Click to expand...
I was using the neighbor's server as RTSP and it worked - but frequently dropped out and no audio. I recently moved to using Raw h264 with the IP of the server, and /h264/[groupname] under the stream. Much more reliable, but still no audio...

1746393634891.png

For grins, I added /h265/[camera_shortname] to the audio field, but it's just whitenoise/static.
 
You could try the .ts or HLS streams that Blue Iris provides (see help file for URLs), to see if they are any better.

I believe for either of those it would be appropriate to select the Model: "HTTP Live Streaming (HLS, M3U8), MP2TS."

Ironically it seems Blue Iris probably does not support consuming the proprietary protocol it uses to send H.264 to mobile apps and UI3, which is a shame because we know that does audio just fine.
 
Also, I think Blue Iris does support streaming "WAV" audio via some other URL. UI2 used to be able to use that way back in the day. That is a path you might try entering into the Audio path field. Otherwise you want to leave the Audio path empty.

Here we are.

/h264/{cam-short-name}/temp.ts. Pull an MPEG-2 transport stream (MIME type video/MP2T).
Click to expand...

/h264/{cam-short-name}/temp.m or .m3u8. Pull a virtual M3U8 file (MIME type application/
vnd.apple.mpegurl). This will play in QuickTime, iPad and the iPhone using the Apple HLS
(HTTP Live Streaming) format.
Click to expand...

/audio/{cam-short-name}/temp.wav. Pull a raw audio stream (MIME type audio/x-wav).
Click to expand...
 
I just tried both and no beans. I suppose I could just create another camera going to just one of the remote cameras and point to that with the audio channel - but I'm up against the 64-camera hard limit (which is why I'm going with the group/index-to-camera option in the first place). Thanks for the suggestions. I may just reach out to Ken to see if he has any other ideas.
 
  • Like
Reactions: bp2008
Hello,

I have tried many of the functions/parameters for the MQTT toast feature and so far, all work as described. Thank you so much for writing the extension as this new feature is really helpful.

One revision did occur to me, but it is a minor suggestion. For the "ui3/{instance_id}/toast/{toast_id}" where one puts a hardcoded unique toast_id in the message (for multiple toast popups), would it be possible to instead just write "ui3/{instance_id}/toast/multi" or something similar, and then internally UI3 would use an algorithm to insert a unique ID in place of multi within the MQTT message. I don't believe one needs to know the toast ID on either end of the communication so any value generated by UI3 should work.

Thx again for this addition.
 
@bp2008 sharing this here because it shows how nice web push notifications can be. Suppose if this was natively integrated into Blue Iris/UI3 then there would be no need for any app installed, you'd have cross-platform compatibility, fast notification alerts, and battery efficient. Great work on UI3 by the way!

 
@wtf911 I agree native web push support would be nice. I've thought a lot about it before and brought it up to the BI dev before, but if I recall he didn't respond to my email (this is pretty typical for such requests from me).

I see 3 challenges with natively supporting web push:

1. I personally do not use or care about alert notifications, and I've never even set them up before in the existing native apps. This means I am not very familiar with how notifications are done already, and I am not motivated to spend a lot of time working on it, which is required because:

2. I would consider it a failure if web push notifications were not at least as easy to set up as for Android/iOS. Dealing with the HTTPS requirement seems like the biggest part of this. Self-hosting HTTPS for every Blue Iris user is a pipe dream -- most would be stuck with self-signed certificates and warning pages which I consider an absolutely unacceptable user experience. Therefore this would require a cloud-hosted website to proxy the notifications through. Like ntfy.sh is doing for you, but in this case I'd have to custom-build it for tight integration with UI3 and Blue Iris, and maintain the service indefinitely. All of this is completely within my skill set, but it is a lot more than I want to do for free.

3. This would require lots of collaboration with the BI dev since he's the only one who can make additions and changes in the BI local console. That is time-consuming for both of us.
 
  • Like
Reactions: wtf911 and jrbeddow
bp2008 said:
@wtf911 I agree native web push support would be nice. I've thought a lot about it before and brought it up to the BI dev before, but if I recall he didn't respond to my email (this is pretty typical for such requests from me).

I see 3 challenges with natively supporting web push:

1. I personally do not use or care about alert notifications, and I've never even set them up before in the existing native apps. This means I am not very familiar with how notifications are done already, and I am not motivated to spend a lot of time working on it, which is required because:

2. I would consider it a failure if web push notifications were not at least as easy to set up as for Android/iOS. Dealing with the HTTPS requirement seems like the biggest part of this. Self-hosting HTTPS for every Blue Iris user is a pipe dream -- most would be stuck with self-signed certificates and warning pages which I consider an absolutely unacceptable user experience. Therefore this would require a cloud-hosted website to proxy the notifications through. Like ntfy.sh is doing for you, but in this case I'd have to custom-build it for tight integration with UI3 and Blue Iris, and maintain the service indefinitely. All of this is completely within my skill set, but it is a lot more than I want to do for free.

3. This would require lots of collaboration with the BI dev since he's the only one who can make additions and changes in the BI local console. That is time-consuming for both of us.
Click to expand...
Thanks for the reply. I'll just mention regarding the HTTPS certs, I had never used Caddy before but after running it, it's really amazing how it simply just works. Runs on Windows, can run as a service, supports a simple few line config file to get a reverse proxy going, and no matter what website you throw at it as long as your router has ports 80 and 443 forwarded it will get you Let's Encrypt certs automatically no work needed for every new domain you route to it.
 
wtf911 said:
Thanks for the reply. I'll just mention regarding the HTTPS certs, I had never used Caddy before but after running it, it's really amazing how it simply just works. Runs on Windows, can run as a service, supports a simple few line config file to get a reverse proxy going, and no matter what website you throw at it as long as your router has ports 80 and 443 forwarded it will get you Let's Encrypt certs automatically no work needed for every new domain you route to it.
Click to expand...
Yup, in fact it is even possible with just port 443 forwarded, via the TLS-ALPN-01 validation method supported by LetsEncrypt and Caddy. I even implemented that validation method in my own reverse proxy server I wrote.

Unfortunately, just getting that far is difficult for a lot of users (thanks largely to CGNAT), and then some don't want to expose their Blue Iris web server online, which makes it a lot trickier for them to get trusted certificates.
 
Any idea what could be causing this flickering of video streams? It's been present for months on the console, but never on UI3 - until this morning. What's odd is it seems to only do it on the native display resolution when the browser is maximized. Any browser smaller than the entire screen, it doesn't do it.

Console:

View attachment glitchy BI console video.mp4

UI3:
View attachment 2025-05-09_6-05-18.mp4

It's interesting that it's the same video streams...

I have yet to reach out to Ken on this as I hardly ever use the console (a testament to how functional UI3 has become).

eta: When I set the "preferred UI scaling" to "medium" or less, the problem goes away, "larger" or "auto" it flickers, if that helps nail it down.

eta2: If I turn off "dynamic group layout" it stops flickering - even if "preferred UI scaling" is set to "auto".

eta3: Setting "Dynamic Group Max Resolution" to minimums has no impact on the flickering.
 
Last edited:
erkme73 said:
Any idea what could be causing this flickering of video streams? It's been present for months on the console, but never on UI3 - until this morning. What's odd is it seems to only do it on the native display resolution when the browser is maximized. Any browser smaller than the entire screen, it doesn't do it.
Click to expand...

Interesting. I've never seen anything like that before. Your camera layout is very unusual. I'm not sure how you even would accomplish this overlapping cameras thing you have going on.

It seems the flickering only happens at very specific stream resolutions, as evidenced by the behavior changing when you make even very minor changes to UI3's video viewport size. But this issue is actually happening within Blue Iris. UI3 has no such control over camera layout beyond deciding what resolution to ask for.
 
  • Like
Reactions: erkme73
Buxton said:
Hello,

I have tried many of the functions/parameters for the MQTT toast feature and so far, all work as described. Thank you so much for writing the extension as this new feature is really helpful.

One revision did occur to me, but it is a minor suggestion. For the "ui3/{instance_id}/toast/{toast_id}" where one puts a hardcoded unique toast_id in the message (for multiple toast popups), would it be possible to instead just write "ui3/{instance_id}/toast/multi" or something similar, and then internally UI3 would use an algorithm to insert a unique ID in place of multi within the MQTT message. I don't believe one needs to know the toast ID on either end of the communication so any value generated by UI3 should work.

Thx again for this addition.
Click to expand...
This is implemented in UI3-291. You can now omit the toast ID or use the toast ID "multi" to allow multiple toasts to exist at the same time.
 
  • Like
Reactions: looney2ns
Please COPY this text to share with support. Error in UI3 (v 290 / 5.9.9.52)

Uncaught NotSupportedError: Failed to execute 'createBuffer' on 'BaseAudioContext': createBuffer(1, 1152, 16000) failed.
at http://censored_hostname/ui3/ui3.js?v=290-5.9.9.52 [29284:24]
NotSupportedError: Failed to execute 'createBuffer' on 'BaseAudioContext': createBuffer(1, 1152, 16000) failed.
at PcmAudioPlayer.AcceptBuffer (/ui3/ui3.js?v=290-5.9.9.52:29284:24)
at PlayDecodedAudio (/ui3/ui3.js?v=290-5.9.9.52:29259:10)
at AudioContext.<anonymous> (/ui3/ui3.js?v=290-5.9.9.52:29238:4)

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36
 
JNDATHP said:
Please COPY this text to share with support. Error in UI3 (v 290 / 5.9.9.52)

Uncaught NotSupportedError: Failed to execute 'createBuffer' on 'BaseAudioContext': createBuffer(1, 1152, 16000) failed.
at http://censored_hostname/ui3/ui3.js?v=290-5.9.9.52 [29284:24]
NotSupportedError: Failed to execute 'createBuffer' on 'BaseAudioContext': createBuffer(1, 1152, 16000) failed.
at PcmAudioPlayer.AcceptBuffer (/ui3/ui3.js?v=290-5.9.9.52:29284:24)
at PlayDecodedAudio (/ui3/ui3.js?v=290-5.9.9.52:29259:10)
at AudioContext.<anonymous> (/ui3/ui3.js?v=290-5.9.9.52:29238:4)

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36
Click to expand...
I haven't seen this happening. Looks like the audio player is crashing (the one used when you unmute camera audio in UI3).

Does it happen reliably? Can you try in an incognito window (so all browser extensions are deactivated) and unmute the audio in UI3 and see if it occurs there too?

Something is either broken about that browser's ability to play audio, or my other theory, you may have an extension that is trying to prevent audio autoplay by sabotaging the browser's audio APIs.
 
Last edited:
  • Like
Reactions: actran and JNDATHP
Anyone have success using the current Brave Browser and UI3?
I've been using an older version of brave till yesterday and it worked very well with UI3, was forced to update brave and now UI3 won't load.

"This site can't be reached"
ERR_ADDRESS_UNREACHABLE

Anyone run into this problem and find a solution.
I'm on a MAC, can still access UI3 using safari but it doesn't work nearly as well as it did using brave, when it worked.

UI3 version 266, Blue Iris version: 5.8.5.3

current version of Brave - 1.78.102
 
bp2008 said:
Then check if there is some kind of VPN being used by Brave (for "privacy").
Click to expand...
They do have a VPN but it's pay to play and not included in the free version.
I'll have my son look into the VPN further just to make sure. We both run Mac OS, both on the newest brave browser, and both cannot access UI3 thru brave anymore.
He tried shutting of their "shield" with no change to UI3 access.

We both also have other devices with older versions of Brave with no troubles - Ipads, laptop, even my phone when at home on WIFI no problems
 
You must log in or register to reply here.
Top Bottom