Tech Talk - SightSpeed

Tech Talk - SightSpeed

Summary: I have received several public and private requests for more technical information about my first experiences with SightSpeed. Some wanted the gory details about the problems I had, as well.

SHARE:
TOPICS: Linux
3

I have received several public and private requests for more technical information about my first experiences with SightSpeed. Some wanted the gory details about the problems I had, as well. I did feel as if I glossed over some things that I wanted to talk about a bit more, for lack of time and space, so here we go again. Please keep in mind, I have only been working with SightSpeed for a few days, so this is still going to be very incomplete in terms of what SightSpeed can and can't do, and I'm undoubtedly going to be wrong about some of the things that I say, but it won't be the first or the last time for that.

First, the helpful comment posted by Peter Csathy, CEO of SightSpeed, was of course correct. Once into a video call, you can switch to "video only view", and the video window can then be stretched to give you the larger view that I said I wanted. This is very nice indeed, and so obvious it had completely escaped me - I suppose that I had become conditioned by Skype's "fixed size video in a window", so resizing the window didn't occur to me.

Next, also in response to a private query, let me explain just a bit more of what I know about video resolution. The resolution that I mention writing about these video chat programs is what is actually sent between the two computers, it is not necessarily (or generally) the resolution that you see on the screen. The initial SightSpeed video window is considerably smaller than 320x240, so the incoming video is "scaled" to fit in that window; if you resize the video only window, you may increase it to exactly 320x240 (if you are very good or very lucky), in which case you see exactly the video that is being sent, or you may make it larger than that, in which case the incoming video is scaled up to fill the window. In the extreme case, "full screen video" actually takes over your entire display and scales the incoming video to fill it. Most PC displays today are in the range from 1024x768 up to 1600x1200 (or even more), and believe me, 320x240 video scaled up to fill a screen that size is not a pretty sight!

Finally, from the comments, the "conservative approach" and the possibility of an "expert/pro" mode. This is an excellent point, and I think for many users an "expert" mode might be good. But this would have to be an addition, not at the expense of the clarity and conservatism SightSpeed has currently. I was answering technical questions in the Skype forums for some time, and I saw a never-ending stream of questions coming from users who were just confused or overwhelmed by the number of options and configuration settings they were presented with, or by some of the conclusions or actions that Skype would take based on those options.

I was also asked for details about the problems I ran into with SightSpeed. There were only two, and they both turned out not to be SightSpeed problems, or at least not directly. The first was the "choppy audio" problem. It was obvious with the first test call to the SightSpeed "fish tank" that the audio was not good. I assumed then that it was something with the bandwidth, and didn't think much about it until I got the first video call from my brother, and we could hardly understand each other. I then installed SightSpeed on my partner's computer, and was shocked when I tried the test call and the audio was just fine! Her PC is considerably less powerful than mine in pretty much every way (and she forbids me to upgrade it!), so obviously the problem was with my laptop. I worked on it some more, and made no headway. So I removed the Vista disk, and put in one that I had prepared with XP Pro / SP2. I installed SightSpeed, called the fish tank, and the audio was just fine. So obviously the problem is on my laptop, and only when it is running Vista. I wish that I could say that this is the only Vista-related problem that I have!

To me, the important thing about this problem is that it gave me an honest opportunity to check out both SightSpeed technical support and their User Forums. I sent a description of the problem to their technical support email, and got a reply within a few hours. It was obvious from the reply that the person had read and understood my problem, and they made several good suggestions to either try to fix the problem, or gather more information if it didn't get fixed. You can't ask for much more than that from technical support. I also posted a query to the SightSpeed user forums. As I have said before, I was involved in the Skype user forums for some time, and I have seen "the good, the bad and the ugly" there, believe me. There can be a lot of good advice passed around in a forum with competent users and moderators; there can be a lot of bad advice as well, some from people who mean well, but the worst of it is the "ugly" - advice that is incorrect, misleading, confusing or just plain irrelevant. I am pleased to be able to say that the responses I have received in the SightSpeed user forums have been consistently good, and I think that we are on the track to figuring it out, but it's not fixed yet.

