[Blase Theodore]

Posted same issue a while ago…

Here you go..

Solution from Rohit:
Source blanking in format page set it to off.

[Blase Theodore]

I’ve been told the remmeber cache feature is in the works, and that would essentially mean they’re already thinking about heirarchy for cache files.

In the meantime, the cache is gone the next time you start so its sort of a waste to render the whole thing. Are you using render selected clips to cache? Maybe more effective?

[Blase Theodore]

I’d say the new color mixers basically reproduce this functionality. Correct me if I’m wrong.

[Blase Theodore]

Id be curious if those are actually implementable. Obviously in RED footage or a raw photo editing platform, you’re working with raw debayer info, and can actually interpret the data. Once its baked in though to a quicktime or frame, not sure how that would work. (Just like you can pick a color temp for a raw still in photoshop, but after that you can only tint it.)

[Blase Theodore]

The above post should cover you. Otherwise:

Obviously make sure you’re using the 120 as the GUI card.
Make sure your system actually sees both cards. (Your galaxies benchmark scores should be 50+ and 300+) If not, how are you initializing the cards? A kext or an EFI string in boot.plist? (Or in bootloader efi?)

[Blase Theodore]

I second this.

[Blase Theodore]

Here’s how I deal with this on features..

I give the client a choice to work completely supervised, or “my way”. My way involves:

Day1: client sets looks for all key scenes.
Day 2, 3, 4: I work unsupervised. First I build the entire film out on a neutral pass and fixing problems. Then I apply style over the top. In case the client changes their mind on the style. Usually 10+ hour days, but I have itunes blaring in the background, and I break when I want. When its done, the film is at a place where I’m generally happy with it.
Day 5, 6: client reviews and tweaks: This gives 2 full days of ironing, and indulging the Dir/DP in power windows that otherwise would never have fit into the schedule.

That way when the film is done, the client is thrilled, and you’re ‘mostly’ happy with the result. Its filmmaking, so you never really feel complete with it. I’ve achieved grading “perfection” 2x in my life. And both times the client was as perfectionist as I was, and decided to spend the extra time until there was nothing more that could be done. But most of the time, you do what you can with the time you have.

[Blase Theodore]

A: unlikely even in latest MacPro you could get away with it but can’t honestly say no for sure. I run my macPro with 470, Redrocket (I assume comparable to a gfx card in power needs) ATTO card, DL 3d+ card and 3 hard drives. Its possible that just the 470 and 4000 would work, but seriously doubt you’d get a full system to work.

B: There’s no advantage to doing this. The 4000 would act as the GUI card and wouldn’t be used for processing. Unless you threw in a 470/4000/120 combo, but really unlikely at that point. And at $1k, that 4000 card is not a deal in my book. Better off buying an expansion chassis and a 2nd 470 (even the cheap 40Gb/s one would be money better spent.)

[Blase Theodore]

Ha, nice Vlad!

[Blase Theodore]

Here’s a test that would troubleshoot it for us.

2 clips on a timeline

• Export XML pre-render: test01
• Set render dialogue to FCP preset, but don’t render, export xml :test02
• Render clip1 in preset mode export xml: test03
• switch render mode to none, but don’t render. export xml: test04
• render both clips in none to new dir, export xml: test05

Test results:

• did the test05 clips have the same extension?
• did the extension change from test03
• did the expected xml clip links change between test01 and test02? Or the other test versions?