Announcement

Collapse
No announcement yet.

Denoiser using remote command prompt

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

  • Denoiser using remote command prompt

    I am still loving the denoiser tool - the time and electricity it saves is incredible, so thank you again.

    I am trying to automate the denoising of sequences using the render nodes and remote command prompts, but I can't seem to get it to work.

    The following works in a local prompt, with and without the GPU switch:

    Code:
    "C:\Program Files\Chaos Group\V-Ray\3dsmax 2014 for x64\tools\vdenoise.exe" -inputfile="\\server\path\seq-A_.????.vrimg" -useGPU=1 -skipExisting=1
    However in a remote prompt for the same node I get:

    Code:
    PsExec v1.94 - Execute processes remotelyCopyright (C) 2001-2008 Mark Russinovich
    Sysinternals - www.sysinternals.com
    
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Windows\system32>"C:\Program Files\Chaos Group\V-Ray\3dsmax 2014 for x64\tools\vdenoise.exe" -inputfile="\\server\path\seq-A_.????.vrimg" -useGPU=1 -skipExisting=1
    V-Ray Denoiser tool for denoising still images and image sequences.
    Copyright (C) 2016 by Chaos Group Ltd. All rights reserved.
    Build from Jun 10 2016
    
    
    Using radius 10, strength 1 and threshold 0.001
    Failed finding OpenCL devices for VDenoise: [OCLDenoiseImpl::pickDevices] No OpenCL devices found
    If I remove the GPU switch on the remote prompt, I get:

    Code:
    PsExec v1.94 - Execute processes remotely
    Copyright (C) 2001-2008 Mark Russinovich
    Sysinternals - www.sysinternals.com
    
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    
    C:\Windows\system32>"C:\Program Files\Chaos Group\V-Ray\3dsmax 2014 for x64\tools\vdenoise.exe" -inputfile="\\server\path\seq-A_.????.vrimg" -skipExisting=1
    V-Ray Denoiser tool for denoising still images and image sequences.
    Copyright (C) 2016 by Chaos Group Ltd. All rights reserved.
    Build from Jun 10 2016
    
    
    Using radius 10, strength 1 and threshold 0.001
    No files found matching "\\server\path\seq-A_.????.vrimg"
    I am guessing this will be permissions related, but I am running the command as a user with admin privileges on the remote node. "\\server\path\" is a ubuntu box running samba.

    Any suggestions gratefully received.

    Many thanks,
    Olly
    Set V-Ray class properties en masse with the VMC script
    Follow me for script updates: @ollyspolys

  • #2
    Is it also possible to specify the output format?
    Set V-Ray class properties en masse with the VMC script
    Follow me for script updates: @ollyspolys

    Comment


    • #3
      Which V-Ray version is that? We had a bug in the original 3.40.01 release where the denoiser didn't work with UNC paths. This is fixed in 3.40.02

      For the OpenCL issues, updating the GPU drivers might help.

      There is currently no way to specify output file name/format explicitly, but we'll get to that.

      Best regards,
      Vlado
      I only act like I know everything, Rogers.

      Comment


      • #4
        Hi Vlado,

        Good to chat to you briefly at EUE.

        We are running 3.40.02.

        I will try and update the GPU drivers to see if that helps, though it does work using the GPU when started locally.
        Set V-Ray class properties en masse with the VMC script
        Follow me for script updates: @ollyspolys

        Comment


        • #5
          Is there a reason ocl is tagged on to the filename for GPU denoised images? Are the two (CPU/GPU) approaches different enough that you would notice if mixed in a sequence?
          Set V-Ray class properties en masse with the VMC script
          Follow me for script updates: @ollyspolys

          Comment


          • #6
            Originally posted by olly View Post
            Are the two (CPU/GPU) approaches different enough that you would notice if mixed in a sequence?
            For now it's just a precaution in case they end up being slightly different. Ideally the result should be exactly the same, but one never knows... We've done some work to unify the CPU and GPU code the last few days, so eventually we will remove the _ocl suffix.

            Best regards,
            Vlado
            I only act like I know everything, Rogers.

            Comment

            Working...
            X