-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can I use the existing code to do expression transfer #6
Comments
Yes, the current code supports it, however, I did not upload the relative expression generation script. I maybe release this part as well. You just need to have the corresponding transforms.json file and meshes. |
thanks for your answer. I also wanna know how to render images with existing checkpoints. |
You can use |
I use "render_from_snapshot":true, and set the --scene, --no-gui, --snapshot, It seems nothing happens. And after I train a scene, the max_steps is fixed. I change the max_steps and use --snapshot, the traing shows the initial max_steps. |
You are right there was a bug. Now it is fixed, you can also specify |
It doesn't seem to work. |
I am using:
{
"parent": "main.json",
"max_steps": 33000,
"max_cached_bvh": 4000,
"max_images_gpu": 1700,
"use_dataset_cache": true,
"render_novel_trajectory": false,
"render_from_snapshot": true
} The output should be in |
I use the same config, the code only outputs after training. When I try to render reults again, nothing appears. |
Hmm, have you pulled the newest changes and rebuilt the project? |
@lsx0101 it is just replacing the previous files in the debug/overlay folder |
it works, but the rendering quality is not as good as training expressions |
I'm gettin these results; imperfect rendering and transfer, is anyone getting better output? Studio_Project_V3.mp4 |
Thanks for your solution for headless trainging, it works well.
In the Supplemental Document->B. Applications, the expression transfer results are attractive. Is it possible to do expression transfer with the existing code?
The text was updated successfully, but these errors were encountered: