Title: Camera binding ("Bind Camera to Markers") is not respected when "All renderable cameras" option is used or when default camera is locked

[fast-blender-add-ons-dot-com]

Title:
Camera binding ("Bind Camera to Markers") is not respected when "All renderable cameras" option is used or when default camera is locked

Body:

Issue Summary
When submitting render jobs via the AWS Deadline Cloud Blender submitter, camera switches driven by "Bind Camera to Markers" are not respected. The render stays locked to the camera set by the marker at the initial frame, even when a marker later in the sequence should change the camera.

Expected Behaviour

Expected Behavior
Camera switches should occur per frame as driven by markers—blender-cli render (-a) behaves correctly in this regard.

---

Current Behaviour

Actual Behavior
The submitter appears to bake in the camera at the first frame of job submission and fails to re-evaluate markers per frame. Even selecting "All renderable cameras" does not work as expected—camera stays stuck.

Reproduction Steps

Steps to Reproduce

1. In Blender, set up timeline markers bound to different cameras.
2. Prepare the scene so that the initial frames are using Camera A, and after a specific frame the marker binds to Camera B.
3. Submit the job using Deadline Cloud Blender submitter, choosing either:
   • "All renderable cameras", or
   • the default option (which appears to lock the scene’s current camera).
4. The farm render only ever uses Camera A, even on frames after the marker.

Environment

Environment

• Submitter version: v0.5.5
• Blender versions tested: 4.5 (also earlier versions)
• Platform: Windows (but likely affects other OSes too)

[fast-blender-add-ons-dot-com]

Did anybody get a chance to see this, it seems like a big company like Amazon would have this monitored constantly... just a little heads up because you know of course everybody wants to see you guys be successful

[edwards-aws]

Thanks for reporting this issue! I was unable to reproduce this on Blender 4.2. I'll try again with Blender 4.5 and report back.

[edwards-aws]

Here's my timeline that I used

The images that were rendered swapped between the cameras as expected. The All Renderable Cameras option is weird here because it gives you more frames than you need. The workflow also isn't intuitive because the dialog asks for a camera, but really we want Blender to choose the camera. All of the output files also have the name of whichever camera was selected, which isn't what I would expect.

I'll talk to the team about how we can improve this workflow.

[fast-blender-add-ons-dot-com]

Yeah this happened with your latest version that I got on the releases page that's been upgraded to Blender 4.5 and that's the only place i'm trying this on is blender 4.5... And thanks for getting back in touch so quickly!

[fast-blender-add-ons-dot-com]

And thank you very much for analyzing the issue and being prepared to fix it...I really appreciate that you're standing behind your products.... I use this every day and because I fully support your ecosystem I'll report back anything I see that's weird immediately.