Dimitris Papaioannou
Dimitris Papaioannou
> Are they different forks or something? Yes > Using the git inputs causes cargo to try to fetch from the network, which doesn't work as it's building in a...
See #3 for why it's happening. I guess a toggle would be desirable
The sampling should be completely independent of the graphics. Every sample that PipeWire sends gets displayed. If you're viewing the graph of a video driver such as a screen or...
Does running with `--device=shm` work?
You ran `flatpak run --device=shm io.github.dimtpap.coppwr` right? (`--device=shm` goes before the ID) The problem is that the PipeWire socket is in the `/dev` directory, which Flatpak blocks from applications. You...
Relevant Alpine Linux documentation: https://wiki.alpinelinux.org/wiki/Wayland#XDG_RUNTIME_DIR
The screenshot is showing the graph view, which shows floating nodes, you decide where they are by moving them around. Is there a problem in other places?
I'd like to add better automatic placing of the graph nodes, but that is a bit complex and would take some time. > And not forced users into minutes of...
The graph has just undergone a rewrite by the way, if you'd like to re-check anything grab a build from [here](https://github.com/dimtpap/coppwr/actions/runs/17436916535)
What's the output of running `pw-cli info` for the node you want to capture? You can use `pw-cli ls` to find the ID of the node, then use that ID...