Talking-Face-Generation-DAVS
Talking-Face-Generation-DAVS copied to clipboard
ValueError: expected 2D or 3D input (got 4D input)
Hi.
I run python test_all.py --test_root ./0572_0019_0003/audio --test_type audio --test_audio_video_length 99 --test_resume_path .\checkpoints\101_DAVS_checkpoint.pth.tar
and see error
Traceback (most recent call last):
File "test_all.py", line 47, in
What can be fixed here ?
Same error here.
To solve this use the pytorch version mentioned (0.2.0)
Hello, Pytorch1.0.0 can also solve this problem. Thank you for your reply.
------------------ 原始邮件 ------------------ 发件人: "JAlexander"[email protected]; 发送时间: 2019年5月14日(星期二) 晚上6:44 收件人: "Hangz-nju-cuhk/Talking-Face-Generation-DAVS"[email protected]; 抄送: "十二象"[email protected];"Comment"[email protected]; 主题: Re: [Hangz-nju-cuhk/Talking-Face-Generation-DAVS] ValueError:expected 2D or 3D input (got 4D input) (#21)
To solve this use the pytorch version mentioned (0.2.0)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
@XRSWATER tried Pytorch1.0.0 but didn't work... Because torch 0.2.0 does not support cuda > 9.0 having trouble to run the code. Do you have any alternative solution?
I changed BatchNorm1d to BatchNorm2d and error disappears. But 'missing keys in state_dict' warning occurs. Don't know this is proper way to do so
Hi all, this is caused by a bug that I wrote which surprisingly did not affect the performance... @DongHwanJang I tried directly changing it in this way but the performance would be hurt.
Tried changing BatchNorm1d to BatchNorm2d and the error disappeared. But 'missing keys in state_dict' warning occurs and the fake images created are black.
im using Pytorch 0.2.0 And Cuda 10. On Google Colab
@Hangz-nju-cuhk Can you help please?
hi guys, so, how to overpass this issue? I've tried different versions of pytorch, but still have "ValueError: expected 2D or 3D input (got 4D input)"
no solution for this issue?
change self.bn1 = nn.BatchNorm1d(64) -> nn.BatchNorm2d(64) in mfcc_networks.py. and the issue fixed in my env.
Who can have a better solution now? Can you provide the version of your requirements.txt? thanks