woovie.net / streamplace-tts
streamplace streaming tools
fork atom

Project Redesign #1

open opened by woovie.net edited

When reviewing this project, I realized I could transform this into a much more structured tool with toggles, settings, and everything handled clientside (outside of advanced TTS)

Here's my design goals:

  • Landing page with basic descriptions of how the various tools work and what their intent is
  • Configuration including Streamplace handle, TTS, etc.
  • Basic, non-local (in-browser?) TTS solution with advanced TTS solutions supporting other tools (initially simply support piper due to familiarity)
  • Deployed to a static page without a local client needing to run the project
  • Maybe oauth eventually?
  • Ingestion of 3rd party chats?
  • Testing?
woovie.net (author)

How about an endpoint like /chat that renders just the chat for OBS overlay, but also embed the chat preview in the "dashboard"

woovie.net (author)

and maybe dashboard is the right word, just need to build it out

woovie.net (author)

After mentally reviewing for a while, cloning the concepts of Johnnycyan but streamplace specific seems like a good place to take this tool!

woovie.net (author)

Do not toggle input fields, keep them static and simply disable them

woovie.net (author)

Chat should flow like so:

  • Chat from $platform event
  • Module for specific $platform stores chat into singleton
  • Singleton stores all chats in a non-platform specific manner
  • Chat is rendered by a Chat view which also loads said singleton
sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

Participants 1
AT URI
at://did:plc:wh2g32kxs6xgduoibqdpne5j/sh.tangled.repo.issue/3mckx24rclz22