|
Size: 961
Comment:
|
Size: 947
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Brain stor page for Video Jack. | Video Jack. |
| Line 3: | Line 3: |
| kysucix: | |
| Line 11: | Line 11: |
| Line 12: | Line 13: |
| Line 15: | Line 17: |
| Line 17: | Line 20: |
| Line 18: | Line 22: |
| Line 20: | Line 25: |
| Line 21: | Line 27: |
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]? why rtcp?
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/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