Replies: 1 comment 2 replies
-
That's a great feature idea! It shouldn't be too hard, as banks are stored internally just as lists of pointers to patches in the Library, so effectively it would be just to create a list of type "bank" after the import. It will be harder to figure our which bank was imported - this is not always possible, as some synths just send a stream of edit buffers as bank dump (e.g. Access Virus), and there is no information which bank had been selected. But that's certainly easier than having to recreate the bank after import. On another idea, the Imports feature is still to be migrated to be proper Lists as well, and then you could drag an import list into a newly created bank - that would not be the same as creating the bank right away, but would avoid the drag one by one issue. I need to look and see what is the easiest and most compatible addition! I will create a proper enhancement issue from this thread. |
Beta Was this translation helpful? Give feedback.
-
When working with my existing synthesizers, example SQ-80, when I import a bank from a file, an import log is created. This works Ok, but it would be more useful for me if when importing a bank sysex file, a user bank was also created with all of the patches in it. The work was already done by the bank sysex file..
A few challenges occur for me:
Thank you in advance for your support and time working on this amazing tool.
Beta Was this translation helpful? Give feedback.
All reactions