Announcement

Collapse
No announcement yet.

vDenoise Command Line tool Helper (Maxscript UI)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mokiki
    replied
    What would be the way to go to keep the multi exr workflow (manipulating passes etc.) and use the denoising functionality without nuke?

    Leave a comment:


  • vlado
    replied
    Extract the plugin for your version of Nuke to some folder, f.e. d:\temp\VRayDenoiser. Go to Control Panel > System > Advanced system settings > Environment variables... button. Click the New... button and enter the variable name NUKE_PATH and set the variable value to the path where you extracted the VRayDenoiser.dll (i.e. d:\temp\VRayDenoiser).

    Next time you start Nuke, you should have the VRayDenoiser node available. If there are any problems, please email me to vlado@chaosgroup.com

    Best regards,
    Vlado

    Leave a comment:


  • AC5L4T3R
    replied
    Could you show me how to set up the environment variable correctly as I'm having trouble with that part.

    Leave a comment:


  • AC5L4T3R
    replied
    Oh right, awesome thanks

    Leave a comment:


  • vlado
    replied
    You don't need V-Ray for Nuke.

    The denoiser plugin for Nuke is a completely separate and free plugin for Nuke, as can be seen in this video:
    https://youtu.be/IzmjPuU3chk

    Best regards,
    Vlado

    Leave a comment:


  • AC5L4T3R
    replied
    Sorry Vlado, I was talking about the Vray 3.5 beta. I've got a super tight deadline atm and have to sacrifice quality for time. Ideally I'd want to denoise the passes so they can be used by the comper (they don't have vray for nuke).

    Leave a comment:


  • vlado
    replied
    The Nuke denoiser is not technically a part of any beta; it will work fine even with the current official releases. You can get it here:
    http://help.chaosgroup.com/vray/misc/vdenoise_nuke.zip

    You can wire as many denoiser nodes as you need to denoise whatever render elements you need.

    However, instead of working with denoised elements, it seems better to leave the denoising for the last stages of compositing where you already have put together the comp and you just denoise the final RGB result. This is also the only way to work with deep compositing. You can also use the noiseLevel render element as a mask to control the strength of the denoising in various parts of the image, if needed.

    Best regards,
    Vlado

    Leave a comment:


  • ^Lele^
    replied
    not entirely sure (am on totally different builds myself.) if it made the first beta cut, or if it'll make the second, for that matter.

    Leave a comment:


  • AC5L4T3R
    replied
    Originally posted by ^Lele^ View Post
    With the free nuke denoiser node, sure.
    SP5 will have the ability to denoise REs.
    Can I do it with the Beta?

    Leave a comment:


  • ^Lele^
    replied
    With the free nuke denoiser node, sure.
    SP5 will have the ability to denoise REs.

    Leave a comment:


  • AC5L4T3R
    replied
    Lele, is it possible to specific render passes such as the GI pass?

    Leave a comment:


  • ^Lele^
    replied
    likely a malformed file name.
    I am removing the BB submitting version from the thread.
    Please do not use it.

    Leave a comment:


  • squeakybadger
    replied
    Hi Lele,

    I'm having trouble getting the BB version to submit, it just pops up an integer error and points to this line in the script:

    "minFrame=(subString (getfilenamefile theFiles[1]) (findString (getfilenamefile theFiles[1]) stringToFind) -1) as integer"

    Any ideas?

    Thanks.

    -j

    Leave a comment:


  • eyepiz
    replied
    Originally posted by ^Lele^ View Post
    I see where the odd behaviour is: each time you pick an image which is detected as part of a sequence, it will turn frame blend to 1.
    So if you have a preset and then pick a file, it'll revert that to 1.
    I'll just remove the automatic behaviour altogether, and simply default it to 1.

    Which version are you using, of the lot i uploaded?
    Hi Lele,

    Anyway you can remove the automatic behavior in the frame blend?

    I would really appreciate it.

    -E

    Leave a comment:


  • eyepiz
    replied
    Originally posted by ^Lele^ View Post
    I see where the odd behaviour is: each time you pick an image which is detected as part of a sequence, it will turn frame blend to 1.
    So if you have a preset and then pick a file, it'll revert that to 1.
    I'll just remove the automatic behaviour altogether, and simply default it to 1.

    Which version are you using, of the lot i uploaded?
    The one from this date "19-08-2016: Updated the BB version"

    Thanks Lele! I'm using this a lot.. being able to deniose 18k VR renders with per element denoising on multiple GPU's gets done in a few minutes.

    Leave a comment:

Working...