Who is actually running s2 and how are you doing it, IE through tsreader or another program?
My pansat 9200 is crap, the s2 card is flakey and bearly works, I have the tt 3200 budget s2 card in my HTPC.
Now with that said I will be useing the 103.0 W location and the NBC hd feeds to test. I have no problems getting the 4:2:2 sd transponders. When it comes to the s2 transponder, thats where I have issues.
I'm late reading this thread (due to superbowl overload), but I noticed that there are no TSREADER responses.
I use the 3200 with TSREADER. I loaded the WDM drivers and TSREADER works OK with it. I generally stream the output to my ROKU for 4.2.0 MPEG2, or play on the computer with VLC (for SD 4.2.2. MPEG4 stuff is still a bit flakey with most versions of VLC.
The 3200 card does a few strange things with VLC though, and I'm not sure if it's because of the card itself or because of the WDM driver, ie might be different for those using the BDA drivers.
First of all, TSREADER seems to often lose indication of lock at times, even though it is still actually locked and processing signal. Doesn't really affect anything, it's just weird to look down and see zero for S/N (ie unlocked), even though data is still going.
Secondly, if I change satellites (card is slaved on C-band) or polarity, and lose signal, and want to tune in a new transponder, OR if I try to tune in a non-existing DVB-S2 transponder, the card takes a LONG TIME before it gives up trying to lock, like something like over a minute sometimes. I think this is because the WDM drivers seem to keep trying with different frequencies, FEC and pilot parameters, looking for a lock, and it doesn't give up until it has tried everything.
Somewhat related to the above, if say I tell it to lock a signal at 4080, and there IS no transponder at 4080, but there is a transponder at say 4060 with similar SR value... when it doesn't find the 4080, it searches around, and eventually locks on the 4060 signal. This can be VERY CONFUSING at times, particularly with a slaved C-band system where I'm setting polarity on another receiver, and it means that you can't trust any signal you've tuned with the 3200 to be close enough to the correct values to lock on any other receiver.
Also related to the search, if I lock on a signal using AUTO FEC, then try to determine the actual FEC, I can't determine the FEC, because it will search through the various FEC values until it locks, and will thus lock regardless of what FEC I have selected.
I have found that the tuner in the 3200 is less sensitive than the tuners in either my Coolsat 8100 or my Diamond 9000, so it won't lock some signals that the other two receivers have no problems with. However 90% of the signals I've tried have worked fine.
Anyway, I like the 3200, but it does have some quirks, at least with the WDM driver.
