Skip to main content
El Wombat
El Wombat
Inspiring
July 12, 2017
Question

Crash during manual lip-sync viseme adjusting

  • July 12, 2017
  • 1 reply
  • 2074 views

Many times Ch crashed while I tried to manually adjust visemes after "compute scene audio from lip-sync".

You can see the error code in German below. It says something about the error coming from "reading after the end of the file". (This is a literal translation I don't understand a word of this, sorry…

Play speed was set to either 1.0 or 0.75 when this happened.

Hope this helps.

This topic has been closed for replies.

1 reply

oksamurai
oksamurai
Legend
July 12, 2017

Is it possible to DM us a link to the project?

El Wombat
El WombatAuthor
Inspiring
July 12, 2017

Not sure if that'll work. The project folder is 1.47 GB and contains over 40.000 files…

Thing is, there are too many things going on in that project right now and I don't really like doing a mirror in the middle of the project, things can get confusing…

Would the sound file and the puppet file alone help? That way you could mirror what I did closely for I'm talking about a single scene with only that puppet (and a simple bg image).

oksamurai
oksamurai
Legend
July 13, 2017

P.P.S.: I found a solution for now:

- created a new project with only the puppet and the soundfile.

- now it worked. No crashes, no 20 seconds wait for playback to start, every finger crossed.

Of course I don't know what really happened but I have a wild shot in the very dark to share with you guys.

In the first project that caused so much trouble I saw the sound file in the "Gathered Media" folder. I remember putting it there, thinking that might make things easier for Ch.

Possibly the opposite occurred? In the second, new project I didn't see no imported soundfiles in the "Gathered Media" folder. It had remained where it was. Maybe that caused the trouble??? After all, the problem seemed to be more in the sound file playback than in the animation. I don't see why this should happen but it's all I got.

Hope it's either just a one-bad-wonder or that you guys can find the troublemaker lest it returns.

Thank you!


Okay, thanks for the detailed info...let us know if it keeps happening!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices