No, this will not increase the amount of kernel panics you see. It just makes them more informational to the average person. Technical folks can disable it, non-technical folks won’t know how to enable it, so on by default it is.
Doesn’t the Linux version of Resolve only read/import (or export? I can’t remember) .mov or something that makes it more or less unusable? Has that changed?
Yeah. On Win and Mac, it imports anything. But on Linux, the paid Studio version will import x264/x265 with mp3 or PCM (wav) audio. Not AAC. People don’t like that. Lol
But you’d be insane to edit with these interframe formats. And most commercial editors would auto-convert ingested x264/265 to an intraframe format like Apple ProRes or Avid DNxHR anyway. They’re essentially containers for jpeg or png frames instead of compressing collections of frames. Much easier to scrub the timeline that way, though the files are huge.
On Linux, Resolve (both free and Studio) imports DNxHR with PCM audio and edits that like butter. ffmpeg easily converts prosumer camera x265/aac output to DNxHR. Or Shuttle encoder, if you want a GUI. And most pro cameras output ProRes, ProRes RAW, or DNxHR directly.
Also, Resolve on Linux will ingest all Blackmagic RAW file formats, if you have a Blackmagic camera. And the little BMPCC 4k is still a steal at $1200 or so. As long as you light your subject properly, that little camera shoots gorgeous photography.
Resolve is a pro tool. But a project takes time to set up. For little things, I’d go with Blender’s VSE, which is full featured but has a terrible interface, or kdenlive, which is a Windows Movemaker like toy, but has a normal interface you’d expect from an NLE.
Sadly even Resolve Studio doesn’t support h264 all-intra as used in Sony’s XAVC-I and XAVC-S-I on Linux, which sucks.
With XAVC-I CineEI Slog footage the metadata is enough that Resolve treats it as Raw (in fact, it’s more flexible than braw). So losing this functionality really hurts.
You could use gpu passthrough with iommu and qemu to a virtual system and run Win. A real PITA. I know.
I’d bitch about that on the blackmagic Resolve forum. That’s a serious hit to your workflow. Call out Dwaine, he works there and does Linux support. Nice guy.
I mean, I dunno about you but for me this is money. I make money with these tools. I prefer Linux for privacy reasons, but I’m not religious about it when it comes to money. We all gotta eat.
The Blackmagic folks might help. Especially if you paid for Studio. I don’t work there and can’t make promises, but I’d definitely make a stink about that. At least get a formal statement from them on Sony support in Linux.
My in-house is an old GH5s w/ a Shogun. But if the client pays, I prefer to rent an URSA mini. So I haven’t hit this.
Thanks for the writeup, that’s far more advanced than what I need to do in my work sometimes ^__^ But cool that it looks like there are options on Linux.
I do this for a living. Most people shooting family vids or youtube vlogs/video essays would find Kdenlive perfectly well suited to their needs. It does simple transforms, titling, adjustments, etc. And it looks like a normal NLE. When you hit a wall with it, the move to a commercial program will be easy.
Fusion is what I hate most! Lol I come from Ae and the Adobe suite before I switched. And while I’m comfortable with node based systems, Fusion just isn’t all that compared to all the plug-ins for Ae. Or Blender, which is also fantastic for motion graphics. Fusion does a great job animating titles though.
Resolve requires a whole production pipeline to use it properly. From ingest, organization, cutting, and post for audii, color, and graphics. It’s best suited to broadcast or features. Or, advertising.
The COPR package didn’t work for me on Nobara, so I had to build from source, but it works great. There are a couple of things I don’t like, but overall seems pretty neat.
If I can get Xwayland to work nicely for steam with high refresh rates, then it seems like this might be the WM for me until COSMIC-DE comes out.
I have had it installed for a while and I check it after every update. I can’t use it yet as my daily driver because of scaling issues. The desktop scales properly but windows do not. Fonts are too small and the cursor is tiny. I figured out how to scale the cursor manually but I couldnt scale the windows.
A+ timing, I’m upgrading from a 1050ti to a 7800XT in a couple weeks! I don’t care too much for “ai” stuff in general but hey, an extra thing to fuck around with for no extra cost is fun.
I’m a bit confused, the information isn’t very clear, but I think this might not apply to typical consumer hardware, but rather specialized CPUs and GPUs?
This is the big thing that all these Nvidia comments miss. It’s not up to Wayland to support a given GPU. Nvidia is actively hostile to Linux users. If you aren’t making money with cuda there are zero reasons to choose Nvidia on a Linux machine over the competition. I’ve been on Wayland for almost a decade now and there’s no way I’m going back to X at this point.
FWIW, I’m typing this on the latest GNOME, on wayland, on nvidia proprietary drivers; and it works just fine — EXCEPT for suspend & resume, which is annoying to be sure; but on 2 screens with different refresh rates & different dpi ratios I at least don’t run into some of the weird behavior I do run into using X11.
I used to be an Xfce purist; but this particular setup is even less taxing on the GPU (GTX 970) compared to Xfce’s standard compositor (around 20W on light usage, vs. 35+W); & and the font rendering is slighly better, which is a huge factor AFAIC.
Really looking forward to the day nvidia drivers properly support wayland. Getting tons of bugs, stutters, and general usability issues with plasma wayland on my 3060. X11 just works on the other hand, even with multiple monitors running at different refresh rates (something a friend of mine said X11 doesn’t work well with). But I want all the nice benefits wayland offers.
I think we may be looking at these wrong. Yes there’s a visible throughput/latency improvement here but what about other factors? Power savings? Cache efficiency? CPU cycles saved for other co-running processes?
These are going to be pretty hard to measure without an x86_64 simulator. So I don’t fault them for not including such benches. But there might be more to the story here.
No, they’re discussing the way forward and what they think makes sense. In fact, they’re even clearly stating that there will be pain, because Wayland intentionally does less than X11. And they’re encouraging people with unsolved pain points to speak up.
phoronix.com
Top