How to build simple speech recognition app in the new Thunkable layout

Hi community,

I’m very new to Thunkable and I’m struggling to use the speech recognition capability in the new Thunkable layout. I want to build a simple app, where:

  • User can click on a button which triggers speech recognition to start
  • When users speech included the word “left” → a previously hidden left label appears
  • When users speech included the word “right” → a previously hidden right label appears

Now of course I tried to look for example apps, tutorials etc. using Speech recognition, but I could only find implementations using the “Speech recogniser” voice blocks in the old layout. In the new layout I can only find a block called “recognised speech in …”, but no example apps or tutorials on how to use it. And I’m struggling to figure it out by myself.

If anyone could point me in the right direction, I would be very thankful :slight_smile: . Many thanks in advance!

1 Like

Recognize Speech

Recognize a piece of audio in a given language. Returns a text transcription of the speech.

My Speech recognition app in New UI
圖片

I tried to make voice commands work and couldn’t. Maybe you’ll have success but I couldn’t find a way. You can right-click on some of the blocks to toggle advanced options. The documentation is limited but available here:

https://docs.thunkable.com/v/drag-and-drop/speech#recognize-speech

1 Like

Hi @tony.ycy.program , many thanks for posting your solution.

I tried to implement it exactly as you did, but it seems not to work for me: Thunkable

Problem is, that when I press the Start button, nothing happens (both in preview and Thunkable Live). Do you have any ideas what could be the problem? Or do you have a link to your solution for me to test your solution on my phone?

Yeah, it’s not work!
BUT First test(1st open) It can show

Hi @tony.ycy.program ,

many thanks for your reply. After your message I retested and you are right. It seems to work for the first open attempt and when I speak directly in the microphone. Then it seems to capture the first 2 seconds. So have many thanks for your help, your solution solved it.

However, as a feedback for the Thunkable team I want to mention that the quality of the speech recogniser is so bad, that it not or only barely usable (at least for me):

  • It only works on 1st open attempt of the app
  • I need to speak directly into the microphone
  • It only records the first 2 seconds maximum
  • And even then it only worked like 50% of the time for me.
3 Likes

This is my experience too has anyone found a solution to it?
It only works once, then I have to actually kill the ios app and reload it for it to work again.

Please post a link to a project that demonstrates this issue.

A link to demonstrate that it doesn’t work? Isn’t it a known bug? I have multiple students trying it and it’s the same thing. It only works the first time you run it on the phone and then you have to kill the app before speech recognition will work again.
Here’s a link on screen 1 of this test app
https://x.thunkable.com/copy/c644bec6708ee86fc05b7a129ccfda88

What max.breitspf said back in April still stands, the issue hasn’t been resolved.

It’s your first post on the forums and we get all flavors of users… some are very young kids, some are retired professionals… it’s hard to know what you’ve tried, etc. when details like that aren’t provided. People often write “I’m having the same problem” but when they show their blocks/project, it’s quite different than what was explained earlier in the topic.

But I can confirm that the speech recognition only works once in your project. If I Live Test on an iPhone, it recognizes and displays the speech once. But after that, it seems to ignore the event. I even tried it with the advanced version of the block and it failed similarly and did not display an error nor speech results.

I would recommend submitting a bug report even though it’s been documented here. You can link to this topic/post.

1 Like

Did this ever get resolved?

It doesn’t look like it but it was reported as a bug:

1 Like