KoljaB / RealtimeSTT

A robust, efficient, low-latency speech-to-text library with advanced voice activity detection, wake word activation and instant transcription.
MIT License
2.1k stars 191 forks source link

Syntax error line 520 audio_recorder.py #87

Open unmotivatedgene opened 4 months ago

unmotivatedgene commented 4 months ago

Updated to 0.2.0 and now getting this error. Tried reinstalling. I'm confused, doesn't look like there is an error to me. From pip, python 3.9.19

File "C:\Users\USERNAME\AgentComms\combined_server.py", line 20, in <module>   
    from RealtimeSTT import AudioToTextRecorder
  File "C:\Users\USERNAME\miniconda3\envs\myai\lib\site-packages\RealtimeSTT\__init__.py", line 1, in <module>
    from .audio_recorder import AudioToTextRecorder
  File "C:\Users\USERNAME\miniconda3\envs\myai\lib\site-packages\RealtimeSTT\audio_recorder.py", line 520
    match self.wakeword_backend:
          ^
SyntaxError: invalid syntax
KoljaB commented 4 months ago

Oh. v0.2.0 brings openwakeword and I thought it would be smart to use the "match" keywords. Wasn't aware that this apparently was introduced with Python 3.10. Will change soon and upgrade.

unmotivatedgene commented 4 months ago

Ah that maxes sense. Thanks.

Jul 19, 2024 2:27:16 PM Kolja Beigel @.***>:

Oh. v0.2.0 brings openwakeword and I thought it would be smart to use the "match" keywords. Wasn't aware that this apparently was introduced with Python 3.10. Will change soon and upgrade.

— Reply to this email directly, view it on GitHub[https://github.com/KoljaB/RealtimeSTT/issues/87#issuecomment-2239978934], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ADINRICLM5ZFDOCF2J3BZF3ZNFSBJAVCNFSM6AAAAABLE72FKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZZHE3TQOJTGQ]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/ADINRIGCBOYMVLE7W2EEJFDZNFSBJA5CNFSM6AAAAABLE72FKWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUFQNO3M.gif]

KoljaB commented 4 months ago

Should be fixed now with v0.2.1