stream_pc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
stream_pc [2012/01/16 17:10] jhb50 |
stream_pc [2012/01/21 21:08] jhb50 |
||
|---|---|---|---|
| Line 34: | Line 34: | ||
| Note that the use of MPEG2 is essential to the success of this process. While h264 may be considered by some to be a better choice, it requires significantly more CPU cycles to encode than MPEG2, and more significantly that load increases in relation to the dynamics of the area being captured, whereas the MPEG2 load is flat regardless of the dynamics. This can lead to the belief that h264 is satisfactory based on the transcoding of a static desktop, however when a video is being played the h264 load soars while the MPEG2 load stays the same. | Note that the use of MPEG2 is essential to the success of this process. While h264 may be considered by some to be a better choice, it requires significantly more CPU cycles to encode than MPEG2, and more significantly that load increases in relation to the dynamics of the area being captured, whereas the MPEG2 load is flat regardless of the dynamics. This can lead to the belief that h264 is satisfactory based on the transcoding of a static desktop, however when a video is being played the h264 load soars while the MPEG2 load stays the same. | ||
| - | Note that your PC must be fast enough to read any incoming stream, render it using a player to the screen, capture the desktop screen, transcode it to an MPEG2 video stream and send it as an output stream, all in real-time, otherwise the TV will sense the real-time delay as the termination of the stream and issue some type of File Format Not Supported message. Reducing your PC screen resolution or the size of the capture window can help reduce the capture and transcoding load. Based on user feedback, even dual core systems can have problems with this. In my case my 8 core I7 uses about 15% cpu but if reduced to 2 cores runs at about 90% cpu. | + | Note that your PC must be fast enough to read any incoming stream, render it using a player to the screen, capture the desktop screen, transcode it to an MPEG2 video stream and send it as an output stream, all in real-time, otherwise the TV will sense the real-time delay as the termination of the stream and issue some type of File Format Not Supported message. Reducing your PC screen resolution or the size of the capture window can help reduce the capture and transcoding load, however the resolution of the streamed picture on the TV will be correspondingly reduced, and only part of the desktop may be streamed. Based on user feedback, even dual core systems can have problems with this. In my case my 8 core I7 uses about 15% cpu but if reduced to 2 cores runs at about 90% cpu. |
| < | < | ||
| Line 42: | Line 42: | ||
| :A corresponding player must be started using HTTP | :A corresponding player must be started using HTTP | ||
| - | " | + | " |
| :Exit | :Exit | ||
| Line 64: | Line 64: | ||
| - Jan 12, 2012 - Edited for more clarity per user feedback. | - Jan 12, 2012 - Edited for more clarity per user feedback. | ||
| - Jan 14, 2012 - Edited to explain why transcoding needs to be to MPEG2 | - Jan 14, 2012 - Edited to explain why transcoding needs to be to MPEG2 | ||
| + | - Jan 21, 2012 - Removed soverlay parameter from command as redundant. | ||
stream_pc.txt ยท Last modified: 2013/01/28 17:29 by rogerdpack
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
