Відео

happy to try to help but i'll need more specific information. - in what software / in what tool are you hitting "group"? - what os? - what version of nuke (if applicable)? - what version of python (if applicable)?

@@jedsmith it happens to me too. I'm using nuke 15 in windows 11 with python 3.10. It happens when I select several images and click on ''short selected reads''

@@jedsmith here the log: [22:04.52] ERROR: ExposureBlend.EqualizeExposure9.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure7.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure8.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure6.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure5.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure4.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure3.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure2.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure1.value: unexpected end of "exposure/" [22:04.52] ERROR: ExposureBlend.EqualizeExposure0.value: unexpected end of "exposure/" Traceback (most recent call last): File "<string>", line 127, in <module> File "<string>", line 43, in sort File "<string>", line 43, in <dictcomp> TypeError: strptime() argument 1 must be str, not None

​@@ivantovaralbaladejo687 Thanks for the additional info, that gives me something to go on. On line 43 the code calls datetime.strptime(n.metadata().get('exr/Exif:DateTimeOriginal')-- this is used for the exposure bracket detection. It sounds like maybe that metadata does not exist in the debayered exr image you are loading as your source. Can you confirm? If so is there other metadata describing the capture time? It's possible Canon cameras use this but not others.

​@@jedsmith I'm using 16-bit tiff images converted from RawTherapee. I tested with Lightroom too and doesn't work. Could it be the format? In the metadata of my file I see the exposure time for each image though

here I believe: studio.blender.org/join/

Not sure it's gonna help you much, but sure I added it to the description: codeshare.io/zyMb7D

I swear I just find you in the most random places on the internet lol

@@InLightVFX haha hello Jacob! Glad to see you on this gem of a video x)!

Thanks! It's Falk Hoffman's Channel Hotbox www.nukepedia.com/python/ui/channel-hotbox

Howdy, I am a little late here but AFAIK, Lightroom will always apply its aestethics to your shots so it should be avoided in a linear workflow altogether?

Hey Daniel! Thanks for the kind words. In Nuke I do wish we had a nice Remap node. The math in the Histogram is the same as the Grade node, but I agree it could be more intuitive to use for the simple task of remapping a source min and max to a target min and max value.

This comment does not constitute legal advice. According to the readme included with the footage media.xiph.org/tearsofsteel/tearsofsteel-footage-exr/README.txt The license of that footage is Creative Commons Attribution 3.0 : creativecommons.org/licenses/by/3.0/

Ah sorry I missed that -- the built-in divide node doesn't handle values below 0 properly so I usually use my own built from a MergeExpression node. Ar/Br

Sometimes I will swap the order so it's Br/Ar as well, so that I can disable the Merge and pass through the B pipe to disable the operation instead of passing through the thing I'm dividing out.

@@jedsmith Hey thank you for the video. Very usefull.When you said Ar/Br. You're using the R channel? and why? Thanks

@@djordjeilic9634 Yeah sorry that was not very clear. It would be Ar/Br for the red channel, Ag/Bg for the green channel etc

Hey! It's all in my nuke-config git repo: github.com/jedypod/nuke-config/blob/master/ToolSets/Merge/ExposureBlend.nk github.com/jedypod/nuke-config/blob/master/ToolSets/Color/CalibrateMacbeth.nk

@@jedsmith Hello Jed, nice to see you again. Would it be possible to make these links live again?

Hey Ms. Robles! Good to hear from you! :D Sorry it looks like I moved those files around since I posted that - I edited the above links so they work again.

@@jedsmith Thank you. You are the best!

Yes it should work fine in Nuke 13. The only thing that would need to be updated is support for Camera3 class nodes in the "Get Selected Camera" python script button.

Hi! Yours is the second request for the topic of scene-linear raw debayer workflow... I will definitely make it my next video. Now... just need to get some spare time to work on this :)

@@jedsmith awesome. Thanks a lot. Looking forward to it.

我对此感到抱歉

Hey! Thanks for the nice comment. Debayering into ACES can be tricky. This is the subject of a video I have planned to create, going into a lot more detail than the little hints I put in this video. Getting Debayer to work on Windows can be tricky due to the OpenImageIO and OpenColorIO dependency. Even using Choco package manager to get them running can be difficult. So I can't say I blame you there. You're actually not the first person to inquire about this, so I think I'll try to work out a how-to for getting Debayer running on windows as well. Short answer for your question: Most raw image formats store the raw bayer data in an integer format. Integer implied a 0 to 1 range, with the number of steps between determined by the bit-depth. Therefore all data that the camera captures is going to be between 0 and 1. Values above 1 will be clipped. If you debayer using the RawTherapee profile I supplied in the Debayer github repo, you will get something resembling Scene Linear ACES data, but encoded in a 0 to 1 range. The next step would be to expose your image such that an 18% diffuse reflector would be a value of 0.18 in scene linear. Now you have a proper scene linear image, maybe with specular highlights above 1. Where sensor clip gets mapped to depends on how your image was exposed in the camera and your camera's dynamic range. For example an Alexa will usually clip at around 35 to 40 in scene linear depending on the camera, the dp and the show. My shitty Canon 5Dmk3 will clip at around 12 to 15 if shooting in dualiso using magic lantern. Hope that helps! I'm working on a video about image data formats, and then one on debayering is up next I think. Just need to get some solid time to work on it! :)

@@jedsmith Thanks a lot for your detailed reply - I appreciate that! Of course there are still a lot of questions but I'm happy to wait for your next video and get my head around it. Maybe I'll also jump on ACEScentral and create a thread to get more information on the workflow. Wish you all the best!

My philosophy exactly. Thanks for your nice comment! :)