@Tamasg I can already think of suggestions, but this is super awesome that it has finally happened. I will tell you you do have to adjust your speed inj the general tts aria. they don't ahve a speed thing yet in the actual app, and I had to put it at 78 percent just to get it at almoost a normal rate, but like I said, this is alpha. I am sure there will be lots of changes being made kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkksoon.
@JamminJerry lol as bad as it is, it's making me wonder if we could get it ported on iOS too just as we have the ESpeak one, but it's an entirely different beast there and Android needed more of the TTS options with as stale as some of the engines were going.
@Tamasg @JamminJerry And with Optispeech in development, we'll have a better, definitely more future-proof alternative to Vocalizer for those seaking a human-like speech engine that's actually responsive.
@JamminJerry oh noooo. If you have ADB access to the phone by chance you might be able to remove the package via the PM command and then it should revert your TTS to the default installed one
@Tamasg oh boy! I think I might have found a phone that the dec-talk doesn't like. lol. just tried to change from google tts to dec-talk on the smart vision 3, and it is like the whole phone froze. lol. touch screen isn't working, and even the arrow keys are not working at all either. woopsy! lol.
@JamminJerry oof yeah, that's quite a pickle to be in right there. Sometimes I've "blindly" tapped the bottom right corner of my screen which accepted it, but it's such a hit or miss type situation then.
@JamminJerry hmm. You'd first need to find the exact package name (unless Jack knows this) - type: adb shell pm list packages | grep "micro" Then you can do an adb uninstall with that package name after words.
@JamminJerry well, the "grep" part there at the end filters through for you, so in theory it should only show packages that have the word micro in their name. You can play around if nothing comes up with other names like "dectalk" in case the package name isn't exact.
ah darn. that's right, it's windows being Windows. you'll have to separate them (so do adb shell first, then hit enter, and the other part of the command after) You can just type exit after to go back to the command prompt and do adb unstall like normal with that package name.
@Tamasg oh dear. I think something really broke. I just tried pressing and holding the volume keys to get talkback on, and I got a notification sound, but still no talkback. oh boy.
@JamminJerry wow hmm. Maybe it needs a full reboot? In theory it should revert you to the last enabled TTS (or a default one like Pico / Google TTS if those came with the system)
@Tamasg oh wow! I think talkback got totally hosed! so I just pressed the google assistant button, and said, "turn on talkback." I just heard from google that talkback isn't available on your device. this isn't good at all!
@Tamasg what if somehow I get the latest talkback installer, and somehow install it using adb? could that work, or would that break things even worse? I mean I would somehow have to get the installer for talkback, but yeah.
@Tamasg ok, it works. it works. meaning talkback is talking again. I don't know why it didn't say it was avaialble, but I have talkback once again. lol.
@JamminJerry yeah, I think sites like apkmirror do host the files for the accessibility suite, unfortunately you'd need to know if you have a 32 or 64-bit chip (most times these days that's arm-64) and grab the right apk file for it. I'm in a work meeting else I would xD
@Tamasg we learned a valuable lesson here today. don't install the dec-talk tts on the smart vision 3 or you will really screw things up. lol. if you are still going to try messing with the dec-talk on the smart vision 3, make sure you have ADB connected, and aloud on the smart vision 3 before installing dec-talk so that if it does what it did to me, you can at least uninstall itk, and get talkback working normally again. lol. I did get it to talk once, when I pressed and held the volume keys to turn talkback on or off, but only once did it say anything at all.
@JamminJerry lol! Super glad you got it working! Wish we could debug exactly what's happening with that phone, in theory things should work since it has both 32 and 64-bit libraries, so maybe certain Cotlin-based apps don't play as nice on older Android versions. Was looking at it though and love how minimally it's built.
@Tamasg @JamminJerry Works great on the braille sense for everything and sense player for third party apps that use android tts. I am finishing my demo tomorrow showing why we need android tts support throughout the sense player.
@JamminJerry @jpellis2008 sadly maybe not. They treat it differently from their BrailleSense 6 a bit which is a shame, and maybe that's on purpose, who knows. This is good news though as it does mean it'll work with the BS6 which I do have to test it out on with Android 12 there.
@jpellis2008 @Tamasg I can tell you right now, I don't see the whole third party tts thing going anywhere with the sense player. they will just tell you it is a multimedia device.
@Tamasg @jpellis2008 well like I just told him, it isn't going to happen. they won't do itl. if I am wrong in the next 18 months, I will give him 15 bucks.
@JamminJerry @jpellis2008 lol I think the issue is that the Sense Player is not Play certified like the BS6, and to them this makes enough of a difference to class-distinguish it. I still can't get why they couldn't play certify a device at that price unless it's hardware related though, but it may be why they locked down shell and settings so much on that.
@jpellis2008 @Tamasg they could, yes. they could have done it way back when I talked to them three different times about it. they didn't, and they won't.
@JamminJerry @Tamasg And that is exactly why it is needed and I will be pointing that out. If it was hard for them to actually implement it I would agree with you but it isn't, just backport from the braille sense. I assume it might literally take seconds to change the code.
@jpellis2008 @Tamasg I will tell you what. if I am wrong, and with in the next year and a half if they actually make it to where you can use what ever ttws you want on the sense player, I will pay you 15 dollars. no it isn't much, but there you go. I am telling you it isn't going to happen.
I am also pointing out in my demo that this has nothing to do with any certifications as I have the braille sense signed out of all google services so it acts as if it isn't certified.
@Tamasg @jpellis2008 as much as that thing costs, they could have done the play services no problem. for what you pay for that thing, they should have built a better body for it too. hell! the victor is cheaper, and doesn't do anywhere near as much, but it is built a lot more stirdy than the sense player, and what in the hell is it with the microphones on the wrong side? not only that, why is the monitoring recording so shitty? seriously? I mean come on!
Dectalk for Android recently fixed a bug that caused it to default to an abnormally high pitch range. As a parting gift, here is said bug as if it were an expiring trial of decTalk for Android.
@fireborn It's a dictionary parsing issue that is being worked through. I think because Microdectalk is 4.2-based, and the 4.99 dictionaries aren't entirely working.
@fireborn Yeah, they're trying to make it run on Dectalks' standard frequency with some success in a test environment, but right now on the actual builds it's using Microdectalk's default.
Jack-Frostodon
Unknown parent • • •JamminJerry
Unknown parent • • •Tamas G
Unknown parent • • •Jack-Frostodon
in reply to JamminJerry • • •Jack-Frostodon
in reply to Tamas G • • •Tamas G
Unknown parent • • •JamminJerry
in reply to Jack-Frostodon • • •Jack-Frostodon
in reply to JamminJerry • • •JamminJerry
in reply to Jack-Frostodon • • •JamminJerry
in reply to Tamas G • • •@Tamasg C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
KAPUS200032 unauthorized
JamminJerry
in reply to Tamas G • • •Tamas G
in reply to JamminJerry • • •JamminJerry
in reply to Tamas G • • •JamminJerry
in reply to Tamas G • • •@Tamasg ok, I think I got it authorized. here is what I see now.
C:\adb>adb devices
List of devices attached
KAPUS200032 device
JamminJerry
in reply to Tamas G • • •Tamas G
in reply to JamminJerry • • •adb shell pm list packages | grep "micro"
Then you can do an adb uninstall with that package name after words.
JamminJerry
in reply to Tamas G • • •Tamas G
in reply to JamminJerry • • •JamminJerry
in reply to Tamas G • • •@Tamasg here is what I got when I tried to do that.
C:\adb>adb shell pm list packages | grep "micro"
'grep' is not recognized as an internal or external command,
operable program or batch file.
Tamas G
in reply to JamminJerry • • •You can just type exit after to go back to the command prompt and do adb unstall like normal with that package name.
JamminJerry
in reply to Tamas G • • •@Tamasg C:\adb>adb shell
SmartVision3us:/ $ pm list packages | grep "micro"
pm list packages | grep "micro"
package:com.bytesizedfox.microdectalk
SmartVision3us:/ $
Tamas G
in reply to JamminJerry • • •adb uninstall com.bytesizedfox.microdectalk
to get rid of it :)
JamminJerry
in reply to Tamas G • • •@Tamasg C:\adb> adb uninstall com.bytesizedfox.microdectalk
Success
JamminJerry
in reply to Tamas G • • •Tamas G
in reply to JamminJerry • • •JamminJerry
in reply to Tamas G • • •JamminJerry
in reply to Tamas G • • •JamminJerry
in reply to Tamas G • • •Tamas G
in reply to JamminJerry • • •JamminJerry
in reply to Tamas G • • •JamminJerry
in reply to Tamas G • • •Tamas G
in reply to JamminJerry • • •JamminJerry
in reply to Tamas G • • •Jay Pellis
in reply to Tamas G • • •Jay Pellis
in reply to Tamas G • • •Tamas G
Unknown parent • • •JamminJerry
in reply to Jay Pellis • • •JamminJerry
in reply to Tamas G • • •Tamas G
Unknown parent • • •Jay Pellis
Unknown parent • • •JamminJerry
in reply to Jay Pellis • • •Jay Pellis
in reply to JamminJerry • • •JamminJerry
in reply to Jay Pellis • • •Jay Pellis
in reply to Tamas G • • •JamminJerry
in reply to Tamas G • • •Jack-Frostodon
in reply to Jack-Frostodon • • •Jack-Frostodon
Unknown parent • • •Jack-Frostodon
Unknown parent • • •