Gamma shift on import of Flame & Smoke quicktime files?

[Joseph Owens]

Sure its not an RGB 0-1023 re-scaling issue? Especially if re-processing through Quicktime apparently fixed the issue.

jPo

You mean “Old Ben”? Ben Kenobi?

[Rohit Gupta]

You can try setting the levels to “Unscaled full range” in the media pool, and see if it solves the problem.

Do you know which codec you are exporting to from Smoke?

[Andrew Smith]

If its for web and broadcast dont i need to set to scaled davinci yrgb to keep things safe? I will try this in the morning to see if that was it but i am curious to know more.

The codec coming from smoke and flame is shown in the screen grab i included.. not sure what you mean rohit.

[Rohit Gupta]

Unfortunately, they are not writing the codec name properly. I suspect it’s some sort of uncompressed codec, and from your description of the problem, I suspect it’s uncompressed YUV.

Resolve (and FCP) interprets this as video-range data, and that’s why the Auto setting treats it as such. If you want to override the behavior, you just select all the clips in the Media Pool, and force the levels to full-range.

Hopefully this fixes the problem for you!

[Gabriele Turchi]

mmm…weird…smoke when render YUV it should properly scale to video levels …

so if video levels is your issue seems that a YUV coded as been generated as full range values

ps: rohit : changing the video level in the media pool as full range does not affect the workflow afterwords right ? i mean , for example rendering than the session as prores : resolve would export video range QT right ? (and not data range (because the media pool as been change right?)

thanks

g

Davinci Resolve Control Surface
MacPro
Cubix desktop 4
2 Red Rockets
GTX470+GTX470+GTX285
24GB RAM
HP Dreamcolor
Panasonic 58PF Plasma

[Rohit Gupta]

Changing the media pool settings only affect the input side of things. The output is controlled by the setting on the render dialog.

[Erik Lindahl]

I think the “LibQT” codec is a none / RGB / higher than 8-bit codec I think. We’ve had huge issues getting workable QT’s from Smoke to our FCP / After Effect station and the post-house we often get files from state the same. Gamma issues primarily (and of course this very odd codec).

Their solution is routing video out from the Smoke and do a capture to a separate station or tape-deck. Sometimes a very cumbersome solution but it give perfect results when comparing to their native dpx-files.

[Andrew Smith]

Ok well then what about when its time to render out in broadcast safe – are you saying i just change that on the render tab and it should be fine or what?

Is it not ok that i transcoded the files to ProResHQ to work with? They seem plenty decent quality to grade off of so why dies it matter?