Translate text-to-speech automatically or add an Excel export for all audio data
I disparatly need Text-to-seech (TTS) translation easier. Right now, the process is way too manual and time consuming. It seems I have to manualy go find EACH TTS file in EACH slide, note them manualy, to then be able to translate them myself or with an external tool and then reimport MANUALY EACH ONE. Therefore, I strongly suggest an upgrade that enables TTS automatic translation with AI OR add an Excel export to extract content and data about all audio files all at once in one sheet. The Data is shown in the Media Library, all that is missing is an export that extracts all that data at once.Chatbots in courses
People have been able to make AI chatbots that pull content and answer user questions in courses. It would be great if this could be a feature storyline provided without having to use external programs to build the chatbot. I build large guides in rise and while the search feature is nice, it would take the guide to the next level if learners could ask their question to the chatbot and get answers from the content in Rise.Expanded JavaScript Access to Characters
I'm unsure how the illustrated characters are "assembled" but if there's any programmatic element combining different poses, expressions, and perspectives, exposing that in the JavaScript API (alongside the default expressions) would permit some pretty nimble narrative development.Color-Coding Triggers
In addition to the having a comment field added to Storyline triggers, it would be super convenient if we could assign colors to the triggers (background) as well. I think a user selectable color would be most useful, as we may only need to highlight a few critical triggers during development. The rest could remain unassigned (i.e., white). It can be quite tedious to repeatedly scroll through dozens of triggers looking for the one that you need to work with while troubleshooting. If I could highlight a few with different colors, then they would stand out and I wouldn't so easily confuse one for another, accidentally overwriting my settings, scripts, or whatever.Search functionality for unassigned trigger.
At present, we are required to manually inspect each page and layer for any unassigned triggers, which is a labor-intensive process and prone to oversight. This method is not only time-consuming but also increases the likelihood that some unassigned triggers may go unnoticed. There are instances when triggers remain unassigned due to various reasons, such as moving or reusing slides, or other operational factors. This can lead to significant functionality errors, which could impact the overall performance. To streamline this process and reduce the risk of errors, it would be highly advantageous to implement a search functionality specifically designed to identify and highlight unassigned triggers.
