Most active commenters

    ←back to thread

    164 points thunderbong | 14 comments | | HN request time: 0.36s | source | bottom
    1. Retr0id ◴[] No.41855110[source]
    Does what it says on the tin, but honestly I find the "uncorrected" video more comfortable to watch.
    replies(4): >>41855157 #>>41855165 #>>41855566 #>>41855574 #
    2. karlgkk ◴[] No.41855157[source]
    There are other implementations that do a better job, such as Apple and Google's. They also are less willing to correct eye contact when it's "out of range" so to speak.
    3. hanniabu ◴[] No.41855165[source]
    I think it's the lack of subtle movement, it's too strict and really locks the pupils front and center
    replies(1): >>41857233 #
    4. ddfs123 ◴[] No.41855566[source]
    I think it's just that naturally nobody is keeping 100% eye contact ( except maybe like TV news reporter ), it feels like an interrogation.
    replies(1): >>41855577 #
    5. mvoodarla ◴[] No.41855574[source]
    Original dev here. I tend to agree for this particular demo video as I'm reading a book and I don't blink in the original.

    The model tries to copy the blinks of the original video so it's possible that in other conditions, you'd notice less of this.

    Fun to see this feedback though, definitely something worth improving :)

    replies(2): >>41855613 #>>41855702 #
    6. XorNot ◴[] No.41855577[source]
    This is what I realized is uncomfortable about camera on group meetings in teams - I can't mute other people's video, and so it feels intensely weird to have a wall of people staring blankly at you.
    replies(3): >>41855669 #>>41856615 #>>41857766 #
    7. mlhpdx ◴[] No.41855613[source]
    I likewise find the “corrections” uncanny. It’s not just the one with the book.
    8. RheingoldRiver ◴[] No.41855669{3}[source]
    > I can't mute other people's video

    you can switch to another tab, use a miniplayer, in some apps u can focus one person's screen and if you choose someone who has a static avatar up you'll barely see other people's faces.

    The nuclear option is to install PowerToys [0] and put something always on top (im a fan of the hotkey winkey+space to toggle always-on-top on and off) in the exact position of the other video feeds. notepad or something.

    [0] https://learn.microsoft.com/en-us/windows/powertoys/

    9. patrickhogan1 ◴[] No.41855702[source]
    BTW your main site is throwing an error. Probably want to edit since your post is growing.

    https://www.sievedata.com/

    Application error: a client-side exception has occurred (see the browser console for more information).

    replies(1): >>41855746 #
    10. mvoodarla ◴[] No.41855746{3}[source]
    Original dev here. Unable to replicate this on my end, try refreshing?
    replies(1): >>41861204 #
    11. abdullahkhalids ◴[] No.41856615{3}[source]
    This has been a feature since 2020 [1]. Similarly exists in zoom now.

    [1] https://answers.microsoft.com/en-us/msteams/forum/all/featur...

    12. lloeki ◴[] No.41857233[source]
    You mean frequent saccades?

    https://en.wikipedia.org/wiki/File:This_shows_a_recording_of...

    or the occasional look away? (for which there appears to be a feature for that)

    > Look Away: enable_look_away helps create a more natural look by allowing the eyes to look away randomly from the camera when speaking

    I expect both to be different: while saccades do happen when occasionally looking _away_ from a person, they also happen when looking _directly at_ one person because we don't constantly stare at a very specific unique and precise point on their face.

    For the demo video, try enable_look_away = true, look_away_offset_max = 10, look_away_interval_min = 1 and look_away_interval_range = 1 (then submit), which from the result I got should really be the default for a more natural result.

    13. prmoustache ◴[] No.41857766{3}[source]
    You can totally turn off incoming video on msteams. What you can't is have it as a default setting afaik.
    14. patrickhogan1 ◴[] No.41861204{4}[source]
    Interesting. The issue occurs because I have WebGL disabled, causing the createShader function you're using to throw an error. You can reproduce this by going to chrome://settings, disabling "Use hardware acceleration when available," refreshing the page, and then triggering the same error.