public override bool Equals(object obj)
{
DriCasCaptureMode captureMode = obj as DriCasCaptureMode;
if (captureMode != null && this == captureMode)
{
return(true);
}
return(false);
}
/// <summary>
/// Upon receipt of the SetChannel action, the DRIT SHALL performin sequence the following actions in less than 1s.
/// 1. Clear all the previous program PID from the PidList (Mux service) state variable.
/// 2. Configure the tuner based on the service information tables received from the Card and either of the
/// NewChannelNumber or the NewSourceId arguments. If both are defined and don’t point to the same
/// physical channel, then NewChannelNumber prevails.
/// 3. Set the ProgramNumber (Mux service) state variable.
/// 4. Reset the ACCI status message (see section 8.3) to 0.
/// 5. Setthe DescramblingStatus (CAS service) state variable to “Unknown”.
/// 6. Set the DescramblingMessage (CAS service) state variable to Null.
/// 7. Send a ca_pmt(Ok_descrambling) APDU to the Card.
/// </summary>
/// <param name="newChannelNumber">This argument sets the VirtualChannelNumber state variable.</param>
/// <param name="newSourceId">This argument sets the SourceId state variable.</param>
/// <param name="newCaptureMode">This argument sets the CaptureMode state variable.</param>
/// <param name="pcrLockStatus">This argument provides the value of A_ARG_TYPE_PCRLock state variable when the action response is created.</param>
public void SetChannel(UInt32?newChannelNumber, UInt32?newSourceId, DriCasCaptureMode newCaptureMode, out bool pcrLockStatus)
{
// Note that the input argument order doesn't match the DRI
// specification. This seems to be due to the hardware vendors choosing
// to support the MS PBDA solution from WMC. The MS implementation sends
// the parameters in the wrong order!
IList <object> outParams = _setChannelAction.InvokeAction(new List <object> {
newChannelNumber, newSourceId, newCaptureMode.ToString()
});
pcrLockStatus = (bool)outParams[0];
}
/// <summary>
/// Upon receipt of the SetChannel action, the DRIT SHALL performin sequence the following actions in less than 1s.
/// 1. Clear all the previous program PID from the PidList (Mux service) state variable.
/// 2. Configure the tuner based on the service information tables received from the Card and either of the
/// NewChannelNumber or the NewSourceId arguments. If both are defined and don’t point to the same
/// physical channel, then NewChannelNumber prevails.
/// 3. Set the ProgramNumber (Mux service) state variable.
/// 4. Reset the ACCI status message (see section 8.3) to 0.
/// 5. Setthe DescramblingStatus (CAS service) state variable to “Unknown”.
/// 6. Set the DescramblingMessage (CAS service) state variable to Null.
/// 7. Send a ca_pmt(Ok_descrambling) APDU to the Card.
/// </summary>
/// <param name="newChannelNumber">This argument sets the VirtualChannelNumber state variable.</param>
/// <param name="newSourceId">This argument sets the SourceId state variable.</param>
/// <param name="newCaptureMode">This argument sets the CaptureMode state variable.</param>
/// <param name="pcrLockStatus">This argument provides the value of A_ARG_TYPE_PCRLock state variable when the action response is created.</param>
public void SetChannel(UInt32? newChannelNumber, UInt32? newSourceId, DriCasCaptureMode newCaptureMode, out bool pcrLockStatus)
{
// Note that the input argument order doesn't match the DRI
// specification. This seems to be due to the hardware vendors choosing
// to support the MS PBDA solution from WMC. The MS implementation sends
// the parameters in the wrong order!
IList<object> outParams = _setChannelAction.InvokeAction(new List<object> { newChannelNumber, newSourceId, newCaptureMode.ToString() });
pcrLockStatus = (bool)outParams[0];
}
