I packaged that driver on the AUR, since I’ve got the same device. I can’t get the binary blob to work (admittedly, I haven’t tried very hard) and it’s not high on my list of priorities so I’m okay using it as a dumb MIDI tool.
Arch package manager here, there is ongoing work behind the scenes to support multiple architectures (aarch64, riscv, etc), but as our volunteers (myself included) are doing this in our free time, progress is up in the air.
Arch package maintainer here; we generally encourage building from source for packages provided by the official repositories. As far as I know, we only ship pre compiled binaries if there is no source available, i.e. commercial programs such as reaper.
Apple (and other streaming services) have been caught out replacing people’s local songs with censored/blessed versions. That is the main reason why some characters will not stream music; because they do not have full control over their own files.
Does anyone know how to access any of the repos listed in this vault? I’m after a particular one that was deleted earlier this year; has zero forks and does not show up in the way back machine.
I don’t know what I would do without sieve, I use it to manage my mailing list subscriptions, eg move to folders, mark emails from specific chatty users as read, etc.
It automates a lot of manual cruft and I’m endlessly thankful for it.
I do wish it was more widely supported, and I try to do my part to encourage adoption (I maintain several sieve related packages for Arch Linux).
> The optocoupler also works like a cheap (although somewhat hard to replace) fuse which is probably a good thing if you want to connect you Roland Jupiter-8 / Fairlight CMI to some dodgy equipment.
In this case, the older synths are more likely to have failing/dodgy components. I have a DX-7 that I'm going to have to replace a lot of components in, and this sort of knowledge/understanding really should be more common along synth enthusiasts.
I have a Z97 board from ASUS that exhibits this behavior. It’s a bit ridiculous because there is no Secure Boot option in BIOS other than disable/enable.
This kind of stuff really needs to be made explicitly clear in any/all API documentation as it inevitably leads to underlying issues later down the line. It's amazing how something as "simple" as official time/date libraries still have footguns like these.
I'm not bashing anyone that's involved as I realize we're all human and prone to mistakes, I just wish we could all do better.