Test 1.1.x with pulseaudio

Description

As discussed in today's meeting, please test pulseaudio with 1.1.x and hammer it over a three day period. Please provide any results that come up from now through Friday. logs, etc.
Thanks!

Activity

Show:
Rubén Pérez
May 27, 2011, 3:15 PM

I scheduled recordings for a couple days and a half, sort of intensively. It turned out it was too much for our testing installation and everything collapsed on Thursday night-Friday early morning. Therefore I haven't seen the videos ingested correctly. At least, not all of them.
The first captures were 5, 10, 20 and 30 minutes long and made it to distribution without problems. I can only assume that any other recording did / would have done the same way.
However, the capture agent "survived" and was part of the problem: it kept trying to ingest the recordings, overloading the core. However, it seems the whole number of scheduled recordings worked, even though some of them never got to the core server.

In conclussion, I believe that pulsesrc "may be" more robust than alsasrc, but I wouldn't bet on it, because this bug seems pretty ellusive. AFAI can tell, though, no recordings got blocked, and since there seems to be a way to control pulseaudio from CLI, perhaps it's a good move to switch to pulseaudio. I only hope the bug doesn't reproduce later.

A
May 27, 2011, 9:23 PM
Edited

what steps did you take to enable pulseaudio and control it via cli? Can you document these?

Please expand upon the ingest problem? Logs? Were there any files in ingest-tmp?

Christopher Brooks
May 31, 2011, 2:44 PM

The big things we need are to change the input we are capturing from (mic or line in) and changing the audio levels from those inputs. Essentially, the same as we have for pulse at http://opencast.jira.com/wiki/display/MH/Capture+Agent+Configuration+(Trunk)

A
June 7, 2011, 7:11 PM

Ruben will include directions as to how to install, and include this in init so pulseaudio starts as user matterhorn. Without this, it's impossible to change via cli. He'll include instructions in this ticket to test.

Rubén Pérez
June 7, 2011, 7:49 PM

Sorry, I used ticket instead.

Just one more comment to what was said over there: if we wanted pulseaudio to start with matterhorn we can just add a line "pulseaudio --start" and redirect the output of this operation to /dev/null (or the log file, doesn't matter): that way we wouldn't see error messages, should pulseaudio not be installed, and would make sure it starts, should it be installed.

Assignee

Rubén Pérez

Reporter

A

Tags (folksonomy)

None

Components

Fix versions

Affects versions

Priority

Critical
Configure