Demonstrative video: https://www.youtube.com/watch?v=3pCSyM6VzrU
audio-src.c: https://docs.pipewire.org/audio-src_8c-example.html
If I create a a node using the audio-src.c
example file and then pause the program running the node using Ctrl+Z, it jams all other audio. The node is modified to produce no audible sound in my case. I do not know if this an issue that should even be acknowledged, but I decided to file a report just in case.
Every time
All audio either cuts off or gets stuck in repeat
All other audio should continue working
pw-dump > pw-dump.log
: pw-dump.log
Antti Savolainen (ee821b3d) at 20 Feb 09:01
nls: add a compose sequence for asterism
... and 11 more commits
This was previously discussed about 5-3 years ago. #123
In the discussion there were two repositories that seemed to have achieved functional drivers, one by @jeffgoh
https://github.com/jeffgoh/libfprint
https://github.com/hrenod/libfprint
Would it be possible to go through these repositories to achieve functionality?
Antti Savolainen (041b5291) at 19 Feb 19:49
imDefLkup: Commit first info in XimCommitInfo
... and 10 more commits
Understandable. The portal is less than a year old after all.
https://flatpak.github.io/xdg-desktop-portal/docs/doc-org.freedesktop.portal.Clipboard.html
https://github.com/flatpak/xdg-desktop-portal/pull/852
Relevant links to the clipboard portal
Asking out of lack of knowledge, why would portal be a worse solution?
I've come across a couple of m4a files and they're not supported by pw-play
. Attempting to play them results in the following error message:
sndfile: failed to open audio file "End Times.m4a": Format not recognised.
error: open failed: Input/output error
pw-dump > pw-dump.log
: pw-dump.log
Hey, may I poke about the status of this issue?
There was a wiki page that included an asterism so I thought to create a compose sequence for it.
Antti Savolainen (9693abc0) at 08 Jan 03:07
nls: add a compose sequence for asterism
Antti Savolainen (723896f4) at 08 Jan 03:04
nls: add compose sequence for asterism
Antti Savolainen (82d989a9) at 08 Jan 02:58
Update file Compose.pre
In the qpwgraph issue tracker they said that separating the two was a deliberate decision because pro-audio people like to have speakers and their monitor separate.
I see. I wouldn't want to detract from the setups of more professional people so an option would be optimal.
I would personally prefer that the speaker monitor was in the speaker node, similar to the OBS monitors.
Thanks, I'll let them know.
In the pipewire issue the developers noted that in my pw-dump the playback and monitor ports share the same node.id
and qpwgraph should be able to find the parent node correctly.
PipeWire version (pipewire --version
): 0.3.85
Distribution and distribution version: Arch Linux
Desktop Environment: KDE Plasma
Kernel version: 6.6.0-273-tkg-eevdf
A demonstrative image of the issue in qpwgraph
Issue I made on the qpwgraph issue tracker rncbc/qpwgraph#94 (comment 2171428)
In qpwgraph it is an issue that I am unable to differentiate microphone input and speaker monitors at a glance value. It would be better if all of the speaker ports were owned by the same node.
Always
Speaker monitor and microphone look the same
Speaker monitor should be tied to the same node as its input
pw-dump > pw-dump.log
:
pw-dump.log