From: Michel C. <mc...@ma...> - 2003-10-06 20:28:03
|
With all the information that we get in previous emails, it seems that it will be a lot of work to write an xine input plugin to support standard rtsp, especially for someone like me that is not familiar with all the architecture of xine and rtsp. Is it possible to create a group of programmers, from xine, live.com and me that can work together on this ? Now we know : 1.We can get a test server from live.com 2.We can keep the actual code in xine rtsp input plugin to keep the ability to play streams from old Real server. 3.xine does assume one single input. 4. Will it be possible for the input plugin to serialize the two streams to feed one demuxer ? Yes, you could do this - but you would need to define your own, new format for representing multiplexed RTP data, and make the rest of xine understand this format. (E.g., you couldn't use an existing multiplexed data format like MPEG Program Streams, because RTP data isn't necessarily MPEG.) 5. live.com is in c++ and xine in c . Complaints about C++ might have been credible 15 years ago, but not in 2003. Pretty much every platform on which you could imagine porting Xine will have C++ compiler support as well as C. (With MPlayer, the only real portability issue that has arisen has been that you need to use the same version of GCC to build both the LIVE.COM libraries and the rest of MPlayer.) 6.Rtp can contain different formats for audio and video. RTP sessions can contain audio and video streams that use completely unrelated codecs (and also other types of stream, such as time-synchronized text (e.g., subtitles)). The audio and video RTP streams could even - in principle - come from different sources. So do WE WORK ALL TOGETHER on this project ? Michel Cunha |