Reply to thread

Message

<blockquote data-quote="sjevtic" data-source="post: 857061" data-attributes="member: 118214">I think it would be difficult to have multiple channel lineups managed by the SchedulesDirect plugin, which would be necessary to accommodate multiple different capture device configurations in the fashion intended by TV-Server; I get the impression that the SchedulesDirect plugin really was never intended to be used that way. You might be able to do this with mc2xml/xmltv since mc2xml can grab SchedulesDirect EPG data, but it would undoubtedly be more work, since the SchedulesDirect plugin, when used as intended is a real breeze to get working.&nbsp;Returning to the topic of pin mapping though, let's look more closely at what happens when you use the automatic audio (audioSource = 0) option. Specifically, we're looking at an excerpt from PerformTuning() in TvEngine3\TVLibrary\TVLibrary\Implementations\Analog\Graphs\HDPVR\TVCardHDPVR.cs:&nbsp;[CODE]if (analogChannel.AudioSource == AnalogChannel.AudioInputType.Automatic){&nbsp; &nbsp; if (_videoPinRelatedAudioMap.ContainsKey(analogChannel.VideoSource))&nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; Log.Log.WriteFile(&quot;HDPVR:&nbsp; audio input -&gt; (auto)&quot;);&nbsp; &nbsp; &nbsp; &nbsp; crossBarFilter.Route(_audioOutPinIndex, _videoPinRelatedAudioMap[analogChannel.VideoSource]);&nbsp; &nbsp; }}[/CODE]&nbsp;Clearly, all the option does is set the audio pin to whatever value is in the related attribute. In the case of both the HD-PVR and the Colossus, the component input's related audio source is line in, so that won't produce the result you want out of the box.&nbsp;As an alternative to the approach I suggested earlier, in which you would add an audio mapping to the HD-PVR configuration, you could change the related audio pin for the component video mapping for both your HD-PVR and Colossus cards.&nbsp;For the Colossus cards:&nbsp;[CODE]&nbsp; &nbsp; &lt;videoPin type=&quot;10&quot; index=&quot;1&quot; related=&quot;9&quot; /&gt;[/CODE]&nbsp;For the HD-PVR:&nbsp;[CODE]&nbsp; &nbsp; &lt;videoPin type=&quot;10&quot; index=&quot;0&quot; related=&quot;3&quot; /&gt;[/CoDE]&nbsp;By doing this, when you choose videoSource = 10 (component) and audioSource = 0 (automatic), you will end up using the TOSLink audio input because that's the related audio source for component input. You're achieving the same effect that I described before, but going about it in a slightly different way. To use an old Perl adage, there's more than one way to do it.&nbsp;I'm sure you'll be happy with your new Colossus. I started out with a Colossus, and then tried switching to HD-PVRs because I wanted more tuners and didn't have slots for more Colossus cards (and originally didn't want to deal with a mix of devices, either). It was nothing but a disappointment. One of the HD-PVRs was DOA, and all of them were unreliable, frequently locking up and requiring power cycles and corresponding TV-Server restarts on at least a daily basis. I ended up building a new machine just so I could accommodate enough Colossus cards, and though I'm still working through some issues, the improvement provided by the Colossus cards over the HD-PVRs is nothing short of amazing.&nbsp;Sasha</blockquote>

[QUOTE="sjevtic, post: 857061, member: 118214"] I think it would be difficult to have multiple channel lineups managed by the SchedulesDirect plugin, which would be necessary to accommodate multiple different capture device configurations in the fashion intended by TV-Server; I get the impression that the SchedulesDirect plugin really was never intended to be used that way. You might be able to do this with mc2xml/xmltv since mc2xml can grab SchedulesDirect EPG data, but it would undoubtedly be more work, since the SchedulesDirect plugin, when used as intended is a real breeze to get working. Returning to the topic of pin mapping though, let's look more closely at what happens when you use the automatic audio (audioSource = 0) option. Specifically, we're looking at an excerpt from PerformTuning() in TvEngine3\TVLibrary\TVLibrary\Implementations\Analog\Graphs\HDPVR\TVCardHDPVR.cs: [CODE] if (analogChannel.AudioSource == AnalogChannel.AudioInputType.Automatic) { if (_videoPinRelatedAudioMap.ContainsKey(analogChannel.VideoSource)) { Log.Log.WriteFile("HDPVR: audio input -> (auto)"); crossBarFilter.Route(_audioOutPinIndex, _videoPinRelatedAudioMap[analogChannel.VideoSource]); } } [/CODE] Clearly, all the option does is set the audio pin to whatever value is in the related attribute. In the case of both the HD-PVR and the Colossus, the component input's related audio source is line in, so that won't produce the result you want out of the box. As an alternative to the approach I suggested earlier, in which you would add an audio mapping to the HD-PVR configuration, you could change the related audio pin for the component video mapping for both your HD-PVR and Colossus cards. For the Colossus cards: [CODE] <videoPin type="10" index="1" related="9" /> [/CODE] For the HD-PVR: [CODE] <videoPin type="10" index="0" related="3" /> [/CoDE] By doing this, when you choose videoSource = 10 (component) and audioSource = 0 (automatic), you will end up using the TOSLink audio input because that's the related audio source for component input. You're achieving the same effect that I described before, but going about it in a slightly different way. To use an old Perl adage, there's more than one way to do it. I'm sure you'll be happy with your new Colossus. I started out with a Colossus, and then tried switching to HD-PVRs because I wanted more tuners and didn't have slots for more Colossus cards (and originally didn't want to deal with a mix of devices, either). It was nothing but a disappointment. One of the HD-PVRs was DOA, and all of them were unreliable, frequently locking up and requiring power cycles and corresponding TV-Server restarts on at least a daily basis. I ended up building a new machine just so I could accommodate enough Colossus cards, and though I'm still working through some issues, the improvement provided by the Colossus cards over the HD-PVRs is nothing short of amazing. Sasha [/QUOTE]

Verification