I've always found Compro cards to be pretty good, but then I haven't bought a new one since the two t300s I used to have.
One thing to be aware of is that the Compro drivers have the same issue as the dvico ones, being where sometimes a new driver will change the hardware ID of the card. For MP, which uses the hardware ID's to identify the cards, this is a problem and is why it then becomes necessary to edit the capturecarddefs.xml file to reflect the new ID. this also explains why that works for some people and not others as the alterations posted above may work for you if you have the same driver version, but otherwise you may need to modify this further.
Then again, the card should work well with the TV server since it just uses the windows idnetification of the card to work, so if your card shows up as a stream under cameras, etc, then you should have no problems.
If there are still issues with the TV server, then you'll need to post here and refer to the logs of the TV server to see what went wrong.
One thing to be aware of is that the Compro drivers have the same issue as the dvico ones, being where sometimes a new driver will change the hardware ID of the card. For MP, which uses the hardware ID's to identify the cards, this is a problem and is why it then becomes necessary to edit the capturecarddefs.xml file to reflect the new ID. this also explains why that works for some people and not others as the alterations posted above may work for you if you have the same driver version, but otherwise you may need to modify this further.
Then again, the card should work well with the TV server since it just uses the windows idnetification of the card to work, so if your card shows up as a stream under cameras, etc, then you should have no problems.
If there are still issues with the TV server, then you'll need to post here and refer to the logs of the TV server to see what went wrong.