New btwincap drivers! :)

[Koepi]

Ahoy,

I just installed the latest drivers (5.2.9) from http://btwincap.sourceforge.net/ and to my surprise, I see a big difference in the quality of my capture!

Is it me who is just dreaming this or can anybody confirm that there is a gain in quality?
(It looks like the field separation works better now resulting in a more crispy picture).

Regards,
Koepi

[Belgabor]

Can't really confirm that, because, and thats why I'm posting, every driver newer than 5.2.5 doesn't really work on my system. .8 and .9 partially work, only some apps (I suspect those accessing the chip directly, e.g. DScaler) lock up my system totally (= not even the mouse curser moves anymore). .6 (and .7? I dun remember exacly) dont work at all (= same lockup on install).

Alas capturing with VDub should work with .9, so I'll gonna check if I can confirm your observation.

Belgabor

P.S: Which TV card do you use? Has it a bt848 or 878?

[Koepi]

I use a relabelled AverMedia TVPhone 98 w/VCR.

Apps like dscaler indeed access the chip directly through own drivers. I didn't encounter lockups using them yet. But I'm on win2k, maybe that makes a difference ;)

Best regards,
Koepi

[Belgabor]

Heh, I'm using Micro$ofts least misarable excuse of a OS, too. So thats not the trouble. Most prolly its either my pretty full PCI bus or Hauppauges 'brilliant' TV card ;)

[VILLA21]

Anyone test it with Haouppauge"s WinTV card and FlyDS 1.2.5, the WDM based capture program i use to ?

[Belgabor]

Nope. I only use VirtualVCR and VDub with the syncro patch. Both work fine, although my TV card kinda garbles the frame order (I dunno whose fault this is, prolly the cards)

Belgabor

[VILLA21]

By the way, i know it"s not the subject, does Vdub work with WDM drivers??...In the official site claims that it works only with VFM...

[jako77]

I have the same problem as Belgabor. I can't test newer versions than 5.2.5 since I use Dscaler to tune the card.

And under XP vdub caps fine using these wdm drivers.

[Belgabor]

@VILLA21
Windows has a vfw wrapper for wdm drivers, its not entierly perfect (preview not really working) but it does the capture stuff fine.

@jako77
I'm kinda glad I'm not the only one suffering from those problems. I'm gonna write a mail to the author of the drivers describing this problem, perhaps he can solve it.
EDIT: Can't you tune your card with the driver?

@koepi
After rereading the news section of the drivers I kinda suspect your improved quality stems either from caputring the stream field instead of frame based or some wierd colorspace converting that was necessary before all formats where enabled with the new drivers.

Regards
Belgabor

[jako77]

I have tried to tune my card with these drivers to no avail using flyDS.

Now, I only install the part of drivers that does not tune.
When I make a full install launching FlyDs is painful long.

In fact, to use these drivers, I first launch Dscaler to tune, then flyDS to activate the drivers and preview TV (I must cycle TV->AV->TV again to make it work), and then only I can use vdub to capture.

Do you know a simpler method ?

[Belgabor]

New drivers out, which (at least according to the changelog) should fix this issue.

Regards
Belgabor

[jako77]

Unfortunately version 5.2.30 does not fix the problem with my config.

[Belgabor]

Neither does it on mine :(

[Koepi]

Well, I can only say these drivers work way better than the manufacturer's drivers on my system.
On win98, I didn't really succeed with them, but on win2k it's a pleasure to use them.

Mybe it's time to upgrade your OSes?

Btw., I'm using vdub_sync directly without hassles here (ok, I _have_ to activate directX acceleration [both fields] in vdub to make the capture work flawlessly, but that's no real problem IMHO. If I don't do that, I get ugly green "stripes" or false copied lines in the image.).

Regards,
Koepi

[ookzDVD]

@Koepi,

sure... I think it's time to upgrade my Win98Se to WinXp,
too many problems with Win98 recently.... especially the
ogg subtitles ;)

and... last night, my WinTV2000 wouldn't play if I use
the WDM driver, hmmmm... only VFW version work for me
on my Win98SE....grrrr.

thank you.

[jako77]

I am afraid upgrading is not an option for me since I already use WIN XP... which I appreciate much except for capturing.
In addition to the problem I share with Belgabor, I also have some sudden, totally unexpected and random, important frame droppping when I capture on one HD (7200 rpm, ATA 100, Maxtor 80 giga), but not on the other (7200 rpm, ATA 100, IBM 40 giga). I have tried every suggestion posted elsewhere to no avail up to now...

