docs: Add Cinema 4D Tile Rendering support doc - #260
Conversation
Signed-off-by: Lagos Gonzales <214008711+gianelli-lagos-aws@users.noreply.github.com>
| ### Platform Compatibility | ||
|
|
||
| * Tile rendering works on both Windows and Linux environments | ||
|
|
There was a problem hiding this comment.
Instead of multiple headers with a single bullet point in each, can we just have one list of supported flows (OS platforms, multi-pass, multiple output types, file formats), and then one list of unsupported flows (Redshift camera, render tokens).
Also, do we support the Redshift renderer when a physical camera is used? That's a pretty easy workaround to still support Redshift even if Redshift cameras don't work.
For the specific instructions about multi-pass outputs, can we just include them in the step by step instructions?
There was a problem hiding this comment.
I agree, I will see how I can improve the layout there.
I will check to see if we support the Redshift renderer when a physical camera is used and let you know!
I also agree that the multi-pass output instructions can go in the actual instructions. Thank you!
| * Set "Tiles per Axis" (between 2-5, where 5x5 creates 25 tiles) | ||
| * Set "Reference Camera" by dragging your default camera to this field | ||
| * Check "Use Tiling" to enable tile rendering | ||
| *  |
There was a problem hiding this comment.
nit: does it look better if images are outside the bullet points i.e. unindented?
There was a problem hiding this comment.
Yes! I will update it.
|
|
||
| #### Configure Render Settings | ||
|
|
||
| 1. Go to "Render Settings" and set "Renderer" to "Physical" |
There was a problem hiding this comment.
Similar note as above - it would be great if we could use Redshift, just with a physical camera
There was a problem hiding this comment.
Yep, I will look into it!
| *  | ||
| 3. In the "Save" tab: | ||
| * Set the file path to your desired output folder | ||
| * Choose either "REGULAR IMAGE" or "MULTI-PASS IMAGE" |
There was a problem hiding this comment.
Yep! I will update it.
|
|
||
| * If you select both "REGULAR IMAGE" and "MULTI-PASS IMAGE" as save options: | ||
| * Both outputs will be stitched separately, resulting in two final images | ||
| * File naming is critical: ensure regular image filenames alphabetically precede multi-pass filenames |
There was a problem hiding this comment.
Can we share an example here? Also is there a reason why regular image filenames should always precede multi-pass filenames?
There was a problem hiding this comment.
Yes, i can add an image of the outputs in the case both are selected. Regular image filenames should always precede multi-pass filenames because the first files are expected to be regular outputs since stitching OutputPath goes first and then MultiPassPath goes.
| 2. In the "Output" tab: | ||
| * Set "Frame Range" to Manual | ||
| * Set "From" to 0 | ||
| * Set "To" to (number of tiles - 1) | ||
| *  |
There was a problem hiding this comment.
Hmm, the submitter would be calculating this no?
There was a problem hiding this comment.
Yes, I need to update this doc with that information after writing the code. Thank you!
| ### Access Results | ||
|
|
||
| 1. Once the job completes, download the output | ||
| 2. Open the output folder to find the "stitched_output.tif" file containing your final rendered image |
There was a problem hiding this comment.
Is the name of the stitched output always "stitched_output"? Regardless of the name of the actual output files?
There was a problem hiding this comment.
Yes, there could either be "stitched_output" or "stitched_multipass" or both. Currently, I do not take into consideration the names of the files.
There was a problem hiding this comment.
Hmm, maybe we should mention "stitched_multipass" too (if customers are using multipass)
There was a problem hiding this comment.
Oh okay! Yes.
Signed-off-by: Lagos Gonzales <214008711+gianelli-lagos-aws@users.noreply.github.com>
f6bf03c to
6b2efb5
Compare
|
|
||
| When you enable tile rendering, the submitter automatically: | ||
| * Adds `conda-forge` to the Conda channels | ||
| * Adds `ffmpeg` to the Conda packages (required for tile stitching) |
There was a problem hiding this comment.
Can you describe what ffmpeg is?
There was a problem hiding this comment.
Hello! Yes I can add that information, thank you! :)
Signed-off-by: Lagos Gonzales <214008711+gianelli-lagos-aws@users.noreply.github.com>
Signed-off-by: Lagos Gonzales <214008711+gianelli-lagos-aws@users.noreply.github.com>
karthikbekalp
left a comment
There was a problem hiding this comment.
Few nits now that we have confirmed that we are able to render with Redshift renderer as well.
|
|
||
| ### Current Limitations | ||
|
|
||
| * Using a Redshift renderer and camera |
There was a problem hiding this comment.
I believe using a Redshift renderer is no longer an issue?
There was a problem hiding this comment.
Yes, I need to update this! Thank you.
|
|
||
| #### Configure Render Settings | ||
|
|
||
| 1. Go to "Render Settings" and set "Renderer" to "Physical" |
There was a problem hiding this comment.
I believe this is no longer a requirement now that we have confirmed that it works with Redshift renderer too on a Physical camera?
Also, can you double check if all the different render engines work? Physical, Standard etc with this feature?
There was a problem hiding this comment.
Yes, I need to update this and I will test the other renderers. Ty!
| #### Set Up Camera | ||
|
|
||
| 1. Add a default camera object to your scene | ||
| 2. Ensure the camera is using the Physical renderer |
There was a problem hiding this comment.
I think we don't need this anymore?
There was a problem hiding this comment.
Yep! It must be physical camera.
| ### Access Results | ||
|
|
||
| 1. Once the job completes, download the output | ||
| 2. Open the output folder to find the "stitched_output.tif" file containing your final rendered image |
There was a problem hiding this comment.
Hmm, maybe we should mention "stitched_multipass" too (if customers are using multipass)
| 1. Once the job completes, download the output | ||
| 2. Open the output folder to find the "stitched_output.tif" file containing your final rendered image | ||
|
|
||
| **File Size:** The final stitched image maintains the same dimensions and file size as a normal render - tile rendering doesn't affect the final image quality or size, only the rendering process. |
There was a problem hiding this comment.
I wonder if we need this line or maybe we should add this to the "what is tile rendering" section?
There was a problem hiding this comment.
I think adding it to the "what is tile rendering" section would be better! Ty!
|
|
||
| ### Supported Features | ||
|
|
||
| * Job submission is supported from Windows and Mac workstations |
There was a problem hiding this comment.
Maybe we want to mention that these are the instructions for SMF and not CMF?
Because it will only work on CMF if customers have already installed ffmpeg?
| ### Current Limitations | ||
|
|
||
| * Using a Redshift renderer and camera | ||
| * Adding Render Tokens to the output paths |
There was a problem hiding this comment.
Discussed offline about this, we should be able to fix this with a regex
There was a problem hiding this comment.
Yes, that will be a follow up after this version is completed.
Signed-off-by: Lagos Gonzales <214008711+gianelli-lagos-aws@users.noreply.github.com>
66a6049 to
7829985
Compare
|



Fixes: #210
This PR is related to #256.
What was the problem/requirement? (What/Why)
Add doc that explains how to use tile rendering.
What was the solution? (How)
Added a doc that contains the instructions on how to use tile rendering in Cinema 4D.
What is the impact of this change?
Customers will be able to use tile rendering.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.