United Kingdom
New Zealand
One thing that you did miss is full logs. I'm giving you full credit for posting your tv.log, but it is really important to us (as developers and indeed anyone that wants to help) to have *all* the information at our disposal. There is a link in my signature showing how to grab logs - the watchdog makes it easy.It's my first post so apologies if I don't get it right (as in I hope my spec is attached), but in case not: win7 sp1 32bit, Compro S500 Core 2 Duo 4gb ram, MP v1.1.3.0
Wow - that's nice of Compro. I'll make a mental note not to buy their hardware...I have managed to get the compro driver installed and working even though Compro will not be releasing a win7 driver as the manufacturer of the chip they use does not support it anymore - there's a rude response to that attitude!
Okay that is a good start. As long as you're not trying to use the card in two programs at once (which isn't possible) that means this is almost certain to be a settings problem.The card does work perfectly using DVBViewerPro and I can get BBC HD. BBC1 HD and ITV HD, though because they are being fed off a sky minidish the signal does break up occasionally - Most, but not all, channels receive fine with epg and channel names.
Yup, that is to be expected since the drivers haven't been created with Windows 7 in mind.As per the OP I have tried scanning using the latest version of media portal and get no signal. I have to enable DVB-S rather than generic in the scanning option for the card otherwise the system hangs.
The important things are:I have tried scaning a single channel, namely BBC1 (West Midlands) which is on BBC 10.788 V TP46 CLEAR 22000 5/6 according to What satellite. I entered 10788000 (as well as 10788) in the frequency setting and also according to the Kingofsat site the modulation is qpsk, so I tried that as well. I note there is nowhere to set the FEC rate which should be 5/6 (This really needs to be added, I think, to the advanced option screen?) I did look at the xml and this was set correctly there, but the modulation is not in that list - does this matter?
Your instincts are very likely to be correct. As I've already said, I'd expect this is a settings problem.This seems to be an issue that could probably easily be sorted out as a) the Compro works and DVBViewer have solved it and b) it just seems too close to working.
As above. Should be modNotSet. We use QPSK to indicate non backward compatible (NBC) DVB-S2 QPSK in some circumstances, so using modQPSK could mess things up.I've looked at trying to manually set the modulation type to QPSK in the xml, but the server won't read the xml, saying it is not a valid type. Another post Tuner parameters DVBC home Netherlands Limburg/Brabant implies that it should be okay. I assume it doesn't work for DVB-S or it's not important (but the devil is in the details n'est ce pas).
STOP PRESS Apparently you need to use modQPSK, whatever it didn't work - sigh.
This is extreme dedication - diving into the code a couple of days after starting to use MP. I take my hat off to you!Okay, I've managed to get my setup organised (using VS2010) and have compiled the TVSetup system.
Putting a breakpoint at the error message I obtained these values for a variable called tuneChannel.
tuneChannel = {
DVBS:tv:
Freq:10788000
ONID:-1
TSID:-1
SID:-1
PMT:0xFFFFFFFF
FTA:False
LCN:10000
SymbolRate:22000
Modulation:ModQpsk
Polarisation:LinearV
InnerFecRate:RateNotSet
DisEqc:None
band:Universal
Pilot:NotSet
RollOff:NotSet}
Obviously I don't know what some of the fields are or what they should be, but I did notice that the FEC rate wasn't set, so I added a drop down combo box for those and tried again with that set to 5/6, but I still get the error.
{DVBS:tv: Freq:10788000 ONID:-1 TSID:-1 SID:-1 PMT:0xFFFFFFFF FTA:False LCN:10000 SymbolRate:22000 Modulation:ModQpsk Polarisation:LinearV InnerFecRate:Rate5_6 DisEqc:None band:Universal Pilot:NotSet RollOff:NotSet}
After all that I would have had enough too! I'd be happy to help you if you can:had enough for tonight, but if anyone on the dev team would care to provide pointers as to what I could now look for, I'd be grateful
Is anyone looking at this thread? perhaps you could just say Hi.
Tuner drivers are smart enough to figure out what the modulation should be unless it is DVB-S2.