I don’t work with music at all, so most of this update doesn’t mean much to me. However, it’s nice to see the export window was improved—I want my single-click behavior, damn it.
The telemetry is limited to update-checking and error reports. Distributions will disable update-checking because they already handle updating Audacity. Error reports need to be manually submitted. It’s possible that most distributions just disable networking altogether when building Audacity, if it even exists in their repositories at all. Fedora’s package is waaay out of date. Arch disables networking altogether.
Audacity has still instituted a CLA. This is quite worrying. But nothing has happened yet.
I should have specified that the Audacity CLA allowed Muse Group to relicense Audacity from GPLv2 to GPLv3. Yes, I agree with you that not all CLAs are bad. While you keep the copyright to all your contributions, because the copyright is assigned to them (? I’m not actually sure about this), they can relicense it. The CLA agreement.
You grant MUSECY SM LTD, an affiliate of MuseScore and Ultimate Guitar, (“Company”) the ability to use the Contributions in any way. You hereby grant to Company , a perpetual, non-exclusive, worldwide, fully paid-up, royalty free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute your Contribution and such derivative works.
There was quite a lot of confusion and outrage about this at the time, so I can’t recall whether Muse Group specifically said they wanted to include Audacity in Apple’s app store or this was given as an example of why the CLA could be beneficial. My rebuttal was this is not a particularly noble cause. There was also the argument that the FSF requires you to sign a CLA for its own projects so it can reserve the right to relicense it if it benefits the project. My rebuttal to this was…well, it’s the FSF. The day the FSF relicenses their software under a non-free license is the day they die.
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.
Yeah of course I get your argument although we have rpm (or deb in debain based distros) across redHat and OpenSUSE it does not mean that the same rpm package would work on both systems due to distro specific aspects (like different root structures, init systems etc . . .), but that’s something for the package manager to solve, the package format could be agreed upon, which would ease the workload of developers and maintainers since the moment you know the target distros of a package they could see the base differences of said distros and add symlinks, dependencies, environment variables, services … as needed for the package.
This seems like it could lead to a whole lotta of conflicts, but I think if the daddy distros were designed all with one package format in mind, such format could be somewhat interoperable.
I can’t really give a super useful opinion given that I haven’t really touched fedora, but I’ve been using mint for school for almost a year, highly recommend
The one that really irks me now is that Nautilus in Ubuntu doesn’t show thumbnails for PNG images in the file selection dialog. It’s such an ass-backwards change that I’m legitimately shocked.
The file selection dialog is not a part of Nautilus. It is either a provided by the toolkit (e.g. Qt, GTK3, GTK4) or by a xdg-desktop-portal implementation. The GTK4 file chooser that is also used by GNOME’s portal implementation supports thumbnails since December 2022 or GNOME 44.
I guess you are using an older (LTS) version of ubuntu that uses an outdated version of GTK.
Okay. I’m glad that the situation is looking better, and it’s probably more on the Ubuntu people than the Gnome people, but it’s still an incredibly shitty experience.
I think one of the smallest yet fully up-to-date distros around is Alpine Linux.
It might not be a perfect desktop because of Musl incompatibilities but hey, it has a ton of apps in the repos, if your usecase it’s simple it might be enough.
Highly recommend using lvm in the future. You can undersize your partitions and when whichever one you need more space on it’s easy to grow. Also really easy to live migrate to other drives as needed. Good luck.
For an easy GUI way to find these, you can go to the
bottom-left menu > administration > system reports
Then go to the System Information tab.
You should have the kernel i.e. 6.3.0-39-generic at the top
Scroll down, and under network you should have something like Device-1 Realtek RTL8111/8168/8411 - that’ll be the WiFi card.
In case you didn’t know, the Kernel contains drivers for things like WiFi and other devices.
An older kernel tends to be more stable (the bugs have been fixed) - but it cannot contain the drivers for devices that didn’t exist at the time.
By default, Mint is likely using the kernel 5.15, from 2022. If your WiFi device is newer than 2022, it won’t work yet. However, you can install a newer kernel (mine, above is 6.3.0). I had to do this to get the WiFi working on my Thinkpad p14s. This is quite simple and safe to do, and completely reversible if there are problems.
There’s a chance if the WiFi card is particularly new or obscure, that it won’t work at all currently. We’re waiting on the company, or more likely a talented volunteer, to write the drivers.
In this case, you may need to buy a USB WiFi adapter, for example TP-Link USB Wifi. I had to do this with my Dad’s laptop recently. Within the next year, he probably won’t need it anymore, as the drivers for the internal one will likely exist.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.