plug in hard drive to laptop, then HVX to hard drive, and it DISMOUNTS? this is new..

D

dv416

Well-known member
my typical workflow to log and transfer is to plug in my external HD to my laptop, then plug in my HVX to the external - b/c it is the only unit with the right firewire connection. both devices 'mount', i log and transfer and its a done deal. at least thats how things typically work...

TODAY, i plug hard drive into laptop - it mounts - and then as soon as i plug the HVX into the HD and turn the camera on, the drive dismounts, and i get that "improper eject" warning message. somehow, by adding the HVX into the mix, the hard drive ejects itself. this has never happened before. just today. also, the drive dismounts just with the HVX on - not even when the camera is in the log and transfer mode.

has anyone ever experienced this and / or have a solution?

thanks!

and fyi, the drive is a lacie rugged 500gb
 
Last edited:
All macs have only one Firewire bus. They may have one or more ports but only one bus. What you experiencing is a lack of throughput on the firewire bus.

You can solve this problem very easily. There is no need for you to daisy chain your camera in order for you to log and transfer.

Let's begin with proper P2 workflow. After your shoot, offload your cards onto a firewire 800 hard drive. With the correct fw 800 to fw 800 cable (assuming you have a macbook pro) connect the hd to your laptop. Open FCP and log and transfer.

If you only have a fw 400 connector on your computer, that is not going to get you very far editing DVC Pro HD. eSata and FW 800 are your best solutions.
 
thanks for your response, steve

to clarify, it is HVX --(firewire 4pin to 6pin - standard for HVX)--> lacie rugged 500gb HD --(firewire 800 to firewire 800)--> macbook pro. pretty standard, as 4 pin firewire ---> f800 is not a very common connection. the thing is though that this worlkflow HAS worked every time prior to today. and it seems to be less an issue of bandwidth on the connection as it does establishing a connection in the first place!

today, in order to download the footage, i had to return home and capture through a different drive. in this case a 500gb AC-powered g-drive. i used the same 4 pin to HD to CPU (via f800) workflow as before, and it worked. though this time, i was getting some fishy "1394 initial error" messages for a second, before toggling into the camera's transfer mode. while there, i finally got a "1394 - connect" message, upon which i was able to successfully transfer my footage.

the only variables at this point are 1. the lacie. and 2. the weird 1394 initial errors i was getting.
 
Last edited:
> lacie rugged 500gb HD
Click to expand...
that lacie may have something to do with it. lacies have a history of power and firewire termination issues. ive seen lacie and my passport products kill more files and workflows than any virus or power surge ; )
 
You must log in or register to reply here.
Back
Top