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
SongRec 0.4.2 crashes when changing, activating or deactivating the audio source.
I've read #58 already and installed package pulseaudio-utils so pactl command is available. Is this a dependency for SongRec not mentioned in the install instructions? Nevertheless, installing it didn't fix the issue.
As you can see from the console output below I have already installed pipewire ver 1.0.3.
Songrec is the single audio program I've met by now not able to connect to the pipewire sound server monitors properly, and it doesn't show up in qpwgraph either, so I can't rewire its input to the proper output therein, while e.g. audacity and other programs do show up when running e.g. a recording; they can be observed therein connecting to one of the monitors on their own, while SongRec doesn't turns up at all.
It doesn't make any difference whether I set the profile in pavucontrol to pro audio or or to analog stereo duplex, the issue stays present.
Also it doesn't make any difference whether audacity, vmpk, qsynth/fluidsynth, pavucontrol, firefox, qpwgraph or other audio programs are running or not, nor from which program the sound is played.
The Audio input pulldown menu in Songrec shows the following entries (which look correct):
Internes Audio Pro (or Internes Audio Analog Stereo)
Monitor of Cedar HDMI Audio [...] Digital Stereo
Monitor of Internes Audio Pro (or Monitor of Inernes Audio Analog Stereo)
Monitor of Internes Audio Pro 1 (or none)
When selecting Internes Audio Pro (or Internes Audio Analog Stereo) instead of one of the monitors, the checkbox is reset from Speakers to Microphone automatically.
But even when the Monitors are selectable, they won't connect.
Remarkable detail might be: When running for the first time after reboot, Songrec connects properly for a single run to the preselected audio source, whichever this might be. Then there is no complaint about DeviceNotAvailable and it properly recognises the music. Only from a second run onwards, and also when you need to switch to another audio source in the first run, this issue occurs, and it seems it can be only solved by full rebooting, to make Songrec work again for a single request.
Also, on the first run of Songrec (when it is able to connect) you can observe the level indivator in its window quiver a bit, independend on what input source is selected, while on all the next runs it is dead until you reboot (while the respective indicators in other programs, e.g. pavucontrol, still work properly). Only Songrec seems to be affected from this strange sudden inavailability of the devices.
Just a suspicion: Is it possible Songrec doesn't free up a device once it had used it, so when calling it for another request or when switching forth and back between the devices it can't connect to the very audio devices it has used before, so it crashes when trying to access them again?
Background info:
Songrec was installed by the command from your readme.md:
(Same result when compiling it after cloning your repo to the local drive and using the other method. Flatpak install wasn't tested, since flatpaks aren't supported by the OS, these are known to work unreliable.)
$ songrec --version
SongRec 0.4.2
$ RUST_BACKTRACE=1 songrec
ALSA lib pcm_dsnoop.c:566:(snd_pcm_dsnoop_open) unable to open slave
thread '<unnamed>' panicked at /home/Robin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/songrec-0.4.2/src/core/microphone_thread.rs:55:60:
Failed to get default input config: DeviceNotAvailable
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: songrec::core::microphone_thread::microphone_thread
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at /home/Robin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/songrec-0.4.2/src/gui/main_window.rs:589:75:
called `Result::unwrap()` on an `Err` value: SendError { .. }
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: <O as gtk::auto::button::ButtonExt>::connect_clicked::clicked_trampoline
4: <unknown>
5: g_signal_emit_valist
6: g_signal_emit
7: <unknown>
8: <unknown>
9: g_signal_emit_valist
10: g_signal_emit
11: <unknown>
12: <unknown>
13: <unknown>
14: g_signal_emit_valist
15: g_signal_emit
16: <unknown>
17: g_cclosure_marshal_VOID__BOXEDv
18: <unknown>
19: g_signal_emit_valist
20: g_signal_emit
21: <unknown>
22: <unknown>
23: <unknown>
24: gtk_event_controller_handle_event
25: <unknown>
26: <unknown>
27: <unknown>
28: g_signal_emit_valist
29: g_signal_emit
30: <unknown>
31: <unknown>
32: gtk_main_do_event
33: <unknown>
34: <unknown>
35: g_main_context_dispatch
36: <unknown>
37: g_main_context_iteration
38: g_application_run
39: <O as gio::application::ApplicationExtManual>::run
40: songrec::gui::main_window::gui_main
41: songrec::main
Issue Description:
SongRec 0.4.2 crashes when changing, activating or deactivating the audio source.
I've read #58 already and installed package pulseaudio-utils so pactl command is available. Is this a dependency for SongRec not mentioned in the install instructions? Nevertheless, installing it didn't fix the issue.
As you can see from the console output below I have already installed pipewire ver 1.0.3.
Songrec is the single audio program I've met by now not able to connect to the pipewire sound server monitors properly, and it doesn't show up in qpwgraph either, so I can't rewire its input to the proper output therein, while e.g. audacity and other programs do show up when running e.g. a recording; they can be observed therein connecting to one of the monitors on their own, while SongRec doesn't turns up at all.
It doesn't make any difference whether I set the profile in pavucontrol to pro audio or or to analog stereo duplex, the issue stays present.
Also it doesn't make any difference whether audacity, vmpk, qsynth/fluidsynth, pavucontrol, firefox, qpwgraph or other audio programs are running or not, nor from which program the sound is played.
The Audio input pulldown menu in Songrec shows the following entries (which look correct):
When selecting Internes Audio Pro (or Internes Audio Analog Stereo) instead of one of the monitors, the checkbox is reset from Speakers to Microphone automatically.
But even when the Monitors are selectable, they won't connect.
Remarkable detail might be: When running for the first time after reboot, Songrec connects properly for a single run to the preselected audio source, whichever this might be. Then there is no complaint about DeviceNotAvailable and it properly recognises the music. Only from a second run onwards, and also when you need to switch to another audio source in the first run, this issue occurs, and it seems it can be only solved by full rebooting, to make Songrec work again for a single request.
Also, on the first run of Songrec (when it is able to connect) you can observe the level indivator in its window quiver a bit, independend on what input source is selected, while on all the next runs it is dead until you reboot (while the respective indicators in other programs, e.g. pavucontrol, still work properly). Only Songrec seems to be affected from this strange sudden inavailability of the devices.
Just a suspicion: Is it possible Songrec doesn't free up a device once it had used it, so when calling it for another request or when switching forth and back between the devices it can't connect to the very audio devices it has used before, so it crashes when trying to access them again?
Background info:
Songrec was installed by the command from your readme.md:
(Same result when compiling it after cloning your repo to the local drive and using the other method. Flatpak install wasn't tested, since flatpaks aren't supported by the OS, these are known to work unreliable.)
Running with pipewire set to analog stereo duplex
Running with pipewire set to pro audio:
System info:
antiX 23.1 full runit 64 bit (Live)
Please let me know if you need further information.
The text was updated successfully, but these errors were encountered: