What's new:
Documentation:
Streamlined documentation.
Simplified instructions.
Gave clear instructions on PowerShell.

The complete Lemonbalm package has just been compiled and is ready for use! Find out more at: https://t.me/VisionBeyondLimits

Hello everyone! This is Ronan and today I want to talk about so called accessibility groups that limit access.
As you all here know, yesterday I compiled the complete Lemonbalm package with all the 6 languages supported by Google.
First of all, we need to talk Lemonbalm:
Lemonbalm, while being a trademark of Google, is part of GoogleTTS, which is free text to speech.
While UI hidden, it is all there, in plane text file, available to download for anyone who uses a web browser.
If Google wanted to restrict Lemonbalm only in it's use cases, than they would've used their infrastructure and coding knowledge to secure the files, the endpoint, and the download server to only authorize GoogleTTS or GMS itself to download the packages, and, even better, lock the links to the files in pure binary or smali.
Instead, their schema looks like this:
{
"compressed_size": 11624764,
"download_packing_scheme": "zvoice",
"download_urls": [
"https://dl.google.com/android/tts/v26/en-us/en-us-x-news-lemonbalm-r83.zvoice",
"https://redirector.gvt1.com/edgedl/android/tts/v26/en-us/en-us-x-news-lemonbalm-r83.zvoice"
],
"name": "en-us-x-news-lemonbalm-r83",
"revision": 83,
"sha256_checksum": "772a749adc31644620a6b0ac4e671cbebc49901529c015ae1abbe1e1adbc3796",
"validation_schemes": [
"sha256"
],
"verify_sizes": false
},

What do we see while looking at the code I just pasted?
JSON schema, available in plane text, in the assets folder of GoogleTTS itself, or in /data/user/0/com.google.android.tts/files/superpacks_manifest.json even, in case you're looking at it on an Android device.
It's discoverable easi, either with root or, even better, by using Android Studio's decompile debug, apktul, or JEB decompiler.
The idea from this?
While a little harder to acces than usual GoogleTTS solutions available in the front-end side of GoogleTTS, Google let this path open, even though they have one of the largest infra and are the creators of Android's own encryption files.
Hard to access? Yes. Not permitted? No.

Despite realizing and knowing this themselves, some accessibility groups which I won't name, wiped clean all of our attempts into sharing Lemonbalm with the world, despite people in their groups already finding interest to try out the engine.
They're doing this under the pretext that they want to control what their users see to protect them from possible piracy or cracking.
This is unfair, in my point of view.
The subscribers to a group are people with anticipation, with brains, with a working mind, not robots, AIs, or devices that need to be given if/else instructions.
People can make their own decisions, people can choose.
It's their choice and they're capable of discerning for keeping/releaasing.
None of my communities do support piracy or cracking, and never did you see us crack something in any or communities, or allowing someone discuss cracking.
Blocking access to the best text to speech technology, however, just because it may be seen by some as cracking isn't the way to go, and not what we should do if our goal and mission is accessibility.
Accessibility means gainning access.
If we're deleting entire message histories, then how will people even know it exists?
This is, in fact, the biggest issue with this.
My problem isn't the fact I wasn't heard, tmy problem is the fact that nobody even knows.
And that's starkingly painful.

In conclusion:
Are you a developer that has worked on an amazing project and you solve an issue or give a quality option?
Don't share your findings, development, or service to either accessible android or blind android users!
They're allowing access to their own things and their limited resources, not welcoming software or services that make the difference.
If you want it to reach people, share it in private to those who can spread the word. Accessible groups where entire messages and histories are curated shouldn't be given the keys to amazing breakthrough tech, I've realized. And that's stark.

HyperTTS!
What's new?
The entire newest platform tools .EXE and .DLL files included in the archive
A setup.bat file that will:
*Set the HyperTTS-Source as a system path environment variable
*Setup a scheduled task that runs adb devices after log on
*Then it runs the script that registers the DLLs.
Improved the DLL registering script with administrative privileges and actual checks if the files were registered.
Updated documentation to reflect the new changes.
Enjoy!
RoApps

Another publication called JumpingFridgeFoundation have created a TTS solution for NVDA, called PureTTS, that trys to mimmic HyperTTS's abilities through NVDA.
This implementation has been advertized on their website without propper credit to RoApps as an inspiration source. This announcement is both if you want to check out the tool, but at the same time a call to action for JumpingFridgeFoundation to credit RoApps.
While we encourage creativity, we do not allow our tools to be coppied and kanged without credit, we do not agree that a TTS solution should be used soly for a screen reader, and, the interface of the app being writen in node.js means it cannot be expanded like HyperTTS to actually implement speaking to Android, and other possibilities. We will showcase the tool here, but our recommendation:
HyperTTS isn't an NVDA add-on. It is a SAPI compatible interface which allows any app, no matter what app it is, speak with your Android voices if it can speak through SAPI.
Gatekeeping solutions to a platform or a screen reader solution is the reason why this announcement and call to action has been rizen.
@JumpingFridgeFoundation, please credit RoApps and edit your post as soon as possible!

Heads up and update:
After direct further contact with Notex, the lead programmer at JFF, waters have been cleared and things have been arranged.
Thank you for your understanding!

