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/13 22:32] jhb50 |
stream_pc [2012/01/15 01:32] jhb50 |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| <note warning> | <note warning> | ||
| - | Process under development and maybe updated at anytime. Last update | + | Process under development and maybe updated at anytime. Last update |
| This process allows any video playable on your desktop, preferably in fullscreen, to be streamed and displayed on your TV. The only Serviio change is to add the video stream from your PC to the Serviio console as a video livestream at your PC address eg: http: | This process allows any video playable on your desktop, preferably in fullscreen, to be streamed and displayed on your TV. The only Serviio change is to add the video stream from your PC to the Serviio console as a video livestream at your PC address eg: http: | ||
| Line 31: | Line 31: | ||
| You may also experiment with : | You may also experiment with : | ||
| + | |||
| + | 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. 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 63: | Line 65: | ||
| - Jan 8, 2012 - Changed setup sequence. Noted stream must be started before adding link to Serviio. Added VACGD info. Added .bat tuning info. | - Jan 8, 2012 - Changed setup sequence. Noted stream must be started before adding link to Serviio. Added VACGD info. Added .bat tuning info. | ||
| - 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 is to MPEG2 | ||
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
