OctaneRender™ 2019.2 XB2 [latest 2019.2.x]

[Notiusweb]

2019.2 XB2

Tell me what the heck I did wrong here, because this looks like a stupid bug:

I rendered frames 1-900, and I wanted to re-do 260-360. So I did the following, thinking it would only render the 100 frames, but number them starting at 260, as opposed to 0:

But, so what does it then do!!!!?....it added my start frame of 260 to the file number start of 260...
260+260 = 520...
So it started at timeline-frame 260 and overwrote file number 520, and ended with timeline-frame 360 and overwrote file number 620.
You can see I screen captured right as it rendered the last frame as 620, but it was 260 to 360 on the frame timeline.

It overwrote completely the wrong 100 frames!

Shouldn't it start at 260, because that's where I told it to start at?

Thanks.

[Notiusweb]

Q: Is BATCH RENDERING in the manual?
A: NO

[Notiusweb]

This is definitely a bug-

If I render starting at frame 260 and set file number of "0", it starts the file numbering at 260.

So, how then would I run timeline frames 260-360 with a file number start of "0" then...
Right!!!? you can't then


It should be that file number overrides frame number in file name.
Say that fast 20 times!

[grimm]

Hi Notuisweb,

Not really a bug, the script doesn't have a function for what you want to do. A field for the start of numbering would have to be added to do what you need. I have modified the script here to do what you want, give it a try and see if it works for you.

BatchRenderingOverrideOutput.lua

(48.28 KiB) Downloaded 221 times

I have only tested it on Octane V4 so it might not work on later versions, YMMV.

Jason

[divasoft]

Crush Crush Crush and Crush again.
5 crushes for 10 minutes. It's my usual work process with C4D octane.
https://drive.google.com/open?id=1tVFU1 ... Fv44BQwJjl

[Notiusweb]

Hi Notuisweb,

Not really a bug, the script doesn't have a function for what you want to do. A field for the start of numbering would have to be added to do what you need. I have modified the script here to do what you want, give it a try and see if it works for you.

BatchRenderingOverrideOutput.lua

I have only tested it on Octane V4 so it might not work on later versions, YMMV.

Jason

Hi Jason, thank you very much for thoughtfully giving your insights on my post and also for going out of your way to create a lua script!
I very much appreciate this, this was very generous of you to offer your time and expertise here.
I am impressed with your lua script - it works in 2019.2 XB2, and can accomplish the override I had envisioned, as you noted.
Very cool, and many thanks!

[Despot]

Crush Crush Crush and Crush again.
5 crushes for 10 minutes. It's my usual work process with C4D octane.
https://drive.google.com/open?id=1tVFU1 ... Fv44BQwJjl

You're not alone Divasoft, I'm getting similar behaviour with occasional crashes to the desktop.

[jobigoud]

This is definitely a bug-

If I render starting at frame 260 and set file number of "0", it starts the file numbering at 260.

If I understand correctly the file numbering field is interpreted for the whole animation. As an offset to the whole, in case you want to start numbering at 1 for example. So unless you have a very specific need it should always be set to 0 (or 1) and never touched after that. In your case just leave it at 0, tell the script to redo 260-360 and it should just work. In other words, don't touch that field after you set it initially, it describes the numbering scheme of the whole sequence.

[grimm]

This is definitely a bug-

If I render starting at frame 260 and set file number of "0", it starts the file numbering at 260.

If I understand correctly the file numbering field is interpreted for the whole animation. As an offset to the whole, in case you want to start numbering at 1 for example. So unless you have a very specific need it should always be set to 0 (or 1) and never touched after that. In your case just leave it at 0, tell the script to redo 260-360 and it should just work. In other words, don't touch that field after you set it initially, it describes the numbering scheme of the whole sequence.

Thanks jobigoud,

I re-ran the test that I did with a simple animation and the output frame numbers were not overridden with the new sequence. All I did was set the start frame to 20 and the end frame to 40, then I selected the "Start file numbering at:" and left the File numbering at 0. When I started the render the output file numbering started at 20, and looking at the code, it looks like the File numbering is ignored. So I was wrong in my initial thoughts, it does look like a bug.

Jason

[grimm]

Hi Jason, thank you very much for thoughtfully giving your insights on my post and also for going out of your way to create a lua script!
I very much appreciate this, this was very generous of you to offer your time and expertise here.
I am impressed with your lua script - it works in 2019.2 XB2, and can accomplish the override I had envisioned, as you noted.
Very cool, and many thanks!

No problem, it was a really simple modification, in fact about the least I could do to get it to work. This means there are limitations with the script, in that it will always start the frame numbering at 0, you can't change it. To fix it correctly a lot more coding would be needed.

Jason