Quicktime Proxies
From Redhax
Red uses the quicktime infrastructure to support REDCODE.
Here's little snag I ran into that you might want to avoid.
The quicktime references to .R3D files are hard links. So if you move the .R3D file you will have to relink the quicktime manually or regenerate it in RedAlert (also manually).
I ran into this problem when I copied my entire directory structure to a new and faster RAID. The Quicktime reference is still looking for the old Volume.
This doesn't occur when the Quicktime file is in the same folder as the .R3D file. But I had created a master directory for proxies when I generated them from RedAlert (off of build 6).
The solution to this problem is to keep your Quicktime proxies in the same directory are your .R3D files. But what a pain then to manage them all. So I hacked this little Applescript
[edit] Playback Benchmarks
|
System |
512 x 256 |
1024 x 512 |
2048 x 1024 |
|
Macbook Pro 2.4 Ghz Core 2 Duo, Internal 7200rpm drive |
24 fps |
12 fps |
4 fps |
|
?Mac Pro 3.2 GHz 8 Core, internal 7200 drive |
24 fps |
24 fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
|
?System? |
? fps |
? fps |
? fps |
