On the subject of labels, it would be nice to be able to create specific label/preset maps for separate instruments/instrument setups, and access them easily from the track event page.
Thats no problem if you give me a list/some concrete ideas
Even better, if I can just dump them as an easily editable text file into the root of the SD card. For example in the drum case, I have a modular drum machine and a couple others (Drumulator, Ensoniq Mirage) that respond to MIDI. It would be nice to have a preset map with labels and midi notes for each of these instruments, so that I can quickly just select the instrument I want and start programming. If I could set up preset label/note maps for each of my instruments, my workflow would speed up 200%.
It was clear to me that sooner or later somebody will request to load predefined labels/maps from SD Card.
But the reason why I don’t store them in RAM is neither lack of programming skills, neither lack of time, but just because I want to reserve the remaining 4k RAM for more useful features.
There could be a way to transfer a .txt file from SD Card into flash memory later.
Or alternatively: to provide different preset patterns stored in a special bank. Would the availability of preset patterns really slow down the editing process so much - would a text file entry complicate the editing process too much? What would people prefer? (I for myself would prefer to edit preset patterns directly from the MBSEQ CS instead of using a text editor)
But so long nobody sends me ideas for labels/drum maps I’m not sure how much memory should be reserved for this. In addition, I will have to balance the memory usage with the required code size for future features.
My proposal: write a new forum topic in the MBSEQ section with a list of your label/drum map ideas.
Let other users add their own ideas.
This should give me a good overview about the requirements, so that I can implement the appr. functions into the firmware quickly w/o the fear that I will have to change the programming concept again and again due to new requirements.
Hi Thorsten – thanks for your reply and your attention to my request!
I completely agree – Your suggestion of “preset patterns” or “pattern templates” is absolutely perfect, at least for me. I would have no real need/desire to have additional drum/instrument maps or presets if this is the case.
Here are a couple suggestions that would fit my personal needs:
Instead of saving pattern to bankstick, you have the option to save it to a new “pattern template”… it would not save any of the sequence data, just category/track/drum labels and track mode configuration. The name/label of the track would become a new option when scrolling through track event modes in the “track event” page.
Or alternately, a special track event mode could be set up to inherit track event properties/labels from another pattern. Then any saved pattern could be used as the “template”.
As far as number of allowed templates, 16-32 would be more than enough for me.
I will post on the SEQ forum as you’ve suggested, I just wanted to share my feedback here first. Thanks!
Instead of saving pattern to bankstick, you have the option to save it to a new “pattern template”… it would not save any of the sequence data, just category/track/drum labels and track mode configuration. The name/label of the track would become a new option when scrolling through track event modes in the “track event” page.
Or alternately, a special track event mode could be set up to inherit track event properties/labels from another pattern. Then any saved pattern could be used as the “template”.
How about following implementation (I think that this is feasible without much programming effort):
template tracks can be stored as separate files into a special directory (e.g. presets/*.V4T)
parameters are stored in text format, so that they could also be edited from a computer
they can be selected in the Track Event mode page as suggested
they can also be stored from there (last item in list “Store new Template”)
while importing a template it will be possible to selected parameter groups which should be inherited (e.g. Name, Chn, Layer Config (e.g. to import a drum map only), Steps, All)
As far as number of allowed templates, 16-32 would be more than enough for me.
By storing templates into files the number of patterns wouldn’t be limited, and we could easily share the presets
Any other ideas?
I will post on the SEQ forum as you’ve suggested, I just wanted to share my feedback here first. Thanks!
I splitted the thread and moved this part into the MIDIbox SEQ section.
This is great! I was thinking to request something like this after upgrade to new core.
This will ease usage for sure. I have few friends who love to work on mbseq but I noticed that setting track event page (midi ch, port, etc.) is hardest thing to understand for them.
I do it in few seconds because I know connections. Named presets are great. Excellent work TK!
