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.
HN user
grawlinson
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.
They've also been working on emulating the JP-8080, as per recent discord announcements.
The JP-8080 uses custom DSP chips designed by Roland, and Roland do not provide a Virtual Instrument (VST) for this much desired synth.
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.
I’ll never understand these big companies, they often seem to be allergic to money.
Realistically, it’ll be when the patents expire.
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.
Well yeah, how else do you stop color bleeding out and staining your other dishes?
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).
Do you have a PKGBUILD available? I'm currently running into this particular issue when installing the requisite chicken libs:
building srfi-14 /usr/bin/chicken-csc -host -D compiling-extension -J -s -regenerate-import-libraries -setup-mode -I /home/deploy/.cache/chicken-install/srfi-14 -C -I/home/deploy/.cache/chicken-install/srfi-14 -O3 -d0 srfi-14.scm -o /home/deploy/.cache/chicken-install/srfi-14/srfi-14.so /usr/bin/chicken-csc -regenerate-import-libraries -M -setup-mode -static -I /home/deploy/.cache/chicken-install/srfi-14 -emit-link-file /home/deploy/.cache/chicken-install/srfi-14/srfi-14.link -host -D compiling-extension -c -unit srfi-14 -D compiling-static-extension -C -I/home/deploy/.cache/chicken-install/srfi-14 -O3 -d0 srfi-14.scm -o /home/deploy/.cache/chicken-install/srfi-14/srfi-14.static.o /usr/bin/chicken-csc -setup-mode -s -host -I /home/deploy/.cache/chicken-install/srfi-14 -C -I/home/deploy/.cache/chicken-install/srfi-14 -O3 -d0 srfi-14.import.scm -o /home/deploy/.cache/chicken-install/srfi-14/srfi-14.import.so installing srfi-14 install: cannot create regular file '/usr/lib/chicken/11/srfi-14.o': Permission denied
Error: shell command terminated with nonzero exit code 256
Maybe there’ll be an article or two, once it’s released!
Oh wait…
Hey! Thanks for writing this, this really helped me setup VyOS as my main router/firewall for my homelab.
Do you have any plans to expand into IPv6 functionality?
Do you know if any of the official FreeCAD tutorials go through using data planes instead of sketch on face?
I assume it’s here: https://news.ycombinator.com/item?id=36362737
It would be much better if this knowledge was available elsewhere for other souls to peruse. Say, maybe, a blog?
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.
that is some amazingly crap UX. who the hell thought this was a good idea?
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.
This is still occurring? I remember the original incident and just assumed that Google had sorted it out with Drew/Sourcehut.
This is absolutely shocking behaviour, and I’m mortified at the precedent that it sets.
Sort of like how retro IBM Thinkpads have all sorts of modifications from new motherboards to screens? I can see something like that happening, I was on the verge of purchasing a Pebble when they announced their doom ^W acquisition via Fitbit.
nerdctl[0] is also worth a look.
It's been a self fulfilling prophecy for several years now. If you use any Google product, expect it to be added to the Google Graveyard[0] when you least expect it.
You can add this to the list: - An update to ca-certificates due to Let's Encrypt's X3 certificate expiring.
That broke Plex on my LG TV.
It'll probably be something like this[0] and this[1]. I think there are more export restrictions than these two examples.
[0] https://en.wikipedia.org/wiki/Export_of_cryptography_from_th... [1]: https://edition.cnn.com/2020/12/18/tech/smic-us-sanctions-in...
I'd love a browser extension that automatically redirects all twitter URLs to the nitter equivalent.
I've seen other crap notifications on my iPhone from other Apple products in the same location.
It's a major turn off.
From one of the blog posts[0]:
There is also the threat of lawsuit. As I’ve later learnt, 51nb was sued by big L on the pretext that the images and website contained trademarked terms. However, the real reason was revealed that 51nb actually owned the tp.cn domain name and big L wanted it for themselves. Even though 51nb actually won the lawsuit, it hurt their financials badly and they were very reluctant on continuing these projects.
Your post is extremely misleading and full of false information.
I’ve been using a small VPS (sub $10/month) to self host mail for at least 10 years, and I’ve migrated hosts a few times without issue.
I’ve even migrated to a “polluted” IP on a different provider and getting that removed from RBLs took a couple of emails and the entire process honestly took less than a week.