На 01.12.10 19:40, Conrad Beckert написа:
I'd guess that a single core 2GHz with 1GB RAM box would probably
also work. I wouldn't go any lower though.
that's a pity
Once again, these were by no means accurate "minimum requirements" but
rather a recommendation: Most of the people using and/or working on SIP
Communicator have that kind of hardware so if you want to make sure you
get optimal performance, you may want to get something similar.
since 1.6GHz is a quite common specification- even
today. Netbooks run mostly on 1.6GHz Atom. And these devices are
ideal to carry around and to communicate. (Actually - this is what I
have my eee for) And once again: In most parts of the world, old
equipment must do the job much longer as in the Golden West (tm)
We never made a decision not to support Atoms nor did we ever determine
that they were unable of running SC. For reasons mostly related to the
priorities of currently active developers (and hence indirectly to
funding) we have simply not had the time to evaluate performance and
optimize SC for similar configurations.
I'm planning to upgrade one of my home PCs by the end of the year and
- as it is a station for websurfing, *communicating* and occational
OpenOffice, one of these Nettops should be enough for almost
It should indeed. We should just as well have echo cancellation, jingle
and ice support, gtalk compatibility, desktop sharing, pseudo tcp and a
bunch of other absolutely useful features.
I am not at all implying that performance or platform specific
optimizations are somehow less important. As a matter of fact, we even
discussed a possible round of performance optimizations just a couple of
Right now however, most of us are struggling to finish other, higher
With the voice latency problem on my eee pending, I hesitate to
invest. Would SC make use of a Dual Core?
We do not have dual-core specific code if that's what you are asking.
However, the general performance boost they give you should put you in a
situation that's more similar to the systems that SC is known to work
Note that we never did determine for sure exactly what was causing the
latency issue on your system. I'd suspect that the lower performance
caps are simply surfacing issues that would otherwise appear less often
or not at all. What I am saying is that the problem is probably more
complicated than simply: you don't have the CPU power to handle audio
and video encoding together.
As far as only text messages is concerned, SC runs on an PIII 1GHz at
decent speed. Only one can forget about any multimedia on such a
Is it true that most the multimedia handling is done outside Java by
Yes. With the exception of some audio codecs (e.g. PCMU and PCMA)
Audio/Video grabbing, rendering and [en|de]coding all happen outside
Is there a chance to lower the specs a bit (not much ) to fit
popular hardware considerably expanding the user base.
Absolutely. I expect this to happen in the following months (unless of
course we obtain contributions earlier).
Sorry for nagging
Not at all. Thanks for your support and patience!
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com