ATI + WinTV2000 = FAIL

[ratdude747]

I have a Shuttle ST61G4 and I mace the mistake of trying to use xp with it...

The thing has both an ATI chipset and an ATI GPU:

specs:

Pentium 4 HT 2.8ghz
ATI Radeon RS300 Chipset
ATI Radeon x1300 GPU

and I installed a hauppauge wintv-go card in it. it has a brooktree 878 chip in it

I installed all the drivers and updated directx.. but whenever I start WinTv200 (the tv viewer/recorder), the audio from the tuner starts and immediately after, the system locks up.

I had no trouble using the card under ubuntu 11.10 using TvTime and some ALSA settings... unfortunately there is no way to RECORD from the card under linux w/o mythtv (which I have never been able to make work), hence why I am trying to make windows work.

any suggestions or am i looking at getting a different tuner card?

[mockingbird]

Re: ATI + WinTV2000 = FAIL

VirtualDub is what you need.

Record to lossless like huffyuv, and then encode into whatever you want (And apply whichever filters, deinterlace, brightness adjustments, etc...). Make sure you are not getting any dropped frames when recording. Might want to disable system restore or things like that that use the HDD.

[ratdude747]

Re: ATI + WinTV2000 = FAIL

VirtualDub is what you need.

Record to lossless like huffyuv, and then encode into whatever you want (And apply whichever filters, deinterlace, brightness adjustments, etc...). Make sure you are not getting any dropped frames when recording. Might want to disable system restore or things like that that use the HDD.

tried it once, didn't like it.

if this were my dazzle, then it would be one thing. this is a tuner... last i tried, virtualdub didn't have port selection/ channel tuning support. granted, it is an old analog tuner, but by default it goes to the tuner and not the composite input... which for my setup is a bit useless ( I plan to do all my stuff via the composite input).

[mockingbird]

Re: ATI + WinTV2000 = FAIL

My suggestion is to first capture the video with VirtualDub, and then use whatever you want to do the post-processing. WinTV-GO is probably the one of the best-supported cards in VirtualDub, so there must be a way to select the desired input. This is what everybody uses.

Heck, people are even using VirtualDub today for low-cost 1080i capture, but that's a different story.

[toastygoodness]

Re: ATI + WinTV2000 = FAIL

you will either need to use virtualdub or vlc, you probably don't have a choice unless you switch operating systems (a box like that should have badass mythtv support right?)

[ratdude747]

Re: ATI + WinTV2000 = FAIL

you will either need to use virtualdub or vlc, you probably don't have a choice unless you switch operating systems (a box like that should have badass mythtv support right?)

well, If I could figure out mythtv, that is. I never have been able to... I have never gotten past getting mysql to play nice...

the stock hauppage program has never given me issues until now; the recording quality seemed ok. I was kinda looking for advice to get it working, but obviously that's not what the answers have been.

I may retry virtualdub, as at the time I was trying to use it with a webcam and I wasn't paying attention to any tuning settings or the like...

unrelated- were there ever any QAM tuners for PCI or are they only found as PCI-E tuners?

[ratdude747]

Re: ATI + WinTV2000 = FAIL

its not a viewer issue. when I tried to access the card with virtualdub the same thing happened.

the drivers are up to date...

must be an issue with the ATI chipset... I used to use the card+wintv2000 on a HP mini-tower with nearly identical specs (identical CPU, same ram, nvidia GPU, Intel chipset).

so, what cards do play well? suggestions? (I may also look to upgrade the tuner in my main rig as well, which uses a PCI-e tuner).

[ratdude747]

Re: ATI + WinTV2000 = FAIL

tried an open source driver, no improvement.

maybe an IRQ issue?

[ratdude747]

Re: ATI + WinTV2000 = FAIL



fixed it

http://www.hauppauge.com/site/suppor...8.html#lockups

it was in the FAQ... and their advice worked (I went back to the OEM driver too).

I feel a bit dumb...