#26 ASR audio files not being written in certain situations

[David Suendermann-Oeft]

Working on the call browser (see Ticket #15 https://sourceforge.net/p/halef/tickets/15 ) disclosed that, at times, a recognition event does not store the actual audio file. This is an issue known from the Halef integration of the alcoholic language classifier. Here is some background information on this problem copied from e-mail conversations earlier this year:

"So, here is what seems to be going on:

There are five rec engines in the pool which are activated one after the other call-by-call. Now, Engines 1 to 3 seem to be doing fine recording the audio, Engines 4 and 5 are failing.

As a quick fix, I could try to reconfigure Cairo to use only 3 engines. @AHMED, do you have an idea what is going on? How do I reduce the number of engines? I am attaching the Cairo log file and also an excerpt in the Excel spreadsheet showing a successful (left) and a unsuccessful (right) attempt. "

"As a quick fix, I activated only three recognizers by altering the Cairo config in

/home/tjr/halef-halef-cairo/cairo-VM/zanzibar-SNAPSHOT/config/cairo-config.xml

At least, I seem not to get the duplicate problems anymore, i.e., all audio recordings seem to be present. Halef is currently a little slow, though.

On the long run, it will be necessary to see why the recording of Engines 4+ does not work properly. "

[David Suendermann-Oeft]

Dear Alex,

Did you have a chance to look into this yet?

Yours,

DSO

[Alexei V. Ivanov]

Did you have a chance to look into this yet?

This one is next on my list.

[Alexei V. Ivanov]

I have looked into the code and config files. Here are my tentative findings:

1. Altering number of engines in halef-cairo/cairo-VM/zanzibar-SNAPSHOT/config/cairo-config.xml DOES AFFECT the launch configuration. E.g. setting this number to 3 will make recording always to work, however, at the cost of the pool reduction.

2. I have seen various parameters that alter recording behaviour, including those supposedly binding the Recorders to the Recognizers. However, the alternated configuration has failed to propagate to the engine.

I will keep looking at this issue during Kaldi engine integration.