Early tests here, but on OSX, the C4D Submit plug-in doesn’t seem to properly read the frame range to be rendered – always comes back with the full range of the scene.
This seems like it could be problematic. Is it a known bug or am I doing something wrong?
–Rob
I checked the code, and we’re getting the start and end frame from the scene’s min/max time, which I guess always represents the full range. So I guess this is more of an oversight than a bug. 
We can see if we have time to deal with this before 5.1 is released. It’s scheduled for next week, so I can’t guarantee anything. The workaround for now would be to modify the frame range in the submitter prior to submitting.
Cheers,
Thanks, Ryan. Yeah, C4D Render Settings has a selctor - All frames / current frame / manual range.
Manual is the most often set parameter, and since we need to be in that dialog to set output filenames, etc. it makes sense to just honor the setting in there.
Thanks!
–Rob