Comments (8)
@beccasaurus gentle ping!
from nodejs-speech.
@blerest
When you get the END_OF_SINGLE_UTTERANCE event, are you then calling stream.end()
?
That's what I'm doing and it works fine... but you still have to keep listening for the "data" event from the stream itself, which should give you the final data
event with isFinal:true
. Then you'll also get an end
event, at which time you can "unlisten" from the stream events: data, error, and end.
From docs:
`
END_OF_SINGLE_UTTERANCE | This event indicates that the server has detected the end of the user's speech utterance and expects no additional speech. Therefore, the server will not process additional audio (although it may subsequently return additional results). The client should stop sending additional audio data, half-close the gRPC connection, and wait for any additional results until the server closes the gRPC connection. This event is only sent if single_utterance was set to true, and is not used otherwise. |
---|
`
from nodejs-speech.
I have the same issue but not only when I'm saying one word. Sometimes it happens while long recognition. I'm using confidence result in my app every time when I receive isFinial=true. But sometimes while long recognition I receive END_OF_SINGLE_UTTERANCE and I cannot use confidence because it always returns only with isFinal=true. And this is really important thing in my app.
Can you return confidence value even if I'm receiving END_OF_SINGLE_UTTERANCE or while interim results?
from nodejs-speech.
I still have issue. Do you have information?
from nodejs-speech.
How about restart the service every single minute
from nodejs-speech.
Just saw this get bumped. Following up on this, will report back.
from nodejs-speech.
Has this issue ever been resolved , @blerest ... I have a similar issues of time , I have noticed the same issue where the commands is on only final after an a new world or sound has been registered between the utterances.
from nodejs-speech.
+1 to what @kidplug said.
Also tried this myself and got:
# First result is a interim result
results {
alternatives {
transcript: "check"
}
stability: 0.009999999776482582
result_end_time {
nanos: 940000000
}
}
# Second result is a interim result
results {
alternatives {
transcript: "check"
}
stability: 0.8999999761581421
result_end_time {
seconds: 1
nanos: 510000000
}
}
# Speech api detects the end of my utterance
speech_event_type: END_OF_SINGLE_UTTERANCE
# Speech api returns is_final=true
results {
alternatives {
transcript: "check"
confidence: 0.9628270864486694
}
is_final: true
result_end_time {
seconds: 3
nanos: 670000000
}
}
If anyone is still having an issue, please comment again here and I'll try to reproduce. But I'm going to close this for now.
from nodejs-speech.
Related Issues (20)
- BetaFeatures: should run speech diarization on a GCS file failed
- BetaFeatures: should run multi channel transcription on a local file failed
- BetaFeatures: should run multi channel transcription on GCS file failed
- BetaFeatures: should transcribe multi-language on a local file failed
- BetaFeatures: should run word Level Confience on a local file failed
- Speech-to-Text export to Cloud Storage : should export transcriptions failed
- Speech-to-Text export to Cloud Storage : "after all" hook: should delete the bucket used for the test for "should export transcriptions" failed
- modelAdaptation: should run modelAdaptation failed
- modelAdaptation: "after all" hook for "should run modelAdaptation" failed
- multiRegion: should run multiRegion failed
- profanityFilter: should run profanityFilter failed
- Quickstart: should run quickstart failed
- Recognize: "before all" hook for "should run sync recognize" failed
- Recognize: "after all" hook for "should run speech diarization on a local file" failed
- Recognize v1p1beta1: should run sync recognize with metadata failed
- transcribe context classes: should detect transcriptions failed HOT 1
- Warning: a recent release failed
- SpeechClient system test v1: calls longRunningRecognize failed HOT 1
- SpeechClient system test v1p1beta1: calls recognize failed HOT 1
- SpeechClient TypeScript system test v1: calls longRunningRecognize failed HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nodejs-speech.