Hi @ferdinand ,
Thanks for the clarifications. I had originally asked maxon support and referenced the original post as a source and they recommended I just post on the forum my questions. I'll take a look at the guidelines for future postings.

The frame padding I was referring to are in regards to the frame numbering that is written out when selecting a render pattern in the output settings that you would find under Render Settings > Save > Name where the one we typically use is Name.0000.TIF.

Based on how you answered my questions it sounds like as long as I load the plugin script that contains the registration code that I could create custom tokens that way. I can also therefore create my own $frame token with my own frame padding (python str.zfill method) for frame numbers however there is no way to override the 4 digit frame padding that comes from the render settings name field. Best case where we use that custom token is we'd have duplicate frame numbers in the final output filename where our custom $frame token will have our custom frame padding numbers and the frame counter that's only 4 digit padding since there doesn't appear to be any setting under Render Settings > Save > Name that doesn't include the frame counter.

Based on your example you gave I would end up with (my_render_frame-000001_001.tif, my_render_frame-000002_002.tif, etc.) if I used the Name000.TIF template and had my own custom $frame token I used in the output filepath.

I've got a script that can address the frame padding for when our shots cross the 10000 frame mark after the renders complete which I suppose I can look into the postprocessor hook you mentioned but was hoping there might've been some way to avoid having to do any post processing.

Thanks again for all the information.

Hello,

I'm looking into implementing 4 to 6 digit frame padding depending on the project an artist is currently assigned to. We would need to have it work both locally on a workstation and on our render farm machines. If I'm understanding the previous posts correctly we would have to override the default $frame token handler since that is what I assume is being used by c4d's output render settings.

Some questions I had are assuming that's true are:

1. Do the token registrations get stored within the project files themselves or do they get stored in local machine or user settings for c4d. Meaning that if we wanted to implement this for our render farm we'd have to register the token on each one of the machines.
2. Depending on how 1 is answered is it possible to support multiple $frame padding configurations?
3. Also depending on how 1 is answered, are the token registrations permanent or are we going to have to register the custom token every time we launch c4d or whenever we want to change it.