53
edits
mNo edit summary |
mNo edit summary |
||
Line 11: | Line 11: | ||
Frustratingly, some menu items are not identical across platforms. In trying to troubleshoot issues we were having, ooVoo's tech support page referred to necessary menu entries which existed on OS X, but not on Windows. | Frustratingly, some menu items are not identical across platforms. In trying to troubleshoot issues we were having, ooVoo's tech support page referred to necessary menu entries which existed on OS X, but not on Windows. | ||
In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with | In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with two people, the video streams appear as adjacent rectangles. With three people present, the right and left streams are angled in a gratuitous 3D effect. As an alternative, any single stream can be designated to fill the window, with the remaining streams delegated into a single corner. | ||
==Testing ooVoo== | ==Testing ooVoo== | ||
We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. | We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. Audio fidelity during conversation was relatively poor, as has come to be expected from internet telephony. All three of us experienced intermittent feedback bursts, where audio with about a half-second of delay would return loudly for a few seconds at a time. ooVoo's automatic gain control didn't have much of an effect on this. | ||
Weimar occasionally experienced bandwidth issues, which ooVoo deals with by automatically dropping the affected video stream, while keeping audio alive. |
edits