[Henry Barrial]

I think this is what’s happening. I’ve had it with this whole ProRes/DNxHD BS. I’ve been exporting 4444 ProRes just fine for months and now it decides to switch settings because somewhere in my timeline I’m sure there is a piece of transcoded something or other to DNxHD? I’m sure that’s what’s happened too, because I’ve just spent some time transcoding a sequence so I could create an AAF. I was one of the stupid ones who bought into all the AMA linking talk. Since AMA linking will block one’s ability to export an AAF, I was forced to transcode the reels into DNxHD.

I’m in puratory for sure. But thanks for your help!

Henry

[Henry Barrial]

Pat, I want to thank you. The transcode worked and, just as importantly, the choice to convert 29.97 audio clips (how some of my audio got this way is anyone’s guess) also worked like a charm. All my audio is checking out in sync. With your help I have gotten over my domestic feud with MC 6.0.1 and gives me hope that I won’t regret choosing this path. Thanks Pat!

[Henry Barrial]

Transcoding proceeding well. Did come across a message that basically told me I had to either convert or skip some media because it was moving at a different rate than the project rate. This is the exact message: “Some clips do not match the rate of the current project.” I converted. I guess I better double check everything later.

[Henry Barrial]

Thank you Pat. I will try that after I get off work but it sounds like there’s a good chance that might be the issue. I hadn’t thought to press that button because it already seems selected. Some of the intricacies involving Avid are new tome. I’ll update later. Thank you!

[Henry Barrial]

I tried that and the Transcode button remains greyed out. I have no video on timeline, only audio because I’m trying to export an AAF. No matter what I check the Transcode button remains grey and unavailable. Curiously, in the upper right hand rectangle of the transcode window it is reported that “0 clips selected” “0 effect clips selected” “1 sequence selected.”

So the transcode seems unavailable. I ask myself, is it the AMA links that won’t allow transcoding? How can I transcode media that is only linked? Do I need to import media? Can’t I just select the media in the sequence, make it off line and then import with handles?

Henry

[Henry Barrial]

This is what I was afraid of. I was warned about AMA but I just liked the thought of editing native. No truth in advertising on that one. In any case, thanks for the white paper. I’ll see what I do after I read that.
Appreciate the help.

[Henry Barrial]

Was able to lose about 2TB of MXF backups of media on my 8Tb gRaid. MC6 playing back better, but everything with multiple layers of effects stumbles into that jitter. I feel like I’m getting closer to an answer. I could probably find another 3-500 gigs to lose. Should I do that? Glad it’s running better though. The drive actually sounds happier.

[Henry Barrial]

Processor 2 x 2.8 GHz Quad-Core Intel Xeon
Memory 4 GB 800 MHz DDR2 FB-DIMM
Graphics ATI Radeon HD 2600 XT 256 MB

I am editing natively in PRORES 444 through AMA linking. The AMA linking has worked fine for months.

Drive is an 8 TB G Raid via eSATA 3Gbit

6.8 TB of the 8TB are used up on the drive.

All clips start to play well then they devolve into jitter. Some sections don’t jitter if I play in a small window. But everything eventually jitters especially when I’m in full screen playback.

I will play back a portion of the timeline and I can actually see the red marks being added in realtime on the timeline as the “cursor” plays through the sequence. My drive sounds like it’s working extra hard. Perhaps I should relieve it of some of its extra material. Clean house a bit and see if it’s the drive. I’ll try that and report back. Thanks!

[Henry Barrial]

Meant to include these. These are specs for my jittery computer:

Processor 2 x 2.8 GHz Quad-Core Intel Xeon
Memory 4 GB 800 MHz DDR2 FB-DIMM
Graphics ATI Radeon HD 2600 XT 256 MB
Software Mac OS X Lion 10.7.5 (11G63)

[Henry Barrial]

At this point I think we’ll stay AMA and keep it with the single CPU and drive and match back (which has been the only consistent fix). I can’t start over. Thanks!