Launchctl unload ~/Library/LaunchAgents/ist Then test it works by activating it before starting resolve.Ĭode: Select all launchctl stop ~/Library/LaunchAgents/ist Launchctl setenv PYTHONHOME "/Library/Frameworks/amework/Versions/3.6" Launchctl setenv PYTHONPATH "/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting/Modules/" Launchctl setenv RESOLVE_SCRIPT_LIB "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Libraries/Fusion/fusionscript.so" Launchctl setenv RESOLVE_SCRIPT_API "/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting" I created an ist file under ~/Library/LaunchAgents with following content, which will run a daemon to setup the environment variables accessible to Resolve UI: Since it is not under path, we have to let Resolve know the location of the python installation. Post installation, verify python 3.6 is installed in /Library/Frameworks/amework/Versions/3.6. If you dont want the standard python installation to interfere with your pyenv environment, then during installation, select "Custom Installation Type", only select the "Python Framework" and disable other options such as "Shell Profile Updater" and "install or upgrade pip". Since M1 Mac does not support python 3.6 natively, install Rosetta (if not installed) and then install the above package. So even when PYTHONHOME environment variable was pointing to pyenv 3.6 installation (verified by calling os.getenv("PYTHONHOME") from lua console), I still got "3.6 not found" error when attempting to select python3 from the console. But within Resolve UI(Scripts Menu), Resolve expects a python standard installer such as Python installed via pyenv works fine while running the resolve scripts from outside the resolve UI/scripts menu such as Pycharm. I was able to finally make python 3.6 work from Resolve console, on my M1 laptop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |