-
Notifications
You must be signed in to change notification settings - Fork 47
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
CoreMediaIO.CMIOObjectSetPropertyData ValueError #554
Labels
bug
Something isn't working
Comments
Same error( |
This is due to incomplete metadata. I'm working on a fix (starting with updating the test that should have detected this problem...) |
ronaldoussoren
added a commit
that referenced
this issue
May 13, 2023
Also add an extra check for the generic metadata sanity check that would have detected this problem (sadly only for functions and not selectors because the test gives too many false positives for selectors). Also exclude definitions from "CMIOHardwarePlugIn.h" from the CoreMediaIO bindings (those never worked and cannot work without a lot more work) Issue #554
I've pushed a fix for this issue. I'm not sure yet when I'll push out a release with this fix, my plan was to wait for the 3.12 beta release, but that's been postponed so I may release sooner than that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Attempting to call CMIOObjectSetPropertyData() raises a ValueError exception:
CMIOObjectGetPropertyData() works fine on the same objectID.
In CoreMediaIO/_metadata.py, I see:
and in the same file:
The two functions have the same signature except for the second to last argument.
I just copy-pasted the tuple for CMIOObjectGetPropertyData into CMIOObjectSetPropertyData, and the exception is gone, it seems to work now.
Platform information
To Reproduce
See here: https://gist.github.com/eliteraspberries/0c26993bc82f7b62056cff1733ebfba8
Expected behavior
CMIOObjectSetPropertyData() should return non-zero (fail).
Additional context
The text was updated successfully, but these errors were encountered: