This guide is applied to any XYZ tiff or DCDM file that you want converted to PixelVision.

Few things to Note:

1. This watch folder is only set up to accept XYZ image sequences of either Tif or DPX. If you have image files in a different color space or codec, this watch folder will not work.

2. The watch folder will copy the naming and frame number of you source files. If your source DCDMs start at 0000000, your PXLVIS DCDMs will start at 0000000. If your source DCDMs start at 0175000, your PXLVIS DCDMs will start at 0175000.

3. The watch folder does not remove your source DCDMs from the input folder after they have been processed. Please remove your source DCDMs after they have been processed. Failure to do so will add unnecessary storage.

4. You can watch your render progress at the links below.

Burbank:
10.100.110.167/cf-web-ui/render

London:
10.110.130.98/cf-web-ui/render

 

1.   Set Up

• Navigate to your source XYZ files that you want to convert to PXLVIS

• Open a new window and navigate to the watch folder location
  • For Burbank navigate here:
    • pfs00/_source/_dc/_watchfolder/TKD/dcdm_to_pxlvis

• For London navigate here:
  • pfs01/_dc/_watchfolder/TKD/dcdm_to_pxlvis

2.  Watch Folder

• The watch folder can accept the parent folder that holds all your image files.
  • `In the example below, "ger_inserts_r2" holds all our R2 inserts. We want to grab this entire folder

• Copy the entire folder that holds your image files to the "input" folder.

• IMPORTANT: Do not remove/change the "_.watchfolder" file. The automation will break if this file is removed or altered. 
• Within 20-40 seconds, TKD will pick up the job and begin processing. 
• Depending on the number of image files and 2K/4K resolution the automation will take anywhere from 10 seconds to 10 minutes. A 200 frame insert takes about 20 seconds to process.
• You can track the progress here
  • Burbank:
    10.100.110.167/cf-web-ui/render
  • London:
    10.110.130.98/cf-web-ui/render

• Once the rendering completes, your render job will be marked as complete and your PXLVIS image files will appear in the "output" folder.
• The output folder will be named the same as your input folder. 

• If you click into your folder, you'll see your image files are named the exact same as your source files. Expect the automation adds "_pxlvis" to end of your files before the frame number. The frame number will match your source DCDMs.
  • Even if you have 4 different image sequences within one folder, the automation will match your source frame number correctly and apply it to the PXLVIS output. 

• Move your PXLVIS folder to its final storage place

• IMPORTANT: The automation does have not remove your source files out of the "input" folder. Please make sure you delete/remove your input folder before continuing on. Failure to do so, will result in unnecessary storage. 

   

3.  Final Steps

• Check your PXLVIS images in TKD to confirm the PixelVision pipeline was applied. A/B your source DCDMs vs the PXLVIS DCDM
• Your PXLVIS image files are now ready to be ingested or used in DVis DCP.