Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Vegas Pro 12, Win 7 and Firewire

  • Vegas Pro 12, Win 7 and Firewire

    Posted by Phil Seymour on December 29, 2012 at 11:47 am

    I’m in trouble. My camera is a Sony EX3, and I have no probs transferring media to my computer for editing, however a friend asked me to edit some footage from his SD DV camera that connects by firewire. I have done this often in the past BUT that was with Windows XP. My current computer has a firewire socket on the motherboard and Win 7 Pro operating system. Vegas capture does not see the DV camera. Googling the web brings up a ton of info about Win 7 IEEE1394 drivers being updated and not compatible with older firewire equipment.. cams, audio mixers, hard drives. Good on ya, Microsoft! Advice is to reload the legacy driver for IEE1394 which I did… but still no DV cam.
    (Big breath) So… has anyone else had this problem and found out what to do?

    Windows 7 Pro64, 16GB RAM, SSD boot drive, GTX 570 Graphics, Vegas Pro 12

    Phil Seymour replied 13 years, 4 months ago 5 Members · 9 Replies
  • 9 Replies
  • Graham Bernard

    December 29, 2012 at 12:29 pm

    [Phil Seymour] “Advice is to reload the legacy driver for IEE1394 which I did… but still no DV cam.”

    Phil, for what Device did you apply the Legacy driver to?

    Cheers

    Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 and two elderly XM2s

  • Roger Bansemer

    December 29, 2012 at 1:41 pm

    I was having the same trouble a few weeks ago and wasn’t able to get Vegas to recognize the DV footage but in my case I found out that it wasn’t Vegas that was the problem but instead the settings inside my camera itself that had to be changed in order for Vegas to recognize the footage.

    Roger Bansemer

  • Steve Rhoden

    December 29, 2012 at 2:34 pm

    As Roger suggested, check the camera settings.

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    https://www.facebook.com/FilmexCreativeMedia
    1-876-832-4956

  • Phil Seymour

    December 29, 2012 at 10:58 pm

    Hi Grazie… I applied it to the buss – the only firewire reference in Device Manager

    Windows 7 Pro64, 16GB RAM, SSD boot drive, GTX 570 Graphics, Vegas Pro 12

  • Phil Seymour

    December 29, 2012 at 11:04 pm

    The camera is just a pipsqueak panasonic DV tape camera circa 2004/5 with a firewire port. I used to sell the things so I am quite familiar with the menu system and settings, so no tricks there.
    It seems Windows isn’t passing info to Vegas.. not sure why. Looks like an afternoon of Google-tripping. All for a favour.
    Phooey! Don’t you just hate technology? It all worked so well with Windows XP. What ever happened to MS Dos 3.2?

    Windows 7 Pro64, 16GB RAM, SSD boot drive, GTX 570 Graphics, Vegas Pro 12

  • Bob Peterson

    December 29, 2012 at 11:14 pm

    I am running Win 7 Pro, and I remember having some problems with firewire. First, I don’t think Windows is primarily responsible for the driver. It should be supplied by the mother board manufacturer. MS may act as a conduit for a driver, but I have not had good luck with that approach. Thus, I installed the drivers from the motherboard software disk.

    Second, I have several devices which communicate via firewire including an external hard drive. The hard drive was very slow under Win 7 until I discovered that the hub I was using had gone bad. Once it was replaced, the problems disappeared.

    I connect my cameras to the external hard drive which is always powered down. That way, I hope I am not connecting or unconnecting the camera to a device which is powered up. That helps insure that the firewire port does not get blown. It also confirms that the system recognizes the attached firewire devices since Windows makes it quite clear when the hard drive is powered up.

  • Phil Seymour

    December 30, 2012 at 3:39 am

    According to an MS techie posting on their forum, MS did re-write the driver, and it was on his suggestion the we (meaning all the other forum-ites) re-installed the legacy driver.
    After doing that, windows still didn’t see the camera in Devices and Printers. I thought that the cable might be faulty, so changed it. No good. Then I remembered that there was a spate of camera firewire port failures about the time the camera came on the market, and so I swapped the camera for my own little dust-gatherer and Voila! … the first cam had a dud firewire port.
    So its all happening now, and thanks to all for taking time to offer suggestions.
    How easy to get trapped when Murphy’s Law strikes.

    Windows 7 Pro64, 16GB RAM, SSD boot drive, GTX 570 Graphics, Vegas Pro 12

  • Graham Bernard

    December 30, 2012 at 3:59 am

    Lol! What have I learnt from this? Don’t be “blinkered” by recent remedies.

    Should have suggested using “another” camera.

    Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 and two elderly XM2s

  • Phil Seymour

    December 30, 2012 at 11:05 am

    Yes… sometimes we are just too smart and overlook the obvious. 🙂

    Windows 7 Pro64, 16GB RAM, SSD boot drive, GTX 570 Graphics, Vegas Pro 12

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy