[–] [S] 3 points 1 year ago

Does anyone know of an Android app to install an additional 3rd party TTS engine that can then be configured to point to a custom Open-AI/Fast-API endpoint for self hosting higher quality voices that are not easily run/fit on mobile hardware?

  • source
  • [–] 5 points 1 year ago

    Yeah, I didn't hear much about the project over this summer.

    Switched from Gnome to Plasma a little after Unity expired, as I couldn't keep up with the churn of Gnome plugins, and hoping Cosmic could balance customizability with stability. KDE has been great with adding HDR support and Wayland features, though as a Rust lang fan, I'm still curious what Cosmic will bring to the table in terms of plugin API and tooling.

  • source
  • parent
  • context
  • [–] 16 points 1 year ago

    Some poignant questions for these new platform requirements:

    • How do you anticipate this being used against journalists and advocacy groups?
    • What research and statistical quantification will be done to evaluate the amount of harm these restrictions can inflict?
    • What precautions or safeguards will users have against malicious state actors or capitulating corporations?
    • How can developers protect themselves from liable damages due to service interruptions caused by third party verification?
    • Do you foresee legal restrictions in rollout due to national security concerns from differing nation states?
  • source
  • [–] 4 points 1 year ago (1 child)

    I've really enjoyed using Kokoro for generating audiobooks:

    Be sure to first try using this convenient API wrapper:

    Note that not all the modelled voices in Kokoro-82M are of equal quality, given disparities in limited training data from reference speakers. However, what's cool is that you can prescribe polynomial weights to multiple voices tags, enabling you to synthesize different variants weighted more heavily from the highest quality voices.

    One current limitation for Kokoro is that there's no way to prescribe emotion or intonation procedurally using markup tags like SSML in the source text, unlike other models like Orpheus. But Orpheus sometimes generate weird hallucinations like repeating sentences, injecting new phrases, appending radio silence or filter words, and generally increasing the tempo of words per minute as a sentence progresses. Still, this may be of interest if you want to add emotion like fear or urgency to your generated dispatches, and manage to tune the input temperature you want for the model.

    However, Kokoro is a lot more compute efficient and audibly consistent, requiring less scrutiny or manual supervision. The author behind Kokoro now also looks to be working towards an emotional variant as well:


    Reference project I've been following for audiobook generation:

  • source
  • [–] 1 point 1 year ago (2 children)

    This is the flake config I started from, but am now refactoring for multi-host support:

    Simple and documented config templates to help you get started with NixOS + home-manager + flakes. All the boilerplate you need!

    I first learned of NixOS through this project, but decided on writing my own config for starters.
    Still, it has been a neat reference as an advance example:

    My main NixOS configuration. Features include a polished Hyprland environment. A fully configured NeoVIM environment, QMK support. A Keyboard shortcut menu pop-down available in the top bar and so much more!


    BTW, could you breakdown your hardware.nix configs?
    They look a lot different from my auto generated one from the ISO install, particularly for fileSystems:

  • source
  • [–] [S] 4 points 1 year ago (1 child)

    Ah, that's a shame. Thanks for the context though.

    I did feel a little bit of that slight dismissal or elitism from the thread I linked above about the graphical installer ISO. Although I think the relative surge of new users after graphical ISO's implementation did end up changing some minds on the merit of its continual development.

    It seems like some tools just never fully realize their potential market demand until they're finally implemented and consequently adopted. Quite the catch 22.

    I also wonder if it's a bit of a motivational aspect for individual contributors, as in demand with mostly originate from novice users who've yet to master the Nix language, yet by the time one's gained enough experience to contribute to Snowflake OS, you've kind of grown out of outgrow the need for it. That kind of reflects my personal interests around graphical programming, as I became more familiar with various languages, my inkling for a graphical representation of control flow gradually waned.

    Still, I think lowering the barrier to adoption is in the long run best serves the community and in sustaining new contributors. Sort of like the conventional Greek proverb:

    A society grows great when old men plant trees whose shade they know they shall never sit in.


    Nix can create attribute sets from JSON, so there isn't a need to generate nix code.

    Is there a good way of mixing and mashing JSON attribute sets with conventional nix config files? Perhaps relegating some config to machine-generated JSON, and some hand crafted configs?

  • source
  • parent
  • context
  • view more: ‹ prev next ›