Bug: Takes submitted to Deadline Cloud all render with Main take's frame range instead of their individual frame ranges

[vaish-gujjari]

Describe the bug

When submitting Cinema 4D scenes that use Takes to Deadline Cloud, all takes are rendered with the same frame range/duration as the Main take. The submitter does not respect the individual time/length settings configured on each take, causing incorrect render output for any take whose duration differs from the Main take.

Expected Behaviour

Each take should be rendered using its own configured time/length (frame range). The submitter should read the frame range from each individual take and pass the correct duration to Deadline Cloud, so renders match what you'd get rendering locally in Cinema 4D.

Current Behaviour

All takes are submitted to Deadline Cloud with the same duration as the Main take, regardless of the individual frame range set on each take. This means takes that are shorter or longer than the Main take get rendered with the wrong frame count.

Reproduction Steps

1. Open Cinema 4D and open a scene with multiple Takes.
2. Set different frame ranges/lengths on each take (e.g., Main take: 0–100, Take 2: 0–50, Take 3: 0–200).
3. Submit the scene to Deadline Cloud with all takes selected.
4. Observe that every take is rendered with the Main take's frame range (0–100 in this example), instead of each take using its own configured range.

Environment

At minimum:

1. Operating system - Windows, Linux
2. Version of Cinema 4D: 2025
3. About panel:

submitter_name: Cinema4D
submitter_package_name: deadline-cloud-for-cinema4d
submitter_package_version: 0.9.2
host_application_name: Cinema 4D
host_application_version: '2025303'
additional_info:
    release_date: December 18, 2025
deadline_dep_versions:
    deadline: 0.54.0
    boto3: 1.42.13
    click: 8.3.1
    psutil: 7.2.2
    pyyaml: 6.0.3
    qtpy: 2.4.3
    typing-extensions: 4.15.0
    xxhash: 3.6.0
    pyside6-essentials: 6.10.2
os_name: macOS
os_version: '26.2'
os_architecture: arm64
python_version: 3.11.4
qt_version: 6.10.2

[karthikbekalp]

This issue may have been already fixed.