Pinned Tweet
You can now also follow me at mastodon.rosseaux.com/web/@b… resp. @[email protected] . But I myself will continue to stay on Twitter as well, Mastodon I will just have in addition for those who want to leave Twitter but at the same time continue to follow me. So don't worry 😀
Rush E on a physically modelled concert grand piano in klangknecht, my own (still unreleased) #DAW.
No samples: waveguide strings, felt hammer, dampers, half-pedaling, sympathetic resonance, modal soundboard, all in real time.
youtube.com/watch?v=oCzmU0He…
#PhysicalModeling #RushE
"Show HN: Our space game has a built-in RISC-V emulator that runs Linux"
news.ycombinator.com/item?id…
SEEDS - Echoes Beneath the Sands is now on Steam and you can wishlist it!🌱
Terraform a barren planet back to life. Powered by PasVulkan, my own #Vulkan engine written in #ObjectPascal. Over 2 million lines of code in total.
store.steampowered.com/app/5…
#gamedev #indiedev
I'm looking for remote client work to bridge the gap until my game project generates revenue. If you know of any opportunities in software dev (Pascal, C/C++, x86 ASM, Vulkan/GFX, engines, compilers), music production, or similar fields, please reach out! rosseaux.com/
"Time", a WIP test track for new BeRoTracker features:
- Pattern Matrix: the whole song at a glance
- Channel Patterns: write a part once, reuse it anywhere
- OPL3 FM synthesis next to samples, in the same patterns
youtube.com/watch?v=udeYsME6…
#BeRoTracker #OPL3 #tracker
New in BeRoTracker: channel patterns. A single channel of a pattern can point at a separate one-channel pattern, usable in any number of patterns. Loop or one-shot per use, own loop length, own start row. New Pattern Matrix page shows all of it.
youtu.be/10tEKlxQe1k
BeRoTracker 1.00.2026.09.15
TL;DR: Now also with a macOS build.
Now with an RHI impl., so it can also use Vulkan and Metal for rendering, no longer OpenGL-only. This means it can now also run on AArch64 macOS, alongside x86-64 Windows and Linux.
berotracker.com/
BeRoTracker 1.00.2026.09.11
New third F12 page: Playback Compatibility. Every tracker quirk the replay goes by, as 159 named switches and 7 family fields, in plain sentences instead of source identifiers. Editable in .brt, read-only for MOD/S3M/XM/IT.
berotracker.com
New BeRoTracker build out: berotracker.com/ - samples, VST2/VST3/CLAP, Buzz-style modular, MIDI, AdLib FM, automation, all in one #tracker. Plays 447/450 AT2 modules with register-identical OPL3 output. 42 AdLib formats import. Win/Linux, X11/Wayland, no SDL.
New video: the current state of KRAFT, my open source Object #Pascal 3D physics engine. Now with signed distance field collisions (even heightfield terrain), plus ragdolls, joints, vehicles & more.
youtube.com/watch?v=qdV6Wlh-…
#gamedev #physics #opensource
vkcube running on 64-bit RISC-V Alpine Linux in my PasRISCV Emulator with the Vulkan-based PasRISCVEmu UI backend. #riscv #vulkan @risc_v @VulkanAPI
Guest Software rendered OpenGL kmscube running on a guest 64-bit RISCV Alpine Linux system in my PasRISCV emulator with active x86-64 Tracing JIT Dynarec compiler with smooth >= 60FPS 🙂 #RISCV #Emulation #JIT
The irony: the entire #RISCV base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, (1/5)
extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, (4/5)
A small rant about vector extensions in RISC-V, although I like RISC-V in general. But why is RISC-V's vector extension (RVV) so different from other SIMD instruction sets like x86's SSE/AVX or ARM's NEON? It seems like RVV is designed to be more flexible and scalable, (1/3)
but it also makes it more complex and harder to implement a JIT compiler for it in my PasRISCV emulator, where the JIted code needs often to bailout to the interpreter for non-native-SIMDizable code cases. I hope that the RISC-V foundation can come up with a more clean and (2/3)