[chemmajik]

Anyone using the btwincapture with a voodootv200, and able to do 640x480 captures? I havent tried them yet, afraid it may mess up what works. I'm wondering if it officially worked good with tuner support.
Its prob no biggy since I don't think I want to reinstall visualreality, when I can use deinterlacer now.

[avih]

regarding voodootv.
1. btwincap supports voodootv out of the box, so i guess it's tested enough and should work pretty good.

2. btwincap has the best uninstaller in the world ;), and it COMPLETELY removes itself, including all it's inf files, registry settings and other stuff, so after you'll uninstall it (if indeed you won't like it), i think you'd stay with a system that's really clean from bt8xx drivers.

imho, worth a try.

cheers
avi.

[Belgabor]

Regarding the DScaler issue, I wrote a mail to the author of the btwincap drivers. He told me its the fault of DScaler as it assumes the card being on, which is as it seems with bt878a based cards not the case.
DScaler 4.0 uses btWincap as source (he told me) and should work.

Regards
Belgabor

P.S.: I dont know how 'official' DScaler 4.0 is, as its not on the homepage. I only found it using google.

P.P.S.: @Koepi: As i (clumsily i admit ;)) tried to say, i'm using w2k, too.

[chemmajik]

Hmm avih I may just have to try it then, since you say it has a good uninstaller. Well I should have known since when you are developing you have to make sure old builds are gone, thats the way it was for me. Might have to test out full frame capture for a test, over odd even. Hopefully my hd isnt to slow...

[Koepi]

Hm, the DScaler CVS has nothing mentioned about this issue and still relies on the old drivers already included in 3.1.2 (which crashes on my system with the new drivers 5.3.0).

Ah, ok, google search. It results in this link (reading through the archive a little - like all users here should usually do for example ;) ):
http://www.adcock8.freeserve.co.uk/DScaler400.zip

I'm trying to compile a more recent dscaler WDM version myself with the current CVS, some changes since that build occured...

Regards,
Koepi

[chemmajik]

Koepi what date is the dscaler4 executable, wonder if that one is dated 3-25? Thats how old the first 4.0 beta test was originally when I first got it. Its worked so good I never bothered went & dug for a newer one. :)

[Belgabor]

@ Koepi: Yeah, thats the one I got. Unfortunately it doesnt work for me. It still tries to use its own driver at start which hangs my pc. DirectShow usage seems to rely on a Filter which isnt included in the zip. (I could check that after renaming DSalers hardware drivers ;))

So entirely a no go for me.

What (kinda) worked was starting the amcap app which is in the utils zip on the btwincap drivers page, then starting DScaler (which didnt work with a error about 'overlay not available'), shutting down dscaler, which kinda broke amcap to the point where i couldnt kill it off anymore (on w2k!), then DScaler worked ;)

Regards
Belgabor

[Koepi]

Well, I didn't unzip that archive yet, dunno what's in there. Renaming those drivers would be the first thing to try for me as well.

