[Kent Kajino]

Yes, I hear it can be a problem when film people are forced to adopt video. But, for the most part, I’ve never personally met a serious producer with enough budget who chooses HD video over film, unless he’s from the broadcast end of the business. But, over in Japan, television is king, so maybe the JP video manufacturers have a warped view of the world outside in marketing their wares.

[Kent Kajino]

Have you tried starting with a sequence preset that matches your 1920×1080 footage (rather than a 1440×1080 sequence)? Maybe then, FCP won’t complain that “presets don’t match”.

Then, when you do a recompress in Media Manager, FCP might accept your desired settings rather than ignoring them.

[Kent Kajino]

Do not use “journaled”

Is what a tech from a RAID box manufacturer has told me.

[Kent Kajino]

I haven’t yet tried edit to tape on my A1J since I bought it, so I’m not sure what problems there might be.

Can you at least re-establish deck control with your A1, like you did when you captured your footage?

I did notice during capture, that one needs to set the capture format to exactly what the camera outputs. FCP won’t detect it for you.

but I’m sure you have the FCP output set to HDV1080i, and the A1 HDV to DV mode turned off and so on…

[Kent Kajino]

I once made a fatal mistake of getting WD Caviar drives to build a SATA RAID tower.

Caviars have a long error recovery cycle that interferes with RAID operation. Their RE line is what you’re supposed to get if you want WD.

[Kent Kajino]

I was under the impression that one should use large block sizes for large files, such as video files, and small block sizes for small files, such as documents.

If your files size is only 12k, it makes no sense to block off a whole 512k, wasting the unused 500k.

but if you have a 2mb file, then the hard drive records it in just four 512kb chunks, rather than twenty 32kb chunks, so that it doesn’t have to search as hard.

[Kent Kajino]

Happened to me last night while capturing DVCAM, but after repeatedly clicking on the application and hitting Esc several times, I was able to abort capture.

[Kent Kajino]

I don’t know (I doubt) that making the media files smaller will help performance, unless your talking about getting rid of media files to go from 90% full to 80% full.

If you want to, maybe you can use the media manager (was it called???) to break up the large clip into smaller ones. I read this in the manual where making subclips is discussed. It involves placing the large clip onto a timeline, shortening it, then draggin it back onto your bin. Then you’d need additional space for the new files when you use the media manager.

[Kent Kajino]

Thanks for the clarification.

I have only tried HDV with FCP5.1 so I didn’t know the capture options were different from DV.

It seems like I will have to live with the automatic scene detect behavior, and replace the clips on the timeline manually.

The clips I have were logged and captured as downconverted DV, then edited onto a sequence in a different NLE. I had he project ported into FCP for HDV capture.

[Kent Kajino]

Thanks for your response.

But, the behavior holds regardless of clip length or file size.

To see if Automatic Duck is causing this, I created a new project, logged a clip that has a scene change in the middle. When I batch captured the clip, two separate clips were created, rather than just one.

If that’s how FCP has been hard-coded (without the option of turning it off), then I’ll just have to manually replace the clips, which is a bit labor intensive…