<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
	<record>
		<datafield tag="980" ind1=" " ind2=" ">
			<subfield code="a">CONF</subfield>
		</datafield>
		<datafield tag="970" ind1=" " ind2=" ">
			<subfield code="a">Vijayasenan_ICASSP-2_2009/IDIAP</subfield>
		</datafield>
		<datafield tag="245" ind1=" " ind2=" ">
			<subfield code="a">Mutual Information based Channel Selection for Speaker Diarization of Meetings Data</subfield>
		</datafield>
		<datafield tag="700" ind1=" " ind2=" ">
			<subfield code="a">Vijayasenan, Deepu</subfield>
		</datafield>
		<datafield tag="700" ind1=" " ind2=" ">
			<subfield code="a">Valente, Fabio</subfield>
		</datafield>
		<datafield tag="700" ind1=" " ind2=" ">
			<subfield code="a">Bourlard, Hervé</subfield>
		</datafield>
		<datafield tag="711" ind1="2" ind2=" ">
			<subfield code="a">Proceedings of International conference on acoustics speech and signal processing</subfield>
		</datafield>
		<datafield tag="260" ind1=" " ind2=" ">
			<subfield code="c">2009</subfield>
		</datafield>
		<datafield tag="771" ind1="2" ind2=" ">
			<subfield code="d">April 2009</subfield>
		</datafield>
		<datafield tag="520" ind1=" " ind2=" ">
			<subfield code="a">This paper aims at investigating the use of Kullback-Leibler
(KL) divergence based realignment with application to speaker
diarization. The use of KL divergence based realignment operates
directly on the speaker posterior distribution estimates
and is compared with traditional realignment performed using
HMM/GMM system. We hypothesize that using posterior
estimates to re-align speaker boundaries is more robust than
gaussian mixture models in case of multiple feature streams
with different statistical properties. Experiments are run on
the NIST RT06 data. These experiments reveal that in case
of conventional MFCC features the two approaches yields the
same performance while the KL based system outperforms the
HMM/GMM re-alignment in case of combination of multiple
feature streams (MFCC and TDOA).</subfield>
		</datafield>
	</record>
</collection>