|
Problem with video Capture
|
|
Senior Member
|
8. March 2005 @ 11:47 |
Link to this message
|
|
This message has been edited since posting. Last time this message was edited on 8. March 2005 @ 11:47
|
|
Advertisement
|
|
|
|
|
jagger123
Newbie
|
8. March 2005 @ 14:20 |
Link to this message
|
|
TPFKAS
Yes I am learning a lot too - Many thanks.
Also found out that although video capture was working fine with DVIO, when I played back I lost audio. I got an error with Windows Media Player of pins not connected. After some research i found out that if i disabled my extended desktop on the second monitor all worked OK on a recapture.
Thanks for the redirection - finally seem to have some ski holiday footage I can now work with.
|
|
supertony
Suspended due to non-functional email address
|
8. March 2005 @ 19:36 |
Link to this message
|
|
ack! dvio didn't work. The cap, drop, and size all remain at zero. I'm going to try out Scenalyzer later in the week but It doesn't seem like the problem lies between the software though.
|
|
Leontari
Suspended due to non-functional email address
|
10. March 2005 @ 14:41 |
Link to this message
|
i really hoped that the link [http://support.microsoft.com/kb/885222] for a microsft patch that TPFKAS would be the solution but unfortunately it wasn't. The same problem stills occurs. I read in the above page something about the registry and adding a value, but in my registry there is no HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\1394_hc_hw_id\1394_instance_id\Device Parameters.
It doesn't allow mou to add it either. I only found an Enum/1394/Canon&MV600 path which is my camera's model. I tried deleting, wasn't allowed. Tried to add some information, wasn't allowed. I'm dying here ...
Here's a link for photo with the info my registry about the above path
http://users.forthnet.gr/ath/leontari/registry.jpg
HEEEEEEEELP!
Events occur in real time.
|
Senior Member
|
11. March 2005 @ 07:40 |
Link to this message
|
You can't edit the registry? You have administrative rights on your PC?
These are the very last suggestions that I can do:
1. Check if you don't have any hardware conflicts on your PC.
2. Try to install this driver: http://members.driverguide.com/driver/detail.php?driverid=78245
3. Remove SP2 and see if it works.
4. Completely re-install your computer :-( and try to see if the transfer works before you start installing anything else..
|
|
Leontari
Suspended due to non-functional email address
|
11. March 2005 @ 14:46 |
Link to this message
|
|
Well, I give up!
I used the link mentioned above with a windows 98 driver ... nothing happened.
I uninstalled Service Pack 2, nothing happened.
So I guess, the ultimate solution is to format my PC and install windows xp again. But, that is not going to happen any time soon as I have tons of data to backup and it would be a real hustle to configure again all the programs the way they are now...
So, if someone finds a solution is welcome.
I guess I can give up my dream as a director! :oP
Events occur in real time.
|
Senior Member
|
11. March 2005 @ 14:52 |
Link to this message
|
|
:-(
|
|
jagger123
Newbie
|
13. March 2005 @ 02:44 |
Link to this message
|
|
After trying nearly everything to enable capture with Pinnacle and Amcap, I read about DXDIAG.exe a Windows Direct X diagnostic tool which can be accessed directly from the RUN command - >DXDIAG. Another tool to the armoury.
1. Ran DXDIAG to check out my DirectX drivers and configuration all showed no problems with sound, video etc. However, I thought that despite this I would load the latest Direct X driver version 9.
2. Guess what AMCAP and Pinnacle Plus 9 now capture OK no problem.
|
|
dragulaAC
Senior Member
|
13. March 2005 @ 16:00 |
Link to this message
|
|
I'm having similar troubles with my Adaptec FireConnect 4300 card. I got it to work after reinstalling windows, so i thought that took care of it, however, next day i tried to capture some more and it didn't work again,...so i reinstalled windows and it worked fine,..and next day NOthing.
No idea what is going on here.
~drags |
|
Hexxus
Newbie
|
14. March 2005 @ 07:27 |
Link to this message
|
Ok.....well its been a while since I have been working on this problem. Finally called Microsoft (they found the fix on the there inhouse knowledge base not the public one we see) and here is what should fix this problem. Read this page and follow the steps.... http://www.rme-audio.de/english/techinfo/fw800sp2.htm
Good luck
|
|
jagger123
Newbie
|
14. March 2005 @ 10:44 |
Link to this message
|
|
Hexxus
Be aware that I got flooded with spyware whilst following your link above.
|
Senior Member
|
14. March 2005 @ 11:31 |
Link to this message
|
|
Not sure if I fully understand what is written there. But also refers to the articel in the MS knowledgebase that I mentioned earlier in this thread.
But anyway, I think it is wise to stay away from 1394b for the moment...
You certainly don't need it for video transfer.
|
|
mpegger77
Newbie
|
17. April 2005 @ 13:07 |
Link to this message
|
|
JVC is the problem. I have a GR-D33 that gives me the same problem - 'no capture device detected'. I've tried it with three computers all running XP - one a vergin installation on a new HP. I've tried it with four video capture/edit programs including Sony vegis, MS Moviemaker. I've emailed JVC "Technical "Support"" three times over the last two weeks throough their web site and haven't gotten any response. Seems their Mini DV cameras aren't the only thing unresponsive about JVC. If JVC goes baknrupt form class action law suits, it will be their just deserts.
|
|
Leontari
Suspended due to non-functional email address
|
17. April 2005 @ 16:37 |
Link to this message
|
|
I really hoped that Hexxus with his link had finally given me the solution i need but again, no luck :o(
I did everything exactly as the link instructed but it didn't work for a zillion time!
I'm so depressed ...
Events occur in real time.
|
|
wjauch
Newbie
|
17. April 2005 @ 17:26 |
Link to this message
|
I disagree re the JVC camcorder being the problem. I too have a JVC GR-D33, capture works fine on my laptop using Firewire, Nero or ULead software. Using a Compusa Firewire card in one computer P4 1.6GHZ, capture works in Nero and either Windows Media player or movie maker, I cann't remember which I used. Unfortunately it doesn't work when the same Compusa Firewire card is in an AMD Sempron 2.8GHz system. (All have 512RAM, Win XP, SR2). The JVC is probably not your problem, nor is the Compusa firewire card faulty in my system, I suspect something isn't set up correctly but don't know what.
Werner
|
|
lus2k
Newbie
|
18. April 2005 @ 08:51 |
Link to this message
|
|
The link in Hexssus's post fixed my problem - sort of. I have XP SP2. Video transfer from Sony DCRHC42 gave me black screen about 50% of the time. But I was always able to control device from WinDV or Windows Movie Maker.
What I found is that I needed to flip firewire drivers (1394bus.sys and ohci1394.sys) between SP1 and SP2. In the half dozen times I encoutered the black screen problem (like after power off cam or stopped WinDV), the transfer resumed immediately after I switched the driver. No need to reboot PC. But I did use the sequence: disable firewire->switch driver->enable firewire.
It seems to me XP firewire driver did have a bug and somehow it was bypassed when the driver is modified. Reinstalling same driver did NOT help though.
|
|
scunky
Suspended due to non-functional email address
|
22. April 2005 @ 03:49 |
Link to this message
|
|
Has anyone thought it may be a Directx 9c problem?
I had the same problem with capturing video, blank or greyed
out capture screen and no control over DV cam via firewire.
I rolled back to Directx 8....problem solved!
|
|
dragulaAC
Senior Member
|
22. April 2005 @ 06:02 |
Link to this message
|
|
I had a similar problem for a while, but what i did to get around it was to just uninstall/reinstall my firewire drivers. After doing this, attempting a capture worked fine.
~drags
|
|
scunky
Suspended due to non-functional email address
|
22. April 2005 @ 08:23 |
Link to this message
|
|
Here is another tip I picked up on my travels.
Windows Movie Maker 2 (which is intalled with SP2)
likes to run the show in windows, so can sometimes disable
some drivers in Pinnacle software. the way to get
around this is to disable some or all of the filters
used in Movie Maker 2.
To do this open M.Maker 2
go to tools,options, compatabiliy
and try changing some settings.
Hope this of some help, I know how frustrating this problem
can be
|
|
scunky
Suspended due to non-functional email address
|
22. April 2005 @ 08:26 |
Link to this message
|
|
sorry that should be "compatibility"
|
|
memento56
Newbie
|
15. May 2005 @ 16:15 |
Link to this message
|
|
Hi, you may have solved it, but after months of trying to get 2 Sony and 1 JVC camera to capture properly I finally solved it. Nothing of course to do with cameras, cables, 1394 cards, interrupts etc.
Its all to do with the .inf files created in ,WINDOWS>\inf directory, specifically the msdv.inf file (and the precompiled one created from it, called msdv.pnf). These have to have the profile for your camera, and SP2 often doesn't ... I can't say where to get them, definitively though.
How do I know? Only my JVC would capture properly (flawlessly, no frame drops etc), but neither Sony would. Gritted teeth and applied SP2 after renaming my .inf files (which I had already after applying a number of MS hotfixes). Rebooted, after SP2 install, and still no working Sony's. THEN, renamed the .inf/pnf files (to use the ones I had prior to SP2), to have the correct file extensions and BANG, worked without even a reboot.
So, trust your hardware, don't fiddle in the registry and look for a working /inf .... good luck.
|
|
memento56
Newbie
|
15. May 2005 @ 16:18 |
Link to this message
|
|
Oh forgot to mention, I also use Pinnacle 9.3.4 with a motherboard 1394/Firewire chipset ... and believe that Pinnacle should not be saying they onyl support Pinnacle hardware - they sell Pinnacle as a software only product ... cheers.
|
|
Leontari
Suspended due to non-functional email address
|
15. May 2005 @ 17:20 |
Link to this message
|
|
So, memento56 what does someone have to do EXACTLY according to your solution so capturing will work ? Where to find an .inf that previously worked ? Please, help!
Events occur in real time.
|
|
memento56
Newbie
|
15. May 2005 @ 17:48 |
Link to this message
|
|
Leontari, unfortunately I can't say where I got the working .inf's from, as I had applied a series of MS hotfixes relating to 1394 prior. I am not at home now so can't post/mail it. I'll try to do that tonight. But Google for the msdv.inf and you might find one that works. Or try a "1394 device enumeration" search at Microsoft and apply those that you find (perhaps make a restore point first though as they are mostly irreversible otherwise, but I didn't ...).
I firmly believe its got nothing to do with Pinnacle or any other editing package; this is a low-level thing.
Cheers.
|
|
Advertisement
|
|
|
|
memento56
Newbie
|
16. May 2005 @ 03:20 |
Link to this message
|
|
Am at home now, but have to go out. My JVC is a GR-DVL9800EA (PAL, for Australia, so no DV-IN issues) btw.
I can't (quickly) see how to post the .inf file ... can someone help?
Cheers.
|
