Moho Forum

I have found that when using Papagayo, the phonetic breakdown in the WAV view does not extend to the end of the file. I cannot drag the text and phonetic cues past a certain point near the end of the file. They refuse to go and shrink up and disappear as though that were the end of the file.

I happen to be using a setting of 30fps instead of the default 24fps. Not sure if this makes a difference, but I am planning outputting later to DV.

Perhaps I am missing something? The audio does play the entire file which is about 330 frames long. But then I have this same problem with the text and phonetic breakdown even on shorter audio files. That's what makes me think it might be due to not using the default of 24fps.

Is anyone else experiencing this problem?

Yes, I've experimented this problem... but seems that it only occurs if yuo are working in a NEW proyects, so if you save your Papagayo proyect and re-open it I think that the problem should have dissapear... Try & see

Well I did a little more experimenting and found if I tack on some silence to the end of the wav file, it then extends it enough to drag the phonetic text over to end of the audion. This is a work around of course and it only raises my thoughts that it is because I am in 30fps as compared to the default 24fps.

But as stated above that is another work around incase anyone else is experiencing the problem. It did not seem to make a difference if I reopen the file again or not. It still had problems.

Also tacking on some silence to the beginning of the file allows you to include animation before the character begins to speak. That is a work around since the wav file starts exactly at the beginning of the timeline in Moho. You figure out how much space you need time wise before the character speaks and add it as muted silence to the beginning of your wav file.

Im guessing its the FPS

FPS?

Steve Polyanchek wrote: FPS?

Frames Per Second, You said you had it set to 30, And defualt is 24.
That just might cause the problem.

Of course, frames per second.... I just wasn't thinking...

But the problem exists anyway , and maybe I be in a mistake, but I'd say that it's not relationated with the FPS issue and I maintain the "little" bug theory

PD: Sorry...