The Google Maps app for Android has, for years now, had the same old voice input that’s slow and not as accurate as Google’s latest offerings. Finally that’s changing, as Google Maps is rolling out a new voice input experience powered by Google Assistant.

  • eggshappedegg@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 year ago

    All of my Google home (nest) speakers have gotten worse for every moth that passes. They understand less and less for every time and often even just ignore me (even though LED register input). I’m removing them all because from what I’ve experienced they’re programmed to break just about a year past the warranty. I’m not replacing all of my nests every 2-3 years. I’ll just press that light switch myself instead like in the old days

    • sloonark@lemm.ee
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      > for every moth that passes

      This is such a cool typo. I love the mental image.

    • yourdogsnipples@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      The ability of my Google Home gadgets to correctly understand speech drops sharply whenever there’s a promo on them - I imagine the influx of new speech patterns from new users tanks the recognition/parsing systems at Google.

  • Moonrise2473@feddit.it
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    > not as accurate as the latest offerings

    Maybe the opposite? Ten years ago it understood everything, now it’s a 80% chance of “sorry, I didn’t understand”

    • XTornado
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Could have been a patent issue or some weird shit?

      Like I think Apple for example had some headphones that did a super awesome noise cancellation but suddenly in a update it got worse and it was although not sure if publically confirmed to the fact it was breaking some patent and they had to introduce workarounds.

      • Moonrise2473@feddit.it
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        No, because if you go on history.google.com you can see what you said, and often it shows exactly what you said. Probably they want to make it look smarter to have some hard coded smart responses instead of just reading a summary of a Google search, but it fails miserably all the times

        • ayyndrew@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Yeah the issue isn’t the voice recognition, from what I can tell that has only gotten better and is really great on my Pixel 6 Pro, it’s how Assistant interprets the commands that has degraded

  • ElPussyKangaroo@lemdro.id
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    How does Google have 4 different Voice Input technologies for essentially the same product?!

    The Gboard uses the new Speech Services. But Assistant uses a better thing… Which is slow at times. But there’s still many Google apps using the old shitty Speech utility. And then there’s YouTube. Goddamn.

  • limecool
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    For some reason Youtube does the fastest and the most accurate voice recognition compared to the offline google Speech to Text. If they want to improve. Implement that in the Speech to Text app.