[Nat Jencks]

Yes, this would be fantastic. I have a CP200 and the wave, and use the wave for resolve, but kind of hate it.

CP200 support would be fantastic.

[Nat Jencks]

Thanks for the feedback Peter! Will let you know how it goes!

[Nat Jencks]

Sasha, agreed that on any platform working with R3D can be more buggy than plain vanilla DPX or a quicktime codec like prores, however, the level of instability I’m seeing can’t be normal even for R3D.

This system has a rocket card and multiple GPUs.

best-
-Nat

[Nat Jencks]

Thanks for the link to the tutorial!

Very useful, but can this be done with a still with embedded alpha do define the matte as opposed to using a keyer like in the tutorial example?

-Nat

[Nat Jencks]

Thanks for the responses everyone. It seems like the behavior we’re seeing is outside the range of “normal” behavior, unless this is linked to working with large amounts of media, and R3D.

What are the experiences of people working on feature length projects with R3D material?

Do people generally keep separate sessions per reel, or have all your reels in a single session?

Also, are other people keeping ALL their source material in the project/media pool or just the shots required for the current cuts? Is there a stability/performance penalty for keeping ALL media in the pool?

Thanks!
-Nat

[Nat Jencks]

no, these were made on a mac. I sometimes use motion jpeg A as a codec when I’m sending to old versions of quicktime, or quicktime on linux, etc.

Prores seems to be working, as does H.264 quicktime. I guess Resolve is just a bit picky about what codec’s it supports. Weird, since for most applications, if quicktime player plays teh file, the application will also.

Thanks!
-Nat

[Nat Jencks]

Thanks!

I tested animation codec which is sometimes referred to as uncompressed or “none”, and it didn’t work. Didn’t test any of the AJA flavors of uncompressed, etc.

Ended up using prores.

I take it you need the $500 avid codec package just to read avid codec quicktimes? That’s crazy!

Every other application that supports quicktime reads avid codec fine. I guess I’ll transcode DHXhd material to prores for now. Seems like an unnecessary roadblock for avid users.

Thanks!
-Nat

[Nat Jencks]

Of course, if he buys two more 8GB chips fora a total of 6x8GB (48GB), that config isn’t officially supported either 🙂

This whole thing of only supporting use of 6 out of the 8 ram slots is really kind of odd.

I would have thought that if adding ram into the additional 2 slots actually slowed down memory performance, apple would have only included 6 slots for RAM…

@Johnathan Lee, yes, it seems like 6x4GB for a total of 24GB is the sweet spot if you are aiming to follow this rule of using 6 out of the 8 slots.

best

-Nat

[Nat Jencks]

Sorry for the ridiculously long delay in response 🙂

Yes, the issue seemed to be with the 8.0 driver. Weird that more people are not troubled by this…

Thanks!
-Nat

[Nat Jencks]

Good call, re looking at the RGB values with the info tab. Using the change to color method (a 16bit effect), I can see that the values change on every frame, in what looks like a linear way, however the displayed color jerks around…

Must be a display issue! I will confirm this soon, viewing this comp on a system with a kona card and a 10-bit monitor.

Thanks again!
-Nat