glad you like it! here what's happening: - The global rigify super.face and local bones are getting aligned with the empties (doesn't take parent scale into account yet) - The generated rigify rig drivers are getting constrained to the empties At first I planned to make any rig snap to the empties, but after some testing I realised that this cannot work out. Usually many drivers are getting used when creating face rigs, that's why I went for the rigify face rig approach :)

thanks a lot, glad it enables you to move further :) keep on creating!

If U are just looking for face tracking, check out my mobile app blendartrack - it's better for facial animation at the moment

Hey Lincoln, I just recognised your comment - sorry for the late answer. how is it going? For learning rigging, I can recommend cgdive. I've started to make some new tutorials about rigging and plan to update blendartrack soon to make the facial animation transfer easier. In which fields are you interested? There are lots of great resources around :)

You should be able to scale the keyframes in the timeline on the x-axis you just have to find the appropriate amount to scale them down by. For example if you worked at 30fps you would scale them down so that they were halved. This video: kzfaq.info/get/bejne/arKeeqmlrNDPYnk.html talks about it more specifically. I've timestamped it to make it easy for you to find :-) I hope this helps!

@@Cripthulu very useful thank you

Hmm..maybe they use the new rigify face rig version. I plan to implement that in the future. Currently that's not supported.

I think you tried transferring to a non generated meta-rig. make sure to upgrade it

can u share the file with me?

@@cgtinker Thanks for the response. I already solve it!. I was trying to apply it to the bones instead the rig. Thank you again for the tutorial and predisposition to answer the questions. Have a great day!

Thanks! The blendartrack facial animation sample file? Gotta check if it's still in my docs. Let me know your mail / way to send it to you if I find it. If U mind sharing it here lmk at hello(at)cgtinker.com

Whats the error message?

I think the easiest workflow is just to parent the mesh to an empty. then scale and transform the empty to your linkings :)

Im having same issue aswell, i have followed every details on tutorial but things go crazy when i generate the drive rig.

it's important to make sure that the scale of the driver rig & the which should get animated is 1.

@@girlxsenpaigaming263 I can't even generate a face rig, it seems like in the video the parent locator he's talking about is called face_Motion_, but in mine the parent locator that moves all the empties is called 'cgt_HeadController'. There is a locator called Face_Motion_ but it doesn't seem to be affecting anything after you apply the translation and rotation. The capitalization is also different than the video which leads me to believe that he updated the code since then and there might be a bug? Even if I try to scale the generated face rig it stays scrambled.

Hello I was having the same issue! Then I realized I needed to change my input device to IOS and it worked!

Currently it's just available for iOS. Guess in a couple of years it will be available for Android too :)

to transfer the action you need to use a generated rigify face rig. on the generated rigify face rig you can just select the action in the action editor (action are stored in the scene and don't depend on a certain object). Hope that helps :) Planning to make again a video about this topic as I have a small usability update in mind

@@cgtinker I got it working. If I concentrate on full driver--> armature rig-->mesh I can get things working. When I just try to move the action from the driver to just the armature rig I can't do it. Anyway all good now. I will link to you on twitter if I get a video going.

The list of available rig types appears in the Bone properties tab when the bone is selected in Pose Mode. Scroll down the Properties editor to find Rigify Type panel.

well, kinda, but you gotta create a rig for that and prolly calculated some data to get there. I don't think it's possible to automate something like this, shape keys are probably the closest but still, it requires user effort

it's only made for the phone app (didn't even know mocha pro till now tbh :P)

working on another tool which will have drivers. but it isn't rdy yet.

@@cgtinker Oh that would be great. Because I have a model which is already rigged with bones and cost me a lot too lol. Just a shame I cannot just copy the driver directly to it.

@@cgtinker Any progress on this? I am in a similar predicament where I have a rigged model, and the rigify bit is possible but not efficient in terms of workflow. But great job on this addon, it's a life saver for short film makers.

Are you sure that you selected the same action? Did you check if the driver rig contains keyframes? Is the rigify rig you want to transfer too "generated" (doesn't work with just the meta rig)?

I had the same problem - I'd forgotten to do a Rigify Generate Rig on my destination face (at 02:30 in the video)

i had thought i had this problem, but what was actually happening is because i had to scale the transfer back down to scale 1 to get the bake to not mangle, the resulting movements were invisible on the larger scale rigged model

the add-on is meant to be used in a specific way and currently is not a one click solution. I consider to make the process easier soon and update the tutorial. In this tutorial, empties are in local space of the parent object which gets scaled. after generating the rig it's important to apply the scale, otherwise weird deformations occur on the generated rig in step 2.

@@cgtinker Thank you for getting back to me. After tinkering a while, I realized that the error was totally on my side. Your add-on is amazing! Do shape keys help synchronize the many data points on the face for by example the eyelids? I get some weird deformations of the eye lids as the facial recognition does not perfectly capture blinking, and similar micro-movements. But judging the add-on as a whole, you sir, have done an amazing job. Thank you so much for providing this wonderful too for us for free!

@@bifrostbeberast3246 glad you got it working! thanks :)

it's supposed to be used with rigify (the metarig also uses the 'superfine')

are you using iOS or android? iOS X+ is required for face tracking

caution: the transfer only works to rigify face rigs. 1. enable rigify, select the rig and go in pose mode. 2. press n, in the rigify panel you can easily convert actions from euler to quaternion.

@@cgtinker It worked! Thanks!

@@cgtinker Also, just a suggestion, I don't know if it's possible or not but if you use mediapipe for creating face empties then it'd be very easy to use the add-on because mediapipe works with any webcam plus it can also track body and hands as well.

​@@vishvaspancholi5362 Thanks, I'll look into it in the future. It seems promising! At the moment I'd like to do a simulation tool first and take a lil break from ar - but I'll stay updated

@@vishvaspancholi5362 made some tests with mediapipe, damn it's fun! maybe it's going to be the next project lol.

You have to be in edit mode

Try blendarmocap, it's better suited for more cartoonish characters. Will soon make a video on how to manipulate results

yes, I only run patreon atm

Day 4 the rig only generates 1 eye and vanishes these MOCAP youtube tutorials are soooooooo bad non of them are usefull

possibly you scaled up either of the rigs and didn't apply the scale?

After transfering just stash the animation in the action editor. Then you have a nla strip you can easily work with in other projects.

@@cgtinker What i meant is to save the rig itself so i don't have to reconstruct it everytime i need to use it for a different animation.

@@1murkeybadmayn not really sure if I understand the question. usually you rig a geometry bind it and use it as character. If you use a rigify rig while doing so, you should be able to transfer the animation to the characters face using the add-on. Animations on a rig can be stored on the character as nla strips (to reuse them). The usual workflow to do so is baking the animation and stashing the result.

@@cgtinker No I meant to resue the rig itself not the animation. Beause I don't want to have to rebuild it for something else but nevermind. I have a bigger issue. I did the weightpainting thing but my neck is still deforming even after adding the support bones. I don't know what is going on. You also mentioned shift click the bones when weight painting, what does this mean because I cannot click on the bones when weight painting.

@@cgtinker @cg tinker Does not matter. The weight painting did not work, the nla animation just disappears once you quit blender and reopen blender anyway, it does ot save. Also, after baking the rig and transfer of the animation, it just broke my model as half the face was separate from the model. The eyes and did not bind to the bone and the head separated from body of my model. I tried to follow every detail in the video, very frustrating for a whole week I was at this and still end up with nothing working. Overall, it was very hard to follow your video. The video is not in sync with the instructions in the video and it was too fast even when I played it at half speed and you skipped some bits when you were clicking, had no idea what you clicked to get certain things up. I think you should take time to do the demostration while talking not doing the audio and video separately. Would also help if it was slower and not skip parts in what you're doing so we can follow it.

The app requires ar core support

made the process easier in v2.2.0 ;)

@@cgtinker thanks your works insane

What happens? I don't fully understand the issue.

When i push generate driver rig button empties that situated in the eyes region captured but all other not. So eyes got the movement, lips end others empties doesn't

I named armature 'rig' as you advised in previous comments also

@@sairuzzz thanks.. hm.. guess the import data is from iOS? there shouldn't be renaming necessary. best is to just leave the names of driver and base rig by now. I think it's only an issue if your actual character face rig is named 'rig' as rigify always names generated rigs 'rig' which can lead to uses. I wasn't able to reproduce this, which blender version are you using? the empties contain a proper animation?

@@cgtinker, i'm on the 3.1 ver. I consider myself as android user:), (mocap made by android app). Problem is that mocap empties from lips didn't respond to drive rig after i generate it

It's supposed to be transferred to another generated rigify rig, not the control rig. The idea is to have a face rigged with the generated rigify face rig and transfer the animation of the driver rig to it

@@cgtinker Yes, I get the idea. The driver rig has the animation that came from the video, which is then copied to the rig that controls the face, which is the control rig. (You gave it that name yourself in the video, hence I named it that way). So after copying the animation, the control rig and the driver rig should move in sync, yet my control rig doesn't move at all. Even though the animation data seems to be copied, as I can see it on the right side under "Animation".

@@nilslemke7542 weird, can you send me the blend file at hello@cgtinker.com? I'll take a look. Probably something went wild. Preferably send it without any meshes (to reduce attachment size)

@@cgtinker I realised that I was just stupid and didn't see you clicking "Bake To Action" because there was a cut right before it and it went so fast. 😅 So after that, it worked.

some bones can only be rotated, others can also be translate. make sure you are in pose mode, navigate to the armature tab and make sure you have activated the bone layers containing the ik bones. (sadly that's a step hard to describe without visuals, just google bone layers) in pose mode you can transform the bones. the "red" bones from rigify are usually IK drivers - those usually can be moved around freely. Yellow bones are usually only for rotations. The green ones are getting driven, so u can basically ignore them.

Here's the error in full: location: :-1 Error: Python: Traceback (most recent call last): File "C:\Users\tim_r\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\blendartrack-main\src\interface\Operators.py", line 56, in execute input_manager.generate_driver_rig() File "C:\Users\tim_r\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\blendartrack-main\src\management\input_manager.py", line 68, in generate_driver_rig rig = armature.get_armature("rig") File "C:\Users\tim_r\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\blendartrack-main\src\utils\blend\armature.py", line 10, in get_armature armature = bpy.data.objects[name] KeyError: 'bpy_prop_collection[key]: key "rig" not found' location: :-1

@@penniesonoureyes3436 I got the same error in blender 3.0 :(

@@maiers24 this may happens because your diver rig name isn't 'rig' - the current version is using hard coded naming conventions (which I'll fix soon).

some older devices are not supported by ArCore, google for ArCore supported devices and you'll find a list

@@cgtinker ah that would explain it then - thanks!

Yep it's possible. You can check out ' the add-on game rig tools' if U like. It's optimized for exactly this process. My add-on focusses only on the transfer to humanoid rigify rigs

@@cgtinker thx for the fast answer. Seems I overcomplicated the whole thing. (Take a sleep and going with fresh eyes to a problem works wonders^^) Found a streamlined workflow to incorporate blendartrack + mocap fusion + metahumans (ok getting metahumans to blender and get them working is horrendous). Your app integrates flawless with mocap fusion, runs on android + you don't have to define 42 shapekeys in a character face to get it working. Unlike the iphone app.

ar core support is required, here is a list of ar core supported devices, cannot rly do anything about that :/ developers.google.com/ar/devices

@@cgtinker heya thanks for the quick reply!

Did you select the device type or changed any bone names?

@@cgtinker i did not change any bone name, wich one is the device type?

oh!!, it was IOS not android!, i'm gonna try again. thanks!!

Most likely your device doesn't match the system require of your device. there are lists from google and apple for ArCore and ArKit supported devices respectively. ArCore or ArKit is required to run BlendArTrack