1394 does not see the Sony DV camera

TorS wrote on 9/22/2002, 7:08 AM

This connection has worked before and I’m not sure just what I did to upset it. If anything.
Everything SEEMS OK – no reports of resource conflicts or anything. The computer used to hang when I turned on the camera, but I got rid of that by changing the 1394’s PCI slot. Video Capture says “Microsoft DV camera could not be opened. Please make sure it’s turned on etc...”. Vegas (Options >Preferences >Video Device) sees the right driver but says “Device unavailable”.
Does this sound familiar to any of you? I’m beginning to suspect the camera, but I have no way of checking that end, other than seeing that the camera appears to be OK. It’s a Sony PC100e.

I run Win98SE, Intel Piii, BH6 2, ATI All In Wonder 128. The 1394 is a Pinnacle.
I have Vegas Video 3c and DirectX 8.1 installed.
Please help.

Tor

Comments

seeker wrote on 9/23/2002, 1:44 AM

Tor,

I suppose it could be a loose cable, a bad cable, or a bad connector, but there might be a simple software solution. If you do Start > Programs > Accessories > System Tools > System Information and on the Microsoft System Information dialog select Hardware Resources > IRQs > Advanced Information to get a list of all of your IRQ Device assignments, which IRQs have more than one device assignment, and what specifically are those IRQs and devices?

TorS wrote on 9/23/2002, 2:26 AM

Irq 11 is shared by Highpoint DMA-66 controller and the 1394 card.
Irq 12 is shared by Delta 66 (sound card) and PCI to USB controller.

Like I said, there are no reports of conflicts, so I've been assuming that these items support irq-sharing.

The cable or one of the connections may be bad, but not in such a way that I can provoke a change by wiggling them.

Tor

seeker wrote on 9/23/2002, 3:52 AM

Tor,

"Irq 11 is shared by Highpoint DMA-66 controller and the 1394 card."

Do you have an unused IRQ you could use to reassign either the DMA controller or the 1394 card? I am not certain, but the dual use of IRQ 11 might be a problem.

TorS wrote on 9/23/2002, 4:14 AM

Alas, no. But I will try to force something else to share. Does anyone know that 1394 cards generally will not share irqs?

Tor

TorS wrote on 9/23/2002, 4:55 AM

I took out the 1394 card and moved the LAN card to where the 1394 had been. The LAN card now share irq with the DMA66 controller. I now have one-way LAN! One computer sees the other, the other sees not the one.
When the 1394 was in that slot the computer did not see the DV camera.

I then put the 1394 when the LAN had been. It now has irq 12 to itself. When I turn on the camera the computer halts. Nothing moves, but if I move the mouse and then turn the camera off, the mouse's pointer jumps to the new location.

I'll appreciate if anyone can shed some light on this mystery.

Tor

seeker wrote on 9/23/2002, 5:42 AM

Tor,

Is your Pinnacle 1394 FireWire card OHCI compliant?

-- Burton --

TorS wrote on 9/23/2002, 6:24 AM

It is. On the board is printed:
DV 1394-400 OCHI V1.2

Also the driver is called Texas Instruments OCHI Compliant IEEE 1394 Host Controller.

And - like I said - it HAS worked. Not with Vegas Video 2, but after I upgraded (recently) everything worked beautifully for a couple of weeks. I grabbed video and printed to tape like there was no tomorrow. Then I did other things for a while and when I returned to grab more video it would not work.

If someone will convince me to get another card, yes I will.
But suspicion this far is going in all directions: the camera, the cable, the 1394 card - even the motherboard. I mean why does the LAN suddenly work only one way?

Tor

SonyEPM wrote on 9/23/2002, 8:38 AM

what on your system changed between the time Vegas worked and didn't work? Did you install or update any non-SF DV apps recently?

TorS wrote on 9/23/2002, 10:36 AM

I started to install PresenterOne (the free version) but as the install proceded I realized I didn't have and didn't (for now) want all the extra programs it told me I'd need. I have most of them, but not on this machine - and I don't particularly want internet on it. So at a point I terminated the install. As far as I could understand (and remember) the termination went without unexpected problems or messages.

After that I have re-installed Vegas 3c and installed the latest DirectX (which said 8.1b on the download but reports as 8.1 on dxdiag).

Today I even re-installed the Pinnacle DV software to see if it had a better rapport with the 1394. It didn't.

Tor

Ruud wrote on 9/23/2002, 12:10 PM

Can it be that you should not use the TI driver but the native windows driver.
That is how it works with my sony digital TRV110E.
In the manual it said don't use the drivers that come with the card.

TorS wrote on 9/23/2002, 12:42 PM

>Ruud said: Can it be that you should not use the TI driver but the native windows driver?

I've tried it and could not see any difference. Went back to the TI because that was the one I used when the setup was working.
Thanks for trying.

I even got a new Firewire cable today. Studied the old one with a magnifying glass. Rather silly, because I don't know what it is supposed to look like, but it seemes a bit beat up, so I replaced it. At least I now know the cable is OK.

Tor

bakerja wrote on 9/23/2002, 2:27 PM

Put the firewire card in the very first PCI slot. I had similar problems and when I moved the firewire to the first slot (right beside the AGP) everything magically started working.

TorS wrote on 9/23/2002, 3:49 PM

>JAB said: Put the firewire card in the very first PCI slot.

OK I'll try that tomorrow morning. It's 10.45 PM here now, and my wife has just come home from a long weekend away...

Do you have a BE6-II, too?

Tor

TorS wrote on 9/24/2002, 3:28 AM

