Is the 8400 below your spec?

Do you mean

MC ver3. HPxw8400 Intel R Xeon quad core 5150@2.66Ghz. 3Gb ram. Nvidia Geforce 7950 GT,  dual display mode.

Yes I think thats what it is, I assume its quad core, in the device manager under processors it lists 4 x Intel Xeon 5150@2.66Ghz,

Also noticed that I cant import anything into a bin - it says there are no media drives available, but there are.  In other projects I can import, but not the HDV one.  I am sure I ahve seen this before but can tremeber how to correct it.

Ok, as I see there are problems capturing from tape from 100/110.

Can anyone who has tried it tell me if the same sync problems appear when importing the 25p files from Firestore DR-HD100 disk - shot by/via a JVC 100/110? Don't want to learn this the hard way.

Thanks for the reply,

m.

 Hope this helps.  Follow this link:  

Has anyone tried capturing JVC footage through the BRHD50 deck?  Moreover,  is it the use of the camera as a deck  that's the problem, or the format?  As others, i'd also be interested in hearing about others experience w/ footage captured w/ the DR-HD100.  I could supply a link to some test footage if someone wants to give it a whirl. 

This has been an issue since MAY 2006 - and has yet to be fixed. The JVC GY-HD100 camera was originally approved.  Eventually I gave up and went FCS2, which works perfectly. I have NEVER seen the 'when capturing it looks out of sync, but on playback it is fine'. Every bit of video and audio - breaks sync around 1 minute after capture begins... and playsback out of sync (about 3-8 seconds out of sync).

I have used the 100, the 200, the HD50 and the FS4ProHD (which has also never worked in HD with Avid) and none of these have ever worked.

When this get's rectified I will gladly be back on Avid with HDV material (again only 720/30), but until then... FCS2 it is for me.

Just to add, the footage was shot using also the 100, the 200, recording directly to the HD50, and, depending on occasion, simul recording to the FS4ProHD. It never worked and - as of 6/13/08 - continues not to work.