With this change, the function should be executable. The remaining problem is,

  • Give a name to each label.
  • Set the minimum, maximum and step correctly.
  • If gr.Number is better than gr.Scale, change it.
  • Where it's a gr.Textbox, it can be gr.Dropdown or gr.Radio.
  • Give choices the right choices (list).
  • There is a place where the numbers are string, what should we do about this?
  • What about the layout? Like the side-by-side part.
  • If there are parts that need to be kept out of the tab, we need to decide on that as well.
    and so on.
Owner

i Cannot merge

it says: This branch has merge conflicts in the following files:
app.py

Owner

@John6666 you can pull request again

Blane187 changed pull request status to closed

I did.
And about Gradio's layout.
https://www.gradio.app/guides/controlling-layout

Owner

thanks

fine.

By the way, the others are all about looks in the end, but this one is essential.
If you want to treat it as a number, you need to receive it as a float or int in the receiving library, round it up, and convert it to str, otherwise it is hard to handle in Gradio.
If it was originally a number to be treated as a string, there is no problem.

    min_pitch="50",
    max_pitch="1100",
Owner

okay

I completely forgot to mention that the " #" is a code word for myself, meaning under construction or to be fixed later...๐Ÿ˜“
Please erase it when you fix it.

Owner

okay, don't worry

Sign up or log in to comment