• 9 Posts
  • 1.5K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle



  • just_another_person@lemmy.worldtoLinux@lemmy.worldNew to this
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    7 days ago

    What I always tell junior devs that want to get familiar:

    1. Find a use-case. Don’t just use it because you have FOMO
    2. Run a desktop environment as your daily driver when you can. You’ll learn a lot.
    3. Try installing packages first, and after you’re comfortable with that, try building a project you intend to use from scratch. It’s a get primer, and gives a ton of context of how software development works along with the dependency chains with the operating environment.
    4. Don’t take a GUI as the “easy route” in spite of non-GUI sokutions. Get familiar with what makes the software run, and customize accordingly.




  • Any software that accepts MIDI as input will work with physical devices that output MIDI. That’s the whole thing there.

    I think what you’re asking about is an input device that can map to whatever software you want to run, and this should be ALMOST and USB device that has uses a generic HID interface.

    If you’re talking specifically about a mixer built for purpose, that doesn’t fall into either of the above categories if you want the sound processing to happen in software. You probably want something that does the DAC and then inputs to your machine maybe?

    If not, check this out, then go looking for any device that will emit HID events as output, and you can turn anything into what you want. Numpads, extra mouse, touchpads, maybe a Korg device (well known to work under Linux).





  • I really think you have conflicting resolvers running on startup, which would explain this. Double check your systemd units that are enabled on boot. If you don’t see anything like networkmanager, reboot the machine, get the status of systemd-resolv to make sure it’s actually running after a fresh boot, check the logs and see if you see anything interesting there, then restart it and check the logs again once DNS works. Something is different between those two actions.