Meeting transcript:
speaker: D
text: And we already got the crash out of the way .
speaker: D
text: It did crash , so I feel much better , earlier .
speaker: F
text: Yeah .
speaker: E
text: Interesting .
speaker: F
text: Will you get the door ,
speaker: E
text: Hmm .
speaker: F
text: and <disfmarker> ?
speaker: F
text: OK .
speaker: D
text: OK , so um .
speaker: F
text: You collected an agenda , huh ?
speaker: D
text: I did collect an agenda .
speaker: D
text: So I 'm gonna go first .
speaker: D
text: Mwa - ha - ha !
speaker: D
text: It shouldn't take too long .
speaker: E
text: Yeah .
speaker: D
text: Um , so we 're pretty much out of digits .
speaker: D
text: We 've gone once through the set .
speaker: D
text: Um , so the only thing I have to do
speaker: F
text: No there 's only ten .
speaker: D
text: Yeah , that 's right .
speaker: D
text: so I <disfmarker> I just have to go through them
speaker: F
text: Well , OK .
speaker: D
text: and uh pick out the ones that have problems ,
speaker: D
text: and either correct them or have them re - read .
speaker: D
text: So we probably have like four or five more forms to be read , to be once through the set .
speaker: D
text: I 've also extracted out about an hour 's worth .
speaker: D
text: We have about two hours worth .
speaker: D
text: I extracted out about an hour 's worth
speaker: D
text: which are the f digits with <disfmarker> for which whose speaker have speaker forms ,
speaker: D
text: have filled out speaker forms .
speaker: D
text: Not everyone 's filled out a speaker form .
speaker: D
text: So I extracted one for speakers who have speaker forms
speaker: D
text: and for meetings in which the " key " file and the transcript files are parsable .
speaker: D
text: Some of the early key files , it looks like , were done by hand ,
speaker: D
text: and so they 're not automatically parsable
speaker: D
text: and I have to go back and fix those .
speaker: D
text: So what that means is we have about an hour of transcribed digits that we can play with .
speaker: D
text: Um ,
speaker: F
text: So you think two <disfmarker> you think two hours is the <disfmarker> is the total that we have ?
speaker: D
text: Liz <disfmarker>
speaker: D
text: Yep ,
speaker: D
text: yeah .
speaker: F
text: And you think we th uh ,
speaker: F
text: I <disfmarker> I didn't quite catch all these different things that are not quite right ,
speaker: F
text: but you think we 'll be able to retrieve the other hour , reasonably ?
speaker: D
text: Yes , absolutely .
speaker: F
text: OK .
speaker: D
text: So it 's just a question of a little hand - editing of some files
speaker: D
text: and then waiting for more people to turn in their speaker forms .
speaker: D
text: I have this web - based speaker form ,
speaker: D
text: and I sent mail to everyone who hadn't filled out a speaker form ,
speaker: D
text: and they 're slowly s trickling in .
speaker: F
text: So the relevance of the speaker form here , s
speaker: D
text: It 's for labeling the extracted audio files .
speaker: F
text: Oh , OK .
speaker: D
text: By speaker ID and microphone type .
speaker: F
text: Wasn't like whether they were giving us permission to use their digits or something .
speaker: D
text: No , I spoke with Jane about that
speaker: D
text: and we sort of decided that it 's probably not an issue that <disfmarker>
speaker: D
text: We edit out any of the errors anyway . Right ?
speaker: F
text: Yeah .
speaker: D
text: So the there are no errors in the digits ,
speaker: D
text: you 'll always read the string correctly .
speaker: D
text: So I can't imagine why anyone would care .
speaker: D
text: So the other topic with digits is uh ,
speaker: D
text: Liz would like to elicit different prosodics ,
speaker: D
text: and so we tried last week with them written out in English .
speaker: D
text: And it just didn't work at all
speaker: D
text: because no one grouped them together .
speaker: D
text: So it just sounded like many many more lines instead of anything else .
speaker: D
text: So in conversations with Liz and uh Jane we decided that if you wrote them out as numbers instead of words it would elicit more phone number , social security number - like readings .
speaker: D
text: The problem with that is it becomes numbers instead of digits .
speaker: D
text: When I look at this , that first line is " sixty one , sixty two , eighteen , eighty six , ten . "
speaker: D
text: Um , and so the question is does anyone care ?
speaker: D
text: Um , I 've already spoken with Liz and she feels that , correct me if I 'm wrong , that for her , connected numbers is fine ,
speaker: E
text: Mm - hmm .
speaker: D
text: as opposed to connected digits .
speaker: D
text: Um , I think two hours is probably fine for a test set ,
speaker: D
text: but it may be a little short if we actually wanna do training and adaptation and all that other stuff .
speaker: F
text: Yeah
speaker: F
text: Um , do um
speaker: F
text: you want different prosodics ,
speaker: F
text: so if you always had the same groupings you wouldn't like that ?
speaker: F
text: Is that correct ?
speaker: G
text: Well , we actually figured out a way to <disfmarker>
speaker: D
text: Yeah , the <disfmarker> the <disfmarker>
speaker: G
text: the <disfmarker> the groupings are randomly generated .
speaker: F
text: No but , I was asking if that was something you really cared about
speaker: F
text: because if it wasn't , it seems to me if you made it really specifically telephone groupings that maybe people wouldn't , uh , go and do numbers so much .
speaker: F
text: You know if it if it 's <disfmarker>
speaker: G
text: I think they may still do it ,
speaker: A
text: Uh <disfmarker>
speaker: G
text: um ,
speaker: F
text: Maybe some , but I probably not so much .
speaker: B
text: What about putting a hyphen between the numbers in the group ?
speaker: G
text: And <disfmarker>
speaker: F
text: Right ?
speaker: F
text: So if you <disfmarker> if <disfmarker> if you have uh
speaker: D
text: Six dash one , you mean ?
speaker: F
text: if you go six six six uh dash uh two nine three one .
speaker: G
text: I <disfmarker> well OK <disfmarker> I <disfmarker> it might help ,
speaker: G
text: I would like to g get away from having only one specific grouping .
speaker: F
text: That 's what I was asking , yeah .
speaker: G
text: Um , so if that 's your question ,
speaker: F
text: Yeah .
speaker: G
text: but I mean it seems to me that , at least for us , we can learn to read them as digits
speaker: G
text: if that 's what people want .
speaker: E
text: Yeah .
speaker: G
text: I <disfmarker> I 'm
speaker: E
text: Yeah .
speaker: G
text: don't think that 'd be that hard to read them as single digits .
speaker: E
text: I agree .
speaker: G
text: Um ,
speaker: G
text: and it seems like that might be better for you guys
speaker: G
text: since then you 'll have just more digit data ,
speaker: D
text: Right .
speaker: G
text: and that 's always a good thing .
speaker: G
text: It 's a little bit better for me too
speaker: D
text: Yep .
speaker: G
text: because the digits are easier to recognize .
speaker: G
text: They 're better trained than the numbers .
speaker: F
text: Right .
speaker: D
text: So we could just , uh , put in the instructions " read them as digits " .
speaker: G
text: Right . Right , read them as single digits ,
speaker: G
text: so sixty - one w is read as six one ,
speaker: E
text: Mm - hmm .
speaker: G
text: and if people make a mistake we <disfmarker>
speaker: D
text: How about " O " versus " zero " ?
speaker: F
text: I mean , the other thing is we could just bag it
speaker: F
text: because it 's <disfmarker> it 's <disfmarker>
speaker: F
text: it 's - I 'm not worrying about it
speaker: F
text: I mean , because we do have digits training data that we have from uh from OGI .
speaker: F
text: I 'm sorry ,
speaker: F
text: digits <disfmarker> numbers training that we have from OGI ,
speaker: F
text: we 've done lots and lots of studies with that .
speaker: F
text: And um .
speaker: G
text: But it 's nice to get it in this room with the acous
speaker: F
text: Yeah .
speaker: G
text: I mean <disfmarker> for <disfmarker> it 's <disfmarker>
speaker: F
text: No , no , I guess what I 'm saying is that
speaker: D
text: Just let them read it how they read it .
speaker: F
text: to some extent maybe we could just read them <disfmarker> have them read how <disfmarker> how they read it
speaker: F
text: and it just means that we have to expand our <disfmarker> our vocabulary out to stuff that we already have .
speaker: G
text: Right .
speaker: G
text: Well that 's fine with me as long as <disfmarker> It 's just that I didn't want to cause the people who would have been collecting digits the other way to not have the digits .
speaker: F
text: Yeah .
speaker: G
text: So <disfmarker>
speaker: F
text: We can go back to the other thing later .
speaker: F
text: I mean we s we <disfmarker> we 've <disfmarker> We can do this for awhile
speaker: G
text: OK .
speaker: F
text: and then go back to digits for awhile ,
speaker: F
text: or um .
speaker: F
text: Do yo I mean , do you want <disfmarker> do you want this <disfmarker> Do you need training data or adaptation data out of this ?
speaker: G
text: OK .
speaker: F
text: How much of this do you need ?
speaker: F
text: with uh the <disfmarker>
speaker: G
text: It 's actually unclear right now .
speaker: G
text: I just thought well we 're <disfmarker> if we 're collec collecting digits , and Adam had said we were running out of the TI forms , I thought it 'd be nice to have them in groups ,
speaker: G
text: and probably , all else being equal , it 'd be better for me to just have single digits
speaker: G
text: since it 's , you know , a recognizer 's gonna do better on those anyway ,
speaker: F
text: OK .
speaker: G
text: um , and it 's more predictable .
speaker: G
text: So we can know from the transcript what the person said and the transcriber , in general .
speaker: F
text: OK , well if you pre
speaker: G
text: But if they make mistakes , it 's no big deal
speaker: G
text: if the people say a hundred instead of " one OO " .
speaker: G
text: and also w maybe we can just let them choose " zero " versus " O " as they <disfmarker> as they like
speaker: G
text: because even the same person c sometimes says " O " and sometimes says " zero " in different context ,
speaker: F
text: Yeah .
speaker: G
text: and that 's sort of interesting .
speaker: G
text: So I don't have a Specific need
speaker: G
text: cuz if I did I 'd probably try to collect it , you know , without bothering this group ,
speaker: G
text: but If we can try it <disfmarker>
speaker: D
text: OK so <disfmarker> so I can just add to the instructions to read it as digits
speaker: D
text: not as connected numbers .
speaker: G
text: Right , and you can give an example
speaker: E
text: Mm - hmm .
speaker: G
text: like , you know , " six <disfmarker> sixty - one would be read as six one " .
speaker: D
text: Right .
speaker: G
text: And I think people will get it .
speaker: E
text: Mm - hmm .
speaker: E
text: And i actually it 's no more artificial than what we 've been doing with words .
speaker: E
text: I 'm sure people can adapt to this ,
speaker: G
text: Right , right .
speaker: E
text: read it single .
speaker: G
text: It 's just easier to read .
speaker: E
text: The spaces already bias it toward being separated .
speaker: G
text: Right .
speaker: E
text: And I know I 'm gonna find this easier than words .
speaker: D
text: Oh yeah , absolutely ,
speaker: G
text: OK
speaker: D
text: cognitively it 's much easier .
speaker: G
text: I also had a hard <disfmarker> hard time with the words ,
speaker: G
text: but then we went back and forth on that .
speaker: F
text: Yeah .
speaker: G
text: OK , so let 's give that a try
speaker: D
text: OK . And is the spacing alright or do you think there should be more space between digits and groups ?
speaker: F
text: OK .
speaker: G
text: and <disfmarker>
speaker: G
text: I mean what do other people think
speaker: D
text: Or is that alright ?
speaker: G
text: cuz you guys are reading <comment> them .
speaker: E
text: I think that i it 's fine .
speaker: E
text: I it <disfmarker> it <disfmarker> to me it looks like you 've got the func the idea of grouping and you have the grou the idea of separation
speaker: D
text: OK .
speaker: G
text: OK .
speaker: E
text: and , you know , it 's just a matter of u i the instructions , that 's all .
speaker: G
text: Great . OK .
speaker: G
text: Well let 's give it a try .
speaker: D
text: And I think there are about ten different gouping patterns
speaker: F
text: Let 's try it .
speaker: D
text: isn't that right , Liz ?
speaker: G
text: Righ - right , and you just <disfmarker> they 're randomly <nonvocalsound> generated and randomly assigned to digits .
speaker: D
text: That we did .
speaker: E
text: I did <disfmarker>
speaker: F
text: So we have <disfmarker>
speaker: E
text: Mm - hmm .
speaker: F
text: Sorry ,
speaker: E
text: Go ahead .
speaker: F
text: I <disfmarker> I was just gonna say , so we have in the vicinity of forty hours of <disfmarker> of recordings now .
speaker: F
text: And you 're saying two hours , uh , is digits ,
speaker: F
text: so that 's roughly the ratio then ,
speaker: F
text: something like twenty <disfmarker> twenty to one .
speaker: D
text: Yep .
speaker: F
text: Which I guess makes <disfmarker> makes sense .
speaker: F
text: So if we did another forty hours of recordings then we could get another couple hours of this .
speaker: D
text: Right .
speaker: F
text: Um , yeah like you say , I think a couple hours for a <disfmarker> for a <disfmarker> for a test <disfmarker> test set 's OK .
speaker: F
text: It 'd be nice to get , you know , more later
speaker: F
text: because we 'll <disfmarker> we might use <disfmarker> use this up , uh , in some sense ,
speaker: E
text: Mm - hmm .
speaker: F
text: but <disfmarker> but uh <disfmarker>
speaker: D
text: Right .
speaker: E
text: Yeah , I also would like to argue for that
speaker: E
text: cuz it <disfmarker> it seems to me that , um , there 's a real strength in having the same test replicated in <disfmarker> a whole bunch of times
speaker: E
text: and adding to that basic test bank .
speaker: D
text: Right .
speaker: E
text: Hmm ?
speaker: E
text: Cuz then you have , you know , more and more , u chances to get away from random errors .
speaker: E
text: And I think , um , the other thing too is that right now we have sort of a stratified sample with reference to dialect groups ,
speaker: E
text: and it might be <disfmarker> there might be an argument to be made for having uh f for replicating all of the digits that we 've done ,
speaker: E
text: which were done by non - native speakers
speaker: E
text: so that we have a core that totally replicates the original data set ,
speaker: E
text: which is totally American speakers ,
speaker: E
text: and then we have these stratified additional language groups overlapping certain aspects of the database .
speaker: D
text: Right .
speaker: D
text: I think that uh trying to duplicate , spending too much effort trying to duplicate the existing TI - digits probably isn't too worthwhile
speaker: D
text: because the recording situation is so different .
speaker: F
text: Yeah .
speaker: D
text: It 's gonna be very hard to be comparable .
speaker: E
text: Except that if you have the stimuli <pause> comparable , then it says something about the <disfmarker> the contribution of setting
speaker: F
text: No it 's <disfmarker> it 's not the same .
speaker: F
text: A little bit ,
speaker: E
text: and <disfmarker>
speaker: F
text: but the other differences are so major .
speaker: E
text: OK .
speaker: F
text: They 're such major sources of variance that it 's <disfmarker> it 's <disfmarker> it 's uh <disfmarker>
speaker: D
text: Yeah I mean read versus not .
speaker: E
text: What 's an example of a <disfmarker> of m some of the other differences ?
speaker: E
text: Any other a difference ?
speaker: F
text: Well i i individual human glottis <vocalsound> is going to be different for each one ,
speaker: E
text: OK .
speaker: F
text: you know , it 's just <disfmarker> There 's so many things .
speaker: E
text: OK .
speaker: F
text: it 's <disfmarker> it <disfmarker> and <disfmarker> and enunciation .
speaker: D
text: Well , and not just that ,
speaker: D
text: I mean the uh the corpus itself .
speaker: D
text: I mean , we 're collecting it in a read digit in a particular list ,
speaker: D
text: and I 'm sure that they 're doing more specific stuff .
speaker: D
text: I mean if I remember correctly it was like postman reading zipcodes and things like that .
speaker: F
text: TI - digits was ?
speaker: F
text: I thought <disfmarker> I thought it was read .
speaker: D
text: I thought so .
speaker: D
text: Was it read ?
speaker: F
text: Yeah , I think the reading zipcode stuff you 're thinking of would be OGI .
speaker: D
text: Oh , I may well be .
speaker: F
text: Yeah , no TI - digits was read in th in read in the studio I believe .
speaker: D
text: I haven't ever listened to TI - digits .
speaker: F
text: Yeah .
speaker: D
text: So I don't really know how it compares .
speaker: F
text: Yeah .
speaker: F
text: But it <disfmarker> but <disfmarker>
speaker: D
text: But <disfmarker> but regardless it 's gonna <disfmarker> it 's hard to compare cross - corpus .
speaker: F
text: It - it 's different people <pause> is the <disfmarker> is the core thing .
speaker: D
text: So .
speaker: F
text: And they 're different circumstances with different recording environment and so forth ,
speaker: E
text: OK , fine .
speaker: F
text: so it 's <disfmarker> it 's <disfmarker> it 's really pretty different .
speaker: F
text: But I think the idea of using a set thing was just to give you some sort of framework ,
speaker: F
text: so that even though you couldn't do exact comparisons , it wouldn't be s valid scientifically at least it 'd give you some kind of uh frame of reference .
speaker: F
text: Uh , you know it 's not <disfmarker>
speaker: E
text: OK .
speaker: B
text: Hey Liz , What <disfmarker> what do the groupings represent ?
speaker: B
text: You said there 's like ten different groupings ?
speaker: G
text: Right , just groupings in terms of number of groups in a line ,
speaker: G
text: and number of digits in a group ,
speaker: G
text: and the pattern of groupings .
speaker: B
text: Mm - hmm .
speaker: B
text: Are the patterns <disfmarker> like are they based on anything or
speaker: G
text: Um , I <disfmarker> I just roughly looked at what kinds of digit strings are out there ,
speaker: G
text: and they 're usually grouped into either two , three , or four , four digits at a time .
speaker: B
text: Oh .
speaker: G
text: And they can have ,
speaker: G
text: I mean , actually , things are getting longer and longer .
speaker: G
text: In the old days you probably only had three sequences , and telephone numbers were less , and so forth .
speaker: G
text: So , there 's between , um <disfmarker>
speaker: G
text: Well if you look at it , there are between like three and five groups ,
speaker: G
text: and each one has between two and four groupings
speaker: G
text: and <disfmarker>
speaker: G
text: I purposely didn't want them to look like they were in any kind of pattern .
speaker: B
text: Mmm .
speaker: G
text: So
speaker: D
text: And which group appears is picked randomly , and what the numbers are are picked randomly .
speaker: B
text: Mm - hmm .
speaker: G
text: Right .
speaker: D
text: So unlike the previous one , which I d simply replicated TI - digits , this is generated randomly .
speaker: B
text: Mmm , oh , OK .
speaker: A
text: Oh OK .
speaker: G
text: But I think it 'd be great i to be able to compare digits ,
speaker: G
text: whether it 's these digits or TI - digits , to speakers , um , and compare that to their spontaneous speech ,
speaker: G
text: and then we do need you know a fair amount of <disfmarker> of digit data
speaker: G
text: because you might be wearing a different microphone
speaker: G
text: and , I mean <disfmarker> so it 's <disfmarker> it 's nice to have the digits you know , replicated many times .
speaker: D
text: Mm - hmm .
speaker: G
text: Especially for speakers that don't talk a lot .
speaker: G
text: So <vocalsound> um ,
speaker: D
text: Yeah .
speaker: G
text: for adaptation .
speaker: G
text: No , I 'm serious ,
speaker: G
text: so we have a problem with acoustic adaptation ,
speaker: F
text: Yeah .
speaker: D
text: Yeah all we have for some people is digits .
speaker: A
text: Yeah .
speaker: G
text: and we 're not using the digit data now ,
speaker: G
text: but you know <disfmarker>
speaker: D
text: Oh , you 're not .
speaker: G
text: Not for adaptation , nope .
speaker: G
text: v W we 're not <disfmarker> we were running adaptation only on the data that we ran recognition on
speaker: G
text: and I 'd <disfmarker> As soon as someone started to read transcript number , that 's read speech
speaker: G
text: and I thought " well , we 're gonna do better on that ,
speaker: D
text: Oh I see .
speaker: G
text: that 's not fair to use " .
speaker: D
text: Oh yeah that 's true , absolutely .
speaker: G
text: But , it might be fair to use the data for adaptation ,
speaker: A
text: OK .
speaker: G
text: so .
speaker: G
text: So those speakers who are very quiet , <comment> shy <disfmarker>
speaker: D
text: That would be interesting to see whether that helps .
speaker: G
text: r Right <disfmarker>
speaker: D
text: Do you think that would help adapting on <disfmarker>
speaker: B
text: Like Adam ?
speaker: D
text: Yeah .
speaker: F
text: Yeah .
speaker: D
text: Yeah , I have a real problem with that .
speaker: G
text: Well , it sh I mean it 's the same micropho
speaker: G
text: see the nice thing is we have that in the <disfmarker> in the same meeting ,
speaker: D
text: Right .
speaker: F
text: Yeah .
speaker: G
text: and so you don't get <disfmarker>
speaker: D
text: Same <disfmarker> same acoustics ,
speaker: D
text: same microphone ,
speaker: D
text: same channel .
speaker: A
text: Yeah .
speaker: G
text: Right , and so I still like the idea of having some kind of <pause> digit data .
speaker: D
text: OK .
speaker: D
text: Good .
speaker: F
text: Yeah I mean , for the <disfmarker> for the um acoustic research ,
speaker: F
text: for the signal - processing , farfield stuff , I see it as <disfmarker> as <disfmarker> as the place that we start .
speaker: F
text: But , th I mean , it 'd be nice to have twenty hours of digits data ,
speaker: F
text: but <disfmarker> but uh the truth is I 'm hoping that we <disfmarker> we through the <disfmarker> the stuff that <disfmarker> that you guys have been doing as you continue that , we get , uh , the best we can do on the spontaneous stuff uh , uh nearfield ,
speaker: F
text: and then um , we do a lot of the testing of the algorithms on the digits for the farfield ,
speaker: F
text: and at some point when we feel it 's mature and we understand what 's going on with it then we <disfmarker> we have to move on to the spontaneous data with the farfield .
speaker: F
text: So .
speaker: G
text: The only thing that we don't have ,
speaker: E
text: Great .
speaker: G
text: I know this sounds weird ,
speaker: G
text: and maybe it 's completely stupid ,
speaker: G
text: but we don't have any overlapping digits .
speaker: D
text: Yeah , we talked about that a couple times .
speaker: G
text: An - yea I know it 's weird ,
speaker: G
text: but um <disfmarker>
speaker: A
text: Overlapping digits !
speaker: D
text: The <disfmarker> the problem I see with trying to do overlapping digits is the cognitive load .
speaker: G
text: Alright everybody 's laughing .
speaker: G
text: OK .
speaker: C
text: Dueling digits .
speaker: D
text: No it 's <disfmarker> it 's not stupid ,
speaker: D
text: it 's just <disfmarker> I mean , try to do it .
speaker: G
text: I 'm just talkin for the stuff that like Dan Ellis is gonna try ,
speaker: D
text: I mean , here , let 's try it .
speaker: G
text: you know , cross - talk cancellation .
speaker: F
text: Let 's try it .
speaker: D
text: You read the last line , I 'll read the first line .
speaker: G
text: OK .
speaker: A
text: Oh !
speaker: G
text: Wait <disfmarker> oh it <disfmarker> these are all the same forms .
speaker: F
text: Sixty - one .
speaker: G
text: OK <comment> So but <disfmarker>
speaker: D
text: So <disfmarker> so you read the last line , I 'll read the first line .
speaker: G
text: So you plu you plug your ears .
speaker: F
text: No , I 'll p
speaker: D
text: Oh I guess if you plug you 're ears you could do it ,
speaker: D
text: but then you don't get the <disfmarker> the same effects .
speaker: A
text: Yeah .
speaker: G
text: Well , what I mean is actually no not the overlaps that are well - governed linguistically ,
speaker: G
text: but the actual fact that there is speech coming from two people
speaker: G
text: and the beam - forming stuf
speaker: D
text: Yeah .
speaker: G
text: all the acoustic stuff that like Dan Ellis and <disfmarker> and company want to do .
speaker: D
text: Oh I see .
speaker: G
text: Digits are nice and well behaved ,
speaker: G
text: I mean
speaker: G
text: Anyway , it 's just a thought .
speaker: D
text: I guess we could try .
speaker: D
text: We could try doing some .
speaker: G
text: It <disfmarker> it would go faster .
speaker: B
text: Parallel .
speaker: G
text: It would take one around <comment> amount of ti
speaker: B
text: It 's the P - make of digit reading .
speaker: D
text: Well <disfmarker> Well OK . Well let 's try it .
speaker: G
text: That 's right .
speaker: G
text: I <disfmarker> I mea I 'm <disfmarker> I was sort of serious ,
speaker: G
text: but I really , I mean , I 'm <disfmarker> I don't feel strongly enough that it 's a good idea ,
speaker: F
text: See , y
speaker: D
text: You do the last line , I 'll do the first line .
speaker: G
text: so .
speaker: F
text: OK .
speaker: D
text: O . <comment> That 's not bad .
speaker: F
text: No , I can do it .
speaker: G
text: A and that prosody was great , by the way .
speaker: B
text: I couldn't understand a single thing you guys were saying .
speaker: E
text: I think it was numbers ,
speaker: E
text: but I 'm not sure .
speaker: G
text: It <disfmarker> it sort of sounded like a duet , or something .
speaker: A
text: Yeah .
speaker: B
text: Performance art .
speaker: F
text: Alright , let 's try three at once you <disfmarker> you pick one in the middle .
speaker: A
text: The Aurora theater .
speaker: G
text: OK .
speaker: F
text: Go .
speaker: G
text: I 'm sorry .
speaker: G
text: I 'm mean I think it 's doable ,
speaker: D
text: The poor transcribers
speaker: G
text: I 'm just <disfmarker>
speaker: D
text: they 're gonna hate us .
speaker: G
text: So , we <disfmarker> we could have a round like where you do two at a time ,
speaker: G
text: and then the next person picks up when the first guy 's done , or something .
speaker: A
text: So pairwise .
speaker: F
text: Oh like a round ,
speaker: F
text: yeah , like in a <disfmarker> a <disfmarker>
speaker: G
text: Like a ,
speaker: A
text: Yeah , just pairwise ,
speaker: F
text: yeah .
speaker: G
text: what do you call it ?
speaker: G
text: Li - a r like <disfmarker>
speaker: D
text: A round .
speaker: A
text: or
speaker: F
text: Row , row , row your boat .
speaker: C
text: Round .
speaker: A
text: yeah .
speaker: D
text: Mm - hmm .
speaker: F
text: Yeah .
speaker: G
text: yeah , like that .
speaker: F
text: OK .
speaker: B
text: It 's gonna require some coordination .
speaker: G
text: Then it would go like h twice as fast , or <pause> a third as fast .
speaker: G
text: Anyway , it 's just a thought .
speaker: E
text: You have to have a similar pace .
speaker: F
text: Yeah .
speaker: G
text: I 'm actually sort of serious if it would help people do that kind o
speaker: G
text: but the people who wanna work on it we should talk to them .
speaker: F
text: I don't think we 're gonna collect vast amounts of data that way ,
speaker: G
text: So .
speaker: D
text: Mmm .
speaker: F
text: but I think having a little bit might at least be fun for somebody like Dan to play around with ,
speaker: G
text: OK .
speaker: D
text: I think maybe if we wanted to do that we would do it as a separate session ,
speaker: F
text: yeah .
speaker: G
text: Yeah .
speaker: D
text: something like that
speaker: D
text: rather than doing it during a real meeting
speaker: D
text: and you know , do two people at a time
speaker: D
text: then three people at a time and things like that .
speaker: D
text: So .
speaker: G
text: Can try it out .
speaker: G
text: If we have nothing <disfmarker> if we have no agenda we could do it some week .
speaker: D
text: See <disfmarker> see what Dan thinks .
speaker: D
text: Yeah , right .
speaker: F
text: Yeah , yeah .
speaker: G
text: OK .
speaker: F
text: Spend the whole time reading digits with different qu quantities .
speaker: E
text: c c Can I can I have an another <disfmarker> another question w about this ?
speaker: D
text: I thought this was gonna be fast .
speaker: D
text: Oh well .
speaker: E
text: So , um , there are these digits ,
speaker: E
text: which are detached digits ,
speaker: E
text: but there are other words that contain the same general phon phoneme sequences .
speaker: E
text: Like " wonderful " has " one " in it
speaker: E
text: and <disfmarker> and Victor Borge had a <disfmarker> had a piece on this where he inflated the digits .
speaker: E
text: Well , I wonder if there 's , um , an if there would be a value in having digits that are in essence embedded in real words to compare in terms of like the articulation of " one " in " wonderful " versus " one " as a digit being read .
speaker: F
text: That 's " two " bad .
speaker: F
text: Yeah .
speaker: G
text: I 'm all " four " it .
speaker: E
text: There you go .
speaker: D
text: Not after I " eight " though .
speaker: F
text: Uh , they don't all work as well , do they ?
speaker: F
text: Hmm .
speaker: F
text: What does nine work in ?
speaker: D
text: Uh .
speaker: F
text: Uh ,
speaker: C
text: Nein !
speaker: C
text: You scream it .
speaker: D
text: Nein !
speaker: F
text: Oh . In German ,
speaker: D
text: You have to be German ,
speaker: B
text: It 's great for the Germans .
speaker: F
text: yeah .
speaker: A
text: That 's German , yeah .
speaker: G
text: Oh , oh !
speaker: D
text: yeah .
speaker: E
text: Nein .
speaker: F
text: That 's right !
speaker: A
text: Yeah .
speaker: D
text: Oh !
speaker: C
text: It only sounds w good when you scream it , though .
speaker: C
text: So .
speaker: F
text: I think everybody 's a little punchy here <vocalsound> today .
speaker: E
text: Well , I mean , I just wanted to offer that as a possible task
speaker: F
text: Yes .
speaker: E
text: because , you know , if we were to each read his embedded numbers words in sent in sentences
speaker: E
text: cuz it 's like an entire sketch he does
speaker: E
text: and I wouldn't take the inflated version .
speaker: E
text: So he talks about the woman being " two - derful " ,
speaker: E
text: and <disfmarker>
speaker: E
text: and <disfmarker> a But , you know , if it were to be deflated , just the normal word , it would be like a little story that we could read .
speaker: F
text: Mm - hmm .
speaker: E
text: I don't know if it would be useful for comparison ,
speaker: E
text: but it 's embedded numbers .
speaker: F
text: Well I don't know .
speaker: D
text: I think for something like that we 'd be better off doing like uh TIMIT .
speaker: F
text: Well I think the question is what the research is ,
speaker: F
text: so I mean , I presume that the reason that you wanted to have these digits this way is because you wanted to actually do some research looking at the prosodic form here .
speaker: D
text: Hmm .
speaker: G
text: Right , yeah .
speaker: F
text: Yeah OK .
speaker: F
text: So if somebody wanted to do that , if they wanted to look at the <disfmarker> the <disfmarker> the difference of the uh phones in the digits in the context of a word versus uh the digits <disfmarker> a <disfmarker> a non - digit word versus in digit word , uh that would be a good thing to do ,
speaker: F
text: but I think someone would have to express interest in that .
speaker: E
text: I see .
speaker: F
text: I think , to <disfmarker>
speaker: E
text: OK .
speaker: F
text: I mean if you were interested in it then we could do it , for instance .
speaker: E
text: OK , thank you .
speaker: E
text: Huh .
speaker: D
text: OK , are we done with digits ?
speaker: D
text: Um ,
speaker: D
text: We have ASR results from Liz ,
speaker: D
text: transcript status from Jane ,
speaker: D
text: and disk space and storage formats from Don .
speaker: D
text: Does <disfmarker> do we have any prefer preference on which way we wanna <disfmarker> we wanna go ?
speaker: G
text: Well I was actually gonna skip the ASR results part , in favor of getting the transcription stuff talked about
speaker: D
text: Mm - hmm .
speaker: G
text: since I think that 's more important to moving forward ,
speaker: G
text: but I mean Morgan has this paper copy
speaker: G
text: and if people have questions ,
speaker: G
text: um , it 's pretty preliminary in terms of ASR results
speaker: G
text: because we didn't do anything fancy ,
speaker: G
text: but I think e just having the results there ,
speaker: G
text: and pointing out some main conclusions
speaker: G
text: like it 's not the speaking style that differs ,
speaker: G
text: it 's the fact that there 's overlap that causes recognition errors .
speaker: G
text: And then , the fact that it 's almost all insertion errors ,
speaker: G
text: which you would expect
speaker: G
text: but you might also think that in the overlapped regions you would get substitutions and so forth ,
speaker: G
text: um , leads us to believe that doing a better segmentation , like your channel - based segmentation , or some kind of uh , echo cancellation to get basically back down to the individual speaker utterances would be probably all that we would need to be able to do good recognition on the <disfmarker> on the close - talking mikes .
speaker: D
text: Um , why don't you , if you have a hard copy , why don't you email it to the list .
speaker: A
text: So these <disfmarker>
speaker: G
text: So , that 's about the summary <disfmarker>
speaker: G
text: But this is <disfmarker> Morgan has this paper .
speaker: A
text: Yeah , yeah .
speaker: G
text: I mean he <disfmarker> he <disfmarker>
speaker: F
text: Yeah , so it 's the same thing ?
speaker: D
text: Oh it 's in the paper .
speaker: G
text: it <disfmarker> it 's that paper .
speaker: F
text: It 's the same thing I mailed to every everybody that w where it was ,
speaker: D
text: OK .
speaker: G
text: Yeah , yeah .
speaker: G
text: So , we basically , um , did a lot of work on that
speaker: D
text: OK then , it 's already been mailed .
speaker: F
text: yeah .
speaker: G
text: and it 's <disfmarker>
speaker: G
text: Let 's see , th
speaker: G
text: I guess the other neat thing is it shows for sure w that the lapel , you know within speaker is bad .
speaker: D
text: Horrible ?
speaker: G
text: And it 's bad because it picks up the overlapping speech .
speaker: A
text: So , your <disfmarker> your ASR results were run on the channels synchronized ,
speaker: G
text: Yes , cuz that 's all that w had been transcribed at the time ,
speaker: A
text: OK .
speaker: A
text: OK .
speaker: A
text: OK .
speaker: G
text: um
speaker: G
text: but as we <disfmarker> I mean I wanted to here more about the transcription .
speaker: G
text: If we can get the channel asynchronous or the <disfmarker>
speaker: A
text: Yeah .
speaker: G
text: the closer t
speaker: G
text: that would be very interesting for us
speaker: G
text: because we <disfmarker>
speaker: B
text: So if <disfmarker>
speaker: F
text: Yeah , that 's <disfmarker> that 's why I only used the part from use
speaker: A
text: Yeah .
speaker: F
text: which we had uh about uh about the alt over all the channels
speaker: A
text: Yeah .
speaker: G
text: Right .
speaker: G
text: That 's <disfmarker>
speaker: A
text: Yeah sure .
speaker: A
text: Yeah .
speaker: F
text: or mixed channel
speaker: F
text: rather mixed signal .
speaker: A
text: Yeah .
speaker: B
text: So if there was a segment of speech this long
speaker: G
text: cuz <disfmarker>
speaker: A
text: Yeah .
speaker: D
text: And someone said " oh " in the front <disfmarker> in the middle .
speaker: B
text: and oh and someone said " oh , " the whole thing was passed to the recognizer ?
speaker: A
text: There were several speakers in it ,
speaker: A
text: yeah .
speaker: G
text: That 's right . In fact I <disfmarker> I pulled out a couple classic examples in case you wanna u use them in your talk of
speaker: C
text: Mm - hmm .
speaker: B
text: That 's why there 's so many insertion errors ?
speaker: G
text: Chuck on the lapel ,
speaker: G
text: so Chuck wore the lapel three out of four times .
speaker: C
text: Mmm .
speaker: D
text: I noticed that Chuck was wearing the lapel a lot .
speaker: G
text: Um , yeah ,
speaker: B
text: Early on , yeah .
speaker: G
text: and I wore the lapel once ,
speaker: G
text: and for me the lapel was OK .
speaker: G
text: I mean I still <disfmarker>
speaker: G
text: and I don't know why .
speaker: G
text: I 'm <disfmarker>
speaker: G
text: But um ,
speaker: G
text: for you it was <disfmarker>
speaker: D
text: Probably how you wear it <disfmarker> wore it I would guess .
speaker: G
text: Or who was next to me or something like that .
speaker: C
text: Yeah , where you were sitting probably affected it .
speaker: A
text: Yeah .
speaker: G
text: Right , but when Chuck wore the lapel and Morgan was talking there 're a couple really long utterances
speaker: G
text: where Chuck is saying a few things inside ,
speaker: G
text: and it 's picking up all of Morgan 's words pretty well
speaker: G
text: and so the rec you know , there 're error rates
speaker: G
text: because of insertion <disfmarker>
speaker: G
text: Insertions aren't bounded ,
speaker: G
text: so with a one - word utterance and ten insertions you know you got huge error rate .
speaker: D
text: Uh - huh .
speaker: A
text: Yeah .
speaker: G
text: And that 's <disfmarker> that 's where the problems come in .
speaker: G
text: So I this is sort of what we expected ,
speaker: G
text: but it 's nice to be able to <disfmarker> to show it .
speaker: D
text: Right .
speaker: G
text: And also I just wanted to mention briefly that , um , uh Andreas and I called up Dan Ellis who 's still stuck in Switzerland ,
speaker: G
text: and we were gonna ask him if <disfmarker> if there 're <disfmarker> you know , what 's out there in terms of echo cancellation and things like that .
speaker: G
text: Not that we were gonna do it ,
speaker: G
text: but we wanted to know what would need to be done .
speaker: D
text: And he said , " Lots lots lots lots . "
speaker: G
text: And he <disfmarker> We 've given him the data we have so far ,
speaker: G
text: so these sychronous cases where there are overlap .
speaker: A
text: Yep .
speaker: G
text: And he 's gonna look into trying to run some things that are out there
speaker: G
text: and see how well it can do
speaker: G
text: because right now we 're not able to actually report on recognition in a real paper ,
speaker: B
text: So <disfmarker>
speaker: G
text: like a Eurospeech paper ,
speaker: G
text: because it would look sort of premature .
speaker: B
text: So <disfmarker>
speaker: B
text: So the idea is that you would take this big hunk where somebody 's only speaking a small amount in it ,
speaker: B
text: and then try to figure out where they 're speaking <comment> based on the other peopl
speaker: G
text: Right . Or who 's <disfmarker> At any point in time who 's the foreground speaker ,
speaker: G
text: who 's the background speaker .
speaker: B
text: I thought we were just gonna move the boundaries in .
speaker: A
text: So yeah <disfmarker>
speaker: G
text: So .
speaker: A
text: Yeah , should it <disfmarker>
speaker: D
text: Well that 's with the hand stuff .
speaker: G
text: So there 's like <disfmarker>
speaker: D
text: But how would you do that automatically ?
speaker: B
text: Right .
speaker: A
text: Uh , I 've actually done some experiments with cross - correlation
speaker: G
text: Well ther there 's <disfmarker>
speaker: A
text: and it seems to work pretty well to <disfmarker> to get rid of those <disfmarker> those overlaps ,
speaker: F
text: Mm - hmm .
speaker: D
text: I mean that that 's the sort of thing that you would do .
speaker: G
text: Yeah .
speaker: G
text: Yeah . Exactly , so it 's <disfmarker> it 's a <disfmarker>
speaker: D
text: So .
speaker: A
text: yeah .
speaker: B
text: So why do you want to do echo cancellation ?
speaker: G
text: Um , it would be techniques used from adaptive <disfmarker> adaptive echo cancellation
speaker: G
text: which I don't know enough about to talk about .
speaker: B
text: Uh - huh .
speaker: F
text: It <disfmarker> just <disfmarker> it just to r to remove cross - talk .
speaker: G
text: Um .
speaker: G
text: But ,
speaker: C
text: Yeah .
speaker: F
text: Yeah .
speaker: G
text: right , um , and that would be similar to what you 're also trying to do ,
speaker: G
text: but using um , you know , more than energy <disfmarker>
speaker: G
text: I <disfmarker> I don't know what exactly would go into it .
speaker: A
text: Yeah .
speaker: A
text: Yeah , sure .
speaker: G
text: So the idea is to basically run this on the whole meeting .
speaker: B
text: So it would be <disfmarker>
speaker: G
text: and get the locations , which gives you also the time boundaries of the individual speak
speaker: B
text: OK .
speaker: B
text: So do sort of what he 's already <disfmarker> what he 's trying to do .
speaker: G
text: Right . Except that there are many techniques for the kinds of cues , um , that you can use to do that .
speaker: B
text: OK , I s I see .
speaker: A
text: Yeah , in another way ,
speaker: A
text: yeah .
speaker: A
text: Yeah .
speaker: B
text: Yeah .
speaker: B
text: I see .
speaker: F
text: Yeah , Dave <disfmarker> Dave uh is , um , also gonna be doin usin playing around with echo cancellation for the nearfield farfield stuff ,
speaker: G
text: So .
speaker: F
text: so we 'll be <disfmarker>
speaker: G
text: And I guess Espen ?
speaker: G
text: This <disfmarker> is <disfmarker> uh <disfmarker> is he here too ?
speaker: G
text: May also be working <disfmarker>
speaker: F
text: Yeah .
speaker: G
text: So it would just be ver
speaker: G
text: that 's really the next step
speaker: G
text: because we can't do too much , you know , on term in terms of recognition results knowing that this is a big problem
speaker: B
text: Mm - hmm .
speaker: G
text: um , until we can do that kind of processing .
speaker: G
text: And so , once we have some <disfmarker> some of yours ,
speaker: A
text: OK .
speaker: A
text: Yeah I 'm working on it .
speaker: G
text: and @ @ we 'll move on .
speaker: B
text: I think this also ties into one of the things that Jane is gonna talk about too .
speaker: D
text: Um ,
speaker: G
text: OK .
speaker: E
text: Mm - hmm . Mm - hmm .
speaker: D
text: I also wanted to say I have done all this chopping up of digits ,
speaker: D
text: so I have some naming conventions that we should try to agree on .
speaker: G
text: Oh right .
speaker: D
text: So let 's do that off - line ,
speaker: D
text: we don't need to do it during the meeting .
speaker: G
text: Yeah .
speaker: G
text: Right .
speaker: C
text: OK .
speaker: G
text: Definitely <disfmarker>
speaker: G
text: Uh , and Don should <disfmarker>
speaker: D
text: And <disfmarker> and I have scripts that will extract it out from " key " files
speaker: D
text: and <disfmarker> and do all the naming automatically ,
speaker: G
text: OK .
speaker: D
text: so you don't have to do it by hand .
speaker: C
text: Alright .
speaker: G
text: Great .
speaker: G
text: So that that 's it for the <disfmarker>
speaker: C
text: You 've compiled the list of , uh , speaker names ?
speaker: G
text: Speakers and <disfmarker>
speaker: D
text: Mm - hmm .
speaker: G
text: OK .
speaker: C
text: Not names ,
speaker: C
text: but I Ds .
speaker: D
text: Yep .
speaker: D
text: Yeah , names <disfmarker> names in the <disfmarker> names to I Ds ,
speaker: D
text: so you
speaker: C
text: OK .
speaker: G
text: Great .
speaker: D
text: and it does all sorts of matches
speaker: D
text: because the way people filled out names is different on every single file
speaker: D
text: so it does a very fuzzy sort of match .
speaker: G
text: Right .
speaker: C
text: Cool .
speaker: G
text: So at this point we can sort of finalize the naming , and so forth ,
speaker: D
text: Yep .
speaker: G
text: and we 're gonna basically re rewrite out these waveforms that we did
speaker: C
text: Mm - hmm .
speaker: G
text: because as you notice in the paper your " M O
speaker: G
text: in one meeting
speaker: G
text: and " M O - two " in another meeting and it 's <disfmarker> we just need to standardize the
speaker: C
text: Yeah .
speaker: C
text: That was my fault .
speaker: G
text: um ,
speaker: G
text: no it 's <disfmarker> it 's <disfmarker>
speaker: F
text: No , I didn't notice that actually .
speaker: G
text: um , that 's why those comments are s <vocalsound> are in there .
speaker: C
text: Yeah .
speaker: D
text: Yep .
speaker: C
text: Then disregard it then .
speaker: D
text: So th I now have a script that you can just say basically look up Morgan ,
speaker: G
text: So <disfmarker>
speaker: G
text: Right .
speaker: F
text: Yeah .
speaker: G
text: OK .
speaker: D
text: and it will give you his ID .
speaker: G
text: Great , great .
speaker: C
text: OK .
speaker: D
text: So .
speaker: G
text: Terrific .
speaker: D
text: Um ,
speaker: D
text: alright .
speaker: D
text: Do we <disfmarker>
speaker: D
text: Don , you had disk space and storage formats .
speaker: D
text: Is that something we need to talk about at the meeting ,
speaker: D
text: or should you just talk with Chuck at some other time ?
speaker: C
text: Um , I had some general questions just about the compression algorithms of shortening waveforms
speaker: C
text: and I don't know exactly who to ask .
speaker: C
text: I thought that maybe you would be the <disfmarker> the person to talk to .
speaker: C
text: So , is it a lossless compression <comment> when you compress ,
speaker: D
text: Mm - hmm .
speaker: C
text: so <disfmarker>
speaker: D
text: Entropy coding .
speaker: C
text: It just uses entropy coding ?
speaker: D
text: So .
speaker: C
text: OK .
speaker: C
text: So , I mean , I guess my question would be is
speaker: C
text: I just got this new eighteen gig drive installed .
speaker: C
text: Um , yeah ,
speaker: C
text: which is <disfmarker>
speaker: D
text: And I assume half of it is scratch and half of it is <disfmarker> ?
speaker: C
text: I 'm not exactly sure how they partitioned it .
speaker: D
text: Probably , yeah .
speaker: C
text: But um ,
speaker: F
text: That 's typical , huh .
speaker: C
text: yeah , I don't know what 's typical here ,
speaker: C
text: but um ,
speaker: C
text: it 's local though ,
speaker: C
text: so <disfmarker>
speaker: D
text: That doesn't matter .
speaker: C
text: But <disfmarker>
speaker: D
text: You can access it from anywhere in ICSI . N <disfmarker>
speaker: C
text: OK .
speaker: F
text: In fact , this is an eighteen gig drive , <comment> or is it a thirty six gig drive with eighteen <disfmarker>
speaker: C
text: Alright .
speaker: C
text: How do you do that ?
speaker: D
text: N <disfmarker>
speaker: C
text: Eighteen .
speaker: G
text: Eigh - eighteen .
speaker: G
text: It was a spare that Dave had around <disfmarker>
speaker: F
text: Oh OK .
speaker: D
text: Slash N slash machine name , slash X A in all likelihood .
speaker: C
text: Oh I see .
speaker: C
text: OK .
speaker: C
text: Alright , I did know that .
speaker: D
text: Um , so the <disfmarker> the only question is how much of it <disfmarker>
speaker: D
text: The distinction between scratch and non - scratch is whether it 's backed up or not .
speaker: C
text: Mm - hmm .
speaker: C
text: Right .
speaker: D
text: So what you wanna do is use the scratch for stuff that you can regenerate .
speaker: C
text: OK .
speaker: D
text: So ,
speaker: D
text: the stuff that isn't backed up is not a big deal
speaker: D
text: because disks don't crash very frequently ,
speaker: C
text: Right .
speaker: D
text: as long as you can regenerate it .
speaker: C
text: Right .
speaker: G
text: Yeah it 's <disfmarker>
speaker: C
text: I mean all of this stuff can be regenerated ,
speaker: C
text: it 's just a question <disfmarker>
speaker: G
text: Well the <disfmarker>
speaker: D
text: Then put it all on scratch
speaker: D
text: because we 're <disfmarker> ICSI is <disfmarker> is bottlenecked by backup .
speaker: G
text: Yeah .
speaker: E
text: Mm - hmm , very good point .
speaker: C
text: OK .
speaker: G
text: Well I 'd leave all the <disfmarker> All the transcript stuff shouldn't <disfmarker> should be backed up ,
speaker: D
text: So we wanna put <disfmarker>
speaker: E
text: Mm - hmm .
speaker: G
text: but all the waveform <disfmarker> <comment> Sound files should not be backed up ,
speaker: C
text: Yeah , I guess <disfmarker>
speaker: C
text: Right .
speaker: G
text: the ones that you write out .
speaker: C
text: OK .
speaker: C
text: So , I mean , I guess th the other question was then , should we shorten them , downsample them , or keep them in their original form ?
speaker: C
text: Um <disfmarker>
speaker: D
text: It just depends on your tools .
speaker: D
text: I mean , because it 's not backed up and it 's just on scratch , if your sc tools can't take shortened format , I would leave them expanded ,
speaker: C
text: Right .
speaker: D
text: so you don't have to unshorten them every single time you wanna do anything .
speaker: C
text: OK .
speaker: G
text: We can downsample them ,
speaker: C
text: Do you think that 'd be OK ?
speaker: G
text: so .
speaker: G
text: Yeah .
speaker: C
text: To downsample them ?
speaker: G
text: Yeah , we get the same performance .
speaker: C
text: OK .
speaker: G
text: I mean the r the front - end on the SRI recognizer just downsamples them on the fly ,
speaker: C
text: Yeah , I guess the only argument against downsampling is to preserve just the original files in case we want to experiment with different filtering techniques .
speaker: G
text: so <disfmarker>
speaker: G
text: So that 's <disfmarker>
speaker: F
text: I <disfmarker> I <disfmarker> I 'm sorry <disfmarker>
speaker: G
text: Yeah , if
speaker: F
text: Yeah , l I mean over all our data , we <disfmarker> we want to not downsample .
speaker: G
text: fe
speaker: G
text: You 'd <disfmarker> you wanna not .
speaker: G
text: OK .
speaker: G
text: So we 're <disfmarker> what we 're doing is we 're writing out <disfmarker>
speaker: F
text: Yeah .
speaker: G
text: I mean , this is just a question .
speaker: G
text: We 're writing out these individual segments , that wherever there 's a time boundary from Thilo , or <disfmarker> or Jane 's transcribers , you know , we <disfmarker> we chop it <pause> there .
speaker: F
text: Yeah .
speaker: F
text: Mm - hmm .
speaker: G
text: And the reason is so that we can feed it to the recognizer ,
speaker: F
text: Mm - hmm .
speaker: G
text: and throw out ones that we 're not using and so forth .
speaker: F
text: Yeah .
speaker: G
text: And those are the ones that we 're storing .
speaker: D
text: Yeah , as I said , since that 's <disfmarker> it 's regeneratable , what I would do is take <disfmarker> downsample it ,
speaker: G
text: So <disfmarker>
speaker: G
text: Yeah .
speaker: D
text: and compress it however you 're e the SRI recognizer wants to take it in .
speaker: G
text: Yeah .
speaker: G
text: So we can't shorten them ,
speaker: F
text: ye
speaker: G
text: but we can downsample them .
speaker: C
text: Right .
speaker: F
text: Yeah , I mean <disfmarker>
speaker: F
text: yeah , I 'm sorry .
speaker: G
text: So .
speaker: F
text: As <disfmarker> yeah , as long as there is a <disfmarker> a form that we can come from again , that is not downsampled , <comment> then ,
speaker: C
text: r
speaker: C
text: Yeah .
speaker: G
text: Oh yeah th
speaker: C
text: Yeah those are gonna be kept .
speaker: G
text: Yeah . Yeah .
speaker: G
text: That <disfmarker> that 's why we need more disk space
speaker: F
text: uuu
speaker: G
text: cuz we 're basically duplicating the originals , um <disfmarker>
speaker: F
text: Yeah .
speaker: F
text: Then it 's fine .
speaker: D
text: Right .
speaker: F
text: But for <disfmarker> for <disfmarker> fu future research we 'll be doing it with different microphone positions and so on
speaker: G
text: Oh yeah .
speaker: G
text: No . We always have the original long ones .
speaker: D
text: Yep .
speaker: C
text: Right .
speaker: F
text: we would like to <disfmarker>
speaker: F
text: Yeah .
speaker: B
text: So the SRI front - end won't take a uh <disfmarker> an <disfmarker> an <disfmarker> a large audio file name and then a <disfmarker> a list of segments to chop out <comment> from that large audio file ?
speaker: B
text: They actually have to be chopped out already ?
speaker: G
text: Um , it 's better if they 're chopped out ,
speaker: G
text: and <disfmarker> and it <disfmarker> it will be <disfmarker>
speaker: B
text: Uh - huh .
speaker: G
text: yeah , y we could probably write something to do that ,
speaker: G
text: but it 's actually convenient to have them chopped out
speaker: G
text: cuz you can run them , you know , in different orders .
speaker: G
text: You c you can actually move them around .
speaker: D
text: And that 's the whole point about the naming conventions
speaker: G
text: Uh , you can get rid of
speaker: D
text: is that you could run all the English speaking ,
speaker: G
text: Yeah , it it 's a lot faster .
speaker: D
text: all the native speakers ,
speaker: G
text: Right . You can grab everything with the word " the " in it ,
speaker: D
text: and all the non - native speakers ,
speaker: D
text: and all the men , and all the women .
speaker: G
text: and it 's <disfmarker>
speaker: D
text: Yeah .
speaker: G
text: That 's a lot quicker than actually trying to access the wavefile each time ,
speaker: G
text: find the time boundaries and <disfmarker>
speaker: G
text: So in principle , yeah , you could do that ,
speaker: B
text: I don't <disfmarker> I don't think that 's really right .
speaker: G
text: but it 's <disfmarker>
speaker: G
text: but it 's um <disfmarker>
speaker: D
text: " That 's just not right , man . "
speaker: G
text: These are long <disfmarker> These are long <disfmarker>
speaker: D
text: The <disfmarker> the point <disfmarker>
speaker: D
text: So <disfmarker> so s For example , what if you wanted to run <disfmarker> run all the native speakers .
speaker: G
text: You know .
speaker: G
text: This is an hour of speech .
speaker: D
text: Right , so if <disfmarker> if you did it that way you would have to generate a program that looks in the database somewhere ,
speaker: D
text: extracts out the language ,
speaker: D
text: finds the time - marks for that particular one ,
speaker: D
text: do it that way .
speaker: D
text: The way they 're doing it , you have that already extracted
speaker: D
text: and it 's embedded in the file name .
speaker: D
text: And so , you know , you just say <disfmarker>
speaker: G
text: We - yeah that 's <disfmarker> so that 's part of it
speaker: D
text: y so you just say you know " asterisk E asterisk dot wave " , and you get what you want .
speaker: G
text: is <disfmarker>
speaker: G
text: Right .
speaker: G
text: And the other part is just that once they 're written out it <disfmarker> it is a lot faster to <disfmarker> to process them .
speaker: D
text: Rather than doing seeks through the file .
speaker: G
text: So .
speaker: G
text: Otherwise , you 're just accessing <disfmarker>
speaker: D
text: This is all just temporary access ,
speaker: D
text: so I don't <disfmarker> I think <disfmarker> it 's all just <disfmarker>
speaker: D
text: It 's fine .
speaker: D
text: You know .
speaker: D
text: Fine to do it however is convenient .
speaker: G
text: Right .
speaker: F
text: I mean it just depends how big the file is .
speaker: F
text: If the file sits in memory you can do extremely fast seeks
speaker: G
text: Right .
speaker: G
text: The other thing is that , believe it or not <disfmarker> I mean , we have some <disfmarker>
speaker: F
text: but .
speaker: D
text: Yeah and they don't .
speaker: D
text: Two gig ?
speaker: G
text: So we 're also looking at these in Waves like for the alignments and so forth .
speaker: G
text: You can't load an hour of speech into X Waves .
speaker: F
text: Yeah .
speaker: G
text: You need to s have these small files ,
speaker: G
text: and in fact , even for the Transcriber program Um <disfmarker>
speaker: D
text: Yes you can .
speaker: B
text: Yeah , you <disfmarker> you can give Waves a start and an end time .
speaker: G
text: Yeah , if you try to load s really long waveform into X Waves , you 'll be waiting there for <disfmarker>
speaker: B
text: And middle .
speaker: B
text: No , I <disfmarker> I 'm not suggesting you load a long wave file ,
speaker: G
text: Oh
speaker: B
text: I 'm just saying you give it a start and an end time .
speaker: B
text: And it 'll just go and pull out that section .
speaker: D
text: I th
speaker: D
text: w The transcribers didn't have any problem with that
speaker: D
text: did they Jane ?
speaker: E
text: What 's th u w in what respect ?
speaker: G
text: Loading the long <disfmarker>
speaker: D
text: They loaded <disfmarker> they loaded the long long files into X Waves .
speaker: A
text: No , with the Transcriber tool , it 's no problem .
speaker: G
text: It takes a very long ti
speaker: E
text: In the <disfmarker> in
speaker: A
text: Yeah just to load a transcription
speaker: E
text: Mm - hmm .
speaker: G
text: Right .
speaker: G
text: It takes a l very long time .
speaker: A
text: takes a long time ,
speaker: A
text: but not for the wavefile .
speaker: A
text: The wavefile is there immediately .
speaker: E
text: Mm - hmm . Yeah .
speaker: D
text: Are you talking about Transcriber or X Waves ?
speaker: G
text: Huh .
speaker: A
text: Yeah .
speaker: A
text: Oh , I 'm tr talking about Transcriber .
speaker: G
text: Actually , you 're talking about Transcriber , right ?
speaker: A
text: Yeah .
speaker: E
text: It was also true of the digits task which was X Waves .
speaker: D
text: Because <disfmarker> because i we used X Waves to do the digits .
speaker: E
text: Yeah .
speaker: D
text: And they were loading the full mixed files then ,
speaker: E
text: Very quickly .
speaker: D
text: and it didn't seem to be any problem .
speaker: E
text: I agree .
speaker: G
text: Huh .
speaker: G
text: Well we <disfmarker> we have a problem with that ,
speaker: G
text: you know , time - wise on a <disfmarker>
speaker: G
text: It - it 's a lot slower to load in a long file ,
speaker: D
text: Hmm .
speaker: D
text: Seemed really fast .
speaker: G
text: and also to check the file ,
speaker: G
text: so if you have a transcript , um ,
speaker: D
text: Well regardless , it 's <disfmarker>
speaker: G
text: I mean it 's <disfmarker>
speaker: F
text: Yeah .
speaker: G
text: I <disfmarker> I think overall you could get everything to work by accessing the same waveform and trying to find two <disfmarker> you know , the begin and end times .
speaker: G
text: Um ,
speaker: G
text: but I think it 's more efficient , if we have the storage space , to have the small ones .
speaker: D
text: and , it 's no problem , right ?
speaker: G
text: Yeah , it 's <disfmarker>
speaker: D
text: Because it 's not backed up .
speaker: G
text: Yeah .
speaker: G
text: It 's <disfmarker> it 's just <disfmarker>
speaker: D
text: So we just <disfmarker>
speaker: D
text: If we don't have a spare disk sitting around we go out and we buy ourselves an eighty gigabyte drive
speaker: D
text: and make it all scratch space .
speaker: D
text: You know , it 's not a big deal .
speaker: E
text: You 're right about the backup being <pause> a bottleneck .
speaker: G
text: Right .
speaker: E
text: It 's good to think towards scratch .
speaker: G
text: Yeah , so these wouldn't be backed up , the <disfmarker>
speaker: E
text: Yeah .
speaker: F
text: Yep .
speaker: G
text: Right .
speaker: D
text: So remind me afterward
speaker: G
text: And <disfmarker>
speaker: D
text: and I 'll <disfmarker> and we 'll look at your disk and see where to put stuff .
speaker: C
text: OK . Alright .
speaker: C
text: I mean , I could just u do a DU on it right ?
speaker: C
text: And just see which <disfmarker> how much is on each <disfmarker>
speaker: D
text: Yep .
speaker: C
text: So .
speaker: D
text: Each partition .
speaker: D
text: And you wanna use , either XA or scratch .
speaker: C
text: OK .
speaker: D
text: Well X question mark ,
speaker: D
text: anything starting with X is scratch .
speaker: C
text: OK .
speaker: E
text: With two <disfmarker> two digits .
speaker: D
text: Two digits , right ,
speaker: D
text: XA , XB , XC .
speaker: F
text: So , @ @ .
speaker: D
text: OK ?
speaker: D
text: Jane ?
speaker: E
text: OK . So I got a little print - out here .
speaker: E
text: So three on this side ,
speaker: E
text: three on this side .
speaker: E
text: And I stapled them .
speaker: E
text: OK .
speaker: E
text: Alright so , first of all , um , there was a <disfmarker> an interest in the transcribe transcription , uh , checking procedures
speaker: E
text: and <disfmarker> <vocalsound> and I can <vocalsound> tell you first , uh , to go through the steps
speaker: E
text: although you 've probably seen them .
speaker: E
text: Um , as you might imagine , when you 're dealing with , um , r really c a fair number of words , and uh , @ @ <comment> natural speech
speaker: E
text: which means s self - repairs and all these other factors , that there 're lots of things to be , um , s standardized and streamlined and checked on .
speaker: E
text: And , um , so ,
speaker: E
text: I did a bunch of checks ,
speaker: E
text: and the first thing I did was obviously a spell - check .
speaker: E
text: And at that point I discovered certain things
speaker: E
text: like , um , " accommodate " with one " M " ,
speaker: E
text: that kind of thing .
speaker: E
text: And then , in addition to that , I did an exhaustive listing of the forms in the data file ,
speaker: E
text: which included n detecting things like f faulty punctuation and things <disfmarker>
speaker: B
text: I 'm <disfmarker> I 'm sorry to interrupt
speaker: E
text: Yeah ?
speaker: B
text: you could <disfmarker> could I just back up a little bit
speaker: E
text: Sure , please ,
speaker: E
text: yeah , please , please .
speaker: B
text: and <disfmarker>
speaker: E
text: Yeah , yeah , yeah .
speaker: B
text: So you 're doing these <disfmarker> So <pause> the whole process is that the transcribers get the conversation
speaker: B
text: and they do their pass over it .
speaker: E
text: Yes .
speaker: B
text: And then when they 're finished with it , it comes to you ,
speaker: B
text: and you begin these sanit these quality checks .
speaker: E
text: That 's right .
speaker: E
text: Exactly .
speaker: E
text: I do these checks .
speaker: E
text: Uh - huh .
speaker: B
text: OK .
speaker: E
text: Exactly .
speaker: B
text: OK .
speaker: E
text: Yeah .
speaker: E
text: Thank you .
speaker: E
text: And so , uh , I do a <disfmarker> an exhaustive listing of the forms <disfmarker>
speaker: E
text: Actually , I will go through this in <disfmarker> in order ,
speaker: E
text: so if <disfmarker> if we could maybe wait and stick keep that for a second
speaker: E
text: cuz we 're not ready for that .
speaker: D
text: So on the fifth page , seven down <disfmarker>
speaker: E
text: Yeah , yeah , yeah , yeah . Exactly ! Exactly !
speaker: E
text: Alright so , <vocalsound> a spelling check first
speaker: E
text: then an exhaustive listing of the , uh <disfmarker> all the forms in the data with the punctuation attached
speaker: E
text: and at that point I pick up things like , oh , you know , word followed by two commas .
speaker: E
text: And th and then another check involves , uh , being sure that every utterance has an identifiable speaker .
speaker: E
text: And if not , then that gets checked .
speaker: E
text: Then there 's this issue of glossing s w so - called " spoken - forms " .
speaker: E
text: So there <disfmarker>
speaker: E
text: mo for the most part , we 're keeping it standard wo word level transcription .
speaker: E
text: But there 's <disfmarker>
speaker: E
text: w And that that 's done with the assumption that <pause> pronunciation variants can be handled .
speaker: E
text: So for things like " and " , the fact that someone doesn't say the " D " , uh that 's not important enough to capture in the transcription
speaker: E
text: because a <disfmarker> a good pronunciation , uh , you know , model would be able to handle that .
speaker: E
text: However , things like " cuz " where you 're lacking an entire very prominent first syllable ,
speaker: E
text: and furthermore , it 's a form that 's specific to spoken language ,
speaker: E
text: those are r reasons <disfmarker> f for those reasons I <disfmarker> I kept that separate ,
speaker: E
text: and used the convention of using " CUZ " for that form ,
speaker: E
text: however , glossing it
speaker: E
text: so that it 's possible with the script to plug in the full orthographic form for that one ,
speaker: E
text: and a couple of others ,
speaker: E
text: not many .
speaker: E
text: So " wanna " is another one ,
speaker: E
text: " going <disfmarker> " uh , " gonna " is another one ,
speaker: E
text: with just the assumption , again , that this <disfmarker> th these are things which it 's not really fair to a c consider <disfmarker> expect that <disfmarker> a pronunciation model , to handle .
speaker: E
text: And Chuck , you in you indicated that " cuz " is <disfmarker> is one of those that 's handled in a different way also , didn't you ?
speaker: E
text: Did I <disfmarker>
speaker: B
text: I don't remember .
speaker: E
text: OK .
speaker: E
text: So <disfmarker> so it might not have been <disfmarker> <vocalsound> It might not have been you ,
speaker: B
text: Hmm .
speaker: E
text: but someone told me that in fact " cuz " is treated differently in , um , i u in this context
speaker: E
text: because of that r reason that , um , it 's a little bit farther than a pronunciation variant .
speaker: E
text: OK , so after that ,
speaker: E
text: let 's see ,
speaker: E
text: um .
speaker: B
text: So that was part of the spell - check , <comment> or was that <disfmarker> that was after the spell - check ?
speaker: E
text: Well so when I get the exhau
speaker: E
text: So the spell - check picks up those words
speaker: E
text: because they 're not in the dictionary .
speaker: B
text: Uh - huh .
speaker: E
text: So it gets " cuz " and " wanna " and that <disfmarker>
speaker: D
text: And then you gloss them ?
speaker: E
text: Yeah , mm - hmm .
speaker: E
text: Run it through <disfmarker>
speaker: E
text: I have a sed <disfmarker> You know , so I do sed script saying whenever you see " gonna " you know , " convert it to gonna " , you know , " gloss equals quote going - to quote " ,
speaker: E
text: you know .
speaker: E
text: And with all these things being in curly brackets
speaker: E
text: so they 're always distinctive .
speaker: D
text: Mm - hmm .
speaker: E
text: OK , I also wrote a script which will , um , retrieve anything in curly brackets , <vocalsound> or anything which I 've classified as an acronym ,
speaker: E
text: and <disfmarker> a pronounced acronym .
speaker: E
text: And the way I tag ac pronounced acronyms is that I have underscores between the components .
speaker: E
text: So if it 's " ACL " then it 's " A " underscore " C " underscore " L " .
speaker: E
text: And the th
speaker: D
text: And so <disfmarker> so your list here , are these ones that actually occurred in the meetings ?
speaker: E
text: Yes . Uh - huh , yeah .
speaker: D
text: Whew !
speaker: E
text: OK , so now . Uh and <disfmarker> a
speaker: D
text: We are acronym - loaded .
speaker: G
text: Um , can I ask a question about the glossing , uh before we go on ?
speaker: E
text: Yeah .
speaker: G
text: So , for a word like " because " is it that it 's always predictably " because " ?
speaker: G
text: I mean , is " CUZ " always meaning " because " ?
speaker: E
text: Yes , but not the reverse .
speaker: E
text: So sometimes people will say " because " in the meeting ,
speaker: E
text: and if <disfmarker> if they actually said " because " , then it 's written as " because " with no <disfmarker> w
speaker: E
text: " cuz " doesn't even figure into the equation .
speaker: G
text: Beca - because <disfmarker>
speaker: F
text: But <disfmarker> but in our meetings people don't say " hey cuz how you doing ? "
speaker: G
text: Right . <comment> <vocalsound> Right .
speaker: D
text: Except right there .
speaker: E
text: Yeah .
speaker: F
text: Yeah .
speaker: G
text: Um , so , I guess <disfmarker> So , from the point of view of <disfmarker>
speaker: E
text: That 's a good point .
speaker: G
text: The <disfmarker> the only problem is that with <disfmarker> for the recognition we <disfmarker> we map it to " because " ,
speaker: G
text: and so if we know that " CUZ " <disfmarker>
speaker: D
text: Well ,
speaker: E
text: That 's fine .
speaker: E
text: Well Don has a script .
speaker: D
text: but they have the gloss .
speaker: C
text: Yeah .
speaker: G
text: but , we don't <disfmarker>
speaker: D
text: You have the gloss form
speaker: D
text: so you always replace it .
speaker: E
text: Exactly .
speaker: D
text: If that 's how <disfmarker> what you wanna do .
speaker: E
text: Uh - huh .
speaker: E
text: And Don knows this ,
speaker: E
text: and he 's bee he has a glo he has a script that <disfmarker>
speaker: C
text: Yeah .
speaker: C
text: I replace the " cuz " with " because " if it 's glossed .
speaker: G
text: S
speaker: G
text: Right .
speaker: G
text: But , if it 's <disfmarker>
speaker: G
text: OK .
speaker: G
text: But then there are other glosses that we don't replace , right ?
speaker: C
text: And <disfmarker>
speaker: G
text: Because <disfmarker>
speaker: E
text: Yes . And that 's why there 're different tags on the glosses ,
speaker: G
text: OK . So , then it 's fine .
speaker: E
text: on the different <disfmarker> on the different types of comments ,
speaker: E
text: which we 'll <disfmarker> which we 'll see in just a second .
speaker: C
text: Right .
speaker: G
text: OK .
speaker: E
text: So the pronounceable acronyms get underscores ,
speaker: E
text: the things in curly brackets are viewed as comments .
speaker: E
text: There 're comments of four types .
speaker: E
text: So this is a good time to introduce that .
speaker: E
text: The four types .
speaker: E
text: w And maybe we 'll expand that
speaker: D
text: Um <disfmarker>
speaker: E
text: but the <disfmarker> but the comments are , um , of four types mainly right now .
speaker: E
text: One of them is , um , the gloss type we just mentioned .
speaker: D
text: Can <disfmarker> ca
speaker: E
text: Another type is , um <disfmarker>
speaker: D
text: So a are we done with acronyms ?
speaker: D
text: Cuz I had a question on what <disfmarker> what this meant .
speaker: E
text: I 'm still doing the overview .
speaker: E
text: I haven't actually gotten here yet .
speaker: D
text: Oh I 'm sorry .
speaker: E
text: OK so , gloss is things like replacing the full form u with the , um , more abbreviated one to the left .
speaker: E
text: Uh , then you have if it 's <disfmarker> uh , there 're a couple different types of elements that can happen that aren't really properly words ,
speaker: E
text: and wo some of them are laughs and breathes ,
speaker: E
text: so we have <disfmarker> uh that 's prepended with a v a tag of " VOC " .
speaker: A
text: Whew !
speaker: E
text: And the non - vocal ones are like door - slams and tappings ,
speaker: E
text: and that 's prepended with a no non - vocalization .
speaker: B
text: So then it <disfmarker> just an ending curly brace there ,
speaker: B
text: or is there something else in there .
speaker: E
text: Oh yeah , so i e this would <disfmarker>
speaker: E
text: Let 's just take one example .
speaker: D
text: A comment , basically .
speaker: B
text: Oh , oh , oh .
speaker: E
text: And then the no non - vocalization would be something like a door - slam .
speaker: E
text: They always end .
speaker: E
text: So it 's like they 're paired curly brackets .
speaker: E
text: And then the third type right now , <vocalsound> uh , is <pause> m things that fall in the category of comments about what 's happening .
speaker: E
text: So it could be something like , you know , " referring to so - and - so " ,
speaker: E
text: " talking about such - and - such " ,
speaker: E
text: uh , you know , " looking at so - and - so " .
speaker: B
text: So on the m
speaker: B
text: on the middle t So , in the first case that gloss applies to the word to the left .
speaker: E
text: Yeah .
speaker: E
text: Yeah , and this gets substituted here .
speaker: B
text: But in the middle two <disfmarker> Th - it 's not applying to anything , right ?
speaker: D
text: They 're impulsive .
speaker: E
text: Huh - uh .
speaker: B
text: OK .
speaker: E
text: No , they 're events .
speaker: E
text: They 're actually <disfmarker> They have the status of events .
speaker: B
text: OK .
speaker: D
text: Well the " QUAL " can be <disfmarker> The " QUAL " is applying to the left .
speaker: B
text: Right , I just meant the middle two ones ,
speaker: D
text: Yep .
speaker: B
text: yeah .
speaker: E
text: Well , and actually , um , it is true that , with respect to " laugh " , there 's another one
speaker: E
text: which is " while laughing " ,
speaker: D
text: " While laughing " .
speaker: E
text: and that is , uh , i i An argument could be made for this <disfmarker> tur turning that into a qualitative statement
speaker: E
text: because it 's talking about the thing that preceded it ,
speaker: E
text: but at present we haven't been , um , uh , coding the exact scope of laughing , you know ,
speaker: E
text: and so to have " while laughing " , you know that it happened somewhere in there
speaker: E
text: which could well mean that it occurred separately and following ,
speaker: E
text: or , you know , including some of the utterances to the left .
speaker: E
text: Haven't been awfully precise about that ,
speaker: E
text: but I have here ,
speaker: E
text: now we 're about to get to the <disfmarker> to this now ,
speaker: E
text: I have frequencies .
speaker: E
text: So you 'll see how often these different things occur .
speaker: E
text: But , um , uh , the very front page deals with this , uh , final c pa uh , uh , aspect of the standardization
speaker: E
text: which has to do with the spoken forms like " mm - hmm " and " mm - hmm " and " ha " and " uh - uh " and all these different types .
speaker: E
text: And , um , uh , someone pointed out to me ,
speaker: E
text: this might have been Chuck , <comment> about , um <disfmarker> about how a recognizer , if it 's looking for " mm - hmmm " with three M 's , <vocalsound> and it 's transcribed with two M 's , <vocalsound> that it might <disfmarker> uh , that it might increase the error rate
speaker: E
text: which is <disfmarker> which would really be a shame
speaker: E
text: because um , I p I personally w would not be able to make a claim that those are dr dramatically different items .
speaker: E
text: So , right now I 've standardized across all the existing data with these spoken forms .
speaker: D
text: Oh good .
speaker: E
text: I <disfmarker> I should say
speaker: D
text: So it 's a small list .
speaker: E
text: all existing data except thirty minutes which got found today .
speaker: E
text: So , I 'm gonna <disfmarker> <vocalsound> I 'm gonna <disfmarker> <vocalsound> I 'm gonna check <disfmarker>
speaker: D
text: That <disfmarker> that 's known as " found data " .
speaker: E
text: Yeah , yeah .
speaker: E
text: Acsu - actually yeah .
speaker: E
text: I got <disfmarker> It was stored in a place I didn't expect ,
speaker: C
text: It 's like the z Zapruder Film .
speaker: E
text: so <disfmarker> and <disfmarker> and um ,
speaker: E
text: w we , uh , sh yea reconstructed how that happened .
speaker: F
text: I wanna work with lost data .
speaker: D
text: Yeah . It 's much easier .
speaker: E
text: And this is <disfmarker> this 'll be great .
speaker: E
text: So I 'll <disfmarker> I 'll be able to get through that tonight ,
speaker: E
text: and then everyth i well , actually later today probably .
speaker: D
text: Hmm .
speaker: E
text: And so then we 'll have everything following these conventions .
speaker: E
text: But you notice it 's really rather a small set of these kinds of things .
speaker: D
text: Yeah .
speaker: E
text: And I made it so that these are , um , with a couple exceptions but , things that you wouldn't find in the spell - checker
speaker: E
text: so that they 'll show up really easily .
speaker: E
text: And , um <disfmarker>
speaker: C
text: Jane , can I ask you a question ?
speaker: C
text: What 's that very last one correspond to ?
speaker: E
text: Sure .
speaker: C
text: I don't even know how to pronounce that .
speaker: E
text: Well , yeah . Now that <disfmarker> that s only occurs once ,
speaker: G
text: Yeah .
speaker: E
text: and I 'm thinking of changing that .
speaker: G
text: Right .
speaker: E
text: So - c I haven't listened to it
speaker: C
text: Uh , is that like someone 's like burning or some such thing ?
speaker: E
text: so I don't know .
speaker: E
text: I haven't heard it actually .
speaker: C
text: Like their hair 's on fire ?
speaker: E
text: I n I need to listen to that one .
speaker: D
text: Ah !
speaker: G
text: Actually we <disfmarker> we gave this to our pronunciation person ,
speaker: A
text: It 's the Castle of Ah !
speaker: C
text: Uh , it looks like that .
speaker: G
text: she 's like , " I don't know what that is either " .
speaker: G
text: So .
speaker: E
text: Did she hear the th did she actually hear it ?
speaker: G
text: No , we just gave her a list of words that , you know , weren't in our dictionary
speaker: E
text: Cuz I haven't heard it .
speaker: G
text: and so of course it picked up stuff like this ,
speaker: G
text: and she just didn't listen
speaker: G
text: so she didn't know .
speaker: G
text: We just <disfmarker> we 're waiting on that <pause> just to do the alignments .
speaker: E
text: Yeah .
speaker: E
text: Yeah I 'm curious to se hear what it is ,
speaker: E
text: but I didn't know <disfmarker> wanna change it to something else until I knew .
speaker: G
text: Maybe it 's " argh " ?
speaker: C
text: Right .
speaker: E
text: Well , sss , <comment> you know <disfmarker>
speaker: C
text: But that 's not really like <disfmarker>
speaker: E
text: Hhh .
speaker: G
text: Yeah .
speaker: C
text: No one really says " argh , " you know ,
speaker: G
text: Right , no one say
speaker: F
text: Well , you just did .
speaker: C
text: it 's not <disfmarker>
speaker: C
text: Well ,
speaker: E
text: Yeah .
speaker: C
text: there 's another <disfmarker> there 's another word error .
speaker: B
text: Except for now !
speaker: E
text: That 's right .
speaker: D
text: Yes , that 's right .
speaker: D
text: We 're gonna have a big problem when we talk about that .
speaker: C
text: Cha - ching .
speaker: G
text: Ah .
speaker: B
text: We 're gonna never recognize this meeting .
speaker: E
text: OK .
speaker: D
text: In Monty Python you say " argh " a lot .
speaker: C
text: Oh yeah ?
speaker: D
text: So .
speaker: D
text: Well , or if you 're a C programmer .
speaker: C
text: Mmm .
speaker: E
text: Yeah , that 's right .
speaker: F
text: Yeah .
speaker: D
text: You say arg - C and arg - V all the time .
speaker: E
text: That 's right .
speaker: F
text: Yeah
speaker: C
text: That 's true .
speaker: G
text: But it has a different prosody .
speaker: E
text: Yeah .
speaker: F
text: Arg .
speaker: D
text: It does .
speaker: F
text: Arg <disfmarker> arg - max , arg - min ,
speaker: C
text: Mm - hmm .
speaker: F
text: yeah .
speaker: D
text: Ah !
speaker: E
text: Uh ,
speaker: G
text: So , Jane , what 's the <disfmarker> d
speaker: D
text: Maybe he died while dictating .
speaker: E
text: so .
speaker: G
text: I have one question about the the " EH " versus like the " AH " and the " UH " .
speaker: E
text: That 's partly a nonnative - native thing ,
speaker: G
text: OK .
speaker: E
text: but I have found " EH " in native speakers too .
speaker: E
text: But it 's mostly non - native <disfmarker>
speaker: G
text: S OK .
speaker: A
text: H
speaker: B
text: That 's " eh " versus " ah " ?
speaker: E
text: Eh .
speaker: D
text: Eh ?
speaker: G
text: " Eh , " yeah right ,
speaker: G
text: cuz there were <disfmarker> were some speakers that did definite " eh 's "
speaker: E
text: Mm - hmm .
speaker: G
text: but right now we <disfmarker>
speaker: B
text: They were the Canadians , right ?
speaker: F
text: Canadians , yeah , yeah , yeah .
speaker: E
text: That 's right .
speaker: G
text: So , it <disfmarker> it 's actually probably good for us to know the difference between the real " eh " and the one that 's just like " uh " or transcribed " aaa "
speaker: E
text: Exactly .
speaker: G
text: cuz in <disfmarker> like in Switchboard , you would see e all of these forms ,
speaker: G
text: but they all were like " uh " .
speaker: D
text: You mean just the single letter " a " <comment> as in the particle ?
speaker: A
text: The transcription or <disfmarker>
speaker: G
text: No , no , I mean like the <disfmarker> the " UH " ,
speaker: D
text: Article .
speaker: E
text: " UH " .
speaker: D
text: Oh .
speaker: G
text: or <disfmarker> the " UH " , " EH " , " AH " were all the same .
speaker: G
text: And then , we have this additional non - native version of <disfmarker> uh , like " eeh " .
speaker: C
text: All the " EH " 's I 've seen have been like that .
speaker: C
text: They 've been like " eh "
speaker: C
text: like that have bee has been transcribed to " EH " .
speaker: E
text: Mm - hmm , that 's right .
speaker: C
text: And sometimes it 's stronger ,
speaker: C
text: like " eeh " <comment> which is like closer to " EH " .
speaker: E
text: Mmm .
speaker: G
text: Right .
speaker: C
text: But .
speaker: E
text: Yeah .
speaker: D
text: I 'm just <disfmarker> these poor transcribers , they 're gonna hate this meeting .
speaker: C
text: I know .
speaker: C
text: We should go off - line .
speaker: E
text: Well , <vocalsound> we 're not doing <disfmarker> We 're not doing length .
speaker: F
text: Quick Thilo , do a <disfmarker> do a filled pause for us .
speaker: E
text: Yeah , that 's right .
speaker: A
text: Ooo <comment> no .
speaker: G
text: But you 're a native German speaker
speaker: G
text: so it 's not a <disfmarker> not a issue for <disfmarker>
speaker: A
text: Yeah .
speaker: G
text: It 's only <disfmarker>
speaker: D
text: Them Canadians .
speaker: G
text: Onl
speaker: G
text: yeah .
speaker: G
text: No , only if you don't have lax vowels , I guess .
speaker: G
text: Right .
speaker: G
text: So it 's <disfmarker> like Japanese and Spanish
speaker: D
text: Oh .
speaker: E
text: This makes sense .
speaker: E
text: Yeah I <disfmarker> I think you 've <disfmarker>
speaker: E
text: uh - huh , yeah .
speaker: G
text: and <disfmarker>
speaker: F
text: Uh - huh .
speaker: D
text: Oh I see .
speaker: E
text: That makes sense .
speaker: D
text: I didn't get that ,
speaker: D
text: OK .
speaker: E
text: Yeah , and so , you know , I mean , th th I have <disfmarker> there are some , um , Americans who <disfmarker> who are using this " eh " too ,
speaker: E
text: and I haven't listened to it systematically ,
speaker: E
text: maybe with some of them , uh , they 'd end up being " uh 's "
speaker: E
text: but , uh , I my spot - checking has made me think that we do have " eh " in also , um , American e e data represented here .
speaker: E
text: But
speaker: E
text: any case , that 's the <disfmarker> this is reduced down from really quite a long a much longer list ,
speaker: G
text: Yeah this is great .
speaker: E
text: and this is
speaker: C
text: Mm - hmm .
speaker: D
text: Yeah , it 's good ,
speaker: G
text: This is really really helpful .
speaker: D
text: yeah .
speaker: E
text: functionally pretty , you know , also <disfmarker>
speaker: E
text: It was fascinating , I was listening to some of these , uh , I guess two nights ago ,
speaker: E
text: and it 's just hilarious to liste to <disfmarker> to do a search for the " mm - hmm 's " .
speaker: E
text: And you get " mm - hmm "
speaker: E
text: and diff everybody 's doing it .
speaker: D
text: And just listen to them ?
speaker: D
text: Yeah .
speaker: E
text: Just <disfmarker> I wanted to say <disfmarker> I w think it would be fun to make a montage of it
speaker: E
text: because there 's a " Mm - hmm .
speaker: E
text: Mm - hmm .
speaker: E
text: Mm - hmm . "
speaker: D
text: Performance art ,
speaker: D
text: just extract them all .
speaker: G
text: Right .
speaker: E
text: It 's really <disfmarker> it 's really fun to listen to .
speaker: B
text: Morgan can make a song out of it .
speaker: E
text: All these different vocal tracts , you know ,
speaker: E
text: but it 's <disfmarker> it 's the same item .
speaker: E
text: It 's very interesting .
speaker: E
text: OK .
speaker: E
text: Uh , then the acronyms
speaker: E
text: y and the ones in parentheses are ones which the transcriber wasn't sure of ,
speaker: E
text: and I haven't been able to listen to to <disfmarker> to clarify ,
speaker: D
text: Oh I see .
speaker: E
text: but you can see that the parenthesis convention makes it very easy to find them
speaker: D
text: o
speaker: E
text: cuz it 's the only place where <disfmarker> where they 're used .
speaker: D
text: How about question mark ?
speaker: A
text: The question marks , yeah .
speaker: E
text: Question mark is punctuation .
speaker: A
text: What are those ?
speaker: E
text: So it <disfmarker> they said that @ @ <disfmarker>
speaker: D
text: Oh .
speaker: C
text: Mm - hmm .
speaker: E
text: um , " DC ? "
speaker: D
text: So they <disfmarker> so it 's " PLP ? "
speaker: A
text: Ah .
speaker: E
text: Exactly .
speaker: E
text: Exactly .
speaker: E
text: Yeah , so the only <disfmarker>
speaker: E
text: Well , and I do have a stress marker here .
speaker: E
text: Sometimes the contrastive stress is showing up ,
speaker: E
text: and , um <disfmarker>
speaker: F
text: I 'm sorry , I <disfmarker> I got lost here .
speaker: F
text: What - w what 's the difference between the parenthesized acronym and the non - parenthesized ?
speaker: E
text: The parenthesized is something that the transcriber thought was ANN , but wasn't entirely sure .
speaker: E
text: So I 'd need to go back or someone needs to go back , and say , you know , yes or no ,
speaker: F
text: Ah .
speaker: G
text: Right .
speaker: E
text: and then get rid of the parentheses .
speaker: E
text: But the parentheses are used only in that context in the transcripts , of of noti noticing that there 's something uncertain .
speaker: D
text: Yeah , P - make is <disfmarker>
speaker: G
text: Yeah I mean cuz they <disfmarker> they have no idea ,
speaker: D
text: That 's a good one .
speaker: D
text: That 's correct .
speaker: G
text: right .
speaker: G
text: If you hear CTPD , I mean , they do pretty well
speaker: F
text: Yeah .
speaker: C
text: Mm - hmm .
speaker: G
text: but it 's <disfmarker>
speaker: F
text: I <disfmarker> I don't recognize a lot of these .
speaker: G
text: you know how are <disfmarker> how are they gonna know ?
speaker: D
text: I know !
speaker: F
text: I <disfmarker>
speaker: D
text: I <disfmarker> I was saying that I think a lot of them are the Networks meeting .
speaker: C
text: Yeah .
speaker: E
text: I think that 's true .
speaker: F
text: Maybe .
speaker: E
text: Yeah , absolutely .
speaker: G
text: Yeah .
speaker: E
text: NSA ,
speaker: D
text: I see a few .
speaker: E
text: a lot of these are <disfmarker> are coming from them .
speaker: E
text: I listened to some of that .
speaker: D
text: Although I see <disfmarker> I see plenty of uh
speaker: C
text: Yeah , we don't have that many acronyms comparatively in this meeting .
speaker: E
text: Yeah .
speaker: E
text: Yeah . I agree .
speaker: C
text: It 's not so bad .
speaker: G
text: Right .
speaker: E
text: And Robustness has a fair amount ,
speaker: E
text: but the NSA group is just very very many .
speaker: A
text: Yeah .
speaker: C
text: Mmm .
speaker: G
text: The recognizer , it is funny .
speaker: G
text: Kept getting PTA for PDA .
speaker: G
text: This is close ,
speaker: F
text: Yeah .
speaker: D
text: Yeah , that 's pretty close .
speaker: G
text: right ,
speaker: G
text: and the PTA was in these , uh , topics about children ,
speaker: C
text: That 's not bad .
speaker: E
text: Yeah .
speaker: G
text: so , anyway .
speaker: E
text: That 's interesting .
speaker: G
text: Is the P - PTA working ?
speaker: E
text: Right and sometimes , I mean , you see a couple of these that are actually " OK 's "
speaker: E
text: so it 's <disfmarker> it 's <disfmarker> may be that they got to the point where <disfmarker> I mean it was low enough understandable <disfmarker>
speaker: E
text: understandability that they weren't entirely sure the person said " OK . "
speaker: E
text: You know , so it isn't really necessarily a an undecipherable acronym ,
speaker: E
text: but just n needs to be double checked .
speaker: C
text: There 's a lot of " OK 's " .
speaker: E
text: Now we get to the comments .
speaker: F
text: The number to the left is the number of incidences ?
speaker: E
text: This <disfmarker>
speaker: D
text: Count .
speaker: E
text: Number of times out of the entire database ,
speaker: D
text: Yep .
speaker: F
text: Uh - huh .
speaker: E
text: w except for that last thirty minutes I haven't checked yet .
speaker: F
text: So CTS is really big here ,
speaker: D
text: Yeah , I wonder what it is .
speaker: F
text: yeah .
speaker: F
text: Yeah .
speaker: A
text: So what is the difference between " papers rustling " and " rustling papers " ?
speaker: F
text: IP ,
speaker: F
text: I know what IP is .
speaker: E
text: I 'd have to listen .
speaker: E
text: I <disfmarker> I I agree .
speaker: E
text: I w I 'd like to standardize these down farther
speaker: E
text: but , um , uh ,
speaker: E
text: uh , to me that sounds equivalent .
speaker: A
text: Yeah .
speaker: E
text: But , I <disfmarker> I 'm a little hesitant to <disfmarker> to collapse across categories unless I actually listen to them .
speaker: A
text: Seems so .
speaker: F
text: OK .
speaker: D
text: Oh I 'm sure we 've said XML more than five times .
speaker: E
text: Well , then , at least now .
speaker: F
text: S s six now , yeah .
speaker: A
text: Now it 's at least six times , yeah .
speaker: E
text: Yeah .
speaker: E
text: Six .
speaker: E
text: OK well <disfmarker>
speaker: F
text: Wh - the self - referential aspect of these <disfmarker> these p
speaker: G
text: I 'm wai
speaker: D
text: Yes , it 's very bad .
speaker: C
text: Yeah .
speaker: G
text: Well this is exactly how people will prove that these meetings do differ because we 're recording , right ?
speaker: D
text: Yes .
speaker: G
text: Y no normally you don't go around saying , " Now you 've said it six times .
speaker: D
text: Yeah <comment> that 's right .
speaker: G
text: Now you 've said "
speaker: E
text: But did you notice that there were seven hundred and eighty five instances of " OK " ?
speaker: E
text: And that 's just without the <disfmarker> without punc punctuation .
speaker: D
text: Yep .
speaker: F
text: No , I didn't .
speaker: A
text: Seven hundred eighty - five instances .
speaker: C
text: Yeah .
speaker: F
text: Yeah .
speaker: D
text: And that 's an underestimate
speaker: E
text: Extra forty one if it 's questioned .
speaker: D
text: cuz they 're
speaker: B
text: Where 's that ?
speaker: F
text: So th
speaker: D
text: Yep .
speaker: E
text: On the page two of acronyms .
speaker: F
text: Yeah .
speaker: C
text: Is this after <disfmarker> like did you do some uh replacements for all the different form of " OK " to this ?
speaker: F
text: Seven hundred eighty .
speaker: E
text: Yeah .
speaker: E
text: Of " OK " , yes .
speaker: C
text: OK .
speaker: E
text: Mm - hmm .
speaker: E
text: So that 's the single existing convention for " OK " .
speaker: B
text: Wait a minute ,
speaker: B
text: w s
speaker: F
text: So now we 're up to seven hundred and eighty eight .
speaker: E
text: Yeah that 's <disfmarker>
speaker: C
text: Although , what 's <disfmarker> there 's one with a slash after it .
speaker: C
text: That 's kind of disturbing .
speaker: E
text: Yeah .
speaker: E
text: That 's <disfmarker> that 's <disfmarker> I looked for that one .
speaker: D
text: Yeah , we 'll have to look at it you know .
speaker: G
text: Yeah .
speaker: C
text: Anyway .
speaker: E
text: I actually explicitly looked for that one ,
speaker: C
text: Mm - hmm .
speaker: E
text: and I think that , um ,
speaker: E
text: I <disfmarker> I 'm not exactly sure about that .
speaker: B
text: Was that somewhere where they were gonna say " new speaker " or something ?
speaker: E
text: No , I looked for that ,
speaker: E
text: but that doesn't actually exist .
speaker: E
text: And it may be ,
speaker: E
text: I don't <disfmarker> I can't explain that .
speaker: C
text: That 's alright .
speaker: C
text: I 'm just pointing that out .
speaker: E
text: I i it 's the only <disfmarker>
speaker: C
text: There 's <disfmarker>
speaker: E
text: it 's the only pattern that has a slash after it ,
speaker: G
text: Well there 's not @ @ .
speaker: E
text: and I think it 's <disfmarker> it 's an epiphenomenon .
speaker: D
text: So I 'll just <disfmarker> I was just looking at the bottom of page three there ,
speaker: D
text: is that " to be " or " not to be " .
speaker: E
text: Yeah .
speaker: E
text: Oh that 's cute .
speaker: B
text: There 's no tilde in front of it ,
speaker: B
text: so .
speaker: E
text: That 's funny .
speaker: E
text: Yeah .
speaker: E
text: OK .
speaker: D
text: OK anyways , sorry .
speaker: E
text: There is th one <disfmarker>
speaker: D
text: " Try to stay on topic , Adam . "
speaker: E
text: Y well , no , that 's r that 's legitimate .
speaker: E
text: So now , uh , comments , you can see they 're listed again ,
speaker: E
text: same deal , with exhaustive listing of everything found in everything except for these final th thirty minutes .
speaker: D
text: OK so , um , on some of these QUALs ,
speaker: E
text: Yeah .
speaker: D
text: are they really QUALs ,
speaker: D
text: or are they glosses ?
speaker: D
text: So like there 's a " QUAL TCL " .
speaker: E
text: " TCL " .
speaker: E
text: Where do you see that ?
speaker: D
text: Uh
speaker: E
text: Oh , oh .
speaker: E
text: The reason is because w it was said " tickle " .
speaker: F
text: What 's a QUAL ?
speaker: D
text: Oh I see , I see .
speaker: C
text: Hmm .
speaker: D
text: So it 's not gloss .
speaker: D
text: OK , I see .
speaker: E
text: Yep .
speaker: D
text: It wasn't said " TCL " .
speaker: C
text: Sh - shouldn't it be " QUAL TICKLE " or something ?
speaker: D
text: Of course .
speaker: C
text: Like <disfmarker> it 's not <disfmarker>
speaker: E
text: On the <disfmarker> in the actual script <disfmarker> in the actual transcript , I s I <disfmarker>
speaker: E
text: So this <disfmarker> this happens in the very first one .
speaker: C
text: Mm - hmm .
speaker: E
text: I actually wrote it as " tickle " .
speaker: C
text: OK .
speaker: E
text: Because we <disfmarker> they didn't say " TCL " , they said " tickle " .
speaker: C
text: Yeah .
speaker: G
text: Right .
speaker: E
text: And then , following that is " QUAL TCL " .
speaker: C
text: Oh I see .
speaker: F
text: I f I forget ,
speaker: C
text: OK .
speaker: F
text: what 's QUAL ?
speaker: E
text: Qual - qualifier .
speaker: B
text: It 's just comment about what they said .
speaker: E
text: Comment .
speaker: C
text: Yeah .
speaker: E
text: Comment or contextual comment .
speaker: C
text: It 's not something you wanna replace <pause> with
speaker: B
text: So they didn't mean " tickle " as in Elmo ,
speaker: C
text: but <disfmarker>
speaker: F
text: Yeah .
speaker: A
text: Tickle ?
speaker: B
text: they meant " tickle " as in <disfmarker>
speaker: D
text: Yeah .
speaker: G
text: Huh .
speaker: F
text: Right .
speaker: G
text: But at some point <disfmarker> I mean , we probably shoul
speaker: D
text: We 'll probably add it to the language model .
speaker: G
text: But we should add it to the dictionar
speaker: G
text: No , to the pronunciation model .
speaker: D
text: Yeah .
speaker: D
text: What did I say ?
speaker: G
text: Language , uh <disfmarker>
speaker: A
text: To the language model <disfmarker> model .
speaker: D
text: Well both .
speaker: D
text: We can go on lan lan add it to both dictionary and language model .
speaker: G
text: Oh lan Oh OK - we OK
speaker: B
text: Add what , Liz ?
speaker: A
text: Yeah .
speaker: G
text: it 's in the language model ,
speaker: G
text: w
speaker: G
text: yeah , but it so it 's the pronunciation model that has to have a pronunciation of " tickle " .
speaker: D
text: Well " tickle " was pronounced " tickle " .
speaker: D
text: Right ?
speaker: B
text: What are you saying ?
speaker: D
text: It 's pronounced the same <disfmarker> it 's pronounced the same as the verb .
speaker: A
text: " tickle " is pronounced " tickle " ?
speaker: G
text: I 'm sorry !
speaker: D
text: So I think it 's the language model that makes it different .
speaker: G
text: Oh , sorry .
speaker: G
text: What I meant is that there should be a pronunciation " tickle " for TCL as a word .
speaker: D
text: Oh I see .
speaker: G
text: And that word in the <disfmarker> in , you know , it stays in the language model wherever it was .
speaker: A
text: Yeah .
speaker: F
text: Mm - hmm .
speaker: D
text: Right .
speaker: D
text: Right .
speaker: G
text: Yeah you never would put " tickle " in the language model in that form ,
speaker: F
text: Right .
speaker: G
text: yeah .
speaker: D
text: Right .
speaker: G
text: Right .
speaker: G
text: There 's actually a bunch of cases like this with people 's names and <disfmarker>
speaker: B
text: So how w there 'd be a problem for doing the language modeling then with our transcripts the way they are .
speaker: G
text: Yes .
speaker: G
text: Yeah .
speaker: G
text: Yeah so th th there there 's a few cases like that where the um , the word needs to be spelled out in <disfmarker> in a consistent way as it would appear in the language ,
speaker: G
text: but there 's not very many of these .
speaker: G
text: Tcl 's one of them .
speaker: D
text: And <disfmarker> and you 'll ha you 'll have to do it sychronously .
speaker: G
text: Um ,
speaker: G
text: y yeah .
speaker: D
text: Right , so y so , whoever 's creating the new models , will have to also go through the transcripts and change them synchronously .
speaker: C
text: It 's just disturbing .
speaker: G
text: Right .
speaker: G
text: Right .
speaker: G
text: We have this <disfmarker> there is this thing I was gonna talk to you about at some point about , you know , what do we do with the dictionary as we 're up updating the dictionary ,
speaker: B
text: Hmm .
speaker: G
text: these changes have to be consistent with what 's in the <disfmarker> Like spelling people 's names and so forth .
speaker: G
text: If we make a spelling correction to their name ,
speaker: G
text: like someone had Deborah Tannen 's name mispelled ,
speaker: G
text: and since we know who that is , you know , we could correct it ,
speaker: D
text: You can correct it .
speaker: G
text: but <disfmarker>
speaker: D
text: Yeah .
speaker: G
text: but we need to make sure we have the mispel
speaker: G
text: If it doesn't get corrected we have to have a pronunciation as a mispelled word in the dictionary .
speaker: G
text: Things like that .
speaker: E
text: Mm - hmm .
speaker: D
text: These are so funny to read .
speaker: E
text: Well , of course now the <disfmarker> the Tannen corre the spelling c change .
speaker: G
text: So .
speaker: E
text: Uh , that 's what gets <disfmarker> I <disfmarker> I picked those up in the frequency check .
speaker: G
text: Right . Right .
speaker: G
text: So if there 's things that get corrected before we get them , it 's <disfmarker> it 's not an issue ,
speaker: G
text: but if there 's things that um , we change later , then we always have to keep our <disfmarker> the dictionary up to date .
speaker: E
text: Mm - hmm .
speaker: G
text: And then , yeah , in the case of " tickle " I guess we would just have a , you know , word " TCL " which <disfmarker>
speaker: B
text: Mm - hmm .
speaker: D
text: You add it to the dictionary .
speaker: G
text: which normally would be an acronym ,
speaker: G
text: you know , " TCL "
speaker: D
text: Right .
speaker: G
text: but just has another pronunciation .
speaker: D
text: Yep .
speaker: E
text: " ICSI " is <disfmarker> is one of those that sometimes people pronounce and sometimes they say " ICSI . "
speaker: D
text: Mm - hmm .
speaker: E
text: So , those that are l are listed in the acronyms , I actually know
speaker: G
text: Oh yeah .
speaker: E
text: they were said as letters .
speaker: E
text: The others , um , e those really do need to be listened to
speaker: E
text: cuz I haven't been able to go to all the IC ICSI things ,
speaker: G
text: Right , exactly .
speaker: E
text: and <disfmarker> <comment> and until they 've been listened to they stay as " ICSI " .
speaker: D
text: Mm - hmm .
speaker: G
text: Right .
speaker: F
text: Don and I were just noticing ,
speaker: F
text: love this one over on page three ,
speaker: F
text: " vocal <disfmarker> vocal gesture mimicking sound of screwing something into head to hold mike in place . "
speaker: C
text: That 's great .
speaker: D
text: It 's this , " rrre - rrre - rrre " .
speaker: D
text: It was me .
speaker: E
text: It was !
speaker: E
text: In fact , it was !
speaker: E
text: Yeah !
speaker: D
text: A lot of these are me
speaker: E
text: He <disfmarker> he s he said <disfmarker> he said get <disfmarker>
speaker: D
text: the <disfmarker> the " beep is said with a high pit high pitch and lengthening . "
speaker: A
text: To head .
speaker: E
text: Yeah , that 's it .
speaker: D
text: That was the <disfmarker> I was imitating uh , beeping out <disfmarker>
speaker: F
text: Beep .
speaker: E
text: Perfect .
speaker: G
text: Oh there is something spelled out " BEEEEEEP "
speaker: F
text: Yeah .
speaker: E
text: Yeah that 's it .
speaker: C
text: Um <disfmarker>
speaker: E
text: That 's it .
speaker: E
text: Yeah , that 's <disfmarker> that 's been changed .
speaker: C
text: Yeah .
speaker: G
text: in the old <disfmarker>
speaker: G
text: Thank you .
speaker: G
text: Because he was saying , " How many E 's do I have to allow for ? "
speaker: C
text: You need a lot of <disfmarker>
speaker: D
text: What I meant was " beep " .
speaker: C
text: You need a lot of qualification Adam .
speaker: E
text: That 's been changed .
speaker: D
text: I guess so .
speaker: E
text: So , exactly , that 's where the lengthening comment c came in .
speaker: D
text: Anyway .
speaker: G
text: Right , thanks ,
speaker: C
text: Subtext .
speaker: E
text: s chan brought it down .
speaker: G
text: yeah .
speaker: D
text: So they 're vocalization ,
speaker: G
text: Right .
speaker: E
text: And those of course get <disfmarker> get picked up in the frequency check
speaker: D
text: glosses .
speaker: E
text: because you see " beep "
speaker: G
text: Right .
speaker: E
text: and you know <disfmarker> I mean it gets kicked out in the spelling ,
speaker: G
text: Right .
speaker: E
text: and it also gets kicked out in the , uh , freq frequency listing .
speaker: G
text: Right .
speaker: E
text: I have the <disfmarker> there 're various things like " breathe " versus " breath " versus " inhale " and , hhh ,
speaker: E
text: you know , I don't know .
speaker: E
text: I <disfmarker> I think they don't have any implications for anything else
speaker: E
text: so it 's like I 'm tempted to leave them for now
speaker: E
text: an and <disfmarker> It 's easy enough to find them when they 're in curly brackets .
speaker: E
text: We can always get an exhaustive listing of these things and find them and change them .
speaker: G
text: Yeah .
speaker: F
text: " Sings finale - type song "
speaker: G
text: Yeah .
speaker: C
text: Yeah , that was in the first meeting .
speaker: F
text: that 's <disfmarker> that 's good .
speaker: D
text: Um ,
speaker: E
text: Yeah , but I don't actually remember what it was .
speaker: E
text: But that was <disfmarker> Eric did that .
speaker: F
text: Yeah .
speaker: E
text: Yeah .
speaker: D
text: So on <disfmarker>
speaker: F
text: Tah - dah !
speaker: F
text: I don't know .
speaker: E
text: I think maybe something like that .
speaker: F
text: Something like that
speaker: F
text: maybe , yeah .
speaker: E
text: Well , that 'd qualify .
speaker: D
text: On the glosses for numbers ,
speaker: E
text: Yeah .
speaker: D
text: it seems like there are lots of different ways it 's being done .
speaker: E
text: OK .
speaker: E
text: Interesting question .
speaker: D
text: There 's a <disfmarker>
speaker: E
text: Yes .
speaker: E
text: OK , now first of all <disfmarker>
speaker: E
text: Ooo - ooo !
speaker: E
text: Very important .
speaker: D
text: " Ooo - ooo . "
speaker: E
text: Uh Chuck <disfmarker> Chuck led to a refinement here
speaker: E
text: which is to add " NUMS " if these are parts of the read numbers .
speaker: E
text: Now you already know i that I had , uh , in places where they hadn't transcribed numbers , I put " numbers " in place of any kind of numbers ,
speaker: E
text: but there are places where they ,
speaker: E
text: um , it <disfmarker> th this convention came later
speaker: E
text: an and at the very first digits task in some transcripts they actually transcribed numbers .
speaker: E
text: And , um ,
speaker: E
text: d
speaker: E
text: Chuck pointed out that this is read speech ,
speaker: E
text: and it 's nice to have the option of ignoring it for certain other prob uh p uh , things .
speaker: E
text: And that 's why there 's this other tag here which occurs a hundred and five <disfmarker> or three hundred and five times right now
speaker: E
text: which is just <disfmarker> well n n " NUMS " by itself
speaker: D
text: " NUMS " ,
speaker: D
text: yeah .
speaker: E
text: which means this is part of the numbers task .
speaker: E
text: I may change it to " digits " .
speaker: E
text: I mean , i with the sed command you can really just change it however you want
speaker: E
text: because it 's systematically encoded , you know ?
speaker: D
text: Yep .
speaker: E
text: Have to think about what 's the best for <disfmarker> for the overall purposes ,
speaker: E
text: but in any case , um , " numbers " and " NUMS " are a part of this digits task thing .
speaker: E
text: Um , now th Then I have these numbers that have quotation marks around them .
speaker: E
text: Um , I didn't want to put them in as gloss comments
speaker: E
text: because then you get the substitution .
speaker: E
text: And actually , th um , <vocalsound> the reason I b did it this way was because I initially started out with the other version ,
speaker: E
text: you have the numbers and you have the full form and the parentheses ,
speaker: E
text: however sometimes people stumble over these numbers they 're saying .
speaker: E
text: So you say , " Seve - seventy eight point two " , or whatever .
speaker: E
text: And there 's no way of capturing that if you 're putting the numbers off to the side .
speaker: E
text: You can't have the seven and <disfmarker>
speaker: D
text: So what 's to the left of these ?
speaker: E
text: The left is i
speaker: E
text: so example the very first one ,
speaker: E
text: it would be , spelled out in words , " point five " .
speaker: D
text: Mm - hmm .
speaker: D
text: OK , that 's what I was asking .
speaker: D
text: Right .
speaker: E
text: Only it 's spelled out in words .
speaker: E
text: So i this is also spelled out in <disfmarker> in words .
speaker: D
text: Point FIVE , yeah .
speaker: E
text: " Point five . "
speaker: D
text: Good .
speaker: E
text: And then , in here , " NUMS " ,
speaker: E
text: so it 's not going to be mistaken as a gloss .
speaker: E
text: It comes out as " NUMS quote dot five " .
speaker: D
text: OK now , the other example is , in the glosses right there ,
speaker: E
text: Thank you .
speaker: D
text: " gloss one one one dash one three zero " .
speaker: C
text: Right .
speaker: E
text: Well now <disfmarker>
speaker: D
text: What <disfmarker> what 's to the left of that ?
speaker: E
text: In that case it 's people saying things like " one one one dash so - and - so "
speaker: E
text: or they 're saying uh " two <disfmarker> I mean zero " whatever .
speaker: D
text: OK .
speaker: E
text: And in that case , it 's part of the numbers task ,
speaker: E
text: and it 's not gonna be included in the read digits anyway ,
speaker: E
text: so <disfmarker> I m in the uh <disfmarker>
speaker: B
text: So there will be a " NUMS " tag on those lines ?
speaker: E
text: There is .
speaker: B
text: Yeah .
speaker: E
text: Yeah .
speaker: E
text: I 've added that all now too .
speaker: D
text: Good .
speaker: C
text: There 's a " numbers " tag <disfmarker>
speaker: G
text: Wait .
speaker: C
text: I 'm sorry I 'm <disfmarker> I didn't follow that last thing .
speaker: E
text: So , so gloss <disfmarker> in the same line that would have " gloss quote one one one dash one thirty " , you 'd have a gloss at the end of the line saying , uh , " curly bracket NUMS curly bracket " .
speaker: C
text: Right .
speaker: E
text: So if you <disfmarker> if you did a , uh , a " grep minus V nums "
speaker: G
text: Oh , so you could do " grep minus V nums " .
speaker: G
text: So that 's the <disfmarker>
speaker: E
text: and you get rid of anything that was read .
speaker: G
text: yeah .
speaker: G
text: So there wouldn't be something like
speaker: C
text: OK .
speaker: G
text: i if somebody said something like , " Boy , I 'm really tired , OK . " and then started reading that would be on a separate line ?
speaker: E
text: Yes .
speaker: G
text: OK great .
speaker: G
text: Cuz I was doing the " grep minus V " quick and dirty
speaker: G
text: and looked like that was working OK ,
speaker: E
text: Mm - hmm .
speaker: G
text: but <disfmarker>
speaker: E
text: Good .
speaker: G
text: Great .
speaker: E
text: Yep .
speaker: G
text: Now why do we <disfmarker> what 's the reason for having like the point five have the " NUMS " on it ?
speaker: G
text: Is that just like when they 're talking about their data or something ?
speaker: E
text: This is more because <disfmarker>
speaker: G
text: Or <disfmarker>
speaker: E
text: Yeah .
speaker: E
text: Oh these are all these , the " NUMS point " , this all where they 're saying " point " something or other .
speaker: G
text: These are all like inside the spontaneous <disfmarker>
speaker: E
text: And the other thing too is for readability of the transcript .
speaker: E
text: I mean if you 're trying to follow this while you 're reading it it 's really hard to read , you know <disfmarker>
speaker: E
text: eh , " so in the data column five has " , you know , " one point five compared to seventy nine point six " ,
speaker: E
text: it 's like when you see the words it 's really hard to follow the argument .
speaker: E
text: And this is just really a <disfmarker> a way of someone who would handle th the data in a more discourse - y way to be able to follow what 's being said .
speaker: G
text: Oh OK .
speaker: D
text: Label it .
speaker: G
text: I see .
speaker: E
text: So this is where Chuck 's , um , overall h architecture comes in ,
speaker: E
text: where we 're gonna have a master file of the channelized data .
speaker: E
text: Um , there will be scripts that are written to convert it into these t these main two uses
speaker: E
text: and th some scripts will take it down th e into a f a for ta take it to a format that 's usable for the recognizer
speaker: E
text: an uh , other scripts will take it to a form that 's usable for the <disfmarker> for linguistics an and discourse analysis .
speaker: E
text: And , um , the implication that <disfmarker> that I have is that th the master copy will stay unchanged .
speaker: E
text: These will just be things that are generated ,
speaker: D
text: Right
speaker: E
text: and
speaker: G
text: OK .
speaker: E
text: e by using scripts .
speaker: D
text: Master copies of superset .
speaker: E
text: When things change then the <disfmarker> the script will cham change
speaker: E
text: but the <disfmarker> but there won't be stored copies of <disfmarker> in different versions of things .
speaker: D
text: Good .
speaker: G
text: So , I guess I 'd have one request here
speaker: G
text: which is just , um , maybe to make it more robust ,
speaker: G
text: th that the tag , whatever you would choose for this type of " NUMS " <comment> where it 's inside the spontaneous speech , is different than the tag that you use for the read speech .
speaker: B
text: Right .
speaker: B
text: Right . That would argue for changing the other ones to be " digits " or something .
speaker: G
text: Um , that way w if we make a mistake parsing , or something , we don't see the " point five " ,
speaker: G
text: or <disfmarker> or it 's not there , then we
speaker: B
text: Mm - hmm .
speaker: G
text: a Just <disfmarker> an And actually for things like " seven eighths " , or
speaker: G
text: people do fractions too I guess ,
speaker: G
text: you <disfmarker> maybe you want one overall tag for sort of that would be similar to that ,
speaker: E
text: Except <disfmarker>
speaker: G
text: or <disfmarker>
speaker: G
text: As long as they 're sep as they 're different strings that we <disfmarker> that 'll make our p sort of processing more robust .
speaker: E
text: Well <disfmarker>
speaker: G
text: Cuz we really will get rid of everything that has the " NUMS " string in it .
speaker: B
text: I suppose what you could do is just make sure that you get rid of everything that has " curly brace NUMS curly brace " .
speaker: E
text: Well <disfmarker>
speaker: E
text: Ex - exactly .
speaker: E
text: Exactly .
speaker: B
text: I mean that would be the <disfmarker>
speaker: E
text: That was <disfmarker> that was my motivation .
speaker: G
text: Yeah .
speaker: E
text: And i these can be changed , like I said .
speaker: E
text: You know , I mean , as I said I was considering changing it to " digits " .
speaker: E
text: And , it just <disfmarker> i you know , it 's just a matter of deciding on whatever it is , and being sure the scripts know .
speaker: B
text: Right .
speaker: G
text: It would probably be safer , if you 're willing , to have a separate tag
speaker: G
text: just because um , then we know for sure .
speaker: G
text: And we can also do counts on them without having to do the processing .
speaker: G
text: But you 're right ,
speaker: G
text: we could do it this way ,
speaker: G
text: it <disfmarker> it should work .
speaker: G
text: Um ,
speaker: B
text: Yeah , and it makes it <disfmarker> I guess the thing about <disfmarker>
speaker: G
text: but it it 's probably not hard for a person to tell the difference
speaker: G
text: because one 's in the context of a <disfmarker> you know , a transcribed word string ,
speaker: B
text: Yeah .
speaker: B
text: Right .
speaker: E
text: The other thing is you can get really so minute with these things
speaker: G
text: and <disfmarker>
speaker: G
text: So <disfmarker>
speaker: E
text: and increase the size of the files and the re and decrease the readability to such an extent by simply something like " percent " .
speaker: E
text: Now I <disfmarker> I could have adopted a similar convention for " percent " ,
speaker: E
text: but somehow percent is not so hard , you know ?
speaker: D
text: Hmm .
speaker: E
text: i It 's just when you have these points and you 're trying to figure out where the decimal places are <disfmarker>
speaker: E
text: And we could always add it later .
speaker: E
text: Percent 's easy to detect .
speaker: E
text: Point however is <disfmarker> is uh a word that has a couple different meanings .
speaker: E
text: And you 'll find both of those in one of these meetings ,
speaker: E
text: where he 's saying " well the first point I wanna make is so - and - so "
speaker: E
text: and he goes through four points ,
speaker: E
text: and also has all these decimals .
speaker: B
text: So Liz , what does the recognizer do ,
speaker: E
text: So .
speaker: B
text: uh ,
speaker: F
text: Hmm .
speaker: B
text: what does the SRI recognizer output for things like that ?
speaker: B
text: " seven point five " .
speaker: B
text: Does it output the word <disfmarker>
speaker: G
text: " Seven point five " .
speaker: B
text: Right ,
speaker: D
text: Well , the numbers ?
speaker: B
text: the word " seven " ?
speaker: B
text: The number " seven " ?
speaker: G
text: The word .
speaker: B
text: The word " seven " , OK .
speaker: F
text: Yeah .
speaker: G
text: Yeah .
speaker: F
text: So I 'd <disfmarker> so " I 'd like <disfmarker> I 'd like to talk about point five " .
speaker: G
text: And <disfmarker> and actually , you know the language <disfmarker>
speaker: G
text: it 's the same point , actually ,
speaker: F
text: Yeah .
speaker: G
text: the <disfmarker> the p you know , the word " to " and the word y th " going to " and " to go to "
speaker: G
text: those are two different " to 's "
speaker: G
text: and so there 's no distinction there .
speaker: B
text: Mm - hmm .
speaker: G
text: It 's just <disfmarker> just the word " point " has <disfmarker>
speaker: G
text: Yeah , every word has only one , yeah e one version
speaker: G
text: even if <disfmarker> even if it 's <disfmarker>
speaker: G
text: A actually even like the word " read " <comment> and " read "
speaker: G
text: Those are two different words .
speaker: G
text: They 're spelled the same way , right ?
speaker: B
text: Mm - hmm .
speaker: G
text: And they 're still gonna be transcribed as READ .
speaker: F
text: Right .
speaker: B
text: Mm - hmm .
speaker: G
text: So ,
speaker: G
text: yeah , I <disfmarker> I like the idea of having this in there ,
speaker: G
text: I just <disfmarker> I was a little bit worried that , um , the tag for removing the read speech <disfmarker>
speaker: G
text: because i What if we have like " read letters "
speaker: G
text: or , I don't know ,
speaker: D
text: We might wanna <disfmarker> just a separate tag that says it 's read .
speaker: G
text: like " read something "
speaker: G
text: like " read "
speaker: G
text: yeah , basically .
speaker: C
text: Mm - hmm .
speaker: G
text: But other than that I it sounds great .
speaker: D
text: Yeah .
speaker: D
text: OK ?
speaker: D
text: Are we done ?
speaker: E
text: Well I wanted to say also regarding the channelized data ,
speaker: D
text: Oh , I guess we 're not done .
speaker: E
text: that , um , Thilo requested , um , that we ge get some segments done by hand to e e s reduce the size of the time bins
speaker: B
text: Yeah .
speaker: E
text: wh like was Chuc - Chuck was mentioning earlier
speaker: E
text: that , um , that , um , if you <disfmarker> if you said , " Oh " and it was in part of a really long , s complex , overlapping segment , that the same start and end times would be held for that one
speaker: D
text: Well <disfmarker>
speaker: E
text: as for the longer utterances ,
speaker: D
text: We did that for one meeting , right ,
speaker: E
text: and <disfmarker>
speaker: D
text: so you have that data don't you ?
speaker: A
text: Yeah , that 's the training data .
speaker: E
text: And he requested that there be , uh , similar , uh , samples done for five minute stretches c involving a variety of speakers and overlapping secti sections .
speaker: E
text: He gave me <disfmarker> he did the <disfmarker> very nice , he <disfmarker> he did some shopping through the data
speaker: A
text: Yeah .
speaker: E
text: and found segments that would be useful .
speaker: E
text: And at this point , all four of the ones that he specified have been done .
speaker: E
text: In addition the I 've <disfmarker> I have the transcribers expanding the amount that they 're doing actually .
speaker: A
text: Oh great .
speaker: E
text: So right now , um , I know that as of today we got an extra fifteen minutes of that type ,
speaker: E
text: and I 'm having them expand the realm on either side of these places where they 've already started .
speaker: A
text: Oh great .
speaker: A
text: OK .
speaker: E
text: But if <disfmarker> if <disfmarker> you know , and I <disfmarker> and he 's gonna give me some more sections that <disfmarker> that he thinks would be useful for this purpose .
speaker: A
text: Yeah .
speaker: A
text: Yeah .
speaker: E
text: Because it 's true ,
speaker: E
text: I mean , if we could do the <disfmarker> the more fine grained tuning of this , uh , using an algorithm , that would be so much more efficient .
speaker: E
text: And , um .
speaker: E
text: So this is gonna be <pause> useful to expand this .
speaker: A
text: So I <disfmarker> I thought we <disfmarker> we sh we sh perhaps we should try to <disfmarker> to start with those channelized versions
speaker: A
text: just to <disfmarker> just to try it .
speaker: A
text: Give it <disfmarker> Give one tr transcriber the <disfmarker> the channelized version of <disfmarker> of my speech - nonspeech detection
speaker: A
text: and look if <disfmarker> if that 's helpful for them ,
speaker: A
text: or just let them try if <disfmarker> if that 's better
speaker: A
text: or If they <disfmarker> if they can <disfmarker>
speaker: E
text: You mean to start from scratch f in a brand new transcript ?
speaker: A
text: Yeah . Yeah .
speaker: A
text: Yeah .
speaker: E
text: That 'd be excellent .
speaker: E
text: Yeah , that 'd be really great .
speaker: E
text: As it stands we 're still in the phase of sort of , um , cleaning up the existing data
speaker: E
text: getting things , uh , in i m more tight tightly time <disfmarker> uh , aligned .
speaker: E
text: I also wanna tell <disfmarker> um , I also wanted to r raise the issue that <disfmarker> OK so , there 's this idea we 're gonna have this master copy of the transcript ,
speaker: E
text: it 's gonna be modified by scripts t into these two different functions .
speaker: E
text: And actually the master <disfmarker>
speaker: B
text: Two or more .
speaker: B
text: Two or more different functions .
speaker: E
text: Two <disfmarker> two or more .
speaker: E
text: And that the master is gonna be the channelized version .
speaker: B
text: Right .
speaker: E
text: So right now we 've taken this i initial one , it was a single channel basically the way it was input .
speaker: E
text: And now , uh , thanks to the advances made in the interface , we can from now on use the channelized part ,
speaker: E
text: and , um , any changes that are made get made in the channelized version kind of thing .
speaker: E
text: But I wanted to get all the finished <disfmarker> all the checks <disfmarker>
speaker: B
text: Yeah , so that has implications for your script .
speaker: C
text: Yeah .
speaker: C
text: So , uh , have those <disfmarker> e e the vis the ten hours that have been transcribed already , have those been channelized ?
speaker: E
text: Yes , they have .
speaker: C
text: And I know <disfmarker> I 've seen @ @ <disfmarker> I 've seen they 've been channelized ,
speaker: D
text: All ten hours ?
speaker: E
text: Except for the missing thirty minutes .
speaker: C
text: but
speaker: D
text: Great .
speaker: C
text: have they uh <disfmarker> have they been <disfmarker> has the time <disfmarker> have the time markings been adjusted , uh , p on a per channel <disfmarker>
speaker: E
text: Uh , for <disfmarker> for a total of like twenty m
speaker: E
text: f for a total of <disfmarker>
speaker: E
text: Let 's see , four times <disfmarker>
speaker: E
text: total of about an <disfmarker> <pause> thirty minutes .
speaker: E
text: That 's <disfmarker> that 's been the case .
speaker: C
text: So ,
speaker: E
text: And plus the training , whatever you have .
speaker: C
text: I guess , I mean , I don't know if we should talk about this now , or not ,
speaker: C
text: but I
speaker: D
text: Well it 's just we 're <pause> missing tea .
speaker: C
text: Yeah , I know .
speaker: D
text: So .
speaker: C
text: No , but I mean my question is like should I wait until all of those are processed , and channelized ,
speaker: C
text: like the time markings are adjusted before I do all the processing ,
speaker: C
text: and we start like branching off into the <disfmarker> into the <disfmarker> our layer of uh transcripts .
speaker: E
text: Well , you know the problem <disfmarker> the problem is that some <disfmarker> some of the adjustments that they 're making are to bring <disfmarker> are to combine bins that were <disfmarker> time bins which were previously separate .
speaker: E
text: And the reason they do that is sometimes there 's a word that 's cut off .
speaker: C
text: Right .
speaker: E
text: And so , i i i it 's true that it 's likely to be adjusted in the way that the words are more complete .
speaker: E
text: And ,
speaker: C
text: OK .
speaker: E
text: so I <disfmarker> it 's gonna be a more reliable thing
speaker: C
text: No I know <disfmarker> I know that adjusting those things are gonna <disfmarker> is gonna make it better .
speaker: E
text: and I 'm not sure <disfmarker>
speaker: E
text: Yeah .
speaker: C
text: I mean I 'm sure about that ,
speaker: C
text: but do you have like a time frame when you can expect like all of it to be done ,
speaker: C
text: or when you expect them to finish it , or <disfmarker>
speaker: E
text: Well partly it depends on how <disfmarker> um , how e effective it will be to apply an algorithm
speaker: E
text: because i this takes time ,
speaker: C
text: Yeah .
speaker: E
text: you know , it takes a couple hours t to do , uh , ten minutes .
speaker: C
text: Yeah .
speaker: C
text: Yeah , I don't doubt it .
speaker: C
text: Um , so .
speaker: B
text: So right now the <disfmarker> what you 're doing is you 're taking the <disfmarker> uh , the o original version
speaker: B
text: and you 're sort of channelizing yourself , right ?
speaker: C
text: Yeah . I 'm doing it myself .
speaker: C
text: I mean i if the time markings aren't different across channels ,
speaker: C
text: like the channelized version really doesn't have any more information .
speaker: B
text: Mm - hmm .
speaker: C
text: So , I was just <disfmarker> I mean , originally I had done before like the channelized versions were coming out .
speaker: B
text: Right .
speaker: B
text: Right .
speaker: C
text: Um ,
speaker: C
text: and so it 's a question of like what <disfmarker>
speaker: B
text: So I <disfmarker> I th I think probably the way it 'll go is that , you know , when we make this first general version and then start working on the script , that script @ @ that will be ma you know primarily come from what you 've done , um , we 'll need to work on a channelized version of those originals .
speaker: C
text: Mm - hmm .
speaker: E
text: Mm - hmm .
speaker: C
text: Mm - hmm .
speaker: B
text: And so it should be pretty much identical to what you have
speaker: E
text: Yep .
speaker: B
text: t except for the one that they 've already tightened the boundaries on .
speaker: E
text: Mm - hmm .
speaker: C
text: Right .
speaker: B
text: Um ,
speaker: E
text: Yeah , I mean <disfmarker>
speaker: B
text: So
speaker: E
text: yeah .
speaker: B
text: uh , and then probably what will happen is as the transcribers finish tightening more and more , you know , that original version will get updated
speaker: B
text: and then we 'll rerun the script and produce better uh versions .
speaker: C
text: OK .
speaker: B
text: But the <disfmarker> I guess the ef the effect for you guys , because you 're pulling out the little wave forms into separate ones , that would mean these boundaries are constantly changing
speaker: B
text: you 'd have to constantly re rerun that ,
speaker: C
text: I know .
speaker: B
text: so , maybe <disfmarker>
speaker: C
text: Right .
speaker: G
text: But that <disfmarker> that 's not hard .
speaker: E
text: But that <disfmarker>
speaker: E
text: Mm - hmm .
speaker: C
text: No .
speaker: G
text: I I think the harder part is making sure that the transc the transcription <disfmarker>
speaker: B
text: OK .
speaker: G
text: So if you b merge two things , then you know that it 's the sum of the transcripts ,
speaker: G
text: but if you split inside something , you don't where the word <disfmarker> which words moved .
speaker: B
text: Mm - hmm .
speaker: B
text: Mm - hmm .
speaker: G
text: And that 's wh that 's where it becomes a little bit <disfmarker> uh , having to rerun the processing .
speaker: B
text: Mm - hmm .
speaker: G
text: The cutting of the waveforms is pretty trivial .
speaker: C
text: Yeah .
speaker: C
text: I mean as long as it can all be done automatically , I mean , then that 's not a concern .
speaker: C
text: You know , if I just have to run three scripts to extract it all and let it run on my computer for an hour and a half , or however long it takes to parse and create all the reference file , that 's not a problem .
speaker: G
text: Right .
speaker: B
text: Mm - hmm .
speaker: B
text: Yeah .
speaker: B
text: Uh - huh .
speaker: B
text: Mm - hmm .
speaker: C
text: Um ,
speaker: C
text: so yeah .
speaker: C
text: As long as we 're at that point .
speaker: C
text: And I know exactly like what the steps will work <disfmarker> what 's going on , in the editing process ,
speaker: B
text: Yeah .
speaker: C
text: so .
speaker: C
text: OK .
speaker: E
text: So that 's <disfmarker> I I mean I could <disfmarker> there were other checks that I did ,
speaker: E
text: but it 's <disfmarker> I think that we 've <disfmarker> unless you think there 's anything else , I think that I 've covered it .
speaker: F
text: Yeah .
speaker: B
text: I can't think of any of the <disfmarker> other ones .
speaker: E
text: OK .
speaker: E
text: Great .
speaker: F
text: OK .
speaker: D
text: Oop !
speaker: D
text: Man !

Meeting summary:
text: The Berkeley Meeting Recorder group discussed digits data, recent ASR results, the status of transcriptions, and disk space and storage format issues.
text: Approximately two hours of digits have been recorded, half of which have been extracted.
text: Researchers doing ASR are looking into methods for generating a better channel-based segmentation to improve recognition results for close-talking microphone data.
text: Transcription checking procedures were reviewed, and efforts to coordinate the channelization and presegmention of data with the tightening of time bins were discussed.
text: The group also talked about downsampling and strategies for coping with low disk space.
text: Digits forms will instruct speakers to read digits separately and not as connected numbers.
text: A tentative decision was made to collect overlapping digits from speakers.
text: Transcribers will be given channelized data that has been segmented for speech/non-speech boundaries to determine whether such pre-processing facilitates the transcription process.
text: Participants have been slow in returning the relevant forms necessary for matching digits data with speaker IDs. Forms containing digits that were written out in English were unsuccessful for obtaining desired prosodic groupings.
text: Acoustic adaptation is problematic for speakers who seldom talk during meetings.
text: Speaker overlap causes recognition errors.
text: The lapel microphone is problematic as it picks up overlapping background speech.
text: More disk space is needed.
text: Loading long waveforms in X Waves is very time consuming.
text: The dictionary must be updated with forms introduced as part of speaker fe008's set of transcription conventions.
text: The ongoing tightening of boundaries on time bins causes segment boundaries to change, indicating potential problems for other ongoing processing tasks.
text: A test set of digits data totalling two hours is nearly complete.
text: Digit extraction has been performed on roughly half of this data.
text: Future work may involve experimenting with the reading of digits in different prosodic groupings.
text: Preliminary ASR results were discussed.
text: Subsequent efforts will involve generating a better channel-based segmentation, and possibly doing echo cancellation, to improve recognition on the close-talking microphone data.
text: Filename conventions are being standardized.
text: Transcription checking procedures have been formalized, including a spell check, producing an exhaustive list of forms identified in the data, attributing every utterance to the appropriate speaker ID, glossing spoken forms with their full orthographic counterparts, e.g. 'cuz' and 'because', transcribing acronyms, and encoding comments, i.e. glosses, vocalic and non-vocalic non-speech events, pragmatic cues, and the standardization of spoken forms, e.g. 'mm-hmm'.
text: Scripts will be used to convert a channelized master copy into forms that are appropriate for doing both recognition and linguistic analysis.
text: Coordinated efforts are in progress between the transcriber pool and speaker mn014 to fine-tune presegmented output to handle data from a variety of speakers and regions of speaker overlap.