My suggestion on improving on the pattern copy framwork
Posted: Tue Oct 06, 2015 7:10 pm
This was discussed in a previous request but Ill restate it here as it relates to what I think is a very significant improvement in how users can use the app. I've said before a lot of features are hidden or obscured by buttons having multiple different functions. Naturally with experience in the app and time spent with the documentation and discussion forum you learn more but I think the menu pages can continue to be built upon.
For example the menus use lists with small check boxes. I personally believe they would look and feel better if they were more graphical, even if they were just tabbed pages with smaller lists and larger buttons.
For example when swapping elements in patterns or soundsets, samples, tracks, automations, whatever, rather than one long list there could be a page organized by track, so tab 1 is track one, tab two track two etc. Within the tab there are different headings, Sample, sequence, automation, etc. Allow the user to navigate the menu in a similar manner as they would interact with the sampler.
Presently when you need to copy something you need to view the content and select the box. I find it saves time and processing power to start by saving the basics to the entire bank or patternset and then copying the mute solo state only. In other words
Load a pattern
Copy the timing measure, mixer, samples, sample params, and sequences to the entire patternset
Solo the first track and copy the solo mute over to the next pattern
Repeat
The quick fix I'm proposing if its not too much work is to have the menu state remember the last item changed. So for example when I choose to copy a pattern, the menu remembers I want the content visible, the menu remenbers I want everything deselected except the solo mute.
This applies to other scenarios, such as copying and altering parameter automations etc. The menu remembers what the user did last.
The next feature suggestion as already described is to make the list menues more graphical in the same theme as the recently updated menues: pages and bigger buttons.
I believe that inexperienced users with less capable devices might also benefitfromthis style of workflow because every time the entire samller is copied to the next pattern, which is sort of the way the program by default copies things, a lot of ram is used, creating stutter and lag or potential crashing. By doing a big copy once, everything to all slots, then small copies, mute solo, the program runs a lot smoother.
For example the menus use lists with small check boxes. I personally believe they would look and feel better if they were more graphical, even if they were just tabbed pages with smaller lists and larger buttons.
For example when swapping elements in patterns or soundsets, samples, tracks, automations, whatever, rather than one long list there could be a page organized by track, so tab 1 is track one, tab two track two etc. Within the tab there are different headings, Sample, sequence, automation, etc. Allow the user to navigate the menu in a similar manner as they would interact with the sampler.
Presently when you need to copy something you need to view the content and select the box. I find it saves time and processing power to start by saving the basics to the entire bank or patternset and then copying the mute solo state only. In other words
Load a pattern
Copy the timing measure, mixer, samples, sample params, and sequences to the entire patternset
Solo the first track and copy the solo mute over to the next pattern
Repeat
The quick fix I'm proposing if its not too much work is to have the menu state remember the last item changed. So for example when I choose to copy a pattern, the menu remembers I want the content visible, the menu remenbers I want everything deselected except the solo mute.
This applies to other scenarios, such as copying and altering parameter automations etc. The menu remembers what the user did last.
The next feature suggestion as already described is to make the list menues more graphical in the same theme as the recently updated menues: pages and bigger buttons.
I believe that inexperienced users with less capable devices might also benefitfromthis style of workflow because every time the entire samller is copied to the next pattern, which is sort of the way the program by default copies things, a lot of ram is used, creating stutter and lag or potential crashing. By doing a big copy once, everything to all slots, then small copies, mute solo, the program runs a lot smoother.