Closed Technologicat closed 10 months ago
Now, when doing a batch export, the manual poser generates _emotions.json
(in the same output folder). This file can be used as SillyTavern/public/characters/characternamehere/_emotions.json
(per-character emotion templates).
Made some doc updates. That part is still WIP, but documentation could be a separate PR.
load_emotion_templates
,load_animator_settings
.talkinghead
README how to use the new configurability.launch
in a separate thread. Better for predictable ordering of startup messages for the ST-extras server.talkinghead
module, highlight the nametalkinghead
, the CUDA device used, and the model variant. Makes it more explicit that it may use a CUDA device different from that of most other extras modules.server.py
to format it more like a standard Python script.main
function and call itif __name__ == "__main__"
, as the pythonic equivalent to the top-level JS IIFE goes, but OTOH,flask
makes that difficult (since we need to instantiateapp
to make@app.route
available for the API endpoint definitions), andserver.py
is not intended to be imported as a module into other scripts anyway. So there would be no practical benefit, other than IDEs being able to catch unused variables.~THIS PR IS NOT YET FINAL:~ EDIT: Now it is. :)
~I will add one more feature - namely, the manual poser doesn't yet automatically generate a suitably formatted
_emotions.json
. This will only take a few lines of code, but I'm out of time right now - I'll finish this either tonight or over the weekend. I'll update the PR once done.~~Meanwhile, the rest can be reviewed.~
Tested with the following
SillyTavern/public/characters/characternamehere/_animator.json
(note: per-character config, at the client end!): EDIT: This configuration is now provided as an example in thetalkinghead
README.The rest are defaults, but the
"postprocessor_chain"
makes the character into a scifi hologram.