I fail to compile the CVS stuff because there is an optimization file staying empty at linking level :( Didn't find a solution yet - and I'm definatly too lazy too install both win2000 and win98 driver development kits (I tried the win98 DDK but that didn't help it so I'm a little lost) to try out if those missing compiles produce this result.

Chemajik,
the executable is dated 30.04.2002.

Regards,
Koepi

[chemmajik]

Thats a month newer version. So your trying to compile Dscaler or btdrivers? I'm assuming Dscaler yeah I remember when I first worked on it, it was a pain to finally get it to compile. I got it to compile with the right combo then couldn't remember what it was, then they redid the whole structure for 4.0. Then I said man I will wait for the API to settle down. You have to be on the CVS because of such major changes daily. I'll probably get involved again, if conexant releases the sdk for the CX23881 chipset. I was going to start a new post about this new chipset, but couldnt decided where to start it.
The first cards are starting to appear with it.
http://www.prolink.com.tw/new_web/products/multimedia/PlayTV%20HD_new.htm
and
http://www.prolink.com.tw/new_web/news/Prolink%20PixelView%20XCapture_0509.htm

[geniv]

What the F**K?!

I have a winTV, WinXP

I installed the drivers and didn't like it since my TVtuner and Radion program no longer works.

now I uninstall it and install my WinTV drivers again I can capture video with VDub or FreeVCR anymore

It keep saying VIDEO DEVICE IN USE then it let me select a capture device and I select "happuage WinTV capture" and then it say it's not detected..

Strange it use to be listed as "WDM ... something"

anyone have this experience.. help :(

[geniv]

opps I mean to say "I CAN'T" capture with Vdub or FreeVCR anymore.

but WinTV2k and Radio program works.
and then Capture program that came with the WinTV works but I hate it and it sucks.

[Koepi]

These generic drivers DON'T have a averm.dll which the software uses to detect the "right" tvcard.

So if you install them, the original software stops working - that's the tradeoff for having the freedom of doing real good captures.

Maybe you should read the FAQ and NEWS and so on (there's a LOT to read) over at btwincap.sourceforge.net - your problem is discussed below the first 5 questions.

[Belgabor]

I found a small workaround for the lockup problem (at least it works on my machine). OPen Garphedit and insert the TV Filter (forgot the exact name, the one with only two output pins), then start DScaler (leaving Graphedit open).
Close Graphedit after exiting DScaler.

Warning: Might fuX0r your capturing afterwards/might work only once till the next restart.

Regards
Belgabor

[tarambuka3500]

Hey, I'm having another problems with the btwincap:

1. I can only capture at RGB24 or YUV2 color spaces, all other (RGB32, IV12, etc) won't work :(
2. Under Windows XP, my DIVX, XVID, MJPEG and other codecs are not visible for VDUB and other problems. I can see only the old and trusty "divx_3.11". I guess it is because they are dshow based, not VFW, but still, WinXP should have a working wrapper (or I'm wrong)?

help me out plz :))

[Koepi]

@Belgabor (& all in fact ;) ):

I wrote ejtagle an email about this issue - and the solution is very easy - but he doesn't want to support it in the drivers :-(

The problem is that the programs assume that the card is "switched on" already. But if the driver gets swapped out into the swap-file, the card goes into a suspend mode. This is causing the crash.

Solution 1:
(Copy'n'Paste from ejtagles eMail-reply)
Well, in fact, ther is a way to "disable" this feature.... But you are
on your own, I won't support that way of installing the driver.
You must delete the line "HKR,,PageOutWhenUnopened,3,01" from the install INF file, and then install the driver... Means the driver won't
be swapped out of memory, so card should remain turned on instead of being turned off while driver is not opened. I haven't tested this myself, but i think it should work....

So we come to solution 2:

Start up regedit via "Start -> Run" in windows.
Search for the key "{4D36E96C-E325-11CE-BFC1-08002BE10318}" (at least the key always gets this name on my machine, didn't verify that on other computers... it's in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet[000|001]\Control\Class . There you have to click through the classes until you find something with "media, gamepads etc. controller" shown in the rioght window.)
Then double-click on that key. On my computer it's 0018 which has the btwincap drivers (something like bt848.dll or similar shows up there).

There is a Key called "PageOutWhenUnopened" - double click it and set the value to 00.

Do the same on the other ControlSet sub-keys.

Reboot your machine.

Regards,
Koepi

[Belgabor]

@Koepi: Thx!!! Real simple solution, I hope it works on my machine :)
(gosh, and that after I tried for several hours to write a proggy doing the graphedit workaround on its own)

Regards
Belgabor

[Koepi]

Eduardo provided me with the necessary information so I can try to code a little app which can switch that key on and off.
Might take some though.

Regards,
Koepi

[Belgabor]

Worked like charm and my keys were exactly the same as yours, Koepi.

Cheers
Belgabor

[Koepi]

I coded a small app that is capable of switching the mode of the driver.
I attached it, but you have to wait for the moderator of this forum to accept the attchment *hint* ;)

I hope this helps.

Before I forget to mention, this just wrks for win2k - I can't find the registry settings in win9x. winXP should work fine as well, please report any success/failure please :)

Regards,
Koepi

[Koepi]

EDIT: finally I got some reaction :)

Still, I uploaded the small app to my homepage:

http://roeder.goe.net/~koepi/

Enjoy - and please report success and failure!

Regards,
Koepi

[tiki4]

Maybe just to complete this:

I tested your app in Windows ME this morning, Koepi. Unfortunately it doesn't work. DScaler kills the whole machine in combination with btwincap drivers. :(

tiki4

[Koepi]

Tadaaa!

