[GH-ISSUE #163] No audio on playback #119

Closed
opened 2026-02-28 14:30:45 +03:00 by kerem · 11 comments
Owner

Originally created by @omnituensaeternum on GitHub (Aug 31, 2021).
Original GitHub issue: https://github.com/jpochyla/psst/issues/163

[2021-08-31T23:01:21Z INFO  psst_gui::data::config] loading config: "/home/User/.config/Psst/config.json"
[2021-08-31T23:01:21Z INFO  psst_core::cache] using cache: "/home/User/.cache/Psst"
[2021-08-31T23:01:21Z INFO  psst_gui::data::config] saved config: "/home/User/.config/Psst/config.json"
[2021-08-31T23:01:21Z INFO  psst_core::access_token] access token expired, requesting
[2021-08-31T23:01:29Z INFO  psst_core::access_token] access token expired, requesting
[2021-08-31T23:01:29Z INFO  psst_core::audio_file] blocked at 7871328
[2021-08-31T23:01:29Z INFO  psst_core::audio_file] blocked at 7904096
[2021-08-31T23:01:29Z INFO  psst_core::audio_file] blocked at 7910408
[2021-08-31T23:01:29Z INFO  psst_core::audio_file] blocked at 7926792
[2021-08-31T23:01:29Z INFO  psst_core::audio_player] starting playback
[2021-08-31T23:01:29Z INFO  psst_gui::controller::playback] playing
[2021-08-31T23:01:40Z INFO  psst_core::audio_player] pausing playback
[2021-08-31T23:01:41Z INFO  psst_core::audio_player] resuming playback
[2021-08-31T23:01:45Z INFO  psst_core::audio_file] blocked at 9059660
[2021-08-31T23:01:46Z INFO  psst_core::audio_file] blocked at 9076044
[2021-08-31T23:01:46Z INFO  psst_core::audio_file] blocked at 9092428
[2021-08-31T23:01:46Z INFO  psst_core::audio_file] blocked at 9098740
[2021-08-31T23:01:46Z INFO  psst_core::audio_file] blocked at 9115124
[2021-08-31T23:01:46Z INFO  psst_core::audio_player] starting playback
[2021-08-31T23:01:46Z ERROR psst_core::audio_output] failed to start device: generic
[2021-08-31T23:01:46Z INFO  psst_gui::controller::playback] playing
[2021-08-31T23:02:02Z INFO  psst_core::audio_player] pausing playback

Recently Updated my system and preformed a restart.
I tried reinstalling, and I got the same results.

Originally created by @omnituensaeternum on GitHub (Aug 31, 2021). Original GitHub issue: https://github.com/jpochyla/psst/issues/163 ``` [2021-08-31T23:01:21Z INFO psst_gui::data::config] loading config: "/home/User/.config/Psst/config.json" [2021-08-31T23:01:21Z INFO psst_core::cache] using cache: "/home/User/.cache/Psst" [2021-08-31T23:01:21Z INFO psst_gui::data::config] saved config: "/home/User/.config/Psst/config.json" [2021-08-31T23:01:21Z INFO psst_core::access_token] access token expired, requesting [2021-08-31T23:01:29Z INFO psst_core::access_token] access token expired, requesting [2021-08-31T23:01:29Z INFO psst_core::audio_file] blocked at 7871328 [2021-08-31T23:01:29Z INFO psst_core::audio_file] blocked at 7904096 [2021-08-31T23:01:29Z INFO psst_core::audio_file] blocked at 7910408 [2021-08-31T23:01:29Z INFO psst_core::audio_file] blocked at 7926792 [2021-08-31T23:01:29Z INFO psst_core::audio_player] starting playback [2021-08-31T23:01:29Z INFO psst_gui::controller::playback] playing [2021-08-31T23:01:40Z INFO psst_core::audio_player] pausing playback [2021-08-31T23:01:41Z INFO psst_core::audio_player] resuming playback [2021-08-31T23:01:45Z INFO psst_core::audio_file] blocked at 9059660 [2021-08-31T23:01:46Z INFO psst_core::audio_file] blocked at 9076044 [2021-08-31T23:01:46Z INFO psst_core::audio_file] blocked at 9092428 [2021-08-31T23:01:46Z INFO psst_core::audio_file] blocked at 9098740 [2021-08-31T23:01:46Z INFO psst_core::audio_file] blocked at 9115124 [2021-08-31T23:01:46Z INFO psst_core::audio_player] starting playback [2021-08-31T23:01:46Z ERROR psst_core::audio_output] failed to start device: generic [2021-08-31T23:01:46Z INFO psst_gui::controller::playback] playing [2021-08-31T23:02:02Z INFO psst_core::audio_player] pausing playback ``` Recently Updated my system and preformed a restart. I tried reinstalling, and I got the same results.
kerem 2026-02-28 14:30:45 +03:00
  • closed this issue
  • added the
    bug
    linux
    labels
Author
Owner

@jpochyla commented on GitHub (Sep 1, 2021):

What OS are you on?

<!-- gh-comment-id:910392101 --> @jpochyla commented on GitHub (Sep 1, 2021): What OS are you on?
Author
Owner

@jacksongoode commented on GitHub (Sep 1, 2021):

Was debugging this issue last night (Fedora 34, pipewire). I think it's related to the fact that the buffersize for psst is too low (at least compared to other media players).

Here is an output of pw-top:

QUANT   RATE    WAIT     BUSY    W/Q   B/Q   ERR
256     48000   253.2µs  60.6µs  0.05  0.01  0    alsa_output.usb-Apple__Inc._USB-C_to_3.5mm_Headphone_Jack_Adapter_DWH035200SQJKLTAA-00.analog-stereo
256     48000   100.8µs  13.9µs  0.02  0.00  0    + psst-gui
3969    44100   133.7µs  58.9µs  0.03  0.01  0    + Rhythmbox

Where, for some reason, psst is taking a very small buffer of 256 compared to other audio applications taking a generous amount more.

<!-- gh-comment-id:910463933 --> @jacksongoode commented on GitHub (Sep 1, 2021): Was debugging this issue last night (Fedora 34, pipewire). I think it's related to the fact that the buffersize for psst is too low (at least compared to other media players). Here is an output of `pw-top`: ``` QUANT RATE WAIT BUSY W/Q B/Q ERR 256 48000 253.2µs 60.6µs 0.05 0.01 0 alsa_output.usb-Apple__Inc._USB-C_to_3.5mm_Headphone_Jack_Adapter_DWH035200SQJKLTAA-00.analog-stereo 256 48000 100.8µs 13.9µs 0.02 0.00 0 + psst-gui 3969 44100 133.7µs 58.9µs 0.03 0.01 0 + Rhythmbox ``` Where, for some reason, psst is taking a very small buffer of 256 compared to other audio applications taking a generous amount more.
Author
Owner

@jpochyla commented on GitHub (Sep 1, 2021):

@jacksongoode miniaudio-tuning branch should increase the buffer size, can you check it out? From the output it also seems that miniaudio is using the alsa backend, correct?

<!-- gh-comment-id:910500028 --> @jpochyla commented on GitHub (Sep 1, 2021): @jacksongoode [miniaudio-tuning](https://github.com/jpochyla/psst/tree/miniaudio-tuning) branch should increase the buffer size, can you check it out? From the output it also seems that miniaudio is using the alsa backend, correct?
Author
Owner

@jacksongoode commented on GitHub (Sep 1, 2021):

@jpochyla Tried the new branch, it does increase the buffer size (now reporting 1440) but it's still running into the same issue. So it may be more of an issue with miniaudio perhaps as the conversation at #138 has lead me to believe. It seems replacing miniaudio with cpal fixed it for me (in pw-top the application is now reported as + PipeWire ALSA [psst-gui]).

<!-- gh-comment-id:910521458 --> @jacksongoode commented on GitHub (Sep 1, 2021): @jpochyla Tried the new branch, it does increase the buffer size (now reporting 1440) but it's still running into the same issue. So it may be more of an issue with `miniaudio` perhaps as the conversation at #138 has lead me to believe. It seems replacing `miniaudio` with `cpal` fixed it for me (in pw-top the application is now reported as `+ PipeWire ALSA [psst-gui]`).
Author
Owner

@etrigan63 commented on GitHub (Sep 5, 2021):

I can confirm this. No audio playback in pipewire. I don't know how to switch it to cpal from miniaudio, however.

<!-- gh-comment-id:913222273 --> @etrigan63 commented on GitHub (Sep 5, 2021): I can confirm this. No audio playback in pipewire. I don't know how to switch it to `cpal` from `miniaudio`, however.
Author
Owner

@jacksongoode commented on GitHub (Sep 15, 2021):

I can confirm this. No audio playback in pipewire. I don't know how to switch it to cpal from miniaudio, however.

If you build the app with this fork's branch, you should be good to go!

<!-- gh-comment-id:919615324 --> @jacksongoode commented on GitHub (Sep 15, 2021): > I can confirm this. No audio playback in pipewire. I don't know how to switch it to `cpal` from `miniaudio`, however. If you build the app with [this fork's branch](https://github.com/H-M-H/psst/tree/cpal), you should be good to go!
Author
Owner

@jacksongoode commented on GitHub (Sep 15, 2021):

I wanted to follow up with this as the latest version of pipewire improved on the buffer/quantum configurations and I believe it resolved the issues here. Currently on version 0.3.35, would love to know if anyone else can confirm this behavior?

I believe it was related to this fix:

Small tweaks to how the quantum and rate are handled when nodes move
between drivers. Make node.lock-quantum work with node.latency

However, I am still getting around 6 "blocked" messages every time a new song is played:
[2021-09-15T07:25:56Z INFO psst_core::audio_file] blocked at 10525539

<!-- gh-comment-id:919766929 --> @jacksongoode commented on GitHub (Sep 15, 2021): I wanted to follow up with this as the latest version of pipewire improved on the buffer/quantum configurations and I believe it resolved the issues here. Currently on version 0.3.35, would love to know if anyone else can confirm this behavior? I believe it was related to [this fix](https://gitlab.freedesktop.org/pipewire/pipewire/-/releases#pipewire): > Small tweaks to how the quantum and rate are handled when nodes move between drivers. Make node.lock-quantum work with node.latency However, I am still getting around 6 "blocked" messages every time a new song is played: `[2021-09-15T07:25:56Z INFO psst_core::audio_file] blocked at 10525539`
Author
Owner

@jpochyla commented on GitHub (Sep 15, 2021):

I wanted to follow up with this as the latest version of pipewire improved on the buffer/quantum configurations and I believe it resolved the issues here. Currently on version 0.3.35, would love to know if anyone else can confirm this behavior?

Thanks!

However, I am still getting around 6 "blocked" messages every time a new song is played:

blocked means blocked on network, it is unrelated to audio output and will always be there when loading/preloading a track.

<!-- gh-comment-id:919785024 --> @jpochyla commented on GitHub (Sep 15, 2021): > I wanted to follow up with this as the latest version of pipewire improved on the buffer/quantum configurations and I believe it resolved the issues here. Currently on version 0.3.35, would love to know if anyone else can confirm this behavior? Thanks! > However, I am still getting around 6 "blocked" messages every time a new song is played: `blocked` means blocked on network, it is unrelated to audio output and will always be there when loading/preloading a track.
Author
Owner

@H-M-H commented on GitHub (Sep 29, 2021):

I am on pipewire 0.3.37 and playback is working again.

<!-- gh-comment-id:930037384 --> @H-M-H commented on GitHub (Sep 29, 2021): I am on pipewire 0.3.37 and playback is working again.
Author
Owner

@naufik commented on GitHub (Oct 5, 2021):

I am receiving no audio output with no pipewire and just pure pulseaudio when building from master.

~ % pulseaudio --version
pulseaudio 14.2-rebootstrapped

pavucontrol does not seem to detect audio coming from psst either. However the cpal patch in the fork works.

<!-- gh-comment-id:934182769 --> @naufik commented on GitHub (Oct 5, 2021): I am receiving no audio output with no pipewire and just pure pulseaudio when building from `master`. ``` ~ % pulseaudio --version pulseaudio 14.2-rebootstrapped ``` `pavucontrol` does not seem to detect audio coming from psst either. However the `cpal` patch in the fork works.
Author
Owner

@jpochyla commented on GitHub (Dec 24, 2021):

Closing because we've migrated to cpal, causing other problems, but most probably fixing this issue.

<!-- gh-comment-id:1000837010 --> @jpochyla commented on GitHub (Dec 24, 2021): Closing because we've migrated to `cpal`, causing other problems, but most probably fixing this issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/psst#119
No description provided.