I’m running short on pages on the E1 Mini, now that I’m developing a preset for the Korg DS-8 and Matrix-1000. Would 12 or 16 be possible? Thanks!
And given that we cannot create controls, we can only repurpose existing controls, extra pages give us more controls to pull from.
Not a blocker for me though … and I’ve had good luck just moving a few controls from page to page when navigating and customizing the control for the page’s need.
@FrankieMachine It’s not as convenient, but it’s likely you can use controls that tie to virtual devices that you then change to emulate a page change. That is, can a single page be reconfigured to serve multiple purposes.
My guess is memory is not an issue on the Mini, but if it is, perhaps this is a device level setting for number of pages. That would complicate the editor and sharing of presets…
So far I could just about fit everything into 8 pages, but now that I’m making a preset for the DS-8 I could use 2 more pages.
I’m not familiair with virtual devices, I only use the web UI. I like to keep it simple and focus my time on sound design (and who know, someday, maybe even make some music again).
Have this same problem already. I wanted to made really big preset, and structure of roland jv2080, give me possible to separate it to the 3 modes, one for rythm, withone have 5 pages, one for performance, where i have everything fitted to all 8 pages to the limit, and one for patch, where i use dynamic controls, and can’t fit it into 8 pages. I need like 4 pages more i think for rest of the parameters.
I’m thinking about making one more preset for Patch mode, but i’m not sure, if they will be pinned, the functions in lua code will hear eachother. Like, if i have in preset A some controls turned on, to edit one tone, then preset B will know, what tone are edited to send properly informations? Can it will be defined in Lua code? I really don’t know, how to bite it.
I was trying with hidden controls, changing names of controls, and it make it only worse, i need more pages to make it clear and functional.
1 Like
Just my opinion, but if a machine needs tons of pages, maybe the Electra One is not the best option for a controller.
Computer editor plus Electra One for hands on control of key params might be the better approach.
Again, I love the Electra One for many things (I have 3), but there are limits
2 Likes
I dissagree: a few more pages could release the E1 Mini’s full potential. But I hear an update is coming up, so I keep my fingers crossed.
1 Like
I hate to use computer to make music and don’t even close to utilize half of potential of this hardware. I think, more limits are in firmwire right now. Some functions are really good, some making problems (or just have too small knowledge), but placement of controls are one of the most annoying thing in electra mini. I was thinking about to use blank pages from bigger version of preset, but it was problematic too, and never get answer it is posible. Theoretically wanted to make more pages with button withone when pressed, hide all the page from electra one mini, and place it on electra one 6x6 page, and taking other controls from 6x6 page, and setting it on actual electra one mini page. It was never working, and i give up with trying that.
I respectfully disagree.
I’m actually dreaming of more pages for my MK2, because I’ve reached the limitations of the 12 pages several times for different reasons being:
- That the device I’d like to control has simply too much parameters, but I’d really like to have the full set of parameters immediately reachable. I think that is really one of the goals of the E1.
- That I often use some slots for fast lua navigation between pages (so much faster and more convenient that using the pages menu and the buttons). Actually the big rubber buttons are what I like the least on the electra one and displaying the thin pages menu on the top of the screen does’t work for me. But using slots for navigation purposes consumes a lot of them.
- That some slots can be consumed by hidden controls,to register values from incoming patch sysex to be then converted to the corresponding controls, which do not represent the value the same way as in the patch sysex (for example 0;1 to 0;127). There’s certainly room for improvement via lua for this, but it will be harder to implement for people like me.
It also often limits the possibilities to set up the controls in a consistent, clearly laid out and logical way, because everything is crowded.
Limitations of the pages on my E1 mini doesn’t bother me much because I’ve also got the MK2 and I use my Mini for simpler tasks, but I can well imagine that it can be frustrating for someone that “only” has a mini.
I must also say that, despite those limitations, the MK2 and the Mini are absolutely wonderful devices. 
2 Likes