patchlore @paul@post.lurk.org

Accidentally created the TNG space sound.

The gist: use a big reverb with nearly infinite decay, send any short sample through it, and sample the reverb tail junk many minutes later.

I'm using a FDN reverb (costello reverbsc topology, to be precise), with the feedback at 1 and the cutoff pretty dark (probably around 1kHz or so)

So Magic Leap is tanking apparently. Good. Never been a fan of the hype + secrecy combo. Always brings out the worst in people.

So, long ago, I learned through trial and error that you can parse a gamecontroller on Linux via reading /dev/input/js0 as a file. What I *didn't* know was that there are special constructs for this in the Linux Kernel. If you don't use this, things may differ from platform to platform.

Haven't tested this, but this gist seems to show how to do this: https://gist.github.com/jasonwhite/c5b2048c15993d285130

This official joystick documentation also looks helpful:

https://www.kernel.org/doc/Documentation/input/joystick-api.txt

From the Steam HID module inside the Linux kernel:

'This is known as the "lizard mode", because apparently lizards like to use the computer from the coach, without a proper mouse and keyboard.'

https://github.com/torvalds/linux/blob/master/drivers/hid/hid-steam.c#L14-L15

Some useful links I found for the steam controller.

The steam HID controller in the linux kernel:

https://github.com/torvalds/linux/blob/master/drivers/hid/hid-steam.c

user-space steam controller (found via source code): https://github.com/rodrigorc/steamctrl

Bought a steam controller after it was on sale for 5 dollars. I hadn't even heard of the steam controller until that point, so it really was a true impulse purchase.

So far, I'm very impressed.

Put in the batteries, plugged in the dongle, and the thing worked. The fact that it acts as a mouse with haptics is really cool. Hoping I can somehow program the haptics myself somehow.

Began examining output via cat /dev/input/js0 | xxd -c 8, and the results are quite revealing. Both circle pads seem to have touch pad capabilities of some kind. Also the L + R triggers have some kind of continuous control as well. Lots of ripe potential for musical expression.

Typing. Mind boggling that to me that humans have the mind + dexterity for it. And it isn't even a superpower. A certain proficiency for it is actually *expected*.

Me watching first episode of carnival row:

"Hey that actor kind of reminds me of Orlando Bloom."

*looks on imdb*

"Oh."

NASA should launch another golden disk into space, but with classic video games.

Anyone have any experience using tinyemu? It's made by Fabrice Bellard (QEMU, FFMPEG, TCC, etc), so I have high hopes for it.

https://bellard.org/tinyemu/

Oasis makes Alpine look like Ubuntu. If you don't know what any of that could mean, maybe turn back now?

Lots and trial and error, but some progress has been made. I now can compile a base system that I can chroot into. Fun stuff.

A few thoughts on it:

Author is super nice, and is quick to respond to git issues + emails. So that's a good sign in my book.

The core linux system builds in a matter of minutes. This makes trial and error quite sane.

Core system is mostly a limited shell, but you also get groovy things too like lua5.2, samu (portable ninja clone), and git. Just enough to recompile oasis inside of itself.

Oasis total size for core (with built source directory) is about 1.5 gigs. Most of that is just the source directory. The core rootfs really tiny. /bin is only 70mb. the musl toolchain I'm using accounts for 191mb. /lib is 16mb, and the root .git directory is 72mb.

Oasis makes heavy use of git. Lots of new commands + features I've never used before, like templates (I'm a pretty basic git user though).

ninja is used as a build system. As things start to work, I'm slowly warming up to it.

Things work better if you configure a musl compiler. musl-cross-make doesn't take ages to compile, fortunately.

More docs needed.

Code smell. It's a useful term in theory, but it is uncomfortable to use in practice.

I, for one, would prefer NOT to know what my code smells like thanks.

What I'd give to hear peter griffin sing some of the music from the Witcher 3.

These experts are very confident in their countertfeit-spotting abilities. They look at a thing for 4 seconds in a dimly lit room, and then proceed to smash it on the floor.

My initial thoughts on AWS composer:

A keyboard.

A... Keyboard.

A FUCKING KEYBOARD.

The "brightest minds" let loose to try and figure out how to apply the Latest and Greatest Machine Learning has to offer. Deep pockets, practically unlimited resources. And...

a god damn fucking keyboard interface.

Did nobody bother to contact an actual musician? Fuck.

I'm so done with keyboardists determining the so-called "future of music technology". The world could be so much more than this. (And if you squint your ears, it really is!)

Oasis is a linux distro that is completely statically linked. It's been a really fun project to fumble through. So far, I've managed to get a chroot set up. Looking into how to install additional packages and get sudo/su working:

https://github.com/oasislinux/oasis/

Naturally, I've forked their code base. They've done a great job up to this point. It takes only takes one average brain to maintain a C codebase of the current size. C++ encourages codebases that require multiple brains to maintain.

Friends of mine are converting their embedded C codebase to C++. Welp. I tried to help them.