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
Is your feature request related to a problem? Please describe.
Having used Amplitude for several days now, it is proving to be an excellent program but the setup and maintenance of large soundboards and clip lists quickly becomes rather tedious. My previous Issue #90 addressed this but I am creating this feature request to supersede that one as this is a more generalized UI revamp that addresses the same core issues.
Describe the solution you'd like
Add the ability to do the most common file and sound clip management functions via drag and drop in addition to the current button-based system.
For example, sound files could be dragged from an external file manager window into a sound clip list window where they would all receive sound clip entries that are autopopulated with the filename as a temporary clip name until manually renamed by the user.
Sound files could also be dragged onto a soundboard button which would autopopulate the parent sound clip list as above. In cases where the user is making a large and complicated soundboard, the process of having to open a file open dialog, navigate the filesystem, copy the clip and paste it into a soundboard button very quickly gets tedious and error prone. In my experience, the existing UI is sufficiently complex that I often found myself loading a sound clip into the wrong button and having to move them around later or accidentally skipping a file or loading one twice by accident. Being able to simply drag and drop would make these sorts of mistakes less likely. Being able to just start dragging sound clips into a soundboard is a much more intuitive and straightforward process. The user would still have to manually rename the sound clips from the filenames but this is far less work. (and if the sound files have sufficiently informative filenames, this step may not even be necessary in many cases)
Soundboard buttons could be populated from clip lists by dragging existing clip list entries to them rather than the copy/paste mechanism currently implemented.
Soundboard buttons could be dragged around the soundboard to reposition them rather than the current method where the user has to copy/paste them around using an extra dummy button for the overflow which then has to be emptied out later.
Another feature that would be nice would be to be able to drag output profiles to the entries in the clip list. This would require another window that lists all the sound profiles but that would be a nice feature on its own to help with sound profile management. This relates a bit to #51 as the creation of a sound profile management window would allow the solving of that issue as well as the ability to drag/drop manage the assignment of the output profiles.
Although implementing a drag and drop UI mechanic to the application would require a significant overhaul of the UI, it would significantly streamline the workflow.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Having used Amplitude for several days now, it is proving to be an excellent program but the setup and maintenance of large soundboards and clip lists quickly becomes rather tedious. My previous Issue #90 addressed this but I am creating this feature request to supersede that one as this is a more generalized UI revamp that addresses the same core issues.
Describe the solution you'd like
Add the ability to do the most common file and sound clip management functions via drag and drop in addition to the current button-based system.
For example, sound files could be dragged from an external file manager window into a sound clip list window where they would all receive sound clip entries that are autopopulated with the filename as a temporary clip name until manually renamed by the user.
Sound files could also be dragged onto a soundboard button which would autopopulate the parent sound clip list as above. In cases where the user is making a large and complicated soundboard, the process of having to open a file open dialog, navigate the filesystem, copy the clip and paste it into a soundboard button very quickly gets tedious and error prone. In my experience, the existing UI is sufficiently complex that I often found myself loading a sound clip into the wrong button and having to move them around later or accidentally skipping a file or loading one twice by accident. Being able to simply drag and drop would make these sorts of mistakes less likely. Being able to just start dragging sound clips into a soundboard is a much more intuitive and straightforward process. The user would still have to manually rename the sound clips from the filenames but this is far less work. (and if the sound files have sufficiently informative filenames, this step may not even be necessary in many cases)
Soundboard buttons could be populated from clip lists by dragging existing clip list entries to them rather than the copy/paste mechanism currently implemented.
Soundboard buttons could be dragged around the soundboard to reposition them rather than the current method where the user has to copy/paste them around using an extra dummy button for the overflow which then has to be emptied out later.
Another feature that would be nice would be to be able to drag output profiles to the entries in the clip list. This would require another window that lists all the sound profiles but that would be a nice feature on its own to help with sound profile management. This relates a bit to #51 as the creation of a sound profile management window would allow the solving of that issue as well as the ability to drag/drop manage the assignment of the output profiles.
Although implementing a drag and drop UI mechanic to the application would require a significant overhaul of the UI, it would significantly streamline the workflow.
The text was updated successfully, but these errors were encountered: