Nice to hear something about development and the future but the online VTT feature for premium paying users which seems to be over one month at least in a non-working state will not even be mentioned directly. Great service attitude for you paying customers!
Reminder to myself:
Cloud plans are automatically renewed on an annual or monthly basis unless you cancel them in your account. Cancellation stops the next billing cycle but does not refund the current one.
Pl send in the details of the disabled service to the Helpdesk using the form at Contact Us. As paying customers let the helpdesk know about this.
The development focus is on offline development for the v4.2 release. This does not mean the online version has been abandoned. They will take it up after the offline related development and testing tasks are complete. If the service is not working as of now the helpdesk should be made aware of this problem.
2 Likes
Iām a paying customer
Service isnāt working as of now
Iām joining Doppel-D in the task of making them aware
Have a pleasant day
1 Like
The āproductā VTT doesnāt seem to have much user on eOSā¦.
1 Like
I received something totally useless from the helpdesk,
which Iāve replied to and Iām happy to share it here:
Hello,
As a paying customer, I feel totally gutted you're telling me this. At no point
did I raise any concerns as I understand how the current version is made and is
meant to work, when it does.
At the moment, it doesn't, while i've still been paying for it, but when it did it
was fine.
I am appalled that you aren't trying to provide a proper solution, I don't want or
care for your offline version, I want you to repair what I'm paying for.
Le 25/06/2026 16:54, Haydee Elizondo via Murena.com helpdesk a Ć©crit:
> Hello,
>
> Thank you for your feedback, and we're sorry for the frustration this issue has caused.
>
> First, we'd like to clarify that the current voice-to-text implementation
> is designed with strong privacy protections. Audio data is anonymized before
> processing, and there are safeguards in place to protect user privacy.
>
> That said, we have heard the feedback from our community, including the concerns
> raised in this thread. We understand that many users would prefer a solution
> that does not rely on server-side processing at all.
>
> For that reason, we are currently working on a new speech-to-text implementation
> that runs locally on the device, works offline, and does not require any server-
> based AI processing. This new solution is planned for release in /e/OS v4.1 or
> v4.2.
>
> We appreciate your patience while we complete this transition, and we thank you
> and other community members for continuing to share your feedback.
1 Like
I donāt know if this is artificially intelligence or some stupid boiler plate ;- ) Thank you that you take the labour to askā¦I probably thought it would be uselessā¦..and I was right :- )
But at least the network team is on it ā¦or isnāt it?
I just received an email claiming they fixed it and they actually did because I am voice typing this 
So that was far from useless Thanks guys.
Hello Pierric,
Youāre right, and I apologize, my previous reply focused on the long-term roadmap instead of addressing the fact that the feature youāre paying for is broken right now. That wasnāt the right response to your issue.
Good news: our technical team identified the root cause of this specific bug. It turned out to be a server-side compatibility issue (the voice-to-text backend was using an older protocol that had been deprecated upstream), and a fix has just been deployed on our end.
Could you please try voice-to-text again now and let us know if itās working for you? If itās still not working, please let us know and weāll keep investigating on our side, this would no longer be a āwait for the futureā answer, but an active bug weāre tracking until itās resolved.
Thank you for your patience, and again, apologies for the earlier mismatched response.
Best regards,
Haydee Elizondo
Murena Customer Support
3 Likes
I still find this a bit irritating as this happened already on 18 May and didnāt helped a bit to solve the problemā¦and that there were no indicators inside the network team about a non-functional state of the service.
This topic was automatically closed after 90 days. New replies are no longer allowed.