-
Notifications
You must be signed in to change notification settings - Fork 6
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
Error Processing DaVinci CTL #2
Comments
That’s odd. It should work with either in theory, although there are some fun bits around the wretched landscape known as shaders. Are you able to find the Resolve log and find the error that it dumps? |
Extracted some bits that seemed related... Hope this is usefull... In the meantime I tried deleting the OpenCL cache to force a recompile with no effect... Thanks for taking the time! |
Thanks for taking the time to trace the log. My rule of thumb is ignore all errors except for the very first one, which is this rather reasonable looking snippet: That’s this line here. Now this particular line is interesting because the compiler seemed to handle the earlier line perfectly fine, and it is very similar. But a hint is that it is not quite identical in structure. If you look right toward the end of the line, you will see that there is a subtle whitespace between the So, try adding a space between that colon and the y on the problematic line, save, and reload. If it still flakes out, the compiler is probably tripping up on those ternary operators, and we’d need to dig a little deeper. |
Unfortunately, it still errors out... I'd be more than happy if you could give me another pointer where to look next. Thank you! |
What were the errors in the log? |
Fixed it! Replaced lines 702, 703, 764, 765, 844, 845 with this:
Works like a charm now. Thanks! PS: I have never created a pull request before, so it will take me a while till I have the time to sit down and figure out how to do that correctly, if u want me to. |
I am happy to integrate a pull request. The easiest way is to fork the branch locally using git, and then push back to your GitHub. In the GitHub interface, you can create a pull request. The code is a bit of a hodge podge from Jed Smith’s original blueprints I believe, which Juan Pablo Zambrano added and modified to cram the whole AgX-like bits into. I kludged in my garbage on top of that, and set the tunings to default for a reasonable AWGv3 / LogCv3 chain. I have a significantly cleaner attempt from the ground up, but it is unfinished and I have not pushed it. I’d like to eventually do so as a historical marker for the next thing that I hope to squeeze out, Flying Spaghetti Monster willing. TL;DR: I am happy to take a PR given this is a bit of a shibboleth. |
getting the same error
|
I will try to find a timeslice to fix the ternary operator to generic shader code. I really should muster up the willpower to get the streamlined DCTL done, with HDR bullshit. Le sigh. |
Hi sobotka,
thank you for the AgX DCTL.
Unfortunately Resolve is throwing an error for me when I attempt to use it:
"Error Processing DaVinci CTL"
I created the AgX folder in LUTs with the two files and set up a CST to output ArriWideGammut3 as instructed
Might there be an issue using OpenCL instead of CUDA?
Im just interested in playing with AgX in Resolve as a final transform after my grades.
If you have an idea how to fix this I'd be most greatful.
Either way, awsome work with AgX! <3
Thank you!
The text was updated successfully, but these errors were encountered: