|
Size: 947
Comment:
|
Size: 992
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 16: | Line 16: |
| why [http://wiki.videolan.org/index.php/RTP rtp]? why rtcp? | why [http://wiki.videolan.org/index.php/RTP rtp]? because it's the Real Time Protocol! |
| Line 18: | Line 19: |
| because it's the Real Time Protocol! [http://wiki.videolan.org/index.php/RTCP rtcp] to have quality information about the stream | why http://wiki.videolan.org/index.php/RTCP rtcp]? [http://wiki.videolan.org/index.php/RTCP rtcp] to have quality information about the stream |
Video Jack.
with the technology and protocols available nowadays video jack would be an rtp server(and even rtsp), maybe with rtcp to sync stream as the jackd transport, using sap to connect to it. the problem would be the format used in order to get rid of bandwidth and cpu problems (rgb? yuv? light huffman compression?)
As for sap server there is [http://wiki.videolan.org/index.php/SAP minisap server] from videolan guys.
for rtp there's live.com or the whole project [http://streaming.polito.it/server fenice]
why [http://wiki.videolan.org/index.php/RTP rtp]? because it's the Real Time Protocol!
why http://wiki.videolan.org/index.php/RTCP rtcp]? [http://wiki.videolan.org/index.php/RTCP rtcp] to have quality information about the stream
Why [http://wiki.videolan.org/index.php/SAP sap]?
because it's the Session Announcement Protocol and can use multicast.
Why [http://www.rtsp.org/ rtcp]?
because it's the Real-Time Streaming Protocol