Is your feature request related to a problem?
A clear description of the problem.
When I want to preview a voice engine, I click it and begin previewing it. But the preview is occurring at the top of the voice engine page, and I'm down in the middle of the page and can't see it--I have to scroll up.
Describe the solution you'd like
What you want to happen.
Could the voice engine preview (as well as the selected voice model when not previewing) be held frozen in a row locked to the top of the page?
Describe alternatives you've considered
Other solutions or features you've considered.
I wondered whether maybe the page was too long, but I actually think it's fine on reflection.
Reviewing alternative implementations, I understand there's also the option to integrate the preview feature into the row of the model the user clicks on. So, the model upon click, the row that the model occupies becomes a preview row. But I like the idea of keeping the voice engine at the top of the page like you've already designed it.
Automatically scrolling to the top of the page may cause the user to lose their place below, so I won't suggest that.
I now see the model preview and the active model are separate. I'm not sure how much sense this distinction makes--will have to think about it. (My first thought is about a comparison mode, or at least a visual "active vs. preview" comparison, but those would be separate pieces of feedback!) Bit of a tangent now:
Some prioritization could be given to downloaded models. One way to think of it is kind of the life cycle and sophistication of the user. The needs of a first time expert user are much different from a beginner who's been using the software for months. The beginner never wants to be confused by too many options, but even the expert will eventually settle on their favorite models until new state of the art models come along. Are we going to the model page to just swap the model that we're using and we know what we're looking for? Or are we in discovery mode interested in downloading and testing a new model?
After that blabbering, some homework for myself might be to think about how comparisons can be done differently; think about segmenting the whole Voice Engine page to offer different experiences for comparing versus selecting models.
Also-
Users on big screens or users selecting one of the first few models shouldn't be impacted by this.
Additional context
Any other context or screenshots.
FluidVoice 1.5.11-beta.3
The preview of this Whisper model is happening at the top of the page off screen:
Is your feature request related to a problem?
A clear description of the problem.
When I want to preview a voice engine, I click it and begin previewing it. But the preview is occurring at the top of the voice engine page, and I'm down in the middle of the page and can't see it--I have to scroll up.
Describe the solution you'd like
What you want to happen.
Could the voice engine preview (as well as the selected voice model when not previewing) be held frozen in a row locked to the top of the page?
Describe alternatives you've considered
Other solutions or features you've considered.
I wondered whether maybe the page was too long, but I actually think it's fine on reflection.
Reviewing alternative implementations, I understand there's also the option to integrate the preview feature into the row of the model the user clicks on. So, the model upon click, the row that the model occupies becomes a preview row. But I like the idea of keeping the voice engine at the top of the page like you've already designed it.
Automatically scrolling to the top of the page may cause the user to lose their place below, so I won't suggest that.
I now see the model preview and the active model are separate. I'm not sure how much sense this distinction makes--will have to think about it. (My first thought is about a comparison mode, or at least a visual "active vs. preview" comparison, but those would be separate pieces of feedback!) Bit of a tangent now:
Some prioritization could be given to downloaded models. One way to think of it is kind of the life cycle and sophistication of the user. The needs of a first time expert user are much different from a beginner who's been using the software for months. The beginner never wants to be confused by too many options, but even the expert will eventually settle on their favorite models until new state of the art models come along. Are we going to the model page to just swap the model that we're using and we know what we're looking for? Or are we in discovery mode interested in downloading and testing a new model?
After that blabbering, some homework for myself might be to think about how comparisons can be done differently; think about segmenting the whole Voice Engine page to offer different experiences for comparing versus selecting models.
Also-
Users on big screens or users selecting one of the first few models shouldn't be impacted by this.
Additional context
Any other context or screenshots.
FluidVoice 1.5.11-beta.3
The preview of this Whisper model is happening at the top of the page off screen: