Stuck with 720x576 res in ati tv wonder 650

[cesm23]

Well it seems that because my card is a hardware mpeg2 encoder the driver ONLY suports a single resolution, 720x576. I have tried many capture programs like virtual dub and all other resolutions give a error complaining about not supported format. Altough i AM able to capture in avi mode (using software encoding of course) so at least without the hardware encoding it SHOULD be possible to unlock the other resolutions, because in the other capture card i have, i use to do several captures at 384x288 using ffdshow with xvid, and OF COURSE at 720x576 it uses all cpu which isn't acceptable...

Maybe there is 3 ways to solve the problem :

- modifying or hacking the tv capture driver to unlock other solutions (highly doubt anyone knows how to do this)

- using some sort of hidden tweak for the capture driver to choose another resolution

- using a kind of direct show filter or codec to resample the video in realtime during capture to another resolution (doing a proper de-interlace when below 288)

Anyone has a idea of what to do ?

[Guest]

Buy better capture hardware.

[*.mp4 guy]

@neuron2 The 650 has one of the best comb filters available, it may be cheep, but the video quality is very good.

@cesm23 you could use vitual vcr to run ffdshow as a directshow filter and downscale the video in realtime before encoding

[cesm23]

Buy better capture hardware.

lool more expensive than this, i would be better buying a tv dvd recorder... this card costs here 80 euros, and it's one of the most expensive ones here were i live, most cards here are only 30-40 euros, those based on the chip saa7134 Philips...

you could use vitual vcr to run ffdshow as a directshow filter and downscale the video in realtime before encoding

Well, virtual vcr doesn't even recognize the internal audio device so i can't use this one... altough the current program i use i also supports directshow filters, and i already tried the "ffdshow raw video filter" (is this the one you meant?), the problem is that unlike when i choose 384x288 (were it always gets perfectly deinterlaced) when i use this filter the capture becomes filled with ghosting... The way i did was to chose that filer, then resize & aspect, then process whole image and specify horizontal and vertical size, is this how you mean ?

I don't know other way of doing it, if it's not like this just tell me how it's done, and if possible tell me if the de-interlace is already done with that or not because the way i tried the video gain ghosting in the movements. (it seems just like bleding was done but i haven't choosed any deinterlace technique or option).

I hope it's possible to resize it without ghosting since i have done thousands of captures in 384x288 with the ffdshow codec and i never had any ghosting or interlace problems...

[cesm23]

Wait a minute i think i got it, in the resize & aspect filter of ffdshow i used the method "point" this was the ONLY one that did not caused ghosting... i even compared with the original video correctly de-interlaced and it was indeed correctly de-interlaced, now is there any disavantage to this method ? I say this because in the description it says this method is the fastest AND THE UGLIEST... even tough i couldn't notice much difference in the picture between this one and the original de-interlaced one... anyone have idea in which area it will be ugliest, and MOST importantly what kind of artifact it could cause? NOTE : i will ONLY use 384x288 to avoid the need to have to re-encode the entire video again to de-interlace it since i do a lot of captures)

[*.mp4 guy]

point is sometimes acceptable for 2x downsizes (what you are doing), but otherswise don't use it, ever. I assumed you would use ffdshow to deinterlace before downsizing, which would solve your problems, as it is using point you are deinterlacing by throwing away half of the fields. A better option would be to use, for instance, the ffmpeg deinterlacer, then use the best downscaler you can (Lanczos3>lanczos2>bicubic>bilinear>fastbilinear) for the speed you need to hit to the highest resolution you can use. That said what you are doing now will most likely only rarely cause aliasing or other trouble that point would usually cause, in this case the limits of analog television are working in your favor.

[Wilbert]

when i choose 384x288 (were it always gets perfectly deinterlaced)
When you cap at 384x288 one of the fields will be thrown away, loosing much information. If that's acceptable to you, i won't complain :)