Bob, the problem you reference is very similar to mine (see thread on canon HV20), although i'm using Windows 7 64bit.  I successfully captured once, popped in the next tape and it would no longer work.  Put the old tape back in that was successful and it too would no longer work.  Nothing I have tried since that time - and I've tried lots of stuff - has had any success.  The only two things I can think of to explain it are;

• Windows update installed something that is causing this to fail.
• Pinnacle (or something else) wrote something to the registry that now is causing this to fail.

If you figure this out I would love to hear how you did it.

BKZ:

Bob, the problem you reference is very similar to mine (see thread on canon HV20), although i'm using Windows 7 64bit.  I successfully captured once, popped in the next tape and it would no longer work.  Put the old tape back in that was successful and it too would no longer work.  Nothing I have tried since that time - and I've tried lots of stuff - has had any success.  The only two things I can think of to explain it are;

• Windows update installed something that is causing this to fail.
• Pinnacle (or something else) wrote something to the registry that now is causing this to fail.

If you figure this out I would love to hear how you did it.

I agree that this issue could be similar in nature. And my gut feeling points to the Firewire chipset drivers.

 

Thanks to you both, well this is what happened.

I disconnected the fire wire to the camera then switched it off, then shut down the computer.

After a few mins I first plugged in the fire wire into the camera, then turned the camera on, then turned the computer on, then started Studio.

As soon as I clicked the capture tab Studio recognised the Sony Z1 straight away and captured no probs – then I captured another tape as well.

I have used Studio since version 8 (do I get some sort of medal ??) and remembered this as a fix from the early days, I don't know how long this “fix” will hold but it's not really too inconvenient to do it again.

 As for a permanent fix it might be easier to turn lead into gold !!!

bob@thefletchers.org.uk:

 

Thanks to you both, well this is what happened.

I disconnected the fire wire to the camera then switched it off, then shut down the computer.

After a few mins I first plugged in the fire wire into the camera, then turned the camera on, then turned the computer on, then started Studio.

As soon as I clicked the capture tab Studio recognised the Sony Z1 straight away and captured no probs – then I captured another tape as well.

I have used Studio since version 8 (do I get some sort of medal ??) and remembered this as a fix from the early days, I don't know how long this “fix” will hold but it's not really too inconvenient to do it again.

 As for a permanent fix it might be easier to turn lead into gold !!!

Thanks for sharing this with us, this makes things a bit more complicated doesn't it. I wish I'd have these cameras within my reach. I ask QA if they could more tests with this kind of setup.

As I said - lead into gold !!!! 

My first bet would be that the programme (which is already of a nervous disposition !) has had a slight hissy fit.

I do like to try different things with Studio's many superb add ons and some of my video's are 3 hrs long at best quality with all sorts of quirks and transitions etc, so there is plenty of strain on the programme and computer, and my (unqualified) opinion is that it needs a good sort out from time to time.

I have had many conversations with Studio support in the past and sadly very few reach a satisfactory conclusion, that said, I think that for the money Studio IS a very good product and has some very good features. Oh ! if only I could remember how to use them all !!!

If anyone can come up with a permanent fix perhaps their next step should be world peace ?

Cheers

Bob

Unfortunately this workaround didn't work for my setup.  Wish I knew where the problem lies; camera, firewire driver, OS, Studio 12...but alas, I'll never know as will have to find another machine to use for import.

Thank you Bob for the tip.

 I just started with my new SONY HDR-HC9 today. And now everything goes fine. It even seems, after a first handshake, as you discribed it, they like to work together - Computer and Camera. BTW mine is a Pentium 4, 2,6GHz.

Sunny cheers from Darmstadt, Germany

Klaus

 

klausdt:

Thank you Bob for the tip.

 I just started with my new SONY HDR-HC9 today. And now everything goes fine. It even seems, after a first handshake, as you discribed it, they like to work together - Computer and Camera. BTW mine is a Pentium 4, 2,6GHz.

Sunny cheers from Darmstadt, Germany

Klaus

 

I'm glad your camera works well now with the software.

Hi Klausdt.  What operating system are you using?  I'm using Vista 64 and that may be the issue.  Or its a compatibitlity problem with my new Dell 435T which many other users are experiencing problems.

Daninvan:

Hi Klausdt.  What operating system are you using?  I'm using Vista 64 and that may be the issue.  Or its a compatibitlity problem with my new Dell 435T which many other users are experiencing problems.

There are make movie issues with this Dell system. But the firewire issue seems to be unspecific with its problem. I don't think your system is the culprit, I'm still investigating this issue some cases leads it to be isolated to firewire drivers and chipset.

