@Lee@retrolemmy.com
@Lee@retrolemmy.com
-
on I finally did it, I am a true linuxer. in c/linuxmemes@lemmy.world · 27 Oct 2026
I’ve also not had great luck with MOTU devices (624, 8pre-es). Granted AFAIK, they’re still not supported in mainline kernel, but I found a few kernel modules on github. Those kernel modules work in that the audio interfaces are detected and I can play audio, but after a couple mins (sometimes immediately), it sounds like I’m getting buffer under runs even if I max out my buffers. If I disconnect and reconnect the devices it will sometimes work for another few mins. They work perfectly on windows. My preferred DAW is also windows only, but I can run a windows VM and do USB pass through on the either of the audio interfaces (other is connected via AVB), and it works great. So this is how I do audio, but this also means I’m using onboard audio for everything except the windows VM.
What I find interesting are new things that weren’t possible before, unnecessary challenges, or rube goldberging things.
N64 emulation has been on the Dreamcast since it was current gen. Cartridge readers have existed since N64 was current gen. What is new about this project (that couldn’t be done before to my knowledge) was to play N64 emulation on Dreamcast directly from cartridge. Previously you’d have to download or use a cartridge dumper to save to a file and then get it on the DC through another method (controller port in this case, but that’s not even in my top 5 ways).
To compare to a similar CSS project would be if you already have a cartridge reader and a CSS N64 emulator, then what would be similar is to have the CSS N64 emulator connect directly to the cartridge reader in a single step rather than dumping cartridge to file and then reading the file in the emulator.