Page 1 of 1

FIle output question

Unread postPosted: Tue Nov 20, 2018 7:51 am
by jeff_bartzis
Hey, this might be a dumb question, but is there a way to disable the addition of frame numbers to rendered images?
I've looked around the forum and google but cannot find how to turn this off .. Aside from doing a batch re-name after the fact, but that just increases the amount of work I will have to do with a potentially large volume of images.

Re: FIle output question

Unread postPosted: Tue Nov 20, 2018 9:26 am
by mdkai
Hi Jeff,

I'm not sure if there some single picture mode like in maya where frame padding is ignored.

However how would you like to output multiple frames without a frame padding ?
Currently clarisse does not support custom render path flags which could help sorting issues like this ...

I guess you may be able to render something based on a python script but not sure how frame padding would be skipped.

Re: FIle output question

Unread postPosted: Tue Nov 20, 2018 9:41 am
by dboude
Hi,

No, you can't remove the frame number from a rendered file. However, you can set the padding with # key.

my_image_###
my_image_#
####_my_image
...

Cheers ;)

Re: FIle output question

Unread postPosted: Tue Nov 20, 2018 9:49 am
by bvaldes
Hi,

Through python there is no frame padding added to the output file. You can find a really simple example to render and image with python:

python code

# The function compute image compute the current frame so you have to set the frame before launching the render:
ix.set_current_frame(0)
computed_image = ix.render_image("project://scene/image") # this function compute and image but do not write the data to the disk
# To write the data to the disk you have to use a save_xxx function or the save_image function with the format in parametter:
ix.save_exr16(computed_image, "output", "sRGB") # The first arg is the computed image, the second is the output path and the third is the LUT
# Same example with the save_image function
ix.save_image(computed_image, "output", "exr16", "sRGB") # first and second arg are the same, the third is the format and the last is the LUT

Re: FIle output question

Unread postPosted: Tue Nov 20, 2018 5:56 pm
by jeff_bartzis
Once again thank you all for the awesome suggestions.

Essentially I'm generating a bunch of image assets for use in a game. and each asset will have multiple different layouts and different variations per layout. So I set up a bunch of different user variables with the variable editor to use in the file name, to help with filename parsing later on. Essentially my problem was that I just didn't like how the frame padding added extra, unnecessary info. Though, it wasn't a major issue really - easy enough to batch rename, after the fact, in bridge or something.

Though, dboude, I did not realize you could shorten the number with the use of hashes. Should have been obvious as this is pretty standard (all those years of using nuke, and I totally forgot, haha). Anyway, this brought up an idea to use animated geometry and render out 3 frames with the different states of the geometry. In the end, I think this will save me time, rather than have multiple different images for each state. I think this is a more procedural solution. So thank you for that!

And bvaldes, Cheers! This looks like another great alternative solution. Python is a bit outside of the scope of my capabilities at this point, even with the clear comments in there. Not that I wont experiment with this later on or anything. For this particular project I'm dealing with hundreds of different images for various states of different assets and I wish I took the time to learn python years ago!

Anyway, thanks again all for the great help!