Skip to content
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

Why encoder_hidden_state is used in the motion module? #125

Open
junwenxiong opened this issue Feb 29, 2024 · 0 comments
Open

Why encoder_hidden_state is used in the motion module? #125

junwenxiong opened this issue Feb 29, 2024 · 0 comments

Comments

@junwenxiong
Copy link

I'm curious why encoder_hidden_state is used in the motion module? The motion module as expressed in the paper is a vanilla temporal attention, not cross-attention.

hidden_states = motion_module(hidden_states, temb, encoder_hidden_states=encoder_hidden_states) if motion_module is not None else hidden_states

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant