Thanks for the input, but I don't think that's my problem. Just for the heck of it when Vegas acts up I test my firewire using Microsoft's cheesy built-in video editor that's part of Windows XP and it doesn't have trouble reading from or to the firewire. Windows even duitfully brings up the Windows "seeing" the camera.

Oh well, maybe its time I reinstall Windows. I just hate to do that when only one application is acting up.

I have Vegas seeing the camera and grabbing all right but being unable to render to tape. I'm beginning to think the IEEE 1394 protocol is not stable enough. To test things I have ordered a Pyro card (been using a Pinnacle till now) but it hasn't arrived yet.

Santa blessed me with a camera for Christmas (Sony TRV 950, thank you very much) but I haven't gotten round to test it on the firewire yet.

Tor

I remember reading about a problem in XP, XP linking hardware to the built-in video editor. Unfortunately I can't find the thread in the achives of that german forum. It's all about how XP refuses to share access to the firewire card, once you linked it with this built-in Windows Movie Maker. Could well be you started the trouble yourself by trying that program.
Alex

I don't have xp I use win 2k and I had similar prob. Vegas would not render to my new hard drives it drove me crazy. I uninstalled vegas and installed it again it works now but I have this crackling noise in my rendered avi files. I don't know if this helped. I would try just uninstalling vegas first.
Good luck.

Bill,
Are you getting a "Data Invalid" message?
If you are re-install the device following this procedure:
The error appears to be due to a protection problem in the Windows registry and can occur with a variety of drivers (sound cards and SCSI drivers have been reported). To fix this problem, go to Start, Run... and type "regedit"
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ENUM\PCI

and you will see a number of keys of the form "VEN_xxxx", where xxxx are strings like "1102&DEV_0004&SUBSYS_00011103&REV_04".
Under each of these folders will be another folder with a long numerical name. Open each folder and look for the "DeviceDesc" which matches the hardware you are trying to install. Right Click on the "VEN_xxxx" for that device and select 'Permissions' and then tick "Allow" for "Full Control". Close Regedit and then continue with the installation of your device.

John

Folks,

I'm having a problem which may or may not be related to Spot's post above.

Occassionally, my OHCI 1394 card (Pyro) will all of a sudden be listed with an exclamation point in WinXP as "device will not start" or something similiar. I have to physically remove then reseat the card and reboot for Windows to recognize it. I can't detect a pattern, other than something to do with the sequence of steps including connecting my firewire cable between PC and camera, turning the camera on/off etc.

Once the card is recognized, I have no problems whatsoever capturing and printing to tape.

G

If you'll look closely at the post that started this thread you'll notice that the error that Vegas is claiming is bogus. It says invalid file type. That's not so. Because after messing with either turning the camera off and on several cycles or just shutting down Vegas and restarting it 'prints to tape' just fine, without me changing a thing using the very same file as-is with exactly the same render settings. That rules out human error.

I have no hardware conflicts, I use the firewire card for other things when not using Vegas, that rules out the firewire card as a problem...it works fine and it is 100% IEEE 1394 compliant. Windows does not, has not shown any configuration problems, neither in Device Manager or as any error message and I see no errors in the Registry either, nore does Norton find any.

Vegas is simply doing something now that it hasn't before, namely not bringing up the inital window that asks if or not I want to rename the file or whatever it asks (sorry don't have the camera connected now so I can't be more precise) as the first step prior to printing to tape. Vegas capture mode DOES open the file. The video I want to print to tape DOES display in the Video Capture window. Vegas does everything it should except actually print to tape until fiddled with. This is similar but not exactly the same as Vegas complaining it can't write to my "z" drive when every other application can. Yes it has done it again. Grrrr...

It is Vegas not "seeing" the camera, AFTER Windows has already brought up the new device window asking how you want to proceed. So Windows does see the camera and does initilize it. I always dismiss this window after selecting the option for Windows to do nothing so focues isn't shifted where it should't be. Vegas should take control, it starts to, then complains about something BOGUS. Either it says the file type is invalid (false, it IS valid) or it says it can't write to the drive (Again false Windows itself and every other application CAN and DOES write to the drive) Why lately more and more often Vegas can't proceed or first complains about it not being able to write to a drive that seems perfectly fine and works perfectly fine for every other application that reads or writes to it is the mystery. Combined with Vegas also complaing that the file type is invlaid when it IS valid, suggests something Vegas is doing or not doing is what is causing my problems anyways. :-(

BB - I'm no expert - but . . . have you checked the file management folder to confirm that the folders ARE where you expect them to be AND that the folder/s you want to PTT are what you expect. Now I understand exactly what you mean. I had something similar some time back, okay in VF, but with the DV device connected VF would tell me that it wasn't connected. Just out of shear frustration I checked everything - including Folder Management. The Folder Management had lost its way - paths were left in limbo - paths had been unchecked - and paths had their actual syntax truncated. Strange but true. Sooo .. I recreated the paths and/or created new folders and it worked. I too reported this "backward" approach to the VF Forum as possible being a tad silly. However, I made it work for me. Mayb just maybe for you too?

Best regards

Grazie