![]() ![]() I did this by setting the "on alert" function (under alerts tab on my gate camera) to send a text to my cell (which sometimes comes in HOURS late - thanks Verizon), a push to the official BI app, and an email. While BI records on motion, it only pushes an alert when the beam is broken. So grateful!Ĭurrently I get push notifications for external triggers on an IR beam sensor at my gate. No more crashes at all on any of the tablets. Because nope, Blue Iris and UI3 have no such limit, in fact I just opened a 2688x1520 cam streaming H.264 via direct to wire right now and it is fine for me.Įverything has been humming along since reducing the resolutions. It is curious that changing the resolution would make it work. I agree, since UI3 still sends all the other encoding parameters in case the camera is not compatible with direct-to-wire, Blue Iris would be using the resolution arguments as a hint to indicate that the sub stream is "good enough". Which is maddening but completely out of my hands The browser vendors decided to prevent access to WebCodecs except from a secure context. Or if you happen to have an HTTPS reverse proxy server available to access Blue Iris with, then you would be able to try the WebCodecs player as a third option that would likely be more efficient than JavaScript. It is less efficient but usually behaves more predictably than the HTML5 player. There's a strong chance the JavaScript H.264 player would work with those cams at native resolution if you switched to that in UI3's settings. But that is really a long shot because plain "H.264" should be as basic and as widely-supported as it can get. All I can say is you might try other H.264 encoding options if your cameras have them (like H.264H) because those might subtly affect the encode in a way that mysteriously works better. Unfortunately the inner workings of H.264 are way over my head so I likely would not be able to figure out a fix even if you were to provide remote access for me to reproduce the issue. Whether the fault is in UI3's code or elsewhere, I could not say. So my best guess is the cameras are doing something unusual with the H.264 frames, and UI3's HTML5 player is not handling it properly. ![]() Because nope, Blue Iris and UI3 have no such limit, in fact I just opened a 2688x1520 cam streaming H.264 via direct to wire right now and it is fine for me.Īny limit imposed by the web browser, OS, video driver, etc would also affect normal non-direct-to-wire streams too. Is there perhaps a resolution limit with BI/UI3 D2W?Ĭlick to expand.It is curious that changing the resolution would make it work. Interestingly, if I drop the profile to 480p, with d2w enabled, I don't get the error, but the stream is 4:3 and poor quality (presumably I'm getting the sub-stream feed).Īny idea what could be causing this error or how to avoid it? I'll play a bit with the main video settings to see if I can find a combination that won't throw an error.ĮTA: I dropped the resolution to 1920x1080 on both cameras, and the problem resolved on d2w streaming on the main profile on all devices. Other cameras (same make/model) don't have the issue despite also being D2W streams. When I use the 1MP profile and switch the D2W from "inherit" to "yes" I get the black screen and error on these two cameras. No problem with composite/group images either. Two cameras that are having this issue have the following video config settings: Happens on Chrome/Brave or the default Silk browser. This is occurring on multiple Fire 10 tablets (latest version) as well as older 8th gens. I'm running 225 on 5.6.53, but problem has occurred since 221. ![]() I am having issues with PIPELINE_ERROR_DECODE: video decoder reinitialization failed: MEDIA_ERR_DECODE on several cameras when using D2W. Old copies of ui3-local-overrides.js all referred to the old setting name which does not exist anymore, so they don't cause unwanted interference. I deleted the old setting, added a new one to replace it, and added code to migrate everyone who previously had "HTML5" selected so they instead had "Automatic" selected. One specific example is when I added the "Automatic" choice for the H.264 Player setting. If I need to change the way a particular setting works (which is unusual but it does happen sometimes), I delete that setting and create a new one with a different name, and add some code to migrate people's previous preference into the new setting. If I add a new feature, it probably uses a new setting which your local overrides file won't interfere with because that setting didn't exist at the time when you created the file. Each setting has a unique name, and if I ever delete the setting from UI3 in the future, then the part of the local overrides file that overrides that setting becomes non-functional. When you download a local overrides file from the link at the bottom of UI Settings, that file contains a snapshot of all your current settings and their values. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |