-
Notifications
You must be signed in to change notification settings - Fork 78
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
"Bad magic number" error on known valid OpenEXR files #140
Comments
@scottdyer I think you can use homebrew to build/install from the master source branch by adding the
I will look into adding automatic version info to the ctlrender usage, that's a great idea. Let me know if build/install using |
I confirmed that your test command/file using ctlrender installed with |
After clearing everything out again and reinstalling using |
Should the current |
@aforsythe I just published release tag |
I found the ctl homebrew formula on github, it looks like it has already picked up the ctl-1.5.3 tag release |
Just installed from |
Finally managed to get ctlrender to run without an iexDebug error, but now am getting an old error where valid OpenEXR files are not recognized and so no image processing takes place.
To be fair, this might be related to an old version of ctlrender since I had to resort back to the old brew formula install for it to run. Is there a way to check version on ctlrender?
% ctlrender -ctl ~/aces-dev/transforms/ctl/utilities/ACESutil.Unity.ctl SonyF35.StillLife.exr ~/tmp/testout.exr
I now recall this error is perhaps why I went back and tried to reinstall everything from source, but then of course I was getting the iexDebugtrap error.
Any recommendations on how to get rid of whatever linked files are causing the install from source to not work? Or, how I might get around this error when using the install from homebrew?
The text was updated successfully, but these errors were encountered: