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
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:
It is nice to have the bank as imported in case I want to dump it all to the synthesizer. without using an external sysex program.
Sometimes, duplicate patches exist in the import and it only imports unique patches (awesome), but that is confusing when I want to reuse the "bank".
If I want to recreate a user bank from the import, I need to drag each patch one at a time (very time consuming). This is even more difficult when duplicates are skipped in the import and I would need to search/find skipped patches in my library to recreate the bank file that "technically" already exists.
Thank you in advance for your support and time working on this amazing tool.
The text was updated successfully, but these errors were encountered:
christofmuc
changed the title
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..
Create banks during import
Oct 18, 2024
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.
Originally posted by @troach242 in #350
The text was updated successfully, but these errors were encountered: