This message is about the problem that I have asked about in my previous message,
https://obsproject.com/forum/threads/obs-studio-not-starting-in-debian-buster-please-help-me.100735/
but now I want to transform it into a bug report.
I have been investigating the problem, by debugging obs-studio with debug messages. It was caused by the fact that
the function
HasAudioDevices
in the source file window-basic-main.cpp never returning.
The problem was caused by the line
obs_property_t *devices = obs_properties_get(props, "device_id");
which never returned. For your information, outuput_id had the value "pulse_output_capture".
So, I guess that the problem was caused by a miss-configured pulse audio system.
I removed the pulse audios config files, and tried again and it worked !
It seems that the problem was that I had the line
default-server = 127.0.0.1
in /etc/pulse/client.conf
So my advise would be
1) add a log message at the beginning of the function HasAudioDevices like
blog(LOG_INFO, "YO: at the beginning HasAudioDevices");
so that it would be easier to detect if it happens to somebody else.
2) Try to make the parsing of pulse audio configuration more robust.
(I don't know exactly how obs-studio does that!)
My system is a 64 bit Debian GNU/Linux (buster).
# uname -a
Linux trinity 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
# uname -a
Linux trinity 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
I'am using pulse audio 12.2-4
The version of obs is 22.0.3+dfsg1-1 (from Debian) but the bug is also present in the development version from github (master) that I am using to debug it.
https://obsproject.com/forum/threads/obs-studio-not-starting-in-debian-buster-please-help-me.100735/
but now I want to transform it into a bug report.
I have been investigating the problem, by debugging obs-studio with debug messages. It was caused by the fact that
the function
HasAudioDevices
in the source file window-basic-main.cpp never returning.
The problem was caused by the line
obs_property_t *devices = obs_properties_get(props, "device_id");
which never returned. For your information, outuput_id had the value "pulse_output_capture".
So, I guess that the problem was caused by a miss-configured pulse audio system.
I removed the pulse audios config files, and tried again and it worked !
It seems that the problem was that I had the line
default-server = 127.0.0.1
in /etc/pulse/client.conf
So my advise would be
1) add a log message at the beginning of the function HasAudioDevices like
blog(LOG_INFO, "YO: at the beginning HasAudioDevices");
so that it would be easier to detect if it happens to somebody else.
2) Try to make the parsing of pulse audio configuration more robust.
(I don't know exactly how obs-studio does that!)
My system is a 64 bit Debian GNU/Linux (buster).
# uname -a
Linux trinity 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
# uname -a
Linux trinity 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
I'am using pulse audio 12.2-4
The version of obs is 22.0.3+dfsg1-1 (from Debian) but the bug is also present in the development version from github (master) that I am using to debug it.