|
|
|
Problem with video Capture
|
|
|
ironbrow
Newbie
|
21. October 2005 @ 19:12 |
Link to this message
|
This is the fix that finally made Studio 9 begin capturing video and showing video in the preview window while capturing. Before this fix, the program would manipulate the camera (play, stop, rewind, etc) and the counter would show video was being captured, but nothing was actually captured and the preview window had not picture. Now everything works perfectly again.
I discovered this fix because neither Windows Movie Maker and AMcap would capture video either. I would get the error "class not registered" when I would try to capture with Windows Movie Maker. I did a search for that error on Google and found the fix at:
http://www.windowsmoviemakers.net/Forums/ShowPost.aspx?PostID=12304
Windows Movie Maker started working after the fix so I tried Studio 9 again and found that it was working, too.
Here's the simple fix I used:
Try executing the following line on Start -> Run dialog (copy paste and press OK)
regsvr32 %windir%\system32\qdv.dll
You should get a "DllRegisterServer succeeded..." message. Try capturing again afterwards.
|
|
Advertisement
|
  |
|
|
|
bbeljic
Newbie
|
21. October 2005 @ 22:16 |
Link to this message
|
|
Guys I SOLVED THE PROBLEM!!!!
I had same problem. I buyed sony camcorder DC19 and firewire card. Come home, put the card in PCI slot, recorded some video with camcorder, instaled software and when i tryed to capture video I can't. I tryed with USB and everything OK. Firstly O tought my camcorder or firewirecard or cable isn't OK, but when I tryed that components with other PC and also evertyng funcionality. I was very angry becouse I formated my hard disk with windows and linux but I didn't solve problem.
And finaly I found what is the problem. Some firewire card has problem with motherboard or graphic card. In that case you need to download latest driver esspecily for mother board. I hava Asus K8TX mother board and ATI Radeon 9550. Since I updated bios, firewire card started to capturing video. Until updating bios I was abble only to control my camcorder throug commputer.
Bye...
|
|
etruscan
Newbie
|
20. February 2006 @ 16:50 |
Link to this message
|
|
I hooked my newly acquired JVC GR-D90U up to my Windows XP (SP2) machine the other day, through the Firewire port on an Audigy 2 Soundblaster card. The result? No luck. I tried every fix I could find by browsing forums where people were having the same issue... and still no luck.
I knew that my port worked, after using several Nikon DSLR's on it, and I knew the camera and cable worked, after transferring successfully to my Mac. Mac's just seem to have better luck when it comes to IEEE compatibility though.
I remembered something from my days in Nikon tech support. IEEE devices on Windows machines can sometimes be very picky about the chipset of the IEEE 1394 Host Controller. Knowing that my Audigy used a TI chipset, I decided to go out and buy an IEEE 1394 PCI card with an NEC chipset.
Installed it, plugged in the camera - and it now works every time. The solution here is almost assuredly to find a Firewire PCI card with an NEC chipset.
Best of luck!
|
|
supertony
Suspended due to non-functional email address
|
21. February 2006 @ 00:45 |
Link to this message
|
|
damn, anyone have the same problems as me? (from orginal post) I still havent fixed it. I just run to my friend's house and burn the avi's to dvds so I can edit them at home...
|
|
etruscan
Newbie
|
21. February 2006 @ 04:17 |
Link to this message
|
|
I believe your Belkin firewire card uses a TI chipset, so refer to my last post regarding NEC. I personally think you need a new firewire card.
|
|
Magnetoo
Newbie
|
4. March 2006 @ 18:24 |
Link to this message
|
|
Problem: Unable to capture digital video from IEEE 1394.
I am capturing via MovieBox DV but I believe that this fix will extend to other devices. After initially installing the hardware, the Device Manager shows the presence of both the OHCI 1394 hardware and the AVC compliant DV camcorder imaging device. However, when trying to capture via AMCAP, Studio 9, Premere Elements 2.0, or MS Movie Maker, the system appears to hang (hour glass cursor). This condition persists until the 1394 cable is disconnected from the device. All attempts to capture fail. I have tested and verified that this is not a hardware issue, but a 1394 driver issue in XP SP2. I successfully ran capture tests (on a test box) using the above setup at the base XP build (5.1.2600.0). I then upgraded the system to XP SP1A (build 5.1.2600.1106) and also was able to successfully run capture tests. I then upgraded the system to XP SP2 (build 5.1.2600.2180) and experienced the same symptoms that I encountered above on my regular PC. To fix this problem I rolled back the XP SP2 1394 driver set to the XP SP1A driver set on both the test and my regular PC and capture / preview is working normally in all the software mentioned above. Here?s what I did to implement the XP SP1A 1394 drivers on my XP SP2 system:
Go to C:\WINDOWS\Driver Cache\i386. In the SP1 cab extract and copy out the
following files:
1394bus.sys
arp1394.sys
nic1394.sys
ohci1394.sys
Hovering the cursor over the extracted files in explorer should show the XP SP1A build (5.1.2600.1106) in the information box. Copy and replace the XP SP2 versions of these files with the XP SP1A versions in the following TWO directories:
C:\WINDOWS\system32\dllcache (This is the first place XP looks when it detects that a system module has changed. When it detects this, it replaces the changed module with the one found in here.)
C:\WINDOWS\system32\drivers
Reboot the system
|
|
Advertisement
|
|
|
|
Magnetoo
Newbie
|
5. March 2006 @ 09:01 |
Link to this message
|
UPDATED PRIOR POSTING.
Problem: Unable to capture digital video from IEEE 1394.
I am capturing via MovieBox DV but I believe that this fix will extend to other devices. After initially installing the hardware, the Device Manager shows the presence of both the OHCI 1394 hardware and the AVC compliant DV camcorder imaging device. However, when trying to capture via AMCAP, Studio 9, Premere Elements 2.0, or MS Movie Maker, the system appears to hang (hour glass cursor). This condition persists until the 1394 cable is disconnected from the device. All attempts to capture fail. I have tested and verified that this is not a hardware issue, but a 1394 driver issue in XP SP2. I successfully ran capture tests (on a test box) using the above setup at the base XP build (5.1.2600.0). I then upgraded the system to XP SP1A (build 5.1.2600.1106) and also was able to successfully run capture tests. I then upgraded the system to XP SP2 (build 5.1.2600.2180) and experienced the same symptoms that I encountered above on my regular PC. To fix this problem I rolled back the XP SP2 1394 driver set to the XP SP1A driver set on both the test and my regular PC and capture / preview is working normally in all the software mentioned above. Here?s what I did to implement the XP SP1A 1394 drivers on my XP SP2 system:
Go to C:\WINDOWS\Driver Cache\i386. In the SP1 cab extract and copy out the
following files:
1394bus.sys
arp1394.sys
nic1394.sys
ohci1394.sys
To be a little more specific, expand these modules into the C:\WINDOWS\Driver Cache\i386 directory. This is the installation source directory and the second place XP looks when it detects that a system module has changed.
Hovering the cursor over the extracted files in explorer should show the XP SP1A build (5.1.2600.1106) in the information box. Copy and replace the XP SP2 versions of these files with the XP SP1A versions in the following TWO directories:
C:\WINDOWS\system32\dllcache (This is the first place XP looks when it detects that a system module has changed. When it detects this, it replaces the changed module with the one found in here.)
C:\WINDOWS\system32\drivers
Reboot the system
P.S. If you don't see these files / folders(ie. C:\WINDOWS\system32\dllcache), try this:
From Explorer, select TOOLS, FOLDER OPTIONS, and then the VIEW tab.
1. Under "Hidden Files and Folders", select the radio button for "Show Hidden Files and Folders".
2. Uncheck the box for "Hide Extensions for Known File Types".
3. Uncheck the box for "Hide Protected Operating System Files" and reply "YES" to the warning.
4. Click on "Apply to All Folders" at the top of the menu and reply "YES" to the information pop-up.
5. Click "OK" to close the dialog window.
Do you see it now?
For more information on Windows File Protection, you may be interested in this document:
http://www.microsoft.com/whdc/winlogo/drvsign/wfp.mspx
|
|
