this post was submitted on 07 May 2025
549 points (98.6% liked)
Technology
69845 readers
3865 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Fair, I’ve seen a ton of complaints about Resolve’s lack of AAC support for far too long, so if your workflow depends on AAC encoding and decoding directly inside Resolve you shouldn’t have to bend over backwards to work around that.
That said I’ve done all of my video editing in Resolve Studio on Linux for years now and haven’t had any trouble. I’m using an Atomos Ninja to record, since my camera outputs 10-bit 4:2:2 over its HDMI port but records 8-bit 4:2:0 internally. The Ninja records PCM and so the AAC issue has never bitten me.
The only thing I can complain to Blackmagic Design about is their official support of Rocky Linux only. The udev rules for things like the Speed Editor or Micro Color Panel don’t work properly for Ubuntu- or Arch-based distros, meaning anyone who wants official support is stuck with their specific modified Rocky Linux ISO. Through trial and error I’ve proven that it works fine on AlmaLinux 9.5 too, so that’s what I’m using, but honestly I’d rather be using something with a newer kernel and better hardware support.