Blue Iris UI3

[hikky_b]

Lol...so got Home From work, looked at the suggestion from hikky_b and was about to create a Group when i had a massive face palm moment...hikky_b you were right it was my webcast settings, it was set on the default group and not the group i had created so i changed it from the Drop down menu accessed webcast settings and sure enough 5fps...change to 25 and footage on ui3 is smooth...really appreciate the help, thanks. (helps to take a break from a problem)

Been there, done that! Glad you found the problem

 

[ChrisX]

Can i select a special cam to activate/deactivate Auto Maximize ? Not with groups. ? Thanks

 

[hikky_b]

Can i select a special cam to activate/deactivate Auto Maximize ? Not with groups. ? Thanks

You are not able to specify which cameras Auto Maximize. UI3 will maximize any camera that is triggered or detecting motion.

 

[bp2008]

You are not able to specify which cameras Auto Maximize. UI3 will maximize any camera that is triggered or detecting motion.

Any camera from the current group -- it doesn't monitor the status of cameras outside the current group.

 

[EyeOfSauron]

@bp2008, when displaying ui3 on iOS, there is no way to enable audio. Do you have any idea what the issue might be? AAC should be supported by the iOS browser, so I don't think it's a codec problem. The use case is monitoring cams via an iPad, which is an excellent platform for the task.

 

[bp2008]

I don't use iOS devices so I'm not really sure what the state of them is, but some features don't work. Open UI3's "About" window and see what it says about incompatible features.

To be clear, the missing features are due to Apple restricting the capabilities of the mobile safari web browser engine. Even if you download different web browsers you will probably find they have the same limitations because Apple will not allow any third-party web browser engine on iOS.

 

[EyeOfSauron]

I don't use iOS devices so I'm not really sure what the state of them is, but some features don't work. Open UI3's "About" window and see what it says about incompatible features.

Looks like it's complaining about AudioBuffer.copyToChannel not being supported.

 

[bp2008]

Looks like it's complaining about AudioBuffer.copyToChannel not being supported.

That sounds familiar.

Blue Iris sends audio in a format invented about 50 years ago, and web browsers do not support it natively so I had to decode the audio in JavaScript and feed the raw audio buffers into the Web Audio API. iOS is the only major platform which doesn't allow this for reasons known only to Apple.

It would be technically possible to work around this by encoding the audio as AAC which even Apple's browser should be able to play natively, but that would be quite complex and inefficient, absolutely not worth my time.

 

[OICU2]

Have there been any recent changes that would cause my CPU to max at 100 when viewing through UI3? I started happening a few updates ago. If I stop viewing through UI3, it goes back to normal at about 30-40%. I do have all my cams setup to use the substream, is there a way to confirm UI3 is using all substreams?

Thx

 

[OICU2]

Have there been any recent changes that would cause my CPU to max at 100 when viewing through UI3? I started happening a few updates ago. If I stop viewing through UI3, it goes back to normal at about 30-40%. I do have all my cams setup to use the substream, is there a way to confirm UI3 is using all substreams?

Thx

It may be a BI thing.. I just updated to the latest version and now BI is crashing about every minute and restarting. I haven't changed anything on the system.

 

[bp2008]

I haven't seen any such problem @OICU2. If Blue Iris is using sub streams (confirm by looking at Blue Iris Status window) then UI3 will use them too in group views.

 

[EyeOfSauron]

Blue Iris sends audio in a format invented about 50 years ago, and web browsers do not support it natively so I had to decode the audio in JavaScript and feed the raw audio buffers into the Web Audio API.

Yikes! After seeing their Android app, I am not surprised. Seems like they need some dev help with skills from this century.

Thanks for confirming it's nothing that I can fix, short of reimplementing the webui .

 

[biggen]

Upgrade to stable 5.4.3.12 two days ago and I'm getting errors in UI3 now complaining about "Alerts". Restarting the VM seems to fix it for a while, and then it happens again after several hours. Just restarted the VM and the problem came back immediately.

Any ideas? I've not emailed support yet.

 

[Ssayer]

I had that problem with Amazon Fire's Silk. I switched to Chrome and it's been working fine. Don't look at me...

 

[biggen]

I had that problem with Amazon Fire's Silk. I switched to Chrome and it's been working fine. Don't look at me...

So for me, its broken on Chome but I don't get any of those error messages with Firefox. Odd. I'm on Chrome Version 90.0.4430.93 (Official Build) (64-bit). I'll have to fire up my desktop to check with Edge since that is the only computer I have in the house that runs Windows.

But its definitely something that changed from 5.3.x to 5.4.x giving me issues. I still have my business running 5.3.x and my laptop (with Chrome) works perfectly when viewing those camera. Its only my home installation that I upgraded to stable 5.4.x that is causing the problems with the same laptop/browser combination.

 

[bp2008]

Upgrade to stable 5.4.3.12 two days ago and I'm getting errors in UI3 now complaining about "Alerts". Restarting the VM seems to fix it for a while, and then it happens again after several hours. Just restarted the VM and the problem came back immediately.

Any ideas? I've not emailed support yet.

View attachment 88456

Show that to Blue Iris support. That sort of error has happened many times in the past because Blue Iris does not use a proper JSON encoder, so sometimes it accidentally violates the syntax rules. If the bug isn't obvious on his end, he might ask for remote access to your system. Or worse he might just forward the support email to me and not look at it at all. sigh

 

[biggen]

Email sent!

 

[biggen]

Support emailed me back and told me that 5.4.4.8 fixed the Chrome/JSON issue. I usually don't like to use his non-stable releases but I took the chance to get clips working in Chrome again and, sure enough, they are working again.

 

[bp2008]

Let me guess. Backslashes in your recording file paths (customized paths)? \ is a backslash. They weren't getting escaped correctly in the JSON responses. At least that is what I determined a couple days ago when I logged in to someone's system to figure out the problem. There could have been more issues than just this one because Blue Iris doesn't use a mature JSON encoding library.

 

[biggen]

Let me guess. Backslashes in your recording file paths (customized paths)? \ is a backslash. They weren't getting escaped correctly in the JSON responses. At least that is what I determined a couple days ago when I logged in to someone's system to figure out the problem. There could have been more issues than just this one because Blue Iris doesn't use a mature JSON encoding library.

I didn't do much troubleshooting to determine exactly what was causing the error messages but that sounds right. Chrome was the only browser I found that the issue manifested itself so I don't know if Chrome is more or less strict when it comes to JSON conventions.