Google TTS Locomel, only compatible with TalkBack. Contains Australian and British English, French, German, and Spanish United States. English United States does also exist, but apparently it's strange and I couldn't get the voices to talk. I'll be posting in here a ZIP with all the U.S. packages currently available, after which, if anyone of you can get the U.S. voices to talk it'd be amazing. Enjoy these voices though, they're fast and responsive, although quality suffers: Their unit selection is stupid kinda and they sound rather rushed up. You'll see if you like them. I'll be posting next the U.S. voice pack. The one with these voices is Locomel R83.

This is the whole EN-US folder in my GoogleTTS voice data. Our goall is to make MultiTTS accept the voices from EN-US-X-Locomel-R83, but whenever I import them, it speaks with those from simple Multi. Is there any way I can choose which of the voices actually speak? It works for all the other languages. The catch is, Multi needs to be there, because it provides necessary files for Locomel to speak.
So, let's work together and make Locomel speak. All the other languages worked, again, by simply putting all the files in just like what I did with U.S. Yet the U.S. voices don't want to speak for some reason. To all the advanced people in my communities and across the MultiTTS community, what should we do?

Do you have music on your computer and want to delete it to save space? Would you rather transfer your songs from your computer to playlists in your favorite digital streamming service? Catalog My Music is here for you! This simple program scans your given music folder for tracks and creates two reports on what tracks it's found: A simple report that includes artist name and song name, and an extended report which includes all the details FFMProbe can discover about a song, plus audio spec, plus aditional information. Enjoy and we hope this program serves you well!

Hello everyone! This is Ronan from RoApps!
If you were to, say, talk to a three years ago version of me that worked before he knew about Google Lemonbalm and you would tell that old Ronan that obsession can get them so high, he would probably laugh at you and dismiss you. But now, after more than 2 years of using Lemonbalm voices day by day on all of my Android devices, I must say we came so far. All of our TTS innovations happened because of this amazing, incredible neural embedded TTS architecture that stole our mind here at RoApps.
Our first TTS tool, HyperTTS, a well regarded hit in it's own right, happened because we wanted Lemonbalm to step out from the Android scene and reach a new, seemingly forgotten platform baked by paid useless TTS engines that cost as much as flour for bread for more than half a year, enough to feed an entire family.
That may not seem like a lot thinking you're paying lifetime, but trust me! It is once you know that the TTS engine you're paying for is not even good at doing it's job, reading the text from the screen properly. Moreover, knowing that there's something way better out there that is available for free, to anyone makes these TTS solutions even more worthless.
This is what made us bring HyperTTS. An unified mission and wish for everyone to have the best possible, no matter the platform they use. Sure, for now the service is not this enhanced and expanded, but this was it's vision, and it will become true!
More recently, though, we completed the circle and released our own third party GoogleTTS player. Optimized for speed, performance, and lag reduction, GoogleTTS Player does not play it safe! It ensures your TTS speaks as fast as your phone can allow. All these innovations happened because of a single reason: Lemonbalm. And we want to thank Google for offering such an amazing and developed TTS architecture.
Our mission continues, though. One of us at RoApps recently got access to an IOS device. Our next objective? Make GoogleTTS Player and HyperTTS, if possible, available to the IWorld.
With help from amazing people like you, no matter if it's developers or just users, we want to bring the amazingness of Lemonbalm to as much of the IWorld as we possibly can.
Thank you for supporting us until the end, and we hope to see you, using GoogleTTS, on your IDevice soon!

You guys! Something very, very big will be coming up in the near future. Stay tuned!

There's been a reality circling around the blind community ever since 2018 when Telegram started gainning traction: Telegram on IOS couldn't be welcome by screen reader users. We, at RoApps, don't just checklist for "Basic Accessibility" to make sure our app passes a standard and let our users go "Button" "Button" "Button" everywhere or, even worse, present a blank screen or inaccessible controls. We at RoApps use screen readers, envision and picture the life of a screen reader user whenever we design a user interface, app or new screen.
With these high standards in mind, Gruia Chiscop, one of the RoApps aware developers, has just released Swift-TG on the Apple app testing platform, Testflight.
Swift-TG means to make Telegram accessible for screen reader users, while at the same time being a feature rich client that unlocks functionality not only for the blind, but also for the sighted. Although for right now, Gruia is working on completing the basic Telegram functions, the app is mostly complete. With calls, channel and topic support, repplies and accessibility actions, and more. Some of Telegram's settings are also available in the "You" tab, so not even those are missing. The app is amazing, very good for a daily driver, and makes for an amazing Telegram experience. Join the TestFlight beta program, report and suggest without entitlement if possible, and help make the app better for everyone.A true recommandation from the bottom of our heart. Swift-TG truly allows the blindto experience a Telegram vision beyond limits! Gruia hopes he will be able to satisfy not only the blind though. So no matter if you see or not, join the program, install the app, test away and suggest! Community brings the strongest force in a project, enjoy and let's rejoice! Telegram Accessibility is now complete! Last to join, the IWorld!
https://testflight.apple.com/join/srB5s8Ta