"I'm a great admirer of MediaPortal, but I often wonder why they make things harder than they should be.
I spent a while researching slow channel changing yesterday & person after person had the issue left unresolved. Finally I found a stray comment about changing the Zap delay setting from the default of 2 to 0. Where is this magical setting? MP Config app (not TV server) > GUI > On Screen Display (I kid you not!) > Zap On-screen Display > Zap Delay (sec)
With that set at the default of 2 seconds, it waits 2 seconds after you press the button to change channels before triggering the change. FFS! What d'head came up with a default option like that? ]And then why wasn't it canvassed as the fix for all these people who have been asking why it's so slow?
also changed the Zap Timeout (sec) from 5 to 2. What that does is reduce the number of seconds the channel/program display remains after the channel has changed from 5 secs to 2. Edit: Actually, the way this appears to work is that it sets the minimum time the OSD will stay on. If you set it at 2 secs & the change takes 3 (as per a client), then the OSD will stay on until the channel has changed. If the change only takes 1 sec (combo client//server), you'll get the OSD for the second before & the second after the change.
The result? On my all in one client/server, my channel changes are now back to about the 1 sec that they were under WMC. The RAM drive is no doubt helping there too. On my clients (which stupidly need to be individually changed too - why isn't it a TV server option?), they've dropped down to about 3 secs (which is down to the overhead of the RTSP stream & the LAN)."
Redigerat av Unregistered05be5f38, 12 februari 2013 - 07:35.