>JAB said: Put the firewire card in the very first PCI slot.

I did. It seems OK, but it still says "device unavailable".
Then I suspected the LAN card. Removed it, but same story.
Tried to re-install the LAN card in another slot. Unable to boot. What?
Took it out again and tried the 1394 in each available slot.
Did it properly (uninst driver, turn off PC, remove card, boot, turn off PC, insert card in another slot, boot, install driver).
In slot 2: improvement! Capture sees camera and controls it. Vegas does not, so print to tape from timeline does not work.
(So I hurry and capture some recent footage.)

How can Video Capture see the camera when Vegas does not?

Tor

TorS wrote on 9/24/2002, 6:05 AM

>Capture sees camera and controls it. Vegas does not, so print to tape from timeline does not work.
Well it does, but with no device control.

To sum up:
The 1394 now works with Vegas. It's in slot 3 sharing irq 11 with the highpoint DMA66 controller.

Vegas observes the driver correctly (I'm still using the Texas Instruments version) but says device unavailable. Will print to tape from timeline but will not control camera.

Video Capture works fine, device control and all.

The LAN card is back in, working one way: it sees the other machines but the other machines does not see it.
Re-installing it made no apparent difference to the 1394's behaviour.

I still don't have the foggiest about what's wrong but I am beginning to believe it must be a Vegas or Sonic Foundry thing.
Thanks to all who expressed an interest.

Tor

salad wrote on 9/24/2002, 7:35 AM

Do you have a Printer connected/installed?......just curious....

TorS wrote on 9/24/2002, 7:41 AM

>salad said:
>Do you have a Printer connected/installed?......just curious....

Not on this machine but I can access it via LAN.

Tor

salad wrote on 9/24/2002, 7:49 AM

.....just a shot in the dark.....there's something that I remember about Win98SE...
I have this SB Live card in the 98 machine, comes with that "Emulation thingy"...., but it wouldn't load completely, until I checked something off in system device manager, about sharing a DMA? with the printer. I can't remember, but maybe with the LAN working one way....go into device manager REALLY deep, and check everything for sharing etc.....
just trying to help. this got all my features working on the SB live card.

vx2000b wrote on 9/24/2002, 8:27 AM

Two things to try:
1.
Make sure you have the msdv driver setup with WINNT\INF\ directory.
msdv.inf
msdv.pnf
If these files are located within this directory, you should bo OK.
If not, do the following:

Ok, make sure your DV camera is unplugged.

Go into the control panel, system menu, device manager, and look under
"imaging devices". Delete any DV drivers listed there.

Go into your WinNT\INF directory (you may have to set windows to show
this directory, as it's normally a hidden system directory).

Look for the following files:

customdv.inf
customdv.pnf

If you're not going to use the Avid software, delete them, otherwise,
just rename them by adding ".bak" on the end.

Now look for:

msdv.inf.1
msdv.pnf.1

Just rename them to;

msdv.inf
msdv.pnf

Now reboot your computer and when windows has finished loading, turn
on your DV camera. It should automatically be detected.

2. If this does not work, try reinstalling directx 8.1

TorS wrote on 9/24/2002, 8:36 AM

>salad said:
>but it wouldn't load completely, until I checked something off in system device manager, about sharing a DMA? with the printer.

This is unknown territory for me. DMA was unchecked on my C: drive. I checked it, rebooted and could see no change.
I remember from a sound card list I'm on that DMA or no DMA meant a lot of difference for audio, including Sound Forge opereation. But the details of it I have forgotten.
Can someone else help here, please?

Tor

TorS wrote on 9/24/2002, 8:59 AM

>vx200b said:
>and when windows has finished loading, turn
on your DV camera. It should automatically be detected.

Thanks. I had the msdv files all right. So I did nothing.
But, the camera now shows up in device manager. Don't think I've ever seen that before.
Still, Vegas reports device unavailable. Capture is OK.

I re-installed dx 8.1. No apparent change. "Device unavailable"

Tor

salad wrote on 9/24/2002, 5:13 PM

Sorry Tor,
I was referring to a (shot in the dark) fix for the LAN only working one sided.
I went into Win98, and in the Device manager,under my SB Live / SB 16 Emulation/properties/there is a box I always had to check called "Allow LPT Interrupt Sharing"....nothing DMA. This won't help you here, but I've seen this on other PC's as well.

So, anyway....Still no progress?

nolonemo wrote on 9/24/2002, 6:01 PM

I have a LAN card that wants to be assigned to a specific IRQ (it's either 10 or 11). I ended up hard setting the IRQ for the slot the card is in via the BIOS. One thing you could try, if the LAN is the only problem, is to switch to a USB LAN adaptor. The downside would be that it would be like having a 10MBIT card rather than the 10/100 you probably have now, but if you don't move a lot of data it might solve the problem. Should run you about $30 if you shop around. Sorry to hear about your problems, good luck.

TorS wrote on 9/25/2002, 2:48 AM

salad,
That's OK. I soon eneough discovered that the DMA thing was the wrong medicine (the PC halted when I tried to access that disk).

nolonemo,
Sorry for leading you on but please let's keep LAN matters away from this forum. Thanks anyway.

Status on the 1394 thing is that Vegas sees the camera but will not control it. This means I have to operate the camera manually when I print to tape. Video Capture on the other hand both sees the camera and controls it.
The difference puzzles me, and I rather hope someone - perhaps from Sonic Foundry - can shed light on it.
Other than that, I can live with it. I can get on with what I wanted to do: get to know this fascinating program (Vegas), develop some really brilliant techniques and post them on this forum :-)

Tor