See if this works.

Be in Edit and press play on the camera. While the video is "playing" go to Capture tab.

 

klausdt:

Thank you Bob for the tip.

 I just started with my new SONY HDR-HC9 today. And now everything goes fine. It even seems, after a first handshake, as you discribed it, they like to work together - Computer and Camera. BTW mine is a Pentium 4, 2,6GHz.

Sunny cheers from Darmstadt, Germany

Klaus

 

I've heard from another thread that a user has had success with his capture by caputiring with the LCD viewfinder open.

Got it to work!  I took the advice of the user who recommended pressing play while in the EDIT screen, then moving to the capture screen.  I was then able to see the video in the capture window.  However, the only drawback to this is that you might lose 5 to 10 seconds of video up front. If you can click fast enough you might only miss a few seconds.  Its a work around but at least I can capture high def now. 

Marc --

 

I am experiencing the same issue that others are -- Studio 12 recognizes my firewire-attached Sony HC-3 just fine.  I  can operate the camera from the Studio 12 UI (rewind, fastforward, etc) and initiate CAPTURE VIDEO.  BUT ... as the tape 'plays' no video displays in the preview window of Studio, and the frame counts do not advance.  When the tape transfer is complete and I click on EDIT, then I get the error message that [filename].m2v cannot be opened.  Also when checking that file in MS Explorer, it exists as a file name but has 0 (zero) bytes.  In other words, CAPTURE did not really transfer any bytes and write to disc.

 I can use the SAME camera and firewire cable with Studio 12 on a Vista 32 Home Premium system and a Windows 7 RC 64-bit system WITH NO ISSUES.  The problem is not the camera or the cable.

I ONLY have a problem with the 64-bit Vista ULTIMATE system. (I have a choice of three systems)

 ALSO, I have exactly the same sort of problem REGARDLESS of the video capture program I use.  In other words, I have tried Windows Movie Maker, muvee REAL, and a built-in program from HP called Media Smart.   They all fail to capture/write the [filename].m2v file

 I have contacted HP, and they have NO new firewire or chipset updates.  

 

For what it's worth, I have two friends with different brands of HD camcorders who are experiencing EXACTLY the same errors -- with Pinnacle Studio AND Movie Maker etc etc.

 

I have to believe the problem resides in MICROSOFT's 64-bit Vista code.  YOU GUYS can help by working with them to resolve the issue for HUNDREDS of people who will have the same issue as they move to 64-bit VISTA ahead of the up-coming Windows 7 upgrade.

While this is hardly a fix, ...

 

IT WORKS!  

 

Now I can at least use my PC until Windows 7 is fully released.

thanks for the updates.

I hope I get lucky on my next vacation leave so I can find a more permanent solution (or a better workaround ).

 

gregrut1:

Marc --

 

I am experiencing the same issue that others are -- Studio 12 recognizes my firewire-attached Sony HC-3 just fine.  I  can operate the camera from the Studio 12 UI (rewind, fastforward, etc) and initiate CAPTURE VIDEO.  BUT ... as the tape 'plays' no video displays in the preview window of Studio, and the frame counts do not advance.  When the tape transfer is complete and I click on EDIT, then I get the error message that [filename].m2v cannot be opened.  Also when checking that file in MS Explorer, it exists as a file name but has 0 (zero) bytes.  In other words, CAPTURE did not really transfer any bytes and write to disc.

 I can use the SAME camera and firewire cable with Studio 12 on a Vista 32 Home Premium system and a Windows 7 RC 64-bit system WITH NO ISSUES.  The problem is not the camera or the cable.

I ONLY have a problem with the 64-bit Vista ULTIMATE system. (I have a choice of three systems)

 ALSO, I have exactly the same sort of problem REGARDLESS of the video capture program I use.  In other words, I have tried Windows Movie Maker, muvee REAL, and a built-in program from HP called Media Smart.   They all fail to capture/write the [filename].m2v file

 I have contacted HP, and they have NO new firewire or chipset updates.  

 

For what it's worth, I have two friends with different brands of HD camcorders who are experiencing EXACTLY the same errors -- with Pinnacle Studio AND Movie Maker etc etc.

 

I have to believe the problem resides in MICROSOFT's 64-bit Vista code.  YOU GUYS can help by working with them to resolve the issue for HUNDREDS of people who will have the same issue as they move to 64-bit VISTA ahead of the up-coming Windows 7 upgrade.

I agree with you on this. I'm sure our QA team has gotten a report about it, and I'm sure they are working hard to find a way to this work better with Vista 64.