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
It is unclear to the user what format is required here. While this will surely be addressed in the documentation, this is so important that an explanation of the types of entries and their required formats should accompany this entry field. Specifically these issues:
The user needs to have examples to see what the required format is.
The user won't know what "all" means. For example, does this apply to all pairs, or all voices being considered together, or absolutely every combination in any number of voices available, etc.
Non-sensical entries should prompt the user with a request for an acceptable entry format. I typed "all bananas" in the entry field and that is what showed up on the corresponding part of the "Analysis Settings" page. The user should be prompted before getting to this point.
The text was updated successfully, but these errors were encountered:
I agree this was confusing, but I'm not sure it's such a big problem now that we have checkboxes and better buttons to help users choose voice combinations. (Admittedly, those checkboxes and buttons weren't present in the publically-available Web app when you filed this issue).
However, there's no way "all bananas" should work as a voice combination. We should certainly have better quality control there.
@alexandermorgan could you review the now-current "Analysis Settings" box to see whether it's clear enough?
It is unclear to the user what format is required here. While this will surely be addressed in the documentation, this is so important that an explanation of the types of entries and their required formats should accompany this entry field. Specifically these issues:
The text was updated successfully, but these errors were encountered: