Voice Recognition

RobotChickens

han614698 wrote:
(#257)
RobotChickens wrote:
undeterminstic wrote:
(#245)
no support unless cloud variables are disabled during it
I can't see why this would be an issue! The only output from these blocks would be text. People would in no way have access to the sounds from the microphone. I don't think disabling Cloud Variables would be necessary. I think people are misunderstanding how this extension works.

1. You tell the extension to listen.
2. You say something.
3. That audio is sent to Google's servers for processing just like all other voice-enabled features on many platforms.
4. The output variable gives you the processed text version of what you said.

The only thing this extension can output is text. You can't do any more with this than what you could with a keyboard. No blocks are able to give you access to the un-processed audio recordings… It's only text.
It could possibly be listening when the user isn't aware.

That's what the huge red microphone icon is for. Go check it out on the github!

DangerPuppy10 wrote:
(#259)
No support, this could hide project features from others. For example, if you have a friend, and you're making a game. And you want that friend to be able to play the game, but NOBODY else. You can use voice recognition to hide it.

This desn't recognize voices and who they're from. This just turns speech into text! Basically the reveres of text to speech.

Last edited by RobotChickens (April 9, 2024 03:57:40)

RobotChickens

medians wrote:
(#258)
-snip-
I stated that and already know that (for the text in cloud vars), but people could turn the speech into numbers, it has been done before for other things too and for cloud lists.

I'm pretty sure encoding any user-generated text onto cloud variables using numbers is banned no matter what. Cloud chat isn't allowed, and that's that. Now, does the fact that the text comes from an extension change anything? How is someone speaking text into a cloud variable different from someone typing it? It's all numbers and plaintext on the cloud either way, so what's the difference? Should cloud variables be banned on projects with the “Ask ( ) and wait” block too? Blocking cloud variables on projects with this extension won't stop people from attempting to make cloud chat projects.

thunderclwd

RobotChickens wrote:
han614698 wrote:
(#257)
RobotChickens wrote:
undeterminstic wrote:
(#245)
no support unless cloud variables are disabled during it
I can't see why this would be an issue! The only output from these blocks would be text. People would in no way have access to the sounds from the microphone. I don't think disabling Cloud Variables would be necessary. I think people are misunderstanding how this extension works.

1. You tell the extension to listen.
2. You say something.
3. That audio is sent to Google's servers for processing just like all other voice-enabled features on many platforms.
4. The output variable gives you the processed text version of what you said.

The only thing this extension can output is text. You can't do any more with this than what you could with a keyboard. No blocks are able to give you access to the un-processed audio recordings… It's only text.
It could possibly be listening when the user isn't aware.
That's what the huge red microphone icon is for. Go check it out on the github!
DangerPuppy10 wrote:
(#259)
No support, this could hide project features from others. For example, if you have a friend, and you're making a game. And you want that friend to be able to play the game, but NOBODY else. You can use voice recognition to hide it.
This desn't recognize voices and who they're from. This just turns speech into text! Basically the reveres of text to speech.

That's not what I'm supporting.
I'm want the extension to check for the volume of voice. I made a topic similar but not exact to this on and I was told to come here, But I think I'm the only one who wants the extension to check for volume. There's a volume block for in-game noises, why not for Our speech?

MousePotato1234

scootyboy-2010 wrote:
nickeljorn wrote:
No support, this invades users' privacy.
No, it doesn't, because anything said can't be uploaded anywhere because variables only support numbers.

But you can encode a value, store it in a cloud variable, and then subsequently decode it, thus making what is effectively an alphabet-supporting cloud variable in Scratch.

thunderclwd

MousePotato1234 wrote:
scootyboy-2010 wrote:
nickeljorn wrote:
No support, this invades users' privacy.
No, it doesn't, because anything said can't be uploaded anywhere because variables only support numbers.
But you can encode a value, store it in a cloud variable, and then subsequently decode it, thus making what is effectively an alphabet-supporting cloud variable in Scratch.

Just make cloud variables not work with it. Also, with my volume idea, this isn't even problem, as it only detects volume

RobotChickens

MousePotato1234 wrote:
(#265)
scootyboy-2010 wrote:
nickeljorn wrote:
No support, this invades users' privacy.
No, it doesn't, because anything said can't be uploaded anywhere because variables only support numbers.
But you can encode a value, store it in a cloud variable, and then subsequently decode it, thus making what is effectively an alphabet-supporting cloud variable in Scratch.

What does speech to text have to do with this? People can do this without speech to text.

-hexacactus-

they would use another company's premade one like how they use Amazon's text to speech and Google Translate

orangeluigi

Complete support! Wasn't this already going to be added in Scratch 3.0?

BladiPetrov

nickeljorn wrote:
No support, this invades users' privacy.

literally say jwhat now

medians

orangeluigi wrote:
Complete support! Wasn't this already going to be added in Scratch 3.0?

I think it was, I feel like I remember there being a “Speech to Text” extension in the gallery but I believe it was removed before 3.0 released.

Scratchedbyyou

Only if cloud variables are disabled, because someone could use them to invade privacy V

encode (words said::pen)::custom
set [☁ Cloud v] to (encoded)
:://then
decode (☁ Cloud)::custom

RobotChickens

Scratchedbyyou wrote:
(#272)
Only if cloud variables are disabled, because someone could use them to invade privacy V
-snip-

We've already established that it won't be an issue. The extension only outputs plaintext. It's the EXACT same situation as this:

ask [Enter text] and wait
encode (answer)::custom
set [☁ Cloud v] to (encoded)
:://then
decode (☁ Cloud)::custom

If cloud is blocked on this extension, then it should also be blocked for the “Ask (…) and wait” block too.

100blacktak

Scratch team, unfortunately, did not add this feature due to safety issues. There's nothing you can do about it, sorry

RobotChickens

100blacktak wrote:
(#274)
Scratch team, unfortunately, did not add this feature due to safety issues. There's nothing you can do about it, sorry

The ST hasn't done anything about it yet… If this suggestion was rejected, rhis topic wouldn't exist!

Scratchedbyyou

RobotChickens wrote:
Scratchedbyyou wrote:
(#272)
Only if cloud variables are disabled, because someone could use them to invade privacy V
-snip-
We've already established that it won't be an issue. The extension only outputs plaintext. It's the EXACT same situation as this:
ask [Enter text] and wait
encode (answer)::custom
set [☁ Cloud v] to (encoded)
:://then
decode (☁ Cloud)::custom
If cloud is blocked on this extension, then it should also be blocked for the “Ask (…) and wait” block too.

Ask is different. It won't listen in on conversations unless you type it in there on purpose.

RobotChickens

Scratchedbyyou wrote:
(#276)
RobotChickens wrote:
Scratchedbyyou wrote:
(#272)
Only if cloud variables are disabled, because someone could use them to invade privacy V
-snip-
We've already established that it won't be an issue. The extension only outputs plaintext. It's the EXACT same situation as this:
ask [Enter text] and wait
encode (answer)::custom
set [☁ Cloud v] to (encoded)
:://then
decode (☁ Cloud)::custom
If cloud is blocked on this extension, then it should also be blocked for the “Ask (…) and wait” block too.
Ask is different. It won't listen in on conversations unless you type it in there on purpose.

Ah, I see what you mean now. If you test out the Scratch 3 beta, you can see a massive red microphone icon in the corner of that stage that lets you know the project is using the microphone. And I'm assuming there would have to be a popup asking if you want to start STT, so no project can start it without users knowing.

julmik6478

Some os'es have they own speech regonizion system, so scratch team don't need to make scratch one.

RobotChickens

julmik6478 wrote:
(#278)
Some os'es have they own speech regonizion system, so scratch team don't need to make scratch one.

Exactly! I'm pretty sure the ST was planning to use the Google's STT but imbedded inside the editor blocks so it's easier to put into projects.

PaperMarioFan2022

bumping because of a dupe

MousePotato1234

RobotChickens wrote:
MousePotato1234 wrote:
(#265)
scootyboy-2010 wrote:
nickeljorn wrote:
No support, this invades users' privacy.
No, it doesn't, because anything said can't be uploaded anywhere because variables only support numbers.
But you can encode a value, store it in a cloud variable, and then subsequently decode it, thus making what is effectively an alphabet-supporting cloud variable in Scratch.
What does speech to text have to do with this? People can do this without speech to text.

What I'm saying is that you could take the results of what the speech to text engine comes up with, encode it, send it over the cloud variable, and decode it on the other end.

Discuss Scratch