Refreshing Image URL - size too large

Hey guys...wasn't sure what section this fits in since it affects all control pages regardless of client.

I just upgraded my front door camera from a 1.2MP to a 4MP cam running 2550x1440 to BlueIris...control pages on certain tablets were set to refresh a URL every second to show the output of that camera.

After upgrading the camera, the log now was filling with this:

Code: Select all

   WebServer                       http://192.168.100.31:8050/image/FrontDoor size too large: received 830099 / max 768000
   WebServer                       http://192.168.100.31:8050/image/FrontDoor size too large: received 835319 / max 768000
   WebServer                       http://192.168.100.31:8050/image/FrontDoor size too large: received 835319 / max 768000
   WebServer                       http://192.168.100.31:8050/image/FrontDoor size too large: received 835306 / max 768000

Is there a way to increase the size limit? I can't seem to find a way to make BlueIris use smaller JPEGs in there. I may email Ken with BlueIris and see if there's a way or if he'd consider making it an option at some point.

Just curious if I was missing something in Indigo that would allow me to get the image capability back.

Thanks
Ross

Aaaand shortly after I posted this...I found where in BlueIris you can adjust the JPEG compression levels...so I have it working now.

For anyone who may ever search and find this, on the affected camera(s) open the Camera Properties
Go to the Webcast tab
Adjust the JPEG Quality to a lower number until you get a usable image.

For me on this Reolink RLC-420 at 2560 x 1440 I reduced the quality to 65% and it's working fine now.

Thanks
Ross

[jay (support)]

Hey guys...wasn't sure what section this fits in since it affects all control pages regardless of client.

I just upgraded my front door camera from a 1.2MP to a 4MP cam running 2550x1440 to BlueIris...control pages on certain tablets were set to refresh a URL every second to show the output of that camera.

After upgrading the camera, the log now was filling with this:

Code: Select all

   WebServer                       http://192.168.100.31:8050/image/FrontDoor size too large: received 830099 / max 768000
   WebServer                       http://192.168.100.31:8050/image/FrontDoor size too large: received 835319 / max 768000
   WebServer                       http://192.168.100.31:8050/image/FrontDoor size too large: received 835319 / max 768000
   WebServer                       http://192.168.100.31:8050/image/FrontDoor size too large: received 835306 / max 768000

Is there a way to increase the size limit? I can't seem to find a way to make BlueIris use smaller JPEGs in there. I may email Ken with BlueIris and see if there's a way or if he'd consider making it an option at some point.

Just curious if I was missing something in Indigo that would allow me to get the image capability back.

FYI, all traffic through reflectors has to bounce off or our servers, which means we have to pay for bandwidth. This is 1) built into the current cost of the UTD subscriptions and 2) is why we don't support video feeds and 3) why we limit the size. We keep an eye out for people using large mounts of bandwidth and will notify if it becomes a problem, so I'd recommend taking a serious look at the frequency that is truly needed for refreshing images (and how those pages are represented in your page hierarchy).

I don't use the reflectors at all...my firewall at home allows traffic on the ports I assigned and I have my domain name connected via DDNS...so everything is a direct connection. When inside the firewall it resolves the local IP and when any device is outside the firewall it gets the public IP of the firewall and routes in from there.

Thanks
Ross

[matt (support)]

I don't use the reflectors at all...my firewall at home allows traffic on the ports I assigned and I have my domain name connected via DDNS...so everything is a direct connection. When inside the firewall it resolves the local IP and when any device is outside the firewall it gets the public IP of the firewall and routes in from there.

Gotcha. We actually use two different limits: ~350K for over reflectors, and ~750K when not. The former is for preventing excessive reflector bandwidth on our servers (some users were leaving iPads open 24/7 on security Control Pages with several images refreshing frequently, all over a reflector) and the latter is more of a performance cap to keep the Web server from becoming too overloaded. We'd definitely consider increasing the latter above 750K if it needs to be, but I'd like to keep some practical cap on there to encourage folks to use compression/smaller images to keep things running smoothly.

Gotcha. We actually use two different limits: ~350K for over reflectors, and ~750K when not. The former is for preventing excessive reflector bandwidth on our servers (some users were leaving iPads open 24/7 on security Control Pages with several images refreshing frequently, all over a reflector) and the latter is more of a performance cap to keep the Web server from becoming too overloaded. We'd definitely consider increasing the latter above 750K if it needs to be, but I'd like to keep some practical cap on there to encourage folks to use compression/smaller images to keep things running smoothly.

Yeah...I have exactly that nightmare scenario that would kill your servers. 9 tablets throughout the house and most of them show at least 1 camera view (Front Door) that refreshes every second. Of course if I was relying on your servers I would not have it configured that way.

If you coded in a check where the client could identify LAN or not and allow unlimited traffic on LAN...having a control page capable of a MJPEG stream would really be useful, plus having the control page open a single connection to the camera server that stayed active while the page was displayed would help. Each image refresh counts as a login event to the Blue Iris server, and all my tablets together total about 100K logins per hour. Creating a single login for a stream would cut that down to <20 at any given moment.

Could the Indigo Touch app technically allow the tablets to establish a link direct via LAN to the Blue Iris server, taking the burden off the Indigo webserver?

(aka "Hey...can you rewrite everything for my particular situation?"...lol)

Thanks
Ross

I can't seem to find a way to make BlueIris use smaller JPEGs in there.

Actually, just ask BlueIris for a smaller image:

Code: Select all

http://192.168.100.31:8050/image/front?w=960

Where 960 is the width, and matches the width of the image object on your control page. You can do the math to adjust the height the object on your control page to preserve the aspect ratio (such as 542 in this fabricated example).

There are also parameters to adjust the quality level of the image as well, but that shouldn't be necessary.

Actually, just ask BlueIris for a smaller image:

Code: Select all

http://192.168.100.31:8050/image/front?w=960

Where 960 is the width, and matches the width of the image object on your control page. You can do the math to adjust the height the object on your control page to preserve the aspect ratio (such as 542 in this fabricated example).

There are also parameters to adjust the quality level of the image as well, but that shouldn't be necessary.

Cool...thanks! Didn't know it would do that. Reducing the quality had fixed the errors and worked on my IOS clients, but the few Android tablets I have running Adam's (RogueProeliator) DomoPad Android Client wouldn't show the image. Changing it to asking BI for an image exactly the size of the control page image fixed it.

This is why I love these forums...problems are seldom problems for long.

Thanks!
Ross