-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pls add support for gnome shell 45 🙏 #1
Comments
Yeah, the breaking changes of version 45. |
Hi @distBit, in regards to issue #1, please, feel free to try the dedicated code for version 45 of the GNOME shell. |
Hmm it now installs however the icon remains yellow once I trigger it with ctrl+alt+z and does not go back to white. maybe it is because my environment is noisy. I ended up writing my own utility for this in the interim though 😅 So I am afraid that at least for the time being I will not be using this extension, although maybe will return to it if it exceeds the usefulness of my script :) Many thx |
Thanks for checking it out. For the sake of convenience and minimum input device interaction, I settled for the built-in VAD (or silence detection) method in sox. So noise has been in the disclaimer from the get go. |
Looks like the problem might just be that I do not have wsi installed:
Btw I personally much prefer being able to specify when the recording is finished via pressing the same keyboard shortcit I used to start the recording, rather than having the recording automatically end upon detection of silence. This is the way my above linked utility works. The reason for this preference is that very often I want to pause and think when I am speaking, just as I often do when I am typing. So I do not want the recording to automatically end when I stop to think, as this forces me to speak even when I have not fully decided what to say, which is a significant UX issue, for me at least. |
Yes, wsi must be installed, it does the mediation in the background. It is amazing how lean, fast and well behaved command-line tools (especially shell built-ins) are in comparison to GUI widgets. So yeah, you need that script. (It also gets rid of non-speech events in the transcribed text, such as [wind blowing] etc.) In principle, I can pass along kill signals from Gio.subprocess to the underlying shell (bash or zsh) so the UI can be reworked to allow start/stop control. My desktop environment is quiet and it seems my webcam microphone is of a decent quality because the silence detection just works. I do prefer the minimal interaction with input devices, but I understand your preference too. |
I get this in 45
|
Hi @jalberto. It seems to be the same error as above, so I would like to ask you if you followed the installation instructions and placed the script wsi from this repo into $HOME/.local/bin/? The async function seems to fail due to the absence of that script. |
yes, I have both: `wsi` and `transcribe`, both with exec permissions.
If I run `wsi` from cli, it works as expected
Thanks for your time!
…On Fri, 9 Feb 2024 at 17:06, QuantiusBenignus ***@***.***> wrote:
It seems to be the same error as above, so I would like to ask you if you
followed the installation instructions and placed the script *wsi* from
this repo into $HOME/.local/bin/? The async function seems to fail due to
the absence of that script.
Please, confirm.
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAYMV5EAVUBNPDCRI7MAFTYSZCPXAVCNFSM6AAAAABC4OBDAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWGE4TEOBRGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi @jalberto . The only way I could reproduce the exact same error, was as expected when I made the wsi script return a code 1.
If you answer Yes to 1 (where CLI is a terminal window in GNOME). Then for now, I have no idea what it could be because wsi clearly exits gracefully and Gio should return success. Try replacing all relative paths with absolute ones in wsi. Any thoughts? |
I have attempted to manually install despite not being able to from https://extensions.gnome.org/ however encountered the following error when running gnome-extensions prefs blurt@quantiusbenignus.local
The settings of extension blurt@quantiusbenignus.local had an error:
I am running fedora 39.
many thx
The text was updated successfully, but these errors were encountered: