Charles Taylor
Forum Replies Created
-
You should be able to just have AE stomp the old file when it renders.
What I’m saying is skip the step where you trash the file – just have AE replace it when you render.
—
Director of Photography
http://www.CharlesAngusTaylor.com -
Definitely lot’s of good reasons to pre-render, but it shouldn’t look better when you do…
What exactly is the problem here – is AE detecting that the comp is at 30% res and deciding that a 1/2 res render is “good enough”? If it is, that’s scary. It shouldn’t do that…
—
Director of Photography
http://www.CharlesAngusTaylor.com -
You will need to animate and render out video for everything you want to happen.
AE cannot make video that renders in real time for an interactive effect, you will have to fake it.
—
Director of Photography
http://www.CharlesAngusTaylor.com -
Sorry to dredge up an old thread…
Seems to me like if the playhead is inside the work area, then the user almost certainly wants to preview the work area, probably starting from the current frame, no?
I would say the current behaviour is confusing.
—
Director of Photography
http://www.CharlesAngusTaylor.com -
Probably far too late on this one, but did you try swapping the ports on the pass-through drive?
—
Director of Photography
http://www.CharlesAngusTaylor.com -
The TIFFs were about 40 MB each. Compression – I’m not sure, and don’t have the files any more.
—
Director of Photography
http://www.CharlesAngusTaylor.com -
Yes, I completely agree that it is application-related – some apps (FrameCycler, AJA System Test) will get occasional drops to 150 MB/s, but usually around 300 MB/s with spikes to 400-500 MB/s.
Shake and Nuke both can only get the array up to 20-30 MB/s, even if they are not doing anything with the footage (ie. read it in, and display it).
Why is that? What can I do about it? I will post this in the Nuke forum, as well, but I’m wondering if different block sizes would help? I think I’m at 64 or 128, but will check when I’m at that machine again.
-
Hmm, I made an earlier post that outlined more exactly what I’m doing, but it seems not to have gone through.
In that post, I stated explicitly that I’m NOT trying to play back 4K files. I am well aware of the data rates needed to play back 4k, but all I’m doing is rendering. Disk speed is much less relevant when reading and writing the files is a small fraction of the render time.
Not to be snippy, let’s try and assume we all know what we’re doing here, and that the underlying workflow makes sense, and let’s deal with the actual question, OK?
The question is why I’m never seeing read speeds above 20MB/s off of the RAID when Nuke has to pull in ~20 4K files to render a frame. I feel like I should be seeing a spike to 200 or 300 MB/s as it reads in the frames, but I’m not.
If anyone knows why that is, I would love to hear it.
-
Cool, thanks!
-
For casual use (which is what it sounds like you’re talking about), I would recommend a 27″ iMac with the Core i5 and 8 gigs of ram.