Reply to thread

Message

This doesnt seem to be something as simple as a wrong codec or s slow machine or even hard drive. Ive done some testing to see how much the Revo can handle on its own, this is what Ive found

Test Series 1 Running as a dedicated server
Revo PC with built in DVB-T Tuner and externer Hauppauge DVB-T tuner
Set Server to Record 4 channels (2 per transponder) and view from remote clients 2 more streams (not the ones being recorded)
Using settings in FTR did tests with RTSP enabled and Disabled
Result: Recordings have no problems and live streams have no problems
CPU at 20%

Test Series 2 Running as client
Test same computer as a Client connecting to remote server. Tests Power DVD codec, Built in Windows Codec and FFDShow
Result: Good playback with PDVD Codec
Good playback with FFDShow
Win7 Codec (Cant remember what its called) has some weird flickering so codec is just crappy
With PDVD and FFDshow codecs, CPU Peaked at about 35%

Based on this I figured, well if the server on its own peak at 20% when under a lots of load and the clients peaks at about 35%, that means if I combine both I should be at 55% CPU which should be fine. Also the test from this client connecting to a remote server was performed without uninstalling the local server, just the the server IP was changed in the client config to point to the remote server.

Well the result turned out badly because as soon as I point the client to the local server everything turned to custard and picture became Jerky and sound out of sync with CPU sitting between 80-100% (mostly at 100) also no difirence between HD and non HD Channels.

What has me even more confused is that when we use the built in MCE software of win7, CPU doesn't go over 10% when viewing channels.

It would have been a nice elegant solution to be able to use the Acer Revo as a all in one MePo machine but it looks like we will have to have a separate server if we don't want to drop back to Windows MCE

<blockquote data-quote="dvbkiwi" data-source="post: 736266" data-attributes="member: 99222">This doesnt seem to be something as simple as a wrong codec or s slow machine or even hard drive. Ive done some testing to see how much the Revo can handle on its own, this is what Ive foundTest Series 1 Running as a dedicated serverRevo PC with built in DVB-T Tuner and externer Hauppauge DVB-T tunerSet Server to Record 4 channels (2 per transponder) and view from remote clients 2 more streams (not the ones being recorded)Using settings in FTR did tests with RTSP enabled and DisabledResult: Recordings have no problems and live streams have no problemsCPU at 20%Test Series 2 Running as client Test same computer as a Client connecting to remote server. Tests Power DVD codec, Built in Windows Codec and FFDShowResult: Good playback with PDVD CodecGood playback with FFDShowWin7 Codec (Cant remember what its called) has some weird flickering so codec is just crappyWith PDVD and FFDshow codecs, CPU Peaked at about 35%Based on this I figured, well if the server on its own peak at 20% when under a lots of load and the clients peaks at about 35%, that means if I combine both I should be at 55% CPU which should be fine. Also the test from this client connecting to a remote server was performed without uninstalling the local server, just the the server IP was changed in the client config to point to the remote server.Well the result turned out badly because as soon as I point the client to the local server everything turned to custard and picture became Jerky and sound out of sync with CPU sitting between 80-100% (mostly at 100) also no difirence between HD and non HD Channels.What has me even more confused is that when we use the built in MCE software of win7, CPU doesn't go over 10% when viewing channels.It would have been a nice elegant solution to be able to use the Acer Revo as a all in one MePo machine but it looks like we will have to have a separate server if we don't want to drop back to Windows MCE</blockquote>

[QUOTE="dvbkiwi, post: 736266, member: 99222"] This doesnt seem to be something as simple as a wrong codec or s slow machine or even hard drive. Ive done some testing to see how much the Revo can handle on its own, this is what Ive found Test Series 1 Running as a dedicated server Revo PC with built in DVB-T Tuner and externer Hauppauge DVB-T tuner Set Server to Record 4 channels (2 per transponder) and view from remote clients 2 more streams (not the ones being recorded) Using settings in FTR did tests with RTSP enabled and Disabled Result: Recordings have no problems and live streams have no problems CPU at 20% Test Series 2 Running as client Test same computer as a Client connecting to remote server. Tests Power DVD codec, Built in Windows Codec and FFDShow Result: Good playback with PDVD Codec Good playback with FFDShow Win7 Codec (Cant remember what its called) has some weird flickering so codec is just crappy With PDVD and FFDshow codecs, CPU Peaked at about 35% Based on this I figured, well if the server on its own peak at 20% when under a lots of load and the clients peaks at about 35%, that means if I combine both I should be at 55% CPU which should be fine. Also the test from this client connecting to a remote server was performed without uninstalling the local server, just the the server IP was changed in the client config to point to the remote server. Well the result turned out badly because as soon as I point the client to the local server everything turned to custard and picture became Jerky and sound out of sync with CPU sitting between 80-100% (mostly at 100) also no difirence between HD and non HD Channels. What has me even more confused is that when we use the built in MCE software of win7, CPU doesn't go over 10% when viewing channels. It would have been a nice elegant solution to be able to use the Acer Revo as a all in one MePo machine but it looks like we will have to have a separate server if we don't want to drop back to Windows MCE [/QUOTE]