[Addon] Quick Talk, lip synching tool - UPDATED 22 Oct 2015

Yeah, if you change the source-file you’ll need to reinstall the addon. The “install” process makes a copy in the blender config directory somewhere I believe.

Glad you got it working :slight_smile:

Thank you for the creation and sharing. I watched some of your videos, appreciate the time and effort. The script seems to be a fine idea, and I have ‘plans’ but I will see what I actually do, . . . back to character creation at the moment…

Thanks. Sharing is caring. Tell your twitter feed which one was your favourite. :slight_smile:

The script seems to be a fine idea, and I have ‘plans’ but I will see what I actually do, . . . back to character creation at the moment…

Cool. Hope Quicktalk makes your plans actually possible, coz without something like it mine would never happen. I certainly don’t have time to worry about animating every individual syllable.

Papagayo was working, but not well. Somehow ergonomically it was literally painful to use.

I’ve been actually using this script in my toons for practically the first time on anything of significance during this last week or two as it goes.

It’s so much smoother a process now than that was. Seems to hurt my wrists less too.

Can see many improvements I could make to how it works if I only had the time. Not sure how valuable the “guess line markers” button is at all. Might as well go straight from Guess Dialogue to Guess Words I’m finding. Should more smoothly handle missing dictionary-words ideally.

Well, ideally, I’d be able to put character-importing and proxying and vague stage directions into the input-script and have it automatically build more broad-brush animation too.

Imagine just being able to write:

TheHero: [Enters stage left]
[Waves Right Arm]Not So Fast Bad Guy!

BadGuy: [Fighting stance]
You’ll never defeat me Hero!

TheHero: [Move to BadGuy]
Charge!

Then you just press “import” on a blank scene that’s got nothing but audio-radio-play and word-markers and they’re all there, doing about the right thing already.

That’s the dream anyway.

I have no time though.

Might look at it more once this current toon is done while I plan the next. Possible I could save time overall by writing some code.

Patches accepted. :wink:

Were can I download the quick talk add-on

Strange, though that URL would have been in the first post, will update it (assuming I can)

Blender 2.8 is coming along marvelously, and the latest version isn’t just crashing all the time like it was the last time I looked.

So I updated my Lip-Sync plugin for Blender to work with Blender 2.8. Wasn’t even difficult really. Just a few API tweeks.

The “Makehuman” compatibility mode will have to wait till Makehuman’s MHX importer is similarly adapted to 2.8 [*], which is surely much more tricky to do so could be a while. But the control-panel-building and marker-guessing and actual lipsynch to shape-keys stuff seems to be working with the new version.

[*] - https://bitbucket.org/Diffeomorphic/mhx2-makehuman-exchange/issues/68/adapting-to-blender-28

1 Like

Thanks!
I can’t wait to test it on my shiny Blender 2.8.
MakeHuman 1.2.0 alpha3 is announced for Blender 2.8, not released yet.
Wait and see.

Hi, Is it possible to add languages ​​other than English to this add-on?
In that case, how do edit py and dictionary?

Should be possible if you can find a phonetic dictionary for that language. Don’t think it should even require any changes to the code. But I have no idea where you’d find a phonetic dictionary for your language I’m afraid.

We are sorry. We didn’t notice because I did not receive notification.
Thanks for the quick reply.
Certainly, I tried to search the dictionary but I can not find it. We decided to convert it to an English format that this add-on can read.

By the way, this add-on is great for its quick action to associate multiple shape keys with bones and drivers.
We create and use scripts to assign custom shapes to all rigs generated by this add-on.
Assigning custom shapes one by one was cumbersome. =)
Thank you for the nice add-ons.

Oh, and. We think that it is better to disable the property of each Deform for quicktalk generated bone.
This is useful when using the add-on rigfy or Voxel Heat Diffuse Skinning, and auto-weighting.
This eliminates the need to attach unintended rig weights and makes weight correction easier.
We tried to edit py and put the option in place, but it has not been done so easily. Sorry for the suggestion only.

Certainly no need to apologize for a suggestion. Not sure I follow it though… “disable the property of each deform?”

Oh. You mean reset the “deform” flag on each bone when I generate a rig. Yeah. Possibly a good plan. I’d have generally not created the shape-keys for a mouth movement till after the weights were set, and usually only done it with the desired bones selected.

Will try and keep it in mind if I do some edits anytime soon. Thanks.

Yes, we talked about the deformation option for that bone. and yes, We use the Quick Talk add-on after all shape keys and all weights have been done.
However, we often adjust weights and change rigs later.

But certainly you do not have to follow. Of course we also understand it. Just a suggestion. =)
We believe that add-on developers have the freedom and choice to allow developers to do the development they want.
There is no need to incorporate what someone wants to do.
Have a nice day.

Firstly, thankyou so much for taking the time to create this godsend.
However, I am having trouble with the plugin. When I build the shapekey armature and try to pose the bones, they do not effect the shapekey. The shapekeys are displaying that they have drivers (purple shading) but the rotation of the bones does not have any effect. Can you please help me!!!

Additionally, when i move the sliders for the shapekey manually in the object data panel, nothing happens.

Presumably the sliders worked before you attached the bones to it? The drivers are likely resetting the sliders as you try to move them once the drivers are attached.

There’s an option in the panel to change whether it’s the bone’s rotation or the bone’s translation which drives the key. Possibly you picked translation and then rotated them?

Other than that I dunno I’m afraid, and am heading out for the weekend shortly so any further help is likely have to wait till next week.

Good luck!

HI, thanks for getting back to me. I hope you have a great weekend. To clarify, yes the sliders did work before attaching the bones. I have tried both rotation and translation options for the bones in the panel and tried to move them accordingly.
I have looked at the driver associations in the graph editor and they all appear to be assigned correctly, however the only thing I note is there is an error “ERROR: Python auto-execution disabled”, just under the expression box.

I am going to try to rebuild my model from scratch to see if I can get it to work. Will let you know how that goes.

Cheers

Ah, the script isn’t able to run because your Blender is set up not to trust it.

See here: https://blender.stackexchange.com/questions/46899/python-auto-execution-disabled-error

Hi. Just an update. I was able to get the armature working by reassigning the drivers in the graph editor. Now I have plotted all the dialogue line and word markers and I am getting an error when plotting (the final step).
I am getting the error:
Traceback (most recent call last)
Line 898, in execute script.plotTimelines()

And

Line 813, in plotTimelines endFrame = wordStarts[n]
IndexError: list index out of range

It seems to plot keyframes to a point and then nothing.
I have removed certain word markers that weren’t needed. Could this cause the issue?

Really hope you can help! Thank you so much for everything you are doing!

Ps. Thanks for the tip re blender trust issues!

Edit: I think I found the issue. I think it is stopping when words are encountered which are not in the dictionary. I have developed a workflow (if anyone is interested). I run the plot then work out where it stops and fix the scrip run again, delete markers and keyframes and try again. Fingers crossed!

Probably a word in your script which isn’t in the dictionary. If you look at the console while running it’ll say which word it couldn’t look up and you can change that word to something else which has a similar set of visemes.

If it’s not that then also the console might have a clue.

In windows the console can be seen from a menu option. In mac/linux launch Blender from a command-line console to see it.