Amcap Free Download For Windows 10

[Camie Fons]

Ive been experimenting with two cameras, one is a webcam and another is an evaluation-kit camera that comes with its own drivers, I can run AMCAP.exe (provided from Vimicro) and it will display live streaming from the connected camera (any of the two) although each one uses a different driver.

My question is: Is it safe to assume that AMCAP.exe is only running as a video-stream display program?In which case, I assume that most camera vendors follow a common standard interface for camera drivers. Could anyone comment on such assumption or explain how AMCAP.exe is able to do that.

I've been able to use both cameras in my c++ based OpenCv applications, but I'm asking because a 3rd company is going to provide me with a usb board-based camera (for evaluation) and they are asking about driver specs. so I suggested that it should work with windows default driver similar to how a webcam would so as to avoid compatibility issues but I'm wondering if there is a better option that I might be missing.

Note I: I've been able to verify that different drivers are being used for each camera by: Start->Devices and Printers->USB 2.0 Camera->Hardware tabe->USB 2.0 camera->Driver->Driver Details. When the webcam is connected, it is using the microsoft provided driver files: ksthunk.sys and usbvideo.sys. When I disconnect the webcam and connect the evaluation camera, I am able to verify that it is using it's own (non-windows) driver.

Camera drivers must implement the OS-defined interface which isn't different for various devices of the same category (in your case it's USB camera). Default drivers for some devices are bundled with Windows and it's ok to use them. However, they aren't necessary optimal for each and every device. E.g., for cameras they might support only a limited set of supported resolutions or might not be optimal with power saving (just an example, not necessary what really happens!). This is because MS implements only the basic and necessary functionality that must be present in every device and doesn't depend on proprietary HW of various vendors. Dedicated camera driver should provide all the additional functionality - you're the one to decide if it's important for you or not.

Just a guess.[annie] could be associated with the amcap.exe application, which is used

for video capture. The vid_093a&pid_2468 belongs to a webcam. -usb.org/usb.ids 093a Pixart Imaging, Inc.

2468 Cammaestro 2.5DU/X-EYE/Orite SC-120/ICGear TravelCam/Easy Snap Snake Eye WebcamSo it is possible you were using amcap.exe, to try to capture video from one of

the named web cams. amcap.exe was a sample application written by Microsoft,

and it is sometimes bundled with webcams or PCI capture cards.I have a copy of amcap.exe on my Hauppauge WinTV Go CDROM, and the file

is pretty small (34304 bytes). The word "annie" can be found, with a hex

editor, inside that application.So amcap.exe may have put that information there. Exactly why that file

was used, I don't know. Paul

Thanks, Paul. I have a webcam, and amcap.exe is on my PC, so now it is clear

that ANNIE is from amcap.exe and some test of video capture.

But is it normal that amcap writes this in WIN.INI ?Thanks, chicchio

I thought the win.ini file went away after Windows NT 3.51 and was

mostly used for 16 bit applications. I haven't seen one in a long

time and don't have any on our XP systems here.Maybe some applications still use it out of habit from writing code

for old Windows versions. It not existing at all does not seem to be

a problem for XP.The free Amcap application used to use win.ini, but apparently someone

there (perhaps Nol Danjou) caught on and started putting their stuff

in their own private .ini called amcap.ini (duh).If it bothers you, make a copy someplace, delete it, reboot and see

who misses it.

The system.ini and win.ini files didn't go away in NT-based versions of

Windows. They are there for compatibility with old applications. Part

of the problem with successive versions of Windows is it retaining

compatibility with old stuff. And I mean really o-l-d stuff. Microsoft

kept win.ini and system.ini for compatibility with old apps that worked

way back in Windows 3.x.When you run msconfig.exe, notice there are still tabs for System.ini

and Win.ini. Sometimes "new" apps are really just old ones that have

merely been adapted to run on later versions of Windows. Sometimes the

developers leave in outdated code (it's not what they were assigned to

work on).

Two comments for you:1. You are using the awful web interface to participate in this

newsgroup--it's the slowest, clunkiest, most error-prone method of

using the newsgroups there is. Do yourself a favor and switch to a

newsreader, such as Outlook Express, which comes with Windows XP, or

Windows Mail, which comes with Vista. See

Your English is just fine. Are you Italian? I know a little of the

Italian language, but your English is much better than my Italian.--

Ken Blake, Microsoft MVP - Windows Desktop Experience

Please Reply to the Newsgroup

Hi Ken, thanks for the advice about OE.

Yes, I am Italian. I know some English because I have 2 cousins in USA, my

aunt came in USA many years ago and her husband was from USA (New Jersey).Thanks again from Enrico (chicchio)

I am working with linux uvc gadget driver with i.mx53 processor(isochronous transfer).I am able to stream data in linux host pc with MJPEG as wel as YUYV using vlc or luvcview application.But wen i connect my usb to windows host pc i can stream only MJPEG data not YUYV data.In windows i am using amcap application in which my i.mx53 board detects as usb video.Please help me out with this or give some suggestion.

I was using usb high bandwidth isochronous transfer ie 1024x3 bytes of data every 125micro seconds.which was working fine in MJPEG and able to achieve 35-40fps.but in YUV i think host not able to recieve such a huge data so i am sending just 1024 bytes every125micro second.now its working well but with 10-15fps.

Yes i tried with vlc in windows.It detects device as video device in vlc.i checked in usb protocol analyser it shows device is sending data continously and host is also recieving but applictaion(vlc or amcap) not able to recieve data.

1. Capture source settings in Studio. Since you may have more than one capture device in your system (e.g. 1394 cards, TV tuners, web cams, etc.) you must be sure to select the correct capture source. In Studio go to Capture > Settings > Capture Source. There is a Video dropdown menu where you can select your video capture device.

If the option for your desired capture device is not listed then go to the Windows Device Manager. If the capture driver for your capture device is flagged or not listed, reload the capture driver as described below.

2. If you are capturing from an analog source, make sure the correct analog type is selected. In the Diskometer window (in Studios Capture mode), click the left tab to open the analog settings flyout. Select Composite or S-Video (whichever is appropriate).

3. If you are capturing from an analog source, check your cabling. The cabling should match the Composite and S-video setting you selected above. If possible, try a different cable, VCR and/or tape to see if the problem is duplicable.

5. If you are capturing from an analog source, you will need to press play before capturing. There is no device control when using analog. If your player is not playing when you press the Capture button, you will get a Capture Error.

If you continue to get a Capture Error after trying the above steps please use the AmCap capture application. AmCap is a generic application used to test device compatibility. If you cant capture with AmCap, then it is likely your capture card doesnt have a proper driver for your version of Windows. A. Click on Start -> Programs -> Studio 8 -> Tools -> Am Capture B. In the AMCAP windows, click on the Devices pulldown menu and select your capture device. C. Then click on the Options pulldown menu and click on Preview and a video should not be seen in the AMCAP window if the video is cabled properly and the source (camcorder, VCR, etc.) is turned on. To capture, click on the Capture pulldown menu and select Start Capture. There may be some selections for setting up your capture card.

3a8082e126