Skip to content

Conversation

@mwoehlke-kitware
Copy link
Member

Adjust stride computation in image to texture conversion. We want strides reported in bytes, and our logic to check for valid strides is based on the same, however KWIVER reports strides in increments of the value type. This was fine for 8-bit images and seems to have been working by accident for single-channel 16-bit images, but was causing the stride check to incorrectly reject some multi-channel 16-bit images.

Adjust stride computation in image to texture conversion. We want
strides reported in bytes, and our logic to check for valid strides is
based on the same, however KWIVER reports strides in increments of the
value type. This was fine for 8-bit images and seems to have been
working by accident for single-channel 16-bit images, but was causing
the stride check to incorrectly reject some multi-channel 16-bit images.
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