Storyline 360 users: What are your localization pain points?

This is how you (Articulate) can best leverage AI. Look at what companies like "HeyGen" are already doing. I upload a video of myself talking in English (a "talking head" video) to their website (or, in Storyline, I'd want to be able to drop a video on a slide). 

Then I select what language I want (for example, Spanish).

That's it. That's all I have to do. HeyGen automatically:

• Creates an AI clone of my voice based on what it hears in the video I uploaded
• AI transcribes what I say in the video
• AI translates the English transcription into Spanish
• Reads the translated transcription using AI text-to-speech with my AI-cloned voice so it sounds like I am speaking the target language (Spanish, in this case)
• AI adjusts the lips in my video so that they now sync up with the Spanish-speaking AI voice clone, completing the illusion that I am speaking Spanish.

Add to this some other AI-powered processes to take the Spanish transcription and use it to create timed closed-caption files synced with the new Spanish audio.

While you're at it, have a different voice generate an audio description of whatever is happening in the video (this is for accessibility purposes).

In other words, nearly everything in the localization and accessibility workflows should be AI-powered and automatic. As soon as I put any media on a Storyline slide, closed captions, translations (if I so desire), audio descriptions of visuals, secondary audio tracks, etc. should all be generated automatically and in the background. For images, ALT tags should be auto-generated.

This would be a HUGE time saver. And I think most of the technology to do this already exists.