BtWinCap Drivers v3.5.1 are out.
Multiple cards support, capture region choosable in dshow apps (unfortunately no zoom as bt8x8s don't support that). No fix for the driver being swapped out, so BtWinCapSwitcher is still necessary :-(

tiki4, you may need to send me your registry to search within it, I don't have the time or space (or even a copy of) WinME to test that :-/ Or can you run RegEdit and search for bt878.dll and post me the complete registry key? (something like: \HKLM\blablub\...\{q8935409812349651}\...)

Too bad that Eduardo doesn't even react on my mail or does proomote that tool to get rid of this particular problem (BUT he mentioned the problem itself in the new changelog *grrr*).

Thanks,
Best regards,

Koepi

[tiki4]

@Koep:

yeah, I can search my registry for bt878.dll. I didn't do that yet as I'm too lazy and I'm capturing in Win2K anyway. But you said it doesn't work in any case in Win9x, so why do you think it will in ME? WinMe isn't too much different from 98, so I don't expect miracles here...

I don't have Windows ME here, so I fear you have to wait till tomorrow.

Your app is very useful for me, so thanks for the work.

tiki4

[tiki4]

@Koepi:

I sent you an email yesterday. I attached the part of the registry you wanted to have. So I guess it would be possible to modify BtWinCapSwitcher to work in Windows ME as well. I hope you find the time to have a look at that.

Regards,

tiki4

[Swan]

Has anyone got the btwincap drivers to work with AverTV Studio?
I can't try the little snooping app, I'm on Win2K. If anyone's generated a Custom Card for the Aver TV Studio, I'd be grateful to have a copy.

[Koepi]

Thanks to tiki4 the new BtWinCapSwitcher works with win9x/ME too! Please confirm this, I don't have such an OS to test it on :)

And swan, if you'd _really_ read this thread you'd _know_ that original manufacturers software stops working. Re-read the whole thread please, look around on the btwincap site at sourceforge and find the answer to your question.

Regards,
Koepi

[Swan]

Perhaps I was unclear, Koepi. Still, you shouldn't be so quick to judge me as a person (idiot) who doesn't take the time to lurk before posting.

I am very well aware that the drivers supplied with my AverTV Studio card are not used when installing Btwincap drivers, in fact, they are uninstalled during the installation of Eduardo's drivers. What I was saying is that there is no driver for the AverTV Studio card in the btwdmdrvinstaller.

Even so, I have got video working, by installing another card in the drop-down list of the installer, but not audio. What I meanm by that is that the driver is not 100% right for the card. It does not instruct the card to switch on audio, so the tuner and FM part does not work for me with the btwincap drivers. I can of course get audio by connecting the audio cables from my external source straight into the sound card (bypassing the capture card), but this leaves me without the FM radio and the use of the TV-tuner. I was simply wondering if anyone with Windows 98 had created a a Custom card profile, using the btspy application and if so, were willing to share it with me. I am running Win2K and btspy doesn't run on that OS.

[Koepi]

My AverTV VideoPhone 98 w/ VCR is the same model for the european market as the AverTV Studio. (I thought you mean the software that shipped with the card).

Uninstall and remove the old drivers first with that btinstaller.exe, reboot your system, and try again installing the drivers.

With the old drivers installed, btinstaller doesn't find the card and says "unknown card", after the procedure described above it finds the card you were searching for.

Regards,
Koepi

[Swan]

The AverTV Studio I have (model 203) is not the same as the Aver TVPhone 98. The btiwncap drivers does not work with my card. I will try the latest one, to see if it included in the drop-down box. I know that the AverTV Phone drivers doesn't work for sure because I've tried them.

[LordDethstar]

I finally came around to trying these new drivers because the Official drivers didn't work correctly (no sound). I don't know what the problems that all of you have, but they work perfectly with my TerraTValue (sound and everything). Finally I can really dump Windows 98 SE.

[tiki4]

Confirmed!

BtWinCapSwitcher v2 works in Windows Millennium Edition. I can't test Win98(SE) as I don't like to install these OS's just to test that. As the app works in WinMe I think they should do so in Windows 98 as well.

I tested Dscaler 3.1.0 stable and Dscaler 4.0 alpha. Also MoreTV works without problems if you switch the driver to compatibility mode.

tiki4

[Koepi]

Well, I tested it (and rewrote the registry access many times) on win98 and couldn't get it to work.

So if it works for you it's nice, it doesn't for me ;)

Regards,
Koepi