![]() ![]() the noise plays even when there is no active client stream until the ALSA HW node itself is closed by PW (and it may resume once the node is re-opened without PW/WP daemon restart). ![]() sometimes (possibly due to a HW node reconfigure) the stream and subsequent device node suspend will clear the fault but most often the only solution is to execute systemctl -user restart pipewire.socket.at least at default log level no obvious or corroborating error messages have been observed or reported.all reported devices that exhibit this issue have so far been USB devices.the noise can suddenly begin in the middle of a stream that has played without user interruption for for 1-2 minutes.people reporting this all seem to have either explicitly allowed multiple sample rates or are implicitly using them due to SPA ALSA plugin thinking the HW can't use the one configured rate, so the device gets reconfigured at some point ( #2620 (closed)).the intended audio signal can often be heard either "over" or "under" the noise. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |