Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 873864" data-attributes="member: 82144">Hi everyone&nbsp;I've been away from this thread for a few months but from the last 10 pages or so it seems like everything is still ticking along okay. Big thanks to you Sasha for your excellent advice!&nbsp;I saw a few comments and questions here and there that I would like to address.&nbsp;First, any &quot;PMT&quot; related errors are indicating that TV Server is not receiving a stream from the HD-PVR/Colossus, which in turn indicates that the inputs are not connected or that TV Server is looking for audio/video from the wrong inputs.&nbsp;Regarding the pin configuration and related pin mapping: that information is actually obtained directly from the crossbar itself (in other words, from the driver). The idea to &quot;hack&quot; the configuration files is very clever - I like it a lot. Those configuration files get written when the device is first detected and used by TV Server. After that I think they're mostly treated as read-only by TV Server, which is why the hack should work.&nbsp;Encoding quality is something that I was written into the code but I was never able to figure out whether it was actually effective. I'm curious to know: is everyone using Showbiz to set resolution and quality settings, and are are the settings in MP TV Server configuration also effective as they should be? Some logs would be useful as I don't have a Colossus or HD-PVR myself.&nbsp;On the topic of video resolution changing on the fly: MP certainly detects certain changes such as audio format (AAC vs. DD/AC3) and will rebuild the client-side graph as required. I'm not sure whether video resolution is one of those triggers. It should be possible to work that out by checking the MediaPortal and TsReader logs. If MP is not doing it then it would be a game of chance finding a video codec that handles such changes automatically.&nbsp;mm</blockquote>

[QUOTE="mm1352000, post: 873864, member: 82144"] Hi everyone I've been away from this thread for a few months but from the last 10 pages or so it seems like everything is still ticking along okay. Big thanks to you Sasha for your excellent advice! I saw a few comments and questions here and there that I would like to address. First, any "PMT" related errors are indicating that TV Server is not receiving a stream from the HD-PVR/Colossus, which in turn indicates that the inputs are not connected or that TV Server is looking for audio/video from the wrong inputs. Regarding the pin configuration and related pin mapping: that information is actually obtained directly from the crossbar itself (in other words, from the driver). The idea to "hack" the configuration files is very clever - I like it a lot. Those configuration files get written when the device is first detected and used by TV Server. After that I think they're mostly treated as read-only by TV Server, which is why the hack should work. Encoding quality is something that I was written into the code but I was never able to figure out whether it was actually effective. I'm curious to know: is everyone using Showbiz to set resolution and quality settings, and are are the settings in MP TV Server configuration also effective as they should be? Some logs would be useful as I don't have a Colossus or HD-PVR myself. On the topic of video resolution changing on the fly: MP certainly detects certain changes such as audio format (AAC vs. DD/AC3) and will rebuild the client-side graph as required. I'm not sure whether video resolution is one of those triggers. It should be possible to work that out by checking the MediaPortal and TsReader logs. If MP is not doing it then it would be a game of chance finding a video codec that handles such changes automatically. mm [/QUOTE]

Verification