Some of the feature requests in the poll are already implemented in the octatrack or not formulated clearly; I have some comments and questions about some of them:
- recording of note length and velocity in trackmode (like midi)
What do you mean or hope to achieve by this? I really don’t understand.
- easy sampling preset (or the ability to set it up globaly settings)
There is a quick recording method and you can set it up for the entire project. Project management update could solve any problem you have with the current method of setting up preferences.
- slide between patterns or banks
This is not going to happen, you could use crossfade/resample tricks, but that’s not the same. To actually slide between two patterns or banks requires two octatracks. But hey, they used to say the earth was flat, so who knows.
- Quick sample slice mode
Very subjective, I personally like the current slicing method and think it’s fast and flexible enough. Also I, and again personally, would not like to get used to a new way of slicing.
- Lock stop and play buttons while performing
Subjective again, it could be a feature, but there are many situations where someone would want to pause or even stop the octatrack during a performance.
- Consistancy for button operations
This sounds more like a complaint than a feature request. I agree that it is not the easiest interface out there and it could be even more complex if you’ve been through some of the previous updates. But don’t you think changing the button operations for more “consistency” would create problems for those who familiarized themselves with the current button functions? A bit of a catch-22 if you ask me.
- Track volumes and scene assignments stored in pattern
This is what ‘parts’ are for. Use four patterns to a part. And try to look at it as 1 song per bank, 4 parts per song with 4 patterns each.
- Save all button (all parts/patterns on all banks in the project)
There is a ‘save project’ button, right?
Don’t take any of these comments the wrong way, I usually avoid the feature request threads and work with whatever a designer throws at me. But in this case I’d like to see some things implemented in the OT and I like the thought that the designers might actually read a thread like this. So make sure any list of requests is on point, simple and perfect to increase the chance of anything actually being implemented!