Forum index > Feature request

UI idea suggestions

Colin Muir Dorward
I've been using my EFM loads lately; still loving it. These are some things that I would change if I could!

1) When I select the LFO to be midi/tempo synced, the sync-setting parameter appears bellow the button, and the LFO speed parameter becomes inactive. Why not just have the speed parameter switch to the sync-setting parameter? Then there is another free spot to put in a new function/button :)

2) The LFO attack parameter should be called "Attack Speed". Most attack controls are attack *time*, meaning the higher the value the slower the attack, but in EFM, it's opposite, so it could be labeled as such, just to make it absolutely crystal clear and easy to remember.

3) The 6x6 operator grid takes up a lot of space. I have yet to use a 1x6 tower of operators even once, meaning that in my case, that top row is 100% unused space... I would gladly give up the chance to use1x6 the tower algo in exchange for more buttons up there.

4) When I click on an OP I get a "Base" tab. When I click on the blank part of the algo grid, I get the other voice-level "Base" tab. Maybe you could call the OP Base tab "OPbase" or just "OP"? It hurts my brain when I'm quickly switching views and have to figure out which "Base" tab I'm looking at.
KODAMO
Thanks for the suggestions. They mostly make sense, and UI changes are usually easy to do. 1) 2) and 4) probably will be done after we checked they have no impact on usability.
For 3), what buttons would you put into that space?
Colin Muir Dorward
Good question, I didn't want to weigh in on that subject without thinking about if there were any functionality additions that might need that space, or if it would more preferably used for UI/speed/usability tweaks.

I'll pay attention to that area during my next session and see if I find ideas for any UI/speed-of-use enhancements.

I wouldn't want to close the door on any functionality enhancements however!
Colin Muir Dorward
Yeah I guess my vote for that top-row space would be for two buttons:
1) free running envelope on/off
2) tie envelope time-scale to midi tempo on/off. I think this could be a global setting for all envs rather than need a dedicated setting for each env.
traffkin
imo, no routing feature should be sacrificed. i personally use cascading mod structures quite often
Colin Muir Dorward
imo, no routing feature should be sacrificed. i personally use cascading mod structures quite often

I actually think that space could be used without sacrificing any routing/algos. With only six operators... is it even possible to have more than one OP in the top row?
Colin Muir Dorward
Another suggestions:

When you switch operators, focus should remain on the same parameter (the one last edited).

So lets say I'm editing the y-axis valueof env-breakpoint-3 on OP1 with the large jogwheel: when I select OP2, the focus should immediately be on OP2 env-breakpoint-3.

The way it works now is as soon as you select a new operator, the jog wheel becomes a scroll-tool to navigate to a new operator (since this is effectively the last field you brought focus to). I find this very confusing and not handy because we loose the ability to rapidly step through the OPs and edit the same Y-axis value on each.

Does anyone ever use the jog wheel to select an op? IMHO it's much faster to select your OP simply by touching it.
fcorona
I second this last suggestion, it would surely be a time saver, and I've yet to select an operator with the jog wheel

Reply