CueSubmit: Chunked Blender render renders the same frame

[Tilix4]

Describe the bug
Submitting a chunked job for blender renders the same frame as many times as the chunk size instead of rendering a range.
The built command is blender -b -noaudio /path/to/file.blend -f 1

To Reproduce
Steps to reproduce the behavior:

1. Open CueSubmit
2. Prepare a layer with Blender
3. Set chunk size to 10
4. Submit

Expected behavior
A chunked submission should render a frame range, such as:

• Clean range command: blender -b -noaudio /path/to/file.blend -a -s 1 -e 10
• Brute force chunk command: blender -b -noaudio /path/to/file.blend -f 1 -f 2 -f 3 -f4 ...

Version Number
0.22.24

[n-jay]

@bcipriano could you assign me to this? Would like to work on it.

[n-jay]

Hi @Tilix4
I'm personally not very familiar with the industry terminology, so could be wrong. I think frame ranges for animations run via Blender render commands can be extracted from the "Frame Spec" field in CueSubmit.
Got a bit of a hint from the tooltip text

OpenCue/cuesubmit/cuesubmit/ui/Frame.py

Lines 27 to 39 in fe519e3

	"""Widget for entering a frame spec."""
	helpText = 'Enter a FrameSpec value.\n' \
	'A frame spec consists of a start time, an optional end time, a step, ' \
	'and an interleave.\n' \
	'Multiple ranges can be added together by separating with commas.\n' \
	' Ex:\n' \
	' 1-10x3\n' \
	' 1-10y3 // inverted step\n' \
	' 10-1x-1\n' \
	' 1 // same as "1-1x1"\n' \
	' 1-10:5 // interleave of 5\n' \
	' 1-5x2, 6-10 // 1 through 5 with a step of 2 and 6 through 10\n'

Sent a draft PR with a fix. Will finalize after I've tested and validated it.