Hola!

Hola!
Sorry for no posts the last week. I was on holiday and certainly did not have video conferencing on my mind. More posts soon.

Adios, Jeff

Content ports

Just a quick note as I got an email asking to clarify Codian content & streaming ports.

Codian 4200 series: The 4200 only has video and audio ports. No content/streaming ports. If you turn on H.239 in a conference, it uses up a video port. If you turn on streaming in a conference, it uses up a video port.

Codian 4500 series: The 4500 has video, audio, and content ports. If you turn on H.239 in a conference, it uses a content port. If you turn on streaming in a conference, it uses up a content port. See the screenshot above from a Codian 4505. You will see it states that a 4505 has 12 content/streaming ports and two are being used. (one for content, one for streaming). Again, it really shows that its not truly a port is a port box and with other mcus on the market, you don't have to have extra ports to do H.239.

What has been very confusing is that Codian documentation has also mentioned video ports being used on the 4500. Luckily our previous post and some emails back and forth with Codian got they have found the mistake and have corrected their own documentation.

Sorry... this blog is Hidden...

Just a quick legal disclaimer to TAA and other competitors... this is supposed to be hidden from you... its not really meant for you. ;-)

I got some emails from one such competitor today and I guess they don't like people poking holes at their products...i guess its not "fair". But...oddly enough I guess its ok if you put out competitive information on your competitor but you make it "hidden". Not sure I get that...if you're going to have a beef, why do it behind someones back?

A nice example... notice the "hidden" in the url... I guess that makes it ok for them to do it:

http://www.codian.com/hidden/Video/4500vsRMX-54.wmv

Static Macroblocks

You certainly dont hear customers bring up the term static macroblocks when you go visit them.

But...you certainly hear about its effects when you visit customers. If that customer is testing TAA & PLCM together, we constantly get comments about the video quality. Typically we'll hear TAA to TAA looks good, PLCM to PLCM looks great, but TAA to PLCM looks terrible.

So, why is that? Well, currently TAA "HD" systems can't do full out HD. They don't have the hardware. It takes 108,000 macroblocks per second to do 30 fps 720HD. All of the current TAA systems are incapable of this amount of processing and therefore only do roughly 30+K. So, at HD resolutions, it means they can only update 30% of the screen at any given second. So, either they need to do less resolution or less frames per seconds. Or... use a controversial feature called static macroblocks. You could roughly say that they freeze parts of the screen that have no movement and thus dont send updates for them. Clever... but unfortunately to work the other endpoint has to support it. You can read here:

http://www.polycom.com/common/documents/whitepapers/hd_video_conferencing_three_leading_contenders_face_off.pdf
http://www.codian.com/support/viewfaqentry.php?id=117&topic=&product=MCU%204200

Unfortunatley TAA doesnt point this out and why would they? it would highlight that their endpoint lineup is completely underpowered.

So, why don't other endpoint companies do it? Well... first off, static macroblocks looks terrible unless everyone is motionless. Sure...that happens in some applications, but not many. And second, if your endpoint has enough horsepower to do real HD 720p at 30fps, why hurt your cusotmers by giving them poor video quality?

I think a common misconception TAA sales people leave cusotmers with is that PLCM is not standards compliant because we don't support Static Macroblocks. Its just not needed. And... its such a short term problem...as its fully expected that TAA will yet again replace their lineup of video endpoints and they'll finally have enough horsepower.

Funny email...

This post has absolutely nothing to do with VTC... but it is pretty funny...

I'm a long time Amazon.com customer...and if you are too, you know that they have an advanced engine for making recommendations for purchases based on your past purchases. The email (attached) goes like this:

"We've noticed that customers who have expressed interest in Configuring Cisco Voice over Ip by Elliot Lewis have also ordered Gerontology Nursing Handbook by Patricia A. Tabloski. For this reason, you might like to know that Patricia A. Tabloski's Gerontology Nursing Handbook is now available. "

Not sure how you can go from Voip to care for the elderly...but there you go... LOL!

Standards based? WTF???

So, the latest trend I'm seeing out in the field is customers, who had visited with a TAA sales team prior, are starting off the conversation with us wanting to know why we're not standards based???

Ok, cmon TAA, this is just ridiculous. Again, its just time wasted having to educate the customer and correct the FUD your throwing at them... we could be spending the time better by working through and helping the customer.

So, lets start to doucment all the funny stories I hear customers tell me in reference to standards compatability.

So first off... everyone... all products are based on standards. There are standards like MPEG1, 802.11, ITU G.722.1c, etc, etc

And there are standards based implementations.... for instance a standards based implemented video endpoint runs H.323, H.264, and G.722.1c.

So... just picking a standard like MPEG1 and putting it into your VTC system doesn't make it standards compliant...in fact, even though MPEG1 is a standard, it is not standardly implemented in VTC systems and can actually create problems if you put it in there.

Which leads me to fallacy #1 that I've heard lately from a customer that talked to TAA.

H.264 RCDO is not a VTC standard. If it was, you'd see PLCM, Sony, Lifesize, etc, etc implement it.

Codian Ports

Ok, I got contacted by someone at Codian today asking me to stop spreading the news about Content port usage in their boxes. Of course...if I'm incorrect, I'm happy to be corrected and will retract any incorrect information I'm posting up here. If you've been reading my blog..I am pretty disappointed about the continuous FUD that our competitors spread out there... so I certainly do not want to be a hippocrate.

But.. if they want me to retract the things I've pointed out, they should really prove the information is false. Here's the exact screenprint from the online help of the Codian 4500. Here it is black n' white. (click on the picture to see it fullsize so you can read it)