开发高品质的视频流媒体视频聊天应用 [英] Developing a Video Chat Application with high quality video streaming
问题描述
我工作的，我们正在开发对现有应用程序的视频聊天支持的公司。我已经看过像
I am working for a company where we are developing video chat support on an existing application. I have looked at various solutions for this like
- 使用管理的直接展示为视频拍摄，并在C＃流
- 在code某些项目code样品，我们拍摄图像，并通过它在网络上（我称之为它，而粗的解决方案，因为这会吃掉大量的带宽。
- code从无到有白手起家一个COM pression算法，并用它来COM preSS-DECOM preSS视频。
现在的挑战是，我们正在寻找，以达到非常高品质的视频流和容器应用程序是在C＃.NET
Now the challenge is that we are looking to achieve very high quality video streaming and the container application is coded in C#.NET
这是我迄今提出的。流数据的网络逻辑是用C＃编写，被写在VC ++视频COM pression并称之为VC ++ DLL使用的PInvoke或任CLI哪种方式成为可能。
This is what I have proposed so far. The network logic to stream data is written in C# , the video compression to be written in VC++ and call this VC++ dll using pinvoke or either CLI which way possible.
我要寻找一些多一个经历了我在这个领域谁可以建议我，如果我要多多正确，或者可以这样还是改善。
I am looking for some one more experienced that me in this field who can suggest me if Iam going correct or can this be still improved.
终极目标是高质量的视频流。
在codeC可以像任何h.2633东西，H.264等。
The ultimate goal is high quality video streaming. The codec can be any anything like h.2633, h.264 etc.
推荐答案
我已经用几种方式来获取视频流/与会议.NET容易，而不需要深入DirectShow的。 （好吧，挖了一些，但不深：）
I've used several ways to get video streaming/conferencing with .net easily, without need to dig into directshow. (ok, dig some, but not deep :)
1）使用普通的Windows媒体连接codeR分量。据记载，在Windows媒体连接codeR SDK样本。适合任何高分辨率流，但延迟对实时聊天过大（0.5-2秒最好）。现代防爆preSS恩codeR SDK另一种选择。
1) Use of plain Windows Media Encoder components. It is documented with samples in Windows Media Encoder SDK. Good for any high resolution streaming, but delay is too big for realtime chat (0.5-2 seconds at best). Modern Express Encoder SDK another option.
2）微软研究院ConferenceXP的 http://cct.cs.washington.edu/ 全功能会议API，包括应用程序流。他们过于低级的Windows Media codeD过滤器和包裹他们入管理code。效果很好。轻松定制。看起来有点现在放弃了。
2) Microsoft Research ConferenceXP http://cct.cs.washington.edu/ Full featured conferencing API including application streaming. They too low level Windows Media coded filters and wrapped them into managed code. Works well. Easily customizable. Looks bit abandoned now.
3）微软RTC客户端高达1.3版本 - Windows Messenger的核心
3) Microsoft RTC Client up to version 1.3 - core of windows messenger.
优点：从Microsoft管理样本，良好的文档，性能可靠，包括自由软件，兼容微软（好）SIP协议栈。喜欢的Emblaze VCON主要会议厂商基于他们的IT解决方案，在一些过去不久，不知道这天，但我知道，腾保行货的Microsft的VC-1。
pros: managed samples from Microsoft, good docs, reliable performance, freely redistributable, microsoft compatible (good) SIP stack included. Major conferencing vendors like Emblaze VCON based their solutions on it in some near past, not sure about this days, but I know that Tandberg licensed Microsft's VC-1.
缺点：版本最多也只有1.3支持H261，H263视频。现代版，支持VC-1（H264）$ C $立方厘米不允许直接无服务器IP的IP连接。它确实需要在微软的Live Communications Server。新版本的SDK不包括以及视频会议通话。
cons: version up to 1.3 support h261-h263 video only. modern version with support of VC-1(h264) codec does not allow direct serverless ip-ip connections. It does at require Microsoft Live Communications server. Newer version SDK does not cover well video conferencing calls.
<一个href=\"http://msdn.microsoft.com/en-us/library/ms775892%28VS.85%29.aspx\">http://msdn.microsoft.com/en-us/library/ms775892%28VS.85%29.aspx
请让我们知道你选择什么平台。顺便说一句，我甚至使用，RTC 1.3语音视频ConferenceXP的部分RTP / SIP功能，共同提高视频质量，让你在这里管理技术的广泛的选择。另一件事是Live Meeting的会上我没有机会好好看看呢。
Please let us know what platform you have chosen. By the way, I've even used ConferenceXP video rtp part with RTC 1.3 voice/SIP features together to improve video quality, so you have wide choice of managed technologies here. Another thing is Live Meeting at which I had no chance to take good look yet.
这篇关于开发高品质的视频流媒体视频聊天应用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
