-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] py_oiio::attribute_typed() doesn't handle tuples #2275
Comments
I'll take a look, thanks for the alert. (And thanks for the repro script -- this makes it so very much easier for me to get started tracking something like this down.) |
Thanks! Hope it's not a wild goose chase. |
Legit bug. Fix proposed as #2279. |
Sweet! Thanks! |
Your fix works like a charm! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
For a while now I've been unsuccessful in adding TimeCode to EXR's through python. In my quest to achieve this I've been digging around in the code and discovered what might be the reason. It seems that
attribute_typed()
only supports int, floats and strings. In other words, when passing a tuple which is required for "non-standard" attributes there's nothing to handle them.Here are a couple of links to my findings: (Please note that I might be barking up the wrong tree here, but seems a bit off)
When passing a tuple to attribute_typed()...
...nothing catches the tuple and handles it
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Get an image with the TimeCode passed
Evidence
Platform information:
IF YOU ALREADY HAVE A CODE FIX: There is no need to file a separate issue,
please just go straight to making a pull request.
The text was updated successfully, but these errors were encountered: