OK so you can without v4l2loopback.

Smoke test:

gst-launch-1.0 \
    videotestsrc ! \
    video/x-raw,format=YUY2 ! \
    pipewiresink mode=provide \
    stream-properties="properties,media.class=Video/Source,media.role=Camera"

iPhone/Airplay:

uxplay -vs 0 -vrtp "config-interval=1 ! udpsink host=127.0.0.1 port=6000"

gst-launch-1.0 -v \
  udpsrc port=6000 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H264,payload=96" ! \
  rtph264depay ! decodebin ! videoconvert ! \
  video/x-raw,format=YUY2 ! \
  pipewiresink mode=provide \
  stream-properties="properties,media.class=Video/Source,media.role=Camera,node.description=iPhone Camera"

Test page used: mozilla.github.io/webrtc-landing/gum_test.html

In Firefox the config option you’re looking for is called media.webrtc.camera.allow-pipewire.

Does kernel.org have Matrix? This use would be really mainly for kernel stuff.

And actually if I want personal Matrix, I'd like to create a separate one for that.

RISC-V with MMU has neither complete spec: https://marcin.juszkiewicz.com.pl/2026/03/10/risc-v-is-sloooow/

For open source to surive, I think there should be radical shift towards wider use of copyleft licenses. This is the reality now, and it is better to accept it. And BTW, I was never a huge GPL advocate before.

How to tackle this with Rust and especially cargo, is an open question that needs to be resolved.

Throwing one potential solution: theoretically cargo could detect LGPL in dependency chains and make DSOs of these crates, which would be piggybacked into a virtual filesystem in the executable.

I'm not sure tho does that still comply for LGPL 2.1 when used e.g., in proprietary context.

There's also ABI work ongoing to get a stable DSO ABI for Rust but perhaps distribution problem could be resolved without resolving the ABI problem?

I totally get now why Logic Pro is AU-only. Having multiple plugin hosts in a DAW has devastative effect on latency compensation.

By having only CLAP latency compensation becomes a problem, which is elegant to resolve, not least because the standard has this inevitable reality recognized and addressed.

Thus, in my world everything is CLAP :-)

#openSUSE is dropping pcr-oracle in Full Disk Encryption #FDE. systemd-pcrlock now handles #TPM2 policy, fixing rollback attacks and simplifying maintenance. Migration is just two commands! 🔒🐧 Find out more. #Linux https://news.opensuse.org/2026/03/11/dropping-pcr-oracle/

It has finally crystalized me what I'm really doing with my leisure time activity since early Fall :-)

"A Linux-focused DAW built from scratch around its own desktop-like UI, deterministic rendering and input handling, a CLAP-only plugin architecture, and persistent CoW snapshot-based history — all aimed at delivering extremely accurate low-latency behavior and eventually industry-leading audio/MIDI routing."

It makes total sense to me now that it is on paper.

#linux #audio #dsp #musicproduction

-0.8309720144822054 + -0.18479928945814048i at zoom 1.1482443609e+12.

Last glitches fixed. I've fully realized a binary DAW project format, which does not have concept of "saving" or "backup files".

Combining the best features of tracker modules and modern developments of file system snapshots. I like how opposite poles these topics are but this actually works :-)

daw making is sick if you get into it. like model railroads type of madness.

i find myself happily making little knob and slider widgets to my UI framework for the use of my clap plugins. and still not bored.

I did read some recentish publications on latency compensaiton, studied clap, and realized that if I fix up to everything is clap I can make things sync really well. Worts case is when you have multiple hosts and bridges and whanot.

How much water do the data centres use? It's a secret.

Do you want Immortan Joes? Because this is how you get Immortan Joes. Roanoke gets its drinking water from Carvins Cove Reservoir. The locals tried to find out just how much water Google would be...
https://jwz.org/b/yk4G

My new guidelines for a new open source project in 2026:

1. Do not publish your test suite.
2. Delay the initial public repository as far away towards future as possible.
3. Do not aim for cross-os portability. Aim for cross-os non-portability.
4. Do not provide any other documentation except minimal man page and README. Less detailed documentation is better documentation.

In my DAW project I apply these best practices and levaraging Pipewire and Linux without any shim layers and at full scale will address the bullet three :-)

Dropped macOS/CoreAudio support from my DAW because of limited time and I want to see what you can accomplish with Linux-exclusive e.g., by taking full advantage of syscalls and Pipewire. Cross-architecture on the other hand is a high priority.

https://www.newscientist.com/article/2517389-human-brain-cells-on-a-chip-learned-to-play-doom-in-a-week/

My strategy to AI theft is to move the release of the source code as far away in time as possible. E.g, this is the approach for my DAW. I'll do the whole thing privately until it is just great enough to get the grip. This builds the community at fast rates, which also mitigates ther risk, and provides governance. It will be GPLv3 but as a in-dev project I'm more vulnerable.

some time ago i (half) joked that the only job #llm can replace outright is the CEO.

today i attended an earnings call where a synthetised voice of our CEO read multi-page long table of numbers from an official financial document, according to a script prepared by claude, over a single slide titled "company earnings 2025" - to a room full of employees who commuted to the office to watch it in person. there was no management present or even shown on the screen.

it was the most disturbed dystopian fucking thing i've experienced in my career of working for soul-crushing corporations.

The cat is out of the box: @matrix is looking for a new Thib!

If you think you can be a good fit for the role, please send me an email explaining why and attach your CV.

If you tick most of the boxes but not all, please reach out nonetheless. It’s a tall order, but we have fantastic volunteers and a great handbook to help you settle into the role.

https://matrix.org/jobs/devrel/

#FediHire #DevRel

4️⃣ Here's the 4th post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

When running code from OS trees, for example in containers, or when booting a full OS in a VM or on bare-metal it's often very useful to put together the basic OS from multiple overlayfs-style layers (directory-backed or backed by DDIs), plus some additional bind mounts, and possibly a tmpfs or two mounted to the right places to get ephemeral or partially ephemeral behaviour.

This my main UI reference or something I will taken now a lot of inspiration from at least because Octamed is superb and nice to use. And stands time just like Vim :-)

1. Octamed was made by a Finn Teijo Kinnunen.
2. Had major share on invention of such electronic music genres at their epoch such as breakbeat, jungle and drum'n'bass.
3. Still widely used as it does the job and has predictability unreachable on a signal chain with adaptive latency prevention algorithms, and especially with hardware samplers and such this makes ones life better.
4. I like it too a lot, it's great for what it does :-)

That is next 6 months at least because I want my tracker to level that I can do a full track with no other tools, and it is surprising how bottomless pit different usage patterns are (and not necessarily bugs, something just works or doesn't). And now that I actually have really good design and implementation for the engine it makes me less eager to less, it's fun to try things out :---)

#octamed #amiga

TTT is my first appy app ever. Never done any so far. I hope this does not happen too often :-) I waited for years someone to make not exactly "chiptune tracker" but neither "renoise". Never happened so there was no choices, and also Caustic died. In the age of all this web vomit (frameworks? i don't know what they are) ,and generally complicated software configurations, you can still do cool stuff with plain C and some assembly magic... It's great.