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
I'm sure many of us have a large number of convolver impulses for all occasions. And many impulses have the same purpose, but realize it in different ways. For example, surround sound impulses, equalizers, various filters, bass amplifiers and many others. What I suggest is to add the ability to group these impulses. For example, give the user the ability to create “collections” of pulses. And in the impulse selection interface, offer to select a collection (if any have been created) and then select an impulse in it. This will make it possible to conveniently structure impulses and not to search for the right one among the others every time. All impulses that are not in a collection should be simply displayed in the same interface, under collections. Also, it would be cool if you could share these collections. For example, we could pack all the impulses in a collection into a zip file, which would contain a text file with the collection name and other parameters, if any. Such a structure would allow users of other processing applications to get such a collection and use impulses from it without any fuss.
The text was updated successfully, but these errors were encountered:
conordy
changed the title
Suggestion - Ability to group pulses
Suggestion - Ability to group impulses
Dec 7, 2024
I'm sure many of us have a large number of convolver impulses for all occasions. And many impulses have the same purpose, but realize it in different ways. For example, surround sound impulses, equalizers, various filters, bass amplifiers and many others. What I suggest is to add the ability to group these impulses. For example, give the user the ability to create “collections” of pulses. And in the impulse selection interface, offer to select a collection (if any have been created) and then select an impulse in it. This will make it possible to conveniently structure impulses and not to search for the right one among the others every time. All impulses that are not in a collection should be simply displayed in the same interface, under collections. Also, it would be cool if you could share these collections. For example, we could pack all the impulses in a collection into a zip file, which would contain a text file with the collection name and other parameters, if any. Such a structure would allow users of other processing applications to get such a collection and use impulses from it without any fuss.
The text was updated successfully, but these errors were encountered: