Go to UI3 screen, upper right corner and click on 3 dots, click on "Help", click on "More Topics", click on "URL Parameters".is there any url commands that can be used to say open ui3 to a certain group in full screen or a particular camera?
ie. 127.0.0.1/ui3.htm?camera01 or ?group01 etc?
Oh, yes, that absolutely would cause this effect. As BI writes to a clip it continuously gets longer and therefore its percent playback position changes. Improving upon how UI3 handles this is on my to-do list.So I'm thinking the line in the sand is whether the clip_of_origin is still being written to by Blue Iris or not.
UI3 has no control over this, but you should be able to solve it by going to BI's camera properties > Audio tab and unchecking the "Webcast audio" box for any camera you want to remain silent.I wasn't expecting to hear audio from the hidden cameras.
Yes, there was.Has there been a recent change in UI3 regarding the H.264 streaming profile? I suddenly can't see H.264 streams using Edge, IE or Firefox. Only Chrome now works and I can't use Jpeg streams for remote installations as the data used is too much. Any ideas please? I'm running Version 4.8.4.7 and I noticed this behaviour with the previous version as well.
Thanks very much!So if you want to stream H.264 well in UI3 you need to use a browser based on Chromium such as Chrome, Opera, Brave, or indeed Chromium itself.
Should be able to manage this with the mobile apps.Also is there a way to access the log file directly without loading the cameras or clips. I manage several blue iris servers that have limited bandwidth so remoting in to check the log file while a client is streaming causes problems.
Never seen that before. I can't even guess what would fix it.Running into an issue where on some phones ui3 cannot login using the carriers service but on wifi only, is there a work around to this? it says redirecting and then goes back to the login page. both were tested using chrome / firefox on android.
The login page works with relative paths so it should not matter in the slightest what the address is.I wrote off the login issue as an anomaly until i was told it happened on more than just my phone, could for whatever reason it be looking for the lan address and not the wan address on the carrier service? is there a way to force it to use the wan address to test this theory? i do have the app and see benefits using both interfaces, i frequently use ui3 for quick testing on other devices.