OTOY Forums

i find i difficult to render file sequences from octane standalone as the script uses the first set of numbers it comes across instead of the last as the frame numbers, i would like to understand the file naming convention that will allow me save files with version numbers and project names that include numbers

e.g
"shot 001_v01_0000.png"

I have the same problem, so for now I use words instead of numbers except for the sequence #

Yes, problem already present in 1.5x.

@ file squence naming pattern

It seems important that the file sequence works with 0 in front of the numbers so the sequences can be properly imported into 3rd party software like video editing.


001
0001
00001
000001
0000001

- - -

Option 1
The user can manually select how many digits the numbers consist of in the preferences.

Option 2:
The software calculates how many digits are needed based on the total frame numbers of the sequence.


For some projects it might be useful if the user can set any start number he wants.

Example:

Instead of starting at 000001 the sqeuence starts at 00543.

- - -


@ more automatic created file name options

In general I would welcome addtional automatic file naming options that are added to any image sequence.

Bascially the final file name should be generated based on some manual entries the user makes and some automatic variables the user selected in the multipass rendering options.

- Scene Name (SCENE NAME)
- Resolution (WIDTH x HEIGHT)
- Samples per Pixel (VALUE spix)
- Kernel (DL, PT, PMC, INFO)
- Multipass (a = ALPHA, z = ZDEPTH, w = WIREFRAME, SURFACEID, SURFACENAME, OBJECTID, OBJECTNAME etc.)
- Framenumber (XXXXXXXX)

In that case the resulting automatic file name would be:

SCENE NAME_WIDTH x HEIGHT_VALUE spix_INFO_a_XXXXXXXX.png

- - -

The variables that identify different multipasses are automatically added to the file name. If those Variable would not be added multiple passes would all have the same name and overwrite each other.

The optional parts of the file name like resolution, Sample per Pixel, Kernel are only added to the file name when the user selects them. A menu with square boxes to add a checkmark seems conveniant to quickly add the most common options.

- - -

Example:
The user selects in the multipass rendering options to

- render the main image: car and background

- a separate alpha BW mask of the car without the background
(this is needed to quickly composite special effects around the car without affecting the background)

- the z-depth channel
(this is needed to quickly alter depth of field effects in postproduction)

- a surface mask of only the car front window
(this is needed to quickly add special effects like alternative reflections in postproduction)


For that example the result are:

Name of the rendered image:

prototypecar_3840x2160_4000spix_PMC_0000001.png

Name of the BW Alpha mask image:

prototypecar_3840x2160_4000spix_INFO_a_0000001.png

Name of the z-depht mask image:

prototypecar_3840x2160_4000spix_INFO_z_0000001.png

Name of the car front window surfacemask

prototypecar_3840x2160_4000spix_carfrontwindow_0000001.png

- - -

I guess we will see some of those features when multipass and cloud rendering are ready and more users are moving on the rendering animations.

About naming frames, I have not checked recently if it has been fixed, but an other problem that I encountered is that if you want to render again just a part of your animation to fix a problem you saw in your rendered sequence , if you choose to render again only frames 153 to 260 for example, the rendered frames are actually named from 1 to 107 ! This leads to overwrite the original frames 1 to 107 which were good !

yeah, not being able to continue renders from a specific frame does not help very much either

in, the animation script works with naming, you can have it start with the number you want.

And in 1.5x you can use the "render animation G" plugin found in the LUA forum which fixes the naming problem also.

And in 1.5x you can use the "render animation G" plugin found in the LUA forum which fixes the naming problem also.

Interesting, Thanks ! I will have a look at that.