Not just a Newbie,a 1st time Ulead user. Firewire card help
Moderator: Ken Berry
-
cocori1
Not just a Newbie,a 1st time Ulead user. Firewire card help
Hi. I am trying to run Ulead Video Studio and realized with my minidv cassette camcorder, I needed a firewire card with (ports?) and a 1394 cable to go from the ports to the camcorder before I even got started. So I bought those over the internet and hooked them up to an empty slot inside my tower. I plugged the 1394 cable into the camcorder then plugged the other end into the port.
The problem lies there. Nothing will recognize that it's even hooked up. When I try to force a capture or anything, it'll say," Make sure device is connected then retry" or something. The capture button never gets highlighted. After I installed Ulead, I did reboot the computer. Anyone know where I should start? Thanks Corey
The problem lies there. Nothing will recognize that it's even hooked up. When I try to force a capture or anything, it'll say," Make sure device is connected then retry" or something. The capture button never gets highlighted. After I installed Ulead, I did reboot the computer. Anyone know where I should start? Thanks Corey
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
-
jchunter
Coincidentally, yesterday, a friend also experienced capture problems with firewire capture from his Sony DV camcorder. He had just returned from a trip, captured the first 20 minutes, or so, stopped the capture to fast forward thru a "nice" shot of the inside of his camera bag, and when he tried to resume the capture, VS would not recognize his camcorder.
He wiggled the firewire cable and could see that the camcorder would alternately detect his computer and not. So we tried his camcorder using my firwire cable on my computer and everything was fine for capture.
Then we tried his cable on my computer and it was intermittent. Fine, we thought, just get a new cable. So he got one and - damned if it did not work - on either his computer or mine. We looked at the camera end of cable with a magnifying glass and could see that his new cable had the contacts recessed about 1/64 of an inch further in than my cable. It just didn't seem to make (reliable) contact with his camera.
So he went to exchange the cable and found that all the firewire cables in that store had pins that were similarly too short. There seems to be quite a variation in manufacturing specs for the pins...
So, he bought a new firewire board that came with a cable (with longer pins) and installed it. After some difficulty getting the computer to recognize the new hardware, it finally did and he was able to capture another half hour of video.
However, when he tried to capture from his second tape, the same thing happened - no camera recognition.
He just sent me the following email: "No amount of jiggling, shoving would work. I think my camcorder has buggered pins in that 4-pin connector and the new cable just jammed them in far enough where they don't make contact. I feel like poking around in the camera's connector to see if I can pull anything straight. The problem now has to be the camera and up your cable no longer works either."
Bottom line:
(1) It seems that the firewire connectors on the camcorder may not work well with some of the new firewire cables that are being sold,
(2) These connectors may not be able to withstand the repeated insertion, wiggling, etc., that naturally occurs during capturing.
(3) Personally, I'm going to treat my treat my firewire cable with "kidd gloves" when capturing and will try to minimize flexing stress that can happen when moving the camera with the firewire cable plugged in.
He wiggled the firewire cable and could see that the camcorder would alternately detect his computer and not. So we tried his camcorder using my firwire cable on my computer and everything was fine for capture.
Then we tried his cable on my computer and it was intermittent. Fine, we thought, just get a new cable. So he got one and - damned if it did not work - on either his computer or mine. We looked at the camera end of cable with a magnifying glass and could see that his new cable had the contacts recessed about 1/64 of an inch further in than my cable. It just didn't seem to make (reliable) contact with his camera.
So he went to exchange the cable and found that all the firewire cables in that store had pins that were similarly too short. There seems to be quite a variation in manufacturing specs for the pins...
So, he bought a new firewire board that came with a cable (with longer pins) and installed it. After some difficulty getting the computer to recognize the new hardware, it finally did and he was able to capture another half hour of video.
However, when he tried to capture from his second tape, the same thing happened - no camera recognition.
He just sent me the following email: "No amount of jiggling, shoving would work. I think my camcorder has buggered pins in that 4-pin connector and the new cable just jammed them in far enough where they don't make contact. I feel like poking around in the camera's connector to see if I can pull anything straight. The problem now has to be the camera and up your cable no longer works either."
Bottom line:
(1) It seems that the firewire connectors on the camcorder may not work well with some of the new firewire cables that are being sold,
(2) These connectors may not be able to withstand the repeated insertion, wiggling, etc., that naturally occurs during capturing.
(3) Personally, I'm going to treat my treat my firewire cable with "kidd gloves" when capturing and will try to minimize flexing stress that can happen when moving the camera with the firewire cable plugged in.
-
cocori1
Thanks George. I just turned off the computer and waited for a few minutes and turned it back on...nothing.
Thanks John. I unplugged the cables checked them closely and plugged them in again. I think that's o.k.
I forgot to say the first time that I am getting the "ding ding" sound from the computer when I turn my camcorder on, but nothing ever pops up saying,"do you want to run new device" or whatever.
Thanks Ken. Yes I am playing the cassette in the screen on the camcorder but it's not being read by Ulead. If I could get Ulead to read it, I could try and capture it but it isn't.
I don't have a question mark by the "bus host controller.." but I do have a yellow exclamation mark next to 2-"SCSI/RAID host controllers". Does that have anything to do with this?
Thanks John. I unplugged the cables checked them closely and plugged them in again. I think that's o.k.
I forgot to say the first time that I am getting the "ding ding" sound from the computer when I turn my camcorder on, but nothing ever pops up saying,"do you want to run new device" or whatever.
Thanks Ken. Yes I am playing the cassette in the screen on the camcorder but it's not being read by Ulead. If I could get Ulead to read it, I could try and capture it but it isn't.
I don't have a question mark by the "bus host controller.." but I do have a yellow exclamation mark next to 2-"SCSI/RAID host controllers". Does that have anything to do with this?
One thing to try (turn down the volume on your computer before doing this). Instead of turning your camcorder to "Playback" mode, turn it to "Camera" mode (as if you were going to start video recording new footage).
Does your computer recognize the camcorder in the "camera" mode
Note-1 the reason I said turn down the volume on your PC first is because the "feedback" from the mic on the camcorder to your computer starts to get loud and annoying...
Note-2 this does not resolve the "capture" problem, but it will help indicate if the firewire card and cable are working...
Regards,
George
Does your computer recognize the camcorder in the "camera" mode
Note-1 the reason I said turn down the volume on your PC first is because the "feedback" from the mic on the camcorder to your computer starts to get loud and annoying...
Note-2 this does not resolve the "capture" problem, but it will help indicate if the firewire card and cable are working...
Regards,
George
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
I honestly don't know. But the yellow question marks mean that something is wrong with your hard drive set-up. If they are in a RAID array, then it seems a driver or drivers are missing. But I wouldn't have thought that would affect your firewire set-up. Someone with more 'techie' experience than I will need to address this...
I notice, from a quick Google search, that other people have the SCSI/RAID host controller problem when virtual SCSI hosts are installed by third party programs like Alcohol. The solution seems to be simply to uninstall them...
By the way, if you go to My Network Places > View Network Connections, do you have an icon for the firewire connection, and is it shown as being 'Connected'?
I notice, from a quick Google search, that other people have the SCSI/RAID host controller problem when virtual SCSI hosts are installed by third party programs like Alcohol. The solution seems to be simply to uninstall them...
By the way, if you go to My Network Places > View Network Connections, do you have an icon for the firewire connection, and is it shown as being 'Connected'?
Ken Berry
-
cocori1
George, I tried the camera mode. I still hear the "ding ding" but no recognizing screen pops up...
Ken, I did look up the " view connections" and the 1394 cable is connected according to that. So we just gotta get Ulead to recognize it, I guess.?
Also I'm not sure if I used a 3rd party or not.
I did go into device driver and clicked on the yellow exclamation point next to SCSI/RAID and uninstalled it according to microsoft's support and then when I reinstalled it and rebooted the computer, it still had a exclamation point there.?.?
Ken, I did look up the " view connections" and the 1394 cable is connected according to that. So we just gotta get Ulead to recognize it, I guess.?
Also I'm not sure if I used a 3rd party or not.
I did go into device driver and clicked on the yellow exclamation point next to SCSI/RAID and uninstalled it according to microsoft's support and then when I reinstalled it and rebooted the computer, it still had a exclamation point there.?.?
-
cocori1
Also, like I said I am new still. But when I install something, I'm used to installing stuff with the wizard taking me step by step. But with this driver disc it allows you to click on whatever icon you want.
Like just in the driver tab alone, there is; a setup folder, a setup config settings icon, a setup installshield icon, a setup INX file icon, a setup HTML document icon, and a setup.boot icon. I'm used to just going through one setup, reboot the computer, and you're good to go.
My point is, I don't know if I've installed everything or not. And I have 7 other folders in ADDITION to the driver folder...AAAGGGHHH!!
Like just in the driver tab alone, there is; a setup folder, a setup config settings icon, a setup installshield icon, a setup INX file icon, a setup HTML document icon, and a setup.boot icon. I'm used to just going through one setup, reboot the computer, and you're good to go.
My point is, I don't know if I've installed everything or not. And I have 7 other folders in ADDITION to the driver folder...AAAGGGHHH!!
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
-
cocori1
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
-
cocori1
O.k. I restored it to way before I installed the drivers. Turned it off and put the card in and rebooted but...nothing. When I go into Ulead and hit the "capture" tab a pop up says "Either no capture driver is installed in this system or no device is connected."
Is there anything I need to do besides restore it to before I installed them in order to get them off?
And how come it seems like XP isn't installing it's own driver? Can I force it to?
Also, you said to watch putting it in the top slot and the bottom slots cause they might conflict. Did you mean I should try not to put it in either one or just don't put a firewire card in the top AND bottom slots.
Is there anything I need to do besides restore it to before I installed them in order to get them off?
And how come it seems like XP isn't installing it's own driver? Can I force it to?
Also, you said to watch putting it in the top slot and the bottom slots cause they might conflict. Did you mean I should try not to put it in either one or just don't put a firewire card in the top AND bottom slots.
-
sjj1805
- Posts: 14383
- Joined: Wed Jan 26, 2005 7:20 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Equium P200-178
- processor: Intel Pentium Dual-Core Processor T2080
- ram: 2 GB
- Video Card: Intel 945 Express
- sound_card: Intel GMA 950
- Hard_Drive_Capacity: 1160 GB
- Location: Birmingham UK
Another suggestion to add to the one above by MD.
Remove the firewire card and then do the system restore.
Now check to see if you still have that yellow exclamation mark.
This will at least reveal if that exclamation mark has anything to do with the installation of the firewire card.
Last year I had a similar problem with Windows XP identifying hardware incorrectly and it turned out to be my (at the time brand new) hard drive was faulty. If after the above steps you still have the exclamation mark try running the Windows XP chkdsk function.
Please view:
http://phpbb.ulead.com.tw/EN/viewtopic. ... 2127#62127
Remove the firewire card and then do the system restore.
Now check to see if you still have that yellow exclamation mark.
This will at least reveal if that exclamation mark has anything to do with the installation of the firewire card.
Last year I had a similar problem with Windows XP identifying hardware incorrectly and it turned out to be my (at the time brand new) hard drive was faulty. If after the above steps you still have the exclamation mark try running the Windows XP chkdsk function.
Please view:
http://phpbb.ulead.com.tw/EN/viewtopic. ... 2127#62127
