Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PulseAudio not starting #7

Open
evelyn opened this issue Jul 16, 2012 · 2 comments
Open

PulseAudio not starting #7

evelyn opened this issue Jul 16, 2012 · 2 comments

Comments

@evelyn
Copy link

evelyn commented Jul 16, 2012

I'm sure it's my own problem, but I figured I'd write it out just in case:

[ 96.18s main info ] starting glc
[ 96.18s file info ] opening /home/matthew/Videos/secondlife.glc for writing stream (no sync)
[ 96.18s pack info ] compressing using QuickLZ
[ 96.18s pack info ] compressing using QuickLZ
[ 96.18s gl_capture info ] reading frames in GL_BGRA format
[ 96.19s main info ] glc running
[ 96.19s alsa_hook info ] starting capturing
[ 96.19s gl_capture info ] starting capturing
[ 96.19s gl_capture info ] refreshing color correction
[ 96.19s state dbg ] applying 96165401 usec time difference
[ 96.19s main info ] started capturing
[ 96.19s pulse error ] Connection failure: Connection terminated

[ 96.21s gl_capture dbg ] calculated capture area for video 1 is 1680x997+0+0
[ 96.21s gl_capture info ] creating/updating configuration for video 1
[ 96.21s gl_capture dbg ] video 1: 1680x997 (1680x997), 0x01 flags
[ 103.32s alsa_hook info ] stopping capturing
[ 103.32s gl_capture info ] stopping capturing
[ 103.32s main info ] stopped capturing
[ 474.48s main info ] closing glc
[ 474.48s alsa dbg ] closing
[ 474.48s opengl dbg ] closing
[ 474.48s pulse dbg ] closing
[ 474.48s log info ] log closed

It looks like Pulse doesn't even start up at all. o.o

I started the program using:
glc-capture -f 30 -o secondlife.glc -p -e 420jpeg -z quicklz -v 4 -l secondlife.log -j -b front exodus

@swick
Copy link
Owner

swick commented Jul 17, 2012

[ 96.19s pulse error ] Connection failure: Connection terminated

Seems like glc can't connect to the pulseaudio server. I guess it's something with your configuration and I'm no expert with pa at all. Maybe more information would help. Don't know though.

@iandall
Copy link

iandall commented Sep 24, 2012

I ran into this as well. It seems that if no audio devices is specified then the "first" input device (i.e. a microphone) is used. If there is no input device you get the symptoms you reported. If you want to record the output of the application you need to specify the right device with -a device. The command pactl list | grep '\.monitor' will show all the monitor devices, which are the devices to use to monitor the corresponding output. The output will potentially be a mix of streams. I expect it is possible to capture (just) a specific stream but I don't know how to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants