It looks this this would only happen if you had a decimal framerate, like 23.75fps where 24fps would have no issues.
Unless 2023.2 now has fractional frames? I’m not seeing anything in the release notes to suggest that.
Attached is a copy of SubmitC4DToDeadline.py that forces the framerate to be an integer when calculating the start and end frames.
SubmitC4DToDeadline.py (197.7 KB)
All I’ve done is force the variable to an integer like this:
startFrame = renderData.GetTime( c4d.RDATA_FRAMEFROM ).GetFrame(int(framesPerSecond) )#jusbla casting fps to int
It’s untested and I think there’s a chance that number rounding will cause a frame and the beginning or end of tasks will be missed. So please do make a backup of the existing C:\DeadlineRepository10/submission/Cinema4D/Main\SubmitC4DToDeadline.py file before you use this one.
Let me know how it goes, and pay close attention to the tasks’ frame ranges. 