When I'm looking at the Item Properties for the Apple ProRes 422 (HQ) multiclip it (of course) shows the data rate for the multiclip itself
V1: 21,8 A1: 21,8 A2: 21,8
as well as the data rate for all four included, individual clips
V1: 21,8 A1: 21,8 A2: 21,8
V1: 22,3 A1: 22,3 A2: 22,3
V1: 21,9 A1: 21,9 A2: 21,9
V1: 22,1 A1: 22,1 A2: 22,1
Should I count the data rate for the multiclip only (about 3x22=66MB/sec) or should I count the combined data rate of all the individual clips (about 15x22=330MB/sec)?
If the latter, it shouldn't be a problem for the Sonnet Fusion DX800 RAID, but maybe for the ATI Radeon HD 5870 graphics card. Here are the technical specs from amd.com:
- Engine clock speed: 850 MHz
- Processing power (single precision): 2.72 TeraFLOPS
- Processing power (double precision): 544 GigaFLOPS
- Polygon throughput: 850M polygons/sec
- Data fetch rate (32-bit): 272 billion fetches/sec
- Texel fill rate (bilinear filtered): 68 Gigatexels/sec
- Pixel fill rate: 27.2 Gigapixels/sec
- Anti-aliased pixel fill rate: 108.8 Gigasamples/sec
- Memory clock speed: 1.2 GHz
- Memory data rate: 4.8 Gbps
- Memory bandwidth: 153.6 GB/sec
- Maximum board power: 188 Watts
Thoughts, anyone? Or am I thinking the wrong way about this?
You need to be factoring the combined data rate of all four clips, since they're all streaming off your drive at the same time to create the multiclip.
I don't think your video card would cause this.
Do you have thumbnails and waveforms turned on or off in your timeline?
You mentioned that a multiclip created from 3 of your angles played fine. Have you tried creating that 3 angle multiclip with different combinations of your 4 angles? Perhaps one clip is simply corrupted and is choking your multiclip.
Your system should handle this. Confusing.
Currently Being ModeratedMay 25, 2011 6:59 AM (in response to thrillcat editorial)
Also, make sure you do not have Video Scopes Playback selected in your timeline. If you must see the scopes during playback, leave Video Scopes Playback selected and select Limited Lines (fastest).
The idea is to reduce the load as much as possible.
Again, investigate the possibility that your Fusion DX800 has a drive that has gone paws up. If you're not sure how to do this, call Sonnet Tech Support.
The problem still sounds like a disk throughput problem...
Remember, your RAID may be able to do that data rate from a single file, but with multiclip, you're reading from 4 separate files. That can involve considerable latency as the drive heads may have to be jumping all over the platters.
Brian Conner wrote:
Especially if the RAID 5 set is degraded due to a drive that's gone down. The OP still hasn't clarified if he's checked that.
I concur. I'd bet the external raid device is not playing up to spec.
Currently Being ModeratedMay 25, 2011 6:13 PM (in response to Patrick Sheffield)
Upthread, the OP says Aya Stem Test benches the DX800 at 650 MB/sec. But that array should be giving him something in the 800 MB/sec range. Sunds like 1 drive is down, which could create throughput problems beyond the raw data rate.
Currently Being ModeratedMay 25, 2011 6:54 PM (in response to Patrick Sheffield)
I agree with the thoughts about it being disc throughput related.
If it worked with ProRes LT, but not with ProRes or ProRes HQ that seems to suggest that ProRes LT's lower bitrate is solving the multiclip problem.
Perhaps you multiclip with LT, then reconnect to HQ?
Currently Being ModeratedMay 25, 2011 10:44 PM (in response to thrillcat editorial)
I've done 90 minute 6-7 angle ProRes multiclips without a problem.
I'm curious, what quality were the ProRes? HQ? Were they 720 50p or superior? What was the data rate of those clips? What was your setup?
It would be interesting for everyone to know. Because the OP's situation and question is pertaining to his particular setup and material, but in the interest of everyone reading, it would be interesting to know if it's possible to edit a hour long 4 camera show filmed in HD and converted to ProRes HQ on a MacPro like the OPs
MacPro 5,1, 3,3 GHz 6-Core Xeon with 12 GB of RAM
Perhaps the OP has left the discussion because he found that using LT and Proxy he could edit the piece as I suggested upthread and for that he gave me the 5 points that I have since shoved up my bum.