I haven't heard anything new on the FCP capture problem of random drop-outs that leave out 4-10 seconds at random spots of a perfectly good tape. Speculation was made about using REC vs. REGEN on the TC Generator, but neither has impacted my capture ability. –24p or 30p

Has this been solved yet? Thanks.

FCP hasn't been updated since September...so no change.

I've never had problems with the ProHD tape. The other day I captured a 15 minute long 720p24 clip without any issues.

I'm not currently an FCP user, but I ran into this over at HD for Indies.

http://www.apple.com/support/downloads/finalcutpro513.html

Apple claims to have fixed some bugs.


Thought you guys might be interested.


Cheers, David

David,

I stand corrected. It looks like version 5.1.3 must have been released about 12 hours ago.

I just read the release notes and there is no specific mention of fixes for ProHD capture. We'll have to test it.

I've had a lot of problems with my ProHD 24P stuff in FCP 5.1.2....

Don't know why. I've gone back to using DVHScap. Oh the fun.....

It looks like version 5.1.3 must have been released about 12 hours ago.


Hmm. Looks like I had impeccable timing with this thread. Didn't know about that. Do test away though as I’m running low on time for it. Let us know what you find.

The last time there was a FCP update there was a firmware update needed for the BR-HD50. Does anyone know if there will be a firmware update needed this time around?

Carlos

Just tried 5.1.3 upgrade. No fix for the dropped frames issue. Doh!

Burt Holland
www.encyclomedia.net

Just tried 5.1.3 upgrade. No fix for the dropped frames issue. Doh!

Burt Holland
www.encyclomedia.net


I tried it earlier and captured an 11 min clip uninterrupted which i could'nt do before (using a cheap jvc tape), it only made a new clip when i stopped/started rec and that i can handle. Maybe it was just luck i don't know, i'll need to test more.

Andy.

Just tried 5.1.3 upgrade. No fix for the dropped frames issue. Doh!

Bummer. I guess I'll have to keep using DVHSCap. Apple, why do you have to be so slow to support this camera fully?

Bummer. I guess I'll have to keep using DVHSCap. Apple, why do you have to be so slow to support this camera fully?

I agree but I am expecting the changes to take place at the NAB in April we will see, maybe final cut pro 6 or what ever. I would be shocked if there are no changes to final cut pro.

I am looking forward to FCP 6 actually. I've submitted a number of enhancement requests and am curious to see how many might be implemented. I can think of at least half a dozen things to improve the program. But I suppose that's for another thread. Hopefully they fix this JVC issue then.

http://www.apple.com/finalcutstudio/resources/devicelist.php

No JVC HDV devices on the official apple list of "products that meet Apple's performance and reliability standards for professional use". Sony, Panasonic and Canon cameras are all represented here.

Interesting... actually - disturbing. I just got my HD-200 delivered 2 days ago, and I'm a confirmed macaholic. This does not bode well for continued effort to solve problems. I assume that JVC WAS on this list before from general publicity and codec development.

Anyone with more knowledge about this?

My workaround is to use iMovie to capture. Downside is that all the footage captured is in Apple Intermediate Codec. But it is bizarre that Apple's amateur editing tool can both capture and convert to another codec in realtime while it's pro offering can't simply capture.

Edwin, can it capture 24p if AIC? Last I checked FCP can capture 30p in AIC, but not 24.

I posted this (http://mac-video-forum.aquafadas.com/en/index.php?topic=248.0) question on the iDive forum.

It would be great when iDive would support HDV for the JVC-HD 1xx/2xx series because FCP has a capture problem with these camera's!

I used to use iDive (http://www.aquafadas.com/idive-digital-video/index.php) to capture my DV tapes.

Another FCP update!

Maybe this time?

http://www.apple.com/support/downloads/finalcutpro514.html

Unless it says something about it in the text, it's not likely. :-(
But thanks for posting.

Hi all,

I'd posted my problems with the 4-Second problem a few months back. At the time, JVC told me I wouldn't be able to get a clean import unless I was using the HD-110, or the HD-100 with the 'A' firmware upgrade and FCP 5.1.

Since then, I've made the software upgrade (firmware upgrade was already done.) Short story is, no joy. I read another post that says 5.1.3 offers hope, but again, JVC said this was supposed to be fixed in 5.1...

The story I'm getting now is that there must be something wrong with my camera in particular, and that I should send it in for repairs.

Two things seem dubious here; (1) judging from this length of this string, I'm hardly alone. (2) They've made no guarantees that the repairs, which I'll need to pay for, will actually work, as the root issue seems to be on the Mac side (details below.)

Instead, I'm simply moving away from the camera. But here are some bits of information I picked up that may be useful to folks still working with it.

1. Incompatibility with Apple

The problem seems to be Mac only. JVC says that has to do with the 'very literal' way OSX deals with incoming transport streams. I wasn't sure what this meant, but apparently it's more stringent than I/O for Win-Tel systems. In other words, the root of the problem is a Mac-specific architecture issue over which JVC has no real control.

Folks using this camera with Premier, Vegas etc. have confirmed that Win-Tel systems don't run into this issue.

JVC did not try to explain why other equipment makers were able to negotiate both Mac and Win-Tel I/O successfully.

2. Video Flags

Apparently, JVC attempted to remedy the situation with improvements to the way the transport streams are flagged by the encoder (i.e. in-camera.)

These were incorporated in the 'A' firmware upgrade. Accordingly (and this is per JVC) tapes recorded on a pre-upgrade HD-100 will still demonstrate the problem, even if the capture deck has been upgraded, and the user is running 5.1. In my experience they both fail, but this the JVC line.

3. Uncompressed Output

None of this has any bearing if you're using the uncompressed component out, and using FCP to manage direct-to-disk capture.

Right now, the camera is doing good service as a signal generator as I get the bugs worked out of a RAID-based DDR solution. But unless I divest myself from FCP (unlikely) I'm unable to rely on it for work that's done on tape.

Hope this helps.

Greetings Alex,

I'm curious to know if you've attempted to capture using the DVHS/Streamclip method. Many people have long since turned away from the native ingest of FCP and have found a very simple effective work-flow using this method.

Hi Alex, I just read your post today. Have you tried this setting in FCP?

1. Open FCP and select audio/video settings
2. Go to the Device Control Presets tab.
3. Select HDV Firewire NDF and click edit
4. Set pre-roll and post-roll to 1 second (default is 3 for both)
5. Save and use that as template for capturing.

I hope this fixes problem you are having. If not, my apologies.

Tim Brown, can you walk me through the DVHS/Streamclip method for capturing footage?

Thanks,
Sharon

The link to the workflow posted by David Knaggs can be found here:

http://www.dvinfo.net/conf/showpost.php?p=598747&postcount=5

George that doesn't work. I tried changing the pre-roll and it still hickups quite often and for more than a couple seconds. I'm going to send in my camera in a couple weeks for some other issues and will note this as one in case they can find a way to fix it...