Monthly Archives: October 2017

Uninstall DaVinci Resolve 14 on Ubuntu

If you, like me, were tempted to Download DaVinci Resolve “free”* for Linux. Be aware that when you add folders to your media library, you won’t see your videos encoded in h.264 (which is the most used format).

Install instructions

Unzip the contents, then from the terminal run:

sudo sh DaVinci_Resolve_14.0.1_Linux.sh

Try to launch it from the command line too, you find the “resolve” program in /opt/resolve/bin

If you see some errors about missing .so files, you may need to install the packages containing the libs:

sudo apt install libssl-dev

You may also need: libgstreamer-plugins-base1.0-0

Then create symbolic links as follows:

sudo ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0  /usr/lib/libcrypto.so.10
sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0  /usr/lib/libssl.so.10

I wanted to quickly try this video editor on Ubuntu 17.04 and I was highly disappointed not to be able to import any of my DJI drone videos. What’s the point of having a powerful professional editor that doesn’t even natively open any of my videos, while other open source editors like kdenlive, openshot can open these files? And no, I don’t want to convert my videos in a different format, just to open them in DaVinci.

Uninstall instructions

Also I struggled to find a way to uninstall this software, so here the instructions if you want to clean your hard drive after a disappointment similar to mine:

sudo rm -f -r /opt/resolve
sudo rm /usr/share/applications/DaVinci\ Resolve.desktop

If you this page was helpful, visit banggood to find a cheap gadget or something useful for a few bucks (free delivery worldwide!), if you buy from my link I get a small commission, thank you.

Jenkins: checkout Gerrit patchset (Gerrit Trigger plugin)

Today I had to setup automatic pipeline triggering for each new patchset pushed to Gerrit for review. The Gerrit Trigger plugin makes it a piece of cake to achieve the goal.

In reply to How to Checkout a Gerrit Change in a Jenkins Sandbox Pipeline: such a snippet can be easily found directly in Jenkins > browse to your pipeline > click “configure” > click “pipeline syntax” > Sample step: select checkout: General SCM > fill what you need, click on advanced and add a refspec and generate the snippet. Here a snippet using the GERRIT variables exposed by the plugin.

node {
 stage('checkout gerrit patchset') {
 echo "gerrit branch: ${GERRIT_BRANCH}, gerrit refspec: ${GERRIT_REFSPEC}"
 checkout([$class: 'GitSCM', branches: [[name: "${GERRIT_BRANCH}"]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CleanBeforeCheckout']], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'jenkins-rsa', refspec: "${GERRIT_REFSPEC}", url: 'ssh://yourgerritserver:29418/yourrepo']]])
 }
}

Note extensions: [[$class: ‘CleanBeforeCheckout’]] is a good idea if you need to build from different branches, if your setup is simpler, you can just use extensions: [].