Yeah, terratec have a similar attitude to drivers & their 2400iDT card has exactly the same problem (fine under vista, fine with terratecs own software but gives 'no signal' on all offset muxes in vista media centre).

Hopefully Jess can get some answer from the team with the logs people sent her!

Just thought I'd add (since the problem appears to have been fixed for one of the tuners) that those of us with terratec tuners are still suffering, and have been told by terratec that they acknowledge the problem but it can't be fixed!!

So, let's hope the vista team can come up with something.  Jess, if it helps I can send you logs from my machine, but I see someone else already sent logs from a terratec 2400iDT.  Would it help to have another set of logs from the same card or not?

My compro E700 is with Aria on an RMA for the vista tuning problem - I have sent their tech support the link to Andy's drivers and this thread they tell me they have tried the new drivers but still get the vista no signal problem - I have been offered a refund.

Issue for me is that I have no spare PCI slots - does anyone know of an alternative PCI-e card that actually works with vista mce - I see the terratec card has problems.

or do I decline the refund and wait for official drivers - probably not !!

Shame I didn't keep my Compro E700 long enough to try out these new drivers but saying that, I know someone else who has one and they're still having problems with the new drivers (kudos to Andy though for all the work he's done with the new drivers from Compro).

Apparently, after spending 2 hours and after I told him to disable the driver signing on Vista bootup, he got the drivers installed and Vista MC to display all muxes but some channels are still dodgy with picture break-up etc. As before, all channels work 100% fine on other software, so it's some sort of Vista MC / Compro driver bug. This is on a totally clean install too.

I wouldn't consider this problem fixed until Compro actually releases proper signed 1.041 drivers. They are obviously now aware of the issue, so they need to do some serious testing of these new drivers.

Looks like this thread has gone quite from a MS point of view and the majority of people still have a problem.

an anyone recommend a (cheap) DVB-T card/stick that works with VMC?
may as well buy a new one since the older hardware doesn't work and a fix isn't looking likely

mmace - the Hauppauge Nova-T 500 dual tuner card works pretty well, its a PCI card though and not PCI-E if that's any use to you.

Ha. This thread is anything but quiet on the inside - I got probably 30+ mails from various people in positions to make changes just yesterday, and people here worked over the weekend to try to troubleshoot.

The issue is that when we get reports like this from a place like The Green Button, they're not quantified. Like, maybe the 5 or 10 people on this thread are the ONLY ones experiencing the problem - certainly not a single OEM has reported it to us - so we don't know how to measure that against other issues that come up.

So it would be super-helpful if people sent me private messages and told me exactly what tuner and if you can find out what driver version you're using - and then any additional information about how many channels are found in the scan, how many work, etc. This especially applies to lurkers. :-)

I'm not sure how well-known this is, but in order to get an update (fix) out via Windows Update, we have to go through a TON of process - first convince our management, then the Media Center sustained engineering team, then the Windows sustained engineering team, and so on. The impact has to be very significant to get something out, because with every change we make to a supposed stable, shipped product, we run the risk of regressing something else. All this is a long way to say I have to do quite a bit of homework in order to make something happen that you see, and I'm willing to do it if you're willing to help me.

One thing that helps is knowing exactly what cards you're seeing the problem with; once we know which cards, we can find out internally approximately how many have sold and where, and we can make good guesses as to how many people are potentially affected.

Hi Jess,

Thanks for the update - I have sent you a brief PM giving details of the cards that I encountered the problem with and the drivers used. Hopefully others will step forward and provide enough information to batter the relevant management with.

I wonder Jess if it would be worth somebody from the VMC management team contacting one of the OEM's that has released drivers to fix this issue and asking them exactly what they needed to change with the drivers in order to get the cards working with VMC. Hauppauge may be the best bet here as they were as far as I know one of the first to release drivers that worked.

Remember folks even if you do eventually find drivers that work please provide Jess with the information that she has asked for, it's the only way the problem is going to be resolved once and for all!

PM sent, let's hope something can be done, or at least someone can find the issue and let us know what it is!  I'm really beginning to rue the day I decided to buy a terratec instead of a hauppage card!

Same problems here, PM sent also.

Well, got another reply from Terratec - we are aware of the issue & are working on it, but if it helps we're not expecting it to be fixed anytime soon.

Great.  At least they're honest about it though.

I found this site after doing a Google for "Freecom Vista Offset" following a description of the problem I seem to be having on http://www.bookhouses.co.uk/.

I found  

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.uk.windows.mediacenter&tid=d2cf79f2-32ae-494d-937a-98534c0b73cc&p=1

which linked to this site.

I'm in London UK and have just built a new Vista machine and am trying to get everything working. I have a Freecom DVB-T stick and my transmitter is Crystal Palace. Only a small number of channels work, the same ones that others have reported. My installed driver says it is "Freecom USB Digital TV Receiver" and the version number is 3.0.1.18. The driver was obtained from

http://www.freecom.com/ecsupportdetail.asp?serie=DVB%2DT&group=11361&interface=1147154

The driver details show I'm using

• c:\windows\system32\drivers\BDA_capture_225.sys
• c:\windows\system32\drivers\BdaSupp.sys
• c:\windows\system32\Westlake.dll

Provider is "Wideview Electronics"

The USB stick fully work previously off the same aerial on a Windows 2000 machine, using the drivers and software that came on the CD.

 

 

Just want to let you know that I've received your PMs and the team is investigating. I'll let you know what we find and decide to do.

I think I've got a slighty better feel for what does and doesn't work. According to this document, all Crystal Palace Multiplexes have a -167khz offset, except multiplex C, which has a +167kHz offset. Research so far indicates I can receive everything on the + offset and nothing on any of the others.

 

 

Chris - You are correct regarding the Crystal palace transmitter and the offsets. I suspect the only channels that you can receive include the Sky channels plus UK History etc (I think there are about 6 in total). I'm also receiving my signal via Crystal Palace so I know all too well the problems you are having unfortunately (although my tv card manufacturers have released new butchered drivers to work around this problem).

Hopefully the MCE team will come up trumps and provide a fix for MCE so that workarounds are no longer required within the drivers - hence saving the day and making the world a better place for all us couch potatoes ;)