Reply to thread

Message

<blockquote data-quote="joboehl" data-source="post: 123896" data-attributes="member: 23490">TvEngine is build around an open protocol. As of today, you could watch it even on a PocketPC device. The protocol for controling the server is the defined by the .Net specification (again, you could use it on the .netcompact framework and control it from CE devices for example). But the beauty of it are the server plug-ins. Let's say that you are working on a platform that doesn't support .Net (like XBox) or you can't change (like Hauppauge MediaVP). One could get what protocols they support and implement a bridge using server plug-ins. Of course, they would have to be able to support the stream, but that's another issue. Transcoding, tough possible, is very limited. And I think your points are not only valid, but shared among a lot of people, including devs. The fact is that they are working on making some of this happening and it will eventually happen. When it's ready. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />I would not expect anybody to start developing for example a XBOX/MediaVP bridge/streamed before the TVServer enters RC code. A lot of things are still going to change under the hoods&nbsp; to achieve the funcionality and performance expected of it.BTW: Look at en.wikipedia.com to learn about the protocol used by tvengine (rtsp) and here <a href="http://store.snapstream.com/hamediamvp.html" target="_blank">http://store.snapstream.com/hamediamvp.html</a> to see the protocols supported by mediamvp. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /></blockquote>

[QUOTE="joboehl, post: 123896, member: 23490"] TvEngine is build around an open protocol. As of today, you could watch it even on a PocketPC device. The protocol for controling the server is the defined by the .Net specification (again, you could use it on the .netcompact framework and control it from CE devices for example). But the beauty of it are the server plug-ins. Let's say that you are working on a platform that doesn't support .Net (like XBox) or you can't change (like Hauppauge MediaVP). One could get what protocols they support and implement a bridge using server plug-ins. Of course, they would have to be able to support the stream, but that's another issue. Transcoding, tough possible, is very limited. And I think your points are not only valid, but shared among a lot of people, including devs. The fact is that they are working on making some of this happening and it will eventually happen. When it's ready. ;) I would not expect anybody to start developing for example a XBOX/MediaVP bridge/streamed before the TVServer enters RC code. A lot of things are still going to change under the hoods to achieve the funcionality and performance expected of it. BTW: Look at en.wikipedia.com to learn about the protocol used by tvengine (rtsp) and here [url]http://store.snapstream.com/hamediamvp.html[/url] to see the protocols supported by mediamvp. ;) [/QUOTE]

Verification