[Scrum] - SUSI Interpretation Project - 20260626

3 views

Skip to first unread message

Eshaan Walia

unread,

Jun 26, 2026, 12:16:44 PM (4 days ago) Jun 26

to SUSI.AI

1. What did I do yesterday?

(eventyay-interpretation) - Made PR (#27) - Feat/Translated subtitles (multi-language)
draft
(eventyay-interpretation) - security fixes for http client PR (#19) - Feat/Milestone 1: SUSI connection layer for eventyay-interpretation
(eventyay-interpretation) - Implement tts in eventyay videos Issue(#25) - Task 2. Translated subtitles (multi-language) in eventyay videos
(eventyay-interpretation) - Updated Issue(#25) - Task 2. Translated subtitles (multi-language) in eventyay videos
(eventyay-interpretation) - Updated Issue(#24) - Task 1. Text-to-Speech (TTS) audio output

Implementing text-to-speech (TTS) support for Eventyay video streams as part of the multilingual interpretation workflow. I also addressed security-related improvements in the HTTP client used by the SUSI connection layer.

2. What do I plan to do today?

Today, I plan to update PR #15 by fixing the Python cache configuration to match the Eventyay project structure. I will also fix the rough layouting for ui in eventyay videos, bringing transcriptions out of the control panel and have its own box. Reorganize the models to follow the pattern used by other Eventyay plugins, and update the streaming flow so that WebRTC is the primary transport with Server-Sent Events (SSE) used as a fallback. To have an initial connection, we added SSE as primary connection and polling as fallback. would get rid of poling completely now that our signals and middleware are configured. here is a flowchart of current communication:
plugin comms.jpeg