Auto Lip Sync Problem creating "S" Visemes erroneously and transcript lip sync crashes

[richardf46745123]

I'm at my wit's end with this problem.  Char Animator lip sync is throwing in S visemes at the beginning of my words and in between words.  The audio is super clean. I use an audio booth and a high-end mic, and it's audio engineered to be clean. 

If I try to use a loaded transcript, Character animator crashes 10% through, even though it's only a 5-minute animation. 

My computer is a high-end gaming machine just bought this year so it's not a processing power or memory issue. 
I've altered the lip sync settings changing the db muting and the viseme detection and the problem doesn't improve.   I loaded an overly noise reduced and noise gate processed audio test file, and the same problem happens. 

Here's a screen capture of the issue. (and attached) https://youtu.be/7nOPv4yqC7s

I've wasted all afternoon trying to solve this problem and I am so frustrated. 

[dtull-adobe]

Sorry this isn't working better, I'll see if I can help.

Did you report and send the crash by chance? I didn't see a crash dialog or errors in the video (only mention of the crash at 10% or so), but if you have an audio and SRT (in the video, it looked like it was in SRT format), I can probably try to debug why transcript lipsync is failing with a few more details on that part.

The option that might help reduce stray visemes there is the audio based muting, but as you note, the audio does look clean in the silence parts, so it does seem like it doesn't really resolve it.

It might also be worth trying out the project in the currently released Beta build of Character Animator to see if the failure happens there as well, though I don't know of any major changes to transcript based lipsync since the 23.1 release.

[dtull-adobe]

I did a quick search for crashes on Windows with 23.1 in the last 24 hours. There was one crash about 11 hours ago that was in the progress dialog code which might have happened during transcript lipsync processing, though there's nothing in the crash that would point to it specifically and I'm not sure that timing is quite right.