home.social

#speechsynthesis — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #speechsynthesis, aggregated by home.social.

  1. We should do a crowdfunding campaign for a "Starcraft Terran siege tank driver" text-to-speech voice for Piper, so that Orca can angrily read GTK widgets at you with this kind of confident and upbeat intonation: youtu.be/dtoIv9BzPHk?t=16

    #Piper #Orca #TTS #texttospeech #speechsynthesis #GNOME

  2. Since my previous post asking about programmers, etc. received so many positive responses, I am going to use the same tags and explain what I wish to accomplish. That way, I can learn from real experts what is possible and what isn't. Note that I am not a programmer and am just writing as a user.

    Hello, everyone. I am forty-one and totally blind, having never seen. I have loved DOS since I was a teenager and basically taught myself tto use it, since by the time I learned about it, people were already moving to Windows. I love XP and 7 but find 11 to be frustrating and annoying. Unlike many, I don't find Linux or Mac OS to be worthy replacements. But I strongly feel, given the general advances in technology, as well as those in modern versions of DOS, that it can be a viable alternative. It's quick, efficient, and text-based. This, then, is my ultimate vision. Some of these things may be easier to implement than others, and some may not even be possible. One of my favourite sites is this one, which debunks all sorts of fallacies related to DOS and gives me hope that my dream may someday be realised.

    chebucto.ns.ca/~ak621/DOS/DOS-

    Summary

    My ultimate vision is a 32-bit version of DOS with true multi-tasking, a talking installer, an updated screen reader, a software synthesizer, and usb support that could be used as a daily operating system on modern (or at least semi-modern) hardware.

    Blind-Specific Goals

    1. Talking installer: One of the main difficulties of installing DOS for a blind person is the lack of speech without a dedicated screen reader. This was true even in Windows XP, and to a lesser degree, 7, though Talking Windows PE (a version with the NVDA screen reader slipstreamed into it) changed that. I have also seen someone load config.sys, autoexec.bat, and command.com along with the ASAP screen reader onto a floppy and boot from it, so it may, indeed, be possible, though booting from a floppy is automatic, whereas booting from anything else would require changing the bootloader, which is not accessible to the blind. If it is not possible to create a talking installer, perhaps some sort of batch system, similar to XP Unattended, can be created, so that the user just has to hit a few keys and start an automatic installation.

    2. Software speech synthesis or reasonable alternative: This might be one of the most difficult things to implement, but it is th emost important. As it stands, most DOS screen readers work with hardware synthesizers that connect either via a serial port or an internal card. They work well, but unless new ones are made, they may be difficult to find. Plus, many computers don't have a serial port, and I'm not sure usb to serial can even work in DOS, especially for this sort of thing. Ideally, there would be a synthesizer, similar to ESpeak in NVDA, that would work directly with the screen reader to voice text on the screen. However, it seems that these sorts of synthesizers require apis, etc. that DOS doesn't have. Whether it would be possible to simulate a hardware synthesizer in real DOS as is done in the Talking DOSBox, which also contains Windows 95, I don't know. It is possible to send speech directly to the pc speaker, but most pc speakers, when they exist, are designed for beeps and very low quality output. That said, there was a novelty synthesizer, called Tran, that did just this. Perhaps a more serious version could be created and connected to a screen reader. There were screen readers that worked with the SoundBlaster synthesizer which did use software, but even that required the real card to be installed. If drivers and synthesizers can be created for more modern soundcards, that might be a bridge between full software synthesis and requiring an external device. A final option is simply to create modern synthesizers with an RS-232 connection. At least the speech would be good and they would still be manufactured, unlike the older ones.

    3. Updated screen reader support: I don't know how much screen readers would need to be updated in order to be able to take advantage of modern programs and versions of DOS, but having that option would be a good thing. The only fully open source screen reader I know of is Provox. While JAWS for DOS, Vocal-Eyes, Flipper, etc. were all made freely available, we don't have their code. I am going to attempt to contact Larry Skutchan, maker of ASAP, to ask if he is willing to let us work with the code, or rewrite and update it, as he may no longer have the program.

    General Goals

    1. 32-bit: Even in Windows, I don't see the need for a 64-bit system. But I do think that DOS can benefit dramatically from being upgraded to 32-bit. It would mean more memory could be used in ram, true multi-tasking without extra tools could be done, and maybe, some of the blind-specific ideas of mine could be accomplished. I really cannot stress the importance of multitasking enough, even for mainstream things such as browsing the Internet while keeping an e-mail client open to alert for notifications, or even listening to music while reading a website or downloading something. I am fully aware of tsr programs, and they are wonderful, but they don't allow for background processes. I have heard of FreeDOs-32, but it seems to be no longer maintained.

    2. Full usb support: I know that there is very rudamentary support for usb storage, but if this could be expanded to other devices, it might be possible to use a sound card for speech, a usb keyboard, a camera or scanner for ocr, a wifi dongle, etc.

    3. An accessible, modern browser and wifi support: I know that it is possible to connect to the Internet using certain wireless cards. I also know that there is at least one graphical browser called Arachne. But whether it is accessible or has been updated, and whether more exist, I don't know. And what about systems without these cards? Can they access the Internet using wifi or at least cable via an ethernet connection?

    4. A text-based, menu-driven desktop: I love the commandline, but sometimes, it might be quicker and/or easier to use menus. The graphical desktops require use of the mouse. I want to retain the text-based nature of DOS. It seems that this may already exist, and that I need to research DOS Navigator, Volkov Commander, Midnight Commander, and Norton Commander.

    Things to Avoid

    Don't turn DOS into Linux or Windows. Keep program installation simple, don't start requiring permissions for things, don't make everything graphical with a terrible interface that keeps changing, ribbons, etc., and don't include artificial intelligence as mandatory.

    #accessibility #AdaptiveTechnology #blind #DOS #FreeDOS #Internet #MSDOS #programmers #programming #ScreenReaders #software #SpeechSynthesis #technology

  3. Would anyone be able to help me contact Larry Skutchan, or could someone please pass a question on to him? I don't wish to disturb him, especially now that he is retired. Several years ago, I recall asking him about ASAP and if I could obtain a full version of it. He told me that he no longer had it, but that the demonstration was fully functional, with only some reminders to buy the product. I must assume that, since he lost the program, he also lost the source code. But if I knew the language in which it was written, I could find a programmer to rewrite the code, updating it to add support for software synthesizers, various modern things, and even create new set files for updated and current programs. But naturally, I need his permission to do so, since it is not open source and I don't want to get in any sort of legal trouble. While Provox is, indeed, open source, ASAP is one of the most advanced and flexible DOS screen readers, and I would like to use it in my project to make FreeDOS and its programs more accessible.

    #accessibility #APH #ASAP #blind #DOS #FreeDOS #programming #ScreenReader #ScreenReader #SpeechSynthesis #technology

  4. Would anyone be able to help me contact Larry Skutchan, or could someone please pass a question on to him? I don't wish to disturb him, especially now that he is retired. Several years ago, I recall asking him about ASAP and if I could obtain a full version of it. He told me that he no longer had it, but that the demonstration was fully functional, with only some reminders to buy the product. I must assume that, since he lost the program, he also lost the source code. But if I knew the language in which it was written, I could find a programmer to rewrite the code, updating it to add support for software synthesizers, various modern things, and even create new set files for updated and current programs. But naturally, I need his permission to do so, since it is not open source and I don't want to get in any sort of legal trouble. While Provox is, indeed, open source, ASAP is one of the most advanced and flexible DOS screen readers, and I would like to use it in my project to make FreeDOS and its programs more accessible.

    #accessibility #APH #ASAP #blind #DOS #FreeDOS #programming #ScreenReader #ScreenReader #SpeechSynthesis #technology

  5. Would anyone be able to help me contact Larry Skutchan, or could someone please pass a question on to him? I don't wish to disturb him, especially now that he is retired. Several years ago, I recall asking him about ASAP and if I could obtain a full version of it. He told me that he no longer had it, but that the demonstration was fully functional, with only some reminders to buy the product. I must assume that, since he lost the program, he also lost the source code. But if I knew the language in which it was written, I could find a programmer to rewrite the code, updating it to add support for software synthesizers, various modern things, and even create new set files for updated and current programs. But naturally, I need his permission to do so, since it is not open source and I don't want to get in any sort of legal trouble. While Provox is, indeed, open source, ASAP is one of the most advanced and flexible DOS screen readers, and I would like to use it in my project to make FreeDOS and its programs more accessible.

    #accessibility #APH #ASAP #blind #DOS #FreeDOS #programming #ScreenReader #ScreenReader #SpeechSynthesis #technology

  6. Would anyone be able to help me contact Larry Skutchan, or could someone please pass a question on to him? I don't wish to disturb him, especially now that he is retired. Several years ago, I recall asking him about ASAP and if I could obtain a full version of it. He told me that he no longer had it, but that the demonstration was fully functional, with only some reminders to buy the product. I must assume that, since he lost the program, he also lost the source code. But if I knew the language in which it was written, I could find a programmer to rewrite the code, updating it to add support for software synthesizers, various modern things, and even create new set files for updated and current programs. But naturally, I need his permission to do so, since it is not open source and I don't want to get in any sort of legal trouble. While Provox is, indeed, open source, ASAP is one of the most advanced and flexible DOS screen readers, and I would like to use it in my project to make FreeDOS and its programs more accessible.

    #accessibility #APH #ASAP #blind #DOS #FreeDOS #programming #ScreenReader #ScreenReader #SpeechSynthesis #technology

  7. I cannot figure out how to get real DOS (of any kind) working in VMWare with Com0com and NVDA (my hardware synthesizers are packed away at the moment), so right now, I have Talking DOSBox. Since it already speaks and has various synthesizers available, I would like to know if it would be possible to substitute MS-DOS with FreeDOS 1.4, since I want to try the advanced features, modern programs, etc.

    freedos.org/download/

    The main problem I see is installing it with speech. Perplexity gave me instructions that seemed viable, but upon actually looking in the various directories, I discovered that the reason Talking DOSBox works with the SoundBlaster synthesizer is that it's not pure MS-DOS but the version that comes with Windows for Work Groups. There is another way to access speech, so that NVDA acts as a bns driver, but I'm not sure if this would work, either with MS-DOS or FreeDOS. Can anyone assist me?

    #accessibility #blind #computing #DOS #DOSBox #FreeDOS #NVDA #OperatingSystems #ScreenReaders #SpeechSynthesis #technology #VirtualMachines #VMWare #Windows

  8. This post was inspired by the accessibility, or lack there of, of various operating systems, annoyances that people have with Windows, and the current state of Linux, which many sighted people tout as a great Windows alternative. While there are obviously some blind people who use it, overall, the experience is neither streamlined nor easy. and it can be downright frustrating. There is Mac OS, but then, there is the expense of a Mac, plus the fact that many normal periferals can't be used with it. There are Android and IOS, but these are touch-based, not built for computers, though both can be used with real keyboards. Still, such operating systems come with their own headaches.

    My solution is one that cuts through all of the hurdles to a system that is fast, efficient, light on resources, and very accessible. This is DOS. I am not referring to MS-DOS, but to modern varients such as FreeDOS (just updated this year), Enhanced DR-DOS (updated a few years ago), VDOS (a version that runs directly in modern Windows systems), etc. For instance, this is FreeDOS.

    freedos.org/download/

    This is a wonderful (and long) list of general fallacies that people may hold about the operating system, as well as statements debunking them and proving why it is still a viable choice in 2025.

    chebucto.ns.ca/~ak621/DOS/DOS-

    For us in the blind community, there are really only two issues standing in our way. The first is a good screen reader, and the second is software synthesis. Yet even these can be overcome. While many DOS screen readers were made in the past, only one is now completely open source. That is Provox. The entire code is available for us to update to our hearts' content. (Look down the page and you will find the download link under the screen reader section.)

    allinaccess.com/happ/

    Of course, we could create an entirely new one, but this gives us a good place to start if we don't want to reinvent the wheel. As for hardware synthesis, it was done in the past, with Flipper. It's not the best, but it shows that it is possible. Now, with all of these updates to DOS itself, as well as faster machines with better memory, soundcards, and drivers, it should be easier to create a software synthesizer.

    There are still people programming for DOS, both for everyday use and versions of the operating system itself. Why not collaborate with them? Why can't we have a text-based, keyboard-driven operating system that works for us, that isn't bloated, and that we can even help to create? Imagine a version of DOS designed with accessibility in mind. What if it came with a built-in screen reader that talked during installation, braille support, a magnifier, ocr software, various other accessibility options, and menus that were easy to navigate for those who didn't wish to use the commandline, as well as access to it for those who did? What if it were free, or at the very least, extremely cheap, and could run on almost anything, so that anyone in the world could use it, provided he had some sort of computer? This is all within reach.

    How many of you would be interested in at least trying out these modern versions of DOS to see what they offer and how far we could take them into the realm of accessibility and daily use?

    #accessibility #blind #commandline #computing #DOS #FreeDOS #OperatingSystem #programming #ScreenReader #SoftwareSynthesizer #SpeechSynthesis #text-based #tui #WindowsAlternative

  9. @thelinuxEXP I really like Speech Note! It's a fantastic tool for quick and local voice transcription in multiple languages, created by @mkiol

    It's incredibly handy for capturing thoughts on the go, conducting interviews, or making voice memos without worrying about language barriers. The app uses strictly locally running LLMs, and its ease of use makes it a standout choice for anyone needing offline transcription services.

    I primarily use #WhisperAI for transcription and Piper for voice, but many other models are available as well.

    It is available as flatpak and github.com/mkiol/dsnote

    #TTS #transcription #TextToSpeech #translator translation #offline #machinetranslation #sailfishos #SpeechSynthesis #SpeechRecognition #speechtotext #nmt #linux-desktop #stt #asr #flatpak-applications #SpeechNote

  10. 🌟 Excited to share Thorsten-Voice's YouTube channel! 🎥 🗣️🔊 ♿ 💬

    Thorsten presents innovative TTS solutions and a variety of voice technologies, making it an excellent starting point for anyone interested in open-source text-to-speech. Whether you're a developer, accessibility advocate, or tech enthusiast, his channel offers valuable insights and resources. Don't miss out on this fantastic content! 🎬

    follow hem here: @thorstenvoice
    or on YouTube: youtube.com/@ThorstenMueller YouTube channel!

    #Accessibility #FLOSS #TTS #ParlerTTS #OpenSource #VoiceTech #TextToSpeech #AI #CoquiAI #VoiceAssistant #Sprachassistent #MachineLearning #AccessibilityMatters #FLOSS #TTS #OpenSource #Inclusivity #FOSS #Coqui #AI #CoquiAI #VoiceAssistant #Sprachassistent #VoiceTechnology #KünstlicheStimme #MachineLearning #Python #Rhasspy #TextToSpeech #VoiceTech #STT #SpeechSynthesis #SpeechRecognition #Sprachsynthese #ArtificialVoice #VoiceCloning #Spracherkennung #CoquiTTS #voice #a11y #ScreenReader

  11. A while ago I asked ChatGPT: "Write a song that explains the concept and differences of instances, holdings and item records in the FOLIO library system." See lyrics at openbiblio.social/@vform/11043

    Now I have it read by elevenlabs.io (without repeating the chorus, only saying "chorus" where it would repeat). Pretty nice even though it is not exactly intended for songs or poems

    #Folio #ChatGPT #fun #music #ElevenLabs #SpeechSynthesis #text2speech

  12. @spacepup

    It's my trusty Grandstand (first) Talking Computer, a #SpeakAndSpell-inspired educational toy.

    I made a little demo video for it here: diode.zone/w/uSpduKTnjRCCxsLaX

    #RetroTech #SpeechSynthesis

  13. @spacepup

    It's my trusty Grandstand (first) Talking Computer, a #SpeakAndSpell-inspired educational toy.

    I made a little demo video for it here: diode.zone/w/uSpduKTnjRCCxsLaX

    #RetroTech #SpeechSynthesis

  14. @spacepup

    It's my trusty Grandstand (first) Talking Computer, a #SpeakAndSpell-inspired educational toy.

    I made a little demo video for it here: diode.zone/w/uSpduKTnjRCCxsLaX

    #RetroTech #SpeechSynthesis

  15. Spotify tests using AI to automatically clone and translate podcast voices - Enlarge (credit: Getty Images)

    On Monday, Spotify rolled out a... - arstechnica.com/?p=1970963 #machinelearning #speechsynthesis #audiosynthesis #aitranslation #voicesythesis #voicecloning #deepfakes #aiethics #podcasts #spotify #biz#tech #ai

  16. for the few that care: DECtalk now builds on 32-bit Raspberry Pi OS (Debian, armhf). It previously only ran on 64-bit OSs.

    dectalk/dectalk: Modern builds for the 90s/00s DECtalk text-to-speech application. — github.com/dectalk/dectalk

    #DECtalk #tts #TextToSpeech #SpeechSynthesis #RaspberryPi #aeiou