5.9.9.96 is broken for me, had to remove

[imrj]

i couldnt live view some cameras on the web ui (Tapo and Reolink).....did a lot of troubleshooting until i thought I read on Reddit that 5.9.9.96 has issues, as soon as i went back to preview release the cameras started working, anyone else had this happen?

 

[TonyR]

Do you have a link to that on Reddit? I'd like to read it.

 

[Bruce_H]

Do you have the Direct to Wire setting turned on in "Blue Iris Settings", "Web Server", "Advanced", under Content click the "Configure" button, look for the check box "Direct-to-wire where possible (H.264). apparently this broke with 5.9.9.96, this was reported by another user and I have confirmed that it is a problem, not sure if this has been reported to support as I don't use this setting!

 

[bp2008]

I can confirm Direct to Wire is not working in 5.9.9.96. I don't normally use it because I do not like the tradeoffs, so hadn't noticed until you mentioned that.

 

[jrbeddow]

I can confirm Direct to Wire is not working in 5.9.9.96. I don't normally use it because I do not like the tradeoffs, so hadn't noticed until you mentioned that.

Can you give a quick summary of the tradeoffs? Consequences for UI3 streaming?

 

[bp2008]

Direct-to-Wire pros:

• Much less CPU cost to live stream a single H.264 camera.
• There's absolutely no quality loss since your client app will be receiving the same exact video frames that Blue Iris originally received, without re-encoding.
• The video stream tends to be smoother because frames don't get dropped. Especially for 4MP and 8MP cameras at high frame rates.

Direct-to-Wire cons:

• Startup of the video stream is delayed until the next i-frame/keyframe arrives in the stream. How long this can take depends on the i-frame interval of the camera.
• Blue Iris can't do any kind of image transformation, such as adding overlays or rotating the video.
• It only works with single-camera H.264 live streams. Not H.265. Not recordings. Not multi-camera views. This is an important aspect many don't seem to understand.
• When direct-to-wire is working, the encoder settings specified by the client are ignored. (most significantly, the bit rate is not limited like it normally would be)
• But when direct-to-wire is not working, the encoder settings are not ignored. So it still matters which streaming profile you have selected.
• Compatibility issues are more likely (you may get video corruption or streams that fail to play).

Direct-to-wire is certainly situationally useful. In the admittedly rare case that I want to use it, I do not enable it in the "Streaming 0" profile. Instead I enable it in Streaming 1 or Streaming 2, or just enable it in one or two specific UI3 streaming profiles.

If you had an always-on device streaming one single camera 24/7, that is like an ideal use case for direct-to-wire.

 

[Keizer]

I can confirm Direct to Wire is not working in 5.9.9.96. I don't normally use it because I do not like the tradeoffs, so hadn't noticed until you mentioned that.

I installed 5.9.9.96 right when it was available and had the same issue with Direct to Wire. I rolled back to .95 and all was well. What's strange is I installed 5.9.9.96 again last night and got Direct to Wire working just fine. I was in UI3 viewing a camera with Direct to Wire unchecked, and while the camera was in full screen I went back into my BI PC and checked Direct to Wire. Backed out of the camera I was viewing in UI3 and viewed a few more cameras in full screen. Direct to Wire was working fine and has been ever since. Not sure if that voo doo process really had anything to do with it but I have done stranger things with Blue Iris to get things to work.