Open redfast00 opened 1 year ago
I also have this error when playing to a null sink, it might be unrelated that there are two consumers of the same sink
I've never tried it with Chromium and also generally haven't used the recorder for ages.
Normally the "workflow" was creating a huge playlist on $music_service
. Then one started the recorder (while nothing is playing yet). Then one starts the playback. A few days later (when the playlist was completed) the server this setup ran on had a huge music collection on the HD. Unfortunately it ceased to the because $music_service
added random delays between the feedback from the D-Bus interface and the actual playback. That's when I've lost interest in this project. I've never tried it with two consumers. Normally this whole setup ran on a server (except for the initial experimenting).
It took me some initial tweaking to get it working with $music_service
. Most likely you'll have to do the same. The code isn't hard to understand (although also maybe not very thought through - I've coded this at university while waiting for the next lecture).
I"m trying to use this application to save audio played by Chromium on Linux. I get the following error:
dbus-soundrecorder seems to immediately stop the stream, and I have to manually restart it before it plays again, after which it goes to the next song, which has the same problem (but a slightly different error message). The alsa_output... sink are my headphones, the chromium.instance... was the application name found from dbus-monitor. I think this might have something to do with the fact that there are multiple consumers of the same sink.