I’m working on a TCP/SOAP interface which consumes a JPEG stream from an image server. It works fine, but I get a heavy load of data (full images at full resolution at full frame rate).
I tried to use 25 at live methodcall, which would fit perfectly my requirements, but the images kept returning the same resolution and size from the original ones.
Since it didn’t work to reduce the stream size, I tried to reduce frame rate with , which is not quite comfortable for the user, and also the resolution with on live methodcall and on connect methodcall. It worked as expected, but upscaling back these reduced images does not have the same quality perception of a corresponding tuning.
One extra observation: although I had set to no, the images I eventually requested which were occasionally larger than the native camera resolution were returned in the resolution I requested, suggesting that my was ignored, so I had to filter these requests in order to not to increase even more the network congestion.
It is not recommended to ask the Image Server protocol for transcoded JPEGs, it can potentially overload the Recording Server and cause it to malfunction.
Please consider instead to use the Mobile Server, the Mobile Server has been optimized for this usage and can easier be scaled.
The compression rate in this XML flow sample is 25, but you can change it to any other value and the image quality is kept on the same level, not reducing the stream size.