The other problem was with firewalls - two problems, actually. The very first time that I ran SightSpeed on my laptop, it worked just fine and connected to the fish tank. The next time I started it up, it said that it couldn't connect to the SightSpeed servers. I use AVG Internet Security, including their Firewall, and it turned out that somehow it had gotten its knickers into a twist over SightSpeed. All I had to do was delete SightSpeed entry from the firewall program list, and the next time I started SightSpeed the AVG Firewall made a new rule, and it has been fine ever since. The second part of this problem is that when I am in my office, the company firewall apparently blocks SightSpeed from connecting also. The symptom is very similar to the previous problem. I'm pretty sure that I just need to find out what ports SightSpeed want to use (I've seen this mentioned in their support web pages), and ask our network administrator to open those ports. Whether he will do that or not is another question...

As usual, this has gone on far too long, and as usual, there is one more thing I would like to say. There has been quite a buzz recently about "High Quality Video" in the IM/chat market. SightSpeed will already do 640x480 resolution at 30 frames/sec, assuming that your camera, PC and communication bandwidth are up to it - and the latter is the key point. They want 1.5 Mb on both ends of the connection in order to do 640x480, and I suspect that kind of bandwidth is not very common yet. But at least they don't try to dictate what kind of camera or computer you have, if your equipment is up to the task, you will get it. I assume that we will see a convergence in the future, as typical bandwidth continues to rise, and SightSpeed continues to improve their video processing so that they require less bandwidth, and hopefully before too long the two ends will meet for a lot more people.

jw 22/11/2007

Topic: Linux

J.A. Watson

About J.A. Watson

I started working with what we called "analog computers" in aircraft maintenance with the United States Air Force in 1970. After finishing military service and returning to university, I was introduced to microprocessors and machine language programming on Intel 4040 processors. After that I also worked on, operated and programmed Digital Equipment Corporation PDP-8, PDP-11 (/45 and /70) and VAX minicomputers. I was involved with the first wave of Unix-based microcomputers, in the early '80s. I have been working in software development, operation, installation and support since then.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

3 comments
Log in or register to join the discussion
  • Tech Talk - SightSpeed

    Hi J.A.,

    thank you for this report, I find it helpful and clear. I installed the proram yesterday in order to test it also. Because of a lack of time I could not use it, but I'll do it soon as it sounds promising :-).

    Because I'm French, I decided to install the French version I could find on a Sightspeed web-site. My first impression was as you said the easy way to install, you are guided through every steps, very good. What I found less pleasant was the french translation, some sentences were ok but others were loose, it is clear to me (I mean I strongly guess ;-)) that this translation is undertaken by a non-native speaker. You should probably find a native one who could improve a little!

    Otherwise, a question about the video resolution. You said J.A. that 640 is possible, but if 1,5MBytes is available... I got something like 1,2MBytes, and I have problem to see where it could not be enough to run a 640x480 conversation! Is it possible to force the 640 to run on the computer even if the requirements of the software do not match? It could be interesting and very attrative!

    Best regards,
    Phil.
    PhilV-29a7e
  • Tech Talk - SightSpeed

    Hello Phil,

    I don't know of any way to force SightSpeed into 640x480 resolution. I agree with you, 1.5 MB bandwidth for 640x480 resolution is a lot, that is why I explicitly mentioned it. I suspect they are using uncompressed video, or some relatively low compression. This is also why I speculated that SightSpeed will improve this area, probably in the near future, but that is really nothing more than speculation on my part, we'll just have to wait and see what happens. If and when they improve it, I will certainly mention it in my blog.

    Thanks for taking the time to read my article and write a comment, and I'm glad that it helped you.

    jw
    j.a.watson@...
  • Tech Talk - SightSpeed

    Hi,

    So on a couple of things I can help fill in the blanks on here- there is a minimum CPU requirement for 640x480 mode because encoding that much data in real time at 30 fps is too much for most (but not all) computers pre- the intel multi-core cpus. There are a bunch of other things happening at higher bandwidths also, such as higher quality audio, better compression, etc. So the CPU load/requirement is very real.

    In order to engage 640x480 mode, both your send and the other party's receive need to be set at 1.5 mbps. In terms of bandwidth, real time, no delay video codecs are pushing it to the edge to do this much data at true 30 fps in 1.5 mbps. SightSpeed is always working to bring this number lower, but how low it goes will always vary based on the content being sent over the wire (i.e. tv content, moving/panning camera vs. stationary camera in a dark room). SightSpeed tries to function optimally across a wide range of content types, and some content will take up more bandwidth than other types.

    Hope that clarifies some things. As you know, much of this is at the sightspeed forums: http://www.sightspeedforums.com/

    Best,
    Tom
    berkeleyfoo-c5e86