[This post is taking part in our Designing Hardware for HD series. Be sure to check it out!]
In my last post, I discussed the different layouts that are required by a video endpoint, focusing mainly on the basics – single video source, single display. This leaves a lot to be desired, both on consumer videophones and on enterprise video phones.
I’d like to address this post what happens when you want to go to the enterprise market with a videophone, where data collaboration is commonplace.
Data Collaboration in Video Conferencing
Let’s assume we have a 720p resolution on all inputs and outputs, just to simplify things. Just keep in the back of your mind that you will probably have to deal with other resolutions – especially when connecting the PC into the device.
This time, we have two additional video inputs which are possible: A PC monitor and PC content coming from the Ethernet off of a remote video terminal. In some cases, there’s the option of having two separate displays as well – especially when designing a room system.

Video feeds to a room system videophone
Usually, the second monitor will be optional – something that the end user can decide to plug into the system or not. This is why some of the layouts discussed below will be for a single monitor while others will have dual monitors in mind.
Oh, and if it’s not clear, all layouts from the previous post are still required.
Presentation Mode
In this case, there are 3 feeds being displayed:
- Self view – the video from my own camera
- Remote view – the video from the remote terminal
- Data view – the PC screen that the remote terminal is sharing with me

Presentation mode
Here, the main focus on the view is the presentation itself – the data view, while the “talking heads” part of it – the remote and self views are placed in smaller windows.
This layout can also be used to show the local PC instead of the remote’s PC, and at times, you might even want to play around with which content is placed in which of the windows.
All-You-Can-Eat

All-You-Can-Eat Layout
I like this layout because it takes all possible feeds and shrinks them down to fit nicely on a single monitor. It allows the user to work on his PC, while seeing a presentation that is shared remotely and the video conference he is attending – all at the same time.
Notice here that there are two options:
- You can place the PC on the whole screen, putting the other windows on top of it (either opaque or a bit transparent)
- You can decide to shrink the PC view as well, losing some of the resolution and the ability to read some of the information
I am not sure what the better choice is, but both are valid options.
There is another important aspect that needs to be taken into consideration here, and that is the fact that the PC runs at higher frame rates with higher color depth (24 bit instead of 16 bit) than the other video feeds. This will require some special support on your side from the hardware.
Dual Monitor Video Conference
Let’s move on to the dual monitor scenarios. The most basic layout to cover here would be the regular video conference – one incoming video stream and one outgoing video stream.

Video conference on dual monitors
There’s nothing to write home about here – each monitor gets a full scale video feed.
You can even replace the self view with the remote data view, for example, if the need arise.
Dual Monitor Presentation Mode
This is the second layout that is necessary for dual monitors. Here, one monitor shows a PIP view of self or remote video, while the other displays either the local PC or the remote PC on the second monitor.

Dual monitors, presentation views
What’s Next?
So I’ve covered most of the layouts necessary on the last two posts. You should make your own analysis of what is necessary for you – especially if you intend to develop a home set-top-box videophone for example.
What is still missing is the issue of scaling – something you should be aware of by now, due to the various layouts I’ve suggested here. I’ll touch this area in my next post.

Trackback this post | Subscribe to the comments via RSS Feed