[Bryan Colvin]

RAD, the answer I was looking for was what you mentioned with the P { } keys

now I can stick to the keyboard to fly through trimming thanks!

[Bryan Colvin]

They are not overlapping timecodes I am able to sort by START and they audio and video pieces alternate since the ToD timecode was close enough in sync on set.

It does make sense that its grouping since I tried to use Mark IN

So I guess using autosync on an entire bin only works if you have a sync broadcast into slate/camera and audio

that is a bummer

Since in this current project the audio has a ToD timecode and the camera has a ToD timecode running separately. IF I can find out how far off the timecodes are can I use that to sync the footage?

[Bryan Colvin]

I am running Avid MC 7. I AMA Linked and then transcoded. Then I used autosync on a single take and it did infact allow me to perf slip. Maybe it didn’t let you do it in previous versions

[Bryan Colvin]

sequence settings:
Frame Size: 1920 x 1080
Aspect Ratio: HDTV 1080i (16:9)
Pixel Aspect Ratio: Square
Editing Timebase: 23.98
Apple ProRes 422 (Proxy)
Audio 48 KHz, 24-bit

all my footage is transcoded as

Frame Rate: 23.98
Codec: Apple ProRes 422(Proxy)
Frame Size: 1920×1080
Pixel Aspect: Square

Data Rate floats around 4 MB/second

Audio media is:
multi-mono files (3-7 tracks)
48 KHz 24-bit
floats around 700/kbs for most (5 tracks)

AJA System Test

The RAID0 drive
Frame Size Sweep
KB MB/sec
Read Write
16.0 27.7 35.0
32.0 58.2 44.8
64.0 69.5 56.0
128.0 76.1 60.4
256.0 78.1 63.4
512.0 81.8 64.6
1024.0 82.3 65.1
2048.0 81.7 64.8
4096.0 81.6 64.8
6144.0 81.6 64.9
8192.0 81.7 64.9

seems to be performing fine

the scratch disk

Frame Size Sweep
KB MB/sec
Read Write
16.0 39.6 31.9
32.0 53.0 39.5
64.0 53.4 47.6
128.0 53.4 49.7
256.0 52.3 50.4
512.0 53.4 51.2
1024.0 52.7 50.1
2048.0 52.7 51.4
4096.0 52.7 50.9
6144.0 53.5 51.6
8192.0 53.1 50.8

I’m at a loss, it seems like I have plenty of power to run this project 🙁

Computer is
Mac Mini
OS X 10.6.8
2.66 GHz Intel Core 2 Duo
8GB 1067 MHz DDR3 RAM

Both RAID 0 Hard Drive arrray and scratch disk are plugged in to firewire 800 (daisy chained). Raid goes directly into computer, scratch is chained to RAID.

I never used a scratch disk before this problem, i was running entirely on the RAID 0

This project has worked beautifully with NO errors for months. Just the last couple days it started having issues.

I’m wondering if its a problem with the FCP Project file… I have all kinds of backups so I’m trying to open old ones and see if i get rid of hte problem by going to versions before it started acting up

🙁

[Bryan Colvin]

well, i spoke too soon… its still dropping 🙁 🙁 🙁 🙁 🙁

[Bryan Colvin]

wow, I think I just solved it.

another detail was that I had a 2.35 bars + timecode burn overlay using Apple ProRes 4444 for its transparency.

I moved that to the scratch disk and SOLVED. Now I can put all my settings back to high quality and it works perfectly.

I guess since hard drives can only read at one point at a time, overlaying the timecode burn (which is on a completely different sector on the hard drive), make the needle have to bounce back and forth like crazy to read both at the same time.

By moving it to another drive the scratch disk can focus on reading the timecode burn in file separately, leaving the RAID 0 or even my small 1TB to focus on the footage only.

you learn something new everyday

[Bryan Colvin]

i know it may make it hard to work with but, precompose?

idk if that feature is in CS5, but you can also put it in its own composition yourself and then drag the composition in.

you can mask that anyway you want

[Bryan Colvin]

brilliant!

I also noticed that you can copy the path of a shape layer and paste it as the mask path.

now i can get it done faster, thanks!