You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Info:
I'm using pipewire. This is my audio pipeline.
When my playback device is connected to either the source or the sink, I am able to hear audio. However when it's piped like this, it does not work.
The behavior is odd because it does work when I reinstall the application. Once it starts processing audio after a re-install, it will work fine until the audio processing stops. This causes the filter to disconnect itself
[13:08:58.832] [DBG] FilterContainer::on_link_changed::<lambda>: No app linked to our device wants to play. Unlinking our filters.
[13:08:58.832] [DBG] FilterContainer::disconnect_filters: disconnecting the JamesDsp filter from PipeWire
When a new audio source starts, the jamesdsp_filter node appears again, and the pipeline is still correct, but there is no audio output from the filter. There is no warning or errors that I'm encountering in the debug output that is shown by starting jamesdspfrom the CLI.
I have checked to make sure nothing has been muted.
The text was updated successfully, but these errors were encountered:
Issue:
No output audio from the application
Info:
I'm using pipewire. This is my audio pipeline.
When my playback device is connected to either the source or the sink, I am able to hear audio. However when it's piped like this, it does not work.
The behavior is odd because it does work when I reinstall the application. Once it starts processing audio after a re-install, it will work fine until the audio processing stops. This causes the filter to disconnect itself
When a new audio source starts, the
jamesdsp_filter
node appears again, and the pipeline is still correct, but there is no audio output from the filter. There is no warning or errors that I'm encountering in the debug output that is shown by startingjamesdsp
from the CLI.I have checked to make sure nothing has been muted.
The text was updated successfully, but these errors were encountered: