Skip to content

fix(sequence): correctly detect padding for frames with no leading zeros#245

Closed
VIKASKENDRE wants to merge 1 commit intoAcademySoftwareFoundation:developfrom
VIKASKENDRE:fix/sequence-padding-detection
Closed

fix(sequence): correctly detect padding for frames with no leading zeros#245
VIKASKENDRE wants to merge 1 commit intoAcademySoftwareFoundation:developfrom
VIKASKENDRE:fix/sequence-padding-detection

Conversation

@VIKASKENDRE
Copy link
Copy Markdown
Contributor

@VIKASKENDRE VIKASKENDRE commented Apr 20, 2026

Summary

Fixes #152

  • pad_size() returned 0 when a frame number's natural string representation matched its string length (e.g. "1000"to_string(1000) == "1000"), indicating "no leading zeros" but incorrectly treating it as unknown/zero padding
  • This produced {:00d} URIs for sequences like shot.1000.exr, causing xSTUDIO to fail loading all frames after the first with Unsupported file type warnings
  • Fix: the padding width is always the length of the frame string, regardless of leading zeros — simply return frame.size()

pad_size() returned 0 when the integer's natural string representation
matched the frame string length (e.g. "1000" -> to_string(1000) == "1000").
This produced {:00d} URIs for sequences like shot.1000.exr, causing all
frames to fail loading after the first.

The padding width is always the length of the frame string regardless of
whether leading zeros are present, so simply return frame.size().

Fixes AcademySoftwareFoundation#152
@VIKASKENDRE VIKASKENDRE deleted the fix/sequence-padding-detection branch April 20, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant