You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, the authers, thanks for sharing this great work!
I have some questions about the Pixel Controller.
As you mentioned in the paper, the pixel controller is responsible for integrating the fine-grained object appearance, the image latent of the reference image (named "ip_img" in your code) is introduced by concatenating it with other view images along the "batch" dimension. To the best of my knowledge, the new added "batch item" still need "noise" to achieve mse loss. Could you give more explanation about how to train this pixel controller module?
I will be very grateful for your. Looking forward to your reply!
The text was updated successfully, but these errors were encountered:
I am curious about it, also. Unlike Wonder3D and MVDream that leverages multi-view attention without an explicit reference image latent, this pixel controller does need an appropriate process about the predicted noise over ref img latent during training.
Hi, the authers, thanks for sharing this great work!
I have some questions about the Pixel Controller.
As you mentioned in the paper, the pixel controller is responsible for integrating the fine-grained object appearance, the image latent of the reference image (named "ip_img" in your code) is introduced by concatenating it with other view images along the "batch" dimension. To the best of my knowledge, the new added "batch item" still need "noise" to achieve mse loss. Could you give more explanation about how to train this pixel controller module?
I will be very grateful for your. Looking forward to your reply!
The text was updated successfully, but these errors were encountered: