Show newer

might make a account for toki pona things. Dunno. The only other fedi account I had than this one kinda got abandoned, I feel like I can't maintain multiple accounts.

jan pi toki pona li lon ilo Masoton, taso lon ilo lawa ante :
@ice (ilo lawa sina li kepeken sitelen pona a!)

if I had a nickel for every animated kid's movie from the mid-2000s with a main character called Rodney, I'd have 2 nickels.
which isn't much, but it's still weird that it happened twice

11 - some fast electronic drums
the way my looptobers vary in length and complexity is probably kinda weird. From an entire track one day to 5 seconds of drums the next. I had an exam today, OK? That's my excuse.

windowmaker feels rn: it's very retro and I quite like it but it does everything a little bit differently, and my apps don't really fit the aesthetic of it (but I do like that aesthetic personally)

windowmaker is kinda weird and retro and I'm trying it out because it seems neat. Need some better way to generate a menu for it though.

Show thread

Nintendo: C&Ds online Melee tournament simply because they're using Slippi
Gamers: well obviously that's bad

Kotaku: Hey, Switch emulation is getting so good it's already running the new Metroid game
Gamers: this is literally killing my friend Nintendo and they'll never make another Metroid game

Show thread

I feel like I just get an itch every now and then to change WMs and I'm not sure why

Show thread

for a while I've been wanting to try another WM. No reason why, just feeling like I want to. Even though fluxbox works fine.

it's just too many steps and a hassle to implement (to anybody who says "use libmonome", I'm writing a renoise tool and can't use libmonome) I might go the approach that duplex uses, and just have the user specify the send/recieve ports themself. It's a pain for the user (me in the future) but easier for me now

Show thread

1. create an osc server
2. create an osc client
3. send a message to serialosc from the client to the server to request the device list sent to the server
4. listen for the device list
5. wait to get the devices (because there's no indication that the list is over)
6. create another client to send message to device info
7. create another server listening on the port that sends back
8. use this final server and client to send messages

Show thread

I really hate how serialosc's device list/connection stuff works
there is literally no elegant way to implement it
why the fuck does it work like it does?

I'm here for like two weeks. It feels much better than constantly being on Facebook. I'm calmer and more present.

But I really miss my #yarn and #handspinning tribe. I have noone to really share this passion with in real life, and there seems to be like I'm the only mastodon user in this niche.
Maybe I should not care and just create. It just feels a bit lonely like this.

Or maybe I'm just too stupid to navigate the #fediverse. But I'm really not that geeky Person...

Web dev be like:

"I want to detect if a CSS variable has been changed"
"Sure, here's a very hacky solution with very specific requirements that are a pain to implement because there's no official way to do this"
"I want to detect if a user is sitting in a >3m² room, alone, and hasn't blinked in the last 2 seconds"
"You can use this 1-liner that utilizes the RoomSizeUserPresenceAndEyeBlink API Google pushed into standards to totally not improve their tracking of users"

10: Lemon Demon - The Ultimate Showdown of Ultimate Destiny (Idunnohowtamayka remix)

This is probably my highest effort looptober and also the one that is least looping, but it would loop if you looped it. Working with vocals in renoise is suprisingly nice for a program that has no concept of an audio track.
(and yes, Idunnohowtamayka is becomeing an alias of mine now, just for the sake of that joke)

I made a loop today but it's too much a joke to be my actual looptober
so for my actual looptober I'm literally remixing a meme
I have no serious ideas today.

only been using renoise for like 2 days and I already am diving into the scripting API
I'm not happy with how duplex (the official fancy renoise controller tool) works so I'm building my own grid interface for it. you can build your own interfaces from within duplex and it seems powerful af but also like a big framework and I would rather just write lua.

I really need to get some more drum samples than just 808s
but I'm worried that the more samples I have the harder it gets to find what I actually want
so it's like, I want a better sample management system before I get more samples but I can't know what that system will be until I have more samples

Show older
Tiny Tilde Website

ttw is the unofficial Mastodon instance of We're only smol, but we're friendly. Please don't be a dick.