ggfox00000's picture
Upload ICSI full mirror (75 wav + ICSI NXT + ICSIplus contrib + MRT)
e0cf8ff verified
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE Meeting SYSTEM "http://www.icsi.berkeley.edu/Speech/mr/Meeting1.dtd">
<Meeting Session="Bmr022" DateTimeStamp="2001-05-03-1445" Version="2" VersionDate="Jan 7 2004">
<Preamble>
<Notes>
me013 left early, and did not read digits.
</Notes>
<Channels>
<Channel Name="chan0" Mic="c1" Transmission="w1" Gain="9" AudioFile="chan0.sph"/>
<Channel Name="chan1" Mic="s1" Transmission="w1" Gain="9" AudioFile="chan1.sph"/>
<Channel Name="chan2" Mic="s1" Transmission="w1" Gain="9" AudioFile="chan2.sph"/>
<Channel Name="chan3" Mic="s1" Transmission="w1" Gain="9" AudioFile="chan3.sph"/>
<Channel Name="chan5" Mic="c1" Transmission="w1" Gain="9" AudioFile="chan5.sph"/>
<Channel Name="chan6" Mic="c2" Transmission="u1" Gain="9" AudioFile="chan6.sph"/>
<Channel Name="chan7" Mic="c2" Transmission="u1" Gain="9" AudioFile="chan7.sph"/>
<Channel Name="chanA" Mic="p1" Transmission="j1" Gain="7" AudioFile="chanA.sph"/>
<Channel Name="chanC" Mic="u3" Transmission="j1" Gain="12" AudioFile="chanC.sph"/>
<Channel Name="chanD" Mic="u3" Transmission="j1" Gain="12" AudioFile="chanD.sph"/>
<Channel Name="chanE" Mic="c2" Transmission="u1" Gain="9" AudioFile="chanE.sph"/>
<Channel Name="chanF" Mic="c2" Transmission="u1" Gain="9" AudioFile="chanF.sph"/>
</Channels>
<Participants DB="icsi1.spk">
<Participant Name="me011" Channel="chan0" Seat="8"/>
<Participant Name="me013" Channel="chan1" Seat="1"/>
<Participant Name="fe016" Channel="chan2" Seat="7"/>
<Participant Name="mn014" Channel="chan3" Seat="2"/>
<Participant Name="me018" Channel="chan5" Seat="6"/>
<Participant Name="fe008" Channel="chanA" Seat="3"/>
</Participants>
</Preamble>
<Transcript StartTime="0.0" EndTime="2977.79">
<Segment StartTime="0.000" EndTime="0.680" Participant="me013">
<VocalSound Description="clears throat"/>
</Segment>
<Segment StartTime="0.269" EndTime="1.330" Participant="me018">
Is it on? <NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="0.449" EndTime="1.537" Participant="me011">
O_K, here we go.
</Segment>
<Segment StartTime="3.755" EndTime="8.237" Participant="me013">
Uh, so - uh, so I c- I definitely have to leave at three-thirty today for <Pause/> whatever. That's -
</Segment>
<Segment StartTime="4.199" EndTime="4.719" Participant="me011">
So -
</Segment>
<Segment StartTime="6.633" EndTime="7.545" CloseMic="false">
<NonVocalSound Description="door closes"/>
</Segment>
<Segment StartTime="7.694" EndTime="10.181" Participant="me011">
Definitely have to go to tea. So - <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="9.593" EndTime="12.893" Participant="me013">
Yeah, they're - they're having birthday cake and such and so I can't miss that.
</Segment>
<Segment StartTime="10.181" EndTime="11.200" Participant="me011">
That too, but -
</Segment>
<Segment StartTime="11.930" EndTime="13.202" Participant="fe016">
You're a May birthday, right?
</Segment>
<Segment StartTime="12.893" EndTime="14.573" Participant="me013">
I'm a May birthday, yeah, so I have to -
</Segment>
<Segment StartTime="14.132" EndTime="15.288" Participant="mn014">
Oops. <Comment Description="interjection"/>
</Segment>
<Segment StartTime="14.600" EndTime="16.194" Participant="fe016">
<Emphasis> Barbara </Emphasis> told me. Barbara Peskin.
</Segment>
<Segment StartTime="15.376" EndTime="16.999" Participant="me013">
Yeah. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="18.710" EndTime="20.082" Participant="me011">
Um -
</Segment>
<Segment StartTime="20.600" EndTime="21.687" Participant="me011">
So,
</Segment>
<Segment StartTime="21.687" EndTime="28.820" Participant="me011">
only a couple of agenda items, since no one sent me email for agenda items. Uh, the first is the I_B_M transcripts. I'd like to
</Segment>
<Segment StartTime="29.201" EndTime="33.480" Participant="me011">
uh, <Emphasis> mention </Emphasis> - I s- I spoke with <Emphasis> several </Emphasis> of you about this, but just to
</Segment>
<Segment StartTime="34.000" EndTime="35.783" Participant="me011">
brainstorm a little bit about what we can do with it.
</Segment>
<Segment StartTime="35.511" EndTime="36.335" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="36.093" EndTime="41.075" Participant="me011">
So we got back the I_B_M transcript, and the <Emphasis> accuracy </Emphasis> looks O_K. There are - I mean, there are areas which are
</Segment>
<Segment StartTime="41.075" EndTime="44.593" Participant="me011">
clearly wrong and there are a lot of areas where they put <Emphasis> question </Emphasis> marks,
</Segment>
<Segment StartTime="44.593" EndTime="49.280" Participant="me011">
where the acoustics weren't very good. And I think that's <Emphasis> fine. </Emphasis> Putting it in question marks is better than doing it wrong.
</Segment>
<Segment StartTime="49.380" EndTime="52.468" Participant="me011">
The <Emphasis> big </Emphasis> problem was, they had the <Emphasis> wrong </Emphasis> number of beeps in it. <Comment Description="while smiling"/>
</Segment>
<Segment StartTime="52.610" EndTime="53.308" Participant="mn014">
Oops. <Comment Description="interjection"/>
</Segment>
<Segment StartTime="52.870" EndTime="54.625" Participant="me011">
So it didn't align.
</Segment>
<Segment StartTime="54.920" EndTime="55.969" Participant="me013">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="55.010" EndTime="56.779" Participant="me011">
And that's <Emphasis> exactly </Emphasis> what I was <Emphasis> afraid </Emphasis> of.
</Segment>
<Segment StartTime="57.260" EndTime="65.609" Participant="me011">
And I went in, and more or less by <Emphasis> hand, </Emphasis> <Emphasis> corrected </Emphasis> it, by loading it - I wrote a script that will convert it to the multi- the Channeltrans format,
</Segment>
<Segment StartTime="66.240" EndTime="68.234" Participant="me011">
looked at it in - in Channeltrans and
</Segment>
<Segment StartTime="68.731" EndTime="72.675" Participant="me011">
found the places where it got a- unsynchronized, and then either -
</Segment>
<Segment StartTime="71.628" EndTime="72.286" Participant="fe008">
Hmm.
</Segment>
<Segment StartTime="72.972" EndTime="73.936" Participant="mn014">
Inserted ones. <Comment Description="completing [me011]'s utterance"/>
</Segment>
<Segment StartTime="73.140" EndTime="77.117" Participant="me011">
And in <Emphasis> this </Emphasis> case only - only had to remove beeps, because that was th- <Emphasis> always </Emphasis> the error,
</Segment>
<Segment StartTime="77.600" EndTime="80.959" Participant="me011">
is that they put in it <Emphasis> extraneous </Emphasis> beeps. But it's <Emphasis> not </Emphasis> easy to <Emphasis> do, </Emphasis>
</Segment>
<Segment StartTime="79.271" EndTime="79.928" Participant="fe008">
Hmm.
</Segment>
<Segment StartTime="80.959" EndTime="82.982" Participant="me011">
because the whole thing gets
</Segment>
<Segment StartTime="82.982" EndTime="89.324" Participant="me011">
offset, and basically, it's assigning the wrong speaker to the text, and it all gets unaligned. So it's very difficult
</Segment>
<Segment StartTime="88.972" EndTime="89.524" Participant="fe008">
Hmm.
</Segment>
<Segment StartTime="89.324" EndTime="91.580" Participant="me011">
to <Emphasis> do. </Emphasis> So it took me several hours
</Segment>
<Segment StartTime="92.100" EndTime="92.779" Participant="me013">
So this is -
</Segment>
<Segment StartTime="92.290" EndTime="93.817" Participant="me011">
just to do that.
</Segment>
<Segment StartTime="93.161" EndTime="94.211" Participant="mn014">
For one meeting.
</Segment>
<Segment StartTime="93.321" EndTime="96.711" Participant="me013">
this is one - it's one hour of - of - of speech?
</Segment>
<Segment StartTime="95.604" EndTime="96.141" Participant="me011">
Yep.
</Segment>
<Segment StartTime="96.711" EndTime="99.026" Participant="me013">
And it took you a few hours to - to do it.
</Segment>
<Segment StartTime="98.580" EndTime="101.287" Participant="me011">
It took me a couple hours to write the scripts, and then
</Segment>
<Segment StartTime="101.610" EndTime="103.133" Participant="me011">
it - it probably took me
</Segment>
<Segment StartTime="103.924" EndTime="110.576" Participant="me011">
maybe forty-five minutes, <Emphasis> just </Emphasis> going <Emphasis> through </Emphasis> it. Now obviously it will be a lot <Emphasis> faster </Emphasis> from now <Emphasis> on, </Emphasis> because now I sort of understand how it works.
</Segment>
<Segment StartTime="111.120" EndTime="116.643" Participant="me011">
But, I think if we had some way - uh some <Emphasis> tool </Emphasis> that made it easier to insert and delete beeps
</Segment>
<Segment StartTime="117.260" EndTime="123.535" Participant="me011">
it would make it a lot easier. Cuz <Emphasis> one </Emphasis> of the problems is that it takes a very long <Emphasis> time </Emphasis> when you make a change to load it back up in the <Emphasis> channel </Emphasis> transcriber.
</Segment>
<Segment StartTime="123.026" EndTime="123.678" Participant="mn014">
Yep.
</Segment>
<Segment StartTime="123.869" EndTime="125.670" Participant="fe008">
Yeah, that's true. I've noticed that. Yeah.
</Segment>
<Segment StartTime="125.880" EndTime="129.913" Participant="me018">
<Emphasis> One </Emphasis> of the things that <Emphasis> Adam </Emphasis> said that I thought would be a good <Emphasis> idea </Emphasis> would be, um,
</Segment>
<Segment StartTime="125.890" EndTime="126.856" Participant="me011">
And so there <Emphasis> may </Emphasis> be -
</Segment>
<Segment StartTime="126.046" EndTime="127.380" Participant="fe008">
Which makes sense.
</Segment>
<Segment StartTime="129.913" EndTime="134.991" Participant="me018">
if we g- used different <Emphasis> beeps. </Emphasis> So for example if we <Emphasis> alternated </Emphasis> between two beeps, a high and a low.
</Segment>
<Segment StartTime="135.135" EndTime="136.008" Participant="me013">
<Emphasis> He </Emphasis> said that?
</Segment>
<Segment StartTime="135.439" EndTime="136.038" Participant="me018">
th-
</Segment>
<Segment StartTime="136.620" EndTime="138.895" Participant="me018">
Uh, well in - in some email that, uh, we had.
</Segment>
<Segment StartTime="136.640" EndTime="138.210" Participant="fe008">
Oh, on the email.
</Segment>
<Segment StartTime="136.700" EndTime="137.674" Participant="mn014">
For -
</Segment>
<Segment StartTime="138.120" EndTime="138.950" Participant="me013">
Oh, oh, O_K.
</Segment>
<Segment StartTime="138.763" EndTime="139.323" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="138.950" EndTime="141.136" Participant="me011">
I didn't <Emphasis> just </Emphasis> say that, no. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="139.817" EndTime="141.470" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="139.950" EndTime="141.924" Participant="me018">
Yeah. Um - Because <Emphasis> then </Emphasis> -
</Segment>
<Segment StartTime="140.268" EndTime="142.740" Participant="me013">
<VocalSound Description="laugh-breath"/>
</Segment>
<Segment StartTime="141.136" EndTime="147.848" Participant="me011">
So th- so this is the o- the other <Emphasis> approach </Emphasis> which is, what do we do in the <Emphasis> future, </Emphasis> to try to make this less common? But it's <Emphasis> still </Emphasis> gonna happen.
</Segment>
<Segment StartTime="143.117" EndTime="143.833" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="148.680" EndTime="154.601" Participant="fe008">
Well, and then the <Emphasis> other </Emphasis> possibility was - e- that we provide them with a - a file that already has the beeps <Emphasis> in </Emphasis> it or something. Wasn't that what you said?
</Segment>
<Segment StartTime="149.370" EndTime="149.793" Participant="me011">
So -
</Segment>
<Segment StartTime="150.900" EndTime="151.395" Participant="me013">
Hunh.
</Segment>
<Segment StartTime="153.900" EndTime="156.246" Participant="me018">
Sort of a text template, but I don't know how
</Segment>
<Segment StartTime="154.705" EndTime="160.457" Participant="me013">
<VocalSound Description="breath"/> <VocalSound Description="sniff"/> <VocalSound Description="breath"/>
</Segment>
<Segment StartTime="155.340" EndTime="155.884" Participant="fe008">
Uh-huh.
</Segment>
<Segment StartTime="156.513" EndTime="163.678" Participant="me011">
Yeah, we don't know what their process is. So I had two ideas. The first was to provide them a text template that had both the beeps in it and the speaker I_Ds.
</Segment>
<Segment StartTime="156.850" EndTime="157.767" Participant="me018">
we can do that.
</Segment>
<Segment StartTime="161.020" EndTime="161.691" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="164.220" EndTime="167.419" Participant="me011">
You know, just "male-female", "English-nonEnglish", "one two three four".
</Segment>
<Segment StartTime="168.190" EndTime="168.726" Participant="me011">
Um -
</Segment>
<Segment StartTime="168.849" EndTime="169.893" Participant="me013">
Can I - I - I just -
</Segment>
<Segment StartTime="169.460" EndTime="170.680" Participant="me011">
And they just filled it in.
</Segment>
<Segment StartTime="170.849" EndTime="171.079" Participant="me013">
<VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="171.079" EndTime="174.846" Participant="me013">
How- how many - how many beeps are there, and how many do we- were they -
</Segment>
<Segment StartTime="172.903" EndTime="174.694" Participant="mn014">
<VocalSound Description="breath-laugh"/>
</Segment>
<Segment StartTime="174.846" EndTime="176.053" Participant="me013">
d- were - were off?
</Segment>
<Segment StartTime="176.430" EndTime="182.203" Participant="me011">
It was like a hundred twenty, and they had a hundred twenty-three or something like that. Is that right?
</Segment>
<Segment StartTime="181.390" EndTime="181.857" Participant="me013">
Alright.
</Segment>
<Segment StartTime="181.980" EndTime="183.418" Participant="me018">
Well, l- I- I thought it was a lot <Emphasis> more </Emphasis> than that.
</Segment>
<Segment StartTime="182.196" EndTime="182.755" Participant="me013">
And is it a -
</Segment>
<Segment StartTime="183.489" EndTime="184.733" Participant="me011">
Well I - I don't remember.
</Segment>
<Segment StartTime="184.940" EndTime="186.911" Participant="me018">
They were <Emphasis> three </Emphasis> off, basically.
</Segment>
<Segment StartTime="186.330" EndTime="188.313" Participant="me013">
Yeah, and it was a hundred-ish.
</Segment>
<Segment StartTime="186.730" EndTime="188.815" Participant="fe016">
And this is the mixed signal?
</Segment>
<Segment StartTime="187.130" EndTime="188.221" Participant="fe008">
<Emphasis> Oh! </Emphasis>
</Segment>
<Segment StartTime="188.221" EndTime="189.030" Participant="fe008">
Hmm.
</Segment>
<Segment StartTime="188.313" EndTime="189.979" Participant="me013">
So - so if you get one -
</Segment>
<Segment StartTime="189.979" EndTime="193.367" Participant="me013">
uh, uh, excuse me. If you get one off, it - t- everything is off <Uncertain> cuz of the alignment </Uncertain> right?
</Segment>
<Segment StartTime="193.440" EndTime="193.897" Participant="me011">
Yep.
</Segment>
<Segment StartTime="193.834" EndTime="194.503" Participant="mn014">
Yep.
</Segment>
<Segment StartTime="194.241" EndTime="197.150" Participant="me013">
Uh, and this is all in one file that's continuous.
</Segment>
<Segment StartTime="196.589" EndTime="197.081" Participant="me011">
Yep.
</Segment>
<Segment StartTime="196.630" EndTime="197.029" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="197.370" EndTime="198.738" Participant="me013">
So why don't you make it multiple files?
</Segment>
<Segment StartTime="199.040" EndTime="199.978" Participant="me011">
How would that help?
</Segment>
<Segment StartTime="200.370" EndTime="203.647" Participant="me013">
Because then if they have one off, then - then it would only screw up that file.
</Segment>
<Segment StartTime="203.990" EndTime="206.384" Participant="me011">
Oh, you mean just break the one hour into
</Segment>
<Segment StartTime="206.579" EndTime="207.214" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="206.880" EndTime="207.928" Participant="me011">
a few chunks.
</Segment>
<Segment StartTime="207.590" EndTime="210.371" Participant="me013">
I mean, it seems now, if you just ha- make one mistake then everything is off.
</Segment>
<Segment StartTime="210.850" EndTime="216.008" Participant="me018">
Well the only - the only question about <Emphasis> that </Emphasis> that I have is, um, I think Brian has to put all this stuff onto a <Emphasis> tape. </Emphasis>
</Segment>
<Segment StartTime="216.008" EndTime="217.321" Participant="me018">
So I don't know whether -
</Segment>
<Segment StartTime="216.105" EndTime="216.580" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="218.624" EndTime="220.920" Participant="me011">
I'm sure they would prefer it sort of one hour.
</Segment>
<Segment StartTime="218.850" EndTime="221.724" Participant="me018">
Can he send them - I guess he could send them multiple
</Segment>
<Segment StartTime="221.278" EndTime="222.039" Participant="fe008">
<NonVocalSound Description="cell phone ringing"/>
</Segment>
<Segment StartTime="222.039" EndTime="222.568" Participant="fe008">
Oh! <Comment Description="interjection"/> <Comment Description="surprised by cell phone"/>
</Segment>
<Segment StartTime="222.180" EndTime="223.046" Participant="me018">
tapes <Pause/>
</Segment>
<Segment StartTime="222.568" EndTime="232.771" Participant="fe008">
<NonVocalSound Description="mike noise"/> <NonVocalSound Description="cell phone ringing"/>
</Segment>
<Segment StartTime="223.600" EndTime="224.468" Participant="me018">
Uh -
</Segment>
<Segment StartTime="224.490" EndTime="225.827" Participant="me013">
Yeah, just say, "O_K, is -"
</Segment>
<Segment StartTime="226.580" EndTime="227.819" Participant="me013">
ten minutes is -" I mean,
</Segment>
<Segment StartTime="227.819" EndTime="233.640" Participant="me013">
maybe there's other things to do that are more <Emphasis> clever, </Emphasis> but this just seemed to be the sort of the obvious thing because, again, if you make <Emphasis> one </Emphasis> <Emphasis> mistake, </Emphasis>
</Segment>
<Segment StartTime="233.640" EndTime="235.861" Participant="me013">
then everything after that mistake is <Emphasis> off. </Emphasis>
</Segment>
<Segment StartTime="233.862" EndTime="234.380" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="236.476" EndTime="238.007" Participant="me013">
And, uh -
</Segment>
<Segment StartTime="237.740" EndTime="241.794" Participant="me018">
Well, the only other issue is we'd have to worry about reassembling them in the proper order.
</Segment>
<Segment StartTime="241.794" EndTime="242.694" Participant="me018">
Uh -
</Segment>
<Segment StartTime="242.496" EndTime="243.115" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="243.460" EndTime="245.707" Participant="me011">
That - I mean, just naming schemes will get -
</Segment>
<Segment StartTime="247.040" EndTime="252.491" Participant="me011">
We can definitely do that. So t- so one question is, are there good places in the files where we can really do that? <Comment Description="last word while laughing"/>
</Segment>
<Segment StartTime="251.726" EndTime="258.051" Participant="fe008">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="253.141" EndTime="255.397" Participant="fe016">
Well, the other thing - You can -
</Segment>
<Segment StartTime="253.970" EndTime="258.142" Participant="me011">
I mean, so - so - so someone will have to go through them and listen to them and pick a place to break them.
</Segment>
<Segment StartTime="256.581" EndTime="257.182" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="259.960" EndTime="264.396" Participant="fe016">
The <Emphasis> other </Emphasis> thing you <Emphasis> can </Emphasis> do- This is on the mixed signal, <Comment Description="rising intonation"/> or are these the individual -
</Segment>
<Segment StartTime="261.841" EndTime="268.476" Participant="fe008">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="265.430" EndTime="267.255" Participant="fe016">
the ones with the beeps that they're getting,
</Segment>
<Segment StartTime="267.255" EndTime="268.872" Participant="fe016">
that they made mistakes on is
</Segment>
<Segment StartTime="269.235" EndTime="271.206" Participant="me011">
They are played from the
</Segment>
<Segment StartTime="269.524" EndTime="270.771" Participant="fe016">
the <Emphasis> mixed </Emphasis> one?
</Segment>
<Segment StartTime="271.680" EndTime="272.723" Participant="me018">
Individual channels. <Comment Description="completing [me011]'s utterance"/>
</Segment>
<Segment StartTime="271.818" EndTime="273.072" Participant="mn014">
Individual channels. <Comment Description="completing [me011]'s utterance"/>
</Segment>
<Segment StartTime="272.210" EndTime="272.975" Participant="me011">
individual.
</Segment>
<Segment StartTime="272.220" EndTime="274.692" Participant="fe016">
Or they're indivi- If it's individual, um -
</Segment>
<Segment StartTime="272.557" EndTime="273.031" CloseMic="false">
<NonVocalSound Description="high pitched beep"/>
</Segment>
<Segment StartTime="275.742" EndTime="276.695" Participant="fe016">
y- c- we can -
</Segment>
<Segment StartTime="277.155" EndTime="278.963" Participant="fe016">
<Emphasis> probably </Emphasis> run a forced <Emphasis> alignment, </Emphasis>
</Segment>
<Segment StartTime="279.850" EndTime="282.300" Participant="fe016">
where you c- include the beeps as words
</Segment>
<Segment StartTime="283.040" EndTime="285.410" Participant="fe016">
and pretty much figure out where the <Emphasis> errors </Emphasis> are.
</Segment>
<Segment StartTime="285.756" EndTime="288.057" Participant="fe016">
I don't think we could do it on the <Emphasis> mixed </Emphasis> signal, cuz it -
</Segment>
<Segment StartTime="288.530" EndTime="291.938" Participant="fe016">
But on the individual channels that would probably work, <Emphasis> if </Emphasis> they have enough
</Segment>
<Segment StartTime="289.449" EndTime="290.683" Participant="me018">
<VocalSound Description="inbreath"/> <Comment Description="as if to speak"/>
</Segment>
<Segment StartTime="292.350" EndTime="294.130" Participant="fe016">
words in the transcript.
</Segment>
<Segment StartTime="294.130" EndTime="296.320" Participant="me018">
Yeah, we - In fact, that's - Yeah, maybe we -
</Segment>
<Segment StartTime="294.780" EndTime="299.040" Participant="fe016">
So, I mean, that's pretty quick to run. It - it's, um -
</Segment>
<Segment StartTime="300.130" EndTime="300.961" Participant="fe016">
I mean, we could <Emphasis> try </Emphasis> it.
</Segment>
<Segment StartTime="300.961" EndTime="302.781" Participant="fe016">
Cuz if a beep is treated as a
</Segment>
<Segment StartTime="302.589" EndTime="306.210" Participant="me011">
You mean, so, actually put - put the wavefile in with beep in it.
</Segment>
<Segment StartTime="303.137" EndTime="304.902" Participant="fe016">
unique word, "beep" - <Comment Description="voice raised due to overlap"/>
</Segment>
<Segment StartTime="306.538" EndTime="308.692" Participant="fe016">
Put in - put "beep" in as a word.
</Segment>
<Segment StartTime="306.820" EndTime="308.808" Participant="me011">
And pu- and have a beep model.
</Segment>
<Segment StartTime="308.970" EndTime="311.550" Participant="me018">
We <Emphasis> have </Emphasis> the original <Emphasis> wavefile </Emphasis> with all the beeps.
</Segment>
<Segment StartTime="308.988" EndTime="310.115" Participant="fe016">
Yeah. Yeah. Well -
</Segment>
<Segment StartTime="310.115" EndTime="314.262" Participant="fe016">
the beep model - Actually, you could <Emphasis> train </Emphasis> a beep model. That - that's a good idea.
</Segment>
<Segment StartTime="313.711" EndTime="317.708" Participant="me018">
It would be very good. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="314.109" EndTime="317.620" Participant="me013">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="314.900" EndTime="315.390" Participant="fe016">
Um -
</Segment>
<Segment StartTime="314.921" EndTime="317.578" Participant="me011">
Yes, it would be, cuz it's very, very regular. <Comment Description="while laughing"/>
</Segment>
<Segment StartTime="315.769" EndTime="316.455" Participant="fe016">
Yeah.
</Segment>
<Segment StartTime="315.790" EndTime="319.132" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="317.360" EndTime="318.797" Participant="fe016">
Yeah. So, um -
</Segment>
<Segment StartTime="317.620" EndTime="322.222" Participant="me013">
Oh. Kind of low variance, wouldn't that be? <VocalSound Description="laugh"/> You sort of <Pause/> might end up with
</Segment>
<Segment StartTime="319.132" EndTime="321.940" Participant="mn014">
Yeah. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="319.230" EndTime="321.416" Participant="me018">
Yeah, <Emphasis> very </Emphasis> low. <Comment Description="while laughing"/>
</Segment>
<Segment StartTime="319.365" EndTime="319.983" Participant="me011">
Yeah. <Comment Description="while laughing"/>
</Segment>
<Segment StartTime="319.550" EndTime="324.038" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="321.851" EndTime="323.873" Participant="fe016">
Um, that might actually -
</Segment>
<Segment StartTime="322.222" EndTime="323.734" Participant="me013">
some infinities there, but - <Comment Description="voice raised on &quot;infinities&quot; due to overlap"/>
</Segment>
<Segment StartTime="322.422" EndTime="324.264" Participant="me011">
You have to - may - add some jitter to it.
</Segment>
<Segment StartTime="323.734" EndTime="324.744" Participant="me013">
Can I see that? <Comment Description="whispered to [fe008], regarding her PalmPilot"/>
</Segment>
<Segment StartTime="323.749" EndTime="344.604" CloseMic="false">
<Comment Description="two parallel conversations, [me013] and [fe008] regarding PalmPilot, and all others regarding beep files"/>
</Segment>
<Segment StartTime="324.142" EndTime="326.065" Participant="fe016">
I mean, that might actually work, because you'll -
</Segment>
<Segment StartTime="325.179" EndTime="326.067" Participant="me013">
Where's the case?
</Segment>
<Segment StartTime="326.565" EndTime="329.670" Participant="fe016">
I guess the trick is figuring out, you know, where it doesn't align? <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="329.670" EndTime="332.164" Participant="fe016">
But if it's a problem of <Emphasis> extra </Emphasis> beeps,
</Segment>
<Segment StartTime="332.164" EndTime="334.180" Participant="fe016">
rather than <Emphasis> missing </Emphasis> beeps, then -
</Segment>
<Segment StartTime="334.750" EndTime="335.218" Participant="fe016">
um -
</Segment>
<Segment StartTime="335.629" EndTime="336.534" Participant="fe016">
that's easier
</Segment>
<Segment StartTime="336.641" EndTime="338.025" Participant="me018">
It could t- it could -
</Segment>
<Segment StartTime="337.480" EndTime="339.492" Participant="fe016">
and it might work. Oh.
</Segment>
<Segment StartTime="338.025" EndTime="340.242" Participant="me018">
There could be some missing ones. But -
</Segment>
<Segment StartTime="340.069" EndTime="340.915" Participant="me013">
So is this a
</Segment>
<Segment StartTime="340.380" EndTime="342.168" Participant="me011">
It's just in <Emphasis> this </Emphasis> case they were not.
</Segment>
<Segment StartTime="340.915" EndTime="342.540" Participant="me013">
<Emphasis> seven </Emphasis> or something? Or - What is it?
</Segment>
<Segment StartTime="341.672" EndTime="343.430" Participant="fe008">
M_one-hundred. <Comment Description="to [me013], model number of her PalmPilot"/>
</Segment>
<Segment StartTime="342.796" EndTime="350.179" Participant="me011">
So I think - uh, Chuck had a good explanation for it which I liked, which is these - they're listening to it and so they write something down, and let's say they miss it, they <Emphasis> rewind. </Emphasis>
</Segment>
<Segment StartTime="343.261" EndTime="344.740" Participant="me013">
M_one-hundred. Oh.
</Segment>
<Segment StartTime="344.346" EndTime="353.018" Participant="fe008">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="344.740" EndTime="345.640" Participant="me013">
<VocalSound Description="breath"/>
</Segment>
<Segment StartTime="351.050" EndTime="356.970" Participant="me011">
Well, they hear the beep again. Was that <Emphasis> that </Emphasis> beep, or was that a <Emphasis> different </Emphasis> beep? So that's why Chuck was suggesting different tones. <Emphasis> My </Emphasis> original thought
</Segment>
<Segment StartTime="353.020" EndTime="353.882" Participant="fe016">
Oh, yeah.
</Segment>
<Segment StartTime="356.970" EndTime="359.075" Participant="me011">
was, you could have a different tone for each <Emphasis> speaker. </Emphasis>
</Segment>
<Segment StartTime="359.075" EndTime="360.733" Participant="me011">
You know, there's plenty of <Emphasis> tone </Emphasis> space.
</Segment>
<Segment StartTime="361.061" EndTime="362.919" Participant="me011">
And that might help <Emphasis> cue </Emphasis>
</Segment>
<Segment StartTime="361.168" EndTime="362.265" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="363.600" EndTime="364.887" Participant="me011">
the <Emphasis> transcriptionist. </Emphasis>
</Segment>
<Segment StartTime="365.306" EndTime="367.340" Participant="me011">
You know, give them a little <Emphasis> cue </Emphasis> about where they <Emphasis> are. </Emphasis>
</Segment>
<Segment StartTime="367.340" EndTime="370.330" Participant="me013">
Or you could - you could have ascending tones, or something.
</Segment>
<Segment StartTime="371.610" EndTime="372.380" Participant="me011">
What do you mean?
</Segment>
<Segment StartTime="372.149" EndTime="373.823" Participant="fe016">
<VocalSound Description="laugh-breath"/>
</Segment>
<Segment StartTime="372.700" EndTime="373.507" Participant="me013">
Uh -
</Segment>
<Segment StartTime="373.781" EndTime="375.336" Participant="me013">
Or - <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="373.823" EndTime="375.310" Participant="fe016">
Yeah. <Comment Description="whispered"/> <VocalSound Description="laugh-breath"/>
</Segment>
<Segment StartTime="374.050" EndTime="376.322" Participant="me018">
Increasingly high - higher frequencies.
</Segment>
<Segment StartTime="375.310" EndTime="380.158" Participant="fe016">
You could have, um, each speaker in the meeting say "beep" and record it and that will be their pro- <Comment Description="while smiling"/>
</Segment>
<Segment StartTime="376.588" EndTime="377.801" Participant="me013">
<VocalSound Description="vocalized outbreath"/>
</Segment>
<Segment StartTime="378.620" EndTime="387.390" Participant="me013">
<VocalSound Description="laugh"/> No, I just - thi- I don't know. If you have a hundred or something just - just sort of move them up i- mu- up a - a half tone or something for - for <VocalSound Description="laugh"/> each one, and then -
</Segment>
<Segment StartTime="378.895" EndTime="379.759" Participant="me011">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="379.010" EndTime="382.399" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="380.771" EndTime="381.067" Participant="fe016">
<VocalSound Description="hiccup"/>
</Segment>
<Segment StartTime="381.067" EndTime="382.451" Participant="fe016">
<VocalSound Description="laugh"/> Sorry.
</Segment>
<Segment StartTime="383.239" EndTime="385.100" Participant="fe016">
<VocalSound Description="breath-laugh"/>
</Segment>
<Segment StartTime="386.520" EndTime="387.160" Participant="me018">
<VocalSound Description="breath-laugh"/>
</Segment>
<Segment StartTime="387.160" EndTime="391.303" Participant="me011">
<Emphasis> That's </Emphasis> what I was <Emphasis> saying. </Emphasis> Is that - that you could have - <Emphasis> each </Emphasis> speaker could have their own <Emphasis> tone. </Emphasis>
</Segment>
<Segment StartTime="388.150" EndTime="388.912" Participant="me013">
Oh was it? Oh.
</Segment>
<Segment StartTime="389.240" EndTime="390.860" Participant="me013">
See, I should <Emphasis> listen. </Emphasis> Yeah?
</Segment>
<Segment StartTime="390.825" EndTime="391.586" Participant="fe016">
Hmm.
</Segment>
<Segment StartTime="391.303" EndTime="393.112" Participant="me011">
And you know, since there are no more than,
</Segment>
<Segment StartTime="393.112" EndTime="395.628" Participant="me011">
you know, ten speakers or so per meeting,
</Segment>
<Segment StartTime="393.410" EndTime="393.770" Participant="fe008">
Oh.
</Segment>
<Segment StartTime="394.179" EndTime="395.050" Participant="fe008">
Well -
</Segment>
<Segment StartTime="395.779" EndTime="396.665" Participant="fe008">
<VocalSound Description="inbreath"/> <Comment Description="as if to speak"/>
</Segment>
<Segment StartTime="396.130" EndTime="397.560" Participant="me011">
there's plenty of tone space.
</Segment>
<Segment StartTime="397.429" EndTime="397.959" Participant="fe008">
But -
</Segment>
<Segment StartTime="397.560" EndTime="399.426" Participant="me013">
Uh, O_K, yeah. So the only -
</Segment>
<Segment StartTime="399.850" EndTime="405.014" Participant="me013">
<Emphasis> That </Emphasis> might work too. Yeah, I was just thinking that actually <Emphasis> temporally </Emphasis> just, uh, uh, uh, an increasing tones so that
</Segment>
<Segment StartTime="402.910" EndTime="403.622" Participant="me011">
Oh, O_K.
</Segment>
<Segment StartTime="405.014" EndTime="409.235" Participant="me013">
they would really have a sense of whether they were going, you know, forward or backward or - Yeah.
</Segment>
<Segment StartTime="405.075" EndTime="406.323" Participant="me011">
Bo-eep <Comment Description="nonword, imitating &quot;beep&quot; with rising tone"/> be-oop. <Comment Description="nonword, imitating &quot;beep&quot; with falling tone"/>
</Segment>
<Segment StartTime="405.638" EndTime="407.337" Participant="mn014">
In the end? Yeah.
</Segment>
<Segment StartTime="407.054" EndTime="408.160" Participant="fe008">
Well <Uncertain> you th- </Uncertain>
</Segment>
<Segment StartTime="408.410" EndTime="412.460" Participant="fe008">
So just r- r- truly chron- chromatically up <Pause/> all the way through the entire meeting.
</Segment>
<Segment StartTime="410.630" EndTime="411.163" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="412.366" EndTime="413.509" Participant="me013">
Well, it's a thought.
</Segment>
<Segment StartTime="412.690" EndTime="413.570" Participant="fe008">
Interesting.
</Segment>
<Segment StartTime="413.590" EndTime="415.109" Participant="me011">
Oh, oh, th- oh, I see.
</Segment>
<Segment StartTime="414.180" EndTime="416.045" Participant="fe008">
It'd be impossible to r- to misorder them.
</Segment>
<Segment StartTime="416.045" EndTime="416.738" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="416.120" EndTime="416.700" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="416.700" EndTime="419.683" Participant="fe016">
But yo- I guess you'd still get the mistake that <Emphasis> you </Emphasis> mentioned, because
</Segment>
<Segment StartTime="420.233" EndTime="425.388" Participant="fe016">
the person - I mean, if that's some of the errors, those would probably stay the same, regardless.
</Segment>
<Segment StartTime="420.320" EndTime="420.714" Participant="me011">
Well -
</Segment>
<Segment StartTime="421.700" EndTime="422.103" Participant="me011">
Yep.
</Segment>
<Segment StartTime="425.144" EndTime="432.561" Participant="me011">
I mean, <Emphasis> Chuck's </Emphasis> suggestion of just <Emphasis> two </Emphasis> beeps is nice because then you could have them actually <Emphasis> transcribe </Emphasis> "H_beep" or "L_beep", "high beep" or "low beep".
</Segment>
<Segment StartTime="425.216" EndTime="426.229" Participant="me013">
Yeah, maybe.
</Segment>
<Segment StartTime="432.660" EndTime="435.152" Participant="me018">
And then when we get <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> back, if we see two L_beeps in a row -
</Segment>
<Segment StartTime="433.651" EndTime="434.895" Participant="me011">
It would be much easier.
</Segment>
<Segment StartTime="434.410" EndTime="436.803" Participant="me013">
That's probably better, yeah. S- scratch my other idea.
</Segment>
<Segment StartTime="435.190" EndTime="440.120" Participant="fe016">
Yeah, you have like a sanity - sanity check on them. That's a good idea. Alternating.
</Segment>
<Segment StartTime="435.980" EndTime="437.930" Participant="fe008">
It's pretty simple, pretty simple.
</Segment>
<Segment StartTime="436.803" EndTime="437.961" Participant="me013">
<VocalSound Description="laugh-breath"/>
</Segment>
<Segment StartTime="437.961" EndTime="438.457" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="438.026" EndTime="438.504" Participant="me011">
Yep.
</Segment>
<Segment StartTime="440.194" EndTime="440.693" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="440.640" EndTime="442.824" Participant="me018">
And it would - it seems like it would help <Emphasis> them, </Emphasis> you know, if they
</Segment>
<Segment StartTime="443.290" EndTime="445.361" Participant="me018">
just finished a long passage and they heard
</Segment>
<Segment StartTime="445.361" EndTime="446.365" Participant="me018">
<Emphasis> one </Emphasis> beep and then they
</Segment>
<Segment StartTime="446.765" EndTime="448.499" Participant="me018">
hear it again, they know it's the same <Emphasis> beep. </Emphasis>
</Segment>
<Segment StartTime="448.793" EndTime="451.970" Participant="me018">
Versus if they heard a slightly different one. <Comment Description="decreasing volume"/>
</Segment>
<Segment StartTime="449.770" EndTime="450.256" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="450.849" EndTime="452.010" Participant="fe008">
Hmm, interesting.
</Segment>
<Segment StartTime="451.360" EndTime="453.440" Participant="fe016">
Yeah, that's a good, like, error checking
</Segment>
<Segment StartTime="453.878" EndTime="454.990" Participant="fe016">
approach, I think.
</Segment>
<Segment StartTime="454.185" EndTime="455.103" Participant="me011">
Yeah, we can,
</Segment>
<Segment StartTime="455.103" EndTime="456.674" Participant="me011">
yeah, like, do - do, uh,
</Segment>
<Segment StartTime="457.500" EndTime="465.850" Participant="me011">
one for each ca- one for each person in the meeting, you can only hire people who have perfect pitch, and they can say "A_flat" <VocalSound Description="laugh"/> "B_". <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="461.765" EndTime="465.586" Participant="me013">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="461.790" EndTime="467.053" Participant="me018">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="461.800" EndTime="467.170" Participant="fe008">
Well. <VocalSound Description="laugh"/> Well, "high", "low" is pretty straightforward, yeah.
</Segment>
<Segment StartTime="464.099" EndTime="466.475" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="464.690" EndTime="466.854" Participant="fe016">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="465.586" EndTime="467.050" Participant="me013">
Great idea, yeah.
</Segment>
<Segment StartTime="468.150" EndTime="473.460" Participant="me013">
No, two is probably better than what I was suggesting, because what I was suggesting, in order to make it through a reasonable range for the whole
</Segment>
<Segment StartTime="473.890" EndTime="475.172" Participant="me013">
thing, you'd have to have the -
</Segment>
<Segment StartTime="475.769" EndTime="479.672" Participant="me013">
the tonal differences between the two kind of small, and actually you want them large. So.
</Segment>
<Segment StartTime="478.032" EndTime="479.821" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="478.046" EndTime="478.569" Participant="me011">
Yep.
</Segment>
<Segment StartTime="479.821" EndTime="485.265" Participant="fe008">
You'd have to - they'd have to have the acoustics of dogs t- <VocalSound Description="laugh"/> hear into the high high ranges.
</Segment>
<Segment StartTime="482.149" EndTime="483.548" Participant="fe016">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="482.528" EndTime="483.060" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="482.647" EndTime="485.717" Participant="me013">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="485.265" EndTime="486.674" Participant="fe008">
<VocalSound Description="laugh"/> Yeah.
</Segment>
<Segment StartTime="485.717" EndTime="486.125" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="485.800" EndTime="491.328" Participant="me011">
So I think, <Emphasis> certainly, </Emphasis> doing two beeps is - is no-brainer. And then the other question is, <Emphasis> if </Emphasis> they can -
</Segment>
<Segment StartTime="486.674" EndTime="487.965" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="492.474" EndTime="493.287" Participant="me011">
If they
</Segment>
<Segment StartTime="494.060" EndTime="500.653" Participant="me011">
<Emphasis> do </Emphasis> something on a computer in a format we can <Emphasis> handle, </Emphasis> we could give them a text file that was a template with speaker I_D and beeps already in it.
</Segment>
<Segment StartTime="494.715" EndTime="496.242" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="501.056" EndTime="501.595" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="501.070" EndTime="502.522" Participant="me011">
And then they could just fill that in.
</Segment>
<Segment StartTime="502.200" EndTime="508.355" Participant="me018">
Maybe I should write to Brian and tell him what the problem <Emphasis> was </Emphasis> and what our proposed solutions are.
</Segment>
<Segment StartTime="502.300" EndTime="503.053" Participant="me013">
So what -
</Segment>
<Segment StartTime="504.575" EndTime="505.263" Participant="fe008">
<VocalSound Description="laugh-breath"/>
</Segment>
<Segment StartTime="505.982" EndTime="506.434" Participant="me011">
Right.
</Segment>
<Segment StartTime="508.355" EndTime="510.850" Participant="me018">
See what he thinks would work best with <Emphasis> them. </Emphasis>
</Segment>
<Segment StartTime="508.550" EndTime="509.420" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="510.580" EndTime="514.378" Participant="me013">
I mean, what's going <Emphasis> wrong </Emphasis> on the other end? What are they <Emphasis> doing? </Emphasis> What, uh -
</Segment>
<Segment StartTime="513.450" EndTime="519.448" Participant="me011">
Well, as I <Emphasis> said, </Emphasis> I think - We don't <Emphasis> actually </Emphasis> know, but I think Chuck's <Emphasis> hypothesis </Emphasis> was a <Emphasis> good </Emphasis> one, which is, you re- r- you <Emphasis> listen </Emphasis> to something,
</Segment>
<Segment StartTime="519.448" EndTime="520.989" Participant="me011">
you write down what you thought you heard,
</Segment>
<Segment StartTime="520.989" EndTime="523.019" Participant="me011">
but you want to listen to it again, so you r- rewind.
</Segment>
<Segment StartTime="523.370" EndTime="524.098" Participant="me018">
And there are some -
</Segment>
<Segment StartTime="523.510" EndTime="526.750" Participant="me011">
And then you hear the beep <Comment Description="lengthened"/> again, and then you say "well, is that <Emphasis> that </Emphasis> beep,
</Segment>
<Segment StartTime="526.750" EndTime="530.500" Participant="me011">
or is that a new beep? <Emphasis> I </Emphasis> don't remember." And so, you know, a <Emphasis> couple </Emphasis> times they got it <Emphasis> wrong. </Emphasis>
</Segment>
<Segment StartTime="530.500" EndTime="532.868" Participant="me018">
And there are <Emphasis> some </Emphasis> cases where there's, um,
</Segment>
<Segment StartTime="532.868" EndTime="537.374" Participant="me018">
very little <Emphasis> speech </Emphasis> before you hear a beep. So you hear a little bit of speech, beep, a little bit of speech, beep.
</Segment>
<Segment StartTime="534.919" EndTime="536.060" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="535.166" EndTime="535.803" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="537.374" EndTime="540.959" Participant="me018">
Maybe three of those in a <Emphasis> row, </Emphasis> and was that <Emphasis> three </Emphasis> beeps, was that <Emphasis> two </Emphasis> beeps? <Pause/>
</Segment>
<Segment StartTime="541.430" EndTime="545.300" Participant="me018">
Um - See, they have th- Brian said the setup that they <Emphasis> have </Emphasis> is, um -
</Segment>
<Segment StartTime="545.300" EndTime="545.987" Participant="me011">
<VocalSound Description="clears throat"/>
</Segment>
<Segment StartTime="545.530" EndTime="546.560" Participant="me018">
uh -
</Segment>
<Segment StartTime="546.560" EndTime="547.580" Participant="me018">
i- um -
</Segment>
<Segment StartTime="547.690" EndTime="552.141" Participant="me018">
They've got headphones and <Uncertain> then </Uncertain> I guess they have a computer, and they have a foot pedal which lets them quickly
</Segment>
<Segment StartTime="552.141" EndTime="557.625" Participant="me018">
scan back and forth through the tape. I- i- t- i- s- makes the tape go real fast forward or fast backward.
</Segment>
<Segment StartTime="557.994" EndTime="561.281" Participant="me018">
And so they can <Emphasis> hear </Emphasis> something, then step on the pedal and quickly rewind
</Segment>
<Segment StartTime="561.800" EndTime="564.140" Participant="me018">
and go back and hear it <Emphasis> again. </Emphasis> And so they're -
</Segment>
<Segment StartTime="564.140" EndTime="568.621" Participant="me018">
I <Emphasis> think </Emphasis> they're probably going over and <Emphasis> over </Emphasis> f- sections. And then they get <Emphasis> confused </Emphasis> about whether
</Segment>
<Segment StartTime="569.150" EndTime="574.114" Participant="me018">
they've already <NonVocalSound Description="mike noise"/> put that beep, or if they heard, you know, three beeps in a row, was that <Emphasis> three </Emphasis> or <Emphasis> two, </Emphasis> and - <Comment Description="abandoned as clear"/>
</Segment>
<Segment StartTime="575.175" EndTime="692.739" CloseMic="false">
<Comment Description="close collaboration in development of number plus beep to help I_B_M transcribers keep their places in linearized meeting data"/>
</Segment>
<Segment StartTime="575.199" EndTime="579.820" Participant="fe008">
It's a <Emphasis> shame </Emphasis> we can't <Emphasis> really </Emphasis> give a <Emphasis> number. </Emphasis> So it would be a <Emphasis> number </Emphasis> <Emphasis> and </Emphasis> a <Emphasis> beep. </Emphasis>
</Segment>
<Segment StartTime="575.443" EndTime="576.047" Participant="me013">
O_K, s-
</Segment>
<Segment StartTime="579.820" EndTime="580.690" Participant="fe008">
e-
</Segment>
<Segment StartTime="580.690" EndTime="582.140" Participant="fe008">
It's a shame we can't do that.
</Segment>
<Segment StartTime="582.380" EndTime="583.674" Participant="me011">
Well, we <Emphasis> could. </Emphasis> <Comment Description="&quot;could&quot; is lengthened, as if pondering"/>
</Segment>
<Segment StartTime="582.470" EndTime="584.297" Participant="me018">
<Emphasis> Oh, </Emphasis> <Emphasis> that's </Emphasis> an interesting idea.
</Segment>
<Segment StartTime="584.266" EndTime="586.365" Participant="me011">
We <Emphasis> could, </Emphasis> but then that starts getting
</Segment>
<Segment StartTime="587.390" EndTime="588.438" Participant="me011">
pretty <Emphasis> long. </Emphasis>
</Segment>
<Segment StartTime="588.229" EndTime="590.550" Participant="me018">
No, no, no. But <Emphasis> wait, </Emphasis> maybe -
</Segment>
<Segment StartTime="590.570" EndTime="595.265" Participant="me018">
maybe what we <Emphasis> have </Emphasis> instead of a <Emphasis> beep </Emphasis> is a, uh, synthesized <Emphasis> number. </Emphasis>
</Segment>
<Segment StartTime="594.901" EndTime="595.574" Participant="mn014">
Yep.
</Segment>
<Segment StartTime="595.960" EndTime="597.809" Participant="me018">
And they put the <Emphasis> number </Emphasis> in when they hear it.
</Segment>
<Segment StartTime="596.924" EndTime="598.074" Participant="fe008">
<Emphasis> That'll </Emphasis> work. <Comment Description="quietly"/>
</Segment>
<Segment StartTime="598.350" EndTime="601.365" Participant="me018">
So, inst- <Pronounce> replacing </Pronounce> the beep with "twenty-<Emphasis> three </Emphasis>",
</Segment>
<Segment StartTime="601.684" EndTime="602.636" Participant="me018">
"twenty-<Emphasis> four </Emphasis>",
</Segment>
<Segment StartTime="602.860" EndTime="605.920" Participant="me018">
"twenty-five" - <Comment Description="abandoned as clear"/> And then they have to transcribe what that <Emphasis> number </Emphasis> is each time.
</Segment>
<Segment StartTime="605.920" EndTime="607.810" Participant="fe008">
Wow, that'd <Emphasis> also </Emphasis> be shorter to <Emphasis> type. </Emphasis>
</Segment>
<Segment StartTime="608.420" EndTime="610.710" Participant="me018">
Yeah, just a "two three, two four", that would be -
</Segment>
<Segment StartTime="609.990" EndTime="611.650" Participant="me011">
Well, they would have to have a mark.
</Segment>
<Segment StartTime="611.339" EndTime="612.680" Participant="fe008">
<Emphasis> Interesting. </Emphasis>
</Segment>
<Segment StartTime="611.415" EndTime="613.162" Participant="me018">
There'd be some kind of mark in front of it.
</Segment>
<Segment StartTime="613.980" EndTime="616.264" Participant="me013">
Well, cuz they're s- distinguishing between twenty-three -
</Segment>
<Segment StartTime="616.790" EndTime="621.784" Participant="me013">
that's your <Emphasis> indicator </Emphasis> there, and twenty-three that somebody happens to <Emphasis> say </Emphasis> in a <Emphasis> meeting. </Emphasis>
</Segment>
<Segment StartTime="619.800" EndTime="621.170" Participant="fe008">
Oh, that's true.
</Segment>
<Segment StartTime="620.010" EndTime="622.530" Participant="me018">
Well it would have t- yeah, it would have to be um,
</Segment>
<Segment StartTime="622.990" EndTime="627.950" Participant="me018">
you know either obviously a s- sounding synthesized, uh, little -
</Segment>
<Segment StartTime="623.750" EndTime="624.518" Participant="mn014">
Yeah. <Comment Description="creaky voice, lengthened"/>
</Segment>
<Segment StartTime="627.182" EndTime="628.480" Participant="me013">
But they might miss that, right?
</Segment>
<Segment StartTime="628.480" EndTime="630.870" Participant="fe008">
Or maybe could it be a <Emphasis> click </Emphasis> and the <Emphasis> number. </Emphasis>
</Segment>
<Segment StartTime="628.607" EndTime="629.590" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="630.940" EndTime="632.260" Participant="me018">
Or a <Emphasis> beep </Emphasis> and the number.
</Segment>
<Segment StartTime="632.260" EndTime="633.744" Participant="me011">
Well, it's sequential.
</Segment>
<Segment StartTime="632.380" EndTime="636.141" Participant="fe008">
Or a beep and the number, and then - and then you just do the - the num- th- you do it as a d- a digit.
</Segment>
<Segment StartTime="634.520" EndTime="637.660" Participant="me011">
Right, you would go sequential. So unless you got pretty unlucky,
</Segment>
<Segment StartTime="635.317" EndTime="636.393" Participant="me018">
Uh, right.
</Segment>
<Segment StartTime="637.454" EndTime="638.591" Participant="mn014">
<Uncertain> Yeah. </Uncertain>
</Segment>
<Segment StartTime="638.996" EndTime="641.015" Participant="me011">
what the person was saying and the number -
</Segment>
<Segment StartTime="641.751" EndTime="645.630" Participant="me018">
<VocalSound Description="inbreath"/> In <Emphasis> fact, </Emphasis> we could put it at the <Emphasis> beginning </Emphasis> of each utterance. We could say "beep
</Segment>
<Segment StartTime="645.760" EndTime="646.435" Participant="me018">
<Emphasis> one </Emphasis>".
</Segment>
<Segment StartTime="646.665" EndTime="648.030" Participant="me018">
And then they'll hear the speech.
</Segment>
<Segment StartTime="647.730" EndTime="649.350" Participant="me013">
I think having a beep too is good.
</Segment>
<Segment StartTime="650.440" EndTime="655.340" Participant="me011">
So beep number. Yeah the- It's just getting pretty <Emphasis> long. </Emphasis> You know, the utterances are very <Emphasis> short. </Emphasis>
</Segment>
<Segment StartTime="651.500" EndTime="652.970" Participant="me018">
Or a number beep -
</Segment>
<Segment StartTime="653.411" EndTime="654.254" Participant="mn014">
Yep.
</Segment>
<Segment StartTime="655.204" EndTime="655.913" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="655.873" EndTime="661.583" Participant="me011">
And so you're gonna be talking beep, number, "yes!" beep, number, "no". <Comment Description="last five words while laughing"/> <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="658.720" EndTime="660.855" Participant="me013">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="659.029" EndTime="661.911" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="659.968" EndTime="660.713" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="660.500" EndTime="662.924" Participant="fe008">
Well, if - if it saves time, yeah.
</Segment>
<Segment StartTime="662.125" EndTime="665.610" Participant="me018">
<Emphasis> Yeah, </Emphasis> and u- I think it would - I - <Emphasis> Actually, </Emphasis> I thi- I <Emphasis> like </Emphasis> that. I think it would -
</Segment>
<Segment StartTime="663.270" EndTime="664.413" Participant="me011">
<VocalSound Description="coughs twice"/>
</Segment>
<Segment StartTime="664.413" EndTime="668.976" Participant="me011">
And when they transcribe <Emphasis> this </Emphasis> meeting it's gonna be <Emphasis> really </Emphasis> <Emphasis> impossible. </Emphasis> <Comment Description="last four words while laughing"/>
</Segment>
<Segment StartTime="665.820" EndTime="672.120" Participant="mn014">
Yeah, <Comment Description="while laughing"/> that's funny. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="666.577" EndTime="668.724" Participant="me018">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="666.770" EndTime="668.176" Participant="me013">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="667.050" EndTime="672.576" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="668.176" EndTime="671.460" Participant="me013">
W- we're <Emphasis> saying </Emphasis> "beep". Yeah - <Comment Description="while laughing"/> for instance.
</Segment>
<Segment StartTime="669.084" EndTime="669.997" Participant="me011">
Yeah, yep.
</Segment>
<Segment StartTime="669.136" EndTime="670.532" Participant="fe016">
<VocalSound Description="breath-laugh"/>
</Segment>
<Segment StartTime="670.000" EndTime="671.009" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="671.009" EndTime="673.738" Participant="me018">
But see that would - that would <Emphasis> definitely </Emphasis> keep -
</Segment>
<Segment StartTime="673.030" EndTime="673.947" Participant="me011">
It's not a bad idea.
</Segment>
<Segment StartTime="673.738" EndTime="675.150" Participant="me018">
Yeah. Keep
</Segment>
<Segment StartTime="675.150" EndTime="680.740" Participant="me018">
things from getting out of <Emphasis> sequence. </Emphasis> If they <Emphasis> heard </Emphasis> it <Emphasis> over </Emphasis> again they would <Emphasis> know. </Emphasis> It would be <Emphasis> obvious </Emphasis> from their <Emphasis> transcript </Emphasis> whether they <Emphasis> did </Emphasis> that one or not.
</Segment>
<Segment StartTime="680.280" EndTime="683.320" Participant="fe008">
It might actually <Emphasis> help </Emphasis> <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> in terms of their <Emphasis> place </Emphasis> holding. Yeah.
</Segment>
<Segment StartTime="680.740" EndTime="682.548" Participant="me011">
That <Emphasis> would </Emphasis> help get them synchronized.
</Segment>
<Segment StartTime="682.800" EndTime="683.320" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="683.320" EndTime="685.530" Participant="fe008">
And it might be helpful to <Emphasis> them </Emphasis> in terms of d- act-
</Segment>
<Segment StartTime="684.740" EndTime="687.564" Participant="me011">
I think it <Emphasis> would </Emphasis> be, because they would know their <Emphasis> place. </Emphasis> Yeah.
</Segment>
<Segment StartTime="685.600" EndTime="687.339" Participant="me018">
And we have plenty of <Emphasis> digits </Emphasis> data, so.
</Segment>
<Segment StartTime="687.339" EndTime="688.205" Participant="me018">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="687.910" EndTime="689.950" Participant="me011">
They would know their place, darn it! <Comment Description="last three words while laughing"/> <Comment Description="humor, play on words"/>
</Segment>
<Segment StartTime="688.205" EndTime="688.682" Participant="me018">
We- <Comment Description="while laughing"/>
</Segment>
<Segment StartTime="688.770" EndTime="689.755" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="689.128" EndTime="694.150" Participant="me018">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="689.755" EndTime="690.075" Participant="fe008">
Know - <Comment Description="while laughing"/>
</Segment>
<Segment StartTime="690.075" EndTime="692.469" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="691.002" EndTime="693.207" Participant="me011">
Those transcriptionists need to know their place.
</Segment>
<Segment StartTime="691.068" EndTime="691.834" Participant="mn014">
<Uncertain> Oh. </Uncertain>
</Segment>
<Segment StartTime="692.469" EndTime="695.691" Participant="fe008">
Well, <Emphasis> no </Emphasis> no no no. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="693.065" EndTime="699.689" Participant="me013">
But it sounds like a k- a - a - a short conversation with Brian might be - might be helpful to get a sense of what's going on.
</Segment>
<Segment StartTime="693.789" EndTime="694.757" Participant="me011">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="696.377" EndTime="698.380" Participant="me018">
Yeah. I'll - I'll - I'll write him an -
</Segment>
<Segment StartTime="698.380" EndTime="699.526" Participant="me011">
Yeah, the <Emphasis> numbers </Emphasis> are a good idea.
</Segment>
<Segment StartTime="699.498" EndTime="700.220" Participant="fe008">
O_K.
</Segment>
<Segment StartTime="699.650" EndTime="700.340" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="699.890" EndTime="700.691" Participant="mn014">
Or just -
</Segment>
<Segment StartTime="699.910" EndTime="702.327" Participant="me011">
Othe- other than <Emphasis> lengthening </Emphasis> the <Emphasis> transcript, </Emphasis>
</Segment>
<Segment StartTime="702.680" EndTime="704.025" Participant="me011">
I think it would be very helpful.
</Segment>
<Segment StartTime="704.760" EndTime="707.048" Participant="mn014">
Just instead of the sequential number, for-
</Segment>
<Segment StartTime="707.048" EndTime="713.104" Participant="mn014">
perhaps just the speaker I_D <Comment Description="rising intonation"/> or something. Just say speaker one <Comment Description="rising intonation"/> or spea- or just one, two, three, four <Comment Description="rising intonation"/> for four speakers or something. <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="713.104" EndTime="713.390" Participant="mn014">
Pppt! <Comment Description="vocal gesture, possibly meaning &quot;what the heck, give it a try&quot;"/>
</Segment>
<Segment StartTime="713.270" EndTime="714.830" Participant="fe008">
<VocalSound Description="inbreath"/> I - i-
</Segment>
<Segment StartTime="713.390" EndTime="714.770" Participant="mn014">
Could - could be helpful.
</Segment>
<Segment StartTime="714.770" EndTime="715.737" Participant="me011">
Yeah, you don't have to -
</Segment>
<Segment StartTime="716.055" EndTime="721.021" Participant="me011">
you <Emphasis> could </Emphasis> keep <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> short by not s- or just go one through ten, one through ten, one through ten, or one through twenty.
</Segment>
<Segment StartTime="716.999" EndTime="717.385" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="717.776" EndTime="718.211" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="718.676" EndTime="719.160" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="719.691" EndTime="720.146" Participant="mn014">
Yep.
</Segment>
<Segment StartTime="721.858" EndTime="727.720" Participant="fe008">
And then <Emphasis> also, </Emphasis> if we - I mean, I don't know what their <Emphasis> setup </Emphasis> is, but your <Emphasis> template </Emphasis> idea might be a way of - of
</Segment>
<Segment StartTime="727.140" EndTime="727.668" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="727.720" EndTime="730.290" Participant="fe008">
of - We could actually <Emphasis> build </Emphasis> the numbers <Emphasis> into </Emphasis> a template.
</Segment>
<Segment StartTime="729.885" EndTime="730.332" Participant="me011">
Yep.
</Segment>
<Segment StartTime="732.048" EndTime="732.547" Participant="fe008">
<Uncertain> Well. </Uncertain> <Comment Description="very quietly"/>
</Segment>
<Segment StartTime="732.937" EndTime="735.290" Participant="me018">
I'll talk to Brian, and see what he -
</Segment>
<Segment StartTime="734.920" EndTime="736.087" Participant="me011">
Yeah, <Emphasis> single </Emphasis> digit numbers -
</Segment>
<Segment StartTime="736.501" EndTime="736.924" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="736.550" EndTime="738.956" Participant="me011">
That also appeals to me. So that you don't have to, you know -
</Segment>
<Segment StartTime="736.900" EndTime="738.020" Participant="fe008">
That's a good idea.
</Segment>
<Segment StartTime="738.310" EndTime="739.260" Participant="fe008">
Very simple.
</Segment>
<Segment StartTime="739.830" EndTime="741.380" Participant="me011">
"One hundred twenty-four" <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="740.547" EndTime="743.480" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="741.650" EndTime="742.330" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="741.750" EndTime="743.967" Participant="mn014">
Yeah. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="742.330" EndTime="743.120" Participant="me013">
Well, th- although -
</Segment>
<Segment StartTime="742.681" EndTime="744.873" Participant="me011">
"Beep. One thousand three hundred forty-two"
</Segment>
<Segment StartTime="743.880" EndTime="746.716" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="744.430" EndTime="745.380" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="745.731" EndTime="749.636" Participant="me013">
You're saying i- it's - it's about an hour meeting, and there were a hundred and twenty-three -
</Segment>
<Segment StartTime="747.728" EndTime="748.205" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="748.850" EndTime="749.551" Participant="me011">
I don't remember.
</Segment>
<Segment StartTime="749.830" EndTime="751.080" Participant="fe008">
It's forty-five minutes.
</Segment>
<Segment StartTime="749.980" EndTime="751.560" Participant="me011">
Chuck was saying there was more than that.
</Segment>
<Segment StartTime="751.294" EndTime="751.742" Participant="me013">
Hmm?
</Segment>
<Segment StartTime="751.830" EndTime="753.349" Participant="fe008">
Forty-five minutes for <Emphasis> that </Emphasis> one. <Comment Description="in response to [me013]'s &quot;Hmm?&quot;, thinking it was intended for [fe008] herself"/>
</Segment>
<Segment StartTime="751.882" EndTime="753.365" CloseMic="false">
<Comment Description="[me013] asked &quot;Hmm?&quot; and both [me011] and [fe008] respond, but on totally different topics"/>
</Segment>
<Segment StartTime="751.940" EndTime="752.877" Participant="me011">
<Emphasis> More </Emphasis> beeps than that. <Comment Description="in response to [me013]'s &quot;Hmm?&quot;, thinking it was intended for [me011] himself"/>
</Segment>
<Segment StartTime="753.040" EndTime="754.860" Participant="me018">
<Emphasis> I </Emphasis> was thinking there was on the order of
</Segment>
<Segment StartTime="755.232" EndTime="757.130" Participant="me018">
fifteen <Emphasis> hundred </Emphasis> segments, but maybe I'm -
</Segment>
<Segment StartTime="757.490" EndTime="760.135" Participant="fe016">
There <Emphasis> must </Emphasis> be. Because <Emphasis> otherwise, </Emphasis> you're going a whole -
</Segment>
<Segment StartTime="758.518" EndTime="760.400" Participant="mn014">
I think it should be more, yeah.
</Segment>
<Segment StartTime="759.050" EndTime="759.788" Participant="fe008">
<Uncertain> It's </Uncertain> possible.
</Segment>
<Segment StartTime="760.632" EndTime="761.346" Participant="fe016">
That was
</Segment>
<Segment StartTime="761.346" EndTime="763.128" Participant="fe016">
at least forty-five minutes, right?
</Segment>
<Segment StartTime="762.603" EndTime="763.535" Participant="fe008">
Yeah. That's right.
</Segment>
<Segment StartTime="763.540" EndTime="765.017" Participant="me011">
Was it that many? I just don't recall.
</Segment>
<Segment StartTime="764.100" EndTime="765.417" Participant="fe008">
Yeah, it was forty-five minutes.
</Segment>
<Segment StartTime="764.640" EndTime="767.647" Participant="fe016">
That's the shortest meeting we <Emphasis> have. </Emphasis> Most of them are <Emphasis> double </Emphasis> that, or
</Segment>
<Segment StartTime="767.411" EndTime="767.924" Participant="me011">
Yep.
</Segment>
<Segment StartTime="769.330" EndTime="771.100" Participant="me013">
Well, I was just wondering what the average length
</Segment>
<Segment StartTime="769.452" EndTime="770.537" Participant="fe016">
<Uncertain> so </Uncertain>
</Segment>
<Segment StartTime="771.580" EndTime="773.853" Participant="me018">
Oh, of a - of a segment that they're hearing?
</Segment>
<Segment StartTime="771.873" EndTime="772.586" Participant="me013">
<Emphasis> thing </Emphasis> was.
</Segment>
<Segment StartTime="771.910" EndTime="772.382" Participant="mn014">
It's -
</Segment>
<Segment StartTime="774.030" EndTime="774.474" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="774.213" EndTime="775.400" Participant="me018">
I don't know.
</Segment>
<Segment StartTime="774.483" EndTime="776.033" Participant="mn014">
<VocalSound Description="brief vocalized outbreath"/> <NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="774.849" EndTime="776.223" Participant="fe008">
Hmm, interesting.
</Segment>
<Segment StartTime="775.907" EndTime="776.828" Participant="me018">
I don't know.
</Segment>
<Segment StartTime="775.991" EndTime="776.431" Participant="me013">
Uh-
</Segment>
<Segment StartTime="776.001" EndTime="778.463" Participant="me011">
Easy enough to figure out. We have all that data.
</Segment>
<Segment StartTime="776.828" EndTime="777.617" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="777.020" EndTime="778.358" Participant="fe016">
So if there <Emphasis> are </Emphasis> in the -
</Segment>
<Segment StartTime="778.358" EndTime="781.229" Participant="fe016">
in the <Emphasis> hundreds </Emphasis> and thou- or <Emphasis> thousands </Emphasis> of these -
</Segment>
<Segment StartTime="782.744" EndTime="785.644" Participant="fe016">
It <Emphasis> must </Emphasis> be in the high <Emphasis> hundreds </Emphasis> of them, at <Emphasis> least. </Emphasis>
</Segment>
<Segment StartTime="785.090" EndTime="786.599" Participant="me013">
So, right. So i-
</Segment>
<Segment StartTime="786.240" EndTime="789.090" Participant="fe016">
So that's getting a little cumbersome for them to type, like,
</Segment>
<Segment StartTime="788.200" EndTime="788.870" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="788.826" EndTime="790.450" Participant="fe008">
<Emphasis> Well, </Emphasis> with <Emphasis> just </Emphasis> one <Emphasis> digit </Emphasis> though,
</Segment>
<Segment StartTime="789.380" EndTime="790.329" Participant="fe016">
five hundred? <Comment Description="quickly decreasing volume"/>
</Segment>
<Segment StartTime="790.450" EndTime="791.242" Participant="fe008">
I think -
</Segment>
<Segment StartTime="790.810" EndTime="791.289" Participant="me013">
Well -
</Segment>
<Segment StartTime="790.840" EndTime="792.936" Participant="fe016">
But yeah, if they recycle through -
</Segment>
<Segment StartTime="792.160" EndTime="794.440" Participant="me018">
Yeah, if we - if we did mod ten, then -
</Segment>
<Segment StartTime="792.523" EndTime="793.031" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="793.900" EndTime="797.819" Participant="me013">
Right, but my <Emphasis> point </Emphasis> was, you know, if - It's a <Emphasis> big </Emphasis> difference to me if there's a <Emphasis> thousand </Emphasis> or there's a <Emphasis> hundred. </Emphasis> If
</Segment>
<Segment StartTime="794.570" EndTime="795.330" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="797.819" EndTime="799.127" Participant="me013">
there's a <Emphasis> thousand, </Emphasis> then that means
</Segment>
<Segment StartTime="799.353" EndTime="802.190" Participant="me013">
that this is only happening <Emphasis> three </Emphasis> times out of a <Emphasis> thousand. </Emphasis>
</Segment>
<Segment StartTime="802.190" EndTime="807.436" Participant="me013">
Which means, you know, even just splitting it up into a few <Emphasis> files </Emphasis> would probably take - You know, nearly all the <Emphasis> time, </Emphasis> there would be no - <Comment Description="abandoned as clear"/>
</Segment>
<Segment StartTime="806.654" EndTime="807.358" Participant="fe016">
Yeah.
</Segment>
<Segment StartTime="807.870" EndTime="811.555" Participant="me013">
W- if it's a <Emphasis> hundred, </Emphasis> then - you know, that's <Emphasis> not </Emphasis> the issue, <Comment Description="embedded"/> but if it's a hundred,
</Segment>
<Segment StartTime="811.922" EndTime="818.081" Participant="me013">
then, the average <Emphasis> length </Emphasis> of each one is pretty - pretty <Emphasis> long </Emphasis> and so having a little thing at the front of it is no big <Emphasis> deal. </Emphasis>
</Segment>
<Segment StartTime="818.057" EndTime="819.113" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="818.448" EndTime="819.832" Participant="me013">
So, <Emphasis> that's </Emphasis> why I was <Emphasis> curious. </Emphasis>
</Segment>
<Segment StartTime="818.590" EndTime="822.309" Participant="me011">
Yeah, <Emphasis> you're </Emphasis> right. It <Emphasis> had </Emphasis> to have been more than that. I mean, it was a forty-five minute meeting, so -
</Segment>
<Segment StartTime="821.780" EndTime="822.349" Participant="fe016">
Right.
</Segment>
<Segment StartTime="822.309" EndTime="825.970" Participant="me011">
And it certainly was not a minute a chunk, it was a few <Emphasis> seconds </Emphasis> a chunk.
</Segment>
<Segment StartTime="825.680" EndTime="826.321" Participant="fe016">
That's what I -
</Segment>
<Segment StartTime="826.312" EndTime="826.771" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="826.321" EndTime="828.494" Participant="fe016">
Yeah, so it'd be a lot of overhead to type.
</Segment>
<Segment StartTime="826.809" EndTime="828.079" Participant="me011">
So I'm just mis-remembering.
</Segment>
<Segment StartTime="829.290" EndTime="830.309" Participant="me011">
I'm just mis-remembering.
</Segment>
<Segment StartTime="829.680" EndTime="830.520" Participant="fe016">
Oh, I -
</Segment>
<Segment StartTime="830.673" EndTime="831.128" Participant="me011">
So.
</Segment>
<Segment StartTime="830.840" EndTime="836.073" Participant="fe008">
Well, and the <Emphasis> other </Emphasis> thing is, maybe the numbers would help them keep their place in the transcript and speed the process -
</Segment>
<Segment StartTime="831.932" EndTime="832.550" Participant="fe016">
<Uncertain> Yeah. </Uncertain> <Comment Description="very quietly"/>
</Segment>
<Segment StartTime="834.527" EndTime="839.308" Participant="me011">
It might make the transcript faster - W- wel- I mean I - A quick conversation with Brian would be good, so.
</Segment>
<Segment StartTime="835.510" EndTime="836.377" Participant="fe016">
Yeah.
</Segment>
<Segment StartTime="837.952" EndTime="838.546" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="838.480" EndTime="839.260" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="844.460" EndTime="845.066" Participant="me011">
O_K.
</Segment>
<Segment StartTime="848.740" EndTime="850.002" Participant="me011">
And other than that -
</Segment>
<Segment StartTime="849.880" EndTime="851.127" Participant="fe016">
Actually, if it <Emphasis> is </Emphasis> -
</Segment>
<Segment StartTime="852.006" EndTime="852.298" Participant="fe016">
u-
</Segment>
<Segment StartTime="852.298" EndTime="853.651" Participant="fe016">
I mean, it's not a bad
</Segment>
<Segment StartTime="854.087" EndTime="855.690" Participant="fe016">
idea to <Emphasis> try </Emphasis> the alignment.
</Segment>
<Segment StartTime="856.384" EndTime="858.075" Participant="fe016">
Um, if there's only like <Emphasis> three </Emphasis> of <Pronounce Pronunciation="&quot;em&quot;"> them, </Pronounce>
</Segment>
<Segment StartTime="858.820" EndTime="859.188" Participant="fe016">
then
</Segment>
<Segment StartTime="859.899" EndTime="864.704" Participant="fe016">
if you <Emphasis> align, </Emphasis> the first point at which things get messed up is sort of the location of the first problem.
</Segment>
<Segment StartTime="864.376" EndTime="864.890" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="865.250" EndTime="867.151" Participant="fe016">
And then, the second p- I mean,
</Segment>
<Segment StartTime="867.470" EndTime="868.743" Participant="fe016">
you could <Emphasis> do </Emphasis> it that way, or you could -
</Segment>
<Segment StartTime="869.232" EndTime="870.380" Participant="fe016">
It's - it's -
</Segment>
<Segment StartTime="870.380" EndTime="871.303" Participant="fe016">
it would be
</Segment>
<Segment StartTime="871.910" EndTime="875.477" Participant="fe016">
able to handle any errors. So if they make, on the average, that <Emphasis> many, </Emphasis>
</Segment>
<Segment StartTime="873.733" EndTime="874.259" Participant="me011">
Right.
</Segment>
<Segment StartTime="876.615" EndTime="881.420" Participant="fe016">
and it costs them more time to do something different than what they're doing, which I don't know, <Comment Description="embedded"/> but if it <Emphasis> does, </Emphasis>
</Segment>
<Segment StartTime="880.609" EndTime="888.762" Participant="me013">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="882.200" EndTime="884.813" Participant="fe016">
then we could <Emphasis> try </Emphasis> doing that as a post-process, and,
</Segment>
<Segment StartTime="885.545" EndTime="890.400" Participant="fe016">
um, have a student or a transcriber run this alignment, or we can do it and -
</Segment>
<Segment StartTime="888.904" EndTime="889.422" Participant="me011">
Yep.
</Segment>
<Segment StartTime="889.490" EndTime="891.910" Participant="me018">
You know <Emphasis> actually, </Emphasis> what - all that we would -
</Segment>
<Segment StartTime="891.050" EndTime="892.543" Participant="fe016">
then you can iteratively
</Segment>
<Segment StartTime="893.257" EndTime="894.923" Participant="fe016">
figure out <Comment Description="while laughing"/> where the problems are.
</Segment>
<Segment StartTime="894.883" EndTime="896.335" Participant="me018">
You know, Liz, all we would re-
</Segment>
<Segment StartTime="895.410" EndTime="899.310" Participant="fe016">
It would take a <Emphasis> little </Emphasis> work, but not any real human - not a lot of human work.
</Segment>
<Segment StartTime="898.110" EndTime="899.827" Participant="me011">
Right. I mean, <Emphasis> that's </Emphasis> what we want to avoid.
</Segment>
<Segment StartTime="898.810" EndTime="905.327" Participant="me018">
I mean if - in terms of the alignment, actually, all we would need is - we wouldn't even need <Emphasis> words. </Emphasis> We would need a <Emphasis> general </Emphasis> speech model and a <Emphasis> beep </Emphasis> model.
</Segment>
<Segment StartTime="903.870" EndTime="907.927" Participant="me013">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="905.327" EndTime="908.977" Participant="me018">
Cuz all we're really <Emphasis> concerned </Emphasis> about is missing beeps or too <Emphasis> many </Emphasis> beeps.
</Segment>
<Segment StartTime="909.750" EndTime="914.148" Participant="fe016">
Well, the for- the <Emphasis> forced </Emphasis> alignment will run fa- otherwise it'll take forever. I mean,
</Segment>
<Segment StartTime="909.820" EndTime="910.729" Participant="me018">
So if we had a -
</Segment>
<Segment StartTime="913.500" EndTime="914.136" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="914.148" EndTime="915.964" Participant="fe016">
to really run recognition? <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="914.450" EndTime="917.637" Participant="me018">
Well - l- I guess what I'm <Emphasis> thinking </Emphasis> of is that w-
</Segment>
<Segment StartTime="915.964" EndTime="916.413" Participant="fe016">
Or - ? <Comment Description="leading question"/>
</Segment>
<Segment StartTime="917.637" EndTime="918.821" Participant="me018">
that a lot of times
</Segment>
<Segment StartTime="919.010" EndTime="921.621" Participant="me018">
there will be - they'll put in question marks,
</Segment>
<Segment StartTime="921.621" EndTime="925.940" Participant="me018">
that represent some unknown amount of speech, so we're gonna have to have some kind of -
</Segment>
<Segment StartTime="922.260" EndTime="923.118" Participant="fe016">
Right.
</Segment>
<Segment StartTime="925.490" EndTime="927.544" Participant="fe016">
Yeah, then we just map it to a <Emphasis> reject </Emphasis> model.
</Segment>
<Segment StartTime="928.040" EndTime="933.445" Participant="fe016">
In - and in fact, that's what we do <Emphasis> now. </Emphasis> Cuz there's cases, even after <Emphasis> Jane </Emphasis> listens, where, you know, we have -
</Segment>
<Segment StartTime="930.181" EndTime="930.615" Participant="me018">
Right, h-
</Segment>
<Segment StartTime="933.445" EndTime="935.991" Participant="fe016">
an <Emphasis> expert </Emphasis> can't even tell what they're talking about.
</Segment>
<Segment StartTime="935.660" EndTime="936.380" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="935.991" EndTime="939.796" Participant="fe016">
Um, so that's O_K. Just map that to reject and -
</Segment>
<Segment StartTime="936.931" EndTime="941.470" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="937.400" EndTime="937.891" Participant="me018">
Right.
</Segment>
<Segment StartTime="937.891" EndTime="942.850" Participant="me018">
Well, what I was <Emphasis> thinking </Emphasis> is, map <Emphasis> all </Emphasis> the speech to the <Emphasis> reject </Emphasis> model. And then you have a <Emphasis> beep </Emphasis> model.
</Segment>
<Segment StartTime="941.470" EndTime="942.617" Participant="fe008">
<VocalSound Description="breath"/>
</Segment>
<Segment StartTime="941.605" EndTime="942.132" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="942.695" EndTime="944.603" Participant="me011">
But that won't <Emphasis> work </Emphasis> because it's -
</Segment>
<Segment StartTime="943.020" EndTime="944.605" Participant="me013">
Yeah, you're still talking a forced al-
</Segment>
<Segment StartTime="944.469" EndTime="948.030" Participant="fe016">
The forced alignment might not work then, <Comment Description="rising intonation"/> although we can <Emphasis> try </Emphasis> it.
</Segment>
<Segment StartTime="948.340" EndTime="948.900" Participant="fe016">
Um -
</Segment>
<Segment StartTime="948.900" EndTime="950.141" Participant="me011">
Well, but, all we'll get -
</Segment>
<Segment StartTime="949.370" EndTime="953.627" Participant="me013">
Well, with the beep models, is what's really - you'd have really g- it would be really good though. So -
</Segment>
<Segment StartTime="951.599" EndTime="954.668" Participant="me018">
The beep model is - is gonna match, like, <Emphasis> really </Emphasis> well.
</Segment>
<Segment StartTime="952.530" EndTime="953.509" Participant="fe016">
Right.
</Segment>
<Segment StartTime="953.627" EndTime="957.271" Participant="me013">
so it's p- so it's really just doing, yeah, a keyword, like a spotting for beep with -
</Segment>
<Segment StartTime="955.950" EndTime="960.631" Participant="fe016">
Right. But it'll - it'll grab the next beep, in other words. It'll be -
</Segment>
<Segment StartTime="960.631" EndTime="962.336" Participant="fe016">
You'll get back another offset.
</Segment>
<Segment StartTime="963.010" EndTime="965.813" Participant="fe016">
Um - I mean, I was <Emphasis> thinking </Emphasis> of - then I - and then I realized "Well,
</Segment>
<Segment StartTime="965.813" EndTime="968.403" Participant="fe016">
the recognizer will just go along and line up all the beeps,
</Segment>
<Segment StartTime="968.403" EndTime="972.200" Participant="fe016">
and then there'll be all the extra beeps at the end <Pause/> if there were more beeps then you
</Segment>
<Segment StartTime="972.270" EndTime="972.911" Participant="fe016">
wanted."
</Segment>
<Segment StartTime="972.290" EndTime="974.268" Participant="me011">
Right, you - you <Emphasis> need </Emphasis> - But you <Emphasis> need </Emphasis> the <Emphasis> text </Emphasis>
</Segment>
<Segment StartTime="972.911" EndTime="978.459" Participant="fe016">
So you need the word - you need the word to c- sort of control the relative location.
</Segment>
<Segment StartTime="975.100" EndTime="976.975" Participant="me011">
to tell it where it got it <Emphasis> wrong. </Emphasis> Yeah.
</Segment>
<Segment StartTime="977.250" EndTime="981.269" Participant="me018">
No, I'm not sug- I'm not suggesting that we don't have anything <Emphasis> between </Emphasis> the beeps.
</Segment>
<Segment StartTime="980.000" EndTime="981.012" Participant="fe016">
It will tell you -
</Segment>
<Segment StartTime="981.800" EndTime="982.220" Participant="fe016">
Oh.
</Segment>
<Segment StartTime="982.220" EndTime="985.410" Participant="me018">
But I - what I'm saying is, what's <Emphasis> between </Emphasis> the beeps we don't really <Emphasis> care </Emphasis> about.
</Segment>
<Segment StartTime="985.680" EndTime="987.363" Participant="fe016">
I think you <Emphasis> do </Emphasis> care about it.
</Segment>
<Segment StartTime="987.060" EndTime="989.317" Participant="me011">
Because you have to know which ones match which.
</Segment>
<Segment StartTime="987.363" EndTime="989.038" Participant="fe016">
<Emphasis> Unless </Emphasis> you wanna know if they're -
</Segment>
<Segment StartTime="989.038" EndTime="991.770" Participant="fe016">
Right. Otherwise you just count up the total
</Segment>
<Segment StartTime="991.740" EndTime="993.660" Participant="me011">
And we can do that with <Emphasis> wordcount. </Emphasis> <Comment Description="while laughing"/> <Comment Description="maybe referring to UNIX program &quot;wc&quot;"/>
</Segment>
<Segment StartTime="991.770" EndTime="992.861" Participant="fe016">
number of beeps.
</Segment>
<Segment StartTime="994.380" EndTime="997.745" Participant="me011">
Right? We <Emphasis> already </Emphasis> know that - that we're three <Emphasis> short. </Emphasis> And so if we just did
</Segment>
<Segment StartTime="995.661" EndTime="996.347" Participant="fe016">
Yeah.
</Segment>
<Segment StartTime="998.630" EndTime="1004.651" Participant="me011">
spee- uh beep and non-beep all you would <Emphasis> get </Emphasis> is that you have three <Emphasis> mistakes, </Emphasis> but you wouldn't tell you which ones were <Emphasis> wrong. </Emphasis>
</Segment>
<Segment StartTime="1006.430" EndTime="1006.974" Participant="fe016">
Right.
</Segment>
<Segment StartTime="1007.339" EndTime="1013.304" Participant="me011">
You need some of the <Emphasis> words </Emphasis> in there, so that you can say "well, <Emphasis> this </Emphasis> segment matches <Emphasis> this </Emphasis> one, <Emphasis> this </Emphasis> segment matches <Emphasis> this </Emphasis> one, and <Emphasis> this </Emphasis> one doesn't match at <Emphasis> all, </Emphasis>
</Segment>
<Segment StartTime="1013.720" EndTime="1015.007" Participant="me011">
unless we insert a <Emphasis> beep </Emphasis>".
</Segment>
<Segment StartTime="1016.935" EndTime="1020.070" Participant="fe016">
<Uncertain> I mean </Uncertain> the <Emphasis> only </Emphasis> thing I'm worried about with that approach is that if
</Segment>
<Segment StartTime="1017.852" EndTime="1018.621" Participant="me013">
O_K.
</Segment>
<Segment StartTime="1020.240" EndTime="1021.168" Participant="fe016">
we need to
</Segment>
<Segment StartTime="1021.690" EndTime="1022.601" Participant="fe016">
figure out the beep
</Segment>
<Segment StartTime="1023.160" EndTime="1024.328" Participant="fe016">
alignment problem
</Segment>
<Segment StartTime="1024.699" EndTime="1031.281" Participant="fe016">
before the transcribers do the corrections here, <Comment Description="rising intonation"/> then we're in trouble. In other words, if the transcripts aren't sort of
</Segment>
<Segment StartTime="1031.900" EndTime="1033.427" Participant="fe016">
good enough that the aligner
</Segment>
<Segment StartTime="1033.986" EndTime="1036.364" Participant="fe016">
constraints are good enough to sort of
</Segment>
<Segment StartTime="1036.364" EndTime="1038.041" Participant="fe016">
show you where the errors are, then
</Segment>
<Segment StartTime="1038.041" EndTime="1042.691" Participant="fe016">
it wouldn't work. But it <Emphasis> might </Emphasis> work. It might work to do this if their transcripts are pretty close
</Segment>
<Segment StartTime="1042.691" EndTime="1045.655" Participant="fe016">
on the words that usually get recognized correctly, which are the,
</Segment>
<Segment StartTime="1046.314" EndTime="1048.516" Participant="fe016">
you know, function words, the <Emphasis> common </Emphasis> words.
</Segment>
<Segment StartTime="1047.190" EndTime="1050.895" Participant="me011">
Well, actually, you know, there's an even easier way. We don't really need a beep model.
</Segment>
<Segment StartTime="1050.895" EndTime="1054.320" Participant="me011">
Um, just extract the segments and do a forced alignment,
</Segment>
<Segment StartTime="1054.930" EndTime="1055.948" Participant="fe016">
Right, you can also -
</Segment>
<Segment StartTime="1054.930" EndTime="1057.890" Participant="me011">
and if the score is <Emphasis> good, </Emphasis> then you say it matches -
</Segment>
<Segment StartTime="1056.292" EndTime="1057.442" Participant="fe016">
In fact that's what we do -
</Segment>
<Segment StartTime="1057.442" EndTime="1060.232" Participant="fe016">
Right. The individual segments <Emphasis> between </Emphasis> the beeps -
</Segment>
<Segment StartTime="1060.790" EndTime="1064.100" Participant="fe016">
Um, if beeps were like the segments that we get from
</Segment>
<Segment StartTime="1064.230" EndTime="1069.856" Participant="fe016">
um, the transcription tool <Emphasis> already, </Emphasis> that <Emphasis> that's </Emphasis> what we have <Emphasis> done, </Emphasis> and it works <Emphasis> very </Emphasis> well. You can see these
</Segment>
<Segment StartTime="1070.270" EndTime="1071.858" Participant="fe016">
segments align and these don't.
</Segment>
<Segment StartTime="1072.440" EndTime="1077.490" Participant="fe016">
Um, then you just have to go back in and figure out where the endpoints of those segments are, cuz some of them will be wrong.
</Segment>
<Segment StartTime="1077.490" EndTime="1079.823" Participant="fe016">
Because the bi- the beeps were missing, by <Emphasis> definition. </Emphasis>
</Segment>
<Segment StartTime="1077.550" EndTime="1078.038" Participant="me011">
Right.
</Segment>
<Segment StartTime="1079.650" EndTime="1082.850" Participant="me018">
So do you get a score for each alignment? Is that what you get?
</Segment>
<Segment StartTime="1079.823" EndTime="1081.662" Participant="fe016">
So it might actually work.
</Segment>
<Segment StartTime="1082.160" EndTime="1084.459" Participant="fe016">
Um, you ca- you get, um -
</Segment>
<Segment StartTime="1086.550" EndTime="1089.218" Participant="fe016">
Definitely when they don't align at all, it - it - it <Emphasis> fails. </Emphasis>
</Segment>
<Segment StartTime="1089.218" EndTime="1090.927" Participant="fe016">
I mean, that - that's how we found a lot of
</Segment>
<Segment StartTime="1089.257" EndTime="1089.973" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="1091.290" EndTime="1095.689" Participant="fe016">
problems <Emphasis> before, </Emphasis> with, um, words being on the wrong place or something.
</Segment>
<Segment StartTime="1095.689" EndTime="1098.061" Participant="fe016">
So a <Emphasis> failed </Emphasis> alignment is a very good indicator that -
</Segment>
<Segment StartTime="1098.018" EndTime="1098.800" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="1098.410" EndTime="1098.923" Participant="fe016">
that -
</Segment>
<Segment StartTime="1099.530" EndTime="1100.776" Participant="fe016">
the words don't match up.
</Segment>
<Segment StartTime="1099.710" EndTime="1101.880" Participant="me018">
I'm just wondering when - wha- what it means to fail.
</Segment>
<Segment StartTime="1101.230" EndTime="1101.876" Participant="fe016">
Um -
</Segment>
<Segment StartTime="1101.880" EndTime="1104.725" Participant="me018">
Is it the - the likelihood scores below some threshold -
</Segment>
<Segment StartTime="1103.960" EndTime="1105.852" Participant="fe016">
Yeah, is, uh - it - Right.
</Segment>
<Segment StartTime="1105.852" EndTime="1107.276" Participant="fe016">
It can't match up the -
</Segment>
<Segment StartTime="1107.276" EndTime="1113.162" Participant="fe016">
That's why you actually need the text. In order to force you to try to match something that gives you a model to match against.
</Segment>
<Segment StartTime="1114.373" EndTime="1116.230" Participant="fe016">
So - It's just an idea, if -
</Segment>
<Segment StartTime="1117.040" EndTime="1118.149" Participant="fe016">
if it turns out that -
</Segment>
<Segment StartTime="1118.149" EndTime="1120.980" Participant="fe016">
I mean, I <Emphasis> also </Emphasis> like this idea of high and low beeps, or -
</Segment>
<Segment StartTime="1120.980" EndTime="1121.919" Participant="fe016">
But it - if -
</Segment>
<Segment StartTime="1121.919" EndTime="1125.109" Participant="fe016">
Suppose we get <Emphasis> one </Emphasis> or <Emphasis> two </Emphasis> errors, <Emphasis> still, </Emphasis> per -
</Segment>
<Segment StartTime="1126.270" EndTime="1127.884" Participant="fe016">
you know, per transcript, then we z-
</Segment>
<Segment StartTime="1128.570" EndTime="1130.620" Participant="fe016">
we might wanna try some approach like that.
</Segment>
<Segment StartTime="1130.620" EndTime="1134.807" Participant="me011">
Well, the <Emphasis> numbered </Emphasis> ones would make it a lot easier, cuz you could then really localize where the error is.
</Segment>
<Segment StartTime="1132.422" EndTime="1132.989" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="1133.720" EndTime="1134.140" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="1134.073" EndTime="1134.810" Participant="fe016">
Where it is. <Comment Description="completing [me011]'s utterance"/>
</Segment>
<Segment StartTime="1134.810" EndTime="1135.309" Participant="fe016">
Right.
</Segment>
<Segment StartTime="1135.290" EndTime="1135.960" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="1135.309" EndTime="1138.476" Participant="fe016">
If - so, if that doesn't add time for <Emphasis> them, </Emphasis> that'd be great. You know, like -
</Segment>
<Segment StartTime="1137.847" EndTime="1138.341" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1138.990" EndTime="1142.105" Participant="fe008">
I think it would <Emphasis> save </Emphasis> them time. I think it would help them keep the track - <Emphasis> track </Emphasis> of it.
</Segment>
<Segment StartTime="1138.999" EndTime="1140.570" Participant="fe016">
We have to ask them.
</Segment>
<Segment StartTime="1142.606" EndTime="1151.302" Participant="me013">
Uh - uh, again, especially if there's hundred - many hundreds or thousands I still think it would - it would cut the incidence of this a lot if it was possible to break it into a couple files.
</Segment>
<Segment StartTime="1146.260" EndTime="1147.223" Participant="mn014">
<VocalSound Description="breath-laugh"/>
</Segment>
<Segment StartTime="1152.170" EndTime="1153.101" Participant="fe008">
Interesting, yeah.
</Segment>
<Segment StartTime="1152.170" EndTime="1155.786" Participant="me013">
<Uncertain> Yeah. </Uncertain> Cuz it, you know, it's r- r-
</Segment>
<Segment StartTime="1154.710" EndTime="1156.854" Participant="fe016">
I guess <Emphasis> also </Emphasis> even for the <Emphasis> transcribers, </Emphasis>
</Segment>
<Segment StartTime="1157.425" EndTime="1159.673" Participant="fe016">
it's quicker to load a smaller file - <Comment Description="last two words while laughing"/>
</Segment>
<Segment StartTime="1160.550" EndTime="1162.572" Participant="fe016">
into the - You know, t- for the checking problem. <Comment Description="voice raised due to overlap"/>
</Segment>
<Segment StartTime="1160.620" EndTime="1162.573" Participant="me011">
Yeah, I mean, we could certainly break the meetings -
</Segment>
<Segment StartTime="1162.572" EndTime="1163.157" Participant="fe016">
Into
</Segment>
<Segment StartTime="1162.573" EndTime="1165.038" Participant="me011">
We could <Pronounce> certainly </Pronounce> break the meetings into pi- pieces. <Comment Description="speech errors maybe due to overlap"/>
</Segment>
<Segment StartTime="1163.461" EndTime="1165.256" Participant="fe016">
twenty minutes chunks or something, or -
</Segment>
<Segment StartTime="1165.926" EndTime="1166.515" Participant="me011">
So, just -
</Segment>
<Segment StartTime="1166.150" EndTime="1170.178" Participant="me013">
I mean, you've already broken them into <Emphasis> chunks, </Emphasis> so if you have - if you have a th- if you have a thousand chunks then
</Segment>
<Segment StartTime="1168.430" EndTime="1168.869" Participant="me018">
Just -
</Segment>
<Segment StartTime="1170.210" EndTime="1171.978" Participant="me018">
Just accumulate it till you get twenty minutes worth? <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="1170.610" EndTime="1173.760" Participant="me013">
make <Pause/> ten things of a hundred, or - or you know.
</Segment>
<Segment StartTime="1171.978" EndTime="1173.470" Participant="me018">
There's one file.
</Segment>
<Segment StartTime="1173.530" EndTime="1174.454" Participant="me011">
<Emphasis> That's </Emphasis> true, yeah.
</Segment>
<Segment StartTime="1173.923" EndTime="1176.343" CloseMic="false">
<NonVocalSound Description="papers rustling"/>
</Segment>
<Segment StartTime="1174.181" EndTime="1174.633" Participant="mn014">
Yep.
</Segment>
<Segment StartTime="1174.606" EndTime="1178.310" Participant="me013">
And then it will be, you know, this - Eve- every now and then there'll be a - a beep missing.
</Segment>
<Segment StartTime="1178.455" EndTime="1180.256" CloseMic="false">
<NonVocalSound Description="papers rustling"/>
</Segment>
<Segment StartTime="1180.598" EndTime="1181.414" Participant="me018">
<VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="1181.190" EndTime="1182.950" Participant="fe008">
So, someone's gonna talk to Brian.
</Segment>
<Segment StartTime="1182.701" EndTime="1183.800" Participant="me018">
Yeah, I'll -
</Segment>
<Segment StartTime="1182.970" EndTime="1183.840" Participant="me011">
I think that was <Emphasis> Chuck. </Emphasis>
</Segment>
<Segment StartTime="1183.840" EndTime="1184.970" Participant="me018">
I'll talk to him.
</Segment>
<Segment StartTime="1183.889" EndTime="1184.533" Participant="fe008">
O_K.
</Segment>
<Segment StartTime="1184.471" EndTime="1184.920" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1186.680" EndTime="1190.190" Participant="fe008">
I also looked thr- over the text and I was impressed by the accuracy, it looks really good.
</Segment>
<Segment StartTime="1189.817" EndTime="1192.603" Participant="me011">
Yeah, it <Emphasis> does </Emphasis> look good. I mean, I found several errors, but they were not
</Segment>
<Segment StartTime="1193.620" EndTime="1194.386" Participant="me011">
significant.
</Segment>
<Segment StartTime="1194.860" EndTime="1197.508" Participant="me011">
They were all things that I could easily listen to and
</Segment>
<Segment StartTime="1198.230" EndTime="1201.567" Participant="me011">
sometimes convince myself they said one thing and sometimes the other, so.
</Segment>
<Segment StartTime="1201.150" EndTime="1203.696" Participant="fe008">
Yeah, it's there. Mm-hmm.
</Segment>
<Segment StartTime="1202.640" EndTime="1204.524" Participant="fe016">
I haven't looked at these, um -
</Segment>
<Segment StartTime="1205.165" EndTime="1206.609" Participant="fe016">
cuz I was gone last week, but -
</Segment>
<Segment StartTime="1206.950" EndTime="1210.051" Participant="fe016">
but Don had told me that there's a difference in some of the conventions?
</Segment>
<Segment StartTime="1210.280" EndTime="1213.670" Participant="fe008">
Oh. Yes. But this is not important. It's systematic, yeah. <Comment Description="voice raised due to overlap"/>
</Segment>
<Segment StartTime="1210.870" EndTime="1213.061" Participant="fe016">
So - but those are all <Emphasis> easy </Emphasis> things, right?
</Segment>
<Segment StartTime="1213.061" EndTime="1213.616" Participant="fe016">
Yeah.
</Segment>
<Segment StartTime="1213.616" EndTime="1214.034" Participant="fe016">
O_K.
</Segment>
<Segment StartTime="1213.710" EndTime="1218.981" Participant="fe008">
And - and Brian actually forwarded me in advance. He - he wor- he very nicely worked out
</Segment>
<Segment StartTime="1218.981" EndTime="1226.010" Participant="fe008">
a set of <Pronounce Pronunciation="&quot;conventionj&quot;"> conventions </Pronounce> which is intermediate between ours and the ones that they're <Emphasis> used </Emphasis> to. Which is - which is really a good - a good way to do it.
</Segment>
<Segment StartTime="1223.036" EndTime="1223.716" Participant="fe016">
O_K.
</Segment>
<Segment StartTime="1224.750" EndTime="1226.076" Participant="fe016">
So we can just map -
</Segment>
<Segment StartTime="1226.366" EndTime="1227.220" Participant="fe016">
map them to -
</Segment>
<Segment StartTime="1226.716" EndTime="1227.603" Participant="fe008">
No problem.
</Segment>
<Segment StartTime="1227.220" EndTime="1227.687" Participant="fe016">
Great.
</Segment>
<Segment StartTime="1229.942" EndTime="1230.860" Participant="fe016">
Hmm.
</Segment>
<Segment StartTime="1232.496" EndTime="1233.224" Participant="me011">
O_K.
</Segment>
<Segment StartTime="1233.770" EndTime="1234.458" Participant="me011">
Um -
</Segment>
<Segment StartTime="1236.670" EndTime="1243.303" Participant="me011">
We still haven't really sat down and talked about file reorganization, <Pause/> and directory reorganization. So we still have to do that.
</Segment>
<Segment StartTime="1243.810" EndTime="1245.656" Participant="me011">
But I don't think we need to do that in this meeting.
</Segment>
<Segment StartTime="1246.591" EndTime="1247.357" Participant="me011">
But, uh -
</Segment>
<Segment StartTime="1248.920" EndTime="1255.565" Participant="me011">
It <Emphasis> is </Emphasis> something that needs to get done, and I wanna <Emphasis> also </Emphasis> coordinate it with Dave so that we do a level zero backup right after.
</Segment>
<Segment StartTime="1256.766" EndTime="1258.455" Participant="me011">
So we don't waste a lot of tapes.
</Segment>
<Segment StartTime="1259.920" EndTime="1260.616" Participant="me011">
But, uh -
</Segment>
<Segment StartTime="1261.070" EndTime="1264.814" Participant="me011">
So - let's - let's try to <Emphasis> do </Emphasis> that sometime, O_K? <VocalSound Description="laugh"/> ch- O_K?
</Segment>
<Segment StartTime="1263.800" EndTime="1264.953" Participant="fe008">
Yeah. We can do it this week.
</Segment>
<Segment StartTime="1264.953" EndTime="1265.362" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="1266.050" EndTime="1266.737" Participant="me011">
Um -
</Segment>
<Segment StartTime="1268.730" EndTime="1272.929" Participant="me011">
We also still <Pause/> have to make a decision about <Emphasis> mike </Emphasis> issues, what we wanna <Emphasis> do </Emphasis> with that.
</Segment>
<Segment StartTime="1274.850" EndTime="1278.190" Participant="fe008">
I thought we were going to get two more of the
</Segment>
<Segment StartTime="1278.289" EndTime="1279.330" Participant="fe008">
ones -
</Segment>
<Segment StartTime="1278.580" EndTime="1279.839" Participant="me011">
And just swap <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> in and out?
</Segment>
<Segment StartTime="1280.410" EndTime="1281.496" Participant="me011">
Yeah, we could certainly do that.
</Segment>
<Segment StartTime="1281.827" EndTime="1283.010" Participant="mn014">
So why not?
</Segment>
<Segment StartTime="1283.320" EndTime="1284.057" Participant="me011">
So -
</Segment>
<Segment StartTime="1284.057" EndTime="1285.288" Participant="me011">
uh, Morgan, just to -
</Segment>
<Segment StartTime="1286.200" EndTime="1292.065" Participant="me011">
uh, since you weren't at the meeting <Emphasis> last </Emphasis> week, uh, apparently a bunch of the E_D_U fe- folks really hate this style mike.
</Segment>
<Segment StartTime="1291.439" EndTime="1292.815" Participant="fe016">
Um, I wouldn't - well, it -
</Segment>
<Segment StartTime="1293.132" EndTime="1294.882" Participant="fe016">
they didn't say "hate" but they -
</Segment>
<Segment StartTime="1294.032" EndTime="1295.819" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1294.290" EndTime="1295.880" Participant="me018">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1294.882" EndTime="1300.079" Participant="fe016">
they c- they come on time to their meetings in order to not be <Emphasis> left </Emphasis> the last person who has to sit by those
</Segment>
<Segment StartTime="1300.282" EndTime="1301.829" Participant="fe008">
Can I - I c- I -
</Segment>
<Segment StartTime="1300.390" EndTime="1303.840" Participant="me011">
I mean, that's - that's - <Emphasis> that's </Emphasis> a fairly strong indication of dislike.
</Segment>
<Segment StartTime="1300.697" EndTime="1301.055" Participant="fe016">
mikes.
</Segment>
<Segment StartTime="1301.055" EndTime="1302.099" Participant="fe016">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1304.191" EndTime="1307.000" Participant="fe008">
<Emphasis> I </Emphasis> actually really like <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> though. <Comment Description="while laughing"/>
</Segment>
<Segment StartTime="1304.700" EndTime="1305.440" Participant="me011">
Um -
</Segment>
<Segment StartTime="1305.110" EndTime="1306.840" Participant="me013">
Which one is these? The uh -
</Segment>
<Segment StartTime="1305.480" EndTime="1309.053" Participant="fe016">
There were a few people - you, and like, three or four people who <Emphasis> really </Emphasis> like them.
</Segment>
<Segment StartTime="1306.190" EndTime="1306.834" Participant="me011">
The Crown.
</Segment>
<Segment StartTime="1307.290" EndTime="1307.816" Participant="me013">
Uh-huh.
</Segment>
<Segment StartTime="1308.900" EndTime="1309.850" Participant="fe008">
Yeah, <Emphasis> I </Emphasis> do.
</Segment>
<Segment StartTime="1309.053" EndTime="1310.752" Participant="fe016">
And e- and th- all the others
</Segment>
<Segment StartTime="1310.752" EndTime="1311.875" Participant="fe016">
really don't.
</Segment>
<Segment StartTime="1310.960" EndTime="1316.620" Participant="me011">
So what I was <Emphasis> thinking </Emphasis> is, we could <Emphasis> get </Emphasis> a few more of the <Emphasis> Sony </Emphasis> ones and just unplug <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> and plug <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> in. And the only thing is that
</Segment>
<Segment StartTime="1316.333" EndTime="1320.444" Participant="me013">
<VocalSound Description="long breath"/>
</Segment>
<Segment StartTime="1316.620" EndTime="1320.682" Participant="me011">
when you fill out the <Emphasis> digit </Emphasis> forms, you have to be sure to indicate which mike was actually used.
</Segment>
<Segment StartTime="1321.150" EndTime="1324.250" Participant="me011">
So, I mean, that's easy to do. Um -
</Segment>
<Segment StartTime="1324.460" EndTime="1325.010" Participant="me011">
it - it -
</Segment>
<Segment StartTime="1325.197" EndTime="1331.180" Participant="me011">
moves us <Emphasis> away </Emphasis> from this uniform, all the mikes are the <Emphasis> same, </Emphasis> which some people had said was a benefit.
</Segment>
<Segment StartTime="1332.330" EndTime="1332.736" Participant="me011">
But -
</Segment>
<Segment StartTime="1332.813" EndTime="1340.180" Participant="fe008">
The <Emphasis> other </Emphasis> thing, <Emphasis> too, </Emphasis> is th- y- <Emphasis> you </Emphasis> said that the acoustic pra- q- quality of the one that you're <Emphasis> wearing, </Emphasis> the <Emphasis> fancy </Emphasis> one, is actually somewhat <Emphasis> better </Emphasis> than
</Segment>
<Segment StartTime="1339.740" EndTime="1340.385" Participant="me011">
It <Emphasis> is. </Emphasis>
</Segment>
<Segment StartTime="1340.385" EndTime="1340.909" Participant="me011">
Yeah.
</Segment>
<Segment StartTime="1341.130" EndTime="1344.141" Participant="fe008">
So I- I don't know if it's a noticeable <Emphasis> difference, </Emphasis> but it is -
</Segment>
<Segment StartTime="1344.141" EndTime="1349.330" Participant="fe008">
I mean, I p- I personally really <Emphasis> prefer </Emphasis> that model, so I think you know we've got this problem of people having different -
</Segment>
<Segment StartTime="1349.687" EndTime="1351.133" Participant="fe008">
different preferences.
</Segment>
<Segment StartTime="1350.990" EndTime="1354.922" Participant="me013">
You know, there are <Emphasis> so </Emphasis> many things about this that are non-uniform that I think having -
</Segment>
<Segment StartTime="1354.922" EndTime="1360.440" Participant="me013">
having <Emphasis> some </Emphasis> modicum of uniformity is a good thing, but you're just not going to - I mean we've -
</Segment>
<Segment StartTime="1360.669" EndTime="1361.260" Participant="fe008">
O_K.
</Segment>
<Segment StartTime="1360.977" EndTime="1361.941" Participant="me013">
uh -
</Segment>
<Segment StartTime="1362.552" EndTime="1371.108" Participant="me013">
For instance, jus- just the fact that people sit in different positions, different times, the - exactly where they put it with respect to their mouth is different each time.
</Segment>
<Segment StartTime="1367.041" EndTime="1367.488" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1369.327" EndTime="1370.251" Participant="mn014">
<VocalSound Description="sudden expulsive outbreath"/>
</Segment>
<Segment StartTime="1371.650" EndTime="1372.617" Participant="me013">
Uh -
</Segment>
<Segment StartTime="1373.260" EndTime="1379.929" Participant="me013">
I - I just don't - I mean, I think we - we're - we're getting rid of <Emphasis> major </Emphasis> differences like we're not using the lapel anymore, an- and so forth. But
</Segment>
<Segment StartTime="1376.642" EndTime="1377.784" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="1379.929" EndTime="1384.060" Participant="me013">
the other stuff is just gonna - some variability we're gonna have to accept.
</Segment>
<Segment StartTime="1383.116" EndTime="1384.034" Participant="fe008">
<VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="1384.034" EndTime="1391.520" Participant="fe008">
It's - I - I understand, that's fine with me. I - I g- <Emphasis> would </Emphasis> say that um, I find this model easier to <Emphasis> adjust, </Emphasis> that's one of the reasons I don't like <Emphasis> these, </Emphasis> cuz I keep m-
</Segment>
<Segment StartTime="1384.366" EndTime="1384.860" Participant="me011">
<VocalSound Description="inbreath"/> <Comment Description="as if to speak"/>
</Segment>
<Segment StartTime="1390.362" EndTime="1391.570" Participant="me013">
Uh-huh.
</Segment>
<Segment StartTime="1391.520" EndTime="1394.560" Participant="fe008">
you know, bending it, and then it's n- and I never really know -
</Segment>
<Segment StartTime="1393.250" EndTime="1395.198" Participant="me013">
Yeah, see I - I happen to like the old one better.
</Segment>
<Segment StartTime="1395.110" EndTime="1396.018" Participant="fe008">
You do? O_K.
</Segment>
<Segment StartTime="1395.198" EndTime="1395.676" Participant="me013">
But -
</Segment>
<Segment StartTime="1395.676" EndTime="1396.193" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1396.310" EndTime="1398.720" Participant="fe016">
What about just a different <Emphasis> headband </Emphasis> thing?
</Segment>
<Segment StartTime="1396.352" EndTime="1397.870" Participant="me013">
And some people do, but -
</Segment>
<Segment StartTime="1398.720" EndTime="1402.506" Participant="fe016">
Or even if we could attach two headband - Like, I don't <Emphasis> mind </Emphasis> those, but it -
</Segment>
<Segment StartTime="1398.859" EndTime="1399.867" Participant="me011">
I mean -
</Segment>
<Segment StartTime="1399.867" EndTime="1400.917" Participant="me011">
<Uncertain> th- </Uncertain>
</Segment>
<Segment StartTime="1400.917" EndTime="1401.762" Participant="me011">
We abs- th-
</Segment>
<Segment StartTime="1402.130" EndTime="1405.844" Participant="me011">
We have lots o- of choices of microphones. So -
</Segment>
<Segment StartTime="1402.911" EndTime="1404.260" Participant="fe016">
they bounce around.
</Segment>
<Segment StartTime="1406.410" EndTime="1409.316" Participant="fe016">
I mean, can we keep the <Emphasis> microphones, </Emphasis> and just
</Segment>
<Segment StartTime="1408.704" EndTime="1409.209" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="1409.630" EndTime="1411.496" Participant="fe016">
somehow attach a more comfortable <Comment Description="last two words while laughing"/>
</Segment>
<Segment StartTime="1412.218" EndTime="1413.261" Participant="fe016">
thing over your head?
</Segment>
<Segment StartTime="1412.354" EndTime="1412.928" Participant="me011">
<Uncertain> Mmm. </Uncertain>
</Segment>
<Segment StartTime="1412.928" EndTime="1413.428" Participant="me011">
Yeah.
</Segment>
<Segment StartTime="1413.261" EndTime="1414.899" Participant="fe016">
<Emphasis> That's </Emphasis> my <Emphasis> problem </Emphasis> with this one. The -
</Segment>
<Segment StartTime="1414.899" EndTime="1418.596" Participant="fe016">
the <Emphasis> ear </Emphasis> thing comes out to <Emphasis> here. </Emphasis> It doesn't even <Emphasis> fit </Emphasis> over my <Emphasis> ear. </Emphasis>
</Segment>
<Segment StartTime="1415.128" EndTime="1416.174" Participant="me018">
<VocalSound Description="breath-laugh"/>
</Segment>
<Segment StartTime="1418.310" EndTime="1418.676" Participant="me011">
Right.
</Segment>
<Segment StartTime="1418.436" EndTime="1419.383" Participant="fe008">
Hmm.
</Segment>
<Segment StartTime="1418.596" EndTime="1422.758" Participant="fe016">
And for some of the others, it's - their ears were shaped in a way that
</Segment>
<Segment StartTime="1422.758" EndTime="1424.080" Participant="fe016">
didn't hold the -
</Segment>
<Segment StartTime="1423.536" EndTime="1424.278" Participant="me011">
Right.
</Segment>
<Segment StartTime="1423.859" EndTime="1424.767" Participant="fe008">
<Uncertain NumSyllables="1"> @@ </Uncertain> Huh.
</Segment>
<Segment StartTime="1424.765" EndTime="1428.900" Participant="me011">
I mean, so we can go microphone shopping, and get - get more microphones. It's just - w- <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1428.771" EndTime="1429.485" Participant="me013">
<VocalSound Description="inbreath"/> <Comment Description="as if to speak"/>
</Segment>
<Segment StartTime="1428.779" EndTime="1430.852" Participant="fe008">
Then they have to be rewired though, don't they?
</Segment>
<Segment StartTime="1429.475" EndTime="1431.181" Participant="me011">
I'm just not sure what we should do.
</Segment>
<Segment StartTime="1429.485" EndTime="1430.465" Participant="me013">
<VocalSound Description="outbreath"/>
</Segment>
<Segment StartTime="1429.690" EndTime="1430.050" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="1430.465" EndTime="1436.900" Participant="me013">
<VocalSound Description="inbreath"/> You know. I mean, here's another argument against worrying too much about uniformity. We have something like forty-five hours of data collected.
</Segment>
<Segment StartTime="1430.852" EndTime="1431.930" Participant="fe008">
<Emphasis> Specially. </Emphasis>
</Segment>
<Segment StartTime="1438.310" EndTime="1442.731" Participant="me013">
And, uh, we're also gonna be integrating in this corpus stuff that's - that's being done at U_W,
</Segment>
<Segment StartTime="1442.517" EndTime="1443.039" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1443.370" EndTime="1446.570" Participant="me013">
uh, with entirely different microphones. So I - I think,
</Segment>
<Segment StartTime="1446.990" EndTime="1447.451" Participant="me013">
you know,
</Segment>
<Segment StartTime="1447.790" EndTime="1449.293" Participant="me013">
getting away from the lapel,
</Segment>
<Segment StartTime="1449.293" EndTime="1454.522" Participant="me013">
having close-mounted mikes, having people adjust them as they're most - as - as - as comfortable as they can -
</Segment>
<Segment StartTime="1454.472" EndTime="1455.618" Participant="me011">
<VocalSound Description="inbreath"/> Well, I -
</Segment>
<Segment StartTime="1455.050" EndTime="1456.464" Participant="me013">
I think that's sort of the big deal.
</Segment>
<Segment StartTime="1455.980" EndTime="1458.174" Participant="me011">
<Emphasis> I </Emphasis> agree with that, and so <Emphasis> my </Emphasis> feeling is,
</Segment>
<Segment StartTime="1458.174" EndTime="1460.173" Participant="me011">
we should get mikes that people like.
</Segment>
<Segment StartTime="1460.240" EndTime="1460.597" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1460.430" EndTime="1460.680" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="1460.680" EndTime="1464.294" Participant="me011">
And so I- <Emphasis> my </Emphasis> feeling is, going out and buying a few more <Emphasis> mikes </Emphasis> is <Emphasis> fine. </Emphasis>
</Segment>
<Segment StartTime="1464.060" EndTime="1464.418" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1464.401" EndTime="1465.405" Participant="mn014">
<Uncertain> Yeah, that's right. </Uncertain>
</Segment>
<Segment StartTime="1464.850" EndTime="1466.453" Participant="me011">
So should I just go <Emphasis> do </Emphasis> that?
</Segment>
<Segment StartTime="1465.980" EndTime="1466.503" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1466.453" EndTime="1467.004" Participant="me011">
O_K.
</Segment>
<Segment StartTime="1466.625" EndTime="1467.897" Participant="fe016">
What about these -
</Segment>
<Segment StartTime="1467.004" EndTime="1469.978" Participant="me011">
And then also, should we go ahead and get another <Emphasis> wireless </Emphasis> system?
</Segment>
<Segment StartTime="1470.660" EndTime="1472.599" Participant="me011">
You know, for whatever it's gonna be, uh -
</Segment>
<Segment StartTime="1474.085" EndTime="1474.910" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="1474.685" EndTime="1476.582" Participant="me013">
Uh, another wireless system. <Comment Description="echoes [me011]'s utterance, indicating not yet clear"/>
</Segment>
<Segment StartTime="1476.773" EndTime="1479.120" Participant="me013">
You mean, another <Emphasis> transmitter? </Emphasis> Or - or -
</Segment>
<Segment StartTime="1479.120" EndTime="1484.129" Participant="me011">
Uh, no, actually, get - we need another box. Because each - each box in the back room can only take six.
</Segment>
<Segment StartTime="1484.590" EndTime="1487.684" Participant="me013">
Oh, to get r- to get rid of the wired things. Yes, absolutely.
</Segment>
<Segment StartTime="1485.005" EndTime="1485.620" Participant="me011">
So we could-
</Segment>
<Segment StartTime="1486.096" EndTime="1486.460" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1487.860" EndTime="1488.344" Participant="me011">
O_K.
</Segment>
<Segment StartTime="1488.870" EndTime="1489.260" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1489.330" EndTime="1497.480" Participant="me013">
Uh, because - cuz we've had - With the exception of forgetting to change the batteries from time to time, uh, we've really had no tr- <Emphasis> no </Emphasis> trouble with this at all, right? And -
</Segment>
<Segment StartTime="1489.400" EndTime="1490.687" Participant="me011">
So I'll just go d- I'll do that.
</Segment>
<Segment StartTime="1496.177" EndTime="1496.657" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1497.793" EndTime="1501.356" Participant="me013">
and the wired stuff is just gonna continue to degrade as, you know, and
</Segment>
<Segment StartTime="1499.713" EndTime="1500.578" Participant="fe016">
<VocalSound Description="laugh-breath"/>
</Segment>
<Segment StartTime="1501.810" EndTime="1503.529" Participant="me013">
nobody will remember how to -
</Segment>
<Segment StartTime="1501.900" EndTime="1504.780" Participant="fe016">
Another one just bit the dust. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1503.529" EndTime="1507.570" Participant="me013">
yeah, nobody will remember how to repair a Jimbox or a Jimlet or a - you know, it's -
</Segment>
<Segment StartTime="1504.110" EndTime="1504.850" Participant="me018">
Really?
</Segment>
<Segment StartTime="1505.220" EndTime="1507.160" Participant="fe016">
I <Emphasis> think </Emphasis> there's a problem with this one.
</Segment>
<Segment StartTime="1506.352" EndTime="1506.800" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1507.570" EndTime="1510.579" Participant="me011">
O_K. Then I will just go do that, and send the bill to -
</Segment>
<Segment StartTime="1508.664" EndTime="1509.188" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1512.000" EndTime="1513.406" Participant="me011">
uh, <Emphasis> what's-her-name. </Emphasis>
</Segment>
<Segment StartTime="1512.750" EndTime="1514.079" Participant="me013">
Whoever will pay, yeah.
</Segment>
<Segment StartTime="1513.760" EndTime="1516.942" Participant="me011">
Whoever will pay. <Emphasis> You. </Emphasis> <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1514.478" EndTime="1516.365" Participant="me013">
Yeah, yeah. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1515.432" EndTime="1516.377" Participant="me018">
<VocalSound Description="laugh-breath"/>
</Segment>
<Segment StartTime="1516.060" EndTime="1518.410" Participant="fe016">
I have a quick question about microphones, um -
</Segment>
<Segment StartTime="1518.410" EndTime="1518.795" Participant="fe016">
I got -
</Segment>
<Segment StartTime="1518.980" EndTime="1520.880" Participant="fe016">
this crazy idea that, um, i-
</Segment>
<Segment StartTime="1521.070" EndTime="1522.298" Participant="fe016">
in the future, people
</Segment>
<Segment StartTime="1523.000" EndTime="1524.404" Participant="fe016">
will just walk around with
</Segment>
<Segment StartTime="1524.633" EndTime="1527.532" Participant="fe016">
the microphones that they use for their cell phones?
</Segment>
<Segment StartTime="1527.532" EndTime="1528.998" Participant="fe016">
You know, these little boom ones,
</Segment>
<Segment StartTime="1529.430" EndTime="1534.640" Participant="fe016">
like, and really go to meetings with close talking mikes. If they're their own personal microphone.
</Segment>
<Segment StartTime="1529.718" EndTime="1531.864" Participant="fe008">
<NonVocalSound Description="mike noise"/> <Comment Description="reaching into purse for her cell phone boom mike"/>
</Segment>
<Segment StartTime="1534.900" EndTime="1535.816" Participant="fe016">
And so I'm wondering if
</Segment>
<Segment StartTime="1536.391" EndTime="1542.420" Participant="fe016">
we can get a couple of tho- I don't know how good <Emphasis> quality </Emphasis> they are, but it would be really interesting to see if they're good <Emphasis> enough. </Emphasis>
</Segment>
<Segment StartTime="1541.800" EndTime="1544.900" Participant="me013">
Do you mean the kind that hang from the ear, sort of thing, or the -
</Segment>
<Segment StartTime="1543.139" EndTime="1547.310" Participant="fe016">
The k- kind that guys that like to look like they're really cool at <Emphasis> airports </Emphasis> wear.
</Segment>
<Segment StartTime="1543.850" EndTime="1544.477" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="1546.730" EndTime="1547.880" Participant="me011">
Yeah. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1547.163" EndTime="1550.474" Participant="me013">
Yeah, but I don't know <Emphasis> that </Emphasis> one. So what's that mean? <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1548.422" EndTime="1557.505" Participant="fe008">
<NonVocalSound Description="mike noise"/> <Comment Description="unpackaging her cell phone boom mike"/>
</Segment>
<Segment StartTime="1548.780" EndTime="1551.399" Participant="me011">
This - it's - it's a cell phone jack.
</Segment>
<Segment StartTime="1548.910" EndTime="1553.873" Participant="me018">
<VocalSound Description="laugh"/> Oh, yeah, you do. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1549.100" EndTime="1553.804" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1549.683" EndTime="1552.180" Participant="fe016">
You <Emphasis> can't </Emphasis> <Emphasis> miss </Emphasis> it. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1552.180" EndTime="1556.099" Participant="fe016">
You cannot miss it. They're the guys going around - they're probably talking to nobody, but
</Segment>
<Segment StartTime="1552.626" EndTime="1553.861" Participant="me013">
Is this - just this little -
</Segment>
<Segment StartTime="1555.410" EndTime="1557.540" Participant="me013">
Oh they - they have little headsets? Or what do they -
</Segment>
<Segment StartTime="1555.596" EndTime="1556.127" Participant="mn014">
Yep.
</Segment>
<Segment StartTime="1556.002" EndTime="1557.163" Participant="me011">
Th- d-
</Segment>
<Segment StartTime="1556.824" EndTime="1558.210" Participant="fe016">
Yes. They wear the heads-
</Segment>
<Segment StartTime="1557.163" EndTime="1557.681" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1557.886" EndTime="1559.155" Participant="fe008">
<Comment Description="holds up cell phone boom mike"/>
</Segment>
<Segment StartTime="1557.889" EndTime="1559.147" CloseMic="false">
<Comment Description="[fe008] holds up her cell phone boom mike"/>
</Segment>
<Segment StartTime="1558.490" EndTime="1562.012" Participant="fe016">
E- Well, <Emphasis> there </Emphasis> you go. Yes. That's - that - it looks sort of like <Emphasis> that. </Emphasis>
</Segment>
<Segment StartTime="1558.930" EndTime="1560.246" Participant="me013">
Oh you've - you've <Emphasis> got </Emphasis> one.
</Segment>
<Segment StartTime="1560.920" EndTime="1565.248" Participant="me011">
Except that one's even bigger than most of the ones I've seen. Most of the ones are just a little boom.
</Segment>
<Segment StartTime="1563.430" EndTime="1565.625" Participant="me013">
So where - where does - how do you <Emphasis> wear </Emphasis> that? What does that -
</Segment>
<Segment StartTime="1566.840" EndTime="1569.270" Participant="fe008">
You - you put it over the corner of your ear. <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="1568.670" EndTime="1570.269" Participant="me013">
Yeah, over the corner of the ear -
</Segment>
<Segment StartTime="1570.434" EndTime="1575.388" Participant="fe008">
I can't - I'm having competing microphone - <Emphasis> headphone </Emphasis> problems here. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1573.160" EndTime="1577.860" Participant="me018">
There's <Emphasis> another </Emphasis> kind which s- goes <Emphasis> in </Emphasis> your ear and it hangs down. There's a little b- <Comment Description="unreleased bilabial merges with &quot;bulb&quot;"/> <Pause/> bulb
</Segment>
<Segment StartTime="1573.281" EndTime="1574.104" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1573.652" EndTime="1574.145" Participant="me013">
Huh.
</Segment>
<Segment StartTime="1575.388" EndTime="1578.469" Participant="fe008">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="1576.390" EndTime="1579.302" Participant="mn014">
Yep. It just ha- just hangs down there. Yeah.
</Segment>
<Segment StartTime="1576.910" EndTime="1578.343" Participant="me013">
Yeah, <Emphasis> that </Emphasis> I've seen. Yeah.
</Segment>
<Segment StartTime="1577.890" EndTime="1579.590" Participant="me018">
that hangs - has the mike on it.
</Segment>
<Segment StartTime="1578.436" EndTime="1580.686" Participant="fe016">
O_K, so whatever people sort of
</Segment>
<Segment StartTime="1578.469" EndTime="1579.900" Participant="fe008">
This one.
</Segment>
<Segment StartTime="1580.686" EndTime="1584.325" Participant="fe016">
wear to use l- Yeah, something like tha- with their cell phones,
</Segment>
<Segment StartTime="1580.780" EndTime="1581.291" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="1581.990" EndTime="1582.855" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1584.325" EndTime="1587.410" Participant="fe016">
it'd be really great, I think, if we can argue t- that -
</Segment>
<Segment StartTime="1586.878" EndTime="1588.250" Participant="fe008">
It's an interesting idea.
</Segment>
<Segment StartTime="1588.080" EndTime="1589.444" Participant="fe016">
people <Emphasis> like </Emphasis> that.
</Segment>
<Segment StartTime="1588.250" EndTime="1589.285" Participant="fe008">
The <Emphasis> acoustics </Emphasis> -
</Segment>
<Segment StartTime="1589.285" EndTime="1592.980" Participant="fe008">
the acoustics on this are really s- m- <Emphasis> better </Emphasis> than when I talk into it directly.
</Segment>
<Segment StartTime="1591.289" EndTime="1595.378" Participant="me011">
Yeah. The - the biggest issue is the stupid cable
</Segment>
<Segment StartTime="1592.660" EndTime="1593.310" Participant="me013">
But - what -
</Segment>
<Segment StartTime="1592.857" EndTime="1593.656" Participant="fe016">
Are they?
</Segment>
<Segment StartTime="1594.040" EndTime="1594.891" Participant="me013">
Why would it be cool?
</Segment>
<Segment StartTime="1595.378" EndTime="1596.208" Participant="me011">
that Sony -
</Segment>
<Segment StartTime="1596.450" EndTime="1598.547" Participant="me011">
The connector that Sony has, that, uh -
</Segment>
<Segment StartTime="1596.670" EndTime="1597.772" Participant="fe016">
Oh, O_K.
</Segment>
<Segment StartTime="1598.550" EndTime="1600.454" Participant="fe016">
So it's - they're not compatible?
</Segment>
<Segment StartTime="1598.842" EndTime="1600.249" Participant="me011">
It's non-standard,
</Segment>
<Segment StartTime="1600.495" EndTime="1603.320" Participant="me011">
and so you can't just plug something in. You need to get it wired.
</Segment>
<Segment StartTime="1602.740" EndTime="1606.828" Participant="me013">
Oh, I'm sorry. You're talking about that as a possible thing to plug into the Sonys. No?
</Segment>
<Segment StartTime="1605.330" EndTime="1606.003" Participant="fe016">
Well,
</Segment>
<Segment StartTime="1606.003" EndTime="1608.934" Participant="fe016">
um, just as an example for,
</Segment>
<Segment StartTime="1606.180" EndTime="1606.592" Participant="me011">
Right.
</Segment>
<Segment StartTime="1606.420" EndTime="1608.070" Participant="me018">
How standard are these?
</Segment>
<Segment StartTime="1608.974" EndTime="1611.120" Participant="fe008">
Works with <Emphasis> this. </Emphasis> I don't know.
</Segment>
<Segment StartTime="1609.600" EndTime="1614.436" Participant="fe016">
you know, the future, of the fact that maybe people <Emphasis> will </Emphasis> wear those microphones, or <Emphasis> some </Emphasis> people might, <Comment Description="embedded"/>
</Segment>
<Segment StartTime="1614.436" EndTime="1616.328" Participant="fe016">
to meetings, you know.
</Segment>
<Segment StartTime="1614.550" EndTime="1616.440" Participant="me013">
Well, some people will, yeah.
</Segment>
<Segment StartTime="1616.328" EndTime="1619.270" Participant="fe016">
Not a - I'm not saying there's not a far-field microphone,
</Segment>
<Segment StartTime="1616.490" EndTime="1617.651" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1619.270" EndTime="1620.508" Participant="fe016">
uh, application, but -
</Segment>
<Segment StartTime="1621.320" EndTime="1624.225" Participant="fe016">
If we have a choi- I've always wondered how well they would work.
</Segment>
<Segment StartTime="1623.700" EndTime="1630.218" Participant="me018">
It <Emphasis> is </Emphasis> an interesting idea. If we could build an <Emphasis> adaptor </Emphasis> that went from - cuz I think <Emphasis> mine </Emphasis> looks like this <Emphasis> too. </Emphasis> If we had <Emphasis> this </Emphasis> style plug that went to <Emphasis> that, </Emphasis>
</Segment>
<Segment StartTime="1629.675" EndTime="1630.408" Participant="me011">
Right.
</Segment>
<Segment StartTime="1630.218" EndTime="1632.700" Participant="me018">
then we'd just have adaptors and people would plug <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> <Emphasis> in. </Emphasis>
</Segment>
<Segment StartTime="1633.170" EndTime="1635.180" Participant="me018">
You could use - they could use their own. <NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="1633.850" EndTime="1635.990" Participant="fe016">
Oh, right. So they could use the -
</Segment>
<Segment StartTime="1634.070" EndTime="1636.855" Participant="me011">
I wonder if you <Emphasis> could </Emphasis> do an adaptor. I don't know if you can or not.
</Segment>
<Segment StartTime="1637.260" EndTime="1639.320" Participant="fe016">
Anyway, it's just an idea. Um -
</Segment>
<Segment StartTime="1638.380" EndTime="1638.827" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1639.507" EndTime="1643.067" Participant="me011">
An adaptor might be a better idea than do- redoing the wiring all the time.
</Segment>
<Segment StartTime="1639.827" EndTime="1640.876" Participant="fe016">
<Uncertain> Mmm. </Uncertain>
</Segment>
<Segment StartTime="1639.837" EndTime="1640.805" Participant="me013">
Well, I mean, another s-
</Segment>
<Segment StartTime="1643.050" EndTime="1647.263" Participant="me013">
An- another side to that is that, um, in <Emphasis> principle, </Emphasis> uh, if it
</Segment>
<Segment StartTime="1647.263" EndTime="1649.768" Participant="me013">
all comes together, supposedly we're gonna get two
</Segment>
<Segment StartTime="1650.222" EndTime="1652.110" Participant="me013">
um, I_RAM boards.
</Segment>
<Segment StartTime="1652.110" EndTime="1652.796" Participant="me011">
Right. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="1652.510" EndTime="1654.674" Participant="me013">
Uh, little later on in the year.
</Segment>
<Segment StartTime="1654.674" EndTime="1658.367" Participant="me013">
And so, we're gonna wanna be thinking in terms of some
</Segment>
<Segment StartTime="1658.367" EndTime="1659.718" Participant="me013">
wireless connection
</Segment>
<Segment StartTime="1659.698" EndTime="1660.353" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="1660.037" EndTime="1660.600" Participant="me013">
to it.
</Segment>
<Segment StartTime="1660.600" EndTime="1661.422" Participant="me013">
Um,
</Segment>
<Segment StartTime="1661.422" EndTime="1664.433" Participant="me013">
so we have, you know, some kind of little something,
</Segment>
<Segment StartTime="1664.433" EndTime="1668.718" Participant="me013">
and, uh, we have a wireless connection, this board, that's doing the computation for the f- the, uh -
</Segment>
<Segment StartTime="1669.524" EndTime="1670.441" Participant="me013">
the recognition.
</Segment>
<Segment StartTime="1670.441" EndTime="1672.995" Participant="me013">
And so, you know, we wanna be able to show off to somebody,
</Segment>
<Segment StartTime="1672.995" EndTime="1674.915" Participant="me013">
you know, we have a base station somewhere, and
</Segment>
<Segment StartTime="1674.915" EndTime="1676.856" Participant="me013">
you're wandering around, uh,
</Segment>
<Segment StartTime="1677.640" EndTime="1678.720" Participant="me013">
hands free, and -
</Segment>
<Segment StartTime="1678.395" EndTime="1678.794" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1679.340" EndTime="1681.972" Participant="me018">
I don't understand. So - so there's a mike that plugs in -
</Segment>
<Segment StartTime="1681.972" EndTime="1684.580" Participant="me018">
You're saying there's a mike that plugs in to the <Emphasis> I_RAM </Emphasis> board? or -
</Segment>
<Segment StartTime="1683.669" EndTime="1689.004" Participant="me013">
No, no, what I'm saying is that we're gonna have to put together <Emphasis> some </Emphasis> kind of a
</Segment>
<Segment StartTime="1689.004" EndTime="1692.699" Participant="me013">
little superstructure, d- <Emphasis> some </Emphasis> sort of demo box that it - that doesn't
</Segment>
<Segment StartTime="1689.090" EndTime="1689.608" Participant="me011">
Demo.
</Segment>
<Segment StartTime="1692.699" EndTime="1695.688" Participant="me013">
do a whole lot, but it somehow connects <Emphasis> to </Emphasis> -
</Segment>
<Segment StartTime="1696.250" EndTime="1699.568" Participant="me013">
uh, remotely <Emphasis> to </Emphasis> this I_RAM board which will be doing the real computation.
</Segment>
<Segment StartTime="1700.850" EndTime="1702.200" Participant="me018">
Oh, I see.
</Segment>
<Segment StartTime="1701.730" EndTime="1704.736" Participant="me013">
In other words, we're - we're not gonna attempt to build, uh, it -
</Segment>
<Segment StartTime="1704.736" EndTime="1708.467" Participant="me013">
do the real work of building a portable device that's little, that
</Segment>
<Segment StartTime="1708.467" EndTime="1713.558" Participant="me013">
is doing all the computation we wanna do for the recognition and the far-field mike, uh,
</Segment>
<Segment StartTime="1713.558" EndTime="1717.732" Participant="me013">
compensation and all that stuff. So we're gonna do all that on this powerful board,
</Segment>
<Segment StartTime="1718.520" EndTime="1722.006" Participant="me013">
and, uh, have some wireless connection to it. And then the question is what is -
</Segment>
<Segment StartTime="1722.006" EndTime="1723.910" Participant="me013">
what does it look like, does it look like
</Segment>
<Segment StartTime="1724.480" EndTime="1725.730" Participant="me013">
something that you - you
</Segment>
<Segment StartTime="1725.730" EndTime="1731.945" Participant="me013">
hold like <Emphasis> this, </Emphasis> or do we make a big deal out of it that you hold it arm - at arm's length th- so that you can see some <Emphasis> display, </Emphasis>
</Segment>
<Segment StartTime="1732.338" EndTime="1733.887" Participant="me013">
or, uh,
</Segment>
<Segment StartTime="1734.280" EndTime="1735.999" Participant="me013">
do we <Emphasis> have </Emphasis> one of these - You know. I don't know.
</Segment>
<Segment StartTime="1736.500" EndTime="1738.600" Participant="me013">
So, it th- these are all possibilities.
</Segment>
<Segment StartTime="1736.864" EndTime="1737.303" Participant="me011">
Yep.
</Segment>
<Segment StartTime="1737.902" EndTime="1742.171" Participant="me011">
I mean, what <Emphasis> I </Emphasis> was envisioning was a P_D_A with a cellular link in it.
</Segment>
<Segment StartTime="1742.171" EndTime="1743.098" Participant="me011">
You know, with one of the r-
</Segment>
<Segment StartTime="1743.868" EndTime="1745.478" Participant="me011">
short-range wireless.
</Segment>
<Segment StartTime="1746.199" EndTime="1746.963" Participant="me011">
And let th-
</Segment>
<Segment StartTime="1746.963" EndTime="1750.258" Participant="me011">
Just do - capture the audio on the P_D_A and send the audio over the
</Segment>
<Segment StartTime="1750.680" EndTime="1751.527" Participant="me011">
wireless net.
</Segment>
<Segment StartTime="1753.070" EndTime="1756.601" Participant="me013">
Yeah. So, is- is <Emphasis> Bluetooth </Emphasis> the sort of thing that'd be, uh -
</Segment>
<Segment StartTime="1753.665" EndTime="1754.069" Participant="me011">
But.
</Segment>
<Segment StartTime="1756.040" EndTime="1759.249" Participant="me011">
Uh, Bluetooth is shorter range, but you could use Bluetooth.
</Segment>
<Segment StartTime="1760.248" EndTime="1765.128" Participant="me011">
Wh- whatever the network guys already have hooked up for this floor. I don't remember what it's called.
</Segment>
<Segment StartTime="1766.984" EndTime="1767.502" Participant="me013">
Hmm.
</Segment>
<Segment StartTime="1767.741" EndTime="1768.966" Participant="me011">
<Pronounce Pronunciation="&quot;kay&quot;"> O_K, </Pronounce> then uh,
</Segment>
<Segment StartTime="1768.966" EndTime="1772.397" Participant="me011">
another issue on file reorganization is, uh,
</Segment>
<Segment StartTime="1772.397" EndTime="1774.797" Participant="me011">
making data available to people outside ICSI.
</Segment>
<Segment StartTime="1775.433" EndTime="1777.737" Participant="me011">
So, specifically, the U_<Emphasis> W </Emphasis> folks have been
</Segment>
<Segment StartTime="1778.295" EndTime="1783.791" Participant="me011">
wanting to get <Emphasis> access </Emphasis> to it. So I think the right thing to do for that, is figure out how to do C_V_S without
</Segment>
<Segment StartTime="1784.443" EndTime="1787.910" Participant="me011">
uh, compromising security. Some pass- S_S_H tunneled
</Segment>
<Segment StartTime="1787.910" EndTime="1789.082" Participant="me011">
C_V_S,
</Segment>
<Segment StartTime="1788.620" EndTime="1790.240" Participant="me018">
Well, I- I was -
</Segment>
<Segment StartTime="1789.082" EndTime="1790.940" Participant="me011">
and then give them access.
</Segment>
<Segment StartTime="1791.430" EndTime="1797.380" Participant="me018">
I was reading through some of the C_V_S documentation and you <Emphasis> can </Emphasis> just <Emphasis> substitute </Emphasis> C_V_S for your R_S_<Emphasis> H </Emphasis> command.
</Segment>
<Segment StartTime="1795.590" EndTime="1796.812" Participant="me011">
<VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="1796.812" EndTime="1800.088" Participant="me011">
Yes, except that the command has to <Emphasis> not </Emphasis> take a <Emphasis> password. </Emphasis>
</Segment>
<Segment StartTime="1801.470" EndTime="1801.850" Participant="me018">
Hmm.
</Segment>
<Segment StartTime="1801.742" EndTime="1806.102" Participant="me011">
Because it- it's non-interactive. And so the only way to <Emphasis> do </Emphasis> that is with, uh -
</Segment>
<Segment StartTime="1806.740" EndTime="1808.468" Participant="me011">
<Emphasis> S_hosts </Emphasis>, which is insecure.
</Segment>
<Segment StartTime="1809.269" EndTime="1809.774" Participant="me018">
Hmm.
</Segment>
<Segment StartTime="1809.900" EndTime="1815.256" Participant="me011">
So we <Emphasis> still </Emphasis> have to sort of <Emphasis> look </Emphasis> at it a little bit. I mean, I'm <Emphasis> sure </Emphasis> it's been <Emphasis> solved, </Emphasis> and I just haven't found the solution yet.
</Segment>
<Segment StartTime="1815.256" EndTime="1818.619" Participant="me011">
But I am sure that people have done it because it's gonna be a problem a lot of people have.
</Segment>
<Segment StartTime="1820.570" EndTime="1821.178" Participant="me011">
But, um -
</Segment>
<Segment StartTime="1821.030" EndTime="1828.100" Participant="me013">
Who - Well, we're s- talking about a fairly limited group, are - are - is it a small enough group that they would - could just have accounts? Does that solve anything?
</Segment>
<Segment StartTime="1827.205" EndTime="1828.800" Participant="me011">
Uh, n- n-
</Segment>
<Segment StartTime="1828.967" EndTime="1832.160" Participant="me011">
not <Emphasis> really, </Emphasis> because then we have the coordination issue.
</Segment>
<Segment StartTime="1832.855" EndTime="1837.195" Participant="me011">
I mean, so <Emphasis> one </Emphasis> thing they could do - I mean, I guess that's true. <Comment Description="embedded"/> They could simply log in to ICSI
</Segment>
<Segment StartTime="1837.331" EndTime="1837.904" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1837.400" EndTime="1838.746" Participant="me018">
Well they're gonna have to have accounts -
</Segment>
<Segment StartTime="1837.930" EndTime="1839.231" Participant="me011">
and do everything locally.
</Segment>
<Segment StartTime="1839.510" EndTime="1841.570" Participant="me018">
If they use S_S_H they have to have an account anyways.
</Segment>
<Segment StartTime="1841.570" EndTime="1842.778" Participant="me011">
Yeah, except they could share one.
</Segment>
<Segment StartTime="1844.518" EndTime="1845.456" Participant="me013">
Well, but that's not -
</Segment>
<Segment StartTime="1845.070" EndTime="1845.766" Participant="me011">
The, uh -
</Segment>
<Segment StartTime="1847.047" EndTime="1849.914" Participant="me011">
the S_S_H accounts, and the
</Segment>
<Segment StartTime="1850.238" EndTime="1852.227" Participant="me011">
user accounts don't have to be similar.
</Segment>
<Segment StartTime="1853.386" EndTime="1853.892" Participant="me011">
So.
</Segment>
<Segment StartTime="1854.349" EndTime="1856.697" Participant="me011">
I mean, there are lots of ways of doing it, but w- but
</Segment>
<Segment StartTime="1856.697" EndTime="1860.259" Participant="me011">
if we can't figure out a remote way of doing it, just letting them log in to ICSI
</Segment>
<Segment StartTime="1860.946" EndTime="1861.907" Participant="me011">
might be O_K.
</Segment>
<Segment StartTime="1861.937" EndTime="1862.488" Participant="fe016">
Mm-hmm.
</Segment>
<Segment StartTime="1863.267" EndTime="1868.535" Participant="me011">
<VocalSound Description="inbreath"/> So the intention was to put everything except the audio files themselves under revision control.
</Segment>
<Segment StartTime="1869.040" EndTime="1873.733" Participant="me011">
And the audio files, it's not worth doing cuz they're too big. You're never gonna be copying them around
</Segment>
<Segment StartTime="1873.733" EndTime="1875.612" Participant="me011">
and making working copies of them.
</Segment>
<Segment StartTime="1875.800" EndTime="1877.277" Participant="mn014">
<VocalSound Description="breath-laugh"/>
</Segment>
<Segment StartTime="1876.890" EndTime="1877.378" Participant="me013">
Right.
</Segment>
<Segment StartTime="1878.340" EndTime="1883.184" Participant="me011">
And then the other issue Jane and I spoke of <Pause/> <Emphasis> briefly </Emphasis> is just general permission issues.
</Segment>
<Segment StartTime="1883.184" EndTime="1887.816" Participant="me011">
That right now, lots of people create the files and then we have group "Meeting Recorder".
</Segment>
<Segment StartTime="1887.816" EndTime="1891.009" Participant="me011">
But that means anyone in the Meeting Recorder <Emphasis> group </Emphasis> can overwrite the files.
</Segment>
<Segment StartTime="1892.010" EndTime="1899.696" Participant="me011">
And so that's a pretty coarse level of <Pause/> granularity. So we <Emphasis> might </Emphasis> wanna think about doing a Meeting Recorder user - <Emphasis> owner </Emphasis>
</Segment>
<Segment StartTime="1899.696" EndTime="1903.777" Participant="me011">
for those files, and then doing group slightly differently. But -
</Segment>
<Segment StartTime="1904.231" EndTime="1907.710" Participant="fe016">
Can you just do, like, S_U_X or something to modify -
</Segment>
<Segment StartTime="1904.480" EndTime="1905.486" Participant="me011">
I think what we have now -
</Segment>
<Segment StartTime="1907.740" EndTime="1909.690" Participant="fe016">
I mean, if you just have one user that -
</Segment>
<Segment StartTime="1910.886" EndTime="1911.644" Participant="me011">
<VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="1911.644" EndTime="1913.896" Participant="me011">
Another option is to m-
</Segment>
<Segment StartTime="1913.896" EndTime="1915.475" Participant="me011">
make a non-
</Segment>
<Segment StartTime="1916.221" EndTime="1920.509" Participant="me011">
make it owned by a not real user, and then <Emphasis> root </Emphasis> will be able to do it.
</Segment>
<Segment StartTime="1920.509" EndTime="1922.573" Participant="me011">
But <Emphasis> root </Emphasis> is pretty tightly controlled here.
</Segment>
<Segment StartTime="1922.489" EndTime="1924.840" Participant="fe008">
I had another thought. <Comment Description="syntactically complete, but abandoned turn."/>
</Segment>
<Segment StartTime="1922.534" EndTime="1923.523" Participant="fe016">
Mm-hmm.
</Segment>
<Segment StartTime="1923.780" EndTime="1925.671" Participant="me011">
So th- I don't think that's a good solution.
</Segment>
<Segment StartTime="1924.860" EndTime="1928.220" Participant="fe008">
Would - w- would it be possi- There are scripts that uh, run,
</Segment>
<Segment StartTime="1928.739" EndTime="1935.140" Participant="fe008">
and - and when it's finished compressing, would it be possible for the script to change the permissions on the file to be more strict?
</Segment>
<Segment StartTime="1935.321" EndTime="1936.430" Participant="fe008">
Have <Pronounce Pronunciation="&quot;em&quot;"> them </Pronounce> -
</Segment>
<Segment StartTime="1935.908" EndTime="1939.816" Participant="me011">
<Emphasis> Yes, </Emphasis> but if you do that, then someone who isn't the owner can't
</Segment>
<Segment StartTime="1940.582" EndTime="1941.385" Participant="me011">
<Emphasis> unchange </Emphasis> it.
</Segment>
<Segment StartTime="1941.930" EndTime="1944.430" Participant="fe008">
But after the meeting's done, would they want to?
</Segment>
<Segment StartTime="1945.280" EndTime="1947.320" Participant="me011">
Yeah, as I said, it's just a question of,
</Segment>
<Segment StartTime="1947.935" EndTime="1950.564" Participant="me011">
uh, do you wanna have to track down root
</Segment>
<Segment StartTime="1950.564" EndTime="1952.327" Participant="me011">
if you have to make any change.
</Segment>
<Segment StartTime="1952.300" EndTime="1956.510" Participant="fe016">
But it doesn't have to be root. It could be some other user that we all can S_U_X <Emphasis> to. </Emphasis>
</Segment>
<Segment StartTime="1956.632" EndTime="1957.319" Participant="fe008">
That's true.
</Segment>
<Segment StartTime="1958.026" EndTime="1959.646" Participant="me011">
You have security issues with that.
</Segment>
<Segment StartTime="1960.691" EndTime="1961.177" Participant="me011">
So.
</Segment>
<Segment StartTime="1960.950" EndTime="1961.753" Participant="fe008">
Yeah, that's true.
</Segment>
<Segment StartTime="1961.825" EndTime="1962.451" Participant="fe016">
I mean -
</Segment>
<Segment StartTime="1963.020" EndTime="1965.170" Participant="me018">
That's what we do with doctor-speech though, right?
</Segment>
<Segment StartTime="1965.092" EndTime="1966.747" Participant="me011">
No, with doctor-speech, it's just a group.
</Segment>
<Segment StartTime="1967.350" EndTime="1972.145" Participant="me011">
So - there're lots of different owners of i- i- of the files, but the group is always doctor-speech.
</Segment>
<Segment StartTime="1972.145" EndTime="1973.571" Participant="me011">
Or real, usually.
</Segment>
<Segment StartTime="1973.401" EndTime="1975.550" Participant="me018">
But there is a <Emphasis> user </Emphasis> doctor-speech.
</Segment>
<Segment StartTime="1976.440" EndTime="1977.120" Participant="me018">
Right?
</Segment>
<Segment StartTime="1977.720" EndTime="1982.020" Participant="me018">
I mean, I - I S_U_X to doctor-speech w- when I need to make a -
</Segment>
<Segment StartTime="1977.986" EndTime="1979.194" Participant="me011">
Nnn-
</Segment>
<Segment StartTime="1979.820" EndTime="1980.554" Participant="me011">
Oh, <Emphasis> do </Emphasis> you?
</Segment>
<Segment StartTime="1980.530" EndTime="1981.395" Participant="fe016">
Oh. So tha-
</Segment>
<Segment StartTime="1981.395" EndTime="1983.120" Participant="fe016">
that's what I meant, it - just some
</Segment>
<Segment StartTime="1982.190" EndTime="1984.440" Participant="me018">
a directory on, uh, one of the -
</Segment>
<Segment StartTime="1983.347" EndTime="1985.043" Participant="fe016">
user like "meeting-root" or something.
</Segment>
<Segment StartTime="1985.043" EndTime="1986.030" Participant="fe016">
<VocalSound Description="breath-laugh"/>
</Segment>
<Segment StartTime="1985.310" EndTime="1985.876" Participant="me011">
Oh, O_K.
</Segment>
<Segment StartTime="1986.030" EndTime="1986.586" Participant="fe016">
I don't know.
</Segment>
<Segment StartTime="1990.740" EndTime="1993.217" Participant="me011">
I mean, I'm not <Emphasis> too </Emphasis> worried, because the group's pretty small.
</Segment>
<Segment StartTime="1994.240" EndTime="1994.597" Participant="me011">
But -
</Segment>
<Segment StartTime="1995.087" EndTime="1995.638" Participant="me013">
Yeah.
</Segment>
<Segment StartTime="1996.850" EndTime="2001.676" Participant="fe008">
Also it seems like once it's been stored that night, it's - it's possible to recover from backups,
</Segment>
<Segment StartTime="2001.676" EndTime="2007.330" Participant="fe008">
so that the main risk is avoiding it being accidentally deleted during the day that it was recorded.
</Segment>
<Segment StartTime="2009.016" EndTime="2013.579" Participant="me011">
Well, and just - You, then, also just have the general problem of permission on the other files,
</Segment>
<Segment StartTime="2015.515" EndTime="2018.669" Participant="me011">
that, do you want people checking out a transcript file
</Segment>
<Segment StartTime="2016.960" EndTime="2018.572" Participant="me013">
<VocalSound Description="cough"/> <VocalSound Description="sniff"/>
</Segment>
<Segment StartTime="2018.669" EndTime="2020.171" Participant="me011">
when they find an error,
</Segment>
<Segment StartTime="2020.171" EndTime="2022.977" Participant="me011">
and <Emphasis> correcting </Emphasis> it, or do they wa- do you want it to go through <Emphasis> you? </Emphasis>
</Segment>
<Segment StartTime="2023.190" EndTime="2023.517" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2025.050" EndTime="2025.506" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2026.110" EndTime="2027.396" Participant="fe008">
And I'd prefer it to go through me.
</Segment>
<Segment StartTime="2027.820" EndTime="2033.354" Participant="me011">
<Pronounce Pronunciation="&quot;kay&quot;"> O_K, </Pronounce> but that means that you're gonna have to be <Emphasis> available </Emphasis> for people, <Emphasis> all </Emphasis> the time, who say "there's an error here",
</Segment>
<Segment StartTime="2033.354" EndTime="2036.050" Participant="me011">
rather than just - them just going in and correcting it.
</Segment>
<Segment StartTime="2034.752" EndTime="2035.531" Participant="fe008">
<VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="2035.531" EndTime="2037.259" Participant="fe008">
Well I p- At <Emphasis> this </Emphasis> point - <Comment Description="abandons to overlap"/> Yeah. <Comment Description="to [me018] meaning &quot;go ahead&quot;"/>
</Segment>
<Segment StartTime="2036.050" EndTime="2039.020" Participant="me018">
Well, with C_V_S, though, you don't actually have to <Emphasis> do </Emphasis> it that way.
</Segment>
<Segment StartTime="2037.497" EndTime="2038.268" Participant="fe016">
<Uncertain> Yeah. </Uncertain>
</Segment>
<Segment StartTime="2038.610" EndTime="2039.218" Participant="me011">
Well, but -
</Segment>
<Segment StartTime="2039.680" EndTime="2040.288" Participant="fe008">
<VocalSound Description="inbreath"/> <Comment Description="as if to speak"/>
</Segment>
<Segment StartTime="2039.830" EndTime="2044.707" Participant="me011">
You have a <Emphasis> choice. </Emphasis> Either you <Emphasis> let </Emphasis> people do it themselves, or you don't. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="2040.780" EndTime="2041.257" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2043.294" EndTime="2044.294" Participant="fe008">
<VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="2044.284" EndTime="2049.650" Participant="me018">
What I'm saying is that it can <Emphasis> be </Emphasis> the case that people can do it themselves <Emphasis> and </Emphasis> it can be reviewed.
</Segment>
<Segment StartTime="2044.294" EndTime="2044.580" Participant="fe008">
w- w-
</Segment>
<Segment StartTime="2044.580" EndTime="2045.130" Participant="fe008">
Well- <Comment Description="abandoned due to overlap"/>
</Segment>
<Segment StartTime="2049.900" EndTime="2050.600" Participant="me018">
Right?
</Segment>
<Segment StartTime="2050.480" EndTime="2050.916" Participant="me011">
Right.
</Segment>
<Segment StartTime="2050.830" EndTime="2053.580" Participant="me018">
I mean, it's not like it's one or the other. We can do both.
</Segment>
<Segment StartTime="2055.060" EndTime="2056.558" Participant="fe016">
Yeah, you can -
</Segment>
<Segment StartTime="2055.340" EndTime="2056.666" Participant="me011">
Right, so you could get email.
</Segment>
<Segment StartTime="2057.520" EndTime="2059.838" Participant="me011">
Send email to Jane that someone has done a
</Segment>
<Segment StartTime="2060.310" EndTime="2060.713" Participant="me018">
Right.
</Segment>
<Segment StartTime="2060.720" EndTime="2061.252" Participant="fe008">
<VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="2061.252" EndTime="2063.032" Participant="fe008">
I - I wanna <Emphasis> also </Emphasis> say that, you know, this is a -
</Segment>
<Segment StartTime="2061.570" EndTime="2062.267" Participant="me011">
revision. <Comment Description="continuation follows 2 sec. pause"/>
</Segment>
<Segment StartTime="2063.032" EndTime="2068.974" Participant="fe008">
uh, uh, My - my <Emphasis> view </Emphasis> on this is that once it's in a final <Emphasis> version </Emphasis> and I'm working <Emphasis> toward </Emphasis> all these being final <Emphasis> versions, </Emphasis>
</Segment>
<Segment StartTime="2064.878" EndTime="2073.162" Participant="fe016">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="2068.974" EndTime="2069.420" Participant="fe008">
<Emphasis> then </Emphasis>
</Segment>
<Segment StartTime="2069.810" EndTime="2074.487" Participant="fe008">
it can go into this next ro- this next realm. But it - it's sort of counter-productive to have
</Segment>
<Segment StartTime="2074.487" EndTime="2079.380" Participant="fe008">
<Emphasis> changes </Emphasis> made which I would be <Emphasis> making </Emphasis> if I'd just gotten that far in the <Emphasis> file. </Emphasis> You know, it's - it's, um.
</Segment>
<Segment StartTime="2078.790" EndTime="2080.636" Participant="me011">
Well, so, you don't have to <Emphasis> release </Emphasis> it
</Segment>
<Segment StartTime="2080.636" EndTime="2083.012" Participant="me011">
to the <Emphasis> world </Emphasis> until you're <Emphasis> ready </Emphasis> to.
</Segment>
<Segment StartTime="2080.710" EndTime="2081.198" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2082.740" EndTime="2083.389" Participant="fe008">
<Emphasis> That's </Emphasis> right.
</Segment>
<Segment StartTime="2083.267" EndTime="2084.847" Participant="me011">
So the question is s- w-
</Segment>
<Segment StartTime="2083.658" EndTime="2085.655" Participant="fe008">
And then after <Emphasis> that, </Emphasis> then this would probably work.
</Segment>
<Segment StartTime="2085.655" EndTime="2086.042" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2085.800" EndTime="2090.623" Participant="me011">
So you would keep it in a separate file structure until you were ready to put it in the repository.
</Segment>
<Segment StartTime="2090.350" EndTime="2091.396" Participant="fe008">
Good, good.
</Segment>
<Segment StartTime="2091.719" EndTime="2092.890" Participant="fe016">
<NonVocalSound Description="mike noise"/> I mean -
</Segment>
<Segment StartTime="2092.500" EndTime="2093.835" Participant="me011">
Or just keep the lock on it.
</Segment>
<Segment StartTime="2092.890" EndTime="2095.650" Participant="fe016">
Is C_V_S, like - Yeah, just keep the <Emphasis> lock </Emphasis> on.
</Segment>
<Segment StartTime="2095.650" EndTime="2098.941" Participant="fe016">
I mean, just check it out - check it out and don't let anyone check it out -
</Segment>
<Segment StartTime="2096.140" EndTime="2096.989" Participant="me011">
Until you're - Yep.
</Segment>
<Segment StartTime="2098.290" EndTime="2100.484" Participant="me018">
No, it does not - the <Pronounce Pronunciation="&quot;Stee-vee-ess&quot;"> C_V_S </Pronounce> doesn't work that way. <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="2098.941" EndTime="2099.735" Participant="fe016">
Oh, it -
</Segment>
<Segment StartTime="2099.735" EndTime="2101.151" Participant="fe016">
Oh, it doesn't. Oh, O_K.
</Segment>
<Segment StartTime="2100.484" EndTime="2104.733" Participant="me018">
There's no - there's no lock when you check something out, not like R_C_S.
</Segment>
<Segment StartTime="2104.733" EndTime="2107.560" Participant="me018">
In other words, <Emphasis> everybody </Emphasis> can check out <Emphasis> anything. </Emphasis>
</Segment>
<Segment StartTime="2107.180" EndTime="2108.253" Participant="fe016">
Oh.
</Segment>
<Segment StartTime="2107.560" EndTime="2109.400" Participant="me018">
The C_ stands for "concurrent". <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="2108.253" EndTime="2111.829" Participant="fe016">
So why not use R_C_S at that point? Just at that stage?
</Segment>
<Segment StartTime="2110.270" EndTime="2111.296" Participant="me011">
Cuz it's not remote.
</Segment>
<Segment StartTime="2113.686" EndTime="2114.870" Participant="fe016">
It's not remote.
</Segment>
<Segment StartTime="2114.990" EndTime="2118.170" Participant="me011">
The nice thing about C_V_S is - is, you can be on a different machine.
</Segment>
<Segment StartTime="2119.440" EndTime="2120.650" Participant="fe016">
But at that point -
</Segment>
<Segment StartTime="2120.750" EndTime="2125.351" Participant="fe016">
we only <Emphasis> want, </Emphasis> probably, Jane to be in control <Emphasis> anyway, </Emphasis> and she - I mean, it's just an i-
</Segment>
<Segment StartTime="2124.570" EndTime="2126.171" Participant="me011">
No, because U_W
</Segment>
<Segment StartTime="2126.540" EndTime="2129.024" Participant="me011">
wants to have access to these <Emphasis> files. </Emphasis> That's the whole <Emphasis> point. </Emphasis>
</Segment>
<Segment StartTime="2129.130" EndTime="2131.110" Participant="fe016">
But not to <Emphasis> modify </Emphasis> them, right? Just to <Emphasis> read </Emphasis> them.
</Segment>
<Segment StartTime="2131.110" EndTime="2136.628" Participant="me011">
Well, if they k- en- if they record a meeting, and they create a "key" file, and they find an error in their "key" file,
</Segment>
<Segment StartTime="2137.060" EndTime="2139.046" Participant="me011">
they shouldn't have to tell <Emphasis> us </Emphasis> about that
</Segment>
<Segment StartTime="2139.046" EndTime="2140.353" Participant="me011">
so that they can create -
</Segment>
<Segment StartTime="2140.353" EndTime="2142.604" Participant="me011">
correct an error in one of <Emphasis> their </Emphasis> <Emphasis> files. </Emphasis>
</Segment>
<Segment StartTime="2142.984" EndTime="2143.430" Participant="fe008">
<VocalSound Description="mouth"/> <VocalSound Description="inbreath"/>
</Segment>
<Segment StartTime="2143.118" EndTime="2144.160" Participant="fe016">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="2143.430" EndTime="2144.465" Participant="fe008">
Well, the "<Emphasis> key </Emphasis>" file is -
</Segment>
<Segment StartTime="2143.540" EndTime="2144.770" Participant="me011">
So that's why I wanna do it -
</Segment>
<Segment StartTime="2144.160" EndTime="2145.583" Participant="fe016">
I don't <Emphasis> know, </Emphasis> uh - I mean -
</Segment>
<Segment StartTime="2144.465" EndTime="2146.014" Participant="fe008">
ke- "<Emphasis> key </Emphasis>" file's different.
</Segment>
<Segment StartTime="2144.770" EndTime="2145.942" Participant="me011">
<VocalSound Description="outbreath"/>
</Segment>
<Segment StartTime="2146.539" EndTime="2147.375" Participant="fe008">
"Key" fi-
</Segment>
<Segment StartTime="2146.750" EndTime="2147.732" Participant="me011">
Different than <Emphasis> what? </Emphasis>
</Segment>
<Segment StartTime="2147.375" EndTime="2155.380" Participant="fe008">
Well, "key" file has the extra attributes that if you notice that there are lots of spikes on channel so-and-so, it's useful as a repository for putting that there.
</Segment>
<Segment StartTime="2155.650" EndTime="2163.737" Participant="fe008">
And also if you notice that <Pause/> there was an extra speaker, and didn't get mentioned in the "key" file, but they were only there for a second, but it's t- useful to mention that they were there.
</Segment>
<Segment StartTime="2163.737" EndTime="2167.560" Participant="fe008">
So I th- I think that the "key" file is usefu- for notations related to the meeting,
</Segment>
<Segment StartTime="2164.920" EndTime="2165.364" Participant="me011">
Well -
</Segment>
<Segment StartTime="2165.788" EndTime="2166.510" Participant="me011">
B-
</Segment>
<Segment StartTime="2167.114" EndTime="2171.420" Participant="me011">
But, I mean, the meetings are gonna be the same <Emphasis> way. </Emphasis> So U_W records a meeting, we transcribe it.
</Segment>
<Segment StartTime="2167.560" EndTime="2169.221" Participant="fe008">
but it's <Emphasis> different </Emphasis> from the <Emphasis> transcript. </Emphasis> <Comment Description="voice raised due to overlap"/>
</Segment>
<Segment StartTime="2171.460" EndTime="2171.866" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2172.610" EndTime="2176.076" Participant="me011">
A few months later they listen to it and they say "Ope! <Comment Description="interjection, related to &quot;oop&quot;"/> They got that acronym wrong."
</Segment>
<Segment StartTime="2177.140" EndTime="2177.600" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2177.547" EndTime="2178.857" Participant="me011">
Why - why sh-
</Segment>
<Segment StartTime="2177.600" EndTime="2180.100" Participant="fe016">
Then they should send that through - Well -
</Segment>
<Segment StartTime="2180.500" EndTime="2186.906" Participant="fe016">
It's sort of not really a question about <Emphasis> permissions, </Emphasis> but more of <Emphasis> procedure. </Emphasis> <Emphasis> Either </Emphasis> those <Emphasis> all </Emphasis> go through <Emphasis> Jane, </Emphasis> or through <Emphasis> someone, </Emphasis>
</Segment>
<Segment StartTime="2186.499" EndTime="2187.075" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="2187.093" EndTime="2189.150" Participant="fe016">
or they <Emphasis> all </Emphasis> <Emphasis> don't. </Emphasis> But it's sort of -
</Segment>
<Segment StartTime="2189.520" EndTime="2194.232" Participant="fe016">
And if they all <Emphasis> do, </Emphasis> then there isn't a <Emphasis> problem, </Emphasis> right? Cuz once they give us the data, it's
</Segment>
<Segment StartTime="2194.810" EndTime="2197.866" Participant="fe016">
<Emphasis> ours, </Emphasis> and if they wanna make changes - I mean, ours to sort of
</Segment>
<Segment StartTime="2198.269" EndTime="2199.808" Participant="fe016">
transcribe and annotate.
</Segment>
<Segment StartTime="2199.808" EndTime="2203.470" Participant="fe016">
And if they wanna make <Emphasis> changes, </Emphasis> they can <Pause/> <Emphasis> do </Emphasis> that.
</Segment>
<Segment StartTime="2199.825" EndTime="2204.311" Participant="me011">
The - the p- the <Emphasis> point </Emphasis> here is that it would be <Emphasis> nice </Emphasis> t- for there to be <Emphasis> one </Emphasis> repository.
</Segment>
<Segment StartTime="2204.554" EndTime="2205.713" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2204.586" EndTime="2205.164" Participant="me013">
Yeah <Comment Description="rising"/>
</Segment>
<Segment StartTime="2205.150" EndTime="2207.936" Participant="me011">
And if <Emphasis> we </Emphasis> don't <Emphasis> let </Emphasis> them modify their own <Emphasis> data, </Emphasis> <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="2208.400" EndTime="2210.806" Participant="me011">
they're not gonna <Emphasis> store </Emphasis> their data in our <Emphasis> repository. </Emphasis>
</Segment>
<Segment StartTime="2210.806" EndTime="2213.530" Participant="me011">
Or if we make it <Emphasis> inconvenient </Emphasis> for them to change their data.
</Segment>
<Segment StartTime="2213.530" EndTime="2215.013" Participant="fe016">
So then if they do have acc-
</Segment>
<Segment StartTime="2214.130" EndTime="2216.189" Participant="me011">
I - I'm just looking at it the other way <Emphasis> around. </Emphasis>
</Segment>
<Segment StartTime="2215.013" EndTime="2216.187" Participant="fe016">
O_K, so what if they have -
</Segment>
<Segment StartTime="2216.187" EndTime="2218.016" Participant="fe016">
What if they have <Emphasis> accounts </Emphasis> here,
</Segment>
<Segment StartTime="2216.189" EndTime="2217.248" Participant="me011">
So - so let's say we k-
</Segment>
<Segment StartTime="2218.016" EndTime="2219.672" Participant="fe016">
and they use R_C_S,
</Segment>
<Segment StartTime="2220.237" EndTime="2223.291" Participant="fe016">
at that point, where you can l- really lock a file.
</Segment>
<Segment StartTime="2224.350" EndTime="2228.030" Participant="fe016">
I mean, I'm worried. If you can't lock a <Emphasis> file, </Emphasis> this - this to me sounds very <Emphasis> scary. </Emphasis>
</Segment>
<Segment StartTime="2224.894" EndTime="2225.461" Participant="fe008">
Hmm.
</Segment>
<Segment StartTime="2228.430" EndTime="2228.877" Participant="fe016">
Um -
</Segment>
<Segment StartTime="2229.274" EndTime="2231.556" Participant="fe016">
And if they have accounts here and they're <Emphasis> modifying </Emphasis> it - If they're ac-
</Segment>
<Segment StartTime="2231.840" EndTime="2234.117" Participant="fe016">
if they're so closely linked that they're actually
</Segment>
<Segment StartTime="2234.117" EndTime="2236.575" Participant="fe016">
<Emphasis> modifying </Emphasis> transcripts and "key" files,
</Segment>
<Segment StartTime="2237.153" EndTime="2238.406" Participant="fe016">
then they <Emphasis> could </Emphasis> do it
</Segment>
<Segment StartTime="2239.050" EndTime="2241.573" Participant="fe016">
by, you know, secure-shelling into ICSI,
</Segment>
<Segment StartTime="2242.560" EndTime="2244.110" Participant="fe016">
under R_C_S, at that point.
</Segment>
<Segment StartTime="2243.920" EndTime="2247.224" Participant="me011">
Ye- well, I don't see a real difference between R_C_S and any <Emphasis> other </Emphasis> system.
</Segment>
<Segment StartTime="2247.224" EndTime="2250.373" Participant="me011">
I mean, it's just mechanisms. The nice thing about C_V_S is that
</Segment>
<Segment StartTime="2250.373" EndTime="2254.904" Participant="me011">
you can have multiple people modifying and if the changes don't <Emphasis> overlap </Emphasis> each other,
</Segment>
<Segment StartTime="2255.760" EndTime="2256.629" Participant="me011">
they can just <Emphasis> do </Emphasis> it.
</Segment>
<Segment StartTime="2256.657" EndTime="2257.319" Participant="fe008">
Hmm.
</Segment>
<Segment StartTime="2258.797" EndTime="2259.590" Participant="fe008">
That's interesting.
</Segment>
<Segment StartTime="2259.410" EndTime="2261.994" Participant="me011">
So the problem with <Emphasis> R_C_S </Emphasis> is that if two people
</Segment>
<Segment StartTime="2259.616" EndTime="2260.168" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="2261.994" EndTime="2264.580" Participant="me011">
want to modify a file at the same <Emphasis> time </Emphasis> they <Emphasis> can't, </Emphasis>
</Segment>
<Segment StartTime="2265.226" EndTime="2268.161" Participant="me011">
because the granularity of locking is at the file level.
</Segment>
<Segment StartTime="2267.683" EndTime="2270.530" Participant="me013">
What- what does C_V_S do if they - if they <Emphasis> do </Emphasis> overlap?
</Segment>
<Segment StartTime="2270.600" EndTime="2273.970" Participant="me011">
Uh, there're lots of different policies for dealing with it. So -
</Segment>
<Segment StartTime="2270.790" EndTime="2271.550" Participant="mn014">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="2272.754" EndTime="2273.930" Participant="fe016">
Mm-hmm.
</Segment>
<Segment StartTime="2273.039" EndTime="2275.240" Participant="me018">
But typically a person has to,
</Segment>
<Segment StartTime="2274.388" EndTime="2274.992" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="2275.522" EndTime="2277.060" Participant="me018">
uh, mediate
</Segment>
<Segment StartTime="2277.679" EndTime="2278.402" Participant="fe008">
Oh.
</Segment>
<Segment StartTime="2277.850" EndTime="2280.420" Participant="me018">
you know, which changes actually get - go through.
</Segment>
<Segment StartTime="2279.045" EndTime="2280.940" Participant="mn014">
Yeah, to decide which one is - Yeah.
</Segment>
<Segment StartTime="2280.439" EndTime="2281.099" Participant="fe008">
Oh.
</Segment>
<Segment StartTime="2281.491" EndTime="2282.184" Participant="fe008">
<VocalSound Description="inbreath"/> <Comment Description="as if to speak"/>
</Segment>
<Segment StartTime="2281.634" EndTime="2282.119" Participant="me013">
Oh, I-
</Segment>
<Segment StartTime="2281.980" EndTime="2285.131" Participant="fe016">
So, maybe there <Emphasis> is </Emphasis> a way in C_V_S to <Emphasis> effectively </Emphasis> <Comment Description="rising intonation"/>
</Segment>
<Segment StartTime="2285.830" EndTime="2288.846" Participant="fe016">
<Emphasis> lock </Emphasis> something if you <Emphasis> don't </Emphasis> want people to make any changes?
</Segment>
<Segment StartTime="2289.330" EndTime="2295.060" Participant="me011">
At the <Emphasis> repository </Emphasis> level, there <Emphasis> certainly </Emphasis> is. You can mark a file as - as "you can't check this out".
</Segment>
<Segment StartTime="2291.308" EndTime="2291.921" Participant="fe016">
Uh-huh.
</Segment>
<Segment StartTime="2294.697" EndTime="2295.743" Participant="fe016">
Oh. So -
</Segment>
<Segment StartTime="2297.720" EndTime="2298.910" Participant="me018">
C_V_S is pretty good.
</Segment>
<Segment StartTime="2297.860" EndTime="2299.471" Participant="fe016">
So then you could use C_V_S
</Segment>
<Segment StartTime="2299.471" EndTime="2303.943" Participant="fe016">
and, you know, just f- have remote access, but then it's up to whoever
</Segment>
<Segment StartTime="2299.729" EndTime="2300.383" Participant="me013">
O_K. <Comment Description="quietly"/>
</Segment>
<Segment StartTime="2301.603" EndTime="2301.971" Participant="me011">
Yep.
</Segment>
<Segment StartTime="2303.943" EndTime="2307.376" Participant="fe016">
is, sort of, <Emphasis> responsible </Emphasis> for that level of <Emphasis> transcription </Emphasis> to decide
</Segment>
<Segment StartTime="2308.022" EndTime="2311.249" Participant="fe016">
<Emphasis> how </Emphasis> and <Emphasis> when </Emphasis> to put these locks, or -
</Segment>
<Segment StartTime="2309.870" EndTime="2312.120" Participant="me011">
Well, it's - it's just like source code, right?
</Segment>
<Segment StartTime="2312.120" EndTime="2316.039" Participant="me011">
So that, when you're developing it and it's really <Emphasis> rough, </Emphasis> you don't put it in the <Emphasis> repository. </Emphasis>
</Segment>
<Segment StartTime="2316.423" EndTime="2316.870" Participant="fe016">
Yeah.
</Segment>
<Segment StartTime="2316.460" EndTime="2321.024" Participant="me011">
You wait to the point when you're ready to <Emphasis> release </Emphasis> it, and then you put it in the <Emphasis> repository </Emphasis> and if other people wanna -
</Segment>
<Segment StartTime="2316.870" EndTime="2323.759" Participant="fe016">
<NonVocalSound Description="mike noise"/>
</Segment>
<Segment StartTime="2319.640" EndTime="2320.319" Participant="me018">
Yeah, so the w-
</Segment>
<Segment StartTime="2319.866" EndTime="2320.359" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="2320.319" EndTime="2320.948" Participant="me018">
In-
</Segment>
<Segment StartTime="2320.948" EndTime="2329.920" Participant="me018">
The - Maybe the model - It's a little bit different in C_V_S. When you check something out, you actually create your own directory with copies of everything in it, and that's what you <Emphasis> work </Emphasis> on.
</Segment>
<Segment StartTime="2326.580" EndTime="2327.168" Participant="me011">
Copy. <Comment Description="completing [me018]'s utterance"/>
</Segment>
<Segment StartTime="2330.060" EndTime="2332.433" Participant="me018">
So, until you're ready to check it in,
</Segment>
<Segment StartTime="2332.433" EndTime="2339.080" Participant="me018">
nobody sees anything you've done. And then when you check it in, it puts, sort of, you know - every change that you've done is - goes into the central -
</Segment>
<Segment StartTime="2336.919" EndTime="2337.688" Participant="fe016">
Right.
</Segment>
<Segment StartTime="2338.870" EndTime="2339.827" Participant="fe016">
So if that's at an-
</Segment>
<Segment StartTime="2339.080" EndTime="2339.505" Participant="me013">
Hmm.
</Segment>
<Segment StartTime="2339.827" EndTime="2346.442" Participant="fe016">
I guess it depends on Jane's - Uh, you know, if that's - if that model <Emphasis> works </Emphasis> for the <Emphasis> transcripts, </Emphasis> then
</Segment>
<Segment StartTime="2346.998" EndTime="2348.803" Participant="fe016">
that's <Emphasis> fine. </Emphasis> But if that pr-
</Segment>
<Segment StartTime="2348.803" EndTime="2349.000" Participant="fe016">
<Uncertain NumSyllables="2"> @@ </Uncertain>
</Segment>
<Segment StartTime="2349.000" EndTime="2350.227" Participant="fe016">
um, allows
</Segment>
<Segment StartTime="2351.040" EndTime="2355.163" Participant="fe016">
someone to come in and modify while <Emphasis> you're </Emphasis> modifying, and they turn out to be changes that,
</Segment>
<Segment StartTime="2356.060" EndTime="2360.686" Participant="fe016">
you know, would have been better to <Emphasis> wait </Emphasis> until your <Emphasis> version </Emphasis> came out, then
</Segment>
<Segment StartTime="2359.280" EndTime="2360.390" Participant="fe008">
<VocalSound Description="inbreath"/> <Comment Description="as if to speak"/>
</Segment>
<Segment StartTime="2360.686" EndTime="2363.360" Participant="fe016">
that's really up to <Emphasis> you, </Emphasis> not up to the <Emphasis> software, </Emphasis> so.
</Segment>
<Segment StartTime="2362.160" EndTime="2362.598" Participant="fe008">
Well,
</Segment>
<Segment StartTime="2362.598" EndTime="2368.477" Participant="fe008">
I also think, um, that the type of change ch- ch- varies an- I think it's a very good point. Because what if
</Segment>
<Segment StartTime="2368.477" EndTime="2372.421" Participant="fe008">
the - uh, what if <Emphasis> one </Emphasis> set of changes <Emphasis> one </Emphasis> person was making was
</Segment>
<Segment StartTime="2372.421" EndTime="2375.077" Participant="fe008">
with reference to some <Emphasis> typographical </Emphasis> convention.
</Segment>
<Segment StartTime="2374.738" EndTime="2375.224" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="2375.077" EndTime="2376.650" Participant="fe008">
And the <Emphasis> other </Emphasis> person n- unkn- n-
</Segment>
<Segment StartTime="2376.650" EndTime="2380.288" Participant="fe008">
quite unknowingly, was changing it the other way <Emphasis> around. </Emphasis> <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="2380.288" EndTime="2386.902" Participant="fe008">
Then you could end up with a <Emphasis> real </Emphasis> <Emphasis> mess, </Emphasis> in terms of, like, consistency of conventions across a file, there <Emphasis> is </Emphasis> an argument to be made for having a single editor editing at that level.
</Segment>
<Segment StartTime="2386.750" EndTime="2390.460" Participant="me018">
Well yeah, there would - there would have to be somebody to enforce the consistency. Yeah.
</Segment>
<Segment StartTime="2386.902" EndTime="2388.578" Participant="fe008">
But I like b- I like what Liz is saying about -
</Segment>
<Segment StartTime="2389.696" EndTime="2392.394" Participant="fe008">
That's right. And I also like - I l- also like Liz's uh, k- um,
</Segment>
<Segment StartTime="2392.394" EndTime="2401.880" Participant="fe008">
phraseology of "at this level of" - I don't remember how you put it, <Comment Description="embedded"/> but this - "at this level of transcription" or whatever. I mean it's like there are different layers of whatever and different <Emphasis> types </Emphasis> of conventions,
</Segment>
<Segment StartTime="2401.880" EndTime="2406.231" Participant="fe008">
and if it were an <Emphasis> acronym, </Emphasis> then I would - I think that it would make sense f- for them to
</Segment>
<Segment StartTime="2406.730" EndTime="2411.454" Participant="fe008">
have <Emphasis> input </Emphasis> <Emphasis> into </Emphasis> <Emphasis> that </Emphasis> level of things, but I wouldn't want them to be changing -
</Segment>
<Segment StartTime="2410.210" EndTime="2410.983" Participant="me011">
I'm just -
</Segment>
<Segment StartTime="2410.983" EndTime="2416.647" Participant="me011">
Imagine that we reverse this and <Emphasis> they </Emphasis> were keeping the repository and <Emphasis> we </Emphasis> were d- collecting meetings and <Emphasis> sending </Emphasis> them to them.
</Segment>
<Segment StartTime="2412.860" EndTime="2413.268" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2416.102" EndTime="2416.635" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="2417.310" EndTime="2418.517" Participant="me011">
If I found an error,
</Segment>
<Segment StartTime="2419.120" EndTime="2422.876" Participant="me011">
and I sent them email and said "here's this error", and I didn't get a <Emphasis> response </Emphasis> for a couple weeks,
</Segment>
<Segment StartTime="2423.279" EndTime="2427.912" Participant="me011">
I would stop sending them the - my data and I would start collecting it here and we would end up with two corpora.
</Segment>
<Segment StartTime="2428.659" EndTime="2429.896" Participant="fe008">
Well, yeah.
</Segment>
<Segment StartTime="2429.040" EndTime="2434.656" Participant="me011">
And I <Emphasis> don't </Emphasis> want that to <Emphasis> happen. </Emphasis> So we have to make it <Emphasis> convenient </Emphasis> for them to make changes that they wanna <Emphasis> make. </Emphasis>
</Segment>
<Segment StartTime="2429.896" EndTime="2430.910" Participant="fe008">
I agree.
</Segment>
<Segment StartTime="2432.880" EndTime="2434.329" Participant="fe008">
Well - <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="2434.329" EndTime="2435.119" Participant="fe008">
<VocalSound Description="inbreath"/> <Comment Description="while smiling"/>
</Segment>
<Segment StartTime="2435.119" EndTime="2438.261" Participant="fe008">
Well, I see now, we're k- back into the same situation as when we were,
</Segment>
<Segment StartTime="2438.261" EndTime="2440.416" Participant="fe008">
uh, talking about a- allowing people to edit
</Segment>
<Segment StartTime="2440.416" EndTime="2442.823" Participant="fe008">
the transcripts before they <Comment Description="while laughing"/> become public.
</Segment>
<Segment StartTime="2442.823" EndTime="2446.095" Participant="fe008">
So there's a question of how easy or how hard to modify, and how that
</Segment>
<Segment StartTime="2445.706" EndTime="2446.274" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="2446.332" EndTime="2448.772" Participant="fe008">
impacts the amount of changing that's done.
</Segment>
<Segment StartTime="2448.772" EndTime="2451.337" Participant="fe008">
And I - I think that it's, um,
</Segment>
<Segment StartTime="2452.130" EndTime="2455.225" Participant="fe008">
I - I have received some suggestions for change, which I've <Emphasis> made. </Emphasis>
</Segment>
<Segment StartTime="2455.762" EndTime="2460.422" Participant="fe008">
And um, I think with an <Emphasis> acronym, </Emphasis> that's a clear case where it would be an <Emphasis> easy </Emphasis> change to incorporate.
</Segment>
<Segment StartTime="2460.422" EndTime="2463.250" Participant="fe008">
But it <Emphasis> would </Emphasis> <Emphasis> worry </Emphasis> me to have people, um,
</Segment>
<Segment StartTime="2463.853" EndTime="2469.533" Participant="fe008">
having free reign to change these things, because of the need to have consistent conventions. And <Pause/> people who
</Segment>
<Segment StartTime="2469.533" EndTime="2473.500" Participant="fe008">
are only just <Emphasis> visiting </Emphasis> the data might not have a sense of the larger system.
</Segment>
<Segment StartTime="2474.190" EndTime="2476.163" Participant="fe016">
Yeah, that's what <Emphasis> I </Emphasis> would be worried about <Emphasis> too. </Emphasis>
</Segment>
<Segment StartTime="2474.493" EndTime="2481.070" Participant="me018">
Well, I think - yeah, I think there are probably ways that you can say that, you know, only certain users are allowed to change
</Segment>
<Segment StartTime="2475.643" EndTime="2476.162" Participant="fe008">
Yeah.
</Segment>
<Segment StartTime="2481.070" EndTime="2481.767" Participant="me018">
things.
</Segment>
<Segment StartTime="2481.694" EndTime="2482.217" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="2482.150" EndTime="2484.590" Participant="me018">
Uh, so we can probably restrict it to be -
</Segment>
<Segment StartTime="2484.800" EndTime="2490.970" Participant="me018">
You know, f- <Emphasis> casual </Emphasis> users who are just <Emphasis> browsing </Emphasis> can just r- get it read-only, can't check in to the archive.
</Segment>
<Segment StartTime="2490.050" EndTime="2490.578" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="2491.060" EndTime="2495.533" Participant="me018">
Whereas we could say "other people", you know, "these people are allowed to actually submit changes".
</Segment>
<Segment StartTime="2494.696" EndTime="2495.465" Participant="fe016">
Right.
</Segment>
<Segment StartTime="2495.533" EndTime="2496.066" Participant="me018">
I mean,
</Segment>
<Segment StartTime="2496.066" EndTime="2500.074" Participant="me018">
I - I think <Emphasis> one </Emphasis> thing that's probably everybody would <Emphasis> agree </Emphasis> on is that
</Segment>
<Segment StartTime="2500.074" EndTime="2502.410" Participant="me018">
there will never be a point where
</Segment>
<Segment StartTime="2503.160" EndTime="2507.185" Participant="me018">
you know, we can say that for <Emphasis> sure </Emphasis> there's no problems with any of the transcripts. I mean there's,
</Segment>
<Segment StartTime="2507.185" EndTime="2513.380" Participant="me018">
uh - f- You know, <Emphasis> something's </Emphasis> going to get overlooked at some point, or somebody's gonna wanna make a change <Emphasis> somehow. </Emphasis> So we need to
</Segment>
<Segment StartTime="2513.463" EndTime="2515.960" Participant="me018">
have <Emphasis> some </Emphasis> mechanism for,
</Segment>
<Segment StartTime="2516.210" EndTime="2519.000" Participant="me018">
um, handling changes in the <Emphasis> future. </Emphasis>
</Segment>
<Segment StartTime="2518.690" EndTime="2521.634" Participant="fe008">
I agr- I agree but I have to also add <Emphasis> one </Emphasis> <Emphasis> other </Emphasis> thing which i- before I forget it, <Comment Description="embedded"/> which is
</Segment>
<Segment StartTime="2521.931" EndTime="2524.813" Participant="fe008">
<Emphasis> Adam's </Emphasis> point about when you were reviewing the I_B_M transcripts.
</Segment>
<Segment StartTime="2524.813" EndTime="2526.248" Participant="fe008">
u- This was mentioned at the beginning of the meeting. <Comment Description="embedded"/>
</Segment>
<Segment StartTime="2526.578" EndTime="2533.163" Participant="fe008">
You said that there were <Emphasis> some </Emphasis> places where <Pause/> it <Emphasis> wasn't </Emphasis> what y- was written <Emphasis> already, </Emphasis> but you could <Emphasis> see </Emphasis> how they might have thought that's what it <Emphasis> said. </Emphasis>
</Segment>
<Segment StartTime="2533.514" EndTime="2541.365" Participant="fe008">
So there - it's <Emphasis> not </Emphasis> just a right and <Emphasis> wrong </Emphasis> thing. <Emphasis> Sometimes </Emphasis> there tru- there are <Emphasis> absolutely </Emphasis> stretches where there <Emphasis> is </Emphasis> no - no - k- if you were at the meeting and you could <Emphasis> ask </Emphasis> the person,
</Segment>
<Segment StartTime="2536.750" EndTime="2538.560" Participant="me018">
Yeah. Exactly.
</Segment>
<Segment StartTime="2541.504" EndTime="2541.975" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="2541.578" EndTime="2545.774" Participant="fe008">
<Emphasis> maybe, </Emphasis> m- you know, they could - they could've <Emphasis> told </Emphasis> you, but five minutes <Emphasis> later </Emphasis> they might not have been able to tell you,
</Segment>
<Segment StartTime="2545.750" EndTime="2546.550" Participant="me018">
Right.
</Segment>
<Segment StartTime="2545.774" EndTime="2547.149" Participant="fe008">
even if they were <Emphasis> listening </Emphasis> to it.
</Segment>
<Segment StartTime="2547.149" EndTime="2551.140" Participant="fe008">
So, sometimes it isn't right and wrong, sometimes it's multiple interpretations, and -
</Segment>
<Segment StartTime="2547.190" EndTime="2548.090" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="2550.970" EndTime="2552.160" Participant="me018">
Good point. Yeah.
</Segment>
<Segment StartTime="2551.562" EndTime="2554.909" Participant="fe008">
Now - But of course, this <Emphasis> does </Emphasis> raise the <Emphasis> possibility </Emphasis> of <Emphasis> allowing, </Emphasis>
</Segment>
<Segment StartTime="2554.909" EndTime="2559.317" Participant="fe008">
um, an extra annotation for, you know, alternative interpretations of a stretch.
</Segment>
<Segment StartTime="2559.303" EndTime="2559.876" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="2559.317" EndTime="2561.948" Participant="fe008">
But I just wanted to say it isn't simply right or wrong.
</Segment>
<Segment StartTime="2561.800" EndTime="2563.380" Participant="me018">
Yeah, that's a good point.
</Segment>
<Segment StartTime="2561.948" EndTime="2563.661" Participant="fe008">
Or overlooked or not overlooked.
</Segment>
<Segment StartTime="2563.661" EndTime="2565.543" Participant="fe008">
Sometimes they're truly ambiguous, and
</Segment>
<Segment StartTime="2565.460" EndTime="2565.980" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="2565.989" EndTime="2568.920" Participant="fe008">
um, uh, um, nice to have a <Emphasis> notation </Emphasis> for that, but. Yeah.
</Segment>
<Segment StartTime="2567.591" EndTime="2569.449" Participant="me013">
Gotta go. <Comment Description="whispered"/> <Comment Description="removes microphone"/>
</Segment>
<Segment StartTime="2568.630" EndTime="2569.390" Participant="me018">
Yeah.
</Segment>
<Segment StartTime="2570.000" EndTime="2573.654" Participant="fe016">
I mean, I like that idea because even a casual user can always send <Emphasis> email </Emphasis>
</Segment>
<Segment StartTime="2573.993" EndTime="2574.592" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="2574.098" EndTime="2575.491" Participant="fe016">
to whoever's in charge, and say,
</Segment>
<Segment StartTime="2575.491" EndTime="2577.951" Participant="fe016">
you know, "we'd like these changes" and,
</Segment>
<Segment StartTime="2576.310" EndTime="2576.797" Participant="me011">
Well -
</Segment>
<Segment StartTime="2577.951" EndTime="2582.461" Participant="fe016">
you know, hopefully we'll give them a response. And if they really do it a <Emphasis> lot, </Emphasis> and they say
</Segment>
<Segment StartTime="2578.050" EndTime="2579.107" Participant="me011">
I just - I don't s-
</Segment>
<Segment StartTime="2580.110" EndTime="2581.402" Participant="me011">
I don't see that this is e-
</Segment>
<Segment StartTime="2582.310" EndTime="2582.715" Participant="me011">
Yep.
</Segment>
<Segment StartTime="2582.461" EndTime="2586.303" Participant="fe016">
"we're a casual user but we want a chance to change the <Emphasis> transcripts </Emphasis>" then we can
</Segment>
<Segment StartTime="2586.760" EndTime="2589.286" Participant="fe016">
face that if it <Emphasis> happens, </Emphasis> but
</Segment>
<Segment StartTime="2587.780" EndTime="2589.685" Participant="me011">
Can you write "unread" on that? <Comment Description="referring to [me013]'s digits form"/>
</Segment>
<Segment StartTime="2589.685" EndTime="2590.794" Participant="me011">
Yeah, thank you.
</Segment>
<Segment StartTime="2589.976" EndTime="2598.278" Participant="fe016">
I don't really see the people at U_W that I <Emphasis> know </Emphasis> of right <Emphasis> now </Emphasis> making huge amoun- investing huge amounts of time in changing transcripts. But I could be wrong.
</Segment>
<Segment StartTime="2596.960" EndTime="2601.251" Participant="me011">
Probably not <Emphasis> transcripts, </Emphasis> but it would be nice to have <Emphasis> one </Emphasis> mechanism for <Emphasis> all </Emphasis> the files.
</Segment>
<Segment StartTime="2601.251" EndTime="2603.473" Participant="me011">
And they're <Emphasis> certainly </Emphasis> gonna wanna change <Emphasis> tools. </Emphasis>
</Segment>
<Segment StartTime="2602.230" EndTime="2602.624" Participant="fe016">
Yeah.
</Segment>
<Segment StartTime="2604.610" EndTime="2607.916" Participant="me011">
And so - you know, it's the same as source code. You - you release source code at some point.
</Segment>
<Segment StartTime="2608.431" EndTime="2612.533" Participant="me011">
And, either <Emphasis> you </Emphasis> have to do everything or you <Emphasis> share </Emphasis> responsibility. <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="2612.340" EndTime="2614.006" Participant="me018">
Yeah I mean a lot of the open source pro-
</Segment>
<Segment StartTime="2614.006" EndTime="2615.849" Participant="me018">
projects face this same problem.
</Segment>
<Segment StartTime="2615.610" EndTime="2616.132" Participant="fe016">
Right.
</Segment>
<Segment StartTime="2615.849" EndTime="2618.620" Participant="me018">
You know, p- <Emphasis> anybody </Emphasis> can check out the code,
</Segment>
<Segment StartTime="2618.840" EndTime="2621.172" Participant="me018">
but <Emphasis> not </Emphasis> everybody can check it in. <Uncertain> Yeah. </Uncertain>
</Segment>
<Segment StartTime="2620.170" EndTime="2623.539" Participant="fe016">
Right. <Uncertain> And </Uncertain> there's some happy medium and we don't know what that <Emphasis> is </Emphasis> yet
</Segment>
<Segment StartTime="2624.040" EndTime="2626.537" Participant="fe016">
until we get feedback from people, but
</Segment>
<Segment StartTime="2627.030" EndTime="2628.996" Participant="fe016">
what <Emphasis> if </Emphasis> it's O_K to just handle it
</Segment>
<Segment StartTime="2629.620" EndTime="2630.158" Participant="fe016">
with
</Segment>
<Segment StartTime="2630.730" EndTime="2634.653" Participant="fe016">
sort of a <Emphasis> person </Emphasis> in <Emphasis> charge </Emphasis> of the <Emphasis> philosophy </Emphasis> behind the changes,
</Segment>
<Segment StartTime="2635.083" EndTime="2637.385" Participant="fe016">
and some people with permissions,
</Segment>
<Segment StartTime="2637.385" EndTime="2643.849" Participant="fe016">
maybe by <Emphasis> request, </Emphasis> to make changes, That we don't just give people permissions if they're not gonna make changes. Because <Emphasis> I've </Emphasis> overwritten a -
</Segment>
<Segment StartTime="2644.126" EndTime="2648.397" Participant="fe016">
a file by <Emphasis> mistake, </Emphasis> not <Emphasis> wanting </Emphasis> to have done that cuz I didn't think I had permission, when I <Emphasis> did. </Emphasis>
</Segment>
<Segment StartTime="2648.245" EndTime="2648.765" Participant="me011">
Mm-hmm.
</Segment>
<Segment StartTime="2649.580" EndTime="2650.884" Participant="fe016">
Um, and then just
</Segment>
<Segment StartTime="2649.968" EndTime="2650.613" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="2651.530" EndTime="2653.773" Participant="fe016">
seeing if that is enough to -
</Segment>
<Segment StartTime="2654.090" EndTime="2655.890" Participant="fe016">
to handle the transcript changes.
</Segment>
<Segment StartTime="2657.480" EndTime="2658.879" Participant="fe016">
I'm just worried about
</Segment>
<Segment StartTime="2658.879" EndTime="2661.884" Participant="fe016">
letting everybody go in and make <Emphasis> changes, </Emphasis> cuz it's real easy when you're
</Segment>
<Segment StartTime="2661.884" EndTime="2667.803" Participant="fe016">
trying to, I don't know, run alignments and there's a word you wanna fix, to go in and do that and then mess up <Emphasis> other </Emphasis> things,
</Segment>
<Segment StartTime="2667.803" EndTime="2668.588" Participant="fe016">
if you don't know,
</Segment>
<Segment StartTime="2669.190" EndTime="2672.005" Participant="fe016">
you know, the overall philosophy behind the - the conventions.
</Segment>
<Segment StartTime="2670.925" EndTime="2671.532" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="2671.340" EndTime="2671.787" Participant="me011">
Right.
</Segment>
<Segment StartTime="2671.680" EndTime="2673.420" Participant="fe008">
<VocalSound Description="inbreath"/> And als- it also- <Comment Description="abandoned due to overlap"/> Mm-hmm.
</Segment>
<Segment StartTime="2671.700" EndTime="2677.070" Participant="me018">
Then - There is also the possibility - Remember, in C_V_S, when we talk about making changes,
</Segment>
<Segment StartTime="2675.189" EndTime="2676.564" Participant="me011">
You can back everything out. <Comment Description="completing [me018]'s utterance"/>
</Segment>
<Segment StartTime="2677.260" EndTime="2680.155" Participant="me018">
there's sort of two types that can be made. <Pause/> To your <Emphasis> local, </Emphasis>
</Segment>
<Segment StartTime="2680.155" EndTime="2681.193" Participant="me018">
or to the <Emphasis> global. </Emphasis>
</Segment>
<Segment StartTime="2681.170" EndTime="2681.657" Participant="fe016">
Mm-hmm.
</Segment>
<Segment StartTime="2681.193" EndTime="2684.650" Participant="me018">
And so people can make <Emphasis> changes </Emphasis> to their <Emphasis> local </Emphasis> and if they screw those up,
</Segment>
<Segment StartTime="2682.987" EndTime="2683.551" Participant="fe016">
Right.
</Segment>
<Segment StartTime="2684.360" EndTime="2685.144" Participant="fe016">
Exactly.
</Segment>
<Segment StartTime="2684.900" EndTime="2690.314" Participant="me018">
that's, you know, in their - that's only on them. It's w- it's the checking <Emphasis> in </Emphasis> part that r- we really care about, and
</Segment>
<Segment StartTime="2685.849" EndTime="2686.632" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="2690.314" EndTime="2695.550" Participant="me018">
<Emphasis> that </Emphasis> we can control with, you know, who can check things in and stuff. So we can - I think we can <Emphasis> do </Emphasis> this.
</Segment>
<Segment StartTime="2694.680" EndTime="2699.545" Participant="fe016">
Or just, yeah, start by make it a really tight control and then as people really need the control you can
</Segment>
<Segment StartTime="2695.223" EndTime="2695.817" Participant="fe008">
Mm-hmm.
</Segment>
<Segment StartTime="2697.080" EndTime="2697.910" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="2699.520" EndTime="2701.720" Participant="me018">
Yeah. They can still check it out -
</Segment>
<Segment StartTime="2700.551" EndTime="2702.629" Participant="fe016">
ascertain whether or not to -
</Segment>
<Segment StartTime="2701.840" EndTime="2706.631" Participant="me018">
Yeah, cuz they can still check out full copies and make whatever changes they want to their local copies.
</Segment>
<Segment StartTime="2703.664" EndTime="2704.328" Participant="fe016">
Right.
</Segment>
<Segment StartTime="2706.631" EndTime="2711.130" Participant="me018">
And it won't affect the - the g- the global, official, ones at all.
</Segment>
<Segment StartTime="2707.701" EndTime="2708.244" Participant="fe016">
Right.
</Segment>
<Segment StartTime="2710.700" EndTime="2713.647" Participant="me011">
Right, but what I want to <Emphasis> avoid </Emphasis> is ending up with two corpora.
</Segment>
<Segment StartTime="2711.643" EndTime="2712.116" Participant="mn014">
Yeah.
</Segment>
<Segment StartTime="2713.590" EndTime="2714.416" Participant="me018">
Yes.
</Segment>
<Segment StartTime="2714.251" EndTime="2718.425" Participant="me011">
And so if you make it too hard for them to check back in, they'll check it out once,
</Segment>
<Segment StartTime="2714.416" EndTime="2715.247" Participant="me018">
Definitely. <Comment Description="quietly"/>
</Segment>
<Segment StartTime="2717.847" EndTime="2718.250" Participant="me018">
Yep.
</Segment>
<Segment StartTime="2718.425" EndTime="2721.664" Participant="me011">
they'll make all the changes, they'll never tell <Emphasis> us </Emphasis> about the changes,
</Segment>
<Segment StartTime="2721.510" EndTime="2722.026" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="2721.664" EndTime="2723.810" Participant="me011">
and we'll get two different corpora.
</Segment>
<Segment StartTime="2723.758" EndTime="2724.275" Participant="me018">
Mm-hmm.
</Segment>
<Segment StartTime="2725.470" EndTime="2725.892" Participant="me011">
Right?
</Segment>
<Segment StartTime="2725.860" EndTime="2728.820" Participant="fe016">
I think we're <Emphasis> already </Emphasis> gonna - I mean there's already
</Segment>
<Segment StartTime="2728.880" EndTime="2731.537" Participant="fe016">
<Emphasis> some </Emphasis> chance that different annotations, different
</Segment>
<Segment StartTime="2731.537" EndTime="2732.870" Participant="fe016">
places, you know -
</Segment>
<Segment StartTime="2732.950" EndTime="2733.606" Participant="fe016">
But you can
</Segment>
<Segment StartTime="2734.293" EndTime="2738.088" Participant="fe016">
<Emphasis> control </Emphasis> that by <Emphasis> knowing </Emphasis> you're making two corpora or <Emphasis> knowing </Emphasis> that you're adding
</Segment>
<Segment StartTime="2738.520" EndTime="2745.533" Participant="fe016">
um, annotations on one version and you don't have the latest corrections maybe at that <Emphasis> point. </Emphasis> And then you finish the project and you realize that there were
</Segment>
<Segment StartTime="2745.760" EndTime="2748.170" Participant="fe016">
<Emphasis> corrections </Emphasis> made on your <Emphasis> originals </Emphasis> and then
</Segment>
<Segment StartTime="2748.170" EndTime="2749.551" Participant="fe016">
you have to <Emphasis> merge </Emphasis> them.
</Segment>
<Segment StartTime="2749.863" EndTime="2750.786" Participant="fe016">
And the b-
</Segment>
<Segment StartTime="2751.194" EndTime="2754.206" Participant="fe016">
the <Emphasis> thing </Emphasis> that makes it ea- O_K to <Emphasis> do </Emphasis> that, is
</Segment>
<Segment StartTime="2754.720" EndTime="2756.797" Participant="fe016">
knowing where the synch time boundaries are.
</Segment>
<Segment StartTime="2756.797" EndTime="2763.008" Participant="fe016">
Cuz you can automatically pretty much <Emphasis> merge </Emphasis> things if you've only got twenty words or so in an utterance. It's when you get the whole <Emphasis> meeting </Emphasis>
</Segment>
<Segment StartTime="2763.386" EndTime="2764.341" Participant="fe016">
and the <Emphasis> synch </Emphasis> times ch-
</Segment>
<Segment StartTime="2764.593" EndTime="2769.442" Participant="fe016">
have changed, or you can't correspond to a previous version with synch times, that you get in trouble.
</Segment>
<Segment StartTime="2771.035" EndTime="2771.680" Participant="fe016">
So.
</Segment>
<Segment StartTime="2778.250" EndTime="2780.240" Participant="fe016">
Was there anything else on your list?
</Segment>
<Segment StartTime="2779.299" EndTime="2779.785" Participant="me011">
Nope.
</Segment>
<Segment StartTime="2781.830" EndTime="2782.997" Participant="me011">
Shall we do some digits?
</Segment>
<Segment StartTime="2785.250" EndTime="2785.565" Participant="me011">
<VocalSound Description="mouth"/>
</Segment>
<Segment StartTime="2785.565" EndTime="2788.002" Participant="me011" DigitTask="true">
Uh, Transcript L_ one one six. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2788.400" EndTime="2792.670" Participant="fe016">
Now, wait, are - are we doing them simultaneously or one at a time? <VocalSound Description="laugh"/> Alright.
</Segment>
<Segment StartTime="2790.680" EndTime="2792.900" Participant="me011">
I wasn't <Emphasis> planning </Emphasis> on doing it simultaneously. <Comment Description="rise-fall-rise intonation"/>
</Segment>
<Segment StartTime="2791.860" EndTime="2796.622" Participant="me018">
<VocalSound Description="laugh"/> <Uncertain> Lee </Uncertain>, you liked that l- huh? <VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="2793.443" EndTime="2795.069" Participant="me011" DigitTask="true">
Transcript L_ one one six. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2793.707" EndTime="2795.518" Participant="fe016">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="2795.069" EndTime="2797.614" Participant="me011" DigitTask="true">
eight two six, four four five, one nine nine <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2795.153" EndTime="2796.464" Participant="fe008">
<VocalSound Description="laugh"/>
</Segment>
<Segment StartTime="2797.899" EndTime="2801.138" Participant="me011" DigitTask="true">
one three one one, eight seven three six, seven one one seven <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2801.590" EndTime="2804.909" Participant="me011" DigitTask="true">
eight, two eight three, eight zero, three eight two, nine <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2805.280" EndTime="2809.003" Participant="me011" DigitTask="true">
two, seven five eight, four three, zero nine nine, seven <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2809.550" EndTime="2812.309" Participant="me011" DigitTask="true">
zero nine four, four eight four, four seven four <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2812.760" EndTime="2815.727" Participant="me011" DigitTask="true">
seven six, four one, eight eight, nine nine, eight seven <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2816.185" EndTime="2819.512" Participant="me011" DigitTask="true">
three two, four six, four three, one nine, two eight <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2819.819" EndTime="2823.494" Participant="me011" DigitTask="true">
four seven six <Emphasis> two, </Emphasis> four O_ four <Emphasis> five, </Emphasis> nine six five one. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2825.500" EndTime="2827.701" Participant="fe016" DigitTask="true">
Transcript L_ one one seven. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2828.450" EndTime="2831.664" Participant="fe016" DigitTask="true">
seven five eight, five one three, O_ seven one four <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2832.026" EndTime="2835.810" Participant="fe016" DigitTask="true">
two six nine four, five six two three, seven O_ four four <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2836.148" EndTime="2839.699" Participant="fe016" DigitTask="true">
seven, five one three, seven four, eight O_ one, five <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2840.240" EndTime="2843.300" Participant="fe016" DigitTask="true">
six six two seven, five, three seven six <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2843.510" EndTime="2846.119" Participant="fe016" DigitTask="true">
eight O_ six, nine seven six, one four two <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2846.710" EndTime="2849.055" Participant="fe016" DigitTask="true">
one three nine, eight five, two three one O_ <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2849.408" EndTime="2852.029" Participant="fe016" DigitTask="true">
eight eight four four, four, two nine five <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2852.510" EndTime="2855.330" Participant="fe016" DigitTask="true">
four six one, one O_ three, two two four. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2857.161" EndTime="2859.460" Participant="me018" DigitTask="true">
Transcript L_ dash one two seven. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2859.748" EndTime="2863.120" Participant="me018" DigitTask="true">
two eight two, two seven six, eight six four <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2863.480" EndTime="2866.950" Participant="me018" DigitTask="true">
eight eight three, two zero six, two six two <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2867.608" EndTime="2871.283" Participant="me018" DigitTask="true">
eight seven, five six, seven six, one seven, zero zero <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2872.000" EndTime="2875.803" Participant="me018" DigitTask="true">
seven eight three zero, seven five two seven, five three eight three <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2876.360" EndTime="2880.443" Participant="me018" DigitTask="true">
five five, seven three, zero eight, five nine, five seven <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2880.750" EndTime="2884.527" Participant="me018" DigitTask="true">
one, four eight two, eight nine, six six seven, zero <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2885.120" EndTime="2888.772" Participant="me018" DigitTask="true">
two nine three six, nine two one five, zero five eight zero <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2889.350" EndTime="2892.590" Participant="me018" DigitTask="true">
nine seven six, six O_ three, nine seven six. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2893.896" EndTime="2895.620" Participant="fe008" DigitTask="true">
Transcript L_ one two nine. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2896.065" EndTime="2899.348" Participant="fe008" DigitTask="true">
zero nine, zero zero, five three, nine two, five five <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2899.840" EndTime="2903.759" Participant="fe008" DigitTask="true">
six, zero three seven, seven zero, nine eight eight, nine <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2904.503" EndTime="2907.638" Participant="fe008" DigitTask="true">
zero seven five, nine six nine, one one eight <Emphasis> two </Emphasis> <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2908.160" EndTime="2910.886" Participant="fe008" DigitTask="true">
six eight seven, two five, one one four four <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2911.400" EndTime="2914.643" Participant="fe008" DigitTask="true">
O_ four four, five five <Emphasis> two, </Emphasis> seven five O_ five <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2915.048" EndTime="2918.177" Participant="fe008" DigitTask="true">
five, seven five three, O_ O_, six seven nine <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2918.847" EndTime="2921.826" Participant="fe008" DigitTask="true">
one seven eight four, three, two seven eight <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2922.560" EndTime="2925.498" Participant="fe008" DigitTask="true">
six three seven five, one, two eight four. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2926.755" EndTime="2929.558" Participant="mn014" DigitTask="true">
Transcript L_ one two eight. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2929.711" EndTime="2933.813" Participant="mn014" DigitTask="true">
eight, four three two, three six, one O_ seven, six <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2934.540" EndTime="2937.870" Participant="mn014" DigitTask="true">
zero four six, six nine, six five O_ nine <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2938.471" EndTime="2942.890" Participant="mn014" DigitTask="true">
six two, eight seven, eight one, seven seven, O_ two <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2943.450" EndTime="2947.599" Participant="mn014" DigitTask="true">
nine, seven nine two, one zero, zero five five, one <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2948.460" EndTime="2952.440" Participant="mn014" DigitTask="true">
three zero, four seven, nine, six one five <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2953.240" EndTime="2958.109" Participant="mn014" DigitTask="true">
two zero <Pronounce> seven </Pronounce> two, six zero, six zero, six seven, four two <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2958.583" EndTime="2964.214" Participant="mn014" DigitTask="true">
three, five two four, zero six, six O_ two, eight <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2965.015" EndTime="2968.710" Participant="mn014" DigitTask="true">
three eight two, two seven, one nine nine six. <Comment Description="Digits"/>
</Segment>
<Segment StartTime="2973.097" EndTime="2975.133" Participant="me011">
<NonVocalSound Description="noise"/> Oop! <Comment Description="interjection"/> Ouch! <Comment Description="interjection"/>
</Segment>
<Segment StartTime="2975.250" EndTime="2976.170" Participant="fe008">
Ooo! <Comment Description="probably reacting to [me011]'s injury"/>
</Segment>
</Transcript>
</Meeting>