Timeline for Why is [f] ambiguous between [f] and [s] after saying the word <three>?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2014 at 4:30 | comment | added | musicallinguist | @user3898238 I'm more of an expert on human speech perception than on automated speech recognition. I can tell you with confidence that the types of errors an automated system makes depends on the algorithms used by the system. I'm also going to go out on a limb and say that the sets of sounds that are ambiguous over the phone for machines and for humans are probably quite similar in general, but that humans have a leg up because they can overcome some ambiguities with certain types of pragmatic expectations that aren't programmed into the machines. | |
| Nov 29, 2014 at 0:16 | comment | added | ruakh | +1. I first discovered this problem when I had college friends named 'Jeff' and 'Jess'. Phone conversations among their mutual friends were frequently derailed by this problem. It wasn't even that we couldn't tell which one was mentioned -- what made it such a problem is that we would often think we'd heard one name when in fact the other had been said. | |
| Nov 28, 2014 at 23:38 | comment | added | user3898238 | As a follow-up, are machine phoneme perception errors transitive, e.g. if a machine has difficulty with some sounds, will it always be the case that a human would too (over a noisy environment like the phone)? Or are there some perception errors that would be expected for a machine but not a human, i.e. the set of sounds which are ambiguous is not the same for both machine/human? | |
| Nov 28, 2014 at 21:19 | vote | accept | user3898238 | ||
| Nov 28, 2014 at 20:18 | history | answered | musicallinguist | CC BY-SA 3.0 |