Pedantic note: JS iterates through UTF-16 2-byte code units. It's that way for compatibility reasons (used to be UCS-2), but it's the worst of both worlds: not as good as UTF-8 for ASCII, can't do operations in O(1) time like UTF-32.
I made a talking emoji using regular emojis and JavaScript
11–20 of 63 posts
Re: I made a talking emoji using regular emojis and JavaScript
#12Re: I made a talking emoji using regular emojis and JavaScript
#13I'm Deaf and read lips. Thanks for this extremely intriguing idea to use emoji to depict a talking person visually. You know, some animated films get it right. Sometimes I clearly see utterances like «Thank you!», «Okay», but more often not. Especially older animations don't care and just let the character move the mouth in very simplistic ways: «Babbabbabaa Baababba ba baaa.» Similarly for that emoji. It is moving t…
You could actually propose a whole set of Unicode characters that are making realistic-for-lip-reading movements.
*(just another rabbit hole actually, Unicode got plenty of them already)
Re: I made a talking emoji using regular emojis and JavaScript
#14Earlier quoted context omitted.
You could actually propose a whole set of Unicode characters that are making realistic-for-lip-reading movements.
That would be a rabbit hole though, if you consider that Unicode isn't English or even Indo-European centric. *(just another rabbit hole actually, Unicode got plenty of them already)
Re: I made a talking emoji using regular emojis and JavaScript
#15Earlier quoted context omitted.
You could actually propose a whole set of Unicode characters that are making realistic-for-lip-reading movements.
That would be a rabbit hole though, if you consider that Unicode isn't English or even Indo-European centric. *(just another rabbit hole actually, Unicode got plenty of them already)
"text engine developers hate him"
Re: I made a talking emoji using regular emojis and JavaScript
#16> Instead iterating through every byte like ""[n] Pedantic note: JS iterates through UTF-16 2-byte code units. It's that way for compatibility reasons (used to be UCS-2), but it's the worst of both worlds: not as good as UTF-8 for ASCII, can't do operations in O(1) time like UTF-32.
Re: I made a talking emoji using regular emojis and JavaScript
#17I'm Deaf and read lips. Thanks for this extremely intriguing idea to use emoji to depict a talking person visually. You know, some animated films get it right. Sometimes I clearly see utterances like «Thank you!», «Okay», but more often not. Especially older animations don't care and just let the character move the mouth in very simplistic ways: «Babbabbabaa Baababba ba baaa.» Similarly for that emoji. It is moving t…
Re: I made a talking emoji using regular emojis and JavaScript
#18I'm Deaf and read lips. Thanks for this extremely intriguing idea to use emoji to depict a talking person visually. You know, some animated films get it right. Sometimes I clearly see utterances like «Thank you!», «Okay», but more often not. Especially older animations don't care and just let the character move the mouth in very simplistic ways: «Babbabbabaa Baababba ba baaa.» Similarly for that emoji. It is moving t…
You could actually propose a whole set of Unicode characters that are making realistic-for-lip-reading movements.
Re: I made a talking emoji using regular emojis and JavaScript
#19> Instead iterating through every byte like ""[n] Pedantic note: JS iterates through UTF-16 2-byte code units. It's that way for compatibility reasons (used to be UCS-2), but it's the worst of both worlds: not as good as UTF-8 for ASCII, can't do operations in O(1) time like UTF-32.
See https://mathiasbynens.be/notes/javascript-encoding for a discussion of the topic.
I’m perpetually sad that a couple of big players decided to go all in on UCS-2/UTF-16 when it should already have been apparent that UTF-8 was roughly uniformly superior and that UCS-2/UTF-16 would have major issues. (I speak as one who was a child at the time, but has read a fair bit about the state of things back then. So don’t trust my yearning optimism.)
The worst part about UTF-16 is how it poisoned Unicode with surrogate pairs. UTF-32 and UTF-8 are both good because they didn’t need any special consideration from Unicode to make them work. But UTF-16, extending UCS-2 as it does… ugh.
Re: I made a talking emoji using regular emojis and JavaScript
#20Earlier quoted context omitted.
Halfway through the article, he shows a picture with mouths for a-z, sh and th: https://cdn-images-1.medium.com/max/1600/0*gwbWfYm-iQIPEXXP%... There are others if you search images for "lip sync animation". It would be interesting to see if the result is understandable if you simply replace the emojis with those images.
Lipreading is different. For example the «sh» sound is made by slightly pursing the lips but not all speakers do this. In German it gives a very clear visual picture.
I agree that the mouth shapes are garbage in this demo. A shame because that is the most interesting & important part of animating speech.