2020.1 / 21.7 - Octane tag issues

[ChrisH]

I have two (small) issues with the Octane file tags:

1. When there's a dot in the tag, the dot and anything after it will be removed in the final filename. Of course you can just not use a dot, but sometimes a dot is preferred over other separators. (Dots work fine when used in the Output path)

2. The "postfix" becomes a prefix in the layer/pass names in the EXR file.

(Side note: It would be nice with the option to not include the filename in the layer/pass names [they can become pretty long and the "pass id", the most interesting info, comes at the end, and might be hidden by the editor], it would also be nice to have the option to not include the frame [when you're just rendering stills] in the file name and/or pass name)

[linograndiotoy]

Dots should only be use to separate a file name from its extension. It's a general and very important rule of the Matrix!

[ChrisH]

Is that you Morpheus?? Can you get me out of here‽
(Also I didn't realize that the Matrix ran on CP/M 1.0! )

I like to use dots to "tag" my files with things like color space, bit depth and such (it's more connected to the file type than the file name), which is usually not a problem (the filenames are valid according to the OS [a filename like ...txt is valid] and I haven't found an application yet that have problem opening them..).

What about #2?

[J.C]

Another issue with file naming is that it adds frame number in the middle of file name eg.
scene_frameNumber_passName.extension

while in most cases it is:
scene_passName_frameNumber.extension

or it should be adjustable like it is done in Standalone using name patterns %f, %p etc.

[pegot]

+1 for a bit more flexibility in the naming conventions and use of patterns.

[linograndiotoy]

I agree it should be totally flexible.