After moving from GalliumOS to Xubuntu, I noticed that playing YouTube videos on both Firefox and Chromium would result in decent playback for a few minutes, but suddenly the audio would turn into a solid beeping tone while the YouTube video displayed the white loading circle on top of the video as it continued trying to play.
The beeping sound would continue until I paused the video for long enough for the beep to stop on its own, or just close the tab. According to some forums around the net, it seemed to be an audio codec or driver issue. After a bit of digging through posts of similar but not exact audio issues, I found one that seemed to match my situation exactly.
The Solution
Apparently this was an issue with running a kernel that didn’t support and/or didn’t have a Sound Open Firmware (SOF) driver installed. Someone brought up an issue on their Github page and a solution was found and shared. This solution was also referenced in a few other places, so I gave it a shot and it 100% worked.
You can install the drivers with this epic bash script (please check it out before running it):
When I try to update my machine by running sudo pacman -Syyu I get an error saying it’s unable to lock the database. Below is an example:
But as you may have noticed, by removing a special database lock file, I was able to solve the issue. You can do this with sudo privileges by running:
sudo rm /var/lib/pacman/db.lck
The above method is dangerous
I’ve done this before, and it’s worked perfectly fine with no issues. But the reason the db.lck file exists is to ensure that only one program can run updates at a time. This prevents partial updates, or interrupted updates, or conflicts, or any other problems that can occur when two programs try to do the same update at the same time.
So before you go deleting your db.lck file like I did, do yourself a favor and make absolute certain that there are no other programs trying to update anything. You can use the lsof command to check what other programs are using the db.lck file. lsof is short for “list open files”.
The lsof command will either return nothing or a single number. If it returns nothing, that means that no process is currently using that file. If it does return a number, then that is the ID of the process currently using that file. In order to delete the file safely, you’ll need to kill that process first. You can do that by running sudo kill -9 <process_id>
Hope that helps! Please leave a comment below if you have any questions. You can find more information on using the command line, check out this awesome book called The Linux Command Line. It’s free!
If you’ve used Linux for any amount of time, you’ve probably come across a PPA. A PPA is short for Personal Page Archive. If you’re looking for a specific piece of software not available in the official software store for your distro, you might look into adding a PPA. Most software that is offered via PPA includes the installation instructions to add their PPA and get everything installed. However, not every software includes instructions on how to remove their PPA and uninstall everything. In this tutorial, we’re gonna learn how to remove a PPA via the command line.
Side Thoughts
As far as I’ve heard on forums and StackOverflow and pretty much everywhere else, it’s typically not the best idea to install software using a PPA. I did it a few years ago when I was first getting into linux, but I don’t do it at all anymore. Generally speaking, PPAs aren’t the safest thing to be using and I really don’t have much need for them anymore. In fact, on of the biggest reasons I switched to Manjaro a while back was because of the massive AUR (Arch User Repository). There you can find a massive community of Arch users who have created a ton of software and configured it just for Arch. Still getting the hang of it, but so far it’s been amazing.
Now for the Actual Tutorial
If you happen to know the exact URL of your PPA, you can remove it by using the --remove flag:
Earlier this week I decided to run DaVinci Resolve on Ubuntu 18.04. This was a terrible idea. I spent the last 3 days banging my head against a wall and scouring countless forums, blogs, articles, and all for nothing. Here’s my situation. I have an AMD Threadripper with a pair of RTX 2080TIs that I was trying to use with Ubutnu and Davinci Resolve.
Of course, if you plan to run Davinci Resolve on Ubuntu 18.04, the default Ubuntu install pretty much gives you the generic graphics drivers and it’s up to you to install the ones you need. Since I want to run Resolve, I’ll be needing the latest Nvidia drivers for Linux. Downloaded and installed from the website, but it didn’t work. Installed CUDA, but it didn’t work.
I tried so many different drivers that they started conflicting with each other and it became an even bigger mess than what I started with. I rebooted a ton of times and sometimes the drivers would work, and other times they wouldn’t even switch from the old driver. I tried with and without CUDA and with and without OpenCL, but nothing worked. I couldn’t get anywhere beyond the opening splash page.
TL;DR
Guys, just save yourself the trouble. Seriously. If you’re wanting to run Davinci Resolve on Linux, but you don’t want the official CentOS build… Do yourself a huge favor, avoid the headache and just install Manjaro. Seriously. I was up and running in Davinci Resolve cutting 5K RED footage in 15 minutes. It’s the easiest Linux video workstation setup ever. I’m never going back.
Full disclosure: I’m not being paid to write this. Opinions are my own. This is just my experience. As always, keep your passwords secure, and your sources open. Cheers.
Let’s locate files using the terminal! This is just a cool little trick you can use if you’re doing a bunch of stuff in the terminal, and you don’t want to leave, or you’re just interested in cool terminal tricks. Let’s say you’re looking for a file, anywhere on your machine, but you don’t know exactly where it is. You can install a very cool search package called mlocate (or merging locate).
Install
On Ubuntu/Debian you can run:
sudo apt-get install mlocate
Or if you’re on that Manjaro/Arch life:
sudo pacman -S mlocate
Syntax
To locate files in the terminal by using mlocate, just type:
locate [name of the file] [directory in which you want to start recursively searching]
If you’re using mlocate for the first time, it’s not gonna work just yet. mlocate is actually a pair of tool bundled into one. The other half of mlocate is called updatedb. So by running updatedb, you’re essentially creating/updating an index so that you can run your search. So any time you want to run a locate command and it’s not giving you the results you are expecting, there’s a good chance your index is outdated, so you can just run updatedb, then run your locate search again, and you should be good to go.
Update your junk by running updatedb then run locate [file] to get your mind blown!
Bonus Tip
If the results of your locate command are crazy long, like… CRAZY long…. too long to view everything in the terminal because your terminal only has a finite history, here’s a tip: You can print the results of ANY command to a text file and save it anywhere by using >. For example:
The above command will run a system-wide search for anything matching myfile.txt recursively from the root directory / and print the results to searchresults.txt on the Desktop.
Good luck and have fun! Now that you’ve found the file you’re looking for, perhaps you want to do something cool with it! If you wanna learn more cool stuff you can do in the terminal, check this out.
Themes can do a lot to change the look and feel of your computing experience. If you’re a Linux user, there’s a good chance you like things customized. Just have a Google for “linux themes” and you’ll see what I mean. You can take this to whatever level you want. You can change the look and feel of literally everything, or you can do a subtle cursor change like me.
Breeze Theme
Lately I’ve been a fan of the Breeze cursor theme. To get that theme and a selection of other themes to choose from later, open a terminal and install the unity tweak tool and a few theme libraries:
Once you install the themes and the unity tweak tool, you can open the tweak tool and head over to Appearance > Cursors. Click through the list until you find one you like. Make note of the name. Once you’ve got one, open your terminal again and type:
This will bring up a list of all the themes you’ve installed on your system. Look through the list and find the theme you liked. Type in the number of your selected theme to confirm your changes. To make sure your changes remain changed, simply run:
$ compiz --replace
and you can either reboot or log out and log back in to make your changes. That’s it! Enjoy your new look!
Janne Liljeblad and other contributors released Flowblade 2.0 recently and I thought I’d try it out. I edited a quick 1 minute video from about 10 drone clips shot in 4k. The first impressive feature was how easily I was able to render proxies. It was just as easy to replace them with the original media before the render.
As both a Premiere user and a Linux user, I’ve been on a quest to find an NLE that is just as capable and intuitive as Premiere, but on Linux. So far, I’ve used only a few and had just ‘okay’ experiences. My first Linux based NLE that I dove headfirst into was Kdenlive. I was cutting some footage for a client and built out the complete project in Kdenlive for a few reasons. First and foremost, at the time, I no longer had access to Adobe CC through a former employer. And finally, even if I had $53/mo, I could think of 1,000 things I’d do before I got an Adobe CC subscription.
But I digress, this is a post about Flowblade. My experience with Kdenlive was fine, the hotkeys took some getting used to. The alpha channels weren’t automatic either, but it worked. Flowblade, however gave me a much more ‘automatic’ experience. I’m on an older mid-range GTX-970 machine and 4k footage doesn’t playback smoothly. Regardless, it felt like proxies were easier to create in Flowblade than in Premiere. Just a few clicks and it was done. Updated right there in my timeline. And encoding was a breeze. Once I made my edits, which was a pleasure by the way, All I had to do was choose “replace proxies with original media” and I was all set to render.
Intuitive Experience
There were several hotkeys that carried over from Premiere and others that just made sense. The i and o keys set in and out points, the HOME and END key pops your playhead to the beginning and end of your timeline, stuff like that. The alpha transparency and title card system took some getting used to, but it wasn’t that bad. I feel like color correction is slightly easier in Flowblade than in Kdenlive. That’s just my experience, and the clips I happen to be working on.
Overall, I still can’t completely commit to Flowblade, even though it’s a pretty great application for basic edits. If I were a vlogger and just needed something to spit out videos with speed, I’d definitely use Flowblade for everything. And even as a pro editor, I still may use Flowblade for some quick edits here and there, based on the situation. But as long as Resovlve remains an option for Linux users, it no doubt offers the absolute best postproduction experience so far. The grades are otherworldly. I’ve never had so much control over color. Not even in Premiere. Lumetri Color doesn’t even compete with Resolve.
So far, my only issue with resolve is it can’t take Panasonic .MTS files by default, they have to be transcoded first. And that just may be a “free version” limitation, I’m not sure. Either way, I’m just a few freelance jobs away from picking up a full copy of Resolve for my personal Linux machine, so I’ll keep you posted if my experience changes once I get everything up and running. Until next time.
If you’re like me, you’ve been on a quest to find the best video editing software that you can run on your Ubuntu Linux PC build. If you’ve been in the video world for any amount of time, you’ll probably know that Resolve 15 is arguably one of the most robust tools in the industry. Here’s my experience on running DaVinci Resolve 15 on Ubuntu 18.04
After the initial install, everything seemed to have went fine, but when I clicked the new icon in my application tray… nothing happened. After a few more clicks, I uninstalled it and went on with my life. A few months later, DaVinci Resolve came up in conversation when talking about postproduction solutions for Linux. So I decided to give it another shot. Same issue.
Unfortunately, in Linux_Installation_Instructions.PDF there is literally nothing telling you that you should install dependencies. I ended up finding the required dependencies somewhere online.
After that simple line in the terminal, Resolve fired right up in Ubuntu 18.04 On to the next hurdle: limited file type imports.
Convert footage using FFMPEG.
Only some file types work with Davinci Resolve 15. The ones I’ve tested that work are:
Apple ProRes (.mov)
Motion JPEG (.mov)
If you can afford the space, I’d choose Apple ProRes before anything else. Unfortunately I haven’t found a way to specify 4:2:2, 4:4:4, or HQ preferences. It’s just ProRes, and from the looks of it, it’s the highest quality possible. You may be able to change this with the -q value. Still testing this.
In my 10+ years as a video editing professional, I have never used the motion jpeg codec. However, after running a few tests, playback in Resolve 15 is flawless, and the file size is the same, if not slightly smaller than the original file. My original test file was a Panasonic .MTS file clip at 1.7GB. After the transcode to motion jpeg, the result was 1.6GB, and played perfectly inside Resolve.
The further I tested this transcode setting in ffmpeg, this reduced the file size just a little bit. The biggest clips were originally 4.3GB and the resulting files were hanging out around 2.3GB-2.7GB.
The only way to truly test if this is a viable alternative to Adobe CC on Mac or Windows is to actually test it on a live project with a real deadline. This may have been unwise, but I found it to be thoroughly worth it. I tried the above ffmpeg commands, only to realize after exporting that the resulting transcodes were sub-par. Pixelated garbage in, pixelated garbage out. So this time I hit up Handbrake. This one got me. Handbrake is essentially ffmpeg under the hood, but it doesn’t offer all the options that the command line does. So my exports out of Handbrake looked great, but there was no audio supported. On Ubuntu, Davinci Resolve only supports PCM audio, and that’s the one thing you can’t kick out of Handbrake (at least from the options I have).
New Plan
The original exports from my ffmpeg commands above looked like garbage, but the audio (pcm_s24le) was supported and sounded fine. So I ended up exporting Mpeg4 video out of Handbrake with no audio. I synced those clips up with the existing PCM audio in Resolve, and everything looked and sounded awesome. Next objective, getting an H.264/AAC file out of the free version of Resolve.
Instead, I exported 20-30 minute bits of my 3 hour long timeline as Quicktime MOV files with MPEG4 codecs. They looked and sounded great, but were a touch big on the file size. Next. I just dropped them in order into Shotcut, and encoded the whole thing as H.264/ACC. Done. So for future reference, it probably wouldn’t hurt to just encode everything as Quicktime ProRes PCM, do my work in Resolve, then export QT ProRes PCM as an intermediate, then concatenate in Shotcut or Kdenlive. Kind of a wonky workaround for now, until I can afford the full version.
Notes about the free version of Resolve 15
The editing capabilities of the free version are quite nice, but they clamp down your options when it comes to exporting. First cheap shot: they don’t support H.264 encoding on export for Ubuntu. And at the time of this writing, DNxHD and DNxHR both cause Resolve to crash upon export. So without H.264 and DNxHD/HR… your export options become extremely limited. This is especially true if you have a long (3 hour) timeline that you need to deliver to a client. So is there a workaround? Fortunately there is one, but it requires a bit of hard drive space, extra time, and some FFMPEG knowledge. First, trying kicking out your timeline with these goofy settings:
I thought a Kakadu was a bird…
Here’s the gigantic and disheartening list of features that they hold back from the free version. Also, here’s another magic setting that seems even smaller than Kakadu:
Project Complete
I eventually exported the video in about 10 different sections, using MPEG4 encoded Quicktime MOV files. Decent quality, and decent file size. I ended up assembling all those color graded and sound-edited files in Shotcut and rendering the H.264 MP4 that I was looking to deliver in the first place. A super wonky workflow, but in hindsight, I think it will be worth picking up a copy of Lightworks for my edit work Resolve Studio for my color work, and cutting audio in Resolve’s Fairlight, or if Fairlight absolutely cannot handle the task at hand, I can always grab a copy of Ardour. Those softwares paired with Blender, Kritia, Inkscape, and GIMP, I don’t think there’s anything I’d be missing from Adobe CC that these platforms can’t provide.
We’ve all been in a situation where a client calls you in a panic and they need something right away. Only problem is, the file they need is on your desktop at work or at home or… basically somewhere you’re not. Remote access can save you from trouble and offer a level of convenience like few other apps can.
Where To Start
There are tons of remote access applications out there, some free, some paid, closed source and open source. Previously, I used the free version of TeamViewer. That is, until they were hacked. So are there any decent applications that can just connect you without having to give up your email address? Thankfully, yes.
Remmina
Remmina is awesome. However, it can be terrible if it’s not set up properly, or if you’re not quite sure exactly how to use it. I’ve learned the hard way, and hopefully I can share enough info to get you up and running in no time!
Install Remmina
If you’re running Ubuntu, Remmina comes in the box. If not, you can grab the snap version by running this in the terminal:
Once you’ve got Remmina on your machine, you should see a window that looks kinda like this:
So fresh and so clean
Set up the Computer You Want To Access Remotely
On the computer you want to access remotely, your first step is to enable screen sharing.
Linux was hitting up that dark theme about 35 years before Apple. Just sayin
By default, screen sharing is disabled, but for this to work, you’re gonna want to turn that on.
Clickity click
Now you should see the screen sharing options. You’ll want to allow others to access the screen, and prompt them with a password upon logging in.
All good
Establishing A Remote Connection
Now, all you need to do is open Remmina on the computer you’ll be accessing FROM, and enter the IP address of your remote computer. This can be tricky if you’ve never done this before. If you’re at home and the computer you want to control is also at home, you’re more than likely on the same network. This is known as a local network connection. You can access your machine easily just by typing in its local IP address. However, if you try this from your local coffee shop wifi, it won’t work.
What’s My IP Address?
As mentioned earlier, there’s your public (external) IP address, and your private (internal) IP address. Which is which, and why does it matter? Your internal IP is used for local networks, like your home wifi that’s connecting your laptop, desktop, Chromecast, AppleTV, Roku, your friend’s phone, and your Alexa. All those devices have their own individual IP addresses, and are connected to your wireless router (wifi), that has its own public IP address, which is accessable over the internet.
Use your PUBLIC IP Address
The point of remote access is… being remote, AKA outside the network where your other computer is. So before you leave the house, go to whatsmyip.com and copy that address to your clipboard. This is your public IP address (hence, why you can just hit that website and it displays it to you).
Set Up Your Router
Paste the IP address you got from whatsmyip.com into your favorite browser. This will bring up the login page to your home router. If you’ve never seen this before, the username and password is typically printed on a sticker on the side or bottom of your router. Look for a button that says “Port Forwarding”. Find the computer that you want to connect to and create a new rule for it. Set your port number to 5900 and save.
Set Up the Remote Computer
You need to install a VNC server that will allow your remote computer to listen for incomming connections. You can do this by running:
sudo apt install vnc4server
Connect
Okay, back to Remmina. In the main window, select VNC from the dropdown at the top.
RDP is only for connecting to Windows, and SSH is just terminal access
Next, type your IP from whatsmyip.com into the bar, and ending it with :5900. So, for example, yours might look something like this:
65.88.88.127:5900
Next, you’ll be prompted for that password you set up earlier.
Tales from the Encrypt
Then, badda bing, you’re looking at your remote desktop! You did it!
such linux. much awesome.
Did I miss a step? Having trouble? If you had any questions or ran into any issues while trying to set up your connection, feel free to reach out! Drop a comment below, or hit me up on Twitter.
