03-04-2009 07:08 AM
in my application i'm making screenshots (every second), write it to Bitmap, then create JPGEncodedImage (using encode() method). and this EncodedImage is send to the server. My problem is, that screenshots comes too slow. i think (except internet connection) that this is caused by the fact, that JPGEncodedImages may be too heavy. i set its' quality to 60.
do You have any ideas how can i make sending screenshots faster without loosing quality too much?
03-04-2009 07:26 AM
Can you tell use where the bottleneck is?
Sending screenshots at that rate over anything other than WiFi would seem to be me to produce a bottleneck in the transmission, but you seem to suggest it is the encoding you wish to optimise?
03-04-2009 08:39 AM
Time for a new dictionary then - it is in both my Chambers and my Oxford...
Google and Wikipedia are good places to look for definitions too, here is the Wikipedia reference...
Hopefully the Wikipedia entry will explain well enough so that you can answer my question.
03-04-2009 11:34 AM
LOL, wiki links are my favorites. A bottleneck usually refers to one process in a series of sequential
processes which consumes the most resources or is the rate limiting step in going from reactants
to products. For example, either the diffusion of reactants to a catalytic surface or the reaction
rate may be the bottleneck depending upon ambient conditions.
This is normally what would obviously be suggested to anyone glancing at a coke bottle.
I've noticed I slip into colloquialisms quite often
Both CPU and bandwidth can be rate limiting. Usually sticking with native codecs is a good choice but
then you need to do IO somehow. An earlier poster happened to be able to express image as SVG which
may in fact be a reasonable option in some cases. Model based compression schemes
( I'm not really sure of taxonomy here as it is similar to transform coding except your basis set is
rather odd things like "circles" or object in SVG rather than sine waves)
can be quite CPU intensive in the general case,