Bleeping Lobster

  • 0 Posts
  • 25 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle


  • Yep I definitely took it wrong, one of the problems with text only communication… No body language or audio cues! No worries.

    The devs of my audio interface have definitely been asked a fair bit about Linux compatibility… But considering they’ve not even bothered bringing their new DAW to PC, it seems they’re strongly focussed on mac ecosystems only for the foreseeable.

    Personally I think compatibility should be a two way street pun not intended! But unfortunately companies tend to vote with our wallets, so until Linux becomes even more established I doubt they will dedicate much if any resources to making their devices work on it. Shame.

    I bought a new audio interface for live work a few months back, went for an audient id24 partly because it’s Linux compatible (although no native drivers). So I will get stuck in at some point. I started using PCs back when floppy disks were actually floppy so I’m not afraid of command line stuff!


  • None of the main adobe suite works on Linux either, so let’s not pretend my use case is so narrow. Literally none of the programs I use to work (Cubase, Audition, After Effects, Illustrator, Premiere, yes I can install a virtual windows machine but that completely defeats the purpose) works with Linux. And from what I gather last time I researched this, hardly any audio interfaces are Linux compatible. Most of the games I want to play also are not Linux-compatible.

    Fact of the matter is, despite the large dedicated userbase (which I appreciate), it still has a giant gap where many prosumers and casual users cannot utilise it. It’s no good saying “ahhh well YOU’RE not compatible with US! No u!”. I’d love to switch and tbh am strongly considering a setup for live PA that’s Linux based, in the hope that it brings greater stability. But it’s going to be a large investment of time, and I’ll have to buy a different audio interface if I have a hope of making it work.














  • Bleeping Lobster@lemmy.worldtoAndroid@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    2 years ago

    I went from a Samsung s9 to a Pixel 7a this year.

    At first I thought I’d made a big mistake; egregious amounts of tracking in all apps, enabled and encouraged by google; no ability to customise the home screen which has a whopping 2/3rds taken up by useless, unremovable widgets. Wtf is this shit?!

    However, now I’ve had it a few months and customised it to suit my needs I’m very happy with it, especially for the price. I installed a custom launcher (fixed home screen woes), and installed DuckDuckGo browser which has an inbuilt tracking blocker for all installed apps and the launcher (using Nova, I know, I know, I should be using grapheneOS bla bla bla but it suits my needs and tracking is blocked).



  • Ah well it was worth a try.

    I’m guessing then it’s a sample rate issue, unfortunately I don’t use Linux so don’t think I can be of much help there. I know I’ve had issue before where the interface and windows were both set to a different rate (44.1 / 48) and it caused all sorts of serious sound issues. Hope you figure it out, when I can’t figure out an issue with my music setup it drives me nuts!


  • This sounds very much like the problems I had recently with two different brand new interfaces, trying to connect over USB-C. Fortunately they were both bundled with a C-to-A USB cable, which had them both working perfectly.

    Over USB-C it was disto city, like when a cable is half-unplugged. I thought maybe it was something to do with the type of USB-C ports my laptop has (one is thunderbolt, one is dual-C / thunderbolt). What sort of cable are you using?