[Nat Jencks]

CUDA 6.0.37
GPU Driver Version: 8.16.76 310.40.00.20f04

But this is happening even when I turn off GPU debayering.

Problem goes away when I go to completely software only debayer.
This rocket card has never had issues before and performs well in RedCineX Pro.

best-
Nat

[Nat Jencks]

Moving it around by hand using dynamics works, but doesn’t give the most organic moves since it moves in a perfectly straight line at a linear speed… I’ve found it need to drop in a lot of keyframes to get something good. if the motion path made a bezier curved path between keyframes it might work better, but it seems to just go in a straight line.

One thing to try if your light source is in frame the whole time is to track it, then put a temp window on it that makes everything in frame black except a little circle on your object. Then use the auto track lens flare to auto position the lens flare based on brightest object, and then disable the window layer. Not sure if this would work, all the times I’ve used flares I’ve wanted the “source” position out of frame.

best-
-Nat

[Nat Jencks]

Juan your right, I was thinking it was encoded as DCI/P3 and targeting Rec709 in which case the gamut conversion would be P3>rec709 as well as changing the encoding XYZ>RGB.

Daniel, if your source was in fact rec709 and so its all in-gamut for rec709 perhaps all you need is conversion from XYZ to rec709 RGB. I believe Steve Shaw should be able to sell you with a LUT to do this.
best
-Nat

[Nat Jencks]

There are multiple ways to do this (going from a wider gamut to smaller), one way is to simply clip colors which fall outside the target gamut. Another strategy is to roll off saturation as it approaches the outer limits of the color gamut, sort of like a soft clip / roll off for gamut.

This second method is a subjective rather than purely mathematical conversion.

Steve Shaw at lightspace will build LUTs one a one off basis, and could certainly provide you with a clipping LUT, and possibly one which rolls off gamut as well.

best-
-Nat

[Nat Jencks]

Nice Steve! Ask and you shall receive 🙂

[Nat Jencks]

Yes, BMD, if you are listening please count this as a feature request…

THIS IS NOT A GOOD WAY TO IMPLEMENT THIS.

If you have 5 discreet tracks, and want to simply leave then discreet with a 1>1 mapping, it shouldn’t be necessary to do anything with Panning.

Its counterintuitive.

As more people start using resolve to make DCPs with the easy DCP plugin this will burn more and more people.

My 2 cents.

best-
-Nat

[Nat Jencks]

Hi Paulus, is this problem intermittent? I haven’t seem this in a while, but I used to see this once in a while, where all R3D footage would go black. Always was solved by a reboot. I assumed it was flakey behavior from my RedRocket card. I’ve talked to many others with rocket cards who have seen this in resolve, although I don’t know if its really result of the rocket or software, or something else. May or may not be related to your current problem of course.

best-
-Nat

[Nat Jencks]

Yes! What is this error message? I get it once in a while, and then it goes away. Ive sent to support many times, but since its intermittent for me its hard to reproduce, and doesn’t seem to have a specific bad side effects?

What causes this?
-N

[Nat Jencks]

I have had this issue a number of times, and its very frustrating. I think its somehow linked to a corrupted project.

I was able to solve the problem eventually by exporting my timeline as an XML, creating a fresh project, and importing the XML into the new project.

I’ve had this happen a few times. Frustrating. Maybe something linked to corrupted project settings.

Try a fresh project.
best-
-Nat

[Nat Jencks]

Yes indeed, and the films that I work on are obviously mixing elsewhere, and then they deliver the LTRT and 5.1 mixes back to me which need to be output as part of the final deliverables.

My question was obviously regarding how resolve handles track allocation and panning when cutting in mixed audio which has been mixed and mastered elsewhere.

-N