-
Notifications
You must be signed in to change notification settings - Fork 245
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
ERROR: Boolean value of Tensor with more than one value is ambiguous #9
Comments
Hi! Thanks for reporting this issue. Could you please provide me with more context into the issue? (E.g. stack trace, inputs, screenshots etc) |
hi @evonneng sure thing!
This happens after recording audio in the gradio app and starting the generation, thanks! |
Ah I see! I believe the issue should be because the max function is returning more than a scalar value (eg if your audio recording is 2xT for binaural audio). Currently I am only supporting single channel audio. But I can push a fix later to combine your audio to single channel and ping this thread after! |
Nice one, I found this if it helps just changing it client-side; |
And something I found for a possible solution in python; |
Okay, as a quick workaround, I updated line 241;
then recorded an mono audio track in Audacity to mp3 and uploaded, seems to now be running |
Okay, I got a generation, but the audio is VERY quiet - unsure what happened here, source seems fine. I'm just tuning the ffmpeg step to see if I can speed things up here |
Adding |
Hi @chrisbward did the issue eventually resolve? In my case, I first got the 'Boolean value of Tensor with more than one value is ambiguous' error originally but it resolved after I used a mono audio. However, a new error ensues:
I wonder if anyone has an idea how to fix this. As it suggests, it has to to do with unmatched tensors due to the |
Thank you all for such active help on these issues! Hi @MustaphaU , it seems that results from the auto-generated mask size not matching that of the audio conditioning tensor. I am not too sure why that might be the case (since it would require more downstream information), but could you please try the above fix in the PR to see if it solves it? I wonder if it is because the audio is somehow getting corrupted downstream... |
Closing this for now due to inactivity. But please feel to reopen if there's more issues related. Thanks! |
This is when running the demo
The text was updated successfully, but these errors were encountered: