Dehancer Pro 3.4.1 (Mac)

Amazing! Thanks a lot!!!

 

Just curious, I've tried running the installer (Intel) AND THEN the Terminal code (without opening Resolve) but when I do open resolve I get:

Dehancer Pro 3.4.1 could not be run successfully.
See DaVinci Resolve logs for details.

Any idea what I should try to do to fix this? I did look at the plugin in Resolve and it's letting me know that the plugin isn't active.

 

@vxdragin Maybe your video card, the drivers, the plugin compatibility, the macos version, the resolve version, I think it requires Metal or CUDA only, take a look to the resolve log for clues but could be a lot of things.

You could try removing the plugin and all its files, clean reinstall and test if it works before the code and then apply the code, doesn't matter, the code just 'blocks' the watermark from overlay.

 

@HappyMacmX It seems to be working now. I don't know how to check the logs in Resolve (one problem with searching 'How to check Davinci Resolve logs' is that "log" is a video curve/profile so a lot of that shows up.)
The fix seemed to be in the Preferences > Memory and GPU > GPU Processing mode

Mine was set to "Open CL" and I ticked the box to "auto". I have a Vega 64 (Hackintosh). Once I restarted Resolve, it seemed to work fine.

Am I right in saying that the LUT export feature doesn't work?

 

Yeah, that was it, the open cl setting.

Yes, the plugin is not activated or licensed so you don't have the lut export option.

 

Hello, thank you very much for uploading this. It's not working for me on my M1 mbp, Resolve crashes if I copy and paste the code in the terminal. If I don't do it, then Resolve opens and I'm able to find the plugin but it has the watermark. I'd be very grateful if you could help me fix this.. I'm posting some of the log messages after the resolve crash below for your reference.

Process: Resolve [4077]
Path: /Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/MacOS/Resolve
Identifier: com.blackmagic-design.DaVinciResolve
Version: 17.1.0 (17.1.00024)
Code Type: ARM-64 (Native)
Parent Process: ??? [1]
Responsible: Resolve [4077]
User ID: 501

Date/Time: 2021-03-28 01:30:28.294 +0530
OS Version: macOS 11.2 (20D64)
Report Version: 12
Anonymous UUID: AB1CF6BB-5005-8402-00F6-66E7098479B6

Sleep/Wake UUID: FE113AE0-134F-4DC2-B50A-557F35FD337B

Time Awake Since Boot: 720000 seconds
Time Since Wake: 8800 seconds

System Integrity Protection: enabled

Crashed Thread: 0 GUI Thread Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes: 0x0000000000000032, 0x00000002c283c878
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x2

 

@shawarma That looks like the code signature.

The answer should be to code sign the plugin but I'm not using Big Sur and I don't have a M1 processor so I really don't know how to proceed in that situation, sorry but I'll try to look into it and let you know if I find something, in the meantime maybe someone else with the M1 processor could chime in with some feedback.

Just in case.. you're using the correct code for M1, right?

 

Yes, I used the arm64 code given in the text file...

 

Woow This is very interesting hope soon there will be a windows version

 

Need a windows version

 

Can this work in windows?

 

Hi... Do you know the location of the installed Dehancer pro file, or do you know how to locate it in the M1 Mac? I tried looking in the library folder but there's nothing, no Ofx or video plugin folders

 

@LordMark No.

@shawarma Whatsup, on Catalina it's here:

Code:

OS HDD/Library/OFX/Plugins/DehancerFilm_v3.ofx.bundle

Now about code signing I really don't know, the general code is this:

Code:

sudo codesign --force --sign - appname.app

I guess you should sign DehancerFilm_v3.ofx.bundle but could be the ofx inside or some binary in there.

 

I manually added the file and added the force sign code but I got this error

"/Library/OFX/Plugins/DehancerFilm_arm64_v3.ofx.bundle/Contents/MacOS/DehancerFilm_arm64_v3.ofx: replacing existing signature
/Library/OFX/Plugins/DehancerFilm_arm64_v3.ofx.bundle/Contents/MacOS/DehancerFilm_arm64_v3.ofx: unsealed contents present in the bundle root"

 

W00t.

That is pretty weird, I have no idea what does that mean.

Maybe signing the bundle from the root or add the --deep variable in the command.

 

I tried the --deep command but I'm getting the same issue, do you know the code/ how to sign the bundle root?

 

The whole package, the .bundle file instead of the .ofx inside, same command.

 

Thanks for the upload.

 

Thanks @HappyMacmX ! I've got the same issue as @shawarma on M1 Mac mini. The same log text, and I tried the same signature solution you suggested earlier with no luck. Any new info on this issue?