Forum index > Feature request

EssenceFM feature requests

fish233	Posted on Mon 22 May 2023, 03:07 PM dunno if this is possible: would be great to have an option for seperate edit buffers for patches per performance. if 2 performances share the same edited patch changes in the patch in one of the performances will also reflect in the other. in terms of saving everything per performance it would be handy to be able to switch this behaviour off. also more lfo's would be nice :)
fish233	Posted on Tue 23 May 2023, 02:14 PM another FR: mod matrix on patch level, esp for midi cc control. so you could modify grouped parameters (say, all OP1 volumes from all layers together) for a synth heavily based on layering this makes more sense and it's tedious to assign midi cc for each layer individually. there is a nice free spot for a 4th tab in the patch menu 😉 also being able to activate that modulation per layer, so if you select a modulation slot the layer list has on/off switches on top of the layer name. oh and being able to preview dx7 sysex voices instead of having to load each bank, would be supercool 😇
fish233	Posted on Tue 23 May 2023, 02:29 PM and a small niggle: if you go down to voice level from performance on (click on patch > edit > click on layer > edit) and you change something in a voice, the patch sometimes doesn't show as edited (with asterisk) if you go back up. also recall doesn't always work in this situation, only if you specifically go down to voice level with the left buttons (which is not always ideal because sometimes it's nicer to edit voices in context instead of solo'ed)
KODAMO	Posted on Tue 23 May 2023, 02:38 PM Thanks for the suggestions! and a small niggle: if you go down to voice level from performance on (click on patch > edit > click on layer > edit) and you change something in a voice, the patch sometimes doesn't show as edited (with asterisk) if you go back up. also recall doesn't always work in this situation, only if you specifically go down to voice level with the left buttons (which is not always ideal because sometimes it's nicer to edit voices in context instead of solo'ed) I will investigate this immediately. That nested system is very powerful but also hard to make perfect, I will check if there is a small bug and fix that in the upcoming firmware.
KODAMO	Posted on Tue 23 May 2023, 02:44 PM Ok I checked, and I think it's the intended behavior. When you edit a voice, the patch is not affected, this is normal since patches and voices are totally different elements (patches do only store references (links) to the voices, they don't contain them). Recalling will only recall the current element you're on. It's the same thing for Performances, they store link to patches, they don't store the patches inside themselves. So editing the related patches won't show the asterisk, since the Performance isn't affected
fish233	Posted on Tue 23 May 2023, 02:44 PM thanks for your reply! yes i understand, it's a complex synth and already marvellous how you dealt with that. i love it 🧡 edit: ok thanks, that makes sense! it also explains my first problem/request, i thought the EFM had a complete seperate edit buffer on performance level (for everything included, patches voices etc..) but yes it's all elements on their own level. good to know
KODAMO	Posted on Tue 23 May 2023, 02:50 PM That linking system was the only solution, otherwise we would have to store 256 * 16 * 128 voices (each performance, containing 16 patches, each containing up to 128 voices....) 😄 It's very powerful but yes it requires some careful management especially if you start sharing voices across multiple patches. When you're editing a voice that is already used somewhere else, I suggest you always save it to another slot instead of overwriting it, to prevent accidentally affecting your other sounds
fish233	Posted on Tue 23 May 2023, 02:52 PM > When you're editing a voice that is already used somewhere else, I suggest you always save it to another slot instead of overwriting it, to prevent accidentally affecting your other sounds yes indeed that's what i just discovered! thanks for clearing that up. my only gripe with this is that i'll probably pile up a lot of patches/voices with minimal differences 😄 but good to be able to backup everything and start over again, i'll do that from time to time
fish233	Posted on Wed 24 May 2023, 09:40 AM oh just discovered that if you are clicking on individual voices in a patch, edit them and press save in voice editor you can quickly save to new slot + saved voice gets autoloaded in the patch. this is neat! i was constantly switching to voice mode with the leftside button for duplicating, requiring a bit more steps to copy/paste/save and also annoyingly exiting multimode + reloading the new voice in the patch manually. huge workflow improvement 👍 edit: small request: if you save a voice this way, only that selected voice in the patch gets replaced with the new saved copy. if you use a bunch of copies in the patch (which i tend to do a lot to detune/pan) only the selected copy gets replaced while the other copies are still original with an * . i think it makes more sense to replace all those voices with the new saved version instead of only the selected one.
KODAMO	Posted on Wed 24 May 2023, 12:22 PM You're right, that totally make sense if they are the same voice. Will check that, thank you for suggesting this idea.
fish233	Posted on Tue 30 May 2023, 03:37 PM thanks! been thinking about this: > That linking system was the only solution, otherwise we would have to store 256 * 16 * 128 voices (each performance, containing 16 patches, each containing up to 128 voices....) 😄 what if you'd be able to save a performance with containing edited patches/voices and keep unedited voices linked? say you use about 2 edited and 2 unedited voices per patch, then it would only add up to 162 voices for that specific performance? i know, still a lot and probably currently not possible but nowhere near 16128. i still think for a complex synth like this it would be handy to be able to just dump the entire performance edit buffer instead of having to manually save 16*2 voices to new slots (which is also a giant waste of space imho if the voices